/

  / CMMC Certification Cost: Complete Pricing Breakdown 2026

CMMC Certification Cost: Complete Pricing Breakdown 2026

CMMC certification costs between $4,000 and $30,000 at Level 1, $30,000 to $300,000 or more at Level 2, and $100,000 to well over $1 million at Level 3. Most contractors expect the audit fee to be the big number. It isn’t. The formal assessment typically accounts for only 25% to 40% of total spend, with preparation, remediation, and technology upgrades consuming the rest.

The stakes changed in late 2025. The final 48 CFR acquisition rule took effect on November 10, 2025, which means CMMC requirements now appear directly in Department of Defense (DoD) solicitations and contracts. Starting in November 2026, Phase 2 of the rollout gives contracting officers the authority to require third-party certification for Level 2 work. If you handle Controlled Unclassified Information (CUI), certification is no longer optional, and the cost question becomes a budgeting exercise rather than a hypothetical.

This guide breaks down every major cost category, what moves your number up or down, and how to keep the total under control.

What Is CMMC Certification and Why Does Cost Vary?

The Cybersecurity Maturity Model Certification (CMMC) is the DoD’s framework for verifying that companies in the Defense Industrial Base (DIB) actually protect the sensitive information they handle. The program, codified in 32 CFR Part 170, builds on the security requirements of NIST SP 800-171 and, at the top tier, selected controls from NIST SP 800-172.

Costs vary so widely because you can’t buy CMMC off a shelf. Your environment has to reach a certain state and then stay there. A 15-person machine shop with one well-scoped CUI enclave faces a fundamentally different project than a 500-person prime contractor with CUI flowing through a dozen systems. Your starting security posture, the scope of your assessment boundary, and whether you build internally or hire help all move the total by six figures in either direction.

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

Schedule Your Free Assessment Today

Average CMMC Certification Cost at a Glance

The DoD’s own published estimates are instructive. A triennial Level 2 certification assessment, including affirmations, is projected at roughly $105,000 for small entities and $118,000 for larger ones. Those figures cover only assessment and affirmation activities, though. The DoD excludes implementation costs from its estimates on the grounds that NIST SP 800-171 compliance has been contractually required under DFARS 252.204-7012 since 2017. Your real budget has to cover both.

CMMC Certification Cost

CMMC Certification Cost by Level

CMMC Level 1 (Foundational) Cost: $5,000 – $30,000

Level 1 covers Federal Contract Information (FCI) and requires 15 basic safeguarding practices drawn from FAR 52.204-21. Because Level 1 permits an annual self-assessment with no third-party auditor, the costs are internal labor, basic tooling, and documentation. Small contractors with reasonable IT hygiene often land near the bottom of the range. The DoD estimates annual Level 1 assessment and affirmation activity at around $6,000 for a small entity, with the remainder of the range driven by any remediation needed to attest honestly.

CMMC Level 2 (Advanced) Cost: $50,000 – $300,000+

Level 2 is where most of the DIB lands and where budgets get serious. It requires full implementation of all 110 security requirements in NIST SP 800-171, assessed across 320 individual objectives. For most contracts, a C3PAO (Certified Third-Party Assessor Organization) accredited by the Cyber AB has to conduct the assessment every three years.

Market data puts C3PAO assessment fees at $30,000 to $100,000 depending on scope, site count, and complexity. Preparation dwarfs that figure for most organizations. Companies starting from a low maturity baseline routinely spend three to four times the assessment fee on readiness work before an auditor ever shows up.

CMMC Level 3 (Expert) Cost: $300,000 – $1,000,000+

Level 3 adds 24 enhanced requirements from NIST SP 800-172 on top of a completed Level 2 certification, and the assessment is conducted by the government’s DIBCAC rather than a commercial C3PAO. DIBCAC charges no assessment fee, but don’t mistake free for cheap. The DoD estimated roughly $41,000 in additional implementation cost for the 800-172 controls alone, and total triennial assessment-related costs in the $146,000 to $159,000 range. Real-world totals run far higher once you account for the advanced tooling, threat hunting capability, and organizational changes Level 3 demands. Only contractors supporting the most sensitive programs need this tier.

Worth Knowing: You can't skip to Level 3.

You can't skip to Level 3. A final Level 2 certification with all POA&M items closed is a prerequisite for the same assessment scope, so Level 3 budgets always include a full Level 2 project first.

CMMC Certification Cost Breakdown by Expense Category

Gap Assessment and Readiness Planning Costs

A gap assessment maps your current environment against NIST SP 800-171 and typically costs $1,500 to $20,000 depending on depth and scope. This is the most valuable dollar you’ll spend in the entire project, because everything downstream is priced off what it finds.

Documentation and System Security Plan (SSP) Costs

The System Security Plan (SSP) is the cornerstone document of any assessment, mapping every control to your specific implementation. Professionally developed SSPs and supporting policies run $12,000 to $60,000. A weak SSP is one of the most common reasons assessments stall or fail, so this is a poor place to economize.

Remediation and Security Control Implementation Costs

Closing the gaps is usually the largest line item: $20,000 to $150,000 or more. Multi-factor authentication, logging and SIEM deployment, encryption, access control restructuring, and incident response capability all live here. Organizations with mature security postures spend far less than those starting from scratch.

Technology and Infrastructure Upgrade Costs

Many contractors move CUI into a dedicated enclave rather than securing their entire network. Enclave platforms typically cost $300 to $400 per user per month. Others upgrade endpoint protection, replace unsupported systems, or migrate to government-grade cloud environments, each with its own licensing and migration costs.

C3PAO Assessment and Audit Fees

The formal Level 2 assessment runs $30,000 to $100,000, driven by assessor-days, number of sites, and evidence quality. Well-organized evidence directly reduces assessor time and therefore your invoice.

Consulting and Advisory Fees

Specialist consultants, including Registered Practitioners (RPs) and Certified CMMC Professionals (CCPs), bill roughly $250 to $400 per hour. Engagements range from targeted advisory work to full program management. Many contractors instead retain a Managed Security Service Provider (MSSP), typically starting at $2,000 to $3,500 per month.

Staff Training and Awareness Program Costs

Security awareness training, role-based training for IT staff, and CUI handling training generally cost $2,000 to $10,000 per year. Assessors check for evidence of training, not just a policy saying it happens.

Internal Personnel and Labor Costs

The least visible cost is your own people’s time: evidence collection, interviews, remediation project management, and documentation review pull hours from billable work. Small contractors feel this hardest, with per-employee compliance costs of roughly $2,500 to $4,600 compared with $600 to $1,000 at enterprise scale.

Ongoing CMMC Costs After Certification

Annual Maintenance and Monitoring Costs

Budget $10,000 to $50,000 per year for continuous monitoring tools, vulnerability scanning, log retention, policy updates, and license renewals. Certification reflects a point in time. Your contractual obligation to stay compliant doesn’t expire between assessments.

Recertification Costs (Every 3 Years)

Level 2 certification lasts three years, after which the full C3PAO assessment repeats. Recertification is usually cheaper than the first cycle because the environment and evidence already exist, but plan for the assessment fee plus refreshed documentation and a pre-assessment review.

Continuous Compliance and Reporting Costs

Annual affirmations by a senior official must be filed in the Supplier Performance Risk System (SPRS), and your score has to stay current. False or careless affirmations carry real legal exposure under the False Claims Act, which is why many companies fund an annual internal review before signing.

Important: The affirmation requirement changes the risk calculus entirely. An executive personally attests to compliance every year, and the Department of Justice has actively pursued False Claims Act cases over cybersecurity misrepresentations. Treat annual affirmations as a compliance event with evidence behind them rather than a formality.

Key Factors That Influence Your CMMC Certification Cost

Company Size and Number of Employees

More users mean more endpoints, more accounts, more training seats, and more assessment hours. Costs scale with headcount, though per-employee cost falls as fixed expenses spread across more staff.

Scope of Controlled Unclassified Information (CUI)

Scope is the single biggest cost driver. CUI touching every system means every system is in scope. CUI confined to a tight enclave means the assessment boundary, and the bill, shrinks accordingly.

Existing Cybersecurity Maturity and Posture

A contractor already operating close to NIST SP 800-171, perhaps with SOC 2 or ISO 27001 in place, inherits significant control overlap and spends far less on remediation than one starting cold.

Cloud vs. On-Premise Environment

Cloud environments with strong compliance inheritance, particularly FedRAMP-authorized services, reduce the number of controls you need to build yourself. Legacy on-premise infrastructure often requires expensive upgrades or segmentation.

Internal Resources vs. Outsourced Support

In-house expertise converts consulting fees into salary you already pay. Most small and mid-size contractors blend the two: internal ownership of the program, external specialists for gap assessment, SSP development, and mock audits.

Timeline and Urgency

Compressed timelines cost more. Rushed remediation means premium consulting rates, expedited procurement, and less time to optimize scope. With C3PAO capacity tightening ahead of the November 2026 Phase 2 milestone, late movers will also face scheduling backlogs.

 

Hidden and Often Overlooked CMMC Costs

Several costs rarely appear in initial budgets.

  • Flow-down requirements mean prime contractors increasingly demand proof of compliance from subcontractors before the government does, sometimes on short notice.
  • External Service Providers (ESPs) that touch your CUI can fall within your assessment scope, adding coordination and evidence-gathering work. Productivity dips during remediation, assessment scheduling delays, and re-assessment fees for failed controls all add up.
  • So does the cost of closing POA&M (Plan of Action and Milestones) items within the mandated 180-day window after a conditional certification.

Insider Note: Only 431 organizations held a final Level 2 certification as of October 2025, against roughly 80,000 companies the DoD expects to need one. That mismatch between assessor capacity and demand is a cost factor in itself. Contractors who book C3PAO slots early are already negotiating from a stronger position than those who wait for a contract clause to force the issue.

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

Schedule Your Free Assessment Today

CMMC Cost Estimates for Small vs. Mid-Size vs. Large Contractors

These are first-cycle figures including preparation. Contractors with strong existing postures can land below these ranges. Those discovering years of deferred IT investment can exceed them.

How to Reduce CMMC Certification Costs

Limit and Segment Your Compliance Scope

Isolate CUI into a defined enclave with strict boundaries. Every system you keep out of scope is a system you neither remediate nor pay an assessor to examine. Scoping decisions made before remediation begins are worth more than any discount negotiated afterward.

Use a Government Community Cloud (GCC High) Environment

Microsoft 365 GCC High and comparable government cloud environments are built for CUI and ITAR data, so you inherit controls instead of building them yourself. Licensing costs more than commercial tiers, but the inherited compliance typically outweighs the premium for CUI-heavy organizations.

Use Compliance Automation Tools

Governance platforms that automate evidence collection, control monitoring, and documentation reduce both consultant hours and internal labor, and they make the triennial re-assessment much cheaper by keeping evidence current year-round.

Use Pre-Built Policy Templates and Documentation

Starting policies and the SSP from proven templates instead of a blank page cuts documentation costs substantially. Templates still require tailoring, and assessors can tell when they haven’t been, but the drafting effort drops by half or more.

Choose the Right C3PAO and Consultants

Get quotes from multiple C3PAOs listed on the Cyber AB Marketplace and compare methodology, not just price. A cheap assessor who drags out the engagement or fails controls that a readiness review would have caught costs more in the end. The same logic applies to consultants: defense-sector experience matters more than hourly rate.

Pro Tip: Ask any Prospective C3PAO

Ask any prospective C3PAO for their assessment-day estimate in writing, broken down by control family, before signing. The spread between quotes usually comes from differing scope assumptions rather than differing rates, and surfacing those assumptions early prevents mid-engagement change orders.

How to Budget for CMMC Certification: A Step-by-Step Approach

Start by confirming which level your contracts actually require, then commission a gap assessment to establish your baseline. Price remediation from the gap findings, not from generic benchmarks, and phase the work so quick wins land first. Reserve the C3PAO engagement early, then hold 15% to 20% contingency for the findings every project surfaces. Finally, build the ongoing annual costs into your indirect rate structure so maintenance is funded before it’s needed rather than scrambled for afterward.

CMMC Certification Cost FAQs

How much does a CMMC Level 2 audit cost?

The C3PAO assessment itself typically costs $30,000 to $100,000, depending on scope, sites, and complexity. The DoD’s own estimate for the full triennial assessment and affirmation cycle is roughly $105,000 for small entities. Preparation and remediation sit on top of that figure.

Small businesses pursuing Level 2 typically spend $50,000 to $140,000 for a first certification cycle, including gap assessment, remediation, documentation, and the C3PAO fee. Level 1 self-assessment usually costs $5,000 to $30,000.

There’s no direct reimbursement program, but compliance costs are generally allowable indirect costs and can be built into your rates. Talk to your DCAA-savvy accountant about structuring them properly.

Level 2 and Level 3 certifications last three years, so the assessment cost recurs on a triennial cycle. Annual affirmations in SPRS and ongoing maintenance costs continue every year in between.

Only where your contract allows it. Level 1 always permits self-assessment, and a subset of Level 2 contracts accept a self-assessment filed in SPRS, at a fraction of C3PAO cost. Most Level 2 work involving sensitive CUI requires third-party certification, especially from Phase 2 onward.

Most Level 2 projects take 6 to 18 months from gap assessment to certificate. Longer timelines spread costs and allow cheaper, deliberate remediation. Compressed timelines inflate consulting fees and procurement costs, and assessor scheduling backlogs make last-minute certification increasingly expensive as the November 2026 milestone approaches.

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.