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
  • Overview of the Incident Workflow
  • Key Steps in the Workflow
  • Incident Creation
  • Assessing & Evaluating an Incident
  • Linking Related Items
  • Business and Framework Dimensions
  • Attach Supporting Documents
  • Review and Closing an Incident
  • Chat and Incident History
  • Incidents Workflow Emails Notifications
Export as PDF
  1. CERRIX Functionalities
  2. Module Overview
  3. Incidents

Incidents Workflow

PreviousCreating a New IncidentNextIncidents Workspace

Last updated 1 day ago

The Incidents module in CERRIX is designed to streamline the process of handling incidents within your organization, providing a structured and auditable workflow. This guide walks you through the standard flow of an incident's lifecycle and highlights key actions and interface elements you can interact with during the process.


Overview of the Incident Workflow

The Incident Workflow guides users through each required step in processing incidents, clearly showing the current status and future actions needed.

At the top of the incident screen, you'll see a clear visualization of the workflow steps:

  • Completed steps are highlighted green.

  • Available next steps are clearly indicated, showing what actions can currently be performed.

  • Future steps are visible but inactive until prior required steps have been completed.

Note: Only assigned users can perform actions at each workflow step.


Key Steps in the Workflow

Incident Creation

Read more about creating a new incident in this article:


Assessing & Evaluating an Incident

After an incident has been reported:

  1. To continue with processing, select either:

    • Accept incident to move forward.

    • Reject incident if it's invalid or incorrect.

    • Leave a comment (required). This comment will be visible in the Chat and Incident History

  2. Click Confirm.

    • The "Assessing" workflow status at the top of the page changes to green, indicating the incident is officially confirmed.

    • The incident now moves to the Improving stage.


Linking Related Items

  • Link existing Risks or Controls

    • Use the dedicated button to select relevant items from the system.

  • Create a Measure of Improvement (MOI)

    • Opens a new tab for MOI creation.

If an incident is created and linked to a Risk or Control, that incident can also be found as a linked item in the specific Risk or Control. For Risks and Controls these incidents are shown in page of linked events.


Business and Framework Dimensions

Additional configuration dimensions include:

  • Business Dimensions Allow associating incidents with particular business dimensions defined in your system.

  • Framework Dimensions Facilitate linking incidents to your organization's compliance and internal control frameworks.


Attach Supporting Documents

  • Drag and drop or select a file to upload.

  • Files will be attached directly to the incident for context and traceability.


Review and Closing an Incident

At the Review stage, the incident has the status Ready for Review:

  1. Review all linked data, documents, and details carefully.

  2. Next, there are two options:

    1. Approve & close, or click

      • The incident workflow finishes, and the incident moves to a read-only state.

      • The workflow view clearly indicates that the incident is completed and can no longer be edited unless it's reopened.

    2. Reject

      1. The incident workflow goes back to the Improving stage


Chat and Incident History

The incident page includes an interactive Chat and History Pane accessible from the right side:

  • View complete audit trails of incident updates, statuses, notes, and decisions made throughout the workflow.

  • Use this pane for update notes. Future releases will enable direct chat functionalities among incident participants for additional collaboration.


Incidents Workflow Emails Notifications

Email messages automatically alert relevant users when the incident advances through workflow stages:

  • Email behaviors in the Incidents module mirror those in the existing Events module used within your CERRIX environment.

  • In your production environment, relevant stakeholders will receive emails upon workflow status changes (e.g., confirmation, review readiness, approval).

  • In this demonstration environment, emails are inactive, but in production, known standard processes apply.

Note: If your existing CERRIX configuration refers to these as "Events," you might consider standardizing your terminology to "Incidents" for clarity, though this naming choice remains flexible.

In the Assessing, Improving or Review stage, you’ll see a Link iconwhich can be used to link relevant items by clicking on the linking button:

Click on the Attach icon

Creating a New Incident