Table of Contents

Reach SOC 2 Compliance in 6 Weeks or Less.

  /

  / 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

Most organizations think their AI governance is further along than it is. McKinsey’s 2026 AI Trust Maturity Survey of roughly 500 organizations found an average maturity score of 2.3 out of 4, and only about a third reported level three or higher in strategy, governance, and agentic AI oversight. Adoption is outpacing control, and regulators have noticed. An AI governance maturity model gives you a way to measure that gap honestly. This guide covers what a maturity model is, the six dimensions it should measure, the five levels most models use, and how to assess your own organization and build a roadmap to the next level. What Is an AI Governance Maturity Model? An AI governance maturity model is a structured framework that describes how capable an organization is at governing its AI systems, usually across five progressive levels. The concept borrows directly from the Capability Maturity Model (CMM) that software engineering has used since the early 1990s: define the capability, describe what it looks like at each stage of development, and score yourself against it. The purpose is diagnosis. A maturity model tells you where governance is strong, where it’s theater, and where it doesn’t exist at all. How It Differs from General AI Governance Frameworks Frameworks like the NIST AI Risk Management Framework or ISO/IEC 42001 tell you what good governance contains: policies, risk assessments, accountability structures, monitoring. A maturity model tells you how well you’re doing those things today. The framework is the destination. The maturity model is the odometer. That distinction matters in practice. Plenty of companies can point to an AI policy document. Far fewer can show that the policy changes what teams actually ship. Why Enterprises Need a Maturity Model Three reasons. First, budget: you can’t prioritize governance investment without knowing which dimension lags. Second, accountability: a maturity score gives boards something concrete to track quarter over quarter. Third, regulation: the EU AI Act and frameworks like ISO 42001 assume a functioning management system, and a maturity assessment is the fastest way to find out whether yours would survive scrutiny. Core Dimensions of an AI Governance Maturity Model A useful model measures more than policy coverage. Six dimensions show up consistently across the credible models, including the IEEE-USA flexible maturity model built on the NIST AI RMF. Strategy and leadership. Does the organization have a stated position on AI risk, an executive owner (increasingly a Chief AI Officer), and board visibility? Gartner’s 2025 polling found 55% of organizations now have an AI board or dedicated oversight committee, which means nearly half still govern by improvisation. Policies, standards, and accountability. Written policies mapped to regulations, a RACI matrix for AI decisions, and clear escalation paths. Many organizations adapt the three lines of defense model from financial risk: the teams building AI, the risk function overseeing them, and internal audit checking both. Data governance and model lifecycle. Training data lineage, quality controls, and lifecycle management from development through deployment, monitoring, and retirement. This is where AI governance meets MLOps, and where mature organizations maintain an AI register, a live inventory of every model and system in production. Risk, compliance, and ethics. Risk classification of AI systems, impact assessments, bias and fairness testing, and explainability requirements. Banks will recognize the DNA of model risk management under SR 11-7 here. People, skills, and culture. Training, role clarity, and whether people outside the governance team actually understand their obligations. Tools, automation, and monitoring. Drift detection, automated policy checks, audit logging, and dashboards. Governance that lives in spreadsheets caps out around level three. The 5 Levels of AI Governance Maturity Level 1: Ad Hoc / Initial AI use happens without oversight. There’s no inventory, no policy, or a policy nobody follows. Shadow AI is common, and risk surfaces only when something breaks publicly. Level 2: Developing / Repeatable Someone has been assigned responsibility. A draft policy exists, a partial inventory exists, and reviews happen for high-profile projects. The practices are repeatable but depend on specific people rather than defined processes. Level 3: Defined / Structured Governance is documented, standardized, and applied across the organization. There’s a governance committee, a risk classification scheme, defined lifecycle gates, and mandatory training. Most organizations pursuing ISO 42001 certification are working to reach and formalize this level. Level 4: Managed / Metrics-Driven Governance produces numbers. Coverage rates, review cycle times, incident counts, and risk reduction are measured and reported to leadership. Controls are enforced by tooling rather than goodwill, and audits confirm the system works as described. Level 5: Optimized / Adaptive Governance improves itself. Monitoring feeds back into policy, controls adapt to new model types (agentic systems being the current test), and the organization anticipates regulatory change rather than reacting to it. Almost nobody is here yet, and that’s fine. Level 5 is a direction, not a deadline. Insider Note: In assessments, the most common self-scoring error is claiming level 3 on the strength of documents alone. If your policy says every model gets a pre-deployment review and your inventory shows 40 models but your review log shows 6, you’re at level 2. Evidence beats paperwork every time, and auditors check the logs first. AI Governance Maturity Matrix The matrix crosses dimensions with levels so you can score each one independently. Organizations are rarely uniform: it’s normal to sit at level 3 on policy and level 1 on monitoring. For scoring, keep the rubric simple: 1 to 5 per dimension, scored on evidence you could show an auditor, not on intentions. Board-level indicators (does the board see AI risk reporting?) and operational indicators (does every production model have a completed impact assessment?) should be scored separately, because they fail independently. How to Assess Your Current AI Governance Maturity Start with a baseline self-assessment. Pull together a cross-functional group covering engineering, legal, risk, security, and the business owners of major AI use cases, and score each dimension against the matrix. Half a day is usually enough for a first pass. For each dimension, the

Most organizations get ISO 42001 certified in 2 to 9 months. Companies that already hold ISO 27001 regularly land in the 2 to 5 month range, while enterprises with sprawling AI portfolios and no existing management system can take 12 months or more. The audit itself only takes days. Almost the entire calendar goes into building and operating your AI Management System (AIMS) long enough to produce evidence an auditor can actually check. That is the short answer. The longer answer depends on your starting point, your scope, and how quickly you can get a certification body on the schedule. This article breaks down the full timeline phase by phase, the factors that stretch or compress it, and what the recertification cycle looks like once you hold the certificate. Typical ISO 42001 Certification Timeline at a Glance ISO/IEC 42001:2023 is the first international standard for AI management systems, published in December 2023. Because it follows the same harmonized structure as ISO 27001 and ISO 9001, the certification process will feel familiar to anyone who has been through a management system audit: build the system, run it, pass a Stage 1 and Stage 2 audit, then maintain it through annual surveillance. Here is how timelines typically break down by company size. Average Timeline for Small Businesses Small companies move fastest because scope stays contained. A startup with two or three AI systems, a handful of decision makers, and short approval chains can finish scoping in a week and get policies signed off in days rather than weeks. The realistic floor for a small business starting from scratch is around 3 months. With an existing ISO 27001 program and a compliance platform already collecting evidence, 2 months is achievable. Average Timeline for Mid-Sized Companies Mid-sized companies usually take 6 to 9 months. The AI inventory is growing, more departments are touching AI systems, and risk assessments have to cover more use cases. Coordination becomes the hidden cost: getting engineering, legal, and product to agree on an AI policy takes longer than writing the policy itself. Average Timeline for Enterprises Enterprises should plan for 9 to 12 months, sometimes longer. The main drivers are AI system sprawl across business units, longer procurement cycles for certification bodies, and audits that take more days. The Stage 2 audit for a large multinational can run two weeks or more on its own, and internal alignment before the audit takes far longer than the audit itself. Breakdown of the ISO 42001 Certification Timeline by Phase The phases below overlap in practice. Treat the durations as effort estimates for a reasonably resourced program, not a strict sequence. Phase 1: Scoping and Gap Analysis (2–4 Weeks) Everything starts with two questions: which AI systems are in scope, and how far is your current governance from what the standard requires? The gap analysis maps your existing policies and controls against the standard’s clauses and Annex A controls, and produces the project plan for everything that follows. Get the scope wrong here and every later phase inherits the mistake. Phase 2: AIMS Design, Leadership, and AI Policy Development (2–4 Weeks) This phase establishes the skeleton of the management system: the AI policy, governance roles, objectives, and the leadership commitments the standard requires. Executive sign-off is the gating item. The documents are not hard to write. Getting senior leadership to formally own AI governance is where programs stall. Phase 3: AI Risk and Impact Assessments (2–6 Weeks) ISO 42001 requires both AI risk assessments and AI impact assessments, and the distinction matters. Risk assessments look at what could go wrong for the organization. Impact assessments look at consequences for individuals and society, which is a newer discipline for most teams. This phase takes longer when you have many AI systems, high-risk use cases, or no prior methodology to adapt. The output feeds directly into your Statement of Applicability (SoA), the document that maps which Annex A controls you have selected and why. Insider Note: Impact assessments are where auditors probe hardest, because they are the most distinctive part of ISO 42001 compared with ISO 27001. A recycled security risk register with “AI” pasted into it will get picked apart in Stage 2. Build the impact assessment methodology properly the first time. Phase 4: Controls Implementation (2–10 Weeks) The longest phase. Here you implement the Annex A controls selected in your SoA: AI system lifecycle documentation, data governance for training data, human oversight mechanisms, transparency measures, supplier management for third-party AI, and so on. Duration depends almost entirely on the gap analysis results. Organizations with mature engineering practices often find they already do much of this and just need to document it. Organizations without formal AI development processes are building from zero. Phase 5: Documentation, Training, and Evidence Collection (2–8 Weeks) Certification requires proof that the system operates, not just that it exists on paper. That means records: training completion logs, risk assessment outputs, review meeting minutes, monitoring reports. This phase runs partly in parallel with implementation, but it cannot be compressed below a certain floor because auditors want to see evidence generated over time, not a folder of documents all created the week before Stage 1. Phase 6: Internal Audit and Management Review (2–4 Weeks) The standard requires an internal audit of the AIMS and a formal management review before the certification audit. This is your dress rehearsal. A good internal audit surfaces nonconformities while they are still cheap to fix. Skipping or rushing it is a false economy that shows up later as Stage 2 findings. Phase 7: Stage 1 Certification Audit (1–2 Weeks) The certification body reviews your documentation and assesses readiness for Stage 2. The audit itself takes 1 to 3 days for most organizations. The auditor examines your scope statement, AI policy, risk and impact assessment methodology, SoA, and internal audit results, then issues findings. The 1–2 week window covers the audit plus the report. Phase 8: Closing Nonconformities (2–4 Weeks) Almost every Stage 1 produces findings.

How Axipro Guided Technovative Solutions & DigiProd Pass to ISO 27001