/

  / IAM Solutions Compared: Top Providers in 2026

IAM Solutions Compared: Top Providers in 2026

The identity and access management market will pass $25 billion in 2026, and it is crowded with vendors that all make the same promise: the right people get the right access to the right resources at the right time. The hard part of any IAM solutions comparison is not finding capable products.

It is that the leading platforms were each built to solve a different problem first, then expanded outward. Okta started with access. SailPoint started with governance. CyberArk started with privilege. Choose by brand reputation alone, and you risk buying a governance tool to solve an access problem, or paying enterprise prices for capabilities a mid-market team will never switch on.

This guide compares the major providers by what they are actually good at, then walks through how to match one to your environment.

IAM Solutions Comparison 2026

What Is an IAM Solution?

An IAM solution is the set of technologies that manages digital identities and controls what each identity can access. NIST frames the goal simply: ensure the right people and things have the right access to the right resources at the right time. In practice, that breaks into a few core functions: authenticating users (proving they are who they claim), authorizing them (deciding what they may do), and administering the account lifecycle as people join, move, and leave.

The category splits into recognizable disciplines.

  • Access management (AM) handles authentication and single sign-on.
  • Identity governance and administration (IGA) handles who should have access and proves it to auditors.
  • Privileged access management (PAM) protects the high-value accounts that can change infrastructure or read sensitive data.

Most vendors now sell across these lines, but few are equally strong in all of them. That gap is the whole reason a comparison is worth doing.

Reach SOC 2 Compliance in 6 Weeks or Less

Schedule Your Free SOC 2 Assessment Today

Why Comparing IAM Solutions Matters in 2026

Identity is now the primary attack surface. Stolen credentials and phishing remain among the top routes attackers use to get inside, which is why identity spending keeps climbing even when other security budgets flatten. The IAM market reached roughly $22 billion in 2025 and is on track for about $25 billion in 2026, growing near 15 percent a year, according to Fortune Business Insights.

Two shifts make the comparison harder than it was a few years ago. First, the workforce went hybrid and cloud-first, so identity has to span on-prem systems, SaaS, and multi-cloud at once. Second, machine identities exploded. Your choice of platform now locks in how well you can govern not just employees but the service accounts, tokens, and AI agents multiplying across your environment.

Gartner has reported that roughly 48 percent of organizations still lack a written IAM strategy — a serious problem, because a comparison is worth little if it is not anchored to documented requirements. Vendor demos are designed to make every product look like the obvious answer.

IAM Solutions Comparison Checklist

Key Criteria for Comparing IAM Solutions

A useful comparison rests on a consistent scorecard rather than the feature checklists vendors supply. The criteria below are the ones that tend to decide satisfaction two years after purchase.

Core Identity and Access Capabilities

Start with the fundamentals: single sign-on, multi-factor authentication, lifecycle provisioning and deprovisioning, and access certification. The differentiator in 2026 is adaptive, risk-based authentication that weighs device, location, and behavior before granting access, alongside phishing-resistant methods such as passkeys. A tool that only does password-plus-OTP is already behind.

Deployment Options: Cloud-Native, Hybrid, and On-Premises

Deployment model shapes cost, speed, and control. Cloud-native SaaS platforms deploy fastest and shift maintenance to the vendor. On-prem suits organizations with strict data-residency rules or deep legacy systems. Hybrid is the common reality, and the question to ask is how gracefully a platform bridges old and new — not whether it claims to.

Integration Capabilities with Existing Infrastructure

An IAM platform is only as good as its connectors. Look for prebuilt integrations with your core systems, directory services, HR platforms, and major SaaS apps, plus open standards support: SAML, OIDC, SCIM, and increasingly standards for continuous authorization. A thin connector catalog means custom engineering, which is where budgets quietly disappear.

Scalability for Enterprise vs. Mid-Market Organizations

Scale is not only user count. It is the number of applications, directories, and identity types a platform can govern without performance or administrative strain. Enterprise suites assume a dedicated identity team. Mid-market tools assume a stretched IT generalist. Buying the wrong tier means either paying for unused complexity or hitting a ceiling within two years.

Pricing Models and Total Cost of Ownership

Headline per-user pricing rarely reflects real cost. Implementation, professional services, connector licensing, premium support, and the internal staff time to run the platform often exceed the subscription itself.

Compliance and Audit Support

For regulated industries, audit support is a core feature, not a bonus. Strong platforms run access certification campaigns, segregation-of-duties checks, and audit-ready reports aligned with frameworks such as SOX, HIPAA, ISO 27001, and PCI DSS. The NIST Digital Identity Guidelines (SP 800-63, revised in 2025) are a useful reference for the assurance levels your authentication should meet.

Vendor Support, Stability, and Roadmap

You are buying a multi-year relationship. Financial stability, support quality, and a credible roadmap matter as much as today’s feature set, especially as the market consolidates and converges. A vendor that gets acquired or pivots can leave you maintaining a product on a slow decline.

Pro Tip: Comparing Quotes

When you compare quotes, normalize them to a three-year total cost of ownership that includes implementation and at least one major version upgrade. Vendors that look cheap per seat sometimes carry the heaviest services bill, and the gap usually shows up in year one, not at signing.

IAM Solutions Compared: The Leading Providers

The vendors below dominate enterprise shortlists. Each entry notes the problem the platform solves best — which is the most reliable way to read past the marketing.

Okta Workforce Identity Cloud

Okta is the largest independent identity vendor and was named a Leader in the 2025 Gartner Magic Quadrant for Access Management for the ninth straight year. Its strength is breadth of integration: thousands of prebuilt connectors and a neutral, vendor-agnostic stance make it a natural hub for organizations running a mix of clouds and SaaS. Workforce access and single sign-on are its core. Governance and privileged access are newer additions and less mature than the specialists’.

Microsoft Entra ID

Entra ID, formerly Azure AD, is the default identity layer for any organization committed to Microsoft 365 and Azure, sharing that nine-consecutive-year Leader position in the 2025 Access Management Magic Quadrant. Its advantage is bundling and tight integration with the Microsoft estate, which makes the economics hard to beat for existing customers. The trade-off is that its best experience assumes a Microsoft-centric world; heterogeneous environments lose some of the seamlessness.

SailPoint IdentityIQ

SailPoint is the reference name in identity governance. IdentityIQ, and its SaaS sibling Identity Security Cloud, is built for complex enterprises that must govern access across structured and unstructured data, prove compliance, and automate certifications at scale. It carries depth that mid-market teams rarely need, and it expects a real governance program and the staff to run it.

CyberArk

CyberArk is the privileged access leader, repeatedly placed in the Leaders quadrant of Gartner’s PAM Magic Quadrant. Its heritage is securing the most dangerous accounts: domain admins, root, service credentials, and now machine and AI-agent secrets. Organizations with serious privilege risk or regulatory pressure on admin access tend to standardize here. It is a specialist platform first, broadening into wider identity security.

Ping Identity

Ping Identity is an enterprise-grade access management and federation platform, recognized as a Leader in the 2025 Access Management Magic Quadrant. It appeals to large organizations with demanding customer-identity (CIAM) and complex federation requirements, and to teams that want fine-grained control and orchestration. It rewards identity maturity and can be heavier to operate than turnkey SaaS.

IBM Security Verify

IBM Security Verify offers a broad identity suite spanning access, governance, and risk, with particular traction in large hybrid enterprises already invested in IBM. Its strength is breadth and fit with complex on-prem-plus-cloud estates. Buyers outside the IBM ecosystem tend to weigh it against more focused competitors.

Saviynt

Saviynt is a cloud-native challenger that converges governance and privileged access on a single platform. Named a Challenger in the 2025 Gartner PAM Magic Quadrant while holding a strong governance reputation, its pitch is convergence: one platform for IGA, PAM, and application access governance, covering human and non-human identities alike. Organizations tired of stitching point tools together find this attractive.

BeyondTrust

BeyondTrust is a privileged access specialist named a Leader in the 2025 Gartner PAM Magic Quadrant, where it was positioned highest of all vendors in Ability to Execute. It is strong in privileged remote access and just-in-time privilege, which matters for organizations securing third-party and vendor access. Like CyberArk, it is a PAM-first platform rather than a full-suite IAM.

JumpCloud

JumpCloud takes a different tack: an open directory platform aimed at small and mid-sized businesses that need to manage identities, devices, and access without a heavyweight enterprise suite. It consolidates directory, SSO, MFA, and device management in one place, which suits lean IT teams. Very large enterprises usually outgrow its governance depth.

Google Cloud IAM

Google Cloud IAM governs access to Google Cloud resources rather than acting as a general workforce IAM. It is essential if your infrastructure runs on GCP, where it controls which users and services can act on which resources at a fine grain. It is not a substitute for a workforce access or governance platform; it solves the cloud-resource layer specifically.

Reach SOC 2 Compliance in 6 Weeks or Less

Schedule Your Free SOC 2 Assessment Today

IAM Solutions Comparison: Providers at a Glance

The table below summarizes where each provider is strongest and the kind of organization it fits. Analyst positions reflect the 2025 Gartner Magic Quadrants for Access Management and Privileged Access Management.

VendorPrimary StrengthBest Fit

2025 Gartner Position

OktaWorkforce access, SSO, broad integrationsMid-market to enterprise, multi-cloud SaaSLeader, Access Management
Microsoft Entra IDMicrosoft ecosystem integration, bundled valueMicrosoft-centric organizations of any sizeLeader, Access Management
SailPointIdentity governance, access certification, complianceLarge enterprises with complex governance needsLeader, IGA
CyberArkPrivileged access, machine identity, secrets managementEnterprises with high privilege risk or compliance pressureLeader, PAM
Ping IdentityCIAM, federation, fine-grained access controlLarge enterprises with complex customer or partner identityLeader, Access Management
IBM Security VerifyBroad suite, hybrid enterprise fitLarge IBM-invested enterprisesChallenger, Access Management
SaviyntConverged IGA + PAM, cloud-nativeCloud-first enterprises seeking platform consolidationChallenger, PAM
BeyondTrustPrivileged remote access, just-in-time privilegeEnterprises with third-party and vendor access riskLeader, PAM (highest Ability to Execute)
JumpCloudDirectory, SSO, MFA, device management unifiedSMBs with lean IT teamsNiche Player
Google Cloud IAMFine-grained GCP resource access controlGCP-native infrastructure teamsN/A (cloud platform IAM)

Insider Note: A Leader badge in one Magic Quadrant says nothing about the others. Gartner publishes separate quadrants for Access Management, PAM, and IGA, and the leaders rarely overlap cleanly. A vendor topping the access quadrant may be a niche player in governance. Always check the quadrant that matches the problem you are actually solving.

IAM Solutions Compared by Category

Best for Privileged Access Management (PAM)

CyberArk and BeyondTrust are the two specialists, with BeyondTrust positioned highest in Ability to Execute in the 2025 PAM Magic Quadrant and CyberArk a long-standing Leader. Saviynt is the convergence option for teams that want PAM inside a broader governance platform. If privilege is your primary risk driver, these three define the shortlist — and the choice between them comes down to whether you want a dedicated specialist or a unified platform.

Best for Identity Governance and Administration (IGA)

SailPoint and Saviynt anchor this category. SailPoint suits the most complex governance programs, particularly where unstructured data and legacy systems are in scope. Saviynt appeals to cloud-first organizations that want governance and PAM unified. Both expect a mature internal program to drive value; neither is a set-and-forget deployment.

Best for Workforce Access

Okta and Microsoft Entra ID dominate workforce single sign-on and access, with Ping Identity strong where federation and customer identity requirements are demanding. The choice often comes down to how committed you are to the Microsoft stack. Organizations with a genuinely mixed environment tend to land on Okta or Ping; Microsoft shops rarely need to look further than Entra.

Best for Machine and Non-Human Identity (NHI)

This is the fastest-moving category in the market. CyberArk and Saviynt have invested heavily in securing machine identities and AI-agent secrets, and the broader market is racing to catch up as non-human identities become the dominant identity type in most environments. Any vendor you shortlist should have a specific, credible answer for how it governs service accounts, API tokens, and AI agents — not just a roadmap slide.

Best for Cloud-Native Environments

Google Cloud IAM, Entra ID, and Okta fit cloud-first estates naturally, while Saviynt and JumpCloud offer cloud-native delivery without on-prem baggage. The right answer here depends almost entirely on where your workloads actually run, not where you plan to be in three years.

IAM Solutions Compared by Organization Size

Best for Small and Mid-Sized Businesses

SMBs need fast deployment, predictable pricing, and minimal administration overhead. JumpCloud’s consolidated directory-plus-device approach fits lean IT teams, and Entra ID is the natural choice for businesses already on Microsoft 365. Enterprise governance suites like SailPoint are usually overkill at this size — both in complexity and cost — and they assume a level of internal governance maturity that most SMBs have not yet built.

Best for Large Enterprises

Large enterprises need depth: complex governance, fine-grained access, strong PAM, and the ability to span many directories, clouds, and application types. SailPoint, CyberArk, Ping, IBM, and the enterprise tiers of Okta and Saviynt populate these shortlists. The realistic outcome is often a small portfolio of best-of-breed tools rather than a single platform, though convergence offerings from vendors like Saviynt are narrowing that gap for organizations willing to place a bigger bet on one provider.

Reach SOC 2 Compliance in 6 Weeks or Less

Schedule Your Free SOC 2 Assessment Today

Cost Comparison of Leading IAM Solutions

Key Pricing Factors to Evaluate

Most enterprise IAM vendors price per identity per month, often in tiers, and reserve advanced governance, PAM, and AI features for higher bands. The line items that catch buyers off guard are connector and integration licensing, professional-services fees for implementation, premium support tiers, and the internal headcount needed to operate the platform day-to-day. Non-human identities increasingly count toward licensing too, which can dramatically change the math given how fast they multiply in cloud-native environments.

Short-Term vs. Long-Term Cost Considerations

A cheaper platform that needs heavy customization can cost more over three years than a pricier turnkey option. Conversely, an over-featured enterprise suite drains budget on capabilities a smaller team will never use. The honest comparison is total cost of ownership across the full contract, including the migration cost you will eventually face if you choose poorly. That last item is easy to ignore in a procurement process and expensive to ignore in practice.

Steps to Choose IAM Solution

How to Choose the Right IAM Solution for Your Organization

Step 1: Assess Your Size and User Base

Count not just employees but contractors, partners, customers where relevant, and the machine identities already in your environment. The ratio of non-human to human identities alone can rule some platforms in or out of contention before you reach a demo.

Step 2: Define Your Security Objectives and Compliance Requirements

Write down the specific outcomes you need: phishing-resistant access, automated certifications for an upcoming audit, privileged-account control, or all of these. Map them to the frameworks you must satisfy — ISO 27001, HIPAA, PCI DSS, SOX, or others. This document becomes your scorecard and prevents requirements from shifting mid-evaluation to favor a vendor that ran a good demo.

Step 3: Evaluate Integration and Deployment Needs

Inventory your core systems and confirm prebuilt connectors exist for each. Decide where you sit on the cloud-to-on-prem spectrum, then test in a proof of concept how the platform handles your messiest integration, not its cleanest demo scenario. The difficult edge cases are where real-world value separates from slide-deck value.

Step 4: Compare Vendor Strengths Against Your Use Cases

Match the problem you are solving to the vendor built for it. An access problem points to Okta, Entra, or Ping. A governance problem points to SailPoint or Saviynt. A privilege problem points to CyberArk or BeyondTrust. Resist buying a specialist’s adjacent module just because it sits on the same invoice.

Important: The most common comparison mistake is letting an incumbent relationship decide the outcome before requirements are written. Buying governance from your access vendor, or privilege from your directory vendor, because it is convenient often means accepting a weaker tool for the job that matters most. Convenience is a legitimate factor, but it should be weighed deliberately — not assumed.

Step 5: Account for Implementation Risk and Change Management

IAM projects fail more often on rollout than on technology. Provisioning rules touch every employee, and a botched deployment either locks people out or grants too much. Budget for a phased rollout, internal expertise or a capable implementation partner, and the cultural change that stricter access controls bring. Enterprise-scope implementations commonly run several months to a year, and that timeline is driven by integration complexity and process change far more than by the software itself.

Reach SOC 2 Compliance in 6 Weeks or Less

Schedule Your Free SOC 2 Assessment Today

Emerging Trends Shaping IAM Solution Comparisons in 2026

AI-Driven Identity Threat Detection

IAM platforms increasingly use machine learning to spot anomalous access in real time and respond before damage spreads. Gartner research has suggested that organizations applying AI to identity can cut identity-related breaches significantly. The capability is real and worth weighting as a comparison criterion, but probe whether it is a working capability or a roadmap slide — the difference is usually visible in a proof of concept.

Converging IAM Domains Into Unified Platforms

The long-standing split between access, governance, and privilege is blurring. Gartner has predicted that a large majority of organizations will prefer converged platforms over point solutions, and vendors like Saviynt have built their entire pitch around that shift. Convergence promises fewer silos and simpler audits, at the cost of betting more of your identity stack on a single provider. That is a reasonable trade for some organizations and a concentration risk for others — know which camp you are in before the sales cycle begins.

Growth of Machine and Non-Human Identity Management

Machine identities now vastly outnumber human ones. CyberArk’s research puts the ratio above 80 to 1 in many organizations, with nearly half of those identities holding sensitive or privileged access. Other studies cite ratios from 45 to 1 up to 144 to 1 in cloud-native environments. The dedicated NHI management market was valued near $3.6 billion in 2025 and is projected to grow past $22 billion by 2034. Any platform you compare in 2026 should have a credible, specific answer for governing service accounts, tokens, and AI agents.

Worth Knowing: Two in Three Enterprises Report Breaches

Industry research has found that two-thirds of enterprises have suffered a breach involving a compromised non-human identity, and a large share of machine credentials are over-privileged or never rotated. If a vendor's NHI story is vague, that gap is where your next incident is most likely to start.

Shift Toward Passwordless and Decentralized Identity

Passwordless access is becoming the workforce default. Gartner expects passwordless to be the standard for workforce authentication across many enterprises by the end of 2026, and the FIDO Alliance reports that more than 15 billion online accounts now support passkeys. Decentralized identity and verifiable credentials are earlier in maturity but worth tracking as a longer-term shift in who controls identity data — particularly for organizations managing large partner or customer identity ecosystems.

 

Conclusion: Choosing the Right IAM Solution

There is no single best IAM solution, only the best fit for the problem you are solving and the environment you run. The leaders are genuinely strong, but they lead in different races: Okta and Entra in access, SailPoint and Saviynt in governance, CyberArk and BeyondTrust in privilege. Anchor the comparison to written requirements, normalize cost to a multi-year total, and weight the criteria that still matter after the demo ends: integration depth, governance for both human and machine identities, compliance readiness, and a roadmap you can trust. Get those right, and the shortlist tends to choose itself.

Frequently Asked Questions About IAM Solutions

What is the difference between IAM, IGA, and PAM?

IAM is the umbrella discipline for managing identities and access. IGA — identity governance and administration — is the subset focused on who should have access, running access certifications, and demonstrating compliance to auditors. PAM — privileged access management — is the subset that protects high-risk accounts with elevated permissions, including admin credentials, service accounts, and machine identities. Most enterprises use all three, sometimes from different vendors, and the boundaries between them are blurring as the market converges.

IAM is commonly described through four functions: authentication (verifying identity), authorization (granting appropriate access), administration (managing the identity lifecycle from onboarding through deprovisioning), and auditing and governance (monitoring and proving that access is correct and compliant). Together, they cover the full life of an identity from creation to removal.

It depends on scope. A focused SMB deployment can go live in weeks, while a full enterprise governance or PAM program commonly takes several months to a year. The timeline is driven by integration complexity and process change far more than by the software itself — a fact that surprises many buyers who treat implementation as an afterthought during procurement.

Platforms with strong hybrid bridging suit mixed estates. Microsoft Entra ID fits Microsoft-heavy hybrids naturally, Okta and Ping handle vendor-neutral mixes well, and IBM and SailPoint serve complex on-prem-plus-cloud enterprises with deep governance needs. The best choice depends on which systems dominate your environment today, not only where you plan to be.

The usual traps are comparing feature lists instead of fit-to-use-case, underestimating total cost of ownership, letting an incumbent relationship preempt requirements, and overlooking machine-identity governance until it becomes a breach. A written scorecard built before vendor contact and a realistic proof of concept focused on your hardest integrations address most of them.

They automate access certifications, enforce segregation of duties, log access events, and generate audit-ready reports mapped to frameworks such as SOX, HIPAA, ISO 27001, and PCI DSS. Strong governance tooling turns audit preparation from a manual scramble into a continuous, documented process — which is a meaningful operational advantage for teams facing regular external audits.

To ensure the right identities have the right access to the right resources at the right time — and no more. Everything else, from single sign-on to adaptive authentication to just-in-time privilege, serves that foundational principle of least privilege.

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.