JOR Regulatory Hub
Region: Middle East
Middle East governance, risk and compliance intelligence
Central Bank of Jordan
Industries Regulated
Banking and lending, Regulated financial services
Jordan Securities Commission
Industries Regulated
Capital markets and listed companies
Ministry of Digital Economy and Entrepreneurship
Industries Regulated
Cross-sector data controllers and processors
Supervisory Priorities
The applicable perimeter depends on entity type, licence and sector. These priorities provide a practical starting point for programme design and evidence management.
Regulatory Alignment
Official-source and product-fit review completed 1 September 2026.
The platform directly manages a central process or evidence set described in the requirement.
The platform contributes linked evidence, oversight or follow-up but is not the main system for the requirement.
A weak or unsubstantiated product relationship is intentionally omitted.
| Regulation and Authority | Applies To | Operational Focus | Platform Fit and Workflow Support | Source |
|---|---|---|---|---|
| Corporate Governance Instructions for Banks No. 2 of 2023CBJ | Banks operating in Jordan | Board and committee governance, control functions, risk oversight, independence and accountability. |
 Primary fit Risk and control registers, assessments, appetite or limits, KRIs, treatments, approvals and board reporting.  Supporting fit Risk-based assurance, control design and effectiveness testing, evidence, findings and action follow-up. BoundaryWorkflow and evidence support only. Applicability and legal interpretation remain with the organisation and its advisers. |
Source |
| Cybersecurity Framework for the Financial SectorCBJ | Financial institutions within CBJ scope | Cyber-risk governance, resilience capabilities, threat understanding, control evidence and sector response. |
Primary fit Operational-risk registers, critical-service assessments, controls, KRIs, treatments and leadership reporting. Supporting fit Risk-based assurance, control testing, evidence, findings, approvals and remediation follow-up. BoundaryGRC workflow and evidence support only. The platforms do not replace technical security monitoring, detection or protection tools. |
Source |
| Jo-FinCERT Incident CoordinationCBJ | Financial and banking institutions | Cyber-incident response, threat coordination, escalation and sector resilience. |
 Primary fit Cyber-event intake, escalation, investigation, root cause, corrective action, recovery tracking and audit trail. Supporting fit Operational-risk registers, critical-service assessments, controls, KRIs, treatments and leadership reporting. BoundaryGRC workflow and evidence support only. The platforms do not replace technical security monitoring, detection or protection tools. |
Source |
| Personal Data Protection Law No. 24 of 2023MODEE | Data controllers processing personal data in Jordan | Data governance, controller responsibilities, data-subject rights, complaints and documented response to breaches. |
Primary fit Incident intake, assessment, investigation, notification workflow, corrective action, escalation and closure evidence. Supporting fit Privacy risks, controls, assessments, treatment actions, ownership, approvals and management reporting. BoundaryWorkflow and evidence support only. Applicability and legal interpretation remain with the organisation and its advisers. |
Source |
This mapping is an implementation aid, not legal advice. It describes configurable workflow and evidence support, not automatic compliance. Always validate applicability, current versions, implementation dates and supervisory expectations with qualified advisers and the relevant authority.
The mapping uses the capabilities documented in the current brochures. It does not extend the platforms beyond their stated functional scope.
Best suited to enterprise risk ownership, risk and control registers, assessments, appetite and tolerances, KRIs, treatments, approvals, dashboards and board reporting.
Best suited to the audit universe, risk-based planning, engagement execution, RCM-linked design and effectiveness testing, evidence, findings, approvals and follow-up.
Best suited to incident intake, triage, investigation, root-cause analysis, escalation, notifications, corrective and preventive actions, closure and lessons learned.
Scope boundary
Connected Operating Model
Structure local requirements by entity, licence, authority and accountable owner.
Link obligations to risks, controls, incidents, tests, findings and remediation.
Track KRIs, control status, audit coverage, incidents and action closure continuously.
Regional Coverage
Delaware, United States
Karachi, Pakistan
Riyadh, Saudi Arabia
Melbourne, Australia
