/

  / ISO 27001 Certification Cost in 2026: Full Breakdown

ISO 27001 Certification Cost in 2026: Full Breakdown

Most companies pursuing ISO 27001 certification cost analysis for the first time will spend between $10,000 and $50,000 in year one, and far less than half of that goes to the auditor. A 50-person SaaS company typically pays $10,000 to $22,000 in certification body fees alone, then doubles or triples that figure in implementation work, tooling, and internal hours before the Stage 2 audit even begins. The wide range exists because ISO 27001 certification cost is not a price tag; it is the sum of a dozen separate decisions: your scope, your security maturity, your certification body, and whether you build the ISMS yourself, hire a consultant, or run it through a compliance automation platform.

This article breaks down every one of those costs, stage by stage and region by region, including the ones that never appear in vendor quotes.

ISO 27001 Certification Cost

What Determines ISO 27001 Certification Cost?

Six variables drive almost all of the variance between a $10,000 certification and a $150,000 one.

Company Size and Employee Count

Headcount is the single biggest cost driver because certification bodies calculate audit days (mandays) primarily based on the number of people working within the scope of your Information Security Management System (ISMS). The calculation is not arbitrary: accredited bodies follow the audit time tables in ISO/IEC 27006, which means a 20-person company and a 200-person company will receive structurally different quotes no matter how hard they negotiate. More employees also means more interviews, more evidence sampling, and more Annex A controls applied across more people.

Scope and Complexity of the ISMS

Scope is the variable you actually control. Your Statement of Scope defines which business units, systems, products, and locations fall inside the ISMS. A scope limited to one product line and the engineering team that runs it costs dramatically less to implement and audit than a whole-of-company scope. Complexity compounds this: bespoke infrastructure, regulated data types, and heavy third-party dependency chains all add controls, evidence, and audit time.

Number of Physical and Cloud Locations

Each physical site within scope can require its own audit visit, with travel costs on top. Multi-site organisations can reduce this through sampling (more on the square root rule later), but every additional location still adds something. Cloud environments count too: multiple cloud providers, regions, and tenancy models expand the technical scope auditors must cover, even when no travel is involved.

Existing Security Maturity

A company that already runs access reviews, maintains an asset inventory, and documents its incident response process is buying a much shorter journey than one starting from a blank page. The gap analysis exists precisely to price this difference. Organisations already aligned to SOC 2, NIST CSF, or Cyber Essentials Plus typically reuse 50 to 70 percent of their existing controls and evidence, which translates directly into lower implementation cost.

Choice of Certification Body

Certification bodies are not interchangeable on price. Large international names like BSI, Bureau Veritas, LRQA, and DNV charge premium day rates, often 30 to 50 percent above smaller accredited bodies, and their brand carries weight with enterprise procurement teams. What matters most is accreditation: a certificate issued by a body accredited by UKAS, ANAB, or another IAF (International Accreditation Forum) member carries international recognition. An unaccredited certificate is cheaper and close to worthless in serious sales conversations.

Internal vs. External Implementation Approach

The final driver is who does the work. Internal teams cost salary hours. Consultants cost fees. Platforms cost subscriptions. Each approach lands at a very different total, which is why this article dedicates a full section to it below.

Reach SOC 2 Compliance in 6 Weeks or Less

Schedule Your Free SOC 2 Assessment Today

Average ISO 27001 Certification Cost Ranges

The ranges below cover total first-year cost: implementation, tooling, and certification audits combined. They assume an accredited certification body and a sensibly defined scope.

Cost for Small Businesses and Startups (1–50 Employees)

A focused startup with a single product, cloud-native infrastructure, and a tight scope can realistically certify for $10,000 to $35,000 all-in. Lean implementations using templates or an automation platform sit at the bottom of that range. UK micro-businesses can find UKAS-accredited audit fees starting around £6,250, with day rates near £1,250.

Cost for Mid-Sized Organizations (50–250 Employees)

This is where most certifications happen, and where costs spread widest. Expect 8 to 12 initial audit days, $30,000 to $80,000 in total first-year spend, and a six to nine month timeline. Multiple departments, more mature customer requirements, and the first real multi-team coordination overhead all show up in the budget.

Cost for Large Enterprises (250+ Employees)

Enterprise certifications routinely exceed $100,000 in year one once you include program management, multiple sites, and large-scale audits. The audit fee alone can pass $50,000 for complex, multi-site scopes. At this scale, the internal time investment, covered under hidden costs below, often outweighs every external invoice.

ISO 27001 Cost Breakdown by Stage

Here is where the money actually goes, in roughly the order you will spend it.

Cost of Purchasing the ISO 27001 Standard

The official ISO/IEC 27001:2022 document costs CHF 155 (roughly $170) from the ISO store. Most teams also buy ISO 27002, the implementation guidance for the Annex A controls, for a similar amount. Budget $300 to $400 for both. Do not skip this purchase: implementing against second-hand summaries of the standard is a common source of audit findings.

Gap Analysis Costs

A consultant-led gap analysis before committing to anything else runs $2,000 to $10,000 depending on scope, while platform-based readiness assessments are often bundled into the subscription. The output, a clear map of where you stand against every clause and control, is what makes the rest of the budget predictable.

ISMS Implementation Costs

This is the largest and most variable line item: building the risk assessment, the risk treatment plan, the Statement of Applicability (SoA), and operationalizing the controls you have selected. Done internally, it consumes 200 to 600 hours of staff time over four to eight months. Done with consultants, expect $10,000 to $50,000 in fees for a typical SMB.

Documentation and Policy Development Costs

ISO 27001 requires a defined set of documented policies and procedures. Template toolkits cost $500 to $2,000 and save weeks. Consultant-drafted documentation runs $5,000 to $15,000. Writing everything from scratch internally is free on paper and expensive in reality.

Employee Training Costs

Security awareness training for all in-scope staff costs roughly $10 to $50 per employee per year via standard platforms. Formal role-based training, such as internal auditor or implementer courses, costs $500 to $2,000 per person. A Lead Auditor course, useful if you want internal audit capability in-house, sits at the top of that range.

Security Tools and Software Costs

Most organisations need to fill at least some tooling gaps: endpoint management, MDM, vulnerability scanning, logging and monitoring, password management. Budget $5,000 to $20,000 annually depending on what you already run. A GRC platform or compliance automation tool adds $7,000 to $30,000 per year on top, if you go that route.

We’ve previously written about the cost of Vanta.

Penetration Testing and Vulnerability Assessment Costs

ISO 27001 does not strictly mandate a penetration test, but auditors expect to see technical vulnerability management in practice, and most certified companies run one. A scoped external penetration test costs $4,000 to $15,000; automated vulnerability assessment tooling runs $1,000 to $5,000 per year.

Pro Tip: Axipro Offers

As implementation partners, Axipro can offer up to 30% off popular compliance automation platforms such as Vanta and Drata.

Audit Cost Breakdown

Internal Audit Costs

The standard requires a completed internal audit before certification. Outsourcing it to an independent consultant costs $2,000 to $8,000. Doing it internally requires a trained auditor who is independent of the ISMS they audit, which is genuinely difficult in companies under 50 people. Most small organisations outsource this one.

Stage 1 Audit Costs

The Stage 1 audit is a documentation readiness review, typically one to two audit days, often conducted remotely. At prevailing day rates of $1,500 to $2,200, expect $1,500 to $4,500. Its job is to confirm you are ready for Stage 2 and flag anything that would cause a failure.

Stage 2 Certification Audit Costs

The Stage 2 audit is the full assessment: interviews, evidence sampling, and control testing against your SoA. For a 50-person company, the combined Stage 1 and 2 effort typically lands at 8 to 10 audit days, putting certification body fees at $12,000 to $22,000 before travel. Smaller scopes can come in at $5,000 to $10,000.

Surveillance Audit Costs (Years 2 and 3)

Certification runs on a three-year cycle. In years two and three, the certification body returns for a surveillance audit, typically one-third to one-half the duration of the initial audit, focused on core clauses, internal audit, management review, and a sample of controls. Budget $3,000 to $10,000 per year for most SMBs.

Recertification Audit Costs (Year 3)

At the end of year three, a recertification audit repeats most of the Stage 2 scope. Price it at 60 to 80 percent of the original Stage 2 fee. Companies that maintained their ISMS well find it routine; companies that let the system gather dust effectively pay for implementation twice.

ISO 27001 Cost by Implementation Approach

DIY with an Internal Team

Lowest cash outlay, highest time cost. You pay for the standard, a template toolkit, training, tooling gaps, and the audits. The real price is 300 to 600 hours of staff time, and the real risk is a failed or delayed audit caused by inexperience with auditor expectations.

Hiring an ISO 27001 Consultant

Consultants charge $150 to $300 per hour, or $15,000 to $50,000 for a full implementation engagement. A vCISO retainer ($3,000 to $10,000 per month) is a common variant that spreads the cost and keeps expertise available after certification. Consultants shine on complex scopes, awkward legacy environments, and organisations with no internal security function.

Using a Compliance Automation Platform

Platforms automate evidence collection from your cloud stack, ship policy templates, and run continuous control monitoring. Subscriptions for ISO 27001 typically run $7,000 to $30,000 per year depending on company size and the number of frameworks. They compress timelines dramatically for cloud-native companies and do much less for organisations with significant on-premise or physical scope.

Hybrid Approach

The most common pattern in practice: a platform for evidence automation and continuous monitoring, plus a fractional consultant for the judgment-heavy work, risk assessment, scoping, internal audit, and audit accompaniment. It usually beats either pure approach on total cost of ownership for SMBs.

 

Hidden Costs of ISO 27001 Certification

The line items above are the visible budget. These are the ones that surprise people.

Lost Productivity and Internal Time Investment

Even with consultants and platforms, your team still attends interviews, remediates findings, documents processes, and sits in audits. For a mid-sized company, expect 200 to 500 internal hours in year one. At a blended $75 per hour, that is $15,000 to $37,500 of payroll that never appears on a compliance invoice.

Re-Audit Fees After a Failed Audit

Major nonconformities at Stage 2 do not usually void the whole audit, but they do require remediation and a follow-up assessment, typically one to three additional audit days plus fees, at $1,500 to $6,000. Worse is the delay: a three-month slip can cost deals that were waiting on the certificate.

Platform Lock-In and Subscription Growth Fees

Automation platforms price by headcount and framework count, so the subscription grows as you do. Migrating years of evidence and control mappings to another platform is painful enough that few companies ever do it. Model the three-year subscription cost, not the year-one promotional price.

Multi-Site Audit Add-Ons

Every sampled site adds audit days, travel, and accommodation to the certification body invoice. Organisations frequently discover these travel recharges only when the first invoice arrives, because quotes are often presented exclusive of expenses.

Ongoing Maintenance and Continuous Improvement

ISO 27001 is a management system, not a plaque. Budget ongoing internal audits, management reviews, risk assessment refreshes, training renewals, and control operation at $5,000 to $25,000 per year in mixed internal and external costs. Certificates lapse for companies that treat year one as the finish line.

ISO 27001 Costs by Region

ISO 27001 Certification Cost by Region

Audit day rates and consultant fees vary substantially by market, even though the standard and the audit-day tables are global.

United States

The most expensive market for both auditors and consultants, with ANAB-accredited bodies charging $1,500 to $2,200 per audit day. US buyers more often pair ISO 27001 with SOC 2, which changes the budget conversation entirely (see bundling, below).

United Kingdom

UKAS-accredited audits average around £1,250 per day in 2026, with micro-business certification audit packages starting near £6,250. The UK has a deep consultant market, which keeps implementation pricing competitive.

European Union

Rates broadly track the UK, with national accreditation bodies (DAkkS in Germany, COFRAC in France) all operating under the same IAF umbrella. GDPR records of processing requirements make ISO 27001 a common board-level mandate, and certificates from any EU-accredited body are recognised across the bloc.

Australia

JAS-ANZ-accredited bodies price slightly above European equivalents once travel is included, since multi-site Australian scopes often involve significant distances. Government supply chains increasingly expect certification, supporting both demand and prices.

Canada

Pricing sits just under the US market. Many Canadian companies use US-based certification bodies, and cross-border audit delivery (often remote) keeps rates aligned.

India

The cheapest major market by far: full certifications for small scopes can complete for under $10,000. The critical check is accreditation. Certificates from non-IAF bodies sell cheaply in this market and fail procurement review with international customers.

Reach SOC 2 Compliance in 6 Weeks or Less

Schedule Your Free SOC 2 Assessment Today

When Do You Pay? ISO 27001 Cost Cash Flow Timeline

The spend is front-loaded but not simultaneous.

  • Months one to two: the standard, gap analysis, and any platform or consultant onboarding (10 to 20 percent of year-one budget).
  • Months two to six: implementation, documentation, tooling, and training (50 to 60 percent).
  • Months six to nine: internal audit, penetration test, and Stage 1 and Stage 2 fees (25 to 35 percent).

Certification body fees are usually invoiced per stage, and many bodies offer the three-year cycle, initial plus two surveillance audits, on a payment schedule. From year two onward, costs settle into a predictable annual rhythm of surveillance fees plus maintenance.

 

How to Reduce ISO 27001 Certification Costs

Start with a Scoped Gap Analysis

Spending $3,000 on a gap analysis before committing to anything else routinely saves five figures later, because it lets you scope the ISMS around what you already do well and price the genuine gaps accurately.

Reuse Existing Documentation and Controls

SOC 2 controls, NIST CSF mappings, GDPR records of processing, and even informal runbooks all count. Auditors care that controls exist and operate, not that they were written fresh for ISO 27001.

Apply the Square Root Rule for Multi-Site Audits

Under IAF MD 1, the mandatory multi-site sampling rules, certification bodies can sample sites rather than visit all of them: the initial audit samples roughly the square root of total sites, surveillance audits sample about 0.6 times the square root, and recertification about 0.8 times. A 25-site organisation gets audited at five sites in year one instead of twenty-five. Structuring your ISMS with a genuine central function is what unlocks this, and it is one of the largest single savings available to distributed companies.

Negotiate Multi-Year Audit Contracts

Committing to the full three-year cycle with one certification body typically earns a 10 to 20 percent discount on audit fees and locks the day rate against annual increases. Quotes are negotiable; treat the first number as an opening position.

Bundle ISO 27001 With Other Audits (SOC 2, ISO 42001)

Integrated audits share evidence, interviews, and sometimes audit days. Pairing ISO 27001 with SOC 2, or adding ISO 42001 for AI management systems, through the same audit firm commonly cuts 20 to 30 percent against running each engagement separately. The overlap in controls does most of the work: a single access review can serve three frameworks.

Leverage Templates and Toolkits

A $1,000 documentation toolkit replacing $10,000 of consultant drafting is the single best cost-to-value ratio in the entire project, provided someone internal actually adapts the templates to reality. Auditors spot unmodified boilerplate instantly, and generic policies that do not match practice generate nonconformities.

ISO 27001 Certification Cost vs ROI

ISO 27001 Certification Cost vs. ROI

Cost of Certification vs. Cost of a Data Breach

IBM’s 2024 Cost of a Data Breach Report puts the global average breach cost at $4.88 million, with US organisations averaging over $9 million. A $40,000 certification programme is roughly one percent of that global average. The certification itself does not prevent breaches, but the ISMS discipline behind it- asset inventories, access reviews, incident response, vendor management, demonstrably reduces both likelihood and impact.

Revenue Impact and Sales Enablement

For most companies, the honest ROI case is commercial, not defensive. Certification unblocks enterprise procurement, shortens security questionnaires from weeks to days, and is increasingly a hard tender requirement in government, finance, and healthcare supply chains. One enterprise deal that closes because the certificate exists usually repays the entire programme.

Reduced Insurance Premiums

Cyber insurers increasingly price against demonstrated security controls, and a certified ISMS maps directly onto their underwriting questionnaires. The more reliable benefit, beyond reported premium reductions, is insurability itself: certified organisations face fewer exclusions and less painful renewals.

In short: ISO 27001 certification costs most organisations between $10,000 and $80,000 in year one, driven primarily by headcount, scope, and implementation approach, with $5,000 to $25,000 per year thereafter to maintain. The budget is controllable through scoping, accredited-body negotiation, multi-site sampling, and framework bundling, and the spend is best evaluated against the revenue it unblocks rather than as a pure compliance tax.

ISO 27001 Certification Cost FAQs

How much does ISO 27001 certification cost on average?

Most small to mid-sized organisations spend $15,000 to $50,000 in the first year, covering implementation, tooling, and the certification audits, with large or complex enterprises exceeding $100,000. Ongoing costs run $5,000 to $25,000 per year across surveillance audits and ISMS maintenance.

Yes, with a tight scope. A cloud-native startup using templates or an automation platform can certify for $10,000 to $25,000 all-in. The key decisions are limiting scope to what customers actually require and choosing a right-sized accredited certification body rather than a premium brand.

Accredited certification bodies charge roughly $1,500 to $2,200 per audit day in the US and £1,000 to £1,500 in the UK in 2026. The number of days is calculated from ISO/IEC 27006 tables based on your in-scope headcount and complexity, so the day rate is only half of the fee equation.

Yes. Surveillance audits in years two and three typically run one third to one half the duration of the initial Stage 2 audit, which puts most SMB surveillance fees at $3,000 to $10,000 per year.

Major nonconformities require remediation plus a follow-up assessment, usually adding $1,500 to $6,000 in audit fees and one to three months of delay. The larger cost is commercial: deals and tenders waiting on the certificate stall until the follow-up closes the findings.

Accredited audits cost more than unaccredited ones because accredited bodies carry oversight obligations, witnessed audits, and qualified auditor requirements. The premium is worth paying: unaccredited certificates are routinely rejected by enterprise procurement and effectively buy you nothing.

It eliminates travel and accommodation recharges and often shortens elapsed time, but the audit-day count itself is fixed by the ISO/IEC 27006 calculation, so the fee reduction is real yet modest. Remote delivery helps most for multi-site and internationally distributed scopes.

The ranges overlap heavily: SOC 2 Type II reports typically cost $20,000 to $60,000 all-in, similar to ISO 27001. The structural difference is that SOC 2 requires a fresh attestation every year, while ISO 27001 runs cheaper surveillance audits in years two and three of its cycle. Companies needing both should bundle them with one audit firm and reuse the shared control evidence.

Axipro Author

Picture of Pedro Dias

Pedro Dias

Pedro has been writing online for over 10 years. With experience in all things programming, cyber security, and compliance, he is our editor-in-chief at Axipro.

Blog Highlights

Explore More Articles

A consultant-grade ISO 42001 gap analysis checklist has 38 Annex A controls, roughly 80 clause-level “shall” statements, and one question attached to every line: where is the evidence, and would a certification body accept it? That last question is what separates the checklists consultants use from the free self-assessment spreadsheets that rank for the same search. This article lays out the checklist itself: what a consultant checks before the engagement starts, the clause-by-clause and control-by-control checkpoints, how evidence gets sampled, how gaps get scored, what the deliverables look like, and what fails most often. Use it to run your own assessment, or to check whether the consultant you’re about to hire is doing the job properly. What Makes a Consultant-Grade ISO 42001 Gap Analysis Checklist Different​ Depth of Evidence Review vs. Self-Assessment Tools A self-assessment tool asks whether you have an AI policy. A consultant asks to see it, checks the approval date and version, reads clause 5.2 against it, and then asks three people in engineering whether they’ve read it. The checklist item is the same. The evidence standard is not. Consultants score every item on three levels: documented, implemented, and effective. A policy that exists but nobody follows scores as “ad hoc,” not “defined.” A control that runs but produces no record scores as unverifiable, which for audit purposes is the same as absent. Self-assessment tools collapse those three levels into a single yes/no, which is why companies that score 85% on a free tool routinely receive major nonconformities at Stage 2. Alignment with Certification Body Expectations Certification bodies auditing against ISO/IEC 42001:2023 now work under ISO/IEC 42006:2025, which sets competence, audit-time, and impartiality requirements for AIMS auditors and builds on ISO/IEC 17021-1. A consultant-grade checklist is written with 42006 in mind: it organizes findings by clause and control identifier, because that’s how the auditor works, and it records evidence locations, because that’s what the auditor will sample. The practical difference shows up in the report. A gap register that says “AI governance needs improvement” is useless in front of an auditor. One that says “A.5.2 not conformant: no documented impact assessment process; two of four in-scope systems have no assessment on file” maps directly to the audit plan. Risk-Weighted Scoring Methodology Self-assessments count gaps. Consultants weight them. A missing AI policy under clause 5.2 and an incomplete competence matrix under 7.2 are both gaps, but the first will block certification and the second will earn you a minor finding. A consultant-grade checklist carries two scores per line: a maturity rating (how far the control is from working) and a certification criticality (what happens at audit if it stays this way). Effort estimates live in the remediation plan, never in the gap score, because mixing them produces a roadmap that fixes easy things first rather than important ones. Insider Note: The fastest tell that a checklist is consultant-grade rather than a marketing download is whether it has a column for evidence location. Auditors don’t accept “yes” as evidence. If the checklist has nowhere to record where the proof lives, it wasn’t built by someone who has sat through a Stage 2. Pre-Engagement Preparation Consultants Complete Before the Gap Analysis Client AI Inventory and Use Case Cataloging Nothing in the checklist works without a complete AI inventory, and it’s the input clients get wrong most often. The inventory records every AI system in use: purpose, the role you play (developer, provider, deployer, or user), data consumed, outputs produced, whether a human sits between the output and the decision, and which third-party model or API it depends on. Consultants push hard on shadow AI here: SaaS tools that added AI features, agents running under employee credentials, and internal scripts calling model APIs. Every one of those is in scope until you document why it isn’t. Defining AIMS Scope Boundaries Clause 4.3 requires a scope statement naming which AI systems, business units, locations, and lifecycle stages the AIMS covers. Consultants draft this from the inventory, not before it. Scope discipline matters commercially too: certification bodies price audits by audit days, and audit days scale with scope. A narrow, well-justified first scope (the customer-facing AI product, say, rather than every internal tool) is usually the right call for a first certification. Stakeholder Interview Planning The checklist needs answers from people who don’t write policies. A typical interview plan covers the executive sponsor (clause 5), the AI or product lead (clauses 6 and 8), data engineering (A.7), procurement or vendor management (A.10), legal or privacy (A.5, A.8), and at least one front-line user of the AI system (A.9). Consultants interview the doers separately from the document owners, because the distance from what the procedure says to what actually happens is the finding. Document Request List (DRL) Consultants Send Clients The DRL goes out one to two weeks before fieldwork. A standard ISO 42001 DRL asks for the AI inventory; existing AI, security, and data policies; org chart with AI governance roles; any AI risk assessments or impact assessments; model documentation (model cards, system cards, or whatever exists); training-data provenance and data quality records; supplier contracts for third-party models; incident and change logs; training records; any ISO 27001 ISMS documentation; and the last internal audit and management review minutes if they exist. Missing items become findings rather than delays. Pro Tip: Return an Honest DRL Return the DRL with a column that says “does not exist” wherever that’s true. Consultants would rather know on day one than discover it in a workshop. An honest DRL shortens fieldwork by days and makes the maturity scores more accurate, which makes the remediation plan cheaper. Clause-by-Clause Checklist Consultants Use (ISO 42001 Clauses 4 to 10) ISO 42001 follows the Harmonized Structure shared with ISO 27001 and ISO 9001, so clauses 4 to 10 will look familiar to anyone who has run an ISMS. What’s different is the content each clause demands. Clause 4 – Context of the Organization Checkpoints Consultants check for a documented analysis of

Scigeniq, a UAE life sciences software vendor, completed SOC 2 Type 2 and ISO 27001 in one three-month engagement with Axipro and Vamu.

ISO/IEC 42001:2023 asks for three assessments, and most teams try to squeeze them into one spreadsheet: a gap analysis against clauses 4 to 10 and Annex A, an AI risk assessment under clause 6.1.2, and an AI system impact assessment under clause 6.1.4. Treat them as one exercise and the auditor pulls them apart for you at Stage 2. Treat them as three unrelated projects and you triple the workshops, the registers, and the remediation lists. What works is a single methodology with distinct outputs that share inputs, share a traceability matrix, and feed one remediation plan. This article lays out that methodology end to end: how gap analysis and risk assessment fit together under ISO 42001, how to prepare, the step-by-step process for each, how to merge the outputs into one risk treatment plan, the registers and templates you’ll need, and what a certification body expects to see when you’re done. Why Gap Analysis and Risk Assessment Must Work Together Under ISO 42001 A gap analysis measures distance from the standard. A risk assessment measures exposure from your AI systems. They answer different questions, and ISO 42001 makes them depend on each other in a way ISO 27001 only implies. Clause 6.1.3 requires you to compare the controls you select through risk treatment against Annex A, and to justify any Annex A control you leave out in the Statement of Applicability (SoA). So your Annex A gap analysis has no defensible baseline until the risk assessment tells you which controls you need. Run the gap analysis on its own, and you end up scoring yourself against all 38 controls, including ones your risk profile never called for. Run the risk assessment on its own, and you pick treatments with no idea what already exists to deliver them. The methodology below interleaves the two. A clause-level gap review sets the scope and evidence base, the risk and impact assessments decide which controls are required, and a control-level gap review then scores only what matters. How AI-specific risks shape the methodology Traditional information security risk works from confidentiality, integrity, and availability. AI risk adds categories that don’t map neatly onto any of those: model drift, bias in training data, outputs nobody can explain, automation bias in the humans doing the reviewing, and dependence on third-party foundation models whose behavior changes without warning. ISO/IEC 23894, the companion guidance on AI risk management, adapts the ISO 31000 cycle (establish context, identify, analyze, evaluate, treat) to these sources rather than inventing a new one. That’s why the methodology here keeps the familiar ISO 31000 shape and changes the inputs, not the process. Regulatory and business drivers for a formal methodology The commercial driver is procurement. Enterprise security questionnaires now ask whether you ran an AI impact assessment, whether a human reviews high-stakes outputs, and which third-party models touch customer data. A documented methodology answers those questions with evidence instead of assurances. The regulatory driver is the EU AI Act, and its timeline moved in July. Regulation (EU) 2026/1744, the Digital Omnibus on AI, entered into force on July 27, 2026, and pushed the high-risk obligations for standalone Annex III systems from August 2, 2026 to December 2, 2027. Annex I embedded systems moved to August 2, 2028. The Article 50 transparency obligations still kicked in on August 2, 2026, as originally planned. Article 9 of the AI Act text on EUR-Lex requires a risk management system for high-risk AI that runs continuously across the system lifecycle, which is exactly what an ISO 42001 methodology gives you. Sixteen extra months is time to build it properly, not a reason to shelve it. Core Principles of an ISO 42001 Gap Analysis and Risk Assessment Methodology Four principles keep the methodology defensible in front of a certification body. Alignment with clauses 4 to 10 and Annex A. Every finding in the gap register cites a clause or an Annex A control identifier. Auditors work clause by clause, so a gap register organized any other way forces a translation step during the audit that nobody enjoys. Integration with the AI system impact assessment. Clause 6.1.4 is what separates ISO 42001 from every other Annex SL standard. The impact assessment looks outward at individuals, groups, and society. The risk assessment under 6.1.2 looks inward at the organization. The standard wants both as separate documented outputs, and the consequences you find in the impact assessment have to feed back into the risk assessment. So the methodology runs the impact assessment as a scheduled input to risk analysis, not something bolted on the week before the audit. Risk-based thinking applied to the AIMS itself. Clause 6.1.1 also asks you to consider risks and opportunities to the management system: someone leaving the AI governance function, a vendor retiring a model, a regulator changing its classification rules. These go in the same register with a different category tag. Defined inputs, outputs, and success criteria. Inputs are the AI system inventory, the scope statement, existing policies, data flow diagrams, model documentation, and your risk criteria. Outputs are the gap register, the AI risk register, impact assessment reports, the SoA, and the risk treatment plan. Success means each output traces to the others, every gap and risk has an owner, and an internal auditor could repeat the process and land somewhere similar. Insider Note: Impact assessments are where certification auditors probe hardest, because they’re the most distinctive part of ISO 42001 compared with ISO 27001. A recycled security risk register with “AI” pasted into the risk titles gets picked apart in Stage 2. Build the impact assessment methodology properly the first time. It’s far cheaper than rebuilding it under a nonconformity deadline. Preparing for the Gap Analysis and Risk Assessment Preparation is where most of the calendar time goes, and where most later problems start. Define scope, boundaries, and the AI system inventory. Scope under clause 4.3 has to name which AI systems, business units, and lifecycle stages the AIMS covers. You can’t write