/

  / CMMC Readiness Assessment: Find Gaps Before Your C3PAO

CMMC Readiness Assessment: Find Gaps Before Your C3PAO

CMMC requirements started appearing in Department of Defense contracts on November 10, 2025, when the final DFARS rule took effect. By November 10, 2028, the clause at DFARS 252.204-7021 must appear in every solicitation and contract where contractor systems process, store, or transmit Controlled Unclassified Information (CUI). For most of the Defense Industrial Base (DIB), the math is blunt: pass a CMMC assessment or lose eligibility for DoD work.

A CMMC readiness assessment is how you find out whether you’d pass before the stakes are real. It’s a structured review of your environment, documentation, and evidence against the requirements of the Cybersecurity Maturity Model Certification, done before you sit for a self-assessment or a Certified Third-Party Assessment Organization (C3PAO) audit. A good one tells you exactly where you stand and what to fix first.

This guide covers what a readiness assessment includes, how the process works at each CMMC level, what it costs, how long it takes, and how to pick someone to run one.

What Is a CMMC Readiness Assessment?

A CMMC readiness assessment is a pre-certification evaluation that measures your organization against the specific requirements of your target CMMC level. It examines your scope, implemented controls, System Security Plan (SSP), Plan of Action and Milestones (POA&M), and the evidence supporting them, then produces a gap analysis and a remediation roadmap.

The purpose is simple: surface every deficiency while it’s still cheap to fix. An assessor who finds a scoping error during a readiness review costs you a few weeks of rework. A C3PAO who finds the same error during a certification assessment can cost you the assessment fee, months of delay, and in some cases contract eligibility.

How It Differs From an Official C3PAO Audit

An official CMMC Level 2 certification assessment is conducted by a C3PAO accredited by the Cyber AB, the official accreditation body for the CMMC ecosystem. The C3PAO’s findings are binding. Results go into the DoD’s assessment systems, and a passing result produces a CMMC status that contracting officers verify before award. A readiness assessment carries no official weight. Nothing gets filed or certified, and a poor result costs you nothing beyond the work needed to fix it. That’s the whole point. It’s the only stage in the entire process where failure is free.

There’s also a conflict-of-interest rule worth knowing. A C3PAO cannot provide consulting and remediation services to an organization and then certify that same organization. If a C3PAO helps you prepare, a different C3PAO has to assess you.

How It Differs From a Mock Assessment

A mock assessment is a dress rehearsal. It simulates the certification assessment itself: assessors interview control owners, request evidence on the spot, and score findings the way a C3PAO would. A readiness assessment is broader and comes earlier, and its job is discovering and closing gaps rather than rehearsing the exam. Most organizations run a readiness assessment first, remediate, then run a mock assessment a few weeks before the real one to see whether staff and evidence hold up under live questioning.

How It Differs From a Self-Assessment

A self-assessment is a formal CMMC mechanism rather than a preparation exercise. CMMC Level 1 and a subset of Level 2 contracts let organizations self-assess, post the results to the Supplier Performance Risk System (SPRS), and have a senior official affirm compliance annually. That affirmation is a representation to the government, and false or careless affirmations carry False Claims Act exposure. A readiness assessment is the check you run before making that representation, so the number you affirm reflects reality.

Why a CMMC Readiness Assessment Matters

Why a CMMC Readiness Assessment Matters

Avoiding Failed Certification Attempts

CMMC Level 2 covers all 110 security controls of NIST SP 800-171, evaluated against 320 assessment objectives. Every objective has to be met for a control to score, and there’s no partial credit. Organizations that skip readiness work routinely walk into certification believing they’re compliant because controls are “mostly” implemented. Mostly implemented scores the same as not implemented.

Protecting DoD Contract Eligibility

Under the phased rollout that began in November 2025, CMMC status is a condition of award. Prime contractors also have to flow the requirement down to subcontractors that handle Federal Contract Information (FCI) or CUI, and they’ve been pushing their supply chains hard. So a missed certification hurts twice: you lose the immediate contract, and you risk dropping out of a prime’s approved supplier pool during the exact window when those pools are being rebuilt around CMMC status.

Reducing Remediation Costs and Delays

Gaps found early get fixed on your schedule with your choice of solution. Gaps found during certification get fixed under deadline pressure, often with whatever expensive tooling can be deployed fastest. There’s a conditional CMMC status for organizations that pass with a limited POA&M, but closeout has to happen within 180 days, and only certain lower-weighted controls are POA&M-eligible in the first place. Readiness work keeps you out of that corner.

Worth Knowing: The DoD Assessment Methodology

The DoD Assessment Methodology weights each NIST SP 800-171 control at 1, 3, or 5 points, deducted from a starting score of 110. The floor is -203. To achieve even a conditional Level 2 status, you need a minimum score of 88. A handful of unmet 5-point controls, such as FIPS-validated encryption or multifactor authentication, can put certification out of reach on their own, so a readiness assessment should always show the point weight attached to every gap.

Let Axipro help you build a business continuity plan that's practical, compliant, and audit-ready.

Schedule Your Free Assessment Today

When to Conduct a CMMC Readiness Assessment

  • Before your first self-assessment. If a contract requires a Level 1 or Level 2 self-assessment, run readiness work before you post a score to SPRS. The score you affirm is a legal representation, and it’s far easier to fix the environment than to explain a misstated score later.
  • When contract requirements are approaching. If CMMC language has shown up in a solicitation you plan to bid, or your prime has set a certification deadline, count backward. Remediation after a readiness assessment typically takes six to twelve months for organizations starting from a moderate posture, and C3PAO scheduling adds lead time on top.
  • After a significant environment or system change. A migration to a new cloud tenant, an acquisition, a new facility, or a redesigned CUI enclave can invalidate assumptions your entire compliance program rests on. Reassess whenever the boundary moves.
  • On a recurring basis. CMMC requires an annual affirmation of continued compliance by an affirming official. An annual internal readiness cycle gives that affirmation a factual basis and catches drift before it compounds.

What a CMMC Readiness Assessment Includes

A thorough readiness assessment covers nine areas, and the order matters because each builds on the last.

  1. Scope definition and CUI boundary mapping.
    Everything starts with scope. The assessment identifies where FCI and CUI live, which systems process, store, or transmit them, and whether the boundary is defensible. Plenty of organizations discover their assumed CUI enclave leaks: a backup job copies CUI to an out-of-scope server, or a shared mailbox pulls it into the corporate tenant.

  2. Information flow and asset inventory review.
    Assets get categorized the way CMMC scoping guidance requires, including CUI assets, security protection assets, contractor risk managed assets, and specialized assets. Data flow diagrams get tested against reality rather than against what the network diagram from 2022 says.

  3. Control evaluation against CMMC requirements.
    Each in-scope control gets evaluated at the assessment objective level. For Level 2, that means all 320 objectives across the 110 controls of NIST SP 800-171, judged as met, not met, or not applicable.

  4. SSP review. The System Security Plan is the anchor document of any CMMC assessment. Assessors check whether it describes the environment as it actually exists, addresses every control, and matches the scoping documentation. An SSP that contradicts the evidence is one of the fastest ways to lose an assessor’s confidence.

  5. POA&M validation. Open items get reviewed for POA&M eligibility, realistic milestones, and assigned owners. Items that should’ve been closed years ago get flagged, because a stale POA&M signals a compliance program that isn’t actually running.

  6. SPRS score calculation and review. The assessment recalculates your score under the DoD Assessment Methodology and compares it with what’s currently posted in SPRS. Discrepancies get corrected before they become a problem in an official review.

  7. Evidence and documentation compilation. For every objective, the assessment confirms that evidence exists, is current, and can be produced quickly. Policies, screenshots, configuration exports, training records, and log samples get organized into an evidence library mapped to objectives.

  8. Gap analysis and risk assessment. Every deficiency gets documented with its affected control, point weight, risk severity, and remediation difficulty.

  9. Remediation roadmap development. Findings become a sequenced plan: quick wins first, high-point-value controls next, long-lead items such as FIPS-validated cryptography or physical security changes scheduled with realistic dates and owners.

Insider Note: Scoping errors sink more certification attempts than technical control failures do. Assessors can only assess the boundary you present, and if CUI turns out to flow outside it, the assessment stops being a test of your controls and becomes a test of your credibility. Spend a disproportionate share of readiness time proving the boundary, especially anywhere email, file sharing, or managed service provider access touches CUI. Your MSP or MSSP belongs in a shared responsibility matrix that states, control by control, who does what. And if a cloud provider stores or processes CUI on your behalf, it needs to meet FedRAMP Moderate or equivalent.

CMMC Readiness Assessment Process: Step-by-Step

Step 1: Initial scoping and kickoff.
Define the target CMMC level, identify the contracts driving the requirement, map where CUI and FCI live, and agree on the assessment boundary. This step also sets logistics: who gets interviewed, what documentation exists, and what access the assessors need.

Step 2: Documentation and control review.
Assessors review the SSP, policies, procedures, network diagrams, asset inventories, and the existing POA&M. Documentation gaps surface here, and they’re usually extensive. Most organizations have implemented more than they’ve documented, which matters because an undocumented control often can’t be verified.

Step 3: Technical testing and interviews.
Assessors validate that controls operate as described. That means reviewing configurations, sampling logs, checking MFA enforcement, inspecting encryption settings, and interviewing the people who own each control. Interviews expose the difference between a policy that exists and a practice that happens.

Step 4: Gap analysis and reporting.
Findings get consolidated into a gap report scored against the assessment objectives, with an updated SPRS calculation and a severity ranking for each deficiency.

Step 5: Remediation planning.
The final step converts findings into a plan with owners, dates, dependencies, and budget implications, ordered so the highest-weight and longest-lead items start first.

Readiness Assessment by CMMC Level

CMMC 2.0 has three levels, and readiness work scales sharply between them.

  • Level 1 readiness verifies the 15 basic safeguarding requirements for FCI. The work is light, but the annual self-assessment and affirmation still carry legal weight, so evidence should exist for every requirement.
  • Level 2 readiness is where most of the DIB lives. It covers the full NIST SP 800-171 control set at the objective level, and it’s the level this article’s process describes. Contracts specify whether Level 2 requires a C3PAO certification or a self-assessment. The security bar is identical either way.
  • Level 3 readiness applies to a small slice of contractors supporting the most sensitive programs. It requires a final Level 2 certification first, then implementation of 24 enhanced requirements from NIST SP 800-172 built to resist advanced persistent threats. The assessment is performed by the government’s Defense Industrial Base Cybersecurity Assessment Center (DIBCAC) rather than a C3PAO, and readiness work has to address the stricter Level 3 scoping model as well as the enhanced controls.

Let Axipro help you build a business continuity plan that's practical, compliant, and audit-ready.

Schedule Your Free Assessment Today

CMMC Readiness Assessment Deliverables

A credible readiness engagement ends with five artifacts.

  • The gap analysis report documents every deficiency at the objective level with severity and point impact.
  • The updated SSP and POA&M reflect the environment as found, with POA&M entries limited to genuinely eligible items.
  • The SPRS score summary shows your recalculated score, the delta from what’s posted, and where the score lands as remediation progresses. The prioritized remediation roadmap sequences the work with owners, dates, and cost estimates.
  • Finally, the executive summary gives leadership what they actually need: certification probability today, the investment required, the timeline, and the contract revenue at risk if the timeline slips.

CMMC Readiness Assessment Checklist

Use this as the closing pass before you schedule anything official.

  • Confirm every control is implemented and verifiable. Implemented means all assessment objectives are met, and evidence proves it. If you can’t produce the evidence within a day, treat the control as unverified.

  • Validate the SSP and POA&M are current. Both documents should describe today’s environment, reference today’s system names, and carry no entries that contradict each other or the network reality.

  • Recalculate and review your SPRS score. Run the DoD Assessment Methodology from scratch rather than editing last year’s spreadsheet, and reconcile the result with what SPRS currently shows.

  • Check consistency across systems and documents. Assessors cross-reference constantly. The asset inventory, the SSP, the data flow diagrams, and the actual configurations have to tell one story.

  • Validate control ownership. Every control needs a named owner who can speak to how it works. “The IT team handles that” is an interview answer that fails.

  • Conduct a mock assessment. Once gaps are closed, rehearse under live conditions with someone playing an unfriendly assessor.

  • Maintain continuous monitoring. Readiness decays. Patch cadence, log review, access recertification, and training records need to keep running between assessments, because the annual affirmation asserts that they did.

Pro Tip: Run Evidence Drills before any Assessment

Run evidence drills before any assessment, readiness or official. Pick ten random assessment objectives and give the control owner 30 minutes to produce current proof for each. Organizations that pass certification smoothly are rarely the ones with the best security tooling. They're the ones that can retrieve any artifact in minutes, because slow evidence retrieval reads as weak control operation even when the control itself is fine.

How Long Does a CMMC Readiness Assessment Take?

The assessment itself typically runs two to six weeks. Small organizations with a contained CUI enclave sit at the short end. Mid-sized contractors with a few hundred employees and multiple systems usually need four to six weeks, and large or multi-site environments can take two to three months before the report is final.

The larger number is what follows. Remediation commonly takes six to twelve months depending on where you start, and the biggest schedule drivers are consistent: unclear CUI boundaries that force re-scoping, long-lead technical items such as FIPS-validated cryptography, dependency on MSPs whose own posture has to be verified, and documentation debt that takes longer to clear than anyone budgets. Environment complexity, staff availability for interviews, and how much evidence already exists in retrievable form all move the timeline more than headcount does.

Common Challenges During a CMMC Readiness Assessment

Underestimating time and resources. Readiness work competes with day jobs. The interview schedule alone can eat dozens of staff hours, and remediation always uncovers second-order work.

Scoping and CUI boundary uncertainty. Many contractors can’t say with confidence where all their CUI is. Legacy file shares, email threads, and subcontractor exchanges scatter it, and every newly discovered location expands scope.

Manual documentation management. Spreadsheets tracking 320 objectives across policies, evidence files, and owners break down fast. Version confusion between the SSP, the POA&M, and reality is one of the most common findings in readiness work.

Linking controls, risks, and evidence. Assessors think in terms of objective, implementation, and proof. Organizations that store evidence by department or by tool rather than by control spend the assessment scrambling to translate.

Choosing a CMMC Readiness Assessment Partner

Look for credentials issued within the CMMC ecosystem. A Registered Provider Organization (RPO) is authorized by the Cyber AB to provide consulting and preparation services. Individual practitioners should hold the Certified CMMC Professional (CCP) or Certified CMMC Assessor (CCA) credential, with CCAs bringing direct experience of how official assessments actually get scored.

Before hiring, ask a few pointed questions. How many Level 2 environments has the team taken through readiness, and how many of those went on to pass certification? Will the assessment evaluate at the assessment objective level or only at the control level? Does the deliverable include an updated SSP and a costed roadmap, or just a findings list? How do they handle MSP and cloud provider responsibilities? Vague answers to any of these predict a shallow engagement.

On independence: an in-house readiness review beats none, and it builds internal capability. But independent assessors catch what familiarity hides, and their findings carry more weight with leadership when remediation needs budget. If your certification path runs through a C3PAO, remember that the assessing C3PAO can’t also be your preparation consultant, so plan for separate parties from the start.

A CMMC readiness assessment is the cheapest point in the entire certification journey to discover bad news. It defines your true scope, scores your real posture against every applicable assessment objective, aligns your SSP, POA&M, and SPRS score with reality, and converts everything it finds into a sequenced plan. With CMMC clauses now flowing into DoD contracts and full inclusion required by late 2028, the contractors who treat readiness as a project this year will be the ones still bidding in three.

Frequently Asked Questions

Is a CMMC Readiness Assessment Required?

No. Neither 32 CFR Part 170 nor the DFARS clauses require one. What the rules require is the outcome a readiness assessment protects: a truthful SPRS score, a passing assessment at the required level, and an annual affirmation you can stand behind.

Yes, and for Level 1 it’s often enough. For Level 2, internal reviews work best as a recurring discipline, supplemented by an external assessment before certification. Internal teams tend to assess intent while external assessors assess evidence, and certification is scored on evidence.

A gap analysis is one component: the comparison of your current state against the requirements. A readiness assessment wraps that comparison in scoping validation, SSP and POA&M review, SPRS recalculation, evidence compilation, and a remediation roadmap.

At minimum, annually, aligned with the affirmation cycle, plus after any major environmental change and before any official assessment. Continuous monitoring between cycles keeps the annual pass small.

No. It cuts the risk of surprise to near zero if you remediate what it finds, but the certification result depends on the official assessment of your environment on the day. Any provider guaranteeing certification is telling you something about their integrity rather than your posture.

A C3PAO can perform readiness and consulting work, but it can’t then conduct your official certification assessment. If you want a C3PAO’s perspective during preparation, engage one C3PAO for readiness and a different one for certification, and confirm the separation in writing.

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.