trio.so
Templates

SAMA Compliance Checklist for the SAMA CSF (PDF + Excel)

SAMA compliance checklist for the SAMA CSF: 4 domains and 32 subdomains, maturity levels 0 to 5, evidence and owners, with a free PDF and Excel tracker.

Mountain landscape representing leadership perspective and vision
Written by
Atena Ladchartabi

Content writer, trio.so

Published on
Modified on

A SAMA compliance checklist turns the Saudi Central Bank's Cyber Security Framework (SAMA CSF) into tasks you can assign, score and prove. This one covers all 4 domains and 32 subdomains of CSF v1.0, broken into 116 checks with the evidence to keep and a suggested owner for each.

It is written for CISOs, IT managers and compliance leads at banks, finance companies, payment service providers and credit bureaus regulated by SAMA. Use it for a gap assessment, to score each subdomain on SAMA's 0 to 5 maturity scale, and to prepare the evidence behind your self-assessment.

The free download has a PDF guide and an Excel tracker with a maturity score per subdomain, targets that switch to level 4 where banks need it, an evidence register, a device tab, a third-party tracker, a task calendar and a dashboard.

Preview of the SAMA CSF checklist PDF and Excel tracker
Preview of the SAMA CSF checklist PDF and Excel tracker

In short

  • The SAMA CSF v1.0 (May 2017) is still the version in force in the SAMA Rulebook. No newer version has been published.
  • It has 4 domains and 32 subdomains. Each subdomain has a principle, an objective and numbered control considerations.
  • Every institution must operate at maturity level 3 or higher. Banks must reach level 4 in 3.3.14 to 3.3.17 (event, incident, threat and vulnerability management).
  • You self-assess with SAMA's questionnaire. SAMA reviews and audits the result and makes inspection visits.
  • There is no SAMA CSF certificate. The self-assessment and SAMA's review set your compliance and maturity level.

Who the SAMA CSF Applies To

The CSF applies to the financial institutions SAMA regulates, which the framework calls Member Organizations. Today the Rulebook lists the banking sector, finance companies, payment systems and payment service providers, credit bureaus and the Regulatory Sandbox. Banks follow all 32 subdomains. Other institutions skip three of them and must align with the banking sector's cyber strategy (3.1.2) only where it applies:

  • 3.2.3 Industry standards: excluded, but if you store, process or transmit card data or use SWIFT, PCI DSS or the SWIFT Customer Security Controls Framework still applies.
  • 3.3.12 Payment Systems: excluded.
  • 3.3.13 Electronic Banking Services: excluded, but if you offer online services to customers you need multi-factor authentication.

The 2017 framework text also lists insurers and reinsurers. The Insurance Authority now supervises the insurance sector, so insurers should confirm with it which cyber rules apply to them. Capital-market firms are licensed by the Capital Market Authority, not SAMA, and are not in the CSF's scope list. Newly licensed and sandbox fintechs start with SAMA's Cyber Resilience Fundamental Requirements. Our guide to SAMA compliance covers scope, history and the related SAMA rules in more depth.

Who the SAMA CSF applies to: banks, finance companies, payment providers and credit bureaus, with notes for new entities, insurers, capital-market firms and vendors
Who the SAMA CSF applies to: banks, finance companies, payment providers and credit bureaus, with notes for new entities, insurers, capital-market firms and vendors

The SAMA CSF Checklist, Subdomain by Subdomain

Each row below is one CSF subdomain. The subdomain names and the numbers in brackets are SAMA's; the checks are our short summary, not SAMA's wording. Read the full control considerations in the SAMA Rulebook before you score yourself.

The SAMA CSF's 4 domains and 32 subdomains, with the device-related subdomains marked
The SAMA CSF's 4 domains and 32 subdomains, with the device-related subdomains marked

Domain 3.1: Cyber Security Leadership and Governance

Seven subdomains about who owns cyber security. Expect SAMA to ask for board papers, the committee charter and the CISO's appointment first.

IDSubdomainWhat to check (our words)Evidence to keep
3.1.1Cyber Security Governance
  • A cyber security committee mandated by the board and chaired by an independent senior manager from a control function (3.1.1.1, 3.1.1.2)
  • An approved committee charter that sets objectives, roles, quorum and meetings at least every quarter (3.1.1.4)
  • A cyber security function separate from IT, with its own reporting line, budget and staff evaluations (3.1.1.5, 3.1.1.6)
  • A full-time CISO at senior management level who is Saudi, qualified and appointed with SAMA's no-objection (3.1.1.8, 3.1.1.9)
  • A cyber security budget allocated by the board (3.1.1.10)
Board resolution, committee charter and minutes, org chart, CISO appointment and SAMA no-objection letter
3.1.2Cyber Security Strategy
  • Strategy defined, approved, kept current and carried out (3.1.2.1)
  • Aligned with business objectives, legal and regulatory duties and the banking sector's cyber strategy (3.1.2.2)
  • States why cyber security matters, the target state and which initiatives run when (3.1.2.3)
Approved strategy, initiative roadmap, approval records
3.1.3Cyber Security Policy
  • Policy defined, approved and communicated, and reviewed through a set process (3.1.3.1, 3.1.3.2)
  • Supported by detailed standards (for example passwords, firewalls) and procedures (3.1.3.3)
  • Covers classification, asset owners, risk assessments, awareness, breach reporting and continuity (3.1.3.4)
Policy with board endorsement and review history, list of supporting standards and procedures
3.1.4Cyber Security Roles and Responsibilities
  • Board: budget, committee charter, endorsement of governance, strategy and policy (3.1.4.1)
  • Committee: risk appetite, programs, risk process, KRIs and KPIs (3.1.4.2)
  • Senior management: cyber duties in job descriptions and standards (3.1.4.3)
  • CISO: strategy, policy, architecture, risk process, reviews and KRI/KPI reporting (3.1.4.4)
  • Internal audit runs cyber audits; all staff follow the policy (3.1.4.5, 3.1.4.6)
RACI matrix, job descriptions, KRI and KPI reports to the committee
3.1.5Cyber Security in Project Management
  • Cyber security part of the project methodology and every project phase (3.1.5.1, 3.1.5.2)
  • A risk assessment at project start, with cyber risks in the project risk register (3.1.5.2)
  • An independent cyber security review of the project (3.1.5.2)
Project methodology, project risk registers, review reports
3.1.6Cyber Security Awareness
  • An approved awareness program for staff, third parties and customers (3.1.6.1, 3.1.6.2)
  • Run through the year over several channels, tailored per audience (3.1.6.3, 3.1.6.4)
  • Covers current threats such as spear-phishing, and its effect is measured (3.1.6.5, 3.1.6.6)
  • Customer awareness lists protections customers can use (3.1.6.7)
Program plan, campaign records, effectiveness results, customer awareness material
3.1.7Cyber Security Training
  • Specialist training for key roles, cyber staff, IT builders and maintainers, and risk assessors (3.1.7.1)
  • Education to operate information assets securely (3.1.7.2)
Training matrix by role, attendance records

Domain 3.2: Cyber Security Risk Management and Compliance

Five subdomains about how you find, treat and review cyber risk, and how you keep up with regulation and industry standards.

IDSubdomainWhat to check (our words)Evidence to keep
3.2.1Cyber Security Risk Management
  • Process approved, aligned with ERM, covering identification, analysis, response and monitoring (3.2.1.1 to 3.2.1.4)
  • Triggered at project start, before critical changes, before outsourcing and for new products (3.2.1 consideration 6)
  • Existing assets reassessed on a schedule set by classification or risk profile (3.2.1 consideration 7)
  • Risk appetite and tolerance approved; accepted risks signed off by the business owner and reported to the committee
Risk register, risk treatment plans, risk acceptance sign-offs, approved risk appetite
3.2.2Regulatory Compliance
  • Regulatory cyber requirements identified and applied periodically and when new rules take effect (3.2.2.1)
  • Key areas involved; policy, standards and procedures updated as needed (3.2.2.1)
Regulatory register, change log for policies and standards
3.2.3Compliance with (Inter)national Industry Standards
Banks only
  • PCI DSS, EMV and the SWIFT Customer Security Controls Framework (3.2.3.1)
  • Other institutions: PCI DSS or SWIFT CSCF still apply if you handle card data or SWIFT (CSF 1.4)
PCI DSS Attestation of Compliance, SWIFT attestation, EMV records
3.2.4Cyber Security Review
  • Periodic reviews of critical information assets (3.2.4.1)
  • Customer and internet-facing services reviewed and penetration tested every year (3.2.4.2)
  • Results recorded, reported to the business owner and followed up (3.2.4.3 to 3.2.4.5)
Review and penetration test reports, follow-up tracker
3.2.5Cyber Security Audits
  • Independent audits under generally accepted auditing standards and the CSF (3.2.5)
  • Run from the audit manual and audit plan (3.2.5)
  • Banks: a yearly internal audit report on CSF compliance against the required maturity (circular 29814/67)
Audit plan, audit reports, management responses

Domain 3.3: Cyber Security Operations and Technology

Seventeen subdomains, the largest share of the work. Most device and endpoint items sit here: asset management, infrastructure security, cryptography, BYOD, secure disposal and vulnerability management.

IDSubdomainWhat to check (our words)Evidence to keep
3.3.1Human Resources
  • Cyber responsibilities and non-disclosure in staff agreements (3.3.1.3.a)
  • Awareness at the start of and during employment; disciplinary rules; screening (3.3.1.3.b to d)
  • Leavers: access revoked and assets returned, mobile devices included (3.3.1.3.e)
Signed agreements, screening records, leaver checklists with returned devices
3.3.2Physical Security
  • Entry controls including visitors; surveillance; protection of data centres and data rooms (3.3.2.3.a to c)
  • Environmental protection; assets protected through transport and disposal (3.3.2.3.d, e)
Access logs, visitor records, data centre controls, transport and disposal records
3.3.3Asset Management
  • Process defined, approved and measured (3.3.3.1, 3.3.3.2)
  • A unified register with owners and custodians (3.3.3.3.a, b)
  • Classification, labelling and handling of assets (3.3.3.3.d)
  • New assets discovered, not only entered by hand (3.3.3.3.e)
Asset register export, ownership list, discovery reports
3.3.4Cyber Security Architecture
  • Architecture defined, approved, implemented and monitored (3.3.4.1, 3.3.4.2)
  • Qualified architects, security-by-design principles and periodic review (3.3.4.3)
Architecture documents, design principles, review records
3.3.5Identity and Access Management
  • An approved IAM policy, monitored and measured (3.3.5.1 to 3.3.5.3)
  • Joiner, mover and leaver changes started by HR, formally approved, with an audit trail (3.3.5.4.b)
  • Periodic access reviews; access management automated and centralized (3.3.5.4.b, c, d)
  • MFA for sensitive and critical systems and for all remote access (3.3.5.4.e, f)
  • Privileged and remote users reviewed; shared admin accounts limited and their passwords changed (3.3.5.4.f)
IAM policy, access review sign-offs, MFA coverage report, privileged account list
3.3.6Application Security
  • Application security standards approved, monitored and measured (3.3.6.1 to 3.3.6.3)
  • Development follows an approved secure SDLC (3.3.6.4)
  • Standards cover secure coding, segregation of duties, data protection, patching, backup and compliance review (3.3.6.5)
Application standards, SDLC, code review records
3.3.7Change Management
  • Impact assessment, classification and review of changes (3.3.7.4.a)
  • Security testing such as penetration tests and code review where relevant (3.3.7.4.b)
  • Approval by the business owner, the cyber function and the CAB; post-implementation review (3.3.7.4.c to f)
  • Separated environments, an emergency change procedure and fall-back plans (3.3.7.4.g to i)
Change tickets with approvals and test results
3.3.8Infrastructure Security
  • Standards cover data centres, DR sites and offices (3.3.8.4)
  • And every infrastructure type, workstations, laptops, tablets and mobile devices included (3.3.8.5)
  • Standards set configuration, events to log, data-leakage prevention, access and remote maintenance (3.3.8.6.a)
  • Approved software only, secure protocols, network segmentation (3.3.8.6.d, e)
  • Malware protection with application allow-listing, patching, backup and periodic compliance review (3.3.8.6.f, g, i, j)
  • DDoS protection where relevant, with scrubbing tested at least twice a year (3.3.8.6.h)
Hardening standards per platform, configuration reports, compliance review results
3.3.9Cryptography
  • A cryptographic standard defined, approved, monitored and measured (3.3.9.1 to 3.3.9.3)
  • Approved solutions and when to use them (3.3.9.4.a, b)
  • Key lifecycle management, archiving and recovery (3.3.9.4.c)
Cryptographic standard, key management procedure, encryption status reports
3.3.10Bring Your Own Device (BYOD)
  • A BYOD standard defined, approved, monitored and measured (3.3.10.1 to 3.3.10.3)
  • User responsibilities and awareness training (3.3.10.4.a)
  • Rules and consequences for tampered devices, leavers and lost or stolen devices (3.3.10.4.b)
  • Business data kept apart from personal data, for example in a container (3.3.10.4.c)
  • Approved corporate and public apps; MDM, device access controls and encryption (3.3.10.4.d, e)
BYOD standard, signed user agreements, enrollment records, encryption and passcode reports
3.3.11Secure Disposal of Information Assets
  • A disposal standard and procedure, monitored and measured (3.3.11, considerations 1 to 3)
  • Disposal in line with legal and regulatory rules (consideration 4)
  • Data made non-retrievable, for example by secure wiping or shredding (consideration 5)
  • Disposal, transport and storage providers follow your standard (consideration 6)
Disposal records, wipe or destruction certificates, provider contracts
3.3.12Payment Systems
Banks only
  • A payment systems security standard, monitored and measured (3.3.12)
  • Follows the SARIE and mada security requirements the CSF refers to (3.3.12)
Payment systems standard, SARIE and mada compliance records
3.3.13Electronic Banking Services
Banks only
  • Brand protection and official app stores; fake apps and sites taken down (3.3.13.4.a, b)
  • MFA at registration and for sign-on, beneficiary changes, high-risk transactions and password resets (3.3.13.4.b.6)
  • Access revoked after three wrong passwords or PINs (3.3.13.4.b.6.d)
  • ATM and POS hardening; SMS notification rules (3.3.13.4.c, d)
  • SAMA approval before a new e-banking service (3.3.13.4.b.11)
  • Other institutions with online customer services: MFA (CSF 1.4)
E-banking security standard, MFA design, SMS rules, SAMA approvals
3.3.14Cyber Security Event Management
Banks: level 4
  • An event monitoring standard listing the mandatory events per asset class (3.3.14.3)
  • A designated, trained SOC team with 24x7 monitoring and a restricted work area (3.3.14.4.a to d)
  • Handling of malicious code and suspicious events; packet analysis; protected logs (3.3.14.4.e to h)
  • Periodic compliance monitoring of application and infrastructure standards (3.3.14.4.i)
  • SIEM correlation, incident reporting and independent SOC testing such as red-teaming (3.3.14.4.j to l)
Monitoring standard, SOC procedures and rota, SIEM use cases, SOC test reports
3.3.15Cyber Security Incident Management
Banks: level 4
  • A designated, trained team with forensic capacity and a CERT area (3.3.15.4.a to d)
  • Incident classification, timely handling, evidence protection, root-cause analysis and a repository (3.3.15.4.e to j)
  • Tell SAMA IT Risk Supervision at once about medium or high incidents (3.3.15.5)
  • SAMA no-objection before media contact; a formal incident report after recovery (3.3.15.6, 3.3.15.7)
Incident procedure, incident register, SAMA notifications and reports
3.3.16Threat Management
Banks: level 4
  • Process approved and measured (3.3.16.1, 3.3.16.2)
  • Internal sources such as logs, SIEM and help desk, plus reliable external sources such as SAMA (3.3.16.3.a, b)
  • A set analysis method, actionable output, and sharing with stakeholders (3.3.16.3.c to f)
Threat intelligence procedure, source list, intelligence reports
3.3.17Vulnerability Management
Banks: level 4
  • Process approved and measured (3.3.17.1, 3.3.17.2)
  • Covers all information assets, with a risk-based scan frequency (3.3.17.3.a, b)
  • Vulnerabilities classified, with fix deadlines per class and priority for classified assets (3.3.17.3.c to e)
  • Patch management and a set deployment method (3.3.17.3.f)
Scan reports, remediation deadlines per class, patch reports

Domain 3.4: Third Party Cyber Security

Three subdomains about vendors, outsourcing and cloud. Two of them need SAMA's approval before you act.

IDSubdomainWhat to check (our words)Evidence to keep
3.4.1Contract and Vendor Management
  • Baseline cyber requirements, the cyber function's role in due diligence, and the right to review and audit (3.4.1.4)
  • Risk assessment in procurement, requirements in tenders, vendor replies evaluated and tested (3.4.1.5.a to d)
  • Incident escalation, exit terms and mutual confidentiality in contracts (3.4.1.5.e to g)
  • Cyber requirements in SLAs, reported and reviewed (3.4.1.6)
Vendor risk assessments, contract clauses, SLA reports
3.4.2Outsourcing
  • Cyber requirements in the outsourcing policy and process, measured (3.4.2.1, 3.4.2.2)
  • SAMA approval before material outsourcing; the cyber function involved (3.4.2.3.a, b)
  • Follows SAMA's outsourcing rules (3.4.2.3.c)
Outsourcing register, SAMA approvals, cyber review records
3.4.3Cloud Computing
  • Risk assessment and due diligence on the provider; SAMA approval before use; a contract with cyber terms (3.4.3.4.a)
  • Cloud services in Saudi Arabia in principle, or explicit SAMA approval for services outside it (3.4.3.4.b)
  • No secondary use of your data; provider controls; logical data segregation (3.4.3.4.c to e)
  • Continuity, your right to review, audit and examine, and data return and deletion on exit (3.4.3.4.f to h)
  • Private (internal) cloud is out of scope of this subdomain
Cloud register, SAMA approvals, provider due diligence, contract clauses

In the Excel tracker every row has a current maturity score, a target, the gap, a status, an owner, a due date and an evidence link.

SAMA CSF Maturity Levels: What Level 3 Means for Each Row

SAMA measures maturity on a six-level scale, and you reach a level only when every criterion of the levels below it is in place. Every Member Organization should operate at level 3 or higher.

SAMA CSF maturity levels 0 to 5, with level 3 as the minimum and level 4 required of banks for 3.3.14 to 3.3.17
SAMA CSF maturity levels 0 to 5, with level 3 as the minimum and level 4 required of banks for 3.3.14 to 3.3.17
LevelName (SAMA)What it looks like (our words)
0Non-existentNothing written, no awareness, the control is not in place.
1Ad-hocPartly defined and run inconsistently; varies by department or owner.
2Repeatable but informalA standard practice exists but is unwritten and not formally approved.
3Structured and formalizedDefined, approved and implemented; you can demonstrate it; policies, standards and procedures exist; compliance is monitored and KPIs are reported.
4Managed and measurableEffectiveness is measured on a schedule with KRIs and trend reporting, and results drive improvements.
5AdaptiveA continuous improvement plan, tied into enterprise risk management and benchmarked against peer and sector data.

In practice, level 3 for a subdomain means four things you can show:

  • A policy endorsed by the board that says why, a standard that says what, and a procedure that says how.
  • The control is in place and you can demonstrate it, not just describe it.
  • Compliance with those documents is monitored. The CSF says a governance, risk and compliance (GRC) tool is preferred for this, not required.
  • KPIs are defined, tracked and reported.

Banks have a higher bar in four subdomains. SAMA's circular 29814/67 asked banks to reach level 4 for all components of 3.3.14 Event Management, 3.3.15 Incident Management, 3.3.16 Threat Management and 3.3.17 Vulnerability Management, with a target of the end of Q3 2022. Level 4 adds key risk indicators (KRIs) with thresholds, measured on a schedule and used for trend reporting. The same circular asks for a yearly internal audit report on CSF compliance against the required maturity. The tracker sets these targets for you when you pick "Bank" as your institution type.

Self-Assessment, SAMA Review and Waivers

The CSF is checked through a periodic self-assessment that you complete with SAMA's questionnaire. SAMA then reviews and audits it to set your compliance level and maturity level, and its inspection visits check that the assessment is accurate. The CSF does not state how often the questionnaire runs or its format, so follow the instructions SAMA sends you.

The SAMA CSF assessment cycle: gap assessment, maturity scoring, board-approved roadmap, implementation with evidence, self-assessment and SAMA review
The SAMA CSF assessment cycle: gap assessment, maturity scoring, board-approved roadmap, implementation with evidence, self-assessment and SAMA review

The framework is principle based. When a control consideration cannot be implemented as written, the CSF expects three things: compensating controls, an internal risk acceptance, and a formal waiver request to SAMA (section 2.2 and its Appendix D). Record each one in the tracker, because an exception without a waiver reads as a gap.

The original 2017 circular gave banks a sequence that still works as a project plan: a gap assessment against every requirement, a roadmap to at least level 3 approved by the board, regular progress reports, and follow-up by the cyber security committee.

Device and Endpoint Items in the SAMA CSF

Laptops, desktops, phones and tablets appear in more places than the BYOD subdomain. The infrastructure security standards in 3.3.8 must cover workstations, laptops, tablets and mobile devices in offices, not only servers in the data centre. This is also where the CSF names mobile device management (MDM): 3.3.10 expects it on personal devices that staff use for work.

Device and endpoint items in the SAMA CSF, with the ones a device management tool can supply evidence for
Device and endpoint items in the SAMA CSF, with the ones a device management tool can supply evidence for
CSF referenceTopicWhat the CSF expects (our words)
3.3.3.3.a, eAsset register and discoveryEvery laptop, desktop, phone and tablet sits in one register with an owner; new devices are found, not only typed in
3.3.8.4, 3.3.8.5Hardening standards cover end-user devicesYour infrastructure standards name workstations, laptops, tablets and mobile devices in offices as well as data centres
3.3.8.6.aConfiguration parametersStandards set the configuration each device type must carry
3.3.8.6.dApproved softwareOnly approved software runs on devices
3.3.8.6.fMalware protectionAnti-malware with application allow-listing and APT protection
3.3.8.6.g, 3.3.17.3Patching and vulnerabilitiesRisk-based scans, fix deadlines per class, a set patch deployment method
3.3.8.6.jPeriodic compliance reviewDevice standards are checked for compliance on a schedule
3.3.9.4EncryptionApproved encryption, when to use it, and key lifecycle management
3.3.5.4.e, fMFA and remote accessMFA for sensitive and critical systems and all remote access
3.3.10.4.a, bBYOD rules and lost devicesUser duties, training and consequences for tampered, lost or stolen devices and leavers
3.3.10.4.cBYOD data separationBusiness data kept apart from personal data, for example a container
3.3.10.4.eBYOD MDM and encryptionMDM, device access controls and encryption on personal devices used for work
3.3.1.3.eLeavers return devicesAccess revoked and devices returned when staff leave
3.3.11Secure disposalData on retired devices made non-retrievable, for example by secure wiping
3.3.14.4.hProtected logsSecurity logs protected from change and loss

The CSF sets no numbers here: no screen-lock timeout, no patch deadline. You set them in your own standards, and SAMA checks that you follow them. Write the values into your infrastructure and BYOD standards, then keep device reports that show the values are in force. Our BYOD policy template and IT asset management policy template give you a starting text.

Third Parties, Outsourcing and Cloud

Domain 3.4 is short but has two hard gates. Material outsourcing needs SAMA's approval first (3.4.2), and banks also follow SAMA's Rules on Outsourcing. For hybrid and public cloud, you need a risk assessment and due diligence on the provider, SAMA's approval before you use the service or sign, and a contract with cyber terms (3.4.3). Cloud services should in principle be located in Saudi Arabia; using one outside the Kingdom needs SAMA's explicit approval.

For every vendor, check that the contract gives you the right to review and audit, sets an incident escalation route, covers exit and data return, and includes mutual confidentiality (3.4.1). The workbook's third-party tab flags vendors that need a SAMA approval you have not recorded, and cloud services outside Saudi Arabia without one.

The SAMA CSF Alongside PDPL and NCA ECC

Two other rule sets often land on the same team. SAMA's PDPL circular of December 2021 tells SAMA-supervised institutions to align with the Personal Data Protection Law through a gap analysis and a board-approved plan. And banks that NCA treats as critical national infrastructure may need NCA's Essential Cybersecurity Controls (ECC-2:2024) as well as the CSF. No SAMA or NCA document maps one onto the other or says which takes precedence, so check your obligations with both regulators.

If you run both, keep one evidence register and tag each item with the CSF subdomain and the ECC control it supports. The Excel evidence register has a column for the ECC reference. Our NCA ECC checklist has a matching tracker.

Common Gaps Before a SAMA Review

  • Scoring level 3 without the documents. Level 3 needs an approved policy, standard and procedure plus proof that the control runs. A working control with no written standard is level 2.
  • Device standards that stop at the data centre. 3.3.8 covers laptops, tablets and phones in offices. Many hardening standards only cover servers.
  • An asset register built by hand. 3.3.3 asks for discovery of new assets, so a spreadsheet nobody reconciles with what is actually on the network falls short.
  • Patching with no deadlines. 3.3.17 asks for fix deadlines per vulnerability class. "As soon as possible" is not a deadline.
  • Personal devices allowed by habit. If staff read work email on their own phones, 3.3.10 applies, with a standard, user agreements, MDM and encryption.
  • Exceptions without waivers. A control you decided not to implement needs compensating controls, a risk acceptance and a waiver request to SAMA.
  • Cloud tools signed by a business team. Under 3.4.3 a public cloud service needs SAMA's approval first, including SaaS tools that IT did not buy.

Where trio.so Fits

Most of the SAMA CSF is governance, risk, operations and third-party work that no device tool does for you. trio.so handles one slice: the laptops, desktops, phones and tablets your staff use, from one console on Windows, macOS, iOS and Android.

  • A SAMA CSF template in the compliance engine. Select it, and trio.so checks your managed devices for settings such as disk encryption, screen lock, firewall and OS updates, then lets you export the results as evidence for your self-assessment.
  • Device setting checks: disk encryption, screen lock, host firewall, secure boot and OS update status, with status per device.
  • Encryption enforcement: BitLocker on Windows, FileVault on Mac and encryption on phones, with encryption status per device.
  • Passcode and screen-lock policies on enrolled devices.
  • OS update status and vulnerability findings scored with CVSS, EPSS and CISA's KEV list.
  • A device inventory that lists installed apps on Windows, macOS, iOS and Android, for your asset register and approved-software checks.
  • Lost and retired devices: wipe a lost company-owned device remotely, or lock a lost Mac, iPhone, iPad or Android device. There is no wipe of business data only on personal devices.
  • Evidence export, so device status goes into your self-assessment file as a dated record.
  • An Arabic console with right-to-left layout.

In the Excel tracker, the "trio.so can supply" column shows which rows device evidence from trio.so can support, such as the asset register, the infrastructure standards for end-user devices, cryptography and vulnerability management. Our SAMA compliance automation guide explains what else you can automate and what you can't.

trio.so does not assess or certify anything, and it does not do the governance, risk, continuity or third-party parts of the CSF. Your self-assessment and SAMA's review decide your maturity level. Learn more about SAMA CSF compliance in trio.so and compliance automation. Plans start at $5 per device.

Start free trial Book a demo

14-day free trial. No credit card required.

Sources. Last reviewed October 2026 against the SAMA Cyber Security Framework v1.0 (May 2017), the version in force in the SAMA Rulebook on 27 October 2026. Control-consideration numbers are SAMA's; every description here is our own paraphrase, not SAMA text. The Rulebook's English is a translation and the Arabic text governs. This article is guidance, not legal advice or an assessment. The SAMA Cyber Security Framework is published by the Saudi Central Bank (SAMA). trio.so is not affiliated with or endorsed by SAMA.

Ready-to-use Templates

Must-have Template Toolkit for IT Admins

Explore All
Template Toolkit

Start your free trial

No credit card required
Full access to all features

Manage Every Device From One Console

trio.so brings device management, patching and security policies for Windows, macOS, Linux, iOS/iPadOS and Android into one console. Enroll a device and see it in the console within minutes.

14-day free trial. No credit card required.

trio.so brings device management, patching and security policies for Windows, macOS, Linux, iOS/iPadOS and Android into one console. Enroll a device and see it in the console within minutes.

Smiling womanAbstract geometric patternAbstract geometric patternSmiling womanSmiling woman

Frequently Asked Questions (FAQ)

Have questions? We've got answers. This section covers some of the most commonly asked questions related to this topic.

A SAMA compliance checklist covers the 32 subdomains of the SAMA Cyber Security Framework across its 4 domains: leadership and governance, risk management and compliance, operations and technology, and third-party security. For each subdomain it lists what to check, the evidence to keep, an owner and a maturity score from 0 to 5.

The SAMA CSF has 32 subdomains in 4 domains: 7 in Cyber Security Leadership and Governance, 5 in Risk Management and Compliance, 17 in Operations and Technology, and 3 in Third Party Cyber Security. Older summaries that say 29 leave some out.

Level 3, Structured and formalized, is the minimum SAMA expects. Controls are defined, approved and implemented, you can demonstrate them, policies, standards and procedures exist, compliance with them is monitored and KPIs are reported. You also need every criterion of levels 1 and 2.

No. The CSF describes no certificate for institutions or vendors. Your self-assessment, SAMA's review and audit of it, and SAMA's inspection visits set your compliance and maturity level, so treat any claim of being SAMA certified with caution.

No. The CSF draws on ISO, NIST, ISF, Basel and PCI material, but SAMA assesses you against the CSF itself, with its own maturity model and SAMA-specific items such as a Saudi CISO approved by SAMA and SAMA approval for material outsourcing and cloud. ISO 27001 work gives you useful evidence for many rows.

Apply compensating controls, accept the remaining risk internally and request a formal waiver from SAMA, as section 2.2 of the CSF describes. Keep the waiver request and SAMA's answer with your evidence.

Related

From the blog

The related industry news, interviews, technologies, and resources.