/

  / How to Become a CMMC Registered Practitioner

How to Become a CMMC Registered Practitioner

The CMMC program turned from advisory framework to binding contract requirement on November 10, 2025, when the DoD’s Title 48 acquisition rule took effect. 

That single date changed the market for CMMC advisory services overnight, and the Cyber AB Registered Practitioner credential moved from a useful business card to a genuine signal of competence. 

Over 80,000 companies in the Defense Industrial Base now need help interpreting the rule, and the RP is the formal entry-level role in the ecosystem authorized to provide it.

This guide explains what a CMMC Registered Practitioner is, how the role fits alongside CCPs, CCAs, RPOs, and C3PAOs, what it takes to earn the designation, and how Organizations Seeking Certification (OSCs) should think about engaging one.

CMMC Registered Practitioner

What Is a CMMC Registered Practitioner (RP)?

A CMMC Registered Practitioner is an individual authorized by the Cyber AB, the official accreditation body for the CMMC ecosystem, to provide non-certified advisory and consulting services to Organizations Seeking Certification. 

RPs help defense contractors interpret the CMMC model, scope their environments, build documentation, remediate gaps against NIST SP 800-171, and prepare for the formal assessment they will eventually undergo.

The credential exists because the CMMC framework is genuinely dense. CMMC Level 2 maps to all 110 controls in NIST SP 800-171, and Level 3 layers on 24 selected requirements from NIST SP 800-172. Most contractors do not have the in-house expertise to implement these controls cleanly, and the Cyber AB needed a way to identify advisors who had at least demonstrated baseline knowledge of the program.

An RP does not perform official assessments. That work is reserved for Certified CMMC Assessors (CCAs) operating under a C3PAO. The RP role is strictly advisory, and the Code of Professional Conduct that every RP must sign makes the boundary explicit.

Reach SOC 2 Compliance in 6 Weeks or Less

Schedule Your Free SOC 2 Assessment Today

How RPs Fit Into the Broader CMMC Ecosystem

The Cyber AB structures the ecosystem into two distinct lanes: consulting and implementation on one side, assessment and certification on the other. RPs sit on the consulting side. CCPs, CCAs, and C3PAOs sit on the assessment side.

The two are kept deliberately separate so that no firm can audit work it helped configure, a separation that preserves the integrity of the certification process.

Registered Practitioners vs. Certified CMMC Professionals (CCPs)

The CCP is a more rigorous credential. CCP candidates must complete formal Cyber AB training delivered by a Licensed Training Provider, pass a commercial background check, and sit a proctored exam administered by CAICO. CCPs can participate in actual assessments as part of a C3PAO assessment team, though they cannot lead them. RPs cannot participate in assessments at all.

In practical terms, the RP credential is the right starting point for consultants, MSPs, and internal compliance staff who want to demonstrate baseline CMMC fluency. The CCP is the right credential for professionals planning a career in CMMC assessment work.

Registered Practitioners vs. C3PAOs

Registered Practitioners vs. C3PAOs

A C3PAO (Certified Third-Party Assessment Organization) is the entity authorized to conduct official Level 2 certification assessments and issue formal CMMC status determinations. Fewer than 100 firms held C3PAO authorization as of early 2026, serving an ecosystem of more than 80,000 contractors. C3PAOs are companies. RPs are individuals. They do completely different jobs: the RP prepares the contractor, the C3PAO certifies them.

Important: A C3PAO that helps a client implement controls is barred from later assessing that same client. This is a hard line in the Code of Professional Conduct. If you engage a firm for both readiness and certification work, you will end up paying two different organizations regardless, so plan accordingly from the start.

Reach SOC 2 Compliance in 6 Weeks or Less

Schedule Your Free SOC 2 Assessment Today

What Does a CMMC Registered Practitioner Do?

The work of an RP is the work of getting an organization to the starting line of a formal assessment without surprises. That includes interpreting which CMMC level applies to a given contract, scoping the CUI and FCI environments, identifying gaps against NIST SP 800-171, drafting the System Security Plan (SSP) and Plan of Action and Milestones (POA&M), advising on technical remediation, and coaching the OSC through mock assessments before the real one.

Who Can a CMMC RP Help?

RPs serve any organization in the Defense Industrial Base that needs to achieve a CMMC status. That includes prime contractors, subcontractors at any tier, MSPs, and MSSPs that handle CUI on behalf of defense clients, manufacturers, research universities, and civilian agency contractors whose departments have adopted CMMC-aligned clauses. The flow-down requirements in 32 CFR §170.23 mean that even small subcontractors who process Federal Contract Information (FCI) must hit Level 1, which keeps RP work relevant well past the first wave of large primes.

What Services Does a CMMC RP Provide?

The core service menu looks consistent across the market: gap assessments against NIST SP 800-171, scope definition, SSP and POA&M drafting, policy and procedure development, technical advisory on encryption, access control and incident response, and pre-assessment readiness reviews. Strong RPs also help clients interpret recent guidance changes, manage their SPRS score, and prepare evidence packages that will survive scrutiny from a C3PAO assessment team.

Pro Tip: Evaluating a Registered Practitioner

When evaluating an RP, ask whether they have walked a client through a full C3PAO assessment cycle, not just a gap assessment. There is a significant difference between consultants who write SSPs and consultants who have watched assessors actually challenge one.

How to Become a CMMC Registered Practitioner

How to Become a CMMC Registered Practitioner

The path is straightforward but not trivial. The Cyber AB controls the registration process end-to-end, and every step must be completed in order.

Step 1: Complete the Required CMMC Registered Practitioner Training

The RP training is delivered online through the Cyber AB’s learning management system. It covers the CMMC model document, the structure of the ecosystem, scoping methodology, FCI and CUI definitions, prime and subcontractor information flow, the assessment process, and the relationship between CMMC and existing DFARS clauses.

The course typically takes around eight hours. Candidates should plan for roughly $500 to $600 in combined training and annual registration costs.

Step 2: Register with the Cyber AB

After training, candidates submit a formal application through the Cyber AB portal. The application captures professional background, contact details, and the candidate’s intended affiliation with an RPO, if applicable.

Step 3: Sign the Code of Professional Conduct (CoPC)

Every RP must sign the Code of Professional Conduct, which governs ethical behaviour, conflict of interest, confidentiality, advertising, and, critically, the boundary between advisory and assessment work.

The CoPC is enforceable, and the Cyber AB can and does revoke credentials for material breaches.

Step 4: Complete Identity and Background Checks

RPs must clear a basic background check focused on felony convictions. The candidate runs the check on themselves through an approved provider and submits the result to the Cyber AB. The cost is modest, in the region of $35.

Step 5: Maintain Active Status

The RP designation is valid for one year. Renewal requires payment of the annual registration fee and continued compliance with the CoPC.

RPs whose status lapses are removed from the Cyber AB Marketplace listing, the public-facing directory OSCs use to find advisors, so staying current is a basic business hygiene issue, not just an administrative one.

 

What Is Covered in the CMMC Registered Practitioner Training?

The training is broader than it is deep. It walks candidates through the structure of 32 CFR Part 170, the roles in the ecosystem, the three CMMC levels, the assessment process, scoping rules, and the appeals path. It introduces the CMMC Assessment Process (CAP), explains how SPRS scoring works, and covers the documentation expectations OSCs must satisfy.

What the training does not do is go deep at the implementation level. It points at the NIST documents and the CMMC model rather than walking through every control in detail. Practitioners who want real depth need to bring prior cybersecurity and compliance experience to the table, or pursue the Registered Practitioner Advanced (RPA) credential.

The course is fully online, self-paced within a window, and delivered through the Cyber AB LMS. Most candidates with an IT or compliance background complete it in six to ten hours.

 

Why Become a CMMC Registered Practitioner?

The market signal is the main value. The Cyber AB Marketplace lists every active RP and RPO, and OSCs increasingly start their consultant search there. Being listed gives consultants credibility that no LinkedIn title can replicate.

For internal employees at defense contractors, the RP credential also signals to leadership that the person responsible for CMMC has at least met the published baseline.

The other value is the path it opens. RPs can pursue the Registered Practitioner Advanced (RPA) designation, which requires demonstrated experience implementing CMMC Level 2 controls and a more rigorous exam. From there, the path continues to CCP and CCA for those who want to move into formal assessment work.

Worth Knowing: RP Credential Not Required for CMMC Consulting

The RP credential is not legally required to provide CMMC consulting services. An OSC can hire any qualified cybersecurity consultant, employee, or MSP without the credential. The RP designation is a market signal, not a regulatory gate, and that distinction matters when comparing it to the CCA, which is required to participate in assessments.

What Is a Registered Practitioner Organization (RPO)?

An RPO is the company-level equivalent of the RP credential. A Registered Practitioner Organization is a firm authorized by the Cyber AB to deliver CMMC consulting services, listed in the Cyber AB Marketplace, and permitted to market using official RPO branding.

Becoming an RPO requires employing or contracting at least one active Registered Practitioner, signing the RPO agreement and the Code of Professional Conduct, passing an organizational background check, and paying the annual registration fee.

Public sources put the RPO registration fee at around $6,000, though this should be verified directly with the Cyber AB before budgeting.

The distinction between RP and RPO matters when an OSC is choosing who to contract with. An individual RP may be highly skilled, but an RPO brings organizational accountability, institutional continuity if a key practitioner leaves, and the ability to field a broader team across a complex engagement. For larger or longer-horizon CMMC programs, the RPO structure is generally the more stable choice.

 

Should You Hire a CMMC Registered Practitioner for Your Compliance Journey?

For most OSCs, the answer is yes, and the earlier the better. The implementation curve for Level 2 is steep. Realistic first-year costs for a fifty-person contractor pursuing Level 2 sit in the range of $70,000 to $350,000 once gap analysis, remediation, documentation, and assessment fees are factored in. Hiring an experienced RP early in that process tends to compress the timeline and cut the total spend, mostly by avoiding the false starts that consume budget on poorly scoped enclaves.

When Should an OSC Engage a CMMC Registered Practitioner?

Engage an RP at the point you know CMMC will appear in a contract you intend to bid on, not after the RFP lands. Most contractors who scramble at the last minute fail their first assessment, and a failed assessment carries both direct remediation cost and a multi-month delay before retest eligibility. According to GAO reporting on DoD cybersecurity readiness, implementation gaps are consistently identified as a leading cause of contractor compliance failures. Front-loading the advisory work is significantly cheaper than fixing it under time pressure.

Reach SOC 2 Compliance in 6 Weeks or Less

Schedule Your Free SOC 2 Assessment Today

How to Choose the Right CMMC Registered Practitioner

The Marketplace listing is the floor, not the ceiling. Beyond verifying credentials, OSCs should look for hands-on experience implementing controls in environments similar to their own, fluency in the specific cloud or on-premise stack they use, and a track record of clients who have completed C3PAO certification assessments cleanly.

Verify their CMMC experience.

Ask how many OSCs they have advised to a successful certification, and how many they have walked through a full C3PAO assessment, not just a gap assessment.

Check their knowledge depth.

A strong RP can explain not just what the controls require but why, and can reference the relevant section of NIST SP 800-171 or 32 CFR Part 170 without hesitation.

Understand their service scope.

Some RPs do scoping and documentation only. Others handle technical remediation and managed compliance. Match the offering to your actual gap. And always ask for references and case studies; a practitioner with real experience can produce both.

Insider Note: The most common reason OSCs fail their first assessment is scope creep, not technical gaps. They define the CUI environment too broadly, and then cannot defend every device and identity in that scope under assessor scrutiny. A good RP spends as much time narrowing the assessment boundary as expanding the controls inside it.

Conclusion

The Registered Practitioner credential is the formal entry point for anyone who wants to advise on CMMC compliance, and the most efficient way for an OSC to identify someone who has at least passed the Cyber AB’s baseline vetting.

It is not a substitute for hands-on cybersecurity experience, and it does not authorize assessment work. But in a market where over 80,000 contractors are working out what compliance actually looks like under the final rule, an RP who knows the model, the ecosystem, and the assessment process is a genuinely useful person to have on the project.

Pick carefully, engage early, and treat the credential as a starting filter rather than a guarantee.

Frequently Asked Questions About CMMC Registered Practitioners

What is a CMMC Registered Practitioner (RP)?

An individual authorized by the Cyber AB to provide non-certified CMMC consulting and advisory services to Organizations Seeking Certification.

Complete the Cyber AB RP training, pass a basic background check, sign the Code of Professional Conduct, and pay the annual registration fee.

Most candidates complete the process in two to four weeks, depending on background check turnaround. The training itself takes six to ten hours.

The RP is advisory only. The CCP is a higher credential, requires a proctored exam and commercial background check, and can participate in C3PAO-led assessments.

No. OSCs can use internal staff or any qualified consultant. The RP credential is a market signal, not a legal requirement.

The Cyber AB Marketplace is the authoritative directory of active RPs, RPAs, RPOs, and C3PAOs.

The Cyber AB is the sole accreditation body authorized by the DoD to manage CMMC training, credentialing, and ecosystem oversight.

The Code of Professional Conduct restricts how RPs and RPOs can describe their authorization, prohibits misrepresenting the scope of services they are allowed to provide, and bars any claim that suggests an RP can issue or influence formal certification decisions.

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.