Table of Contents

Reach SOC 2 Compliance in 6 Weeks or Less.

  /

  / 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

CMMC certification costs between $4,000 and $30,000 at Level 1, $30,000 to $300,000 or more at Level 2, and $100,000 to well over $1 million at Level 3. Most contractors expect the audit fee to be the big number. It isn’t. The formal assessment typically accounts for only 25% to 40% of total spend, with preparation, remediation, and technology upgrades consuming the rest. The stakes changed in late 2025. The final 48 CFR acquisition rule took effect on November 10, 2025, which means CMMC requirements now appear directly in Department of Defense (DoD) solicitations and contracts. Starting in November 2026, Phase 2 of the rollout gives contracting officers the authority to require third-party certification for Level 2 work. If you handle Controlled Unclassified Information (CUI), certification is no longer optional, and the cost question becomes a budgeting exercise rather than a hypothetical. This guide breaks down every major cost category, what moves your number up or down, and how to keep the total under control. What Is CMMC Certification and Why Does Cost Vary? The Cybersecurity Maturity Model Certification (CMMC) is the DoD’s framework for verifying that companies in the Defense Industrial Base (DIB) actually protect the sensitive information they handle. The program, codified in 32 CFR Part 170, builds on the security requirements of NIST SP 800-171 and, at the top tier, selected controls from NIST SP 800-172. Costs vary so widely because you can’t buy CMMC off a shelf. Your environment has to reach a certain state and then stay there. A 15-person machine shop with one well-scoped CUI enclave faces a fundamentally different project than a 500-person prime contractor with CUI flowing through a dozen systems. Your starting security posture, the scope of your assessment boundary, and whether you build internally or hire help all move the total by six figures in either direction. Average CMMC Certification Cost at a Glance The DoD’s own published estimates are instructive. A triennial Level 2 certification assessment, including affirmations, is projected at roughly $105,000 for small entities and $118,000 for larger ones. Those figures cover only assessment and affirmation activities, though. The DoD excludes implementation costs from its estimates on the grounds that NIST SP 800-171 compliance has been contractually required under DFARS 252.204-7012 since 2017. Your real budget has to cover both. CMMC Certification Cost by Level CMMC Level 1 (Foundational) Cost: $5,000 – $30,000 Level 1 covers Federal Contract Information (FCI) and requires 15 basic safeguarding practices drawn from FAR 52.204-21. Because Level 1 permits an annual self-assessment with no third-party auditor, the costs are internal labor, basic tooling, and documentation. Small contractors with reasonable IT hygiene often land near the bottom of the range. The DoD estimates annual Level 1 assessment and affirmation activity at around $6,000 for a small entity, with the remainder of the range driven by any remediation needed to attest honestly. CMMC Level 2 (Advanced) Cost: $50,000 – $300,000+ Level 2 is where most of the DIB lands and where budgets get serious. It requires full implementation of all 110 security requirements in NIST SP 800-171, assessed across 320 individual objectives. For most contracts, a C3PAO (Certified Third-Party Assessor Organization) accredited by the Cyber AB has to conduct the assessment every three years. Market data puts C3PAO assessment fees at $30,000 to $100,000 depending on scope, site count, and complexity. Preparation dwarfs that figure for most organizations. Companies starting from a low maturity baseline routinely spend three to four times the assessment fee on readiness work before an auditor ever shows up. CMMC Level 3 (Expert) Cost: $300,000 – $1,000,000+ Level 3 adds 24 enhanced requirements from NIST SP 800-172 on top of a completed Level 2 certification, and the assessment is conducted by the government’s DIBCAC rather than a commercial C3PAO. DIBCAC charges no assessment fee, but don’t mistake free for cheap. The DoD estimated roughly $41,000 in additional implementation cost for the 800-172 controls alone, and total triennial assessment-related costs in the $146,000 to $159,000 range. Real-world totals run far higher once you account for the advanced tooling, threat hunting capability, and organizational changes Level 3 demands. Only contractors supporting the most sensitive programs need this tier. Worth Knowing: You can’t skip to Level 3. You can’t skip to Level 3. A final Level 2 certification with all POA&M items closed is a prerequisite for the same assessment scope, so Level 3 budgets always include a full Level 2 project first. CMMC Certification Cost Breakdown by Expense Category Gap Assessment and Readiness Planning Costs A gap assessment maps your current environment against NIST SP 800-171 and typically costs $1,500 to $20,000 depending on depth and scope. This is the most valuable dollar you’ll spend in the entire project, because everything downstream is priced off what it finds. Documentation and System Security Plan (SSP) Costs The System Security Plan (SSP) is the cornerstone document of any assessment, mapping every control to your specific implementation. Professionally developed SSPs and supporting policies run $12,000 to $60,000. A weak SSP is one of the most common reasons assessments stall or fail, so this is a poor place to economize. Remediation and Security Control Implementation Costs Closing the gaps is usually the largest line item: $20,000 to $150,000 or more. Multi-factor authentication, logging and SIEM deployment, encryption, access control restructuring, and incident response capability all live here. Organizations with mature security postures spend far less than those starting from scratch. Technology and Infrastructure Upgrade Costs Many contractors move CUI into a dedicated enclave rather than securing their entire network. Enclave platforms typically cost $300 to $400 per user per month. Others upgrade endpoint protection, replace unsupported systems, or migrate to government-grade cloud environments, each with its own licensing and migration costs. C3PAO Assessment and Audit Fees The formal Level 2 assessment runs $30,000 to $100,000, driven by assessor-days, number of sites, and evidence quality. Well-organized evidence directly reduces assessor time and therefore your invoice. Consulting and Advisory Fees Specialist consultants, including Registered Practitioners (RPs) and

SOC 2 and ISO 27001 Engagement

After a SOC 2 and ISO 27001 engagement, there are two documents out of the whole pile that actually close deals: the SOC 2 attestation report and the ISO 27001 certificate. Everything else your engagement produces exists to create those two, support them, or keep them alive for another year. Companies routinely ask their auditor for a SOC 2 certificate, which doesn’t exist. They send a prospect their full ISMS documentation when a one-page certificate would have done. They pay for six months of readiness work and then can’t say what they’re holding at the end of it. So here’s the full list. What a SOC 2 engagement produces, what an ISO 27001 engagement produces, what a combined program produces, and who gets to see each one. Understanding SOC 2 and ISO 27001 Engagement Outputs The Core Difference: Report vs. Certificate SOC 2 is an attestation. A licensed CPA firm examines your controls against the Trust Services Criteria under standards set by the AICPA, then writes up what it found and signs an opinion. No certificate. No logo from the AICPA. No pass or fail stamp. What you get is the report, and it usually runs 60 to 120 pages. ISO 27001 is a certification. An accredited certification body audits your Information Security Management System (ISMS) against ISO/IEC 27001:2022, and if you conform, it issues a certificate of registration. The certificate itself is a page or two. All the detail lives behind it, in your ISMS documentation and the audit reports the certification body writes as it goes. SOC 2 Engagement Deliverables The SOC 2 Attestation Report The report is the engagement. The AICPA’s illustrative SOC 2 report lays out the standard structure: auditor’s report, management’s assertion, system description, the Trust Services Criteria in scope, and the controls tested with their results. A Type I covers control design at one point in time. A Type II covers whether those controls actually operated over a period, usually three to twelve months, and most enterprise buyers now won’t accept anything else. Independent Auditor’s Opinion Letter First section of the report, and the first thing anyone experienced turns to. It gives the scope, the examination period, and the auditor’s conclusion. An unqualified opinion means the description held up and the controls worked. A qualified opinion means the auditor found something material, and every serious reviewer will want to talk about it. Management Assertion Your leadership signs a written statement stating that the system description is accurate and that the controls were properly designed and are operating. It reads like a formality, and it isn’t. The auditor’s entire examination runs against what management asserts here, so overstating anything creates real exposure. System Description Usually the longest part of the report, and you write it, not the auditor. It covers the services in scope, your infrastructure, software, people, processes, how data moves, which subservice organizations you depend on, and the complementary user entity controls your customers have to run on their side for your controls to hold up. Trust Services Criteria Applied Security (the Common Criteria) is in every SOC 2. Availability, Processing Integrity, Confidentiality, and Privacy are optional, and the report names exactly which ones you picked. Whatever you decide during scoping ends up printed in a document your customers read for the next several years. Description of Tests of Controls and Results (Type II) The matrix: every control, what the auditor did to test it, and what came back, including exceptions. Reviewers spend most of their time here, because the exceptions tell them things the opinion letter won’t. Bridge Letter / Gap Letter Your report covers a fixed window, so one ending December 31 leaves a hole for a customer doing diligence in June. A bridge letter from your management, not the auditor, confirms that nothing material changed in the control environment between the report’s end date and today. You’ll write these often enough to keep a template. Management Letter and Observations Plenty of auditors also send an internal-only letter covering observations, minor exceptions, and suggestions that never reached the threshold of a qualified opinion. It’s the closest thing to free consulting you’ll get before next year’s audit starts. Insider Note: Ask early whether your auditor issues a management letter, and whether exceptions land in the report body or only in that letter. Firms handle this differently, and the answer decides what your customers see versus what stays behind your firewall. It rarely comes up in the proposal, but it changes how the finished report reads to a buyer. ISO 27001 Engagement Deliverables ISO 27001 Certificate of Registration The document everyone asks for. It names the certified legal entity, states the ISMS scope, identifies the certification body, carries an accreditation mark from a body recognized under the International Accreditation Forum such as UKAS or ANAB, and shows the validity dates. It’s good for three years as long as you pass annual surveillance audits. Read the scope statement carefully, on your own certificate as much as anyone else’s. A certificate covering one office or one product line says nothing about the rest of the business. Statement of Applicability (SoA) After the certificate, this is the document buyers request most. The Statement of Applicability runs through all 93 Annex A controls in ISO/IEC 27001:2022, says which apply to you, justifies the ones you excluded, and records where each stands. Auditors use it as the map of your control environment, and larger customers increasingly want to see it or a summary of it during diligence. Risk Assessment and Risk Treatment Plan Your methodology, the register it produced, and the Risk Treatment Plan showing what you decided to do about each significant risk: mitigate it with a control, transfer it, avoid it, or accept it. ISO 27001 is built around risk, so these documents are what justify every control decision recorded in the SoA. Information Security Management System (ISMS) Documentation The policy and procedure set, plus the operational records that prove any of it happens. Information

The EU AI Act’s transparency requirements take effect on 2 August 2026, and most of the companies they cover still think the rules are not their problem. Article 50 applies to any business that publishes AI-generated content or runs an AI system that talks to people in the EU. That includes the marketing team generating campaign images and the support team running a chatbot. It also covers the AI agents you’ve wired into customer email. Penalties reach €15 million or 3% of total worldwide annual turnover, whichever is higher, and you don’t need an office in Europe to be in scope. If your content or your chatbot reaches EU users, the obligations reach you. In a nutshell: if you publish AI-generated images or video, deploy chatbots or AI agents that interact with EU users, or publish AI-written text on matters of public interest, then yes, the EU AI Act applies, starting 2 August 2026. A quick word on the “AI Act delay” headlines. The Digital Omnibus package did push the high-risk system deadlines back, in some cases by more than a year, but it did not move the deployer obligations in Article 50. Companies that read those headlines and stood down their AI Act work made an expensive mistake, because the rules most likely to touch an ordinary business are the ones that stayed on the calendar. What Article 50 Actually Requires Article 50 of the AI Act sets out transparency obligations in four situations. In plain English: Tell people when they’re talking to AI. Systems designed to interact directly with people — chatbots, voice assistants, and AI agents — must make clear that the user is dealing with AI, unless that’s already obvious. Mark AI-generated content so machines can detect it. Providers of generative AI systems must mark outputs in a machine-readable format, typically through metadata and watermarking, so the content is detectable as artificially generated. Label deepfakes. Anyone deploying AI to generate or manipulate image, audio, or video content that resembles real people, places, objects, or events, and could falsely appear authentic, must disclose that the content is artificial. Label AI-generated text on matters of public interest. Text published to inform the public must carry a label if AI-generated or manipulated, unless a human reviewed it and a person or organization holds editorial responsibility for it. Article 50 also covers emotion recognition and biometric categorization systems, which carry their own disclosure duties. Far fewer businesses run into those, so this article sticks to the four above. The distinction running through all of this is provider vs deployer. The provider builds or supplies the AI system. The deployer uses it professionally. Most companies reading this are deployers. If You Use AI-Generated Images Realistic AI images sit closer to the deepfake rules than most marketing teams assume. The Act’s definition covers content depicting people, objects, places, and events that could falsely appear authentic to a viewer, which describes a large share of what image generators produce for campaigns, social posts, and landing pages. So what does “clearly and distinguishably labeled” mean? The threshold is best described by its failures: a tiny disclosure hidden in the website footer doesn’t qualify. Neither does a faint label on an image, a label that flashes for an instant in a video, or a disclosure buried in your terms and conditions. The label has to be visible right where someone sees the content, and it has to meet accessibility standards so people with disabilities can perceive it too. The Code of Practice proposes a standardized “AI” visual label, localized per language (“KI” in German, “IA” in French). It also draws a useful line between fully AI-generated content and AI-assisted content, with lighter requirements for the latter. A designer who used AI to extend a background is in a different position from a team publishing a fully synthetic image of a person who doesn’t exist. Important: The deepfake duty doesn’t care about intent. A flattering, harmless AI image of your CEO at an event that never happened is still a deepfake under the Act. Marketing teams generate this kind of content casually. From August, every one of those images needs a label. If You Deploy AI Agents or Chatbots The rule itself is simple: people must know they’re dealing with AI. The provider carries the design obligation, but as the deployer you’re the one putting the system in front of your customers, and you’re the one an EU regulator will contact if your branded assistant pretends to be human. The Act contains an exception for cases where it’s “obvious” the user is talking to AI, judged from the perspective of a reasonably well-informed and observant person. Don’t lean on it. What’s obvious to your product team isn’t obvious to every customer, and the human-sounding voice agents and email-writing AI agents rolling out right now are designed specifically to not feel like software. If an AI agent negotiates a renewal over email or handles a support ticket end to end, disclose it. Pro Tip: Put the Disclosure at the Start of the Interaction Put the disclosure at the start of the interaction, in the interface itself: “You’re chatting with an AI assistant.” A line in your privacy policy doesn’t meet the standard, and a disclosure that appears after the conversation ends is worthless. For voice agents, say it up front in the greeting. What Your AI Vendors Owe You The machine-readable marking obligation in Article 50(2) sits with providers — the companies supplying your generative AI tools. The final Code of Practice expects providers to apply at least two layers of marking where necessary, such as embedded metadata combined with watermarking, and to offer detection mechanisms so deployers, authorities, and researchers can verify whether a piece of content came from AI. One timing caveat: the Digital Omnibus gives generative AI systems already on the market before 2 August 2026 until 2 December 2026 to comply with the marking requirement. Every other Article 50 obligation stays on