---
title: "SOC 2 Compliance Checklist: A Step-by-Step Guide - Axipro"
description: "Simplify SOC 2 compliance with our 12-step compliance checklist. Gain clarity and ensure your controls are effective and proven."
canonical: "https://axipro.co/soc-2-compliance-checklist/"
language: "en-US"
modified: "2026-03-30T10:31:46+00:00"
generator: "WordPress 7.1.2"
---

[Home](https://axipro.co)

/ [All Blog](https://axipro.co/category/blog/), [SOC-2](https://axipro.co/category/soc-2-2/)

/ SOC 2 Compliance Checklist: A Step-by-Step Guide

# SOC 2 Compliance Checklist: A Step-by-Step Guide

![Picture of Pedro Dias](https://axipro.co/wp-content/uploads/2026/05/pedro-passport-picture-scaled.jpg)

- Pedro Dias
- February 13, 2026

Copy Link

[SOC 2](https://axipro.co/soc-2) compliance can sometimes feel like a needlessly complex Pandora’s box of documentation. But it shouldn’t be. That’s why today, we’ll show you how to easily become compliant with our 12-step SOC 2 compliance checklist.
In its simplest form, all the SOC 2 sections point to the same question:

*Can you prove your controls work?*

This **SOC 2 Compliance Checklist** guides you through the process from scoping through audit completion for both **SOC 2 Type 1 and** **Type 2**. It is practical, auditor-aligned, and written for teams that want clarity rather than theory.

If you want the short version: SOC 2 is not about tools or paperwork. It is about **repeatable processes, clear ownership, and evidence that stands up to scrutiny**.

Reach SOC 2 Compliance in 6 Weeks or Less

Schedule Your Free SOC 2 Assessment Today

[Schedule](https://axipro.co/free-assessment/)

## **What is a SOC 2 compliance checklist?**

A SOC 2 compliance checklist is a structured roadmap that maps your internal controls to the AICPA Trust Services Criteria and prepares your organization for a Type 1 or Type 2 audit.

For a full breakdown of SOC 2 requirements, read our [detailed SOC 2 guide](https://axipro.co/what-is-soc-guide/).

## **How to Use This SOC 2 Compliance Checklist**

Think of this checklist as a **living roadmap**, not a one-time document. You should revisit it at four points: **before scoping, during readiness, throughout evidence collection, and after the audit** for continuous compliance.

## **Type 1 vs. Type 2: Which Checklist Items Change?**

The core checklist does not change dramatically between [Type 1 and Type 2](http://axipro.co/what-is-soc-guide). What changes is **time and proof**.

Type 1 evaluates whether controls are *designed correctly* at a specific point in time. Type 2 evaluates whether those same controls **operated effectively over an observation period**, usually 3, 6, or 12 months.

This means evidence for Type 2 must show **consistency**, such as quarterly access reviews, repeated vulnerability scans, and incident response tests that actually occurred.

## **Who Owns Each Workstream**

SOC 2 is cross-functional by design. Security may lead, but it cannot succeed alone.

Engineering typically owns secure SDLC, change management, and logging. IT owns IAM, endpoints, and device management. Legal and HR contribute policies, onboarding controls, and training. GRC or compliance coordinates risk assessment, evidence, and auditor communication.

The fastest SOC 2 projects have **named control owners** with deadlines, not shared responsibility.

## **What “Audit-Ready” Really Means**

Being audit-ready does not mean “we think we are secure.” It means you can produce **clear, dated, and traceable evidence** that maps directly to the [**Trust Services Criteria**](https://axipro.co/five-trust-service-criteria-soc-2-for-leaders/).

Auditors test design, then operation. They expect policies, tickets, screenshots, logs, and approvals. They also expect alignment. If your policy says quarterly, your evidence cannot show annual.

The **AICPA** provides the underlying standard, supported by **SSAE 18** and **AT-C 205**.

## **Pre-Checklist: Confirm You Actually Need SOC 2**

Not every company needs SOC 2 immediately. If your customers are SMBs, you may see lighter requirements. If you sell to enterprises, SOC 2 often becomes non-negotiable.

**Security questionnaires** are the strongest signal. When **prospects ask about penetration testing, access reviews, and incident response evidence, SOC 2 is usually the cleanest way to respond** at scale.

Alternatives like ISO 27001, PCI DSS, or HIPAA can be valid. But SOC 2 is uniquely **customer-facing**, especially in North America. ISO 27001 is excellent for global alignment, while SOC 2 maps directly to buyer trust.

## **The 12-Step Checklist**

![SOC 2 checklist Compliance](https://axipro.co/wp-content/uploads/elementor/thumbs/SOC-2-checklist-Compliance-rn5o07f86ls3r7t4zfv9fvy6uv6te8mjqhlpj9ps74.png)

## **Step 1- Define Scope**

Scoping mistakes cause more SOC 2 delays than any missing control.

Your scope must clearly define **the services you provide, the systems that support them, and the access controls**. Over-scoping increases cost and complexity. Under-scoping leads to auditor pushback.

In-scope systems usually include production cloud environments, CI/CD pipelines, support tooling, and identity providers. In-scope people include employees and contractors with access to customer data. Third parties are addressed as **Subservice organization**, using either the **Carve-out method** or **Inclusive method**.

Data classification and flows must identify PII, PHI, or payment data, and how it moves through systems.

**Action Plan for Scoping**

1. **Define the Service Commitment**
2. **List In-Scope Systems**
3. **Identify In-Scope People**
4. **Document Third Parties**
5. **Map Data Flows**
6. **Validate Scope with Leadership**

## **Step 2- Select the Trust Services Criteria**

All SOC 2 reports include **Security (Common Criteria)**. The others are optional but must be justified.

Availability focuses on uptime and disaster recovery. Confidentiality focuses on sensitive data protection. Processing Integrity focuses on system accuracy. Privacy applies when personal data obligations are central.

Your report must document why each criterion is included or excluded. Auditors look closely at this rationale.

**Trust Service Criteria Action Plan**

1. **Confirm Security (Mandatory)**
2. **Assess Optional Criteria**
3. **Document Inclusion Rationale**
4. **Obtain Executive Sign-Off**

## **Step 3- Choose the Audit Path and Timeline**

Most teams benefit from a readiness assessment before audit. This is often referred to as a **Readiness assessment** or **Gap analysis**.

Type 1 audits can be completed in weeks once controls are ready. Type 2 timelines depend on the observation period. Six months is the most common balance between speed and credibility.

Define control owners early and create an evidence calendar. Late evidence is the enemy of clean audits.

**Audit Path and Timeline Action Plan**

1. **Conduct Readiness or Gap Assessment**
2. **Choose Audit Type**
3. **Set Observation Period (Type 2)**
4. **Assign Control Owners**
5. **Build Evidence Calendar**

## **Step 4- Pick an Auditor and Define the Engagement**

Choose a CPA firm with real SOC 2 experience in your industry. Responsiveness matters more than brand name.

Confirm standards, testing approach, sampling expectations, and how subservice organizations are treated. The engagement letter should clearly state scope, period, and deliverables. A clear **PBC list** process avoids confusion later.

**Action plan for finding an auditor.**

1. **Shortlist CPA Firms**
2. **Review Testing Approach**
3. **Clarify Subservice Treatment**
4. **Finalize Engagement Letter**
5. **Request Preliminary PBC List**

## **Step 5- Perform a SOC 2 Gap Analysis**

Map existing controls to the Trust Services Criteria. Missing policies, undocumented processes, and inconsistent evidence usually surface here.

Prioritize high-risk gaps first. Document known exceptions and compensating controls honestly. Auditors prefer transparency over perfection.

**Gap Analysis Action Plan:**

1. **Map Controls to Criteria**
2. **Identify Missing Controls**
3. **Prioritize by Risk**
4. **Document Compensating Controls**

## **Step 6- Build the Policy and Governance Foundation**

Policies should reflect reality. Information security, access control, change management, incident response, vendor risk management, and BCDR must all exist, be approved, and be followed.

If Privacy is in scope, privacy notices, data handling, and retention policies must align with actual practices.

**Governance Action Plan**

1. **Draft Core Policies**
2. **Align Policy to Reality**
3. **Obtain Formal Approval**
4. **Train Staff**

## **Step 7- Implement Security (Common Criteria) Controls**

This is where most effort goes. **IAM**, **MFA**, **SSO**, and **RBAC** must be enforced, not optional. Logging, monitoring, vulnerability scanning, and patch management must be operational.

Auditors expect [encryption](https://axipro.co/soc-2-encryption-requirements/) in transit and at rest, typically supported by **KMS**. Secure SDLC, change management, incident response, risk assessment, vendor reviews, and physical security all fall under this umbrella.

**Common Control Implementation Action Plan**

1. **Enforce Identity Controls**
2. **Enable Monitoring**
3. **Implement Vulnerability Management**
4. **Encrypt Data**
5. **Operationalize Secure SDLC**
6. **Run Risk Assessment**

![trust service criteria](https://axipro.co/wp-content/uploads/2025/02/trust-service-criteria-768x432.png)

## **Step 8- Availability, Confidentiality, Processing Integrity, Privacy**

Only implement what is in scope. Availability requires uptime definitions, monitoring, and tested disaster recovery. Confidentiality focuses on data handling and disposal. Processing Integrity requires evidence that systems do what you promise customers. Privacy requires DSAR handling, consent, and cross-border controls.

### **Availability**

1. **Define uptime commitments.**
2. **Document monitoring thresholds.**
3. **Test BCDR annually.**
4. **Record test results and improvements.**

### **Confidentiality**

1. **Classify confidential data.**
2. **Restrict access via RBAC.**
3. **Define disposal procedures.**
4. **Validate encryption controls.**

### **Processing Integrity**

1. **Document system processing controls.**
2. **Define input validation mechanisms.**
3. **Monitor output accuracy.**
4. **Track customer issue resolution.**

### **Privacy**

1. **Publish privacy notice aligned with practice.**
2. **Implement DSAR handling process.**
3. **Define data retention schedule.**
4. **Control cross-border transfers.**

## **Step 9- Build the Evidence Package**

Auditors test evidence, not intent. They expect a clear **System description**, control narratives, access reviews, change tickets, incident records, vulnerability scans, vendor SOC reports, training logs, and BCDR test results.

Evidence must be complete, dated, and traceable.

**Evidence Package Action Plan**

1. **Draft System Description**
2. **Collect Control Evidence**
3. **Ensure Traceability**

## **Step 10 — Run Internal Reviews**

Before the auditor looks, you should. Control owners should sign off. Exceptions should be documented with root cause and corrective action. Management review is not optional.

**Internal Review Action Plan**

1. **Control Owner Sign-Off**
2. **Document Exceptions**
3. **Management Review**

## **Step 11 — Complete the Audit**

Expect walkthroughs, sampling, and follow-up questions. Review the draft report carefully, especially scope language and subservice organization descriptions.

**Audit Action Plan**

1. **Prepare for Walkthroughs**
2. **Respond to Sampling Requests Quickly**
3. **Review Draft Report Carefully**

## **Step 12 — Maintain Continuous SOC 2 Compliance**

SOC 2 is not annual busywork. Continuous monitoring, periodic access reviews, quarterly vulnerability scans, annual risk assessments, and vendor re-reviews keep you audit-ready.

Teams that treat SOC 2 as a one-time project struggle with every renewal.

**Maintaining Compliance Action Plan**

1. **Schedule Recurring Reviews**
2. **Monitor Vendor Changes**
3. **Automate Evidence Collection**
4. **Track Metrics**
5. **Embed Compliance into Operations**

## **Ready to Use This Checklist in Practice?**

If you want to turn this SOC 2 compliance checklist into a **clear plan with owners, timelines, and auditor-ready evidence**, Axipro can help.

Our **Achievement Plan** guides teams from scope to SOC 2 readiness in as little as six weeks, combining human expertise with the right [automation tools](https://axipro.co/drata-soc-2-guide/). Whether you need a readiness assessment, a full Type 1 or Type 2 audit, or help maintaining compliance, we simplify the process so your team can focus on growth.

**Book a SOC 2 readiness call or request a checklist walkthrough today, and move from “working on compliance” to confidently audit-ready.**

Reach SOC 2 Compliance in 6 Weeks or Less

Schedule Your Free SOC 2 Assessment Today

[Schedule](https://axipro.co/free-assessment/)

Is this SOC 2 compliance checklist enough to pass an audit?

The checklist is designed to align with the AICPA Trust Services Criteria and reflects what auditors test in both Type 1 and Type 2 engagements. However, a checklist alone does not guarantee a clean report. Success depends on Accurate scoping, Clear control ownership, Proper documentation, Consistent evidence over time, and Management oversight. The checklist provides structure. Execution determines the outcome.

How should we use this checklist internally?

This checklist should function as a project management framework rather than a static document. Organizations should assign ownership for each step, define deadlines, and maintain an evidence tracker alongside the checklist. During readiness, it should be reviewed regularly to monitor progress and identify blockers. After certification, it should evolve into a quarterly governance tool to maintain continuous compliance rather than being archived as a completed project.

What is the most commonly overlooked step in the checklist?

Scoping is the most frequently underestimated step. Poor scope definition can result in expanded audit testing, increased costs, and delays due to auditor pushback. Another commonly overlooked area is evidence preparation. Many organizations implement controls but fail to collect clear, dated, and traceable documentation. Even well-designed controls can create audit friction if evidence is incomplete or inconsistent.

Can we exclude optional Trust Services Criteria to simplify the checklist?

Yes, but exclusions must be intentional and justified. Security, also known as the Common Criteria, is mandatory in every SOC 2 report. The inclusion of Availability, Confidentiality, Processing Integrity, or Privacy depends on customer commitments, regulatory requirements, contractual obligations, and data sensitivity. Auditors expect a documented rationale explaining why each optional criterion was included or excluded. Simply omitting criteria without explanation can raise concerns during review.

Who should own the checklist within the organization?

SOC 2 is inherently cross-functional. While security or GRC teams often coordinate the effort, engineering, IT, HR, legal, and executive leadership all play essential roles. The checklist works most effectively when each control area has a clearly defined owner with accountability for implementation, documentation, and ongoing monitoring. Shared responsibility without defined ownership frequently leads to gaps and delays.

How do we know when we are truly audit-ready?

You are audit-ready when every control has a designated owner, policies are formally approved and consistently followed, evidence is complete and traceable, and your system description accurately reflects your environment. Management should have reviewed and signed off on the program before the auditor begins testing. If your team can confidently walk an auditor through each checklist step with supporting documentation, you are prepared for a structured and efficient audit experience.

Axipro Author

![Picture of Pedro Dias](https://axipro.co/wp-content/uploads/2026/05/pedro-passport-picture-scaled.jpg)

### 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.

- February 13, 2026
- [All Blog](https://axipro.co/category/blog/), [SOC-2](https://axipro.co/category/soc-2-2/)

Copy Link

## Blog Highlights

## Explore More Articles

[Read More Blogs](https://axipro.co/blog/)

- [Vanta](https://axipro.co/category/vanta/)

- October 3, 2026

#### [Best Vanta Deployment Service (2026): 7 Partners Ranked](https://axipro.co/best-vanta-deployment-service/)

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

[Read more](https://axipro.co/best-vanta-deployment-service/)

- [ISO-27001](https://axipro.co/category/iso-27001-2/)

- September 29, 2026

#### [ISO 27001 Consultant vs. Software: Which Is Faster?](https://axipro.co/iso-27001-consultant-vs-software/)

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

[Read more](https://axipro.co/iso-27001-consultant-vs-software/)

- [AI Security](https://axipro.co/category/ai-security/)

- September 27, 2026

#### [Uzbekistan AI Regulation 2026: Law ZRU-1115 Explained](https://axipro.co/uzbekistan-ai-regulation/)

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

[Read more](https://axipro.co/uzbekistan-ai-regulation/)

WhatsApp us