CERRIX Documentation
  • Introduction to CERRIX
  • CERRIX Functionalities
    • Getting Started
    • Using the Dashboard
    • Module Overview
      • Risks
        • AI Risk Description Refinement
        • Budget-based Risk Scoring
      • Controls
        • AI Control Description Refinement
      • Control Advanced Effectiveness Testing
        • Control Advanced Effectiveness Testing Video's
      • Incidents
        • Incidents Standing Data & Emails
        • Creating a New Incident
        • Incidents Workflow
        • Incidents Workspace
        • Incidents Roles & Rights
        • Incidents: Known Issues & Future Improvements
      • Events
      • Business Improvement Management
        • Measures of Improvement (MoIs)
          • Working with MoIs (Measures of Improvement)
        • Findings Report
      • Data Management
      • Third Party Management
      • Tasks & Control Execution
      • Key Risk Indicators (KRI's)
  • Admin Settings
    • External Connections
    • AI Settings
    • Authentication & User Provisioning
  • API Documentation
  • Best Practices & Guides
    • Control Design & Implementation, Execution & Effectiveness Testing: What's the Difference?
    • CERRIX AI FAQ
  • Implementation Guide
  • Import Templates
  • About CERRIX
    • Getting Support
    • Release Notes
    • Release Planning
    • Product Strategy & Roadmap
    • Heavy & Light Users
  • Compliance
    • Strategic Information Security Policy
    • ISO 27001
    • ISAE 3402 Type II
    • Privacy / GDPR
    • Security Statement
    • FSQS Certificate
Powered by GitBook
On this page
  • Control Design & Implementation Testing
  • Control Execution
  • Control Advanced Effectiveness Testing
  • Summary Table
  • Best Practices
Export as PDF
  1. Best Practices & Guides

Control Design & Implementation, Execution & Effectiveness Testing: What's the Difference?

In the CERRIX platform, controls are a central component of your governance, risk, and compliance framework. Understanding the different types of control activities and testing phases is essential for effective risk mitigation and assurance.

This article explains the differences between Control Design & Implementation Testing, Control Execution, and Control Effectiveness Testing.


Control Design & Implementation Testing

Definition: This is a test of the suitability and proper setup of the control. It determines whether the control, as designed and implemented, is capable of addressing the associated risk.

Purpose: To assess whether the control is appropriate and has been set up correctly within business processes or IT systems.

Example: Reviewing if a purchase approval workflow enforces segregation of duties between requester and approver.

In CERRIX: Documented in the Control Library or during Control Assessment workflows, often by second or third line teams (Compliance, Audit). Testing results are stored and linked to the control for transparency and auditability.


Control Execution

Definition: Control execution refers to the actual performance of a control activity by the responsible party or system, according to its defined frequency and procedure.

Purpose: Ensure that the control is carried out as designed, on time, and by the appropriate stakeholder.

Example: A weekly review of user access logs performed by an IT administrator.

In CERRIX: Control execution is logged through the Control Monitoring module. Control owners receive automated tasks or notifications to perform and evidence control activities.


Control Advanced Effectiveness Testing

Definition: This test checks whether the control operates effectively over time. It involves reviewing historical evidence to confirm that the control consistently works as intended.

Purpose: To validate that the control not only exists but also reliably mitigates the associated risk.

Example: Sampling the past 6 months of control executions to verify timely and complete access reviews were performed.

In CERRIX: Performed through the Control Advanced Effectiveness Testing feature, allowing testers to upload sampling results, attach evidence, and rate control performance (e.g., effective, partially effective, ineffective).

Learn more about Control Advanced Effectiveness Testing here:


Summary Table

Activity
Focus Area
Key Question
Typical Role

Design & Implementation Testing

Setup & Appropriateness

Is the control well-designed and implemented correctly?

Risk/Compliance/Audit

Control Execution

Operational Delivery

Was the control performed as required?

Control Owner

Effectiveness Testing

Performance Assurance

Is the control working reliably over time?

Compliance/Audit


Best Practices

  • Ensure roles and responsibilities are clearly defined in the Control Owner field in Cerrix.

  • Use automation to schedule recurring control executions and reminders.

  • Link testing activities to relevant risks, processes, and audits for traceability.

  • Leverage AI Assistance in Cerrix to prefill control descriptions and suggest test procedures based on best practices.


Need help setting up control workflows? Contact support or your CERRIX Customer Success Manager for hands-on assistance.

PreviousAPI DocumentationNextCERRIX AI FAQ

Last updated 2 months ago

Control Advanced Effectiveness Testing