Enterprise Risk
Every risk, scored your way, measured against the appetite the board set
Your taxonomy, your matrices, your formulas. Sentinel Unity runs the methodology you already defend to the board, compares every score to appetite, escalates on its own, and explains how each number was reached.
- Versioned taxonomies, matrices, severity bands and scoring formulas as configuration, not code
- Score on a matrix, or quantitatively with frequency and magnitude distributions and scenarios
- Appetite and tolerance per category, entity or objective; a breach runs the action you chose
- Inherent, residual and target scoring, and every score explains its factors
In the application · Assure
- Risk register
- Heatmap
- Appetite & tolerance
- Treatment & acceptance
- Escalations
- Risk universe
- Board report
Methodology
Your scoring model, not ours
Matrix definitions carry versions, axes, axis levels, severity bands and per-cell mappings. Formulas are versioned too, with overrides where a programme needs to diverge, and normalisation profiles when programmes score on different scales.
- Matrix and formula versions kept side by side so history stays interpretable
- Taxonomy imported as a draft, diffed against the active version, then activated
- Quantitative analysis with simulation results kept on the risk
- Deletion guarded: a node in use returns a conflict rather than orphaning records
Appetite that acts
Within appetite, within tolerance, above tolerance, outside appetite
Define appetite and tolerance per category, entity or objective. Each risk lands in one of four bands, and a breach runs the action you chose: notify, escalate, mandate treatment, or put it in front of the board.
- Appetite definitions and thresholds; tolerance metrics, rules and bands
- Breach actions configured per tolerance rule
- Escalates overdue treatment and lapsed acceptance automatically
- Pending validation and reassessment queues for the second line
Privileged accounts without review
KRI · monthly · owner: Security Operations
Treatment and reporting
Mitigate, transfer, avoid, or formally accept
Treatment plans hold actions with owners, targets and the controls they rely on; control effectiveness feeds the residual score. Acceptances expire; reviews run on a cadence. The board pack exports with trend and history.
- Named owners, with confidential-risk visibility restricted to those cleared
- Reviews and reassessments that recalculate residual exposure
- Score snapshots, board roll-up snapshots and hierarchy aggregates
- Risk universe versions with attestation records
Treatment decision
- 1Treatment planActions with owners, priority, and due dates
- 2Action trackingStatus per action, SLA where defined
- 3ReassessmentResidual score recalculated after closure
Framework alignment
Works with your control frameworks
This module shares the platform control library. International standards, sector regulations and your own internal standard are loaded the same way and mapped to one another, wherever you operate.
Solutions by role
Built for your team
See enterprise risk in your environment
A walkthrough scoped to your entities, your frameworks, and the way your programme is actually run.