Many remediation plans built after a SAMA Cyber Resilience Framework Review fail for a reason that has little to do with effort or budget. The findings refer to each other. Closing one requires evidence that only exists once another is closed, and that other finding in turn waits on the first. Managing SAMA CRFR remediation dependencies deliberately, from the first week, is what separates a plan that converges from one that circles.
This article describes the three dependency patterns we see, a simple method for mapping them, and a sensible order of work.
Why findings depend on each other
The SAMA CRFR assesses cyber resilience across a set of domains, and the findings that result are rarely independent. A weakness in asset inventory affects vulnerability management. A gap in governance affects how incident response is approved and tested. Reviewers write findings against observable control failures, so the same root cause can appear in several places, and the closure evidence for one finding often relies on an artefact owned by another.
The usual gaps follow from this:
- Each finding is assigned to a separate owner who plans in isolation.
- Evidence requirements are read literally, without asking what else must exist first.
- Deadlines are set per finding, not per chain of findings.
- Nobody holds the whole picture, so a loop is discovered only when a deadline is missed.
The three dependency patterns
1. Hierarchical
One finding is a foundation for others. A policy, an asset register or a defined governance role must exist before downstream controls can be evidenced. The direction is one-way and clear. Hierarchical dependencies are the easiest to sequence: the foundation goes first, and dependent findings are scheduled behind it.
2. Lateral
Two or more findings need each other's outputs, but not at the same moment. For example, a monitoring improvement may need a completed asset list, while the asset list only needs a first-pass scope from the monitoring team. Lateral dependencies are manageable when the shared output is split into stages, so each finding can take what it needs from an early version.
3. Circular
Finding A cannot close without evidence from finding B, and B cannot close without evidence from A. Followed literally, neither ever closes. Circular dependencies are almost always a sign that the findings share a root cause or that the evidence requirement has been defined too broadly. They must be broken deliberately, not worked around.
The three sequences that prevent circularity
Each sequence below is a way to resolve one of the patterns into an order that closes every finding once.
- Foundation first. Place hierarchical foundations at the front of the plan, and do not allow dependent findings to start evidence collection until the foundation is approved. This removes the most common cause of rework: evidence gathered against a control that later changes.
- Staged hand-off. For lateral pairs, define a minimum viable output from the first finding, such as an approved scope or a first-cycle register, and let the second finding proceed against it. The first finding then completes its full output in parallel.
- Break and bundle. For a true loop, identify the shared root cause. Either close both findings through one piece of work with one evidence pack, or split the evidence requirement so that each finding relies on a distinct, earlier artefact. Agree the approach with the reviewer before work starts.
A week-one mapping method
The mapping exercise is simple enough to do on a whiteboard, and it should be done before owners commit to dates.
- List every finding with its owner, its stated evidence requirement and its regulatory deadline.
- For each finding, write down every input it needs from another finding or from another team.
- Draw findings as boxes and inputs as arrows. Use one style of arrow for foundations, another for staged hand-offs.
- Look for loops. Any closed path of arrows is a circular dependency.
- Apply one of the three sequences to each cluster, then redraw the map until no loops remain.
- Convert the map into a working order and carry the dependencies into the plan and the risk log, so that a slipping foundation is visible as a risk to everything behind it.
Keep the map as a living document. Dependencies change when evidence is rejected, scope shifts or an owner changes, and the map should be reviewed at each weekly status meeting.
What changes for the organisation
Ownership shifts from per-finding to per-chain. One person should be accountable for each cluster of related findings, even if several teams contribute. Deadlines should be set at the cluster level, with the foundation dates driving the rest. Evidence should be reviewed internally before it is submitted, since a rejected artefact in a foundation finding can reopen several others.
Where the remediation touches documents or risk processes, related work such as policies, standards and procedures, or the cyber risk register, belongs on the same map, because these are frequent foundations for technical findings.
How we support this
Our Regulatory Compliance Remediation Program is built to run remediation after an assessment or regulatory review. We run your remediation program after an assessment or regulatory review: prioritizing gaps, coordinating owners, implementing controls and building the evidence that closes each finding. The work follows four stages: prioritize, mobilize, remediate and prove. In the first stage, gaps are ranked by risk, regulatory deadline and effort, which is where the dependency map is built and the sequence agreed.
The deliverables support the mapping method directly: a remediation roadmap, a weekly status and RAID log, evidence packs per control, a monthly steering committee report and a closure report for the regulator. Evidence is reviewed before closure, so findings are formally closed only once the proof is ready.
We work alongside your internal team. We provide the program discipline and specialist depth, while your teams own and operate the controls. The program runs as a retainer of 3–9 months, depending on the number and complexity of findings.
Next step
If your SAMA CRFR remediation plan contains findings that cite each other, the most useful first step is a dependency map before any dates are committed. Speak with us about the Regulatory Compliance Remediation Program and we can start from your findings and work out the order in which they can each close once.
