Risk and audit are one loop. Most organisations we work with run them as two.
Audit tests the controls that treat your risks, and its findings should change your risk position. When the register and the audit programme live in separate systems, that loop never closes — and the same finding reappears cycle after cycle. Govrly holds both on the same records.
This page describes how we approach this work and how Govrly supports it. Where regulatory requirements are mentioned, confirm what applies to your organisation against the source documents published by the relevant authority.
What is risk and audit management?
From the compliance programmes we build and run in Saudi Arabia: risk and audit management is the assurance layer of a compliance programme. Risk management identifies what could go wrong, scores it before and after controls, and assigns treatment. Audit independently tests whether those controls actually operate. The two are a single loop: audit findings should change the residual risk score, and the risk register should drive what gets audited next.
In most organisations we work with they are not one loop. The risk register sits with a risk function and gets reviewed quarterly. The audit programme sits with internal audit and runs on an annual plan. They reference the same controls, but nothing connects them — so a finding closes without the risk score moving, and a high residual risk goes unaudited because the plan was set before it was raised.
The consequence is familiar: the same finding recurs across cycles, and the risk register describes a position that audit has already disproved.
The loop that has to close
Five steps, on one set of records. Break the link at any point and the assurance stops being assurance.
Scored for inherent likelihood and impact, before any control is considered.
One or more controls linked to the risk, each with a named owner and an implementation status.
What remains after the control operates — which is the number leadership actually needs.
Independent testing of whether the control genuinely operates as claimed.
A failed test raises the residual score and triggers corrective action — closing the loop.
Step five is the one most programmes lose. A finding is raised, remediated, and closed — while the risk register that depended on that control is never updated, and continues to report a residual score the audit already contradicted.
Inherent and residual risk
Two scores on every risk. Recording only one is the most common weakness in a risk register, and it removes the ability to show whether controls are working at all.
A residual score with no tested control behind it is an opinion. That distinction is what an auditor, a regulator, and a board are all separately trying to establish.
| Score | What it measures | Why it matters |
|---|---|---|
| Inherent | Likelihood and impact before any control is applied | Shows the size of the exposure you are managing, and justifies the investment in the control |
| Residual | What remains once the linked controls operate | The number leadership decides on. It is only credible if the controls behind it have actually been tested |
| The gap between them | How much risk the control set is genuinely removing | The clearest evidence that a control programme is producing value rather than paperwork |
| Accepted risk | Residual risk formally accepted rather than treated further | Acceptance must be an explicit, owned, documented decision — not the absence of one |
Where risk and audit programmes break down
- 01/07The register is written once and reviewed annually
Risks identified in a workshop, scored on the day, and left untouched until the next workshop — while the environment they describe changes continuously.
- 02/07Risks are not linked to controls
A register that lists risks without connecting them to the controls that treat them cannot produce a defensible residual score, because nothing explains the reduction.
- 03/07The audit plan ignores the register
An annual plan set in advance, testing what was tested last year, while the highest residual risks raised since go unexamined.
- 04/07Findings close without verification
An owner reports the corrective action complete and the finding is marked closed. Nobody confirms it. The next cycle raises the same finding.
- 05/07Root cause is skipped
The symptom is fixed, the underlying cause is not, and the finding recurs in a different system six months later.
- 06/07Audit re-collects evidence that already exists
Fieldwork begins with a fresh document request to teams who submitted the same artefacts to compliance weeks earlier.
- 07/07Nothing flows back to the risk score
The loop's final step. Findings are resolved, the register is not updated, and residual scores drift away from what audit actually found.
Risk and audit in Govrly
The register and the audit programme run on the same records as your controls and evidence, so the loop closes by construction rather than by discipline.
The control library, evidence workflow, privacy records, and vendor assessments are separate use cases drawing on the same underlying records — linked below rather than duplicated here.
Each risk carries inherent and residual scores, an owner, a treatment decision, and the specific controls that reduce it — so the residual number has something behind it.
Plan against the risks that actually matter and the controls that treat them, rather than repeating last year's scope because it is what exists.
Audits work from evidence already collected and reviewed, so fieldwork starts with testing rather than with a fresh document request.
Every finding records what failed, why it failed, who owns the correction, and when it is due — not just that something was wrong.
A corrective action closes when a verification step confirms it, not when the owner says it is done. This single distinction is what stops findings recurring.
A failed control test surfaces against every risk that depended on it, so residual scores reflect what audit found rather than what was assumed.
What your frameworks require here
Risk and audit are not optional additions to a compliance programme. Every framework you carry mandates both.
Risk management, compliance, and audit sit within the Cybersecurity Governance domain, with implementation evidenced like any other control.
Cyber Security Risk Management and Compliance, including the review and audit subdomains — where evidence quality most often determines the maturity score.
One of the six control domains, with independent compliance verification at the higher compliance levels.
Risk assessment and treatment are mandatory clause requirements, as are internal audit and management review — none of which can be excluded.
Risk assessment is expected where processing or transfer conditions require it, with the reasoning recorded.
One risk register and one audit programme, mapped across every framework — rather than a separate assurance exercise for each.
How to close the loop
- 01/07Link every risk to the controls that treat it
Start here. A register without this link cannot produce a defensible residual score, and everything downstream depends on it.
- 02/07Score inherent and residual separately
If only one score exists, you cannot demonstrate that the control programme reduces anything — which is the question leadership is actually asking.
- 03/07Make risk acceptance an explicit decision
With a named owner, a stated rationale, and a review date. Accepted risk is a legitimate position; undocumented accepted risk is a finding.
- 04/07Scope the audit plan from the register
Test the controls behind the highest residual risks first. Repeating last year's scope tests what you already know.
- 05/07Require root cause on every finding
The symptom and the cause are different things, and fixing only the symptom is why findings recur.
- 06/07Separate the verifier from the owner
Wherever the structure allows it. Self-verified closure is the weakest link in most audit programmes.
- 07/07Push findings back into the register
A failed test should move the residual score of every risk that relied on that control. This is the step that turns two functions into one loop.
Risk and audit — FAQs
The assurance layer of a compliance programme. Risk management identifies what could go wrong, scores it before and after controls, and assigns treatment. Audit independently tests whether those controls actually operate. The two form a single loop: audit findings should change the residual risk score, and the risk register should drive what gets audited next.
Inherent risk is the likelihood and impact before any control is applied — the size of the exposure. Residual risk is what remains once the linked controls operate, and it is the number leadership decides on. The gap between them shows how much risk the control set is genuinely removing, which is only credible if those controls have been tested.
Because audit tests the controls that treat the risks, and its findings should change the residual score. When the register and the audit programme sit in separate systems, a finding can close without the risk position moving, and a high residual risk can go unaudited because the plan was set before it was raised. The loop stays open.
A corrective action closes only when a verification step confirms it was completed and effective — not when the owner reports it as done. Self-reported closure is the most common reason the same finding reappears in the following cycle.
From the risk register. Test the controls behind the highest residual risks first, rather than repeating the previous year's scope. A plan set in advance and never revisited tests what you already know and leaves newly raised risks unexamined.
Yes, all of them. Risk management and audit sit within the NCA ECC's governance domain, form SAMA CSF domain 3.2, appear as a control domain in the CST CRF, and are mandatory clause requirements in ISO 27001 under clauses 6, 9.2 and 9.3 — where they cannot be excluded.
Yes. Because risks link to controls and controls map across frameworks, a single register and a single audit programme can satisfy the risk and audit requirements of every framework you carry, rather than running a separate assurance exercise for each.
Yes, provided it is an explicit decision with a named owner, a stated rationale, and a review date. Formally accepted residual risk is a legitimate position. Risk that is accepted by default, because nobody decided anything, is a finding.
Not where evidence has already been collected and reviewed against the relevant controls. Fieldwork can begin from approved artefacts and focus on testing rather than on a fresh document request to teams who submitted the same material weeks earlier.
Compliance management is the framework, control, and requirement layer — what applies, who owns it, and whether it is in place. Risk and audit is the assurance layer — what could go wrong, how much exposure remains, and whether the controls genuinely operate when independently tested. Both run on the same underlying records.
Close the loop between risk and audit
Risks linked to controls, audits scoped from risk, and findings that close only when someone verifies them.
