Ordit
Guide

ADGM cyber risk management (FSRA GEN 3.5): a practical guide

After reading this you will know what the FSRA's cyber risk management rules require, whether they apply to your entity, how they map to ISO 27001 and NIST CSF, and what to have in place before a supervisor asks.

Who this guide is for

  • Compliance officers, MLROs and heads of technology at FSRA Authorised Persons and Recognised Bodies who must evidence GEN 3.5 to a supervisor.
  • Founders applying for a Financial Services Permission in ADGM, who will be asked how the framework will be met from day one.
  • Boards and senior managers of any regulated firm, in ADGM or elsewhere, who want a worked example of what a modern cyber rulebook asks of them: board ownership, an asset inventory, third-party terms, testing and fast notification.
  • Outsourced compliance providers and group security leads who support an ADGM entity alongside entities regulated by the DFSA, the FCA, MAS or others.

What is FSRA GEN 3.5?

GEN 3.5 is the chapter of the FSRA's General Rulebook that sets binding cyber risk management requirements for financial firms in Abu Dhabi Global Market. It requires each firm to run a Cyber Risk Management Framework owned by its governing body, to know and protect its ICT assets, to manage the cyber risk in its service providers, to test and train, and to notify the FSRA of material cyber incidents within 24 hours. The rules were made by the FSRA Rules (Cyber Risk Management) 2025, announced on 29 July 2025, and compliance has been required since 31 January 2026.

GEN 3.5 is the chapter of the FSRA's General Rulebook that sets binding cyber risk management requirements for financial firms in Abu Dhabi Global Market.

The rules did not appear from nowhere. The FSRA set out its expectations in the Guidance on Governance Principles and Practices to Mitigate Cyber Threats and Crime (Notice FSRA/FCPU/15/2020) in November 2020, consulted on IT risk through Discussion Paper No. 1 of 2023, and published the 92-page Information Technology Risk Management Guidance on 20 November 2024. Notice 13 of 2025 introduced standard incident reporting templates in February 2025. Consultation Paper No. 3 of 2025, published on 30 April 2025 with comments due by 11 June, proposed the rules with a three-month transition. After feedback the FSRA extended the transition to six months, announced the final rules on 29 July 2025 and made consequential changes to COBS, PIN, CIB, PRU and GLO, as well as to the Market Infrastructure Rulebook. Notice 22 of 2026, issued on 29 January 2026, revised the incident templates to match the new rules two days before they took effect.

One caveat runs through this guide. The final text of GEN 3.5 is published in the ADGM Rulebook hosted by Thomson Reuters, which returned an error when we tried to fetch it on 8 November 2026. The rule numbers and wording below follow the draft text in Appendix 3 to Consultation Paper No. 3, cross-checked against the FSRA's Notice 22 (which cites GEN 3.5 and 3.5.18) and against published law-firm analyses of the final rules. Where the final text is known to differ from the draft, we say so. Check rule numbers against the Rulebook before quoting them to a supervisor.

Does it apply to us?

GEN 3.5 applies to every FSRA Authorised Person, and to Recognised Bodies (exchanges and clearing houses) through an amendment to the Market Infrastructure Rulebook. It does not apply to ADGM entities that are not regulated by the FSRA, such as holding companies, special purpose vehicles or professional services firms registered only with the Registration Authority. Those entities have no FSRA cyber obligation, but they are not free of duties: the ADGM Data Protection Regulations 2021 require every controller to notify personal data breaches to the Commissioner of Data Protection.

GEN 3.5 applies to every FSRA Authorised Person, and to Recognised Bodies (exchanges and clearing houses) through an amendment to the Market Infrastructure Rulebook.

Work through the following:

  1. Are you an Authorised Person holding a Financial Services Permission? GEN 3.5 applies in full, proportionate to your nature, scale and complexity.
  2. Are you a Recognised Investment Exchange or Recognised Clearing House? The same requirements apply through the Market Infrastructure Rulebook.
  3. Are you applying for a Financial Services Permission? Expect to show how the framework will be in place at authorisation.
  4. Are you an ADGM-registered company with no FSRA permission? GEN 3.5 does not apply. The Data Protection Regulations 2021 do, and we found no separate Registration Authority cyber instrument.
  5. Are you an FSRA firm that also holds personal data? Both regimes apply, with two different clocks (see the notification section).

Under the Data Protection Regulations 2021, a controller must notify a personal data breach to the Commissioner without undue delay and, where feasible, within 72 hours, inform data subjects where there is a high risk to them, and keep a record of breaches and of decisions not to notify. The Office of Data Protection's page states the 72-hour window; we could not confirm the section number, so we do not cite one.

Proportionality is written into the rule. GEN 3.5.1 requires systems and controls proportionate to the nature, scale and complexity of the business, and the FSRA's 2025 survey findings accept that smaller firms adopt basic controls widely and advanced controls less so. Proportionate does not mean optional: every element of the framework must exist, scaled to the firm.

How does GEN 3.5 relate to the IT Risk Management Guidance and the 2020 principles?

GEN 3.5 is the binding "what", the IT Risk Management Guidance is the non-binding "how", and the 2020 governance principles are the earlier expectations the rules now formalise. The three documents form one stack, and supervisors will read your framework against all of it.

GEN 3.5 is the binding "what", the IT Risk Management Guidance is the non-binding "how", and the 2020 governance principles are the earlier expectations the rules now formalise.

The Information Technology Risk Management Guidance (VER01.201124, 20 November 2024) runs to 92 pages and 15 chapters, each with desired outcomes and best practices, in four sections: culture (governance, risk management, third parties and supply chain, compliance and audit); the IT environment (system lifecycle, asset management, infrastructure, data lifecycle, resilience, cyber event management and security testing); interacting securely (access management, online transaction security, cryptography); and business-embedded technologies (algorithm-driven solutions, meaning AI and models, and decentralised infrastructure). It applies to Authorised Persons and Recognised Bodies as guidance, proportionate to size. It is expressly non-binding, but the FSRA says the rules build on it, so a framework that follows its desired outcomes will be well placed to evidence the rules.

The Governance Principles and Practices to Mitigate Cyber Threats and Crime (Notice FSRA/FCPU/15/2020, 9 November 2020) set out the FSRA's earlier view of good cyber governance. If your firm built its approach on the 2020 principles, most of it carries forward; the rules add fixed minimums (annual assessment, annual testing, annual training, 24-hour notification) and make the governing body's responsibility a rule rather than a principle.

What does GEN 3.5 require?

Rule numbers follow the consultation draft, as explained above.

What must the cyber risk management framework contain?

GEN 3.5.1 requires each firm to establish and maintain a Cyber Risk Management Framework, with systems and controls proportionate to the nature, scale and complexity of the business, clearly defined roles and accountability for decisions in both business-as-usual and stressed situations, and systems for identifying and assessing cyber risk, protecting ICT assets, monitoring and testing, and managing incidents. The framework must be reviewed regularly and at least annually, and integrated into the firm's overall risk management framework under GEN 3.3.4 to 3.3.6, not run as a separate IT document.

The guidance to the rule lists frameworks a firm may build on: the UAE Information Assurance Regulation (2020), the ISO/IEC 27000 family, the NIST Cybersecurity Framework (2018), the CIS Critical Security Controls (2024), the CPMI-IOSCO guidance on cyber resilience for financial market infrastructures (2016), the CSA Cloud Controls Matrix (2024) and NIST SP 800-30 for risk assessment. The FSRA does not prescribe one. Pick the one your firm already uses and map the rule to it.

What is the governing body responsible for?

GEN 3.5.3 places ultimate responsibility for cyber risk on the governing body and senior management. They must set the firm's cyber risk tolerance, receive regular reporting on cyber risk and the performance of the framework, and take part in cyber training themselves. The FSRA's 2025 survey findings reinforce this: cyber risk needs ongoing board attention and clearly assigned operational roles. A board that has never seen a cyber report or set a tolerance is the first gap a supervisor will find.

What must the asset inventory and risk assessment cover?

GEN 3.5.4 requires a current inventory of ICT assets, classified by confidentiality and business criticality, recording location and purpose, and including assets held by third-party service providers. On top of the inventory, the firm must perform cyber risk assessments regularly and at least annually, covering threats, the effectiveness of controls, test results and business impact. The FSRA's survey found that firms without complete inventories and systematic vulnerability management cannot prioritise protection, and said so in its recommendations.

Which protection controls are required?

GEN 3.5.5 to 3.5.12 set out the baseline controls every firm must have. In summary: up-to-date anti-malware with automatic scanning; network security controls and perimeter protection; access on the principle of least privilege, with prompt revocation and controlled privileged access; strong authentication, with multi-factor authentication cited for internet-facing systems and privileged accounts; change management with testing, approval and either separated environments or segregation of duties; patch and vulnerability management prioritised by criticality; encryption proportionate to sensitivity, in transit and at rest; and restricted, logged physical access to data centres and server rooms. These are the controls the FSRA found widely adopted in its 2025 survey; the rules make them a floor.

What does the rule require for third parties and outsourcing?

GEN 3.5.2 requires due diligence on ICT service providers, contracts that oblige the provider to notify the firm of incidents, cooperate in remediation and allow the firm to verify the service, and effective supervision of the service, with the firm remaining fully responsible. The scope is wider than the GEN 3.3.31 to 3.3.32 outsourcing rules: it covers all ICT services, including cloud and server maintenance, and including one-off services.

Two points from the final text matter here. The draft had included a general duty for providers to comply with the firm's cyber risk requirements, which was dropped, and the FSRA has said that on-site audit rights are not required for every provider. Verification can be proportionate. The practical consequence is a contract review: every ICT contract needs incident notification, cooperation and verification clauses, and the FSRA's survey recommended that service provider agreements include explicit incident reporting and defined security standards. The FSRA also ran an outsourcing thematic review in 2025, reported in a Dear SEO letter on 29 January 2026, so expect third-party arrangements to be looked at.

What testing is required?

GEN 3.5.14 requires ongoing monitoring of the effectiveness of controls and a resilience testing programme, which may include vulnerability assessments, scenario-based tests, penetration tests, bug bounties and red teaming. Testing must be regular, and at least annual for internet-facing systems. Findings must be prioritised and remediated, and results reported regularly to senior management. The survey found penetration testing and red teaming adoption limited, which is a signal of where supervisors will look.

What training is required?

GEN 3.5.13 requires all relevant employees to be trained at least annually on the firm's cyber policies, and to be able to detect and report incidents. New joiners must be trained within a reasonable period, and privileged users must receive targeted training. Combined with GEN 3.5.3, this means the board trains too.

What must the incident response plan cover?

GEN 3.5.15 to 3.5.17 require continuous monitoring and log review, an escalation process with a named point of contact, and a written Cyber Incident Response Plan that is tested regularly, reviewed at least annually and after any reportable incident, and integrated with crisis management and disaster recovery under GEN 3.3.33. When an incident occurs the firm must investigate, contain it immediately, restore systems and data, remediate the exploited vulnerabilities and communicate internally and externally. The FSRA's survey put it plainly: incident plans that are not tested are less effective.

When and how must we notify the FSRA of a cyber incident?

GEN 3.5.18 requires the firm to notify the FSRA immediately, and in any event no later than 24 hours, including weekends and public holidays, after becoming aware of, or having information that reasonably suggests, a material Cyber Incident, using the prescribed form. "Cyber Incident" is defined in GLO without a materiality threshold; materiality matters only for notification. The guidance treats as material any incident that affects customer information or client assets, may cause material financial loss or reputational impact, disrupts critical functions, or involves malware, denial of service, unauthorised intrusion or insider threats. The general duty under GEN 8.10.6 to notify the FSRA immediately of significant matters continues to apply alongside.

The mechanics are in Notice FSRA/FCCP/22/2026 of 29 January 2026. Template A, the initial report, is emailed to incidents.fsra@adgm.com with the firm's lead supervisor or pooled supervision team copied. Template B, the progressive report, goes to the same mailbox at a frequency agreed case by case. Both templates are on the FSRA's Financial and Cyber Crime Prevention forms page and the IT Risk Management page. The notice also reminds firms of their separate duties: the 72-hour personal data breach notification under the Data Protection Regulations 2021, reporting to the Financial Intelligence Unit where relevant, and reporting to law enforcement. One incident can start three clocks.

What did the FSRA's 2025 cyber survey find?

Notice FSRA/FCCP/15/2026, issued on 22 January 2026, reports the FSRA's Q3 2025 cyber risk survey of 315 firms, of which 263 responded. Basic controls such as passwords, multi-factor authentication and anti-malware were widely adopted; advanced controls, penetration testing and red teaming less so, which the FSRA accepts as proportionate for smaller firms. Its recommendations are the ones quoted through this guide: board attention and assigned roles, complete inventories and vulnerability management, explicit provider terms, and tested incident plans. The FSRA framed its expectations as five pillars: framework and governance; identification and assessment; protection; monitoring and testing; detection, response and recovery. Use the same five headings in your own framework and the supervisor's reading becomes easier.

Key dates and deadlines

5 more dates in the table below.

Date Event
9 November 2020 Guidance on Governance Principles and Practices to Mitigate Cyber Threats and Crime (FSRA/FCPU/15/2020)
November 2023 Discussion Paper No. 1 of 2023 on IT Risk Management
20 November 2024 IT Risk Management Guidance published (VER01.201124)
4 February 2025 Notice 13 of 2025: standard IT and cyber incident reporting templates
30 April 2025 Consultation Paper No. 3 of 2025 proposes the Cyber Risk Management Rules
11 June 2025 Consultation closes
29 July 2025 FSRA Rules (Cyber Risk Management) 2025 announced; six-month transition
22 January 2026 Notice 15 of 2026: cyber risk survey findings and recommendations
29 January 2026 Notice 22 of 2026: revised incident templates, 24-hour notification restated; Dear SEO letter on the outsourcing thematic review
31 January 2026 GEN 3.5 in force; compliance required
Ongoing At least annual: framework review, risk assessment, testing of internet-facing systems, training, incident plan review

How GEN 3.5 relates to ISO 27001 and NIST CSF

There is no official FSRA mapping to either standard. What the FSRA has said, in the guidance to GEN 3.5.1, is that ISO/IEC 27000, NIST CSF and CIS Controls are acceptable bases for the framework, so the rules are designed to be met through ISO 27001, NIST CSF or an equivalent. The table below is an illustrative correspondence between the rule text and the well-known structure of ISO/IEC 27001:2022 and NIST CSF 2.0. Treat it as a starting point for your own mapping, not as an FSRA document.

GEN 3.5 area ISO/IEC 27001:2022 NIST CSF 2.0 function
3.5.1 and 3.5.3 framework, governing body, risk tolerance Clauses 4 to 6 and 9.3; A.5.1 to A.5.4 Govern
3.5.4 asset inventory and risk assessment 6.1.2 and 8.2; A.5.9, A.5.12 Identify
3.5.2 third-party cyber risk A.5.19 to A.5.23 Govern (supply chain), Identify
3.5.5 to 3.5.12 protection controls A.8 technological controls, A.7 physical controls, A.5.15 to A.5.18 access control Protect
3.5.13 training 7.2 and 7.3; A.6.3 Protect (awareness and training)
3.5.14 monitoring and testing 9.1 and 9.2; A.8.8, A.8.16 Detect, Identify (improvement)
3.5.15 to 3.5.17 detection, response, recovery A.5.24 to A.5.30 Detect, Respond, Recover
3.5.18 notification A.5.5 contact with authorities; A.6.8 event reporting Respond

Where the rules go beyond a generic ISO 27001 management system: a fixed 24-hour notification backstop; at least annual testing of internet-facing systems; at least annual training for all relevant staff; contractual terms with every ICT provider, not just outsourcing partners; and board-level ownership written into a rule. An ISO 27001 certificate is strong evidence for most of GEN 3.5, and it does not on its own demonstrate any of those five.

What are the supervisory consequences?

As at 8 November 2026 we found no published FSRA enforcement case specific to cyber. That should not be read as comfort. Consultation Paper No. 3 said the FSRA plans a thematic or similar review of how firms have implemented the rules, and that it is contemplating an annual Cyber Risk Management Return. The FSRA ran an outsourcing thematic review in 2025, and its 2025 annual report, as summarised by Pinsent Masons, recorded 38 regulatory actions and US$9.24 million in fines across all matters.

The FSRA's general powers under the Financial Services and Markets Regulations 2015 include financial penalties, public censure, conditions on or cancellation of a Financial Services Permission, and prohibitions on individuals. Vendor claims of specific cyber penalties are unsourced, and we have not repeated them. The realistic consequence of a weak framework in 2026 is a thematic finding, a supervisory requirement to remediate and, after an incident, a hard look at whether the board met GEN 3.5.3.

A readiness checklist

  1. Approve a written Cyber Risk Management Framework at board level, integrated with your risk management framework under GEN 3.3, with a recorded cyber risk tolerance and named roles for normal and crisis operations.
  2. Build a complete ICT asset inventory, classified by confidentiality and criticality, including third-party assets, and refresh it on every change.
  3. Run a cyber risk assessment at least annually that draws on test results and business impact, and minute the board's review of it.
  4. Review every ICT contract, cloud included, for incident notification, cooperation, verification and subcontractor terms, and record the due diligence.
  5. Evidence the baseline controls: anti-malware, network monitoring, least privilege and privileged access, multi-factor authentication on internet-facing and privileged access, patching by criticality, encryption, physical access.
  6. Train all relevant staff at least annually, new joiners promptly, privileged users specifically, and the board.
  7. Run a testing programme with at least annual penetration testing of internet-facing systems, remediation tracking and reporting to senior management.
  8. Write and test a Cyber Incident Response Plan integrated with business continuity and disaster recovery, reviewed at least annually and after any reportable incident.
  9. Put a 24-hour notification procedure in place that works at weekends and on public holidays, uses Templates A and B, copies the lead supervisor, and runs in parallel with the 72-hour data breach process.
  10. Review the framework at least annually with board sign-off, and keep the evidence ready for a thematic review or a future annual return.

Common mistakes

Treating GEN 3.5 as an IT project

The rule places ultimate responsibility on the governing body, requires it to set a tolerance, to receive reporting and to train. A framework written by the IT function and never seen by the board fails GEN 3.5.3 however good the controls are. Start with the board paper, not the firewall.

An asset inventory that stops at your own equipment

GEN 3.5.4 requires the inventory to include assets held by service providers and to record location and purpose. A list of laptops and servers misses the cloud tenancies, SaaS platforms and outsourced systems where most of the risk now sits, and the FSRA's survey called out incomplete inventories directly.

Assuming the outsourcing rules cover your ICT providers

GEN 3.5.2 is wider than the GEN 3.3 outsourcing rules. It covers every ICT service, including one-off work and cloud subscriptions that no one classed as outsourcing. If a contract has no incident notification, cooperation or verification clause, it does not meet the rule, whether or not the provider counts as an outsourcing partner.

A notification process that only works on weekdays

Twenty-four hours including weekends and public holidays is the rule. A process that depends on one person's inbox, or on a Monday morning meeting, will miss it. Decide in advance who assesses materiality, who signs Template A and who copies the supervisor, and test it out of hours.

An incident plan that has never been tested

GEN 3.5.17 requires the plan to be tested regularly and reviewed at least annually and after any reportable incident. The FSRA's own survey found untested plans less effective. A tabletop exercise once a year, minuted, with actions tracked, is the minimum evidence.

Confusing ISO 27001 certification with compliance

An ISO 27001 certificate covers most of GEN 3.5 and none of its fixed minimums by itself: the 24-hour clock, annual testing of internet-facing systems, annual training for everyone, terms with every ICT provider and board ownership. Map the rule to the standard and fill the five gaps rather than assuming the certificate answers the supervisor.

Frequently asked questions

Compliance has been required since 31 January 2026. The FSRA announced the Rules (Cyber Risk Management) 2025 on 29 July 2025 with a six-month transition, extended from the three months proposed in Consultation Paper No. 3 of 2025 after industry feedback. Notice 22 of 2026, issued on 29 January 2026, updated the incident reporting templates to match the rules two days before they took effect.

No. GEN 3.5 applies to FSRA Authorised Persons and, through the Market Infrastructure Rulebook, to Recognised Bodies. We found no separate Registration Authority cyber framework. Every ADGM entity that holds personal data is, however, subject to the Data Protection Regulations 2021, which require breach notification to the Commissioner of Data Protection without undue delay and, where feasible, within 72 hours.

The rule does not fix a numeric threshold. The guidance treats as material any incident that affects customer information or client assets, may cause material financial loss or reputational impact, disrupts critical functions, or involves malware, denial of service, unauthorised intrusion or insider threats. The definition of Cyber Incident itself has no materiality limit; materiality only governs whether you must notify.

Immediately, and in any event no later than 24 hours after becoming aware of, or having information that reasonably suggests, a material Cyber Incident. The clock runs at weekends and on public holidays. Use Template A for the initial report, emailed to incidents.fsra@adgm.com with your lead supervisor copied, and Template B for progress reports at the frequency the FSRA sets.

No. The FSRA names ISO/IEC 27000, NIST CSF and CIS Controls as acceptable bases and does not require certification to any of them. ISO 27001 is a good foundation and maps to most of the rule, but you still need to evidence the fixed minimums the rule adds: 24-hour notification, annual testing, annual training, ICT contract terms and board ownership.

Internet-facing systems must be tested at least annually under GEN 3.5.14, and the testing programme as a whole must be regular. The rule lists vulnerability assessments, scenario-based tests, penetration tests, bug bounties and red teaming as options. Findings must be prioritised, remediated and reported to senior management. The FSRA's 2025 survey found adoption of penetration testing and red teaming limited.

Probably. GEN 3.5.2 covers all ICT services, including cloud and one-off services, and requires contracts that oblige the provider to notify you of incidents, cooperate in remediation and allow verification. The final rules dropped a draft duty for providers to comply with your cyber requirements generally, and the FSRA has said on-site audit rights are not needed for every provider, so verification can be proportionate.

No. The guidance, published on 20 November 2024, is expressly non-binding. It describes desired outcomes and best practices across 15 chapters. GEN 3.5 is the binding rule and builds on it, so a framework that follows the guidance will find the rule easier to evidence, and supervisors are likely to read your framework against both.

Yes, if personal data is involved. The Data Protection Regulations 2021 require notification to the Commissioner of Data Protection without undue delay and, where feasible, within 72 hours, with data subjects informed where there is high risk. Notice 22 of 2026 reminds firms of this alongside FSRA notification, and of reporting to the Financial Intelligence Unit and law enforcement where relevant.

Key takeaways

  • GEN 3.5 has been binding on FSRA Authorised Persons and Recognised Bodies since 31 January 2026, and it is proportionate, not optional.
  • The board owns cyber risk under the rule: tolerance, reporting and training are its job, not the IT function's.
  • Five things go beyond a generic ISO 27001 system: the 24-hour clock, annual testing of internet-facing systems, annual training for all relevant staff, terms with every ICT provider, and board ownership in a rule.
  • One incident can start three clocks: 24 hours to the FSRA, 72 hours to the Commissioner of Data Protection, and FIU or law enforcement reporting where relevant.
  • The final rule text was not available to us; confirm rule numbers against the ADGM Rulebook before quoting them.

What if we are not in ADGM?

The ingredients of GEN 3.5 are not peculiar to Abu Dhabi: a framework owned by the board, a classified inventory of technology assets, proportionate controls, contractual control over service providers, regular testing and training, a tested response plan and a fixed window to tell the regulator. Financial regulators elsewhere express the same ideas under headings such as operational resilience, technology risk or outsourcing, and the FSRA's rule is a clear worked example of the class. We have not researched the equivalent provisions of the DFSA, the FCA, MAS or others for this guide, so we do not cite them; check your own rulebook for the notification window in particular, because it is the term most likely to be tested after an incident. Because GEN 3.5 is built to be met through ISO 27001, NIST CSF or CIS Controls, a firm that organises its cyber programme around one of those standards and maps each regulator's rule to it will find the same controls and evidence serve every jurisdiction.

Sources

  1. ADGM announcement, "ADGM's FSRA issues Cyber Risk Management Framework", 29 July 2025. https://www.adgm.com/media/announcements/adgms-fsra-issues-cyber-risk-management-framework (checked 8 November 2026)
  2. ADGM, IT Risk Management page (FSRA rules, guidance, notices and incident reporting). https://www.adgm.com/operating-in-adgm/it-risk-management (checked 8 November 2026)
  3. FSRA Consultation Paper No. 3 of 2025, Proposed Enhancements to Cyber Risk Management, 30 April 2025. https://assets.adgm.com/download/assets/Consultation+Paper+No+3+of+2025+Cyber+Risk+Management+Framework.pdf/e5bbf72c24c911f088e1e26659cc3b20 (checked 8 November 2026)
  4. FSRA Consultation Paper No. 3 of 2025, Appendix 3, Proposed Amendments to GEN (draft GEN 3.5 text and guidance). https://assets.adgm.com/download/assets/Appendix+3+Proposed+Amendments+to+GEN.pdf/e6033dda24c911f0b81ad6cf99b46a99 (checked 8 November 2026)
  5. FSRA, Information Technology Risk Management Guidance, 20 November 2024 (VER01.201124). https://assets.adgm.com/download/assets/Information+Technology+Risk+Management+Guidance+20241120.pdf/014f7430a71811efa4b7bae6ac7fc29c (checked 8 November 2026)
  6. FSRA Notice FSRA/FCPU/15/2020 and Governance Principles and Practices to Mitigate Cyber Threats and Crime, 9 November 2020. https://assets.adgm.com/download/assets/FCPU+Notice+No+15+of+2020+Notice+and+Principles.pdf/7aa5bd187b2f11ef9d7d7e18b289a17d (checked 8 November 2026)
  7. FSRA Notice 13 of 2025, IT and Cyber Incident Reporting, 4 February 2025. https://assets.adgm.com/download/assets/FSRA+Notice+13+of+2025+-+Information+Technology+and+Cyber+Incident+Reporting.pdf/b31aa2e2e2f611efb6ee769067822a45 (checked 8 November 2026)
  8. FSRA Notice FSRA/FCCP/22/2026, Updates to IT and Cyber Incident Reporting, 29 January 2026. https://assets.adgm.com/download/assets/Notice+FCCP+No+22+of+2026+Updates+to+Information+Technology+IT+and+Cyber+Incident+Reporting.pdf/c8f0d192fcfc11f0a151e2f9ff4b015c (checked 8 November 2026)
  9. FSRA Notice FSRA/FCCP/15/2026, Cyber Risk Survey Findings and Recommendations, 22 January 2026. https://assets.adgm.com/download/assets/FCCP+Notice+No+15+of+2026+Cyber+Risk+Survey+Findings+and+Recommendations.pdf/3113de1cf77711f0aa26965f5e1b9ba4 (checked 8 November 2026)
  10. ADGM Rulebook (Thomson Reuters), FSRA Rules (Cyber Risk Management) 2025, 29 July 2025 (not retrievable on 8 November 2026). https://en.adgm.thomsonreuters.com/rulebook/29-july-fsra-rules-cyber-risk-management
  11. ADGM Data Protection Regulations 2021 (consolidated) and ADGM Office of Data Protection, Data Breach Notifications page. https://adgm.com/operating-in-adgm/office-of-data-protection/data-breach-notifications (checked 8 November 2026)
  12. Norton Rose Fulbright, "Cyber risk management in the ADGM: an analysis of the new regulatory framework" and "Technology contracts in the ADGM: new requirements under the Cyber Risk Management Framework", August 2025. https://www.nortonrosefulbright.com/en/knowledge/publications/55179310/cyber-risk-management-in-the-adgm-an-analysis-of-the-new-regulatory-framework (checked 8 November 2026)
  13. ACA Group, "The FSRA raises the bar for cybersecurity risk management", 5 August 2025. https://www.acaglobal.com/industry-insights/the-fsra-raises-the-bar-for-cybersecurity-risk-management/ (checked 8 November 2026)
  14. Ronin Legal Consulting, "The ADGM's new Cyber Risk Management Framework: a closer look", 11 August 2025. https://roninlegalconsulting.com/the-adgms-new-cyber-risk-management-framework-a-closer-look/ (checked 8 November 2026)
  15. Pinsent Masons Out-Law, "Financial crime and operational resilience in ADGM regulator's sights", 24 July 2026, and FSRA Dear SEO letter, Outsourcing Thematic Review, 29 January 2026. https://www.pinsentmasons.com/out-law/news/financial-crime-operational-resilience-adgm-regulator-sights (checked 8 November 2026)
How Ordit helps

How Ordit helps

GEN 3.5 is, at heart, a demand for evidence: that the board owns cyber risk, that you know your assets and your providers, that controls exist and are tested, and that you can notify within a day. Ordit holds that evidence in the same register as the rest of your regulatory duties, so the cyber framework is one view of the firm's compliance rather than a separate binder, and the same approach works for any regulator's cyber rule.

From rulebook to evidenceHow this framework becomes a register you can prove, with people deciding at every step.
  1. 01Read the frameworkGEN 3.5 is held rule by rule as a set of obligations, alongside the IT Risk Management Guidance outcomes and the Data Protection Regulations 2021 breach duty, each with its frequency: at least annually for the framework review, risk assessment, testing and training, 24 hours for notification.
  2. 02Map every requirementMap every requirement to one register of obligations, controls and evidence alongside your regulatory duties. Your cyber policies are read against the rule, each control from GEN 3.5.5 to 3.5.12 is a record with an owner, and every ICT provider sits in a supplier record with its contract clauses, due diligence and review date.
  3. 03Name an owner for each gapA cloud contract without a notification clause, an internet-facing system with no test in the last twelve months or a board that has not set a cyber risk tolerance becomes a task with a person and a date.
  4. 04Link controls and evidenceLink controls and evidence once so they serve every framework. The multi-factor authentication control that answers GEN 3.5 is the same control your ISO 27001 auditor and your other regulators ask about. It is tested once for design and operation, its evidence is fingerprinted and held in the immutable event chain, and it is shown through a scoped auditor or regulator view or exported in open formats. Cyber scenarios run through the risk engine, with Monte Carlo output at P50, P90 and P95 and key risk indicators feeding the board report GEN 3.5.3 requires; incidents carry a materiality assessment, a 24-hour clock and a Template A and B record ready for your firm to send.
  5. 05Review as it changesReview as the framework changes, with a named person accepting, amending or rejecting every change. When the FSRA issues a new notice, revises a template or introduces the annual return it is contemplating, horizon scanning proposes the change to the obligations and controls it affects, and nothing moves until someone in your firm decides.
Where it lives in OrditEach requirement on the left, the record or view that answers it on the right.
GEN 3.5.1 cyber risk management framework
In OrditRegister of obligations: GEN 3.5 held rule by rule, each linked to policies, controls and evidence
GEN 3.5.3 governing body ownership and risk tolerance
In OrditRisk engine: cyber risk appetite, key risk indicators and board reporting, with decisions held in the immutable event chain
GEN 3.5.4 ICT asset inventory and annual risk assessment
In OrditRisk engine: cyber scenarios run by Monte Carlo to P50, P90 and P95 against the asset register, reviewed at least annually
GEN 3.5.5 to 3.5.12 protection controls
In OrditControls and testing programme: each control tested for design and operation, evidence with fingerprints
GEN 3.5.2 third-party cyber risk
In OrditSupplier and third-party record: due diligence, contract clauses on notification, cooperation and verification, review dates
GEN 3.5.13 and 3.5.14 training and resilience testing
In OrditControls and testing programme: annual training and penetration test cycles with owners, due dates and evidence
GEN 3.5.18 notification within 24 hours
In OrditIncidents: materiality assessment, 24-hour clock, Template A and B record prepared for the firm to send, exported in open formats
Changes to the rules, guidance and notices
In OrditHorizon scanning and pack updates: each change proposed, a named person accepts, amends or rejects

Ordit proposes; your people decide, and the record shows who decided what and when.

This guide is for information only. It reflects the position on 8 November 2026 and is not legal or regulatory advice.

Book a discovery call
More guides

Plain answers to the frameworks you are asked about.

GuideThe EU AI Act: a practical guide for regulated firms

The EU AI Act for regulated firms inside and outside the EU: scope, risk tiers, obligations, the 2 December 2027 deadline, penalties, ISO 42001 and GDPR.

18 minute readRead the guide
GuideISO 42001: a practical guide for regulated firms

What ISO/IEC 42001 requires, whether a regulated firm needs it, how it fits with supervisory expectations and the EU AI Act, and how to get certified.

19 minute readRead the guide
GuideISO 27001: a practical guide for regulated firms

What ISO/IEC 27001:2022 requires, how a regulated firm scopes and certifies an ISMS, and how it maps to supervisory cyber rules and data protection law.

18 minute readRead the guide
GuideCyber Essentials: a practical guide for regulated firms

What Cyber Essentials covers, when a regulated firm in or outside the UK should get it, what it costs, why firms fail and what applies instead.

16 minute readRead the guide