Capital-market firms in the Kingdom preparing for a follow-up assessment need a remediation approach that reflects how the controls actually relate to one another. In SAMA CRFR remediation capital market Domain 3 findings are rarely self-contained. Many of them rest on cybersecurity controls assessed elsewhere in the framework, and that dependency is where programs lose time.
This article describes the pattern we see at brokers, asset managers and other licensed firms, and a method for avoiding it. It is written for chief risk officers, compliance directors and remediation program managers.
The problem: findings that look independent but are not
The SAMA Cyber Security Risk Framework Review (CRFR) organizes expectations into domains. Technology-risk findings under Domain 3 commonly cover areas such as change management, system resilience, logging, monitoring and operational procedures. Cybersecurity control findings under Domain 4 cover areas such as access control, detection and incident response.
On a spreadsheet these appear as separate lists with separate owners. In practice they overlap. A technology-risk finding about trading-platform change control may rely on how privileged access is governed. A finding about operational resilience may depend on incident-response logging and escalation. If the technology team closes its findings first, and the cybersecurity team then changes a control the first set relied on, the earlier work has to be reopened.
Why sequential remediation creates circular rework
Most firms organize remediation by domain because the assessment report is organized that way. Each domain owner builds a plan, and the plans run one after another or loosely in parallel without a shared view of what depends on what.
The result is predictable:
- A Domain 3 control is implemented and evidenced against a particular logging design.
- A Domain 4 workstream later changes the logging or incident-response requirement.
- The Domain 3 control, and sometimes the platform configuration behind it, must be revisited and re-evidenced.
- Both deadlines move, and the reviewer sees closed findings that no longer hold.
For a trading platform the cost is higher than for most systems. Configuration changes need testing, change windows and business sign-off, and every unnecessary change adds operational risk during market hours.
The cross-domain dependency map
The remedy is to establish dependencies before any implementation begins. A cross-domain dependency map is a simple working document. It lists every finding, shows which other findings or controls it relies on, names the owner of each, and marks which items are fixed and which are likely to change.
A useful map answers four questions for each finding:
- Which controls, in either domain, must be in a stable state before this finding can be closed?
- Which systems or platform configurations will this remediation touch?
- Which other workstreams could change the requirement this finding is built on?
- What evidence will a reviewer expect, and does it depend on another team's evidence?
Once these are answered, the findings fall into groups. Some can proceed immediately in parallel. Some must wait for a specific upstream decision. Some should be combined into a single change so that a platform is configured once, not three times.
Designing for requirements that change mid-program
Requirements move during a remediation program. A regulator may clarify an expectation, an internal risk decision may tighten a standard, or the cybersecurity team may revise incident-response logging after a design review. A plan that assumes none of this will happen is fragile.
The dependency map makes change manageable because the affected findings are visible at once. When a logging requirement changes, the firm can see which Domain 3 findings reference it, which platform configurations are involved and which evidence packs need updating. Platform teams can hold changes that depend on an unsettled decision, and proceed with those that do not.
Two practices help:
- Decision gates for items that other findings rely on, such as logging scope, retention and escalation criteria. The decision is made and recorded before dependent implementation starts.
- Configuration batching, so that the trading platform is changed once for a group of related findings and not repeatedly.
Governance that matches the map
A dependency map only works if ownership is clear. Each finding needs one accountable owner, and each dependency needs a named counterpart in the other domain. Weekly coordination between technology-risk and cybersecurity owners is more effective than separate domain meetings, because the interactions are the point.
Senior oversight matters too. A steering committee that sees progress by domain will miss circular risk. A committee that sees progress by dependency group can ask the right question: which upstream decision is holding the most findings?
Evidence that survives a reviewer's questions
Closure under SAMA CRFR depends on evidence, not on assertions that a control exists. Evidence should show that the control is designed, implemented and operating, and it should be consistent across domains. If a Domain 3 evidence pack describes one logging configuration and a Domain 4 pack describes another, the reviewer will notice.
Building evidence against the dependency map helps here. Shared artifacts, such as a logging standard or an access review record, can be referenced by every finding that relies on them and updated in one place.
How we run this for capital-market firms
Our Regulatory Compliance Remediation Program is built around this discipline. 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 program follows four stages:
- Prioritize: gaps ranked by risk, regulatory deadline and effort.
- Mobilize: owners, plans and governance agreed.
- Remediate: implementation support and weekly tracking.
- Prove: evidence reviewed and findings formally closed.
Dependency mapping belongs in the first two stages, so that owners and plans are agreed with the interactions already visible. Where the dependencies expose gaps in written standards, for example an incident-logging standard that does not yet exist or is inconsistent with practice, our Policies, Standards & Procedures service can develop or update the documents in Arabic and English.
The deliverables include 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. The RAID log is where cross-domain dependencies and their risks are tracked week by week.
The usual model is to work alongside your internal team. We provide the program discipline and specialist depth; your teams own and operate the controls. That division matters for trading platforms, where platform engineers and business owners must remain accountable for changes to their own systems.
Practical steps before your follow-up assessment
Even before a program is mobilized, a firm can take preparatory steps:
- Consolidate all open findings from both domains into one register.
- For each Domain 3 finding, record the Domain 4 controls it relies on.
- Identify the three or four upstream decisions that most findings depend on, and settle them first.
- Group findings that touch the same platform so that changes are batched.
- Agree who can approve a change to an upstream requirement once work has started.
Closing
A SAMA CRFR follow-up assessment rewards firms that can show consistent, durable closure, not a list of findings closed and later reopened. If your Domain 3 and Domain 4 findings are being worked on separate tracks, a dependency map is the most useful first step. Our Regulatory Compliance Remediation Program typically runs as a retainer of 3–9 months and combines prioritization, program management, control implementation support and evidence review. Contact CISO Consulting to discuss how it would apply to your findings.
