Skip to main content

Free 30-min security demo Book Now

Application Security

NCA ECC and SAMA CSF: AppSec Testing Guide

What Saudi NCA ECC and the SAMA Cyber Security Framework expect for secure development, code review, SAST, DAST and penetration testing evidence.

Offensive360 Security Research Team 5 min read
NCA ECC SAMA CSF Saudi Arabia cybersecurity compliance application security testing secure code review SAST DAST PDPL

Neither the NCA Essential Cybersecurity Controls (ECC) nor the SAMA Cyber Security Framework (CSF) tells you to buy a specific tool. Both require a secure development process, security testing before systems go live, regular vulnerability assessment and penetration testing, and evidence that findings are fixed. In practice, organisations meet those requirements with a secure coding standard, static testing (SAST), dynamic testing (DAST), periodic penetration tests and tracked remediation.

This guide maps the framework areas to practical testing activities and to the evidence an assessor normally asks for. It is a working summary, not legal advice. Use the current official texts from the National Cybersecurity Authority and the Saudi Central Bank as the reference.

Who must comply

  • NCA ECC applies to government organisations in the Kingdom, including ministries, authorities and their companies, and to private organisations that own or operate critical national infrastructure. The current version is ECC-2:2024.
  • SAMA CSF applies to organisations regulated by the Saudi Central Bank: banks, insurance and finance companies, and financial market infrastructure.
  • PDPL, the Personal Data Protection Law, applies to organisations that process personal data of individuals in the Kingdom, and requires appropriate technical measures to protect it.

Many organisations fall under more than one, and additional NCA frameworks such as the Cloud Cybersecurity Controls may apply.

NCA ECC areas that touch application security

ECC areaWhat it asks for, in summaryTypical testing activity
Cybersecurity in information and technology project management (1-6)Cybersecurity requirements in projects, including secure coding standards, trusted sources for tools and libraries, security testing of software, secure integration, and configuration review and hardening before go-liveSecure coding standard, SAST and dependency analysis in the pipeline, pre-release security test
Vulnerabilities management (2-10)Periodic vulnerability assessment, classification by severity, and remediationScheduled DAST and infrastructure scans, remediation tracking
Penetration testing (2-11)Periodic penetration tests of externally facing and critical systemsManual penetration test with retest
Web application security (2-15)Protection of external web applications, including secure architecture, secure protocols and strong authenticationDAST of external applications, configuration review

The implementation guide published by the NCA lists example deliverables for these controls, such as a secure coding standard and records of the security tests performed.

SAMA CSF areas that touch application security

The SAMA framework organises its controls by domain. The areas most relevant to development teams are:

  • Application security. Defined and approved application security standards, applied to in-house and acquired applications.
  • Change management. Security requirements and security testing as part of changes before production.
  • Vulnerability management. Regular identification and remediation of vulnerabilities, including penetration testing.
  • Electronic banking and payment systems. Additional protection for customer-facing channels.

SAMA assesses maturity, so a control that is documented, applied consistently and measured scores higher than one that is performed ad hoc.

Evidence assessors usually ask for

  1. An approved secure coding standard and proof that developers are trained on it.
  2. Testing records per release. SAST and DAST reports linked to the application version, with dates.
  3. Third-party component inventory. A software bill of materials with known-vulnerability and licence status.
  4. Penetration test reports for critical and internet-facing systems, with scope, method and retest results.
  5. Remediation tracking. Each finding with severity, owner, due date and closure evidence.
  6. Go-live approval. A record that security testing and hardening were reviewed before release.

A practical testing programme

StageActivityOutput
DesignThreat modelling for new systemsSecurity requirements
DevelopmentSAST and dependency analysis on each mergeFindings fixed before release
Pre-releaseAuthenticated DAST and configuration reviewRelease security report
ProductionScheduled DAST and attack surface monitoringTrend and remediation reports
Yearly, and after major changeManual penetration test with retestIndependent assurance report

Hosting and language considerations

Source code and findings are sensitive, and many public-sector and financial organisations prefer to keep them inside their own environment. A self-hosted testing platform, on-premise or in a cloud region in the Kingdom, supports that choice. Arabic-language reports and interfaces help when results are shared with management and auditors.

How Offensive360 supports this

Offensive360 provides SAST, DAST, mobile application testing and software composition analysis in one platform that runs on-premise, in Azure or in a disconnected network, with Arabic and English interfaces and reports. Findings are mapped to OWASP and CWE categories and can be exported as evidence. The GRC platform includes NCA ECC-2:2024, SAMA CSF and PDPL control packs for tracking control status and evidence, and the services team performs manual penetration tests and code reviews.

See the Gulf overview by country, GRC for Saudi Arabia, compliance mapping and deployment options, or book a demo.

This summary reflects the publicly available framework texts as of November 2026. Control wording and numbering can change between versions, so confirm against the official documents.

Frequently asked questions

Does NCA ECC require SAST and DAST?

The Essential Cybersecurity Controls do not name specific tool types. They require secure coding standards, security testing of software against the organisation's requirements, and review and hardening before go-live. Static and dynamic testing are the usual way to produce evidence for those requirements.

Which NCA ECC areas cover application security?

The main ones are cybersecurity in information and technology project management (subdomain 1-6), vulnerability management (2-10), penetration testing (2-11) and web application security (2-15). Always read the current official NCA text for the exact control wording.

What does the SAMA Cyber Security Framework expect for applications?

SAMA expects member organisations to define and apply application security standards, follow a secure development life cycle, test security before changes go to production, and manage vulnerabilities, with penetration testing of important systems.

Can security testing tools be hosted inside the Kingdom?

Yes. Self-hosted testing platforms can run in your own data centre or in a cloud region in the Kingdom, which keeps source code and findings inside your environment. This helps with data-location policies set by the organisation or its regulator.

Governance, risk & compliance

Evaluate your risk and evidence workflows

Explore Offensive360 GRC in Arabic or English. Bring your frameworks, evidence requirements and deployment constraints to an early-access walkthrough.

Also see: GRC for Saudi Arabia

Evaluate your risk and evidence workflows

Book a GRC demo