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
Export as PDF
  1. CERRIX Functionalities
  2. Module Overview

Control Advanced Effectiveness Testing

PreviousAI Control Description RefinementNextControl Advanced Effectiveness Testing Video's

Last updated 1 month ago

Control Effectiveness Testing ensures that controls are functioning as intended to mitigate risks. This process involves multiple steps to validate design and operational effectiveness.

Steps for Effectiveness Testing

Step 1: Source Document Upload

  1. Navigate to the test plan in the Controls module.

  2. Click Upload Source Document.

  3. Drag and drop files or browse to upload relevant documents.

  4. Optionally, add a description for the uploaded file.

Step 2: Generating Samples

  • Choose a sampling method:

    • By Number: Generate samples based on a predefined count.

    • By Date: Use a date range to generate samples.

    • By Spreadsheet: Upload a spreadsheet and configure sample generation.

Step 3: Uploading Evidence

  • Upload evidence for each sample.

  • Mark samples without evidence and provide a reason in the comments.

Step 4: Testing

  • Assess each sample and document findings.

  • Provide scores and comments for each test step.

Step 5: Reviewer Step

  • The reviewer assesses the results, provides feedback, and confirms the final outcome.

Best Practice: Ensure all required documents are uploaded before moving to the next step.