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
  • Incidents Standing Data
  • Creating a New Incident
  • Incidents Workflow
  • Incidents Workspace
  • Incidents Roles & Rights
  • Best Practices and Tips
  • Key Benefits of Incidents Compared to Events
Export as PDF
  1. CERRIX Functionalities
  2. Module Overview

Incidents

The Incidents module in CERRIX helps organizations track, manage, and resolve risk-related incidents in a structured and auditable manner. This module supports the full lifecycle of incident management, from initial reporting to final resolution, with integrated workflows, data governance, and transparency across all stakeholders.

Use this overview to navigate to detailed guides on each component of the Incidents module.

The Incidents module is designed to help users:

  • Capture and report new incidents in a standardized way

  • Monitor the status and progress of incidents via a structured workspace

  • Apply organization-specific workflows for processing incidents

  • Maintain accurate and consistent reference data for categorizing and analyzing incidents

Below are the key documentation articles that explain each component of the Incidents module:

Incidents Standing Data

Review the reference data that underpins incident classification and reporting.

  • Categories and subcategories

  • Impact and severity ratings

  • Cause and root cause options

  • Screenshot placeholders:

    • Standing data configuration

    • Example dropdowns using standing data


Creating a New Incident

Learn how to create a new incident from scratch, including required fields, categories, and options for assigning responsibilities.

  • Walkthrough of the incident form

  • Mandatory vs optional fields

  • Assigning responsible users or departments

  • Screenshot placeholders:

    • Incident creation form

    • Example of a completed incident entry


Incidents Workflow

Understand how incident workflows are configured and how incidents progress through stages in your organization.

  • Overview of workflow stages

  • Transition logic and actions

  • Escalation and reassignment rules

  • Screenshot placeholders:

    • Workflow stage diagram

    • Example of an incident in-progress


Incidents Workspace

Explore the centralized workspace where you can view, filter, and manage all existing incidents.

  • Grid and filter functionalities

  • Status indicators and priority levels

  • Search and sorting capabilities

  • Screenshot placeholders:

    • Incidents workspace grid

    • Filtering panel


Incidents Roles & Rights

Understand how user roles determine access and responsibilities within the Incidents module. This page outlines all available roles, their permissions, and how they support collaboration across teams during the incident lifecycle.


Best Practices and Tips

To make the most of the Incidents module, consider the following best practices and tips:

  • Define clear escalation paths and responsibilities in your workflow configuration

  • Regularly review and update standing data to align with organizational risk posture

  • Use custom fields if your organization requires additional data points

  • Consider integrating incidents with related modules (e.g., Risk, Controls, or MoI's) for better traceability


Key Benefits of Incidents Compared to Events

  • Greater flexibility – Easily create custom fields for each incident type, allowing full customization to match your organization’s needs.

  • Streamlined workflows – A single, standardized workflow for all incident types simplifies handling and tracking.

  • Enhanced financial impact tracking – Record financial impact per department and third party for improved reporting.

  • New and improved fields – Includes a due date, support for Framework dimensions, and the ability to register third parties directly in incidents.

  • Improved collaboration – Discuss incidents directly within the incident page using built-in comments, enabling faster decision-making and follow-ups.

PreviousControl Advanced Effectiveness Testing Video'sNextIncidents Standing Data & Emails

Last updated 2 days ago

Incidents Standing Data & Emails
Creating a New Incident
Incidents Workflow
Incidents Workspace
Incidents Roles & Rights