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

ISO 27001 certification, without duplicating your Saudi framework work

Build the Statement of Applicability, the risk assessment, the controls, and the evidence once in Govrly — then reuse that same work across the NCA ECC, SAMA CSF, CST controls, and Saudi PDPL, instead of running an ISO program alongside them.

Annex A controls
93
Control themes
4
Mandatory clauses (4–10)
7
New controls in 2022
11
Frameworks · ISO 27001Govrly

This page reflects how we see these requirements applied in practice. It is not an official reference. The authoritative source is the current document published by ISO, which may be revised — confirm what applies to your organisation against it and with your own advisers.

§ 01Govrly
Frameworks · ISO 27001

What is ISO 27001?

From the compliance programmes we build and run in Saudi Arabia: ISO 27001 is the international standard for information security management systems. The current edition, ISO/IEC 27001:2022, sets out mandatory requirements in clauses 4 to 10 and lists 93 controls in Annex A across four themes — Organizational, People, Physical, and Technological. Unlike Saudi regulatory frameworks, it is voluntary and independently certifiable by an accredited body.

The distinction between clauses and controls matters more than it first appears. Clauses 4 to 10 are the requirements — scope, leadership, planning, support, operation, performance evaluation, and improvement. They are not optional and cannot be excluded. Annex A controls are the safeguards you select to treat identified risks; each one is either applied or excluded with documented justification in the Statement of Applicability.

Amendment 1:2024, published in February 2024, added a requirement to consider whether climate change is a relevant issue for the ISMS. It is a small change in wording and a mandatory one in effect — an auditor will look for evidence that the question was asked and answered.

§ 02Govrly
Frameworks · ISO 27001

The 2013 edition is no longer valid

If your organisation still holds an ISO 27001:2013 certificate, it has lapsed. This is the single most common misconception we encounter with clients.

There is also no separate 2026 edition of the standard, despite the phrase circulating. The current standard is ISO/IEC 27001:2022 together with Amendment 1:2024. Anyone offering to certify you against a newer edition is describing something that does not exist.

Govrly
The transition deadline was 31 October 2025.

Certificates issued against ISO 27001:2013 that were not transitioned by that date expired and are no longer recognised by accredited certification bodies. Organisations in that position are treated as new certifications against the 2022 edition rather than transitions, which means the full audit cycle rather than a transition audit.

§ 03Govrly
Frameworks · ISO 27001

The four Annex A themes

The 2022 edition reorganised 114 controls across 14 domains into 93 controls across four themes — by merging overlapping controls, not by weakening requirements.

A.5
Organizational 37

Policies, roles, supplier relationships, threat intelligence, cloud services, incident management, and continuity. The largest theme, and where most of the 2022 additions landed.

A.6
People 8

Screening, terms of employment, awareness and training, disciplinary process, and responsibilities after employment ends.

A.7
Physical 14

Secure areas, equipment protection, clear desk and screen, physical security monitoring, and secure disposal of media.

A.8
Technological 34

Access control, cryptography, secure development, configuration management, data masking, data leakage prevention, logging, monitoring, and web filtering.

§ 04Govrly
Frameworks · ISO 27001

The 11 controls introduced in 2022

If your ISMS was built against the 2013 edition, this is where most of the gap analysis effort sits. Each one must be assessed for applicability and either implemented or excluded with justification in the SoA.

ControlNameWhy it was added
A.5.7Threat intelligenceCollecting and analysing threat information to inform defensive decisions rather than reacting after the fact.
A.5.23Information security for cloud servicesCloud adoption outpaced the 2013 control set entirely. Covers acquisition, use, management, and exit.
A.5.30ICT readiness for business continuityContinuity planning specifically for ICT capability, tested rather than documented alone.
A.7.4Physical security monitoringActive monitoring of premises for unauthorised access, not just controlled entry.
A.8.9Configuration managementSecure baselines defined, applied, and monitored across hardware, software, and services.
A.8.10Information deletionDeleting data when it is no longer required — closely aligned to PDPL retention obligations.
A.8.11Data maskingLimiting exposure of sensitive data in non-production and analytical contexts.
A.8.12Data leakage preventionDetecting and preventing unauthorised extraction of information across systems and endpoints.
A.8.16Monitoring activitiesMonitoring networks and applications for anomalous behaviour, with defined response.
A.8.23Web filteringManaging access to external websites to reduce exposure to malicious content.
A.8.28Secure codingSecure development practices applied throughout the software lifecycle.

Running ISO 27001 in Govrly

SoA screenshot
SoA
The Statement of Applicability stops being a document someone updates before the audit.Hover or scroll to inspect
A.
SoALive, not historicalAll 93 Annex A controls with applicability, justification for every inclusion and exclusion, implementation status and the evidence behind each — updated as the organisation changes.
B.
Clauses4 to 10, trackedScope, leadership, internal audit and management review held as records with dates and owners, rather than as activities someone remembers doing before a surveillance audit.
C.
RiskTraceable to controlsEach risk connected to the Annex A controls treating it, which is the traceability an auditor follows and the link most commonly missing.
D.
ReuseSaudi frameworks count hereControls implemented for the ECC, CSF or CRF carry into Annex A entries from the same record. For organisations already carrying Saudi obligations, most of the ISO work is already done.
E.
FindingsNonconformities to verified closureRoot cause, corrective action, owner and verification — closing only when verification completes, which is what the surveillance audit examines.
F.
AmendmentClimate, answeredAmendment 1:2024 expects the climate question to have been asked and answered. It is a small record, and its absence is an easy finding to avoid.
§ 06Govrly
Frameworks · ISO 27001

Why ISO 27001 is worth holding in Saudi Arabia

It is the only voluntary framework in this set — which is exactly what makes it commercially useful rather than merely required.

Commercial
It is independently certifiable

The NCA ECC, SAMA CSF, and CST CRF are assessed against, not certified. ISO 27001 produces a certificate from an accredited body — something a buyer, partner, or tender panel can verify without taking your word for it.

Procurement
It answers the question tenders ask

International clients and many Saudi tenders ask for ISO 27001 by name. It is the recognised shorthand for a managed security program, and its absence is noticed.

Efficiency
It accelerates every other framework

Organisations with a mature ISMS reach ECC or CSF readiness faster, because the evidence, the risk process, and the control ownership already exist in a reusable form.

Structure
It gives you a management system, not a checklist

Clauses 4–10 require scope, leadership, risk process, internal audit, and management review. That machinery is what sustains compliance between assessment cycles for every other framework you hold.

Alignment
It maps cleanly to Saudi regulation

The CST CRF explicitly aligns with ISO 27001. The ECC and CSF overlap substantially at control level. The mapping work is real and it runs in both directions.

Trust
It supports your own trust story

A current certificate, with the SoA and evidence behind it, shortens the security review your customers put you through before signing.

§ 07Govrly
Frameworks · ISO 27001

Where ISO 27001 programs come apart

Certification is rarely lost at the first audit. It is lost in the two years between them.

  1. 01
    /06
    The SoA becomes a historical document

    Written for the certification audit, then never updated as controls, systems, and exclusions change. At the surveillance audit it describes an organisation that no longer exists.

  2. 02
    /06
    Exclusions have no recorded justification

    A control marked not applicable without documented reasoning is a finding. Auditors ask why far more often than they ask whether.

  3. 03
    /06
    The risk assessment and the controls drift apart

    Annex A controls exist to treat identified risks. When the risk register and the control set are maintained separately, the link the auditor traces is missing.

  4. 04
    /06
    Internal audit and management review get skipped

    Clauses 9.2 and 9.3 are mandatory. They are also the easiest things to defer in a quiet year, and their absence is immediately visible.

  5. 05
    /06
    Evidence is collected for the audit, not from operations

    Assembled in the weeks beforehand rather than produced continuously — which is precisely what "operating effectively over time" is meant to demonstrate.

  6. 06
    /06
    ISO runs as a parallel program to the Saudi frameworks

    Two control sets, two evidence libraries, two sets of findings, and a reconciliation exercise nobody owns. This is the most expensive mistake on the list.

§ 08Govrly
Frameworks · ISO 27001

How Govrly runs ISO 27001

The ISMS lives in the same system as your Saudi frameworks, so one control, one owner, and one piece of evidence serve all of them.

SoA
A living Statement of Applicability

All 93 controls with applicability, justification for every inclusion and exclusion, implementation status, and the evidence behind each — updated as the organisation changes, not before the audit.

Risk
Risk assessment linked to controls

Inherent and residual scoring, with each risk connected to the Annex A controls that treat it — so the traceability an auditor looks for is already there.

Clauses
Clauses 4–10 tracked, not assumed

Scope, leadership, internal audit, and management review held as records with dates and owners, rather than as activities someone remembers doing.

Evidence
Continuous collection and review

Requested from a named owner with a due date, reviewed before it counts, and linked to every requirement it satisfies across ISO, ECC, CSF, CRF, and PDPL.

Findings
Nonconformities to verified closure

Root cause, corrective action, owner, due date, and verification — closing only when verification completes, which is what the surveillance audit examines.

Reuse
One control, many frameworks

Implement access control once and satisfy A.5.15, the ECC requirement, the CSF subdomain, and the CRF control from the same record with the same evidence.

§ 09Govrly
Frameworks · ISO 27001

ISO 27001 vs Saudi regulatory frameworks

Understanding what ISO 27001 does and does not replace is the difference between reusing work and duplicating it.

Holding ISO 27001 does not discharge a Saudi regulatory obligation, and no certification body can certify you against the NCA ECC, SAMA CSF, or CST CRF. What the overlap buys you is reusable evidence and a shorter path — not an exemption.

FeatureISO 27001:2022Saudi frameworks (ECC / CSF / CRF)
StatusVoluntaryMandatory for in-scope entities
Issued byISO and IECNCA, SAMA, and CST respectively
OutcomeCertificate from an accredited bodyRegulatory assessment or self-assessment
StructureClauses 4–10 plus 93 Annex A controlsDomain and control hierarchies specific to each
ExclusionsPermitted with documented justificationApplicability set by the regulator
Does it satisfy the other?No — but it accelerates it substantiallyNo — regulatory obligation stands independently
Managed in GovrlyYesYes
§ 10Govrly
Frameworks · ISO 27001

A practical path to ISO 27001 certification

Most organisations we work with reach certification in six to twelve months. Those already running a Saudi framework programme move faster, because the risk process and much of the evidence already exist.

  1. 01
    /08
    Define the ISMS scope

    Which parts of the organisation, which locations, which systems and services. Scope decisions made loosely here create audit problems later.

  2. 02
    /08
    Secure leadership commitment

    Clause 5 is not ceremonial. The auditor will look for evidence of genuine management involvement, resourcing, and a defined policy.

  3. 03
    /08
    Run the risk assessment

    Identify risks to confidentiality, integrity, and availability within scope, and establish the criteria and method you will apply consistently.

  4. 04
    /08
    Build the Statement of Applicability

    Assess all 93 controls for applicability. Every inclusion links to a risk; every exclusion carries a documented justification.

  5. 05
    /08
    Map what your Saudi frameworks already cover

    If you hold ECC, CSF, or CRF obligations, identify the overlap before implementing anything new. This is usually the largest saving available.

  6. 06
    /08
    Implement, and evidence as you go

    Controls in place, owners named, and evidence produced by operations rather than assembled retrospectively.

  7. 07
    /08
    Internal audit and management review

    Both mandatory under clauses 9.2 and 9.3, and both required before certification. Treat findings honestly — a clean internal audit that misses what the external auditor finds helps nobody.

  8. 08
    /08
    Stage 1 and Stage 2 audit

    Stage 1 reviews documentation and readiness; Stage 2 tests whether the ISMS actually operates. Then surveillance audits annually and recertification every three years.

Govrly
What this looks like in Govrly

The Statement of Applicability stays current because it draws on live control records rather than a document someone updates before the audit — and each Annex A control is the same record carrying your NCA ECC or SAMA CSF requirement.

See it in a demo →

§ 11Govrly
Frameworks · ISO 27001

ISO 27001 FAQs

ISO 27001 is the international standard for information security management systems. The current edition, ISO/IEC 27001:2022, sets out mandatory requirements in clauses 4 to 10 and lists 93 controls in Annex A across four themes — Organizational, People, Physical, and Technological. It is voluntary and independently certifiable by an accredited certification body.

ISO 27001:2022 has 93 Annex A controls in four themes: Organizational (37), People (8), Physical (14), and Technological (34). The 2013 edition had 114 controls across 14 domains; the reduction came from merging overlapping controls, not from removing requirements, and 11 entirely new controls were added.

No. The transition deadline was 31 October 2025. Certificates issued against the 2013 edition that were not transitioned by that date have expired and are no longer recognised by accredited certification bodies. Organisations in that position must certify against the 2022 edition through the full audit cycle rather than a transition audit.

No. The current standard is ISO/IEC 27001:2022 together with Amendment 1:2024, which added a requirement to consider whether climate change is a relevant issue for the ISMS. There is no separate 2026 edition.

Clauses 4 to 10 define the mandatory requirements for establishing, operating, and improving the information security management system — they cannot be excluded. Annex A controls are the specific safeguards selected to treat identified risks; each is either applied or excluded with documented justification recorded in the Statement of Applicability.

The Statement of Applicability is the document recording, for all 93 Annex A controls, whether each applies, why, its implementation status, and the justification for any exclusion. It is the document auditors examine most closely, and the one most often found out of date at surveillance audits.

Typically six to twelve months from starting the ISMS to certification, depending on organisational size, scope, and existing maturity. Organisations already operating a Saudi regulatory framework programme generally move faster, because the risk process, control ownership, and much of the evidence already exist in a reusable form.

No. ISO 27001 is a voluntary international standard and does not discharge a Saudi regulatory obligation. The frameworks overlap substantially at control level, so evidence and implementation work can be reused across them, but each regulatory requirement stands independently and is assessed by its own authority.

Threat intelligence, information security for cloud services, ICT readiness for business continuity, physical security monitoring, configuration management, information deletion, data masking, data leakage prevention, monitoring activities, web filtering, and secure coding. Each must be assessed for applicability and either implemented or excluded with justification.

Yes. Controls, measures, and evidence are shared objects in Govrly, so one implementation effort and one piece of approved evidence can support the Annex A control, the NCA ECC requirement, the SAMA CSF subdomain, the CST CRF control, and the corresponding PDPL safeguard at the same time — while each framework keeps its own scoping, scoring method, and reporting.

§ Frameworks · ISO 27001NCA · SAMA · CST · PDPL

Build the ISMS once, certify against it, reuse it everywhere

Statement of Applicability, risk assessment, controls, and evidence — connected to every Saudi framework you already carry.

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