Skip to main content
Regulator guide · Saudi Arabia

SAMA Cybersecurity Framework: the evidence an outside view produces

The Saudi Central Bank’s Cyber Security Framework sets control considerations for asset discovery, vulnerability management, threat intelligence, brand protection and third parties. Part of the evidence for each is visible from the internet. This page quotes six subdomains and shows the dated record ShadowMap produces for each one.

The text

Four domains, and six subdomains that face outward

The Framework is structured around four domains: Cyber Security Leadership and Governance, Cyber Security Risk Management and Compliance, Cyber Security Operations and Technology, and Third Party Cyber Security. For each subdomain it states a principle, an objective and control considerations. Section 1.4 applies it to the banks, insurance and reinsurance companies, financing companies and credit bureaus operating in Saudi Arabia, and to the financial market infrastructure.

Most of the Framework concerns governance, people and internal systems. Six subdomains concern things an attacker, a customer or a supervisor can see without being let in, and those are the six below. The quotations come from the Cyber Security Framework in the SAMA Rulebook, read on 18 November 2026.

Subdomain by subdomain

What SAMA’s text says, and the record that answers it

In the Framework’s own order. Each entry names the capability that produces the record and the part of the subdomain that stays with the institution.

3.2 Cyber Security Risk Management and Compliance

3.2.4

Cyber Security Review

Continuous Automated Red-Teaming

Control consideration 2

Customer and internet facing services should be subject to annual review and penetration tests.

The list of customer and internet facing services as it stands today, built from your apex domains and rebuilt every 24 hours, so the annual review starts from a current scope. Between two tests, Continuous Automated Red-Teaming validates external findings where it is safe and authorised, and every finding states whether it was tested.

Stays with you: The annual review and the penetration test are separate engagements carried out by people.

3.3 Cyber Security Operations and Technology

3.3.3

Asset Management

Attack Surface Management

Control consideration 3.e

the discovery of new information assets.

Discovery of the internet-facing estate from a single apex domain, with no seed list, compared run against run. A host, service or certificate that was not there yesterday is recorded on the day it appears, and the differences from your asset register are dated.

Stays with you: The unified register, and the ownership and classification of each asset in it.

3.3.13

Electronic Banking Services

Brand Protection

Control considerations 4.a and 4.b.2

use of brand protection measures to protect online services including social media … use of detection measures and take-down of malicious apps and websites (applicable for online and mobile banking)

Cloned banking pages, republished mobile applications and social profiles using your name, matched against your real sites, marks and copy. Each confirmed case carries its evidence pack, and the removal is filed with the registrar, host, store or platform on your authorisation. The case history is the record of the measure operating.

Stays with you: The electronic banking standard itself. Section 1.4 lists this subdomain among the exceptions for institutions other than banks.

3.3.16

Threat Management

Threat Intelligence

Control consideration 3.b

the use of reliable and relevant external sources, such as SAMA, government agencies, security forums, (security) vendors, security organizations and specialist notification services

An external source that is specific to you: actor, malware, vulnerability and indicator data correlated against the technology discovered on your estate, and credentials attributed to your domains in stealer-log and breach material, each reported as Confirmed Working, Maybe Working, Not Working or Not Tested.

Stays with you: The threat intelligence management process, its internal sources, and what is shared with SAMA.

3.3.17

Vulnerability Management

Attack Surface Management

Control considerations 3.b and 3.d

frequency of performing the vulnerability scan (risk-based) … defined timelines to mitigate (per classification)

Continuous assessment of the external estate. Each finding is dated when it is first seen, assigned to an owner and carried to a disposition, so the time each one took to close can be read against the timeline you defined for its class.

Stays with you: Scanning of internal systems, patch deployment, and the timelines themselves.

3.4 Third Party Cyber Security

3.4.1

Contract and Vendor Management

Third-Party Risk Management

Objective

the compliance with the cyber security requirements is being monitored and evaluated during the contract life-cycle.

A dated outside-in read of each third party you nominate, produced with the methodology applied to your own estate and repeated for the life of the contract. It needs nothing from the third party, so it is there between two questionnaires.

Stays with you: The contract clauses, due diligence and the right to audit. A third party’s systems are observed from the internet and are not tested.

Maturity levels

Levels 3 and 4 are about proof over time

Section 2.4 says institutions should at least operate at maturity level 3 or higher, and section 2.3 has SAMA review and audit each self-assessment. Both levels ask for something a single report cannot show.

Section 2.4.1

Maturity level 3

To achieve level 3 maturity, a Member Organization should define, approve and implement cyber security controls. In addition, it should monitor compliance with the cyber security documentation.

A control that runs every day leaves a trail: the run dates, the scope each run covered, the findings and who closed them. That trail shows the external controls were implemented and operating across the period, in place of a statement that they were.

Section 2.4.2

Maturity level 4

To achieve maturity level 4, the Member Organization should periodically measure and evaluate the effectiveness of implemented cyber security controls. In order to measure and evaluate whether the cyber security controls are effective, key risk indicators (KRIs) should be defined.

Every finding carries the date it was first seen and the date it reached a disposition. Those dates are the raw material for the indicators you define for the external estate, such as how long an exposed service stays open, and for the trend reporting the Framework describes.

Questions on the SAMA framework and external monitoring

Which SAMA Cybersecurity Framework subdomains does external monitoring produce evidence for?

Six, in three of the four domains: 3.2.4 Cyber Security Review, 3.3.3 Asset Management, 3.3.13 Electronic Banking Services, 3.3.16 Threat Management, 3.3.17 Vulnerability Management and 3.4.1 Contract and Vendor Management. In each, part of the evidence is visible from the internet, and that part is what ShadowMap records.

Does ShadowMap replace the annual penetration test in subdomain 3.2.4?

No. Subdomain 3.2.4 says customer and internet facing services should be subject to annual review and penetration tests, and a penetration test is an exercise carried out by people. Continuous Automated Red-Teaming validates external findings between those tests. Security Brigade, the company behind ShadowMap, carries out penetration tests as a separate engagement.

How does a monitoring record help with the maturity levels?

Section 2.4 says institutions should operate at maturity level 3 or higher. Level 3 turns on controls being implemented and compliance being monitored, and level 4 on effectiveness being measured with key risk indicators. A dated record that runs every 24 hours shows a control operating over time and supplies the dates an indicator is calculated from.

Do you test the third parties we nominate?

No. A third party’s estate is observed from the public internet and nothing on it is probed, because authorisation to test another company’s systems is not yours to give. Findings arrive as dated observations for the third party to confirm and fix.

Which text of the Framework does this page quote?

The Cyber Security Framework as published in the SAMA Rulebook, issued under Circular No. 381000091275 dated 24 May 2017 and shown there as in force, read on 18 November 2026. Check the Rulebook for the current text before relying on any quotation.

Other regimes: NCA ECC, MAS TRM Guidelines, DORA.

See the six records for your own estate

A 30-minute demo walks through the record behind each subdomain above. Or send one apex domain and receive a written exposure snapshot in two business days.