SAMA CSF

Released / current context

Saudi financial-sector cybersecurity framework issued by the Saudi Central Bank for supervised financial institutions.

Mandatory or voluntary

Applies where SAMA supervision, policy, contract, or customer assurance requires it.

Who should care

Banks, insurers, payments firms, finance companies, fintech partners, and service providers supporting Saudi financial services.

Control model

Cyber governance, risk management, cyber defense, resilience, third-party controls, incident readiness, monitoring, and evidence of periodic assessment.

What SAMA CSF asks teams to prove

Cyber Security Framework becomes operational when obligations are turned into scoped controls, named owners, evidence requests, review decisions, residual risk, and management reporting. The guide page keeps that chain explicit so buyers can understand how the standard is handled inside PlanGRC.

Practical roadmap

1. Define scope

   Confirm business units, systems, data classes, regions, and services where SAMA CSF applies.

2. Map controls

   Translate obligations into controls, owner assignments, due dates, testing approach, and evidence expectations.

3. Collect proof

   Request evidence from owners, preserve attachments or vault references, and keep reviewer decisions traceable.

4. Assess gaps

   Score readiness, identify missing evidence, evaluate residual risk, and create remediation tickets where needed.

5. Report and maintain

   Publish executive and audit-ready views, keep exceptions visible, and re-run periodic reviews after change.

Related workflows