Operational GRC for audit-ready organizations in Saudi ArabiaBook a Demo
PlatformSaudi Arabia

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.

PlatformGovrly

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.

§ 01Govrly
Platform

What is Govrly?

From the compliance programmes we build and run in Saudi Arabia: 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.

One model, not five silos
Connected
Implement once, satisfy many
Multi-framework
Oversight with isolation
Multi-entity
Built around NCA, SAMA, CST, PDPL
Saudi-first
§ 02Govrly
Platform

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.

Reference
Framework

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

Reference
Requirement

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

Yours
Control

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

Yours
Measure

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

Operations
Evidence

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

Yours
Risk

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

Assurance
Audit and finding

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

Context
Vendor and asset

Suppliers and systems, with the data they touch and the controls their access affects.

Linked to controls, data categories and risks

Personal data
Privacy record

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.

§ 03Govrly
Platform

What this replaces

Most organisations we work with arrive with some combination of these, and the cost is not the tools — it is the reconciliation between them.

TodayThe problem it createsIn one model
A tab per frameworkThe same control appears four times with four statuses that drift apartOne control, mapped to every requirement it satisfies
A shared drive of evidenceNo review, no expiry, no link to what it supportsRequested, reviewed, linked, and renewed on a validity period
A separate risk registerResidual scores with nothing behind them, unchanged by audit findingsRisks linked to the controls that treat them, updated when testing fails
An audit toolFieldwork begins with a fresh document request to teams who just submitted the same filesAudits draw on evidence already collected and approved
A privacy spreadsheetTwo programmes evidencing the same access control separatelyPrivacy records sharing the controls that protect them
Board reporting by handRebuilt each quarter, stale before the meetingDrawn from live records at the moment it is opened
§ 05Govrly
Platform

Frameworks available

Each framework keeps its own structure and its own scoring method, while drawing on the same controls and evidence underneath.

Mandatory · NCA
NCA ECC-2:2024

The national baseline for government entities, affiliates, and critical national infrastructure. Scored on implementation status.

Mandatory · SAMA
SAMA CSF

For Member Organizations supervised by the Saudi Central Bank. Scored on a six-level maturity model with level 3 as the floor.

Mandatory · CST
CST CRF

For licensed and registered providers in the ICT, telecom, postal and space sectors. Tiered compliance levels CL1 to CL3.

Law · SDAIA
Saudi PDPL

Personal data obligations run as records and workflows rather than as a control checklist alone.

Voluntary
ISO 27001:2022

Clauses 4–10 and 93 Annex A controls, with a Statement of Applicability that stays current rather than becoming a historical document.

Yours
Custom frameworks

Internal standards, group policies, and contractual requirements defined as their own control set and mapped alongside the rest.

§ 06Govrly
Platform

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.

Isolation
Each entity keeps its own workspace

Its own users, controls, risks, evidence, and audit records. Entities do not see one another.

Oversight
Consolidated view above them

Posture, progress, risk, and open actions across the entities within a remit, with the ability to drill into any one of them.

Accountability
Ownership stays at the entity

Visibility does not transfer responsibility. Each entity remains accountable for its own implementation and remediation.

Comparability
One scale across entities

The same control library and the same status definitions, so aggregation is meaningful rather than approximate.

§ 07Govrly
Platform

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.

  1. 01
    /07
    Confirm scope and applicable frameworks

    Which entities, which systems, which frameworks, and at what level. Scoping errors here propagate into every control decision that follows.

  2. 02
    /07
    Build 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.

  3. 03
    /07
    Map requirements to controls

    Once. This is the step that removes the duplication, and the only part of the work that compounds.

  4. 04
    /07
    Assign ownership

    Every applicable control gets a named person and a target date. Where no owner can be found, that is itself the first finding.

  5. 05
    /07
    Migrate evidence that is still valid

    Not everything in the existing folder is worth moving. Anything past its useful life is best recollected rather than imported.

  6. 06
    /07
    Shift 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.

  7. 07
    /07
    Move 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.

§ 08Govrly
Platform

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 is best 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.

§ PlatformNCA · SAMA · CST · PDPL

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.

Govrly's risk register: inherent and residual risk heat maps, scored by likelihood and impact№ 04B&W
Risks · inherent → residualPlate IV