Two frameworks shape application security work in Jordan. The Central Bank of Jordan (CBJ) cybersecurity framework for the financial sector requires a secure development life cycle and secure coding, with penetration testing among the checks. The Jordan National Cybersecurity Framework from the National Cybersecurity Center (NCSC) describes security in development as a set of capabilities: secure code management, test management and defect management. Neither names a tool. Both expect a process that can be shown to work.
This guide maps those expectations to practical testing activities. It is a working summary, not legal advice. Use the current official texts as the reference.
Who must comply
- CBJ framework. Banks and other financial institutions supervised by the Central Bank of Jordan, including payment and electronic money companies under their own instructions.
- National framework. Government entities and organisations brought into its scope by the NCSC, with banking named as a sector where it carries special weight.
What the CBJ framework expects
| Control area | What it asks for, in summary | Typical testing activity |
|---|---|---|
| Secure development life cycle | Security in every development phase, not only at the end, with penetration testing among the checks | Design review, SAST during development, DAST and penetration test before release |
| Secure coding | Coding practices based on recognised references such as the OWASP Top Ten and the CWE Top 25, root-cause analysis when a flaw is found, and secure coding terms in supplier agreements | Coding standard, static analysis rules mapped to those lists, supplier code review |
| Vulnerability management and testing | Regular assessment and testing of systems by sensitivity | Scheduled scans and periodic penetration tests |
What the national framework expects
The security in development capabilities describe a pipeline in which:
- Code is managed securely, with review before merge.
- Testing is planned and automated, including static analysis and vulnerability scanning.
- Penetration testing has defined checkpoints in delivery.
- Defects are tracked to closure.
The framework builds on ISO/IEC 27001 and the NIST Cybersecurity Framework, so organisations already aligned with those have a head start.
Evidence a supervisor or assessor asks for
- A secure development policy and an approved coding standard.
- Static and dynamic testing reports per release.
- Root-cause notes for significant findings.
- Penetration test reports for critical systems, with retest results.
- A defect register with severity, owner and closure evidence.
- Supplier agreements that include secure coding and testing terms.
A practical programme
| Stage | Activity | Output |
|---|---|---|
| Design | Threat modelling | Security requirements |
| Development | SAST and dependency analysis on each merge | Findings fixed before release |
| Before release | Authenticated DAST and mobile app testing | Release security report |
| Yearly, and after major change | Independent penetration test with retest | Assurance report |
| Continuous | Scheduled scans, defect tracking | Trend and closure reports |
How Offensive360 supports this
Offensive360 provides SAST, DAST, mobile application testing and software composition analysis in one platform that runs on-premise or in a disconnected network, with Arabic and English interfaces and reports. Findings map to the OWASP Top Ten and CWE, which matches the references used by the CBJ framework. The services team performs manual code reviews and penetration tests with retests.
See solutions for financial services, deployment options and the companion guides for Saudi Arabia and Qatar, or book a demo.
This summary reflects publicly available texts as of November 2026. Wording changes between versions, so confirm against the official documents.
Frequently asked questions
Does the Central Bank of Jordan require secure development?
Yes. The CBJ cybersecurity framework for the financial sector includes a secure development life cycle control that covers every development phase and names penetration testing among the checks, and a secure coding control that refers to the OWASP Top Ten and the CWE Top 25.
What does the Jordan National Cybersecurity Framework say about development?
Its security in development capabilities cover secure code management, test management and defect management, with automated testing, static analysis, code review and penetration testing as part of the delivery pipeline.
Do these frameworks name specific tools?
No. They describe the controls and the outcomes. Static testing, dynamic testing and independent penetration tests are the usual way to produce the evidence.
Can the testing platform stay inside our own network?
Yes. A self-hosted platform runs in your own data centre, so source code and findings stay inside your environment.