Implement a control once. Satisfy every framework that asks for it.
Most compliance work is duplicated work. The same access control appears in the NCA ECC, the SAMA CSF, the CST CRF, and ISO 27001 Annex A — and most organisations we work with implement it four times. Govrly holds controls, measures, and evidence as shared objects, so one implementation carries every requirement it satisfies.
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 compliance management?
From the compliance programmes we build and run in Saudi Arabia: in our work, Compliance management is the work of knowing which requirements apply to your organisation, which controls satisfy them, who owns each one, and whether it is actually in place. It is the layer that connects a published framework to an operating reality — and in organisations carrying several frameworks, it is mostly an exercise in avoiding the same work being done repeatedly.
The distinction that matters is between a requirement and a control. A requirement is what a framework asks for. A control is what you actually do. The relationship between them is many-to-many: one control can satisfy requirements in several frameworks at once, and one requirement may need several controls.
Most compliance tooling collapses that relationship, treating each framework as a separate list to complete. That is where the duplication originates — not from the frameworks themselves, which overlap heavily, but from a data model that cannot represent the overlap.
How cross-framework reuse actually works
A single implemented control, carrying its requirement in four frameworks at once — with the same owner and the same evidence behind each.
Defined once in the control library with a named owner, an implementation status, and the evidence that demonstrates it operates. Everything below draws on this single record.
Carried as an implementation status against the applicable ECC control.
Scored against the maturity model for the relevant subdomain.
Mapped to the domain at the entity's assigned compliance level.
Recorded in the Statement of Applicability with its justification.
Each framework keeps its own scoring method — implementation status for the ECC, maturity levels for the CSF, compliance levels for the CRF, applicability for ISO. What is shared is the underlying control and the evidence, not the way each regulator reads it.
Why spreadsheet compliance stops scaling
A spreadsheet works for one framework in one entity. It fails at the second framework, and it fails badly at the second cycle.
- 01/06One tab per framework, no link between them
The same control appears in four tabs with four statuses that drift apart. Nobody can say which one is right, so the answer becomes whichever was updated most recently.
- 02/06Status is asserted, not derived
A cell says "implemented" because someone typed it. There is nothing behind the cell — no owner, no date, no artefact — so the assertion cannot be checked without asking a person.
- 03/06Ownership lives in a column, not a system
A name in a cell does not notify anyone, does not escalate, and does not update when that person changes role. Half the owners in a year-old tracker have moved on.
- 04/06Exclusions lose their justification
A control marked not applicable was excluded for a reason that made sense at the time. Six months later the reason is gone and only the exclusion remains — which is exactly what an assessor questions.
- 05/06A framework update means starting over
When an edition changes — ECC-1 to ECC-2, ISO 2013 to 2022 — a spreadsheet cannot tell you which of your existing controls already satisfy the new requirements. The mapping has to be rebuilt by hand.
- 06/06The reporting is a separate exercise
Producing a coverage view means someone building a summary from the tabs, by hand, every time it is asked for — and it is stale before the meeting starts.
What compliance management looks like in Govrly
Compliance management is one layer of the programme. Evidence collection, risk scoring, audit lifecycle, and privacy operations are separate use cases that draw on the same records — linked below rather than duplicated here.
Controls defined once and mapped to every framework requirement they satisfy. Adding a framework maps against what already exists rather than starting a new list.
Each control is applicable or excluded, and every exclusion carries written reasoning that stays attached to the record — the thing assessors ask about most.
Every applicable control has a person, a status, and a date. Not a department, not a column — a record that can be tracked and escalated.
Policies, standards, and procedures with version history, approval trails, and a traceable link to the controls they support.
Coverage by framework, by domain, and by owner, drawn from the underlying records rather than assembled by hand before each meeting.
Where an internal standard or a client requirement does not map to a published framework, define it as its own control set and map it alongside the rest.
Requirements, controls, and evidence
Three distinct things that spreadsheets tend to merge into one column — and separating them is what makes reuse possible.
Keeping requirements separate from controls is what lets a framework edition change without invalidating your implementation work. The requirements change; your controls mostly do not.
| Object | What it is | Who defines it | Reusable? |
|---|---|---|---|
| Requirement | What a framework asks for, in the framework's own words and numbering | The regulator or standards body | No — belongs to one framework |
| Control | What your organisation actually does to satisfy requirements | You | Yes — across every framework it satisfies |
| Measure | The specific implementation activity, with an owner and a status | You | Yes — attached to the control |
| Evidence | The artefact demonstrating the control operates | Your operations | Yes — linked to every requirement it supports |
| Mapping | The link between a requirement and the controls that satisfy it | You, once | This is what makes the rest reusable |
Who this is for
Running one or several frameworks and spending more time reconciling trackers than improving controls.
Needing a defensible answer to "are we compliant?" that is not assembled fresh each time it is asked.
Where the second or third framework is arriving and the honest question is how much of the existing work already covers it.
Moving from ECC-1 to ECC-2, or ISO 2013 to 2022, and needing to see which existing controls carry over.
Delivering programmes across several clients and frameworks, needing a consistent model rather than a bespoke spreadsheet per engagement.
Maintaining one control library that entities inherit rather than each subsidiary building its own.
How to move off spreadsheets
The mapping is the work. Everything else follows from it.
- 01/07Confirm which frameworks actually apply
And at what scope. Getting this wrong at the start propagates into every control decision that follows.
- 02/07Build the control library from what you already do
Start from your existing controls, not from a framework's list. You are describing your organisation, then mapping frameworks onto it — not the reverse.
- 03/07Map requirements to controls, once
This is the step that removes the duplication, and it is the step most programmes skip because it feels like overhead. It is the only part that compounds.
- 04/07Assign an owner to every applicable control
A named person with a target date. Where no owner can be found, that is itself the finding.
- 05/07Record every exclusion with its reasoning
At the moment of exclusion, while the reasoning is still fresh. Reconstructing it a year later for an assessor rarely goes well.
- 06/07Link documents to the controls they support
So a policy change surfaces the controls it affects, rather than the connection living in someone's memory.
- 07/07Let evidence attach as operations produce it
Rather than collecting it in the weeks before an assessment. This is where compliance management hands over to evidence management.
Compliance management — FAQs
Software that holds the relationship between requirements, controls, owners, and evidence in one connected model. Its core job is knowing which requirements apply, which controls satisfy them, who owns each control, and whether it is genuinely in place — rather than maintaining a separate list per framework.
A requirement is what a framework asks for, in the framework's own words and numbering — it belongs to that framework. A control is what your organisation actually does to satisfy requirements. The relationship is many-to-many: one control can satisfy requirements across several frameworks, and one requirement may need several controls.
Yes, and this is where most of the saving in a multi-framework programme comes from. An access control implemented once can carry its NCA ECC requirement, its SAMA CSF subdomain, its CST CRF control, and its ISO 27001 Annex A entry — with each framework applying its own scoring method to the same underlying record.
Substantial at control level. The NCA ECC, SAMA CSF, and CST CRF all cover governance, access control, asset management, incident response, and third-party security, and the CST CRF explicitly aligns with ISO 27001. What differs is scope, assessment method, and the supervising authority — not usually the underlying safeguard.
Yes. Where an internal standard, a group policy, or a client contractual requirement does not map to a published framework, it can be defined as its own control set and mapped alongside the rest, so it draws on the same controls and evidence.
Because requirements and controls are held separately, a new edition changes the requirements without invalidating your implementation work. The mapping is reviewed to see which existing controls already satisfy the new requirements, and the genuine gap becomes visible — rather than the whole programme being rebuilt from a new list.
They are closely connected but distinct. Compliance management is the framework, control, and requirement layer — what applies, who owns it, and whether it is in place. Evidence management is the request, review, and reuse of the artefacts that prove it. Both draw on the same records.
A spreadsheet holds a status; it does not hold the relationships behind it. There is no link between the same control appearing in four framework tabs, no owner that can be notified, no justification attached to an exclusion, and no way to see which existing controls already satisfy a newly added framework. Those relationships are the whole point.
Yes. A group-level control library can be inherited by entities that rely on shared services, with each entity adding what is specific to its own environment and answering to its own regulator with its own scoring method.
At the boundary of the neighbouring use cases. Risk scoring and the audit lifecycle, evidence request and review, privacy records and rights requests, and vendor assessments each have their own workflow, drawing on the same underlying controls and evidence rather than duplicating them.
One control library. Every framework you carry.
See how a single implementation and a single evidence set can satisfy four regulators at once.
