/ ISO 27001 Internal Audit Explained: Key Steps and Best Practices

ISO 27001 Internal Audit Explained: Key Steps and Best Practices

Achieving ISO 27001 certification signifies excellence in information security management, demonstrating your organization’s dedication to protecting sensitive data. However, this process involves careful steps, with one of the most important being the internal audit. This crucial phase verifies that your Information Security Management System (ISMS) meets ISO 27001 standards and is strong enough to reduce risks.

Watch the Loom Video for a detailed explanation of our internal audit services, check out our Loom video, where our Principal Consultant Ali Hayat breaks down the process step-by-step and shares tips for seamless ISO 27001 compliance. Click here to watch the Loom video.

ISO 27001 Internal Audit

What is an ISO 27001 Internal Audit?

 

An ISO 27001 internal audit is a structured review of your ISMS to check its compliance with the standard’s requirements. Unlike external audits done by certification bodies, internal audits are performed by the organization itself or by a third-party auditor to find gaps, evaluate risks, and ensure readiness for certification.

The main goal of an internal audit is to ensure that your ISMS meets ISO 27001 requirements and effectively reduces risks. It also offers a chance to find areas for improvement and strengthen your organization’s security efforts. By conducting a thorough gap analysis during this stage, you help set your organization up for success in the certification process.

ISO 27001 Internal Audit Requirements: Understanding Clause 9.2

 

Clause 9.2 of ISO 27001:2022 establishes the specific requirements for internal audits, forming the backbone of audit governance. This section mandates that organizations establish and implement audit programs to evaluate the effectiveness of their ISMS at planned intervals.

The standard specifies several critical requirements within Clause 9.2:

Clause 9.2.1 – Audit Program Requirements: Organizations must define audit objectives, scope, frequency, and methodologies. Your audit program should establish criteria against which the ISMS will be evaluated, ensuring that all relevant information security controls are systematically reviewed over a defined period.

Clause 9.2.2 – Auditor Competence and Objectivity: This is perhaps the most critical requirement. Auditors must be objective, impartial, and free from conflict of interest. The standard explicitly prohibits auditors from evaluating areas for which they hold direct responsibility, as this compromises independence and undermines audit credibility.

To meet Clause 9.2.2, auditors should possess documented competence in ISO 27001 standards and audit methodologies. Many organizations require auditors to hold certifications such as Certified Information Systems Auditor (CISA) or ISO 27001 Lead Auditor. Reference to ISO 19011 – Guidelines for auditing management systems – provides additional guidance on selecting, evaluating, and managing auditors.

Who Can Perform an ISO 27001 Internal Audit?

Internal audits can be carried out by your organization’s own internal audit team or outsourced to a third-party auditor or an ISO 27001 consulting firm. Unlike external certification audits, you can choose the most suitable approach for your organization. However, it’s crucial to follow Clause 9.2(e) of the ISO 27001 standard, which stresses the importance of selecting an internal auditor who is objective and impartial. This means avoiding any potential conflicts of interest—specifically, the auditor should not have been involved in developing the ISMS or in operating or monitoring any of the controls under review. The reason for this requirement is simple: reviewing your own work can undermine objectivity and hinder a thorough evaluation.

Essential Auditor Qualifications

When selecting an auditor, ensure they meet the following criteria:

In-Depth ISO 27001 Knowledge: Auditors must understand the standard’s requirements, Annex A controls, and how they apply to your organization’s context.

Audit Methodology Expertise: Knowledge of audit planning, sampling techniques, evidence collection, and report writing.

Relevant Certifications: ISO 27001 Lead Auditor (IRCA or equivalent), CISA, or similar credentials demonstrate formal competence.

Industry Experience: Understanding of your sector’s specific security challenges and regulatory landscape adds significant value.

If internal expertise is limited, hiring an experienced third-party auditor or consulting firm can provide a fresh, unbiased perspective and valuable insights tailored to your organization’s unique environment.

Internal Audit vs External Certification Audit: Key Differences

Understanding the distinction between internal and external audits is crucial for effective compliance strategy. While both serve important roles, they differ significantly in purpose, scope, and outcome.

Aspect

Internal Audit

External Certification Audit

Conducted By

Organization (internal or contracted third party)

Accredited certification body

Primary Purpose

Identify gaps and prepare for certification

Verify compliance and issue certificate

Focus

Detailed improvement; addresses specific findings

Overall conformance; verifies readiness

Flexibility

High – customize scope and approach

Low – standardized audit procedures

 

Internal audits serve as your organization’s opportunity to address vulnerabilities proactively before the certification audit. They foster a culture of continuous improvement and ensure that any gaps are remediated well in advance. This strategic advantage makes internal audits invaluable in the certification journey.

How to Conduct an ISO 27001 Internal Audit: Key Phases

Conducting an ISO 27001 internal audit involves a series of well-defined steps to ensure that your Information Security Management System (ISMS) is thoroughly evaluated. Below is a detailed breakdown of the process:

Phase 1: Determine the Scope of the Audit

The first step is to clearly outline the audit’s scope, specifying the systems, functions, people, and processes that will be assessed. This scope ensures the audit comprehensively covers all necessary areas to meet compliance objectives. Defining the boundaries early on helps the auditor focus on the most relevant elements of the ISMS, particularly considering your organization’s specific ISMS scope boundaries and the applicability of controls.

Phase 2: Documentation Review

Before proceeding with on-site evaluations, the internal auditor will review all key ISMS documents to verify that they align with ISO 27001 requirements. An effective ISMS requires a well-defined scope, a comprehensive Statement of Applicability (SoA), a robust Information Security Policy, a thorough risk assessment and treatment plan, and clear definitions of responsibilities. Additionally, identifying individuals responsible for implementing and operating controls, and documenting evidence of control implementation, provides valuable context for the field review.

Phase 3: Management Review and Approval

The audit plan must be reviewed and approved by senior management. Regular meetings should be scheduled to set expectations, discuss timelines, and maintain open communication. Management also plays a critical role in reviewing the internal audit findings, collaborating with the auditor to assess the organization’s readiness for an external certification audit, and ensuring that all significant issues are addressed beforehand.

Phase 4: Pre-Audit Preparation

Preparation is critical for a successful audit. This phase includes developing detailed audit checklists, identifying key personnel for interviews, scheduling on-site activities, and gathering necessary documentation. A well-prepared audit checklist aligned with ISO 27001 requirements and your organization’s context ensures comprehensive coverage and consistency.

Phase 5: Conducting the Field Review

The field review is the core of the internal audit process. During this phase, the auditor evaluates the ISMS through multiple evaluation methods, gathering evidence to support findings and determine the effectiveness of controls.

Audit Tests: Assessing controls to ensure they are effectively implemented and functioning as intended. This involves testing a sample of control activities to verify control effectiveness.

Audit Evidence Collection: Reviewing documented information and audit trails to confirm compliance and identify gaps. Evidence should support all audit conclusions.

Staff Interviews: Engaging with employees to gauge their understanding of and adherence to ISMS policies. These interviews provide crucial insight into whether controls function as designed in practice.

Observations and Documentation: Recording findings, highlighting areas of non-conformity, and identifying strengths. Clear documentation enables transparent reporting and actionable recommendations.

This comprehensive review enables the auditor to pinpoint what’s working well and what needs improvement, providing a clear roadmap for corrective actions.

ISO 27001 Internal Audit Checklist: Essential Items

A well-designed audit checklist is fundamental to conducting a thorough and consistent internal audit. The checklist should cover all ISO 27001 requirements and be tailored to your organization’s context. Below are the essential categories and items to include:

Organizational Context (Clauses 4.1-4.3): Verify that the organization understands its internal and external context, interested parties, and scope of the ISMS.

Leadership and Governance (Clauses 5-6): Confirm management commitment, information security policy, allocation of roles and responsibilities, and evidence of management review.

Planning (Clause 6): Assess risk assessment methodology, risk treatment plans, and management of information security objectives.

Support and Operation (Clauses 7-8): Check resource availability, competence assessments, awareness and training programs, and operational control implementation.

Performance Evaluation (Clause 9): Review monitoring and measurement of controls, incident management procedures, and evidence that internal audit has been appropriately planned and conducted.

Improvement (Clause 10): Evaluate management of non-conformities, corrective action effectiveness, and documented information control.

Incorporating Annex A controls into your checklist ensures that all 114 control objectives are evaluated within the scope of your ISMS. Many organizations create control-specific evaluation criteria linked to this comprehensive checklist.

Addressing Non-Conformities

 

Non-conformities can range from minor documentation gaps to critical security flaws. Identifying and addressing these issues promptly is essential to maintain the integrity of your ISMS. By developing comprehensive corrective action plans and monitoring their implementation, organizations can ensure continuous improvement and long-term compliance with ISO 27001 standards.

 

Common ISO 27001 Internal Audit Findings

Understanding typical non-conformities helps organizations proactively address vulnerabilities. Here are the most frequently encountered findings:

Documentation Gaps: Missing, incomplete, or outdated policies, procedures, or records. For example, risk assessment documentation that doesn’t clearly link to implemented controls.

Access Control Deficiencies: Inadequate user access reviews, orphaned accounts, lack of segregation of duties, or insufficient multi-factor authentication implementation.

Incident Management Issues: Incomplete incident logs, lack of timely incident classification, or insufficient root cause analysis documentation.

Training and Awareness Gaps: Insufficient security awareness training records, lack of role-specific training, or no evidence of competency assessment.

Change Management Failures: Changes implemented without proper authorization, risk assessment, or documented approvals.

Backup and Recovery Defects: Untested backup procedures, unclear recovery objectives, or lack of documented restoration testing records.

The Corrective Action Process

Addressing non-conformities requires a structured, documented approach. The standard corrective action process includes:

Classification: Categorize each finding as Major (major risk or complete absence of a control) or Minor (temporary deviation or incomplete implementation that doesn’t significantly impact security).

Root Cause Analysis: Investigate why the non-conformity occurred—whether due to lack of awareness, insufficient resources, or inadequate procedures.

Corrective Action Plan: Develop specific, measurable actions with defined timelines and responsible parties. Plans should address root causes, not just symptoms.

Implementation Monitoring: Track progress toward completion and verify that actions are implemented as planned.

Effectiveness Verification: Re-audit completed actions to confirm they have resolved the non-conformity and prevented recurrence.

Major non-conformities must be resolved before certification, while minor findings require documented action plans with appropriate timelines. Organizations should also review common mistakes during ISO 27001 implementation to avoid repeating the same errors across multiple audits.

Timeline of Internal Audits

A successful ISO 27001 internal audit requires careful planning and execution. Here’s a detailed breakdown of the key phases and estimated time required for each, though actual duration depends on organization size, ISMS complexity, and control maturity.

Planning (0.5 days): Define the audit scope, objectives, and methodology. Develop an audit plan, including the schedule and resource allocation. This phase establishes the foundation for all subsequent work.

Preparation (0.5 days): Review relevant documentation, develop audit checklists, and identify key personnel to be interviewed. Preparation ensures efficiency during field activities.

Audit Execution (1-2 weeks): Conduct interviews, document reviews, and observations. Verify the implementation of controls and procedures. Identify non-conformities and opportunities for improvement. This phase is the most time-intensive and involves active on-site engagement.

Reporting (1 day): Prepare a detailed audit report, including findings, recommendations, and corrective action requirements. Review the report with management to ensure accuracy and completeness.

Closure (1 day): Finalize the audit report and distribute it to relevant stakeholders. Monitor the implementation of corrective actions. Schedule follow-up audits to verify the effectiveness of corrective actions and ensure sustainable improvement.

The audit execution timeline varies significantly based on organization size. A small organization with a well-defined scope might complete field activities in 3-5 days, while a larger enterprise with multiple business units could require 2-3 weeks. The complexity of your ISMS and the maturity of your existing controls also play significant roles in determining realistic timelines.

ISO 27001 Internal Audit Timeline

Benefits of a Well-Executed Internal Audit

Conducting a comprehensive internal audit provides key benefits for organizations aiming for ISO 27001 certification:

Certification Readiness: Identifying and fixing gaps before the certification audit greatly boosts the chances of passing on the first attempt and minimizes the need for re-audits.

Enhanced Security: Internal audits reinforce your ISMS by verifying control effectiveness, reducing weaknesses, and increasing your organization’s resilience to security risks.

Operational Efficiency: The process reveals inefficiencies and overlaps, helping you streamline workflows and better allocate resources for security efforts.

Stakeholder Trust: Showcasing strong, documented security practices through internal audits builds confidence with clients, partners, regulators, and other stakeholders. This often provides a competitive edge and supports business growth.

Culture of Improvement: Regular audits foster a mindset of continuous enhancement, motivating ongoing review and improvement of security measures beyond mere compliance.

Understanding Your Path to Certification with Axipro

 

Axipro’s internal audit services are designed to simplify the ISO 27001 compliance process. Our team of experienced auditors conducts thorough assessments, identifying gaps and providing actionable insights to strengthen your ISMS.

We tailor our approach to your organization’s unique needs, offering guidance from planning to corrective actions. With Axipro, you can streamline your internal audit process, reduce complexity, and achieve ISO 27001 certification confidently.

Conclusion

 

An ISO 27001 internal audit is a cornerstone of effective information security management. It ensures compliance, enhances security practices, and prepares your organization for certification success. By following a structured approach and leveraging expert support, you can make the audit process smooth and impactful.

Frequently Asked Questions

What is the purpose of an ISO 27001 internal audit?

The primary purpose is to verify that your ISMS aligns with ISO 27001 standards, identify gaps and non-conformities before external certification, ensure controls are effectively operating, and prepare the organization for successful certification audit.

Internal audits can be conducted by your organization’s internal audit team or outsourced to qualified third-party auditors or consulting firms. However, auditors must be objective, impartial, and free from conflicts of interest as required by Clause 9.2.

After completion, the audit report is distributed to management. Non-conformities are categorized and corrective action plans are developed. Organizations then implement and monitor these corrections. Follow-up audits verify the effectiveness of corrective actions. Once major non-conformities are resolved, the organization proceeds to schedule the external certification audit.

ISO 27001 requires audits at planned intervals, typically at least annually for certified organizations. Pre-certification organizations should conduct audits multiple times (3-6 months before certification). Focused audits can be conducted quarterly or as-needed after significant changes.

Simplify your ISO 27001 compliance journey with Axipro’s expert internal audit services.

Axipro Author

Picture of Abeera Zainab

Abeera Zainab

Blog Highlights

Explore More Articles

Vanta can tell you a control is failing within the hour. It cannot rewrite your access review process, decide which systems belong in audit scope, or explain to a CPA why a test that shows red is actually fine. That work falls to people, and choosing the right ones is the difference between a 6-week path to audit readiness and a 6-month slog that ends with your Vanta subscription renewing before you have a report. This guide ranks the 7 best Vanta deployment services for 2026, explains what each one is good at, and covers what most comparison pages skip: how long this really takes, what it costs, and how to spot a partner who’ll hand you a half-configured platform and disappear. What Is a Vanta Deployment Service? A Vanta deployment service is a hands-on engagement where a specialist firm sets up, configures, and operationalizes Vanta so your company reaches audit readiness for one or more compliance frameworks. Vanta itself is a compliance automation and trust management platform: it connects to your cloud, identity provider, code repositories, HR system, and endpoints, then runs automated tests and maps the evidence to frameworks such as SOC 2, ISO 27001, HIPAA, and GDPR. The platform automates evidence collection and continuous monitoring. It doesn’t put controls in place for you. A deployment partner handles the judgment work around the tool: scoping, gap analysis, control mapping, policy writing, risk assessment, remediation of failing tests, and coordination with the audit firm. The best partners also stay on after the audit, because a Vanta instance nobody owns degrades fast. Worth Knowing: Vanta is a software vendor, not an auditor. Vanta is a software vendor, not an auditor. Your SOC 2 report still comes from a licensed CPA firm under AICPA attestation standards, and your ISO 27001 certificate comes from an accredited certification body. A deployment partner sits between the platform and the auditor. 1. Axipro Best for: SaaS and technology companies that want Vanta deployed, controls implemented, and the audit delivered by one accountable team, fast. Axipro is an authorized Vanta partner and a Drata Elite Partner, so its team works inside both leading compliance automation platforms every day. Founded in 2023, it has served 200+ clients from offices in the US, UK, and Bahrain, with a 100% audit success rate across 200+ certified clients. What puts Axipro first is scope. Most Vanta partners configure the platform and leave control implementation to you. Axipro’s Achievement Plan covers the whole path: kick-off and Vanta setup, gap analysis, a full policy and procedure suite, risk assessment and treatment, control implementation, vulnerability scanning, an internal audit, and external audit facilitation with an independent auditor. Clients get a dedicated infosec team over Slack, and the Achievement Plan comes with guaranteed certification. The other reason is speed. Axipro typically reaches SOC 2 readiness in around four weeks and ISO 27001 certification readiness in as little as six. It supports 20+ frameworks, including SOC 2, ISO 27001, HIPAA, PCI DSS, GDPR, CMMC, ISO 42001, and the EU AI Act, plus Gulf frameworks such as NCA ECC and SAMA CSF that most US-only partners cannot cover. Teams that want to test the relationship first can start with the free 30-day Compliance Accelerator Plan, which includes Vanta setup, gap analysis, and policy documentation, and continue into ongoing vCISO and continuous monitoring through the Trust Assurance Plan after certification. Watch for: Axipro is built for companies that want the work done for them. Teams that want a light-touch coaching engagement and plan to run the program in-house will use only part of what it offers. 2. Control and Function Best for: US SaaS companies of roughly 10 to 60 people that want SOC 2 and ISO 27001 run as one fixed-price project. Control and Function is a Denver-based consultancy built around fixed-scope, fixed-price readiness for small SaaS teams that have no compliance department. Its sweet spot is the dual-framework engagement: building SOC 2 and ISO 27001 from one shared control set rather than running two projects back to back. It also covers HIPAA for healthtech and maps ed-tech requirements such as FERPA and HECVAT. The firm is platform-neutral, so it works inside Vanta rather than reselling it, and it is explicit about handing off cleanly to an independent auditor. It’s also one of the few firms here that publishes prices, with readiness coaching starting around $8,000 and full readiness around $15,000. Watch for: The framework range is narrower than larger partners. Companies that need PCI DSS, CMMC, or international frameworks will need a second provider. 3. Neutral Partners Best for: Growing companies that need managed GRC across SOC 2, ISO 27001, CMMC, and FedRAMP without hiring an internal compliance team. Neutral Partners, based in Miami, runs a managed GRC model. It builds and documents the compliance program, tests it through internal audits, and then hands off to the relevant independent assessor: a CPA firm for SOC 2, a certification body for ISO 27001, or a C3PAO for CMMC. It never issues the certificate itself, which keeps the independence question simple. Its framework coverage leans toward regulated and government-adjacent work, including CMMC, FedRAMP, PCI DSS, HIPAA, and HITRUST. That makes it worth a look for defense suppliers and companies selling to the public sector. Watch for: Vanta isn’t its main focus. Ask for recent Vanta deployment examples in your framework before signing. 4. Kobalt.io Best for: Small and mid-sized businesses that want Vanta plus managed security operations. Canada-based Kobalt.io markets itself as one of Vanta’s leading global service partners. Its Vanta practice covers policy and control development inside the platform, custom control mapping where standard controls do not fit, and an applicability review of Vanta’s tests. The broader appeal is its managed security services, which suit companies that want compliance and security operations from the same provider. 5. AuditPeak Best for: Startups that want a readiness and audit-preparation partner focused narrowly on SOC 2. AuditPeak focuses on SOC 2 audit readiness for early-stage companies working in

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