Ordit
Guide

ISO 27001: a practical guide for regulated firms

After reading this you will know what an information security management system has to contain, how it maps to your regulator's cyber rules, and what it takes to pass the certification audit.

Who this guide is for

Compliance officers and heads of risk at regulated firms who have to show a supervisor a cyber or information security framework and want to build it once, to a recognised standard. Founders preparing a licence application who know that systems and controls will be examined. Boards and senior managers who carry ultimate responsibility for cyber risk and want to understand what they are signing off. Technology leads and outsourced compliance providers asked by clients, counterparties and group parents for ISO 27001 evidence. The examples come from the UK and the Gulf, but the standard and the pattern of regulatory expectations are the same everywhere.

What is ISO 27001?

ISO/IEC 27001:2022 is the current edition of the international standard for information security management. It specifies the requirements for establishing, implementing, maintaining and continually improving an information security management system, and it is certifiable: an accredited certification body audits the ISMS and issues a certificate valid for three years, subject to annual surveillance.

ISO/IEC 27001:2022 is the current edition of the international standard for information security management.

An ISMS is not a product. It is the complete set of policies, processes, procedures, controls and records a firm uses to manage information security risk, tailored to its own assets, business and regulatory obligations. The standard runs on the Plan-Do-Check-Act cycle: assess risk and plan controls, implement and operate them, monitor, measure and audit, then correct and improve. The cycle repeats indefinitely; certification is a point on it, not the end of it.

How is the standard structured?

Clauses 4 to 10 are the management system backbone that every certified firm must have: context and interested parties (4), leadership and policy (5), risk assessment and treatment planning (6), resources, competence, awareness, communication and documented information (7), operational planning and control (8), monitoring, internal audit and management review (9) and continual improvement (10).

Annex A holds 93 reference controls in four groups: organisational (37), people (8), physical (14) and technological (34). They are not a checklist. Your risk assessment decides which apply, and the Statement of Applicability records that decision for every one of them, with a justification for each exclusion.

What changed in the 2022 edition?

The 2022 revision restructured Annex A from 14 categories and 114 controls to 4 groups and 93 controls, merging and modernising the rest. Eleven controls were new, covering threat intelligence, information security for cloud services, ICT readiness for business continuity, physical security monitoring, configuration management, information deletion, data masking, data leakage prevention, monitoring activities, web filtering and secure coding. Firms certified to the 2013 edition had to transition by October 2025, so every new certificate is now against the 2022 standard.

Does it apply to us?

ISO 27001 is voluntary everywhere. What is not voluntary for a regulated firm is the cyber framework its supervisor expects, usually written as outcomes rather than a named standard: proportionate to the firm, reviewed at least annually, owned by the board. The FSRA's GEN 3.5 is a useful worked example because its guidance lists the ISO/IEC 27000 family, the NIST Cybersecurity Framework and the CIS Critical Security Controls as frameworks a firm may build on. The UK's FCA expects adequate systems and controls for operational resilience, and the ICO treats ISO 27001 certification as evidence of appropriate measures under UK GDPR. ISO 27001 is therefore an obvious way to satisfy a supervisor, and the only common framework that comes with independent certification.

Beyond the rulebook, the drivers are the same in any market. Enterprise clients and group parents put ISO 27001 in their vendor due diligence. Cyber insurers want evidence of structured controls before they quote. Data protection law requires appropriate technical and organisational measures and prompt breach notification, and an ISMS is the standard way to evidence the measures.

If this is true of your firm Then
You hold a licence from a financial regulator A cyber risk framework is almost certainly required. An ISO 27001 ISMS is an accepted basis, with your regulator's specific rules added on top.
You are a regulated firm's service provider or group company The firm's outsourcing and third-party rules will reach you, and ISO 27001 is the evidence most often requested.
You handle client assets, customer data or confidential deal information Expect ISO 27001 to appear in client, counterparty and insurer questionnaires.
You are part of a larger group The group ISMS may already cover you; check its scope statement before you build another.
You are applying for a licence or permission A documented, risk-based security framework strengthens the systems and controls section of your application.

What does ISO 27001 require?

What does Clause 4 ask you to understand about your context?

Before building anything you have to state what you are protecting, from what, and for whom. External context covers the regulatory landscape (your supervisor's cyber and outsourcing rules, data protection law in each jurisdiction you touch), the threat environment for your sector, client expectations and contractual obligations. Internal context covers your structure, strategy, technology estate, existing security capability, culture and risk appetite.

Before building anything you have to state what you are protecting, from what, and for whom.

You then list interested parties and their requirements: customers, employees, the regulator, the data protection authority, shareholders, suppliers and partners. Finally you set the ISMS scope: which entities, locations, systems and information assets are inside. For most small firms the scope is the whole firm. A narrower scope is permitted but must be meaningful and defensible, and an auditor will test the boundary.

What does leadership have to do under Clause 5?

Clause 5 requires visible, demonstrable leadership commitment. Top management must set the information security policy, assign and communicate roles and authorities, resource the ISMS and take part in management review. For a regulated firm this lines up with what supervisors increasingly write into rules: GEN 3.5, for example, places ultimate responsibility for cyber risk on the governing body and senior management, requires them to set risk tolerance, receive regular reporting and participate in training. The chief executive and the board will be interviewed at the certification audit, and their familiarity with the ISMS is obvious within minutes.

How does Clause 6 handle risk assessment and treatment?

Risk assessment is the engine of the ISMS. It decides which controls you need, in what order, and what residual risk you accept. Identification means listing the realistic threats to your information assets, the vulnerabilities they could exploit and the impact if they did. Analysis assigns likelihood and impact to produce a risk level, using a method that is consistent and repeatable. Evaluation compares each risk with your acceptance criteria.

Treatment gives you four options: treat the risk with controls, tolerate it with documented justification, transfer it through insurance or outsourcing, or terminate the activity that creates it. The output is a risk treatment plan and the Statement of Applicability, which records for every Annex A control whether it applies, whether it is implemented and why anything is excluded. Supervisors often add a cadence: GEN 3.5 requires a cyber risk assessment at least annually, drawing on threat information, control effectiveness, test results and business impact.

What support does Clause 7 require?

An ISMS needs an owner with time and budget, people with the competence to run it, a workforce that knows the policy and its own responsibilities, and controlled documentation with versioning, approval and review cycles. Regulators sharpen the awareness point into rules: at least annual training for all relevant employees, new joiners within a reasonable period, targeted training for privileged users is the GEN 3.5 formulation. Keep the attendance and completion records, because both the auditor and the supervisor will ask.

What does Clause 8 expect in operation?

Clause 8 requires you to do what you planned: run the risk assessments at planned intervals and on significant change, execute the treatment plan, operate the controls and manage change to the ISMS through a defined process. Significant change includes new systems, new threats, reorganisation and incidents that expose risks you had not seen.

How do you prove it works under Clause 9?

Three mechanisms. Monitoring and measurement tracks control effectiveness against defined metrics: incident rates, vulnerability scan results, patching times, training completion, phishing simulation outcomes. Internal audit assesses conformity and effectiveness across the whole scope over the audit cycle, and must be objective, so nobody audits their own work; a small firm can use an external auditor for the internal audit role. Management review is senior leadership examining audit results, corrective actions, stakeholder feedback, risk results and improvement opportunities, with documented decisions.

What does Clause 10 mean by continual improvement?

When a nonconformity surfaces, through audit, incident or monitoring, you investigate the root cause, correct it and verify the correction worked. Beyond that the ISMS must show it improves proactively, using trends and changing circumstances rather than waiting for failures.

What are the 93 Annex A controls?

Organisational controls (A.5, 37 controls) are the governance layer: policies, roles, threat intelligence, asset inventory and classification, access and identity management, supplier and cloud security, incident management, business continuity, legal and regulatory requirements, privacy and independent review.

People controls (A.6, 8 controls) cover screening, employment terms, awareness and training, disciplinary process, responsibilities after termination, confidentiality agreements and remote working. Physical controls (A.7, 14 controls) cover perimeters, entry, secure areas, physical monitoring, environmental protection, clear desk and screen, equipment, off-site assets, storage media, utilities, cabling, maintenance and disposal.

Technological controls (A.8, 34 controls) cover endpoints, privileged access, authentication, malware, vulnerability and configuration management, deletion, masking, leakage prevention, backup, redundancy, logging and monitoring, network security and segregation, web filtering, cryptography, the secure development lifecycle, security testing, outsourced development, separation of environments, change management and test data.

Not every control applies to every firm. A 30-person advisory firm and a 200-person exchange operator will have very different profiles, and both can be certified. The skill is in knowing which controls are universally expected, which are commonly excluded with good reason, and how to implement each proportionately rather than at enterprise scale.

Special considerations for regulated firms

A regulated firm that builds a textbook ISO 27001 ISMS will have most of its supervisor's cyber rules covered and should check the places where rules are more specific than the standard. GEN 3.5 illustrates the pattern. Notification: the FSRA must be told immediately, and in any event within 24 hours including weekends and public holidays, of a material cyber incident, using prescribed templates, while the 72-hour data breach clocks under the ADGM Data Protection Regulations 2021 and UK GDPR run in parallel. Testing: internet-facing systems tested at least annually, findings remediated and reported to senior management. Training: at least annual for all relevant staff, targeted for privileged users. Third parties: due diligence and contract terms with every ICT provider, including cloud and one-off services, covering incident notification, cooperation and verification, with the firm remaining fully responsible. Governance: the board's ownership of cyber risk and its tolerance written into the framework. Whatever your regulator, find its version of these five themes and write each into the ISMS as an explicit control.

A typical implementation timeline

The ranges below are typical and indicative. Your own timeline depends on size, number of sites, technology complexity, current maturity and how much time your people can give it.

Firm profile Typical time to certification-ready What stretches it
Small: roughly 20 to 50 staff, one site, simple estate 3 to 6 months Starting from very low maturity
Mid-sized: roughly 50 to 200 staff 6 to 9 months Several offices, diverse technology, regulated-industry expectations
Large: 200 or more staff, several locations 9 to 15 months Scope complexity, physical security assessments per site

Within those ranges, the active implementation work for a small firm typically takes 8 to 12 weeks, with the certification audit following 4 to 6 weeks later. Afterwards expect an annual surveillance audit covering part of the scope each year, and a full recertification audit at the end of the three-year cycle.

How it relates to other frameworks

Framework Relationship to ISO 27001
Supervisory cyber rules (FSRA GEN 3.5 as the example) Usually framework-agnostic; GEN 3.5 guidance names the ISO/IEC 27000 family as an acceptable basis. Illustratively, framework and governing body rules sit in clauses 4 to 6 and 9.3 and A.5.1 to A.5.4; inventory and assessment in 6.1.2, 8.2, A.5.9 and A.5.12; third parties in A.5.19 to A.5.23; protection in A.8, A.7 and A.5.15 to A.5.18; training in 7.2, 7.3 and A.6.3; monitoring and testing in 9.1, 9.2, A.8.8 and A.8.16; detection, response and recovery in A.5.24 to A.5.30; notification in A.5.5 and A.6.8. No official mapping exists.
Supervisory IT risk guidance Non-binding "how" documents such as the FSRA's IT Risk Management Guidance set desired outcomes across governance, third parties, asset and data lifecycle, resilience, access, cryptography and algorithm-driven solutions. Use them to calibrate control depth.
GDPR, UK GDPR and local data protection law Require appropriate technical and organisational measures and breach notification, typically within 72 hours. The ISMS evidences the measures; it does not cover lawful basis, data subject rights or impact assessments, which need separate privacy governance.
ISO/IEC 42001:2023 Same harmonised structure, extended to AI-specific risk. Firms with ISO 27001 typically reuse 40 to 50 percent of their governance infrastructure when adding an AIMS. See our ISO 42001 guide.
NIST Cybersecurity Framework 2.0 Voluntary and widely accepted by regulators as a basis. Its Govern, Identify, Protect, Detect, Respond and Recover functions map comfortably onto an ISMS; the difference is certification.
Cyber Essentials (UK) Five baseline technical controls, self-assessed or tested, relevant to firms with UK operations or UK government work. A useful starting point and a subset of what an ISMS covers. See our Cyber Essentials guide.
SOC 2 The assurance report US clients expect. Significant control overlap, so a certified firm can usually add SOC 2 incrementally if the client base requires it.

Which approach, and what does it cost?

Firms take one of three routes. Doing it yourself works where you have strong internal security expertise and time; the risk is inefficiency, because first-time implementers tend to over-engineer some areas, under-engineer others and discover late that their documentation or risk method will not satisfy an auditor. Consultant-led implementation brings experience and speed; the risk is an ISMS built for you rather than with you, which nobody in the firm can maintain once the engagement ends, so insist on capability transfer. Platform-supported implementation puts obligations, controls, evidence and review dates into one system of record, which matters most after certification, when keeping the ISMS alive is the problem rather than building it.

Cost has four parts. Internal time is the largest: someone must own the ISMS, attend the workshops, make the risk decisions and coordinate control owners, typically a part-time commitment for one or two people during implementation. External expertise, if used, for gap analysis, risk facilitation, documentation, internal audit and audit preparation. Technology to close control gaps such as endpoint protection, backup and vulnerability scanning, much of which a regulated firm already has. And certification body fees for Stage 1, Stage 2 and annual surveillance, which scale with the size of the firm and the scope. For a UK small or mid-sized firm the all-in figure has typically fallen in the low tens of thousands of pounds; elsewhere, obtain local quotes, since fees vary by certification body and market.

A readiness checklist

  1. Define the ISMS scope in writing: entities, sites, systems and information assets, with the boundary justified.
  2. Run a gap analysis against clauses 4 to 10 and all 93 Annex A controls, recording what exists, what needs creating and the effort involved; most firms are further along than they think and lack only the formalisation.
  3. Agree and document the risk methodology, then build the asset inventory, identify threats and vulnerabilities, rate the risks and decide treatment.
  4. Produce the Statement of Applicability and the risk treatment plan.
  5. Write the mandatory documented information and the core policies: information security, access control, acceptable use, classification, incident response, business continuity, supplier security, and the risk method itself. Keep them short enough to be read.
  6. Implement the controls in priority order, starting with asset inventory and access management because so much else depends on them, and add your regulator's specifics as explicit controls: notification deadlines and templates, testing cadence, training cadence and ICT provider contract terms.
  7. Deliver awareness training to everyone and role-specific training to control owners, and keep the records.
  8. Complete one full internal audit cycle across the whole scope, using someone independent of the processes audited, and close the findings.
  9. Hold a management review with the board or chief executive present, covering the required inputs, and minute the decisions.
  10. Choose an accredited certification body, book Stage 1 and Stage 2, and plan the surveillance calendar for the three years that follow.

Common mistakes

Treating it as a documentation project

Impressive policies, controls that do not operate, a risk assessment that describes a firm that does not exist, and staff who have never read any of it. Auditors interview people and test controls, and the pattern is visible immediately. Build from operations outward: formalise and improve what you actually do, then document the reality. A policy that claims a control you do not run is a nonconformity, not a control.

Over-engineering the risk assessment

Elaborate scoring matrices, exhaustive asset registers and hundreds of risk entries produce something accurate on the day and abandoned within months. Keep it proportionate. A 50-person firm does not need a 500-line register. Focus on the risks that would genuinely hurt the business and use a method your team can maintain between audits.

Delegating everything to IT

Information security is a business risk discipline spanning HR, legal, facilities, procurement and the board. An ISMS owned entirely by IT misses the organisational, people and physical controls and fails on governance. Distribute ownership: HR owns people controls, facilities owns physical, procurement owns suppliers, the board owns policy and risk acceptance. That distribution is also what regulators now write into their rules.

Neglecting the management system clauses

Excellent firewalls, no management review. Strong access controls, no internal audit. The audit then fails on clauses 4 to 10 rather than on technology. Give the governance mechanisms equal weight; they are what turn a set of controls into a system that still works next year.

Building for the auditor rather than the business

An ISMS designed to pass a three-day visit rarely changes how anyone works. Design it to solve your actual problems: your real risks, your real vulnerabilities, the way your firm actually operates. A useful ISMS passes the audit as a side effect.

Underestimating the ongoing commitment

Certification is a project; keeping it is an operating rhythm. Firms that celebrate and move on find policies past review, registers stale and evidence sporadic by the first surveillance audit. Schedule quarterly risk reviews, annual policy reviews and monthly control checks as business as usual, and give someone clear ownership of the calendar.

Frequently asked questions

Almost certainly not by name. Supervisors typically require a cyber or information security framework proportionate to the firm, reviewed regularly and owned by the board, and many list the ISO/IEC 27000 family, NIST CSF and CIS Controls as acceptable bases; the FSRA's GEN 3.5 does exactly that. ISO 27001 is therefore a recognised route, and the only one of those with third-party certification.

Typically 3 to 6 months for a small single-site firm, 6 to 9 months for a mid-sized firm and 9 to 15 months for a large or multi-site one. For a small firm the active implementation work is usually 8 to 12 weeks, with the certification audit following 4 to 6 weeks later. Existing good practice that only needs formalising shortens the timeline; low maturity and complex technology lengthen it.

Four lines: internal time, any external expertise, technology to close control gaps, and certification body fees for Stage 1, Stage 2 and annual surveillance. Fees scale with the size of the firm and the scope. In the UK a small or mid-sized firm's all-in cost has typically been in the low tens of thousands of pounds; elsewhere, obtain quotes from accredited bodies operating in your market.

Yes. The standard is written to scale, and controls and documentation are meant to be proportionate to size and risk. A 20-person firm does not need enterprise-grade controls. Small firms often certify faster than large ones because there is less complexity to manage, provided someone owns the ISMS and the board engages.

It is not a pass-or-fail event. The auditor raises major or minor nonconformities. Minor ones need a corrective action plan and are checked at the next surveillance audit; they do not block certification. Major ones must be resolved before the certificate is issued, and the certification body gives you time to do so. With a proper internal audit beforehand, majors are uncommon.

Most of them. The management system clauses and Annex A controls address framework, governance, inventory, risk assessment, protection, training, monitoring, testing, response and recovery. Add the specifics your rulebook states explicitly, which under GEN 3.5 means 24-hour notification of material incidents, at-least-annual testing of internet-facing systems, annual training for all relevant staff and contract terms with every ICT provider.

It evidences the "appropriate technical and organisational measures" those regimes require, and many Annex A controls on access, encryption, incident management and suppliers support those duties directly. It does not cover lawful basis, data subject rights, impact assessments or breach notification timing, which need separate privacy governance built on the security foundation.

Regular, not heavy: annual risk and policy reviews, internal audits, management review, continuous evidence collection and preparation for the surveillance audit. For a small firm that is a few focused hours a month plus audit preparation. The risk is drift, so put the review dates into a system that tracks them rather than relying on memory.

They serve different audiences. ISO 27001 is the recognised certification in the UK, the EU, the Gulf and most international markets. SOC 2 is what US clients usually ask for. The underlying controls overlap heavily, so a firm with one can add the other incrementally. For most regulated firms outside the US, ISO 27001 is the starting point.

Key takeaways

ISO/IEC 27001:2022 is the certifiable standard for an information security management system: clauses 4 to 10 plus 93 reference controls in Annex A, selected by risk and recorded in the Statement of Applicability. No regulator requires it by name, but supervisors require a cyber framework and commonly accept the ISO/IEC 27000 family as its basis, with their own notification, testing, training, provider contract and board ownership rules added explicitly. Certification typically takes 3 to 15 months, then runs on a three-year cycle with annual surveillance. The implementations that fail are built for the auditor, delegated to IT, or left to drift after the certificate arrives.

Sources

  1. ISO/IEC 27001:2022, Information security, cybersecurity and privacy protection, Information security management systems, Requirements: https://www.iso.org/standard/27001 (the ISO site blocks automated fetching; edition confirmed by reference, 8 November 2026)
  2. 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)
  3. ADGM FSRA, IT Risk Management page (rules, guidance, notices, incident reporting templates): https://www.adgm.com/operating-in-adgm/it-risk-management (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; final rule text sits in the ADGM Rulebook)
  5. 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)
  6. FSRA, Information Technology Risk Management Guidance, 20 November 2024: https://assets.adgm.com/download/assets/Information+Technology+Risk+Management+Guidance+20241120.pdf/014f7430a71811efa4b7bae6ac7fc29c (checked 8 November 2026)
  7. ADGM Data Protection Regulations 2021 (consolidated): https://assets.adgm.com/download/assets/ADGM+Data+Protection+Regulations+2021+Updated.pdf/146aa34858b011efb99a36e29b0f3a63 (checked 8 November 2026)
  8. NIST Cybersecurity Framework: https://www.nist.gov/cyberframework (checked 8 November 2026)
  9. ICO, A guide to data security (UK GDPR): https://ico.org.uk/for-organisations/uk-gdpr-guidance-and-resources/security/a-guide-to-data-security/ (checked 8 November 2026)
How Ordit helps

How Ordit helps

The mistakes in this guide share a cause: the ISMS lives in documents, the controls live in systems, the regulator's rules live in a rulebook, and nothing connects them, so the firm cannot show at any moment which control answers which duty or whether it ran. Ordit puts ISO 27001 and the firm's regulatory duties into one register, so a control and its evidence are recorded once and answer the standard, the supervisor and the auditor together.

From rulebook to evidenceHow this framework becomes a register you can prove, with people deciding at every step.
  1. 01Read the frameworkOrdit reads ISO/IEC 27001 clause by clause and all 93 Annex A controls, then reads your security policies against them, with automated gap analysis showing which clauses, controls and regulatory rules each policy answers and which it leaves open.
  2. 02Map every requirement to one registerEach clause and control sits in the register of obligations beside your regulator's cyber, outsourcing and data protection rules, so the Statement of Applicability, the supervisory framework and the breach notification duties are one view rather than three documents.
  3. 03Name an owner for each gapEvery unimplemented control, untested procedure and unreviewed supplier becomes an item with a named owner and a date, tracked to closure, with the information security risks on the risk engine linked to the controls that treat them and key risk indicators that show drift before the auditor does.
  4. 04Link controls and evidence onceA penetration test report, an access review or a training record is attached once, fingerprinted, and serves ISO 27001, your regulator's rules and your clients' questionnaires simultaneously, with a scoped auditor view and exports in open formats for Stage 1, Stage 2 and surveillance.
  5. 05Review as the framework changesHorizon scanning pushes changes to the standard, to your rulebook and to supervisory notices to the controls they affect, and a named person accepts, amends or rejects every change, with the decision written to the immutable event chain.
Where it lives in OrditEach requirement on the left, the record or view that answers it on the right.
Clause 4.3 ISMS scope and context
In OrditRegister of obligations: the standard's clauses and the firm's cyber, outsourcing and data protection duties side by side, with scope recorded per entity
Clause 5.2 information security policy and Annex A 5.1
In OrditPolicies read against duties with automated gap analysis, showing which clauses, controls and regulatory rules each policy answers and which it leaves open
Clause 6.1.2 risk assessment
In OrditRisk engine: information security risks linked to obligations, policies and controls, with key risk indicators and Monte Carlo scenarios (P50, P90, P95) for the risks worth quantifying
Clause 6.1.3 Statement of Applicability
In OrditControls and testing programme: every Annex A control marked applicable or excluded with its justification, test schedule and results, exportable in open formats for the auditor
Annex A 5.19 to 5.23 supplier relationships and cloud services
In OrditSupplier and third-party record: due diligence, contract terms, incident notification duties and review dates for every ICT provider
Annex A 5.24 to 5.28 incident management
In OrditIncidents: detection, containment, root cause and regulatory notification deadlines tracked against each incident, written to the immutable event chain
Clause 9.2 internal audit and 9.3 management review
In OrditScoped auditor view: controls, tests and fingerprinted evidence open to the internal or certification auditor for a limited time, with management review decisions recorded
Clause 10 improvement and rule changes
In OrditHorizon scanning and pack updates: changes to the standard or your regulator's rulebook pushed to the affected controls for a named person to accept, amend or reject

People decide; Ordit proposes, organises and remembers.

This guide is informational. 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
GuideADGM cyber risk management (FSRA GEN 3.5): a practical guide

FSRA GEN 3.5 cyber risk rules for ADGM firms, in force since 31 January 2026: governance, controls, suppliers, testing and 24-hour incident notification.

17 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
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