Operational GRC for audit-ready organizations in Saudi ArabiaBook a Demo
Frameworks · CustomSaudi Arabia

The framework you actually need is not in the library

Every GRC platform ships a framework library, and every library stops somewhere. In Saudi Arabia it stops sooner than elsewhere — because the specialised control documents, national data standards, sector rules and buyer requirements that apply here were not written for a product built for a US market.

Frameworks · CustomGovrly

This page describes how we approach frameworks that are not in a standard library, based on implementation work. Where it refers to published requirements — national standards, sector rules, or a buyer's control set — the authoritative source is the document issued by the body that published it. Confirm what applies to your organisation against it.

§ 01Govrly
Frameworks · Custom

What is a custom framework?

From the compliance programmes we build and run in Saudi Arabia: a custom framework is a requirement set you define yourself — with its own structure, its own numbering and its own scoring — and then map onto the controls you already operate. It behaves like any other framework in the platform, except that you wrote it.

The distinction that matters is between the requirement and the control. A framework — any framework — is a list of requirements expressed in someone else's language. Your controls are what your organisation actually does. Mapping the two is what lets one implemented control satisfy the NCA ECC, a group policy and a customer's contractual annex at the same time.

A custom framework is simply a requirement set whose author happens to be you, your parent company, your regulator, or your largest customer — rather than ISO or the NCA.

Domains and requirements you define
Your structure
Assessed the way it is assessed
Your scoring
Mapped to what you already run
Shared controls
Its own view, its own audience
Reported separately
§ 02Govrly
Frameworks · Custom

What is missing from every standard library

These are real, they are imposed, and a platform built for a US or European market does not ship them.

The pattern is consistent. A platform that can only manage the frameworks it ships handles perhaps half of what a Saudi organisation actually answers to. The other half ends up in spreadsheets, which is exactly the situation the platform was bought to end.

NCA
The specialised control documents

Beyond the ECC, the NCA issues further control sets covering areas such as critical systems, cloud computing, data, and telework. They add to the baseline rather than replacing it, and organisations in scope carry both.

NDMO
National data management standards

Data governance, classification and management standards directed at government data. Distinct from the ECC in subject and in the office that issues them.

DGA
Digital government policy

Policy and requirements for digital services in the public sector, which interact with both security and privacy obligations rather than sitting beside them.

Sector
Regulator-specific requirements

Health, capital markets, energy and other sectors carry rules issued by their own authorities. They rarely appear in a generic library because they are specific to one country and one industry.

Buyers
Large-customer control sets

Major Saudi buyers issue supplier security requirements that read like a framework and are enforced like one. If you supply them, you carry that requirement set whether or not anyone calls it a framework.

Group
Parent company standards

A multinational's internal standard, imposed on a Saudi subsidiary, sits above the local obligations rather than replacing them — and is usually assessed on a different schedule by a different team.

§ 03Govrly
Frameworks · Custom

What you define

A framework is four things. Get these right and it behaves like any other framework in the platform.

Yours
Structure

Domains, subdomains, or whatever hierarchy the source document uses. Mirror the published structure rather than improving it — the people assessing you will read it in the original order, and a reorganised version costs you the ability to answer them directly.

Verbatim
Requirements

Each requirement in the source document's own wording and its own numbering. Resist paraphrasing. When an assessor asks about clause 4.2.7, you want to be looking at clause 4.2.7 rather than at your interpretation of it.

Theirs
Scoring

Implementation status, maturity levels, compliance tiers, or a scheme unique to that document. The framework should be assessed the way its author assesses it, not converted into a scheme that makes your dashboard tidier.

The work
Mapping

Each requirement linked to the controls that satisfy it — drawn from the library you already run. This is the step that turns a new requirement set from a new programme into an additional view of work you have already done.

The fourth is where the value is. The first three are transcription; the mapping is what makes a custom framework cheaper than the standard one it sits beside.

§ 04Govrly
Frameworks · Custom

When to build one, and when not to

The failure mode is a custom framework that duplicates a standard one, after which nobody can reconcile the two. It is worth being clear about the line.

The test we use: who assesses you against this, and on what schedule? If there is a name and a date, it is a framework. If there is neither, it is something else — and modelling it as a framework will cost you more than it saves.

01
Build one when
  • Someone external imposes it
    A regulator, a parent company, or a customer contract — a requirement set you are assessed against by someone else.
  • It has its own structure and scoring
    If it is assessed on its own terms and reported to its own audience, it is a framework whatever it is called.
  • It is not in the library and will not be
    Country-specific and sector-specific requirement sets rarely arrive in a generic product.
  • You need to report on it separately
    A distinct audience asking a distinct question needs a distinct view.
02
Do not build one when
  • A standard framework already covers it
    Rebuilding ISO 27001 as a custom framework because you dislike the numbering creates two versions of the same thing that will disagree.
  • It is really a control library
    If it describes what you do rather than what someone requires of you, those are controls. Adding them as a framework inverts the model.
  • It is a checklist for one project
    A one-off list with no ongoing assessment is a task list. Treating it as a framework creates a permanent object for a temporary need.
  • Nobody will assess you against it
    If no external party ever asks, an internal policy is better held as policy with controls beneath it.
§ 05Govrly
Frameworks · Custom

Custom frameworks in Govrly

A custom framework is a first-class object, not a workaround. It sits on the same control library as the standard ones.

Shared controls
One control, several authors

An access control implemented once can satisfy an ECC requirement, a group policy clause and a customer's contractual annex simultaneously — from the same record, with each framework scoring it in its own terms.

Shared evidence
Collected once

The artefact proving that control operates supports every requirement mapped to it. A custom framework does not trigger a second evidence request to the same owner for the same thing.

Independent scoring
Assessed on its own terms

Its own status scheme, its own applicability decisions, its own exclusions with justification — because the body that issued it will assess it their way, not yours.

Separate reporting
Its own view

Coverage and progress reported against the custom framework alone, for the audience that asked for it — without their view being contaminated by frameworks that do not concern them.

Ownership
Named, as everywhere else

Each applicable requirement carries an owner and a target date. Custom does not mean informal — a requirement someone imposed on you needs an owner as much as a regulatory one does.

Reuse
The overlap is visible

Because the mapping runs through shared controls, you can see how much of a new requirement set you already satisfy before committing to a programme — which is usually more than expected.

§ 06Govrly
Frameworks · Custom

Who builds custom frameworks

Note the third column. A framework without an assessor is a document; a framework with one is a programme. That column is the reason the object exists.

WhoWhat they defineWho assesses it
Government entitiesSpecialised control documents and national data standards alongside the ECCThe issuing authority
RegulatorsThe control set they impose on their own licenseesThemselves, across the entities they supervise
Multi-entity groupsA group standard applied consistently across subsidiariesGroup internal audit
SuppliersA major customer's security requirements as a tracked requirement setThe customer, during vendor review
ConsultanciesTheir own assessment methodology, applied consistently across clientsTheir own quality process
Any organisationInternal standards that go beyond what any regulator requiresInternal audit, and the board
§ 07Govrly
Frameworks · Custom

Building one properly

Transcription is quick. The mapping decides whether it saves you work or adds some.

  1. 01
    /08
    Confirm it is a framework

    Who assesses you against it, and when. If there is no name and no date, model it as policy and controls instead — you will save yourself an object you have to maintain forever.

  2. 02
    /08
    Take the structure from the source

    Its domains, its hierarchy, its numbering. Improving on the published structure feels productive and costs you the ability to answer an assessor in their own terms.

  3. 03
    /08
    Transcribe requirements verbatim

    Paraphrasing introduces drift you will not notice until someone quotes the original back at you.

  4. 04
    /08
    Use their scoring, not yours

    If it is assessed on maturity levels, score it on maturity levels. Converting to a scheme that suits your dashboard means your dashboard no longer answers the question you will actually be asked.

  5. 05
    /08
    Map against existing controls first

    Before writing anything new, check what your current controls already satisfy. This is where you find out whether this is a small addition or a genuine programme — and it is usually the former.

  6. 06
    /08
    Record applicability and exclusions

    Which requirements apply to your scope and why the others do not. Same discipline as a Statement of Applicability, same reason: the exclusions are what get questioned.

  7. 07
    /08
    Assign owners to the gaps

    Whatever is not already satisfied needs a person and a date, exactly as in a regulatory programme.

  8. 08
    /08
    Decide who maintains it

    Source documents get revised. A custom framework with no owner drifts out of date silently, and the first sign is usually an assessor citing a clause you do not have.

Govrly
What this looks like in Govrly

Your custom framework keeps its own structure, scoring and reporting, while its requirements map onto the control library already carrying your NCA ECC, SAMA CSF and ISO 27001 work — so one implemented control and one approved artefact answer to several authors at once.

See it in a demo →

§ 08Govrly
Frameworks · Custom

Custom frameworks — FAQs

A requirement set you define yourself, with its own structure, numbering and scoring, mapped onto the controls you already operate. It behaves like any other framework in the platform — the difference is that its author is you, your parent company, your regulator or your customer, rather than ISO or the NCA.

Because the library stops where the international standards stop. The NCA's specialised control documents, national data management standards, digital government policy, sector-specific rules and large-buyer supplier requirements are all real obligations in this market, and a product built for a US or European buyer does not ship them.

No, and that is the whole point. One implemented control can satisfy a requirement in your custom framework, an NCA ECC requirement and an ISO 27001 Annex A control at the same time, from the same record — with each framework scoring it in its own terms.

Yes, and you should. If the body that issued it assesses on maturity levels, score it on maturity levels. Converting someone else's scheme into one that suits your dashboard means your dashboard stops answering the question you will actually be asked.

When a standard framework already covers it, when it is really a control library describing what you do rather than what someone requires of you, when it is a checklist for a single project, or when no external party will ever assess you against it. The test is simple: who assesses you against this, and on what schedule? If there is no name and no date, it is not a framework.

The transcription is quick. The mapping is the work, and it is also where the saving comes from — because mapping against your existing controls usually reveals that you already satisfy more of the new requirement set than expected. Do that step before deciding how large the programme is.

You update the framework, which is why it needs a named maintainer. A custom framework with no owner drifts out of date silently, and the first sign is usually an assessor citing a clause you do not have. This is the most common failure we see, and it is entirely avoidable.

That is one of the more common uses. A supervisory body defines its control set once and applies it across the entities it supervises, each of which reports against it from its own isolated workspace while the regulator sees consolidated coverage.

Yes. A major buyer's supplier security requirements read like a framework and are enforced like one, so modelling them as one is accurate rather than a workaround. It also means the next customer asking similar questions maps onto controls you have already evidenced.

No — it organises your work against a requirement set. It does not confer approval, and no platform can. What it does is let you answer the body that imposed the requirements in their own structure and their own terms, with evidence attached, rather than assembling that answer from a spreadsheet each time they ask.

§ Frameworks · CustomNCA · SAMA · CST · PDPL

Bring the framework that is not in anyone's library

See how much of it your existing controls already satisfy before you scope it as a programme.

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