One connected system, not five disconnected tools
Most compliance stacks are a framework tracker, a risk spreadsheet, a document folder, an audit tool, and a privacy register — each holding its own version of the same control. Govrly holds them as one connected model, so a change in any of them is visible in all of them.
What is Govrly?
Govrly is a governance, risk and compliance platform built for the Saudi regulatory environment. It holds frameworks, requirements, controls, evidence, risks, audits, vendors, assets and privacy records as connected objects rather than separate lists — so one implemented control can satisfy requirements across the NCA ECC, SAMA CSF, CST CRF, Saudi PDPL and ISO 27001:2022 at the same time.
The distinction that matters is not the feature list. Most GRC tools can store a control, attach a document, and produce a dashboard. The difference is whether those objects are linked — whether marking a control as failed automatically surfaces against every risk that depended on it, every framework requirement it satisfied, and every entity that inherited it.
That is the whole design. Everything below follows from it.
The connected model
Nine object types, and the relationships between them. The relationships are the product — the objects themselves are unremarkable, and every competitor has them.
A published control set — NCA ECC, SAMA CSF, CST CRF, ISO 27001:2022, Saudi PDPL, or one you define yourself.
Contains requirements · Keeps its own scoring method
What a framework asks for, in the framework's own words and numbering. It belongs to that framework and cannot be reused elsewhere.
Satisfied by one or more controls · Scored in its framework's terms
What your organisation actually does. This is the object that makes multi-framework work possible, because one control can satisfy requirements in several frameworks at once.
Satisfies many requirements · Treats risks · Carries measures and evidence
The specific implementation activity, with a named owner, a status, and a target date. Where accountability actually lives.
Belongs to a control · Owned by a person, not a department
The artefact proving a control operates — requested from an owner, reviewed before it counts, and given a validity period.
Supports many requirements · Expires · Reviewed by someone other than the owner
Scored inherent and residual, with treatment and ownership. The residual score only means something if the controls behind it have been tested.
Treated by controls · Updated when an audit finding lands
Independent testing, with findings carrying root cause, owner, due date, and a verification step distinct from the owner's report.
Draws on approved evidence · Feeds back into residual risk
Suppliers and systems, with the data they touch and the controls their access affects.
Linked to controls, data categories and risks
Processing activities, lawful basis, rights requests, breach decisions, transfers and retention.
Protected by the same controls carrying your security obligations
Read the relationships column rather than the object names. A platform where a control cannot satisfy two frameworks, or where a finding does not touch the risk register, is storing the same nine objects without any of the connections that make them useful.
What this replaces
Most organisations arrive with some combination of these, and the cost is not the tools — it is the reconciliation between them.
| Today | The problem it creates | In one model |
|---|---|---|
| A tab per framework | The same control appears four times with four statuses that drift apart | One control, mapped to every requirement it satisfies |
| A shared drive of evidence | No review, no expiry, no link to what it supports | Requested, reviewed, linked, and renewed on a validity period |
| A separate risk register | Residual scores with nothing behind them, unchanged by audit findings | Risks linked to the controls that treat them, updated when testing fails |
| An audit tool | Fieldwork begins with a fresh document request to teams who just submitted the same files | Audits draw on evidence already collected and approved |
| A privacy spreadsheet | Two programmes evidencing the same access control separately | Privacy records sharing the controls that protect them |
| Board reporting by hand | Rebuilt each quarter, stale before the meeting | Drawn from live records at the moment it is opened |
Six use cases, one set of records
Each of these has its own workflow and its own reporting. None of them keeps its own copy of the data.
Frameworks available
Each framework keeps its own structure and its own scoring method, while drawing on the same controls and evidence underneath.
The national baseline for government entities, affiliates, and critical national infrastructure. Scored on implementation status.
For Member Organizations supervised by the Saudi Central Bank. Scored on a six-level maturity model with level 3 as the floor.
For licensed and registered providers in the ICT, telecom, postal and space sectors. Tiered compliance levels CL1 to CL3.
Personal data obligations run as records and workflows rather than as a control checklist alone.
Clauses 4–10 and 93 Annex A controls, with a Statement of Applicability that stays current rather than becoming a historical document.
Internal standards, group policies, and contractual requirements defined as their own control set and mapped alongside the rest.
Built for more than one organisation
A ministry overseeing affiliates, a regulator supervising licensees, or a group carrying subsidiary compliance all need the same thing: visibility across entities without collapsing the separation between them.
Its own users, controls, risks, evidence, and audit records. Entities do not see one another.
Posture, progress, risk, and open actions across the entities within a remit, with the ability to drill into any one of them.
Visibility does not transfer responsibility. Each entity remains accountable for its own implementation and remediation.
The same control library and the same status definitions, so aggregation is meaningful rather than approximate.
How implementation actually goes
The mapping is the work. Everything else follows from it, and the organisations that rush this step spend the saved time twice over later.
- 01/07Confirm scope and applicable frameworks
Which entities, which systems, which frameworks, and at what level. Scoping errors here propagate 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 and mapping frameworks onto it — not the reverse.
- 03/07Map requirements to controls
Once. This is the step that removes the duplication, and the only part of the work that compounds.
- 04/07Assign ownership
Every applicable control gets a named person and a target date. Where no owner can be found, that is itself the first finding.
- 05/07Migrate evidence that is still valid
Not everything in the existing folder is worth moving. Anything past its useful life should be recollected rather than imported.
- 06/07Shift collection to the operating rhythm
Evidence produced as operations run rather than assembled before a deadline. This takes a cycle or two to establish and is where the durable saving comes from.
- 07/07Move reporting off spreadsheets last
Only once enough is in the model for the roll-up to be meaningful. Switching too early produces a partial view that undermines confidence in the whole programme.
Platform — FAQs
A governance, risk and compliance platform built for the Saudi regulatory environment. It holds frameworks, requirements, controls, evidence, risks, audits, vendors, assets and privacy records as connected objects rather than separate lists, so one implemented control can satisfy requirements across several frameworks at the same time.
The NCA ECC-2:2024, SAMA CSF, CST CRF, Saudi PDPL, and ISO 27001:2022, along with custom frameworks you define yourself for internal standards, group policies, or contractual requirements. Each keeps its own structure and scoring method while drawing on the same underlying controls and evidence.
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 who can be notified, no justification attached to an exclusion, no evidence that expires, and no way to see which existing controls already satisfy a newly added framework. Those relationships are the product.
Yes, and this is where most of the effort 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.
Yes. Each entity operates in its own isolated workspace with its own users, controls, risks, evidence, and audit records, while a parent organisation, regulator, or group holds a consolidated view above them. Visibility does not transfer accountability — each entity remains responsible for its own programme.
It depends far more on the number of frameworks in scope, the number of entities, and the state of existing documentation than on the platform. The mapping step — connecting requirements to your existing controls — is the substantive work, and organisations that rush it usually spend the saved time again later.
Yes, though not all of it is worth bringing. Evidence past its useful life should be recollected rather than imported, because migrating a stale artefact simply moves the problem. The migration is a good moment to establish validity periods for each evidence type.
Govrly runs on Google Cloud Platform with Cloudflare edge protection and multi-tenant isolation. Organisations with specific data residency or sovereignty requirements should discuss those with us directly rather than rely on a general statement.
Saudi government entities and their affiliates, regulators and supervisory authorities, SAMA-supervised financial institutions, CST-licensed providers, and multi-entity groups — along with any organisation carrying more than one framework and finding that the overlap between them is being paid for repeatedly.
No. Govrly governs the compliance programme — what applies, who owns it, whether it operates, and what proves it. It does not replace the security controls themselves, the systems that implement them, or the tools that monitor them.
See the connections, not the feature list
The best way to judge a connected model is to watch one control change and see what moves with it.
