/

  / 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

Compliance software collects the evidence. A consultant builds the system that evidence is meant to prove. That’s the real difference in the ISO 27001 consultant vs software decision, and most teams only figure it out after they’ve bought one and realized they still need the other. Below, we compare what each route covers, where it breaks down, and what it costs you in time, money, and your team’s hours. Short version: software on its own works for a small group of companies. For most SaaS and tech scale-ups trying to get an enterprise deal over the line, consultant-led implementation on a compliance platform is the faster and safer path to a certificate. Quick Answer: Consultant, Software, or Both? Software-only works if you already have an in-house security lead who’s taken a company through ISO/IEC 27001 before and has the time to own the project. Consultant-only still makes sense if you run mostly on-premise or legacy systems that platforms barely integrate with. For everyone else, which means most cloud-native companies under a few hundred people, a hybrid works best: a platform to handle evidence and monitoring, and a consultant to build the management system and stand behind it in front of an auditor. Here’s why. What an ISO 27001 Consultant Handles ISO/IEC 27001:2022 is a management system standard. Clauses 4 to 10 cover how you run information security, and Annex A lists 93 controls you pick from based on risk. Almost none of it is box-ticking. Most of it comes down to judgment calls about your business, and that’s what you’re paying a consultant for. Scoping, Gap Analysis and Risk Assessment Scope is the first decision you make, and the most expensive one to get wrong. Go too wide and you’ll spend months on controls for systems no customer asks about. Go too narrow and the certificate won’t get through the procurement review it was supposed to pass. A consultant scopes around the deals you’re trying to close, runs a gap analysis, and builds a risk assessment based on your real assets and threats. That’s the document auditors dig into hardest. ISMS Documentation and Policy Writing The standard asks for a specific set of documents: the ISMS scope, information security policy, risk assessment and treatment methodology, Statement of Applicability, risk treatment plan, and evidence of competence, monitoring, internal audit, and management review. A consultant writes these around how your company works day to day, instead of how a template imagines it works. Auditors check whether you follow your own procedures, so a mismatch shows up fast. Internal Audit and Certification Audit Support You need an internal audit before certification, and Clause 9.2 says the auditor has to be objective and impartial. In a small company, the people who built the ISMS can’t credibly audit it, so most teams outsource it through ISO 27001 internal audit services. A good consultant also gets your team ready for the Stage 1 and Stage 2 audits, joins the conversations that matter, and handles corrective actions if the auditor raises nonconformities.  What ISO 27001 Compliance Software Handles Compliance automation platforms, often called GRC platforms, have changed how cloud-native companies get certified. They’re very good at the repetitive, evidence-heavy side of the work. Automated Evidence Collection and Continuous Control Monitoring The platform plugs into your cloud provider, identity provider, code repos, HR system, and device management tools, then pulls evidence on its own. It’ll flag an unencrypted storage bucket, an ex-employee who still has access, or a laptop without disk encryption. For technical controls, that saves weeks of screenshots and spreadsheet tracking. Policy Templates and Annex A Control Mapping Most platforms come with a policy library and map each control to the ISO 27001 clauses and Annex A. You get a starting point and a clear view of which controls have evidence and which don’t. Auditor Access and Ongoing Compliance Tracking Auditors can log in and review evidence themselves, which cuts down fieldwork. After you’re certified, dashboards show when controls slip between surveillance audits, so you aren’t rebuilding evidence from scratch every year. Where Each Approach Falls Short Neither route covers everything by itself. The good news is that the ways each one fails are predictable, so you can plan around them. Limits of Compliance Automation Platforms A platform can tell you a control is failing. It can’t decide your scope, run your risk assessment, write a policy that matches your operations, convince your CTO to change the offboarding process, or explain to an auditor why you excluded a control from your Statement of Applicability. Templates can also make you feel further along than you are. A dashboard at 90% can hide an ISMS that won’t survive Stage 1, because the missing 10% is the management system itself. Insider Note: The Stage 1 problem we see most on software-only projects is a risk assessment copied straight from the platform’s default risk library. The risks are generic, the scores are almost identical, and nothing ties back to the company’s own assets. Auditors notice within minutes, and it weakens the Statement of Applicability that’s built on it. The other problem is ownership. Software assumes someone inside the company will drive the project. At most startups that’s a CTO or ops lead who already has a full-time job, and the subscription renews whether the work gets done or not. Limits of a Consultant-Only Approach A consultant working without automation spends billable days on things a platform does for free, like chasing screenshots, updating evidence trackers, and collecting the same proof again before every surveillance audit. You pay more and wait longer. You also end up with a program that’s only accurate on the day it’s handed over. Once the engagement ends, the evidence goes stale and year-two surveillance turns into a scramble. ISO 27001 Consultant vs Software: Side-by-Side Comparison Factor Consultant only Software only Hybrid (consultant + platform) Time to audit readiness 3 to 6+ months Highly variable; depends on internal expertise As little as 6 weeks for well-scoped

Uzbekistan regulates artificial intelligence through two documents. The first is Law ZRU-1115, signed on 21 January 2026. It amends existing legislation to define AI, stops anyone from basing decisions about people’s rights on AI output alone, and fines companies that process personal data unlawfully with AI. The second is the set of Ethical Rules approved by Order No. 3787, in force since 17 June 2026, which spell out what developers, implementers, and users actually have to do. Uzbekistan hasn’t passed a standalone AI act, and its rules don’t sort systems into risk tiers or require conformity assessments. The framework is short and blunt, and it’s already enforceable. Below we walk through what each document requires, who it applies to, how it stacks up against the EU AI Act, and what a company using AI in Uzbekistan should do next. Uzbekistan AI Regulation at a Glance (TL;DR) Instrument Date What it does Who it binds Law ZRU-1115 Signed 21 January 2026 Defines AI in law, sets general rules for AI-built information resources and systems, bans legally significant decisions based only on AI, adds fines for unlawful AI processing of personal data State bodies, organizations, website owners, anyone processing personal data with AI Order No. 3787 (Ethical Rules) Registered 14 March 2026, in force 17 June 2026 Sets eight mandatory ethical principles and lists rights and obligations for developers, implementers, and users Individuals and companies developing, implementing, or using AI in Uzbekistan Law No. 1125 (Personal Data amendments) Adopted 26 March 2026 Limits data localization to biometric, genetic, and local telecom user data, and allows cross-border transfers under conditions Personal data operators, including AI providers AI Strategy until 2030 (RP-358) 14 October 2024 Sets national targets for AI adoption, infrastructure, and skills Government bodies What Is Law ZRU-1115? The law’s official title is a mouthful: “On making additions and changes to certain legislative acts of the Republic of Uzbekistan in connection with the regulation of relations arising from the use of artificial intelligence.” Put simply, it’s an amending law. Instead of creating a new AI code, it writes AI into laws that were already on the books. When It Was Signed and When It Took Effect The Legislative Chamber of the Oliy Majlis adopted the bill on 12 August 2025, and the Senate approved it on 1 November 2025. President Shavkat Mirziyoyev signed it on 21 January 2026. You can read the official text in Lex.uz, Uzbekistan’s national legislation database. The law set out the principles and the penalties. The day-to-day detail arrived later with the Ethical Rules, which came into force on 17 June 2026. For compliance planning, treat mid-June 2026 as the point when the whole framework started applying. Why Uzbekistan Amended Existing Laws Instead of Passing a Standalone AI Act Uzbekistan wants more AI, not less. Its national strategy sets numeric targets for adoption, investment, and local computing capacity, and a heavy EU-style act would have worked against them. So lawmakers kept it light. They defined AI, drew two hard lines (human control over decisions that affect people’s rights, and protection of personal data), and left the Ministry of Digital Technologies to fill in the rest through secondary rules. Businesses get less legal certainty, and the government gets to move faster. Which Laws ZRU-1115 Changes For businesses, two amendments matter most. The Law “On Informatization” (ZRU-560-II, 2003) now contains a legal definition of AI, a new article on using AI in information resources and systems, duties for website owners, and updated powers for the ministry in charge. The Code on Administrative Liability now includes an offense for processing and spreading personal data unlawfully using AI. The Legal Definition of Artificial Intelligence in Uzbekistan Under the amended Law “On Informatization,” AI is a set of technological solutions that imitate human cognitive functions, including learning on their own and solving problems, and that produce results on specific tasks comparable to what a person could do. That’s deliberately broad. It covers generative AI, machine learning classifiers, recommendation engines, and most agentic systems. The Ethical Rules add a narrower term, the AI system: software built on AI that can find, collect, store, analyze, process, evaluate, and use data, and make decisions on its own based on that data. If your product makes a decision from data, or shapes one, assume it counts. Key Rules Introduced by Law ZRU-1115 General Principles for Using AI in Information Systems and Resources The new article in the Law “On Informatization” starts from harm. Information resources created with AI, and information systems running on AI, must not harm people’s life, health, freedom, honor, or dignity, or violate their other inalienable rights. The standard is short and open-ended. It gives regulators something to enforce against without saying in advance what counts as harm. Principle-based rules like this deserve to be taken seriously precisely because the edges are undefined. Human Oversight: No Decisions on Rights and Freedoms Based Solely on AI Most coverage leads with this provision, and it’s easy to see why. When someone makes a legally significant decision that affects human rights and freedoms, they can’t rely only on conclusions produced by AI systems or AI-built information resources. AI can feed into the decision, but a person has to make it. That applies to loan denials, benefit eligibility, hiring rejections, licensing outcomes, and disciplinary action. In each case, someone needs to look at the AI output and own the final call. Insider Note: In AI governance engagements, teams rarely struggle to show that a review step exists. What they struggle to show is that the reviewer could disagree, and sometimes did. If a human clicks “approve” on every AI recommendation and nobody ever records an override, auditors will see automation with a signature on top. Build the override path and log when people use it, starting on day one. Powers of the Authorized State Body (Ministry of Digital Technologies) ZRU-1115 makes the Ministry of Digital Technologies the authorized state body for AI. Among its new jobs, it’s

You can get a SaaS company ready for a SOC 2 audit in six weeks, but you’ll feel every one of them. Most published timelines say three to six months. For a company with no project owner, no identity provider, and nothing written down, that’s about right. A cloud-native startup that already has the basics in place and can protect some time is a different story, and it can fit the work into six hard weeks. This plan walks through that route one week at a time. Each week has an owner, an hour estimate, and a clear test for when it’s finished. The free Google Sheet version turns the plan into a tracker you can hand out to owners and update in your weekly standup. Before you start, know what you’re signing up for. At the end of week 6 you’ll be audit-ready, which isn’t the same as holding a Type II report. Nobody can get you a Type II in six weeks. This is also the do-it-yourself route, and it takes a lot of hours. We’ll show you where those hours go and what the faster option looks like. Is Six Weeks Realistic for Your Company? Six weeks works when most of the plumbing already exists and your job is to formalize it, fill the gaps, and prove it all works. It falls apart when you’re building the foundations and documenting them at the same time. Go through this table honestly before you promise a customer a date. Six weeks is realistic if… Plan for 10 to 16 weeks if… Your product runs on a major cloud provider You host on-premise or across several data centers You already use an identity provider with SSO Every tool has its own login and password You have fewer than about 50 employees You have multiple offices, subsidiaries, or products in scope One named person owns the project with 10 to 15 hours a week Compliance is “everyone’s job,” so in practice nobody owns it An engineer can give you 15 to 20 hours in weeks 3 and 4 Engineering is fully committed to a launch You only need the Security criteria You need Availability, Confidentiality, or Privacy on day one Landing mostly in the right-hand column doesn’t mean you should throw the plan out. Give each week two weeks instead of one and follow the same order. What “SOC 2 Ready” Means at the End of Week 6 SOC 2 doesn’t give you a certificate. An independent CPA firm examines your controls against the AICPA Trust Services Criteria and writes a report, and which of the two report types you go for decides what you can show a buyer after week 6. A Type I report checks whether your controls are designed properly on a single date. Once you’re ready, a Type I audit can start almost right away. A Type II report checks whether those controls kept working over an observation period of at least three months, and usually six to twelve. Most enterprise procurement teams want Type II in the end. Being “ready” at the end of this plan means your in-scope controls are in place, you can pull evidence for any of them on request, and your auditor is booked. From there you either start a Type I audit or open your Type II observation window. Plenty of buyers will sign with a Type I report plus a letter from your auditor saying the Type II period is underway. Important: The Type II clock doesn’t start until your controls are running. If readiness slips by a week, your Type II report slips by a week too. Founders who tell a prospect “we’ll have SOC 2 in Q3” often forget this and end up renegotiating the deal. Before Week 1: Four Decisions to Make First Settle these before the clock starts. If you change any of them halfway through, you’ll redo work. Scope. Decide which systems, teams, and data the report covers. For most SaaS companies that’s the production environment, the code repository, the identity provider, customer data stores, and any support tools that touch customer data. Corporate systems that never see customer data can usually stay out. Trust Services Criteria. Security (also called the Common Criteria) is mandatory. Availability, Confidentiality, Processing Integrity, and Privacy are optional. Report type. Pick Type I if a deal is blocked right now and the buyer will accept it. If there’s no deadline, go straight to Type II. You’ll need it eventually, and skipping Type I saves you an audit fee. Owner and tooling. Name one person who’s accountable for the plan, and decide where your controls and evidence will live. The tooling choice gets its own section below. Pro Tip: Adding Criteria Only add optional criteria when a customer contract or security questionnaire asks for them. Each one brings more controls to set up and more evidence to collect, and you can widen the scope in next year’s audit. Spreadsheet or Compliance Software: Choosing Your Tracking Tool Every SOC 2 program needs a system of record, meaning one place where each control, its owner, its status, and its evidence live. You can run it yourself in a spreadsheet or a GRC platform, or have a consultant implement it for you. The right choice depends mostly on which report you’re after and how much of your team’s time you can spare. A spreadsheet is free and familiar. It also makes you understand your own environment before you automate any of it. For a Type I, or for a small team with a tight scope, a well-built spreadsheet can take you all the way to the audit. Axipro’s free GRC workbook for SOC 2 and ISO 27001 covers all 33 SOC 2 Common Criteria plus the optional criteria, with evidence, risk, policy, and gap trackers built in. It has no macros and opens straight in Google Sheets or Excel. A GRC platform connects to your cloud, identity provider, code repository, and HR system.