Platform module · Governance, risk and compliance
Risk, control and audit on the assets that matter most.
Risks, controls, audits and obligations sit on the same assets as everything else, so each one carries the value of what it protects. The work goes first where the most value is at stake.
One chain, one set of records
From the asset to the evidence, without copies.
Risk, internal control and internal audit usually keep their own lists. Here they work on one chain: a risk is raised on an asset, a control treats it, a test proves it, and a finding goes back to the owner.
Register and treatment
Risks raised on real assets, assessed, treated and monitored, with owners and due dates.
Library, tests, evidence
One control library mapped to risks and requirements. Design and effectiveness tests keep their evidence attached.
Plans, findings, follow-up
Audit programmes built on the asset and control universe, findings tracked to closure as actions.
Regulations and obligations
Requirements from regulations and standards mapped once to controls, and reused for every audit that asks.
Value at risk
A severity score is not a priority.
A critical weakness on a test server and a moderate one on the payment gateway are not the same problem. Ranking by the value of the asset behind a weakness puts the effort where the business depends on it.
Prioritised by value
The score decides where governance effort goes.
Exposure in value terms
A risk on assets with a combined Vi of 805 in a portfolio of 15,000 touches 5.4% of organisational value. That share, not a colour, sets the treatment.
Test where it counts
Controls on Sustain and Invest assets are reviewed more often than those on assets heading for retirement.
Loss sets the priority
When an asset fails, the value lost (ΔVi) sets the priority and the target time, from P1 to P5.
Example figures from the framework books. How value is measured →
Inside the module
What risk, control and audit teams work with.
Part of one platform
The red line runs through the value engine.
GRC connects policies, risks, controls, audits, compliance and regulations. Every station it shares with the other lines is a record you only keep once.
Risk follows dependencies
A risk on a server reaches the applications and capabilities above it, with their value.
Findings become work
Treatment plans and audit findings turn into tracked actions with owners and deadlines.
Incidents feed the register
Real incidents update risk likelihood and show which controls failed.
Start with Core and GRC.
Bring your risk register and control library, link them to assets, and see which risks threaten the most value.