Table of Contents

Reach SOC 2 Compliance in 6 Weeks or Less.

  /

  / What Is a 3PAO? The Independent Assessor Behind FedRAMP

What Is a 3PAO? The Independent Assessor Behind FedRAMP

A 3PAO is the independent firm that decides whether a cloud service is secure enough to handle federal data. The acronym stands for Third-Party Assessment Organization, and these accredited auditors sit at the center of the FedRAMP process. A federal agency will not grant an Authority to Operate (ATO) at the Moderate or High impact level without a 3PAO assessment behind it.

That makes the 3PAO one of the most consequential vendors a cloud service provider (CSP) will hire on the road to the federal market. This guide explains what a 3PAO is, what it actually does, how a firm earns the accreditation, and when you should bring one in. It also covers how the role is changing under FedRAMP’s 2025 overhaul, because the job looks different now than it did even a year ago.

What Is a 3PAO

What Does 3PAO Stand For?

3PAO stands for Third-Party Assessment Organization. The “third party” part is the whole point. The assessor is independent of both the cloud provider being evaluated and the government agency relying on the results. That independence is what gives a 3PAO report its weight. An agency can trust the findings precisely because the assessor has no stake in the outcome.

Reach SOC 2 Compliance in 6 Weeks or Less

Schedule Your Free SOC 2 Assessment Today

What Is a 3PAO?

A 3PAO is an independent firm accredited to evaluate the security of cloud services seeking authorization under FedRAMP, the Federal Risk and Authorization Management Program. The FedRAMP Program Management Office (PMO) recognizes these firms only after they pass a demanding accreditation process. Once recognized, a 3PAO is listed publicly on the FedRAMP Marketplace under the Assessors tab, where CSPs and agencies can find them.

3PAOs are not limited to federal work. The same firms are commonly authorized to perform GovRAMP assessments, the program formerly known as StateRAMP, for state and local government cloud procurement. The skill set transfers directly, since both programs lean on the same NIST control foundations.

What does a 3PAO do

What Does a 3PAO Do?

A 3PAO independently tests whether a cloud service offering (CSO) does what its documentation claims. The longer version breaks into four distinct areas:

1- Independent Security Assessments

The core deliverable is a security assessment. The 3PAO evaluates a CSP’s controls against the relevant FedRAMP baseline, which maps to NIST SP 800-53. It builds a Security Assessment Plan (SAP), executes the testing, and documents the findings in a Security Assessment Report (SAR). The SAR is the artifact an agency’s Authorizing Official reads when deciding whether to grant an ATO.

2- Documentation Review and Validation

Before any testing happens, the 3PAO reviews the System Security Plan (SSP), the primary document describing how each control is implemented. SSPs routinely run to hundreds of pages, and a vague or incomplete one will stall the schedule fast. The assessor checks that what the SSP claims matches what the system actually does, then tracks unresolved issues in a Plan of Action and Milestones (POA&M).

3- Penetration Testing

FedRAMP assessments include mandatory penetration testing, and the 3PAO performs it. The assessor probes the system the way an attacker would, looking for exploitable weaknesses that control documentation alone would never surface. A clean SSP means little if a tester can walk straight through the front door.

4- Ongoing Continuous Monitoring Support

Authorization is not a one-time event. CSPs must sustain compliance through continuous monitoring (ConMon), which includes regular scanning, vulnerability remediation, and periodic reassessment. 3PAOs often support annual assessments and significant-change reviews. One structural note worth tracking: as of March 2025, FedRAMP stopped running centralized continuous monitoring, and that responsibility now sits with each sponsoring agency.

Worth knowing: 3PAO Reports

FedRAMP states that 3PAO reports "serve as the basis from which the federal government makes informed, risk-based authorization decisions." The assessment is not a formality. It is the evidence the entire authorization rests on.

How Does an Organization Become an Accredited 3PAO?

Becoming a 3PAO is nearly as demanding as the assessments these firms perform. There is one accreditation body, and the bar is high.

A2LA Accreditation Requirements

The American Association for Laboratory Accreditation (A2LA) is the sole body that accredits FedRAMP 3PAOs. Its FedRAMP 3PAO accreditation program puts applicants through a rigorous evaluation of technical competence. A firm must spend at least a year in A2LA’s Cybersecurity Inspection Body Program before it can even be considered for FedRAMP recognition, and it must pass technical proficiency testing administered through A2LA’s testing partner.

ISO/IEC 17020 Compliance

Accreditation hinges on conformance with ISO/IEC 17020, the international standard for bodies that perform inspections. The standard sets requirements for impartiality, independence, technical competence, and a functioning quality management system. In practice, this is what stops a 3PAO from cutting corners or playing favorites. The accreditation certifies the firm’s process, not just the talent of its people.

FedRAMP-Specific Requirements

Beyond ISO/IEC 17020, FedRAMP layers on its own recognition requirements covering program-specific knowledge and assessment methodology. A firm has to demonstrate it understands FedRAMP’s baselines, templates, and reporting expectations — not just general inspection practice. Only after clearing both bars does the firm appear on the Marketplace as a recognized 3PAO.

Why are 3PAOs Important for FedRAMP

Why Are 3PAOs Important for FedRAMP?

FedRAMP runs on a “do once, use many” philosophy. One rigorous, independent assessment lets multiple federal agencies reuse the same authorization package instead of each running its own review. The 3PAO is what makes that trust transferable. Because the assessor is accredited and independent, an agency in one department can rely on a SAR produced for another.

The program exists because federal systems must meet security obligations set under FISMA, the Federal Information Security Modernization Act, and the General Services Administration (GSA) runs FedRAMP to standardize how cloud services meet them. Without accredited assessors, every agency would judge cloud security on its own terms — which is exactly the fragmentation FedRAMP was built to end.

Worth knowing: The FedRAMP Authorization

The FedRAMP authorization landscape changed significantly in 2024 and 2025. The Joint Authorization Board (JAB) and its provisional ATO path were dissolved under OMB Memorandum M-24-15, leaving a single "FedRAMP Authorized" designation. Authorizations now flow through agency authorization or the new 20x path, but the 3PAO's role as independent assessor carried straight through the transition.

Who Needs to Work with a 3PAO?

Any CSP that wants to sell a cloud service to the federal government at the Moderate or High impact level needs a 3PAO. At those levels, the assessment is mandatory, and an authorization package cannot be accepted without it. Providers handling federal data, contractors building CSOs for agency use, and vendors pursuing GovRAMP all fall into the same category.

At the Low impact level, the picture is more flexible, and the emerging 20x pathway is reshaping expectations there. Still, the safe assumption for most providers chasing meaningful federal business is that an independent assessment will be required at some point. The question is usually when, not whether.

One common point of confusion: a 3PAO is not a C3PAO. The names differ by a single letter, but they serve different programs. A 3PAO assesses cloud services for FedRAMP authorization and is accredited by A2LA. A Certified Third-Party Assessor Organization (C3PAO) assesses defense contractors for CMMC, the Cybersecurity Maturity Model Certification, and is authorized by the Cyber AB rather than A2LA. A handful of firms hold both, but the credentials are entirely separate.

Reach SOC 2 Compliance in 6 Weeks or Less

Schedule Your Free SOC 2 Assessment Today

How to Find an Accredited 3PAO

Start with the FedRAMP Marketplace. Its Assessors tab is the authoritative, public list of recognized 3PAOs, and any firm not on it is not a valid FedRAMP assessor — full stop. From there, the real work is vetting fit rather than legitimacy.

Pro tip: Do not choose on price or brand alone.

Do not choose on price or brand alone. Ask for verified experience at your target impact level, the names and credentials of the assessors who will actually do the work, and redacted samples that show SAR quality. A cheap assessment that an agency rejects is the most expensive option there is.

When Should You Engage a 3PAO?

Timing matters. Engage a 3PAO after your system and security program have matured, not before. Bringing in an assessor while controls are half-built guarantees findings, delays, and rework you will pay for twice. Most providers take a readiness step first, often producing a Readiness Assessment Report (RAR), which FedRAMP strongly recommends for the agency authorization process and which surfaces gaps before the formal assessment begins.

Insider note: FedRAMP 20x is changing when and how you work with assessors. As the program shifts toward automated, machine-readable validation built on Key Security Indicators and OSCAL, the 3PAO’s job is moving from reviewing screenshots to verifying that automated checks actually enforce the controls they claim to. Assessors now validate and verify rather than certify, and the CSP carries responsibility for the accuracy of what it submits. Expect to involve a 3PAO earlier in your process, and expect the engagement to be far more technical than the old document-review model.

There is also a hard rule worth flagging on independence. A 3PAO can offer advisory or consulting services, but it cannot assess a system it helped build. If you use one 3PAO as an advisor, you must hire a different one to perform the assessment, or the impartiality that A2LA accreditation depends on collapses entirely.

 

The Bottom Line

A 3PAO is the independent, accredited firm that turns a cloud provider’s security claims into evidence an agency can act on. The role is mandatory at higher impact levels, the accreditation behind it is hard-won, and the way 3PAOs work is shifting fast under FedRAMP 20x. Choose carefully, engage at the right moment, and treat the assessment as what it is: the foundation your entire authorization stands on.

Frequently Asked Questions

Is a 3PAO the same as an auditor?

Functionally, yes — with a caveat. A 3PAO performs an independent assessment much like a financial auditor, but under FedRAMP 20x the framing has shifted. Assessors now validate and verify a provider’s security claims rather than certify them or recommend an ATO. The agency, not the assessor, makes the final authorization decision.

There is no fixed price, and the assessment is only one line item in a larger FedRAMP budget. The fee scales with impact level, system complexity, and scope. Serious engagements run well into six figures — industry estimates commonly place a full initial FedRAMP authorization in the low-to-mid six figures once preparation, the assessment itself, and remediation are included. Get fixed-scope quotes from more than one recognized 3PAO before committing.

Yes, but not for the same system it assesses. FedRAMP allows 3PAOs to act as advisors, but impartiality rules mean a separate, independent 3PAO must perform the actual assessment of a service the first firm helped prepare. Mixing the two roles on one engagement is not permitted.

Accreditation is not permanent. A2LA recognition runs on a recurring cycle with ongoing surveillance and periodic reassessment, and a 3PAO must keep demonstrating independence, quality, and current FedRAMP knowledge to hold its standing. Firms that let competence or impartiality slip can lose recognition.

The FedRAMP PMO, operated under the GSA, recognizes 3PAOs and sets program requirements. A2LA is the sole accreditation body and verifies conformance with ISO/IEC 17020 plus FedRAMP-specific criteria. Recognized firms appear on the FedRAMP Marketplace.

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

A 3PAO is the independent firm that decides whether a cloud service is secure enough to handle federal data. The acronym stands for Third-Party Assessment Organization, and these accredited auditors sit at the center of the FedRAMP process. A federal agency will not grant an Authority to Operate (ATO) at the Moderate or High impact level without a 3PAO assessment behind it. That makes the 3PAO one of the most consequential vendors a cloud service provider (CSP) will hire on the road to the federal market. This guide explains what a 3PAO is, what it actually does, how a firm earns the accreditation, and when you should bring one in. It also covers how the role is changing under FedRAMP’s 2025 overhaul, because the job looks different now than it did even a year ago. What Does 3PAO Stand For? 3PAO stands for Third-Party Assessment Organization. The “third party” part is the whole point. The assessor is independent of both the cloud provider being evaluated and the government agency relying on the results. That independence is what gives a 3PAO report its weight. An agency can trust the findings precisely because the assessor has no stake in the outcome. What Is a 3PAO? A 3PAO is an independent firm accredited to evaluate the security of cloud services seeking authorization under FedRAMP, the Federal Risk and Authorization Management Program. The FedRAMP Program Management Office (PMO) recognizes these firms only after they pass a demanding accreditation process. Once recognized, a 3PAO is listed publicly on the FedRAMP Marketplace under the Assessors tab, where CSPs and agencies can find them. 3PAOs are not limited to federal work. The same firms are commonly authorized to perform GovRAMP assessments, the program formerly known as StateRAMP, for state and local government cloud procurement. The skill set transfers directly, since both programs lean on the same NIST control foundations. What Does a 3PAO Do? A 3PAO independently tests whether a cloud service offering (CSO) does what its documentation claims. The longer version breaks into four distinct areas: 1- Independent Security Assessments The core deliverable is a security assessment. The 3PAO evaluates a CSP’s controls against the relevant FedRAMP baseline, which maps to NIST SP 800-53. It builds a Security Assessment Plan (SAP), executes the testing, and documents the findings in a Security Assessment Report (SAR). The SAR is the artifact an agency’s Authorizing Official reads when deciding whether to grant an ATO. 2- Documentation Review and Validation Before any testing happens, the 3PAO reviews the System Security Plan (SSP), the primary document describing how each control is implemented. SSPs routinely run to hundreds of pages, and a vague or incomplete one will stall the schedule fast. The assessor checks that what the SSP claims matches what the system actually does, then tracks unresolved issues in a Plan of Action and Milestones (POA&M). 3- Penetration Testing FedRAMP assessments include mandatory penetration testing, and the 3PAO performs it. The assessor probes the system the way an attacker would, looking for exploitable weaknesses that control documentation alone would never surface. A clean SSP means little if a tester can walk straight through the front door. 4- Ongoing Continuous Monitoring Support Authorization is not a one-time event. CSPs must sustain compliance through continuous monitoring (ConMon), which includes regular scanning, vulnerability remediation, and periodic reassessment. 3PAOs often support annual assessments and significant-change reviews. One structural note worth tracking: as of March 2025, FedRAMP stopped running centralized continuous monitoring, and that responsibility now sits with each sponsoring agency. Worth knowing: 3PAO Reports FedRAMP states that 3PAO reports “serve as the basis from which the federal government makes informed, risk-based authorization decisions.” The assessment is not a formality. It is the evidence the entire authorization rests on. How Does an Organization Become an Accredited 3PAO? Becoming a 3PAO is nearly as demanding as the assessments these firms perform. There is one accreditation body, and the bar is high. A2LA Accreditation Requirements The American Association for Laboratory Accreditation (A2LA) is the sole body that accredits FedRAMP 3PAOs. Its FedRAMP 3PAO accreditation program puts applicants through a rigorous evaluation of technical competence. A firm must spend at least a year in A2LA’s Cybersecurity Inspection Body Program before it can even be considered for FedRAMP recognition, and it must pass technical proficiency testing administered through A2LA’s testing partner. ISO/IEC 17020 Compliance Accreditation hinges on conformance with ISO/IEC 17020, the international standard for bodies that perform inspections. The standard sets requirements for impartiality, independence, technical competence, and a functioning quality management system. In practice, this is what stops a 3PAO from cutting corners or playing favorites. The accreditation certifies the firm’s process, not just the talent of its people. FedRAMP-Specific Requirements Beyond ISO/IEC 17020, FedRAMP layers on its own recognition requirements covering program-specific knowledge and assessment methodology. A firm has to demonstrate it understands FedRAMP’s baselines, templates, and reporting expectations — not just general inspection practice. Only after clearing both bars does the firm appear on the Marketplace as a recognized 3PAO. Why Are 3PAOs Important for FedRAMP? FedRAMP runs on a “do once, use many” philosophy. One rigorous, independent assessment lets multiple federal agencies reuse the same authorization package instead of each running its own review. The 3PAO is what makes that trust transferable. Because the assessor is accredited and independent, an agency in one department can rely on a SAR produced for another. The program exists because federal systems must meet security obligations set under FISMA, the Federal Information Security Modernization Act, and the General Services Administration (GSA) runs FedRAMP to standardize how cloud services meet them. Without accredited assessors, every agency would judge cloud security on its own terms — which is exactly the fragmentation FedRAMP was built to end. Worth knowing: The FedRAMP Authorization The FedRAMP authorization landscape changed significantly in 2024 and 2025. The Joint Authorization Board (JAB) and its provisional ATO path were dissolved under OMB Memorandum M-24-15, leaving a single “FedRAMP Authorized” designation. Authorizations now flow through agency authorization or

The NIST AI Risk Management Framework (AI RMF 1.0) is the most widely referenced standard for managing AI risk in the United States, and it is not a law, a regulation, or a certifiable standard. It is voluntary guidance. That combination explains both its rapid adoption and the confusion around it: regulators cite it, enterprise buyers ask about it in security questionnaires, and AI governance programs are built on it, yet no auditor will ever hand you an AI RMF certificate. This article explains what the framework actually contains, how its four core functions work, and where it fits alongside ISO/IEC 42001 and the EU AI Act. What Is the NIST AI RMF 1.0? Background and Purpose of the Framework The AI RMF is a structured approach for identifying, assessing, and managing the risks that AI systems create across their entire lifecycle, from design and data collection through deployment, monitoring, and decommissioning. Its stated goal is to help organizations build and use AI systems that are trustworthy: valid, reliable, safe, secure, accountable, transparent, explainable, privacy-enhanced, and fair. The framework treats AI as a socio-technical system, meaning risk does not come from models and data alone. It also comes from how people build, deploy, oversee, and interact with those systems. That framing is the single most important idea in the document, because it pushes risk management beyond model accuracy metrics and into governance, human oversight, and organizational culture. Who Published It and When The framework was published by the National Institute of Standards and Technology (NIST), an agency of the U.S. Department of Commerce, on January 26, 2023. The official document is NIST AI 100-1, developed over 18 months of public workshops, requests for information, and two public draft rounds. Congress directed NIST to create it through the National Artificial Intelligence Initiative Act of 2020, so the framework carries legislative backing even though compliance with it does not. Voluntary Nature of the Framework NIST describes the AI RMF as voluntary, rights-preserving, non-sector-specific, and use-case agnostic. There is no enforcement mechanism, no audit regime, and no certification. In practice, the word voluntary undersells its weight. U.S. regulators, including the FTC and sector agencies, reference NIST principles when assessing whether an organization exercised reasonable care; federal contractors face growing expectations to demonstrate NIST-aligned AI governance, and enterprise procurement teams increasingly ask vendors how they apply it. Voluntary frameworks have a habit of becoming de facto requirements, and the AI RMF is following that exact path. Insider Note: In vendor risk assessments, “do you align with the NIST AI RMF” is becoming the AI equivalent of “do you have a SOC 2 report.” There is no certificate to show, so what buyers actually want is documented evidence: an AI inventory, a risk assessment methodology, and named accountability for AI decisions. Organizations that can produce those three artifacts pass most questionnaires. Why the NIST AI RMF 1.0 Was Developed Addressing Unique AI Risks Traditional software risk frameworks assume deterministic systems: the same input produces the same output, and failures are traceable to specific defects. AI systems break those assumptions. Models drift as real-world data shifts; training data can embed historical bias at scale; outputs can be opaque even to their developers; and the same model can behave differently across deployment contexts. The AI RMF was built specifically for these properties. It treats risk as continuous rather than one-shot, requiring ongoing measurement and monitoring instead of a single pre-deployment review. Building Trustworthy AI Systems The second driver was the trust gap. By 2022, organizations were deploying AI faster than they could explain or govern it, and high-profile failures in hiring, lending, and facial recognition had made AI bias a mainstream concern. NIST’s answer was to define trustworthiness in operational terms rather than aspirational ones, breaking it into seven measurable characteristics that risk, security, and product teams could actually work against. Key Drivers Behind Its Creation Three forces converged. First, the congressional mandate in the National AI Initiative Act of 2020. Second, international momentum: the framework explicitly aligns with the OECD AI Principles, positioning U.S. guidance within a global consensus on responsible AI. Third, industry demand for a shared vocabulary. Before the AI RMF, every organization defined AI risk differently, which made procurement, audits, and cross-industry collaboration unnecessarily painful. The framework gave executives, engineers, auditors, and regulators a common language. Core Concepts Behind the NIST AI RMF 1.0 Defining AI Risk The framework defines risk as the composite measure of an event’s probability of occurring and the magnitude of its consequences. Two things distinguish the AI RMF’s treatment of risk from older frameworks. It explicitly considers positive impacts as well as harms, framing risk management as a way to maximize benefits, not just avoid downsides. And it acknowledges that AI risk is genuinely hard to measure: third-party models, emergent behavior, and a lack of agreed metrics mean organizations must often manage risks they cannot precisely quantify. Characteristics of Trustworthy AI Systems The AI RMF defines seven characteristics of trustworthy AI: valid and reliable; safe; secure and resilient; accountable and transparent; explainable and interpretable; privacy-enhanced; and fair with harmful bias managed. Validity and reliability is described as a necessary precondition for all the others, since an inaccurate system cannot be meaningfully safe or fair. The framework is candid that these characteristics involve trade-offs. Improving explainability can reduce accuracy, and strengthening privacy can limit the data available for bias testing. Managing those tensions is a governance decision, not a technical one. Framing Risks: Harms to People, Organizations, and Ecosystems The framework organizes potential harm into three groups. Harm to people covers individual civil liberties, physical and psychological safety, and economic opportunity, as well as harm to communities and society at large. Harm to organizations covers business disruption, security breaches, financial loss, and reputational damage. Harm to ecosystems covers damage to interconnected systems, including the global financial system, supply chains, and natural resources. This breadth is deliberate. It forces impact assessments to look beyond the deploying organization’s own balance

Every defense contractor that handles Controlled Unclassified Information (CUI) has a number attached to its CAGE code in a DoD database. That number ranges from -203 to a perfect 110 and most organizations that calculate it honestly for the first time land somewhere they would rather not advertise. This guide covers how CMMC scoring works: where the number comes from, what counts as a passing score at each CMMC level, how to calculate and submit a score in SPRS, and where Plans of Action and Milestones (POA&Ms) fit in. What Is CMMC Scoring? CMMC 2.0 is the Department of Defense program for verifying that companies in the Defense Industrial Base (DIB) actually protect Federal Contract Information (FCI) and CUI, rather than simply attesting that they do. The program rule, 32 CFR Part 170, took effect in December 2024, and the acquisition rule that inserts CMMC requirements into contracts via DFARS 252.204-7021 began phasing in from November 2025. Phase 2, which makes third-party certification the default for contracts involving CUI, arrives in November 2026. CMMC scoring is the quantitative layer underneath all of this. At Level 2, the score measures implementation of the 110 security requirements of NIST SP 800-171, the standard that has applied to contractors handling CUI since DFARS 252.204-7012 made it mandatory. CMMC did not invent new controls at Level 2; it created a verification and scoring regime around controls contractors were already obligated to implement. The score matters for three practical reasons. It determines contract eligibility, because solicitations now specify a required CMMC status and contracting officers check SPRS before award. It drives prime contractor flow-downs, since primes must verify subcontractor scores before passing CUI down the supply chain. And it creates legal exposure: a senior official affirms the score, and a knowingly inflated number is a False Claims Act problem, not a paperwork problem. Understanding the SPRS Scoring System The Supplier Performance Risk System (SPRS) is the DoD’s authoritative source for supplier risk information. For cybersecurity purposes, it stores the results of NIST SP 800-171 assessments and CMMC statuses against each contractor’s CAGE code. Contracting officers, programme offices, and DCMA personnel query it routinely; prime contractors can verify that a subcontractor has a current assessment on file. SPRS does not perform the assessment. It is a reporting database. Self-assessment scores are entered directly by the contractor through the Procurement Integrated Enterprise Environment (PIEE). Results of third-party certification assessments are entered by the C3PAO into the CMMC instance of eMASS, which then populates SPRS automatically. The relationship between an SPRS score and CMMC certification is straightforward: same methodology, different assessor. The self-assessment score is your own claim about your posture. A CMMC Level 2 certification is the same 110 requirements scored by a Certified Third-Party Assessment Organization (C3PAO), with the result carrying formal status under the programme rule. A contractor whose self-reported 110 collapses to 60 under C3PAO scrutiny has a credibility problem on the record. The CMMC Scoring Methodology Explained The methodology comes from the NIST SP 800-171 DoD Assessment Methodology, Version 1.2.1, now codified for CMMC in 32 CFR 170.24. Every organisation starts at the maximum of 110 points. For every requirement scored NOT MET, a weighted value of 1, 3, or 5 points is subtracted. The weighting reflects security impact. Five-point requirements are those whose absence exposes the network or CUI directly. Three-point requirements have a specific, meaningful effect on security. One-point requirements have a limited or indirect effect. Because total possible deductions add up to 313, the floor is -203. Negative scores are common on a first honest assessment, and they are not a clerical curiosity: a deeply negative number visible to a contracting officer signals an organisation years away from certification. There is no partial credit. A requirement that is 90 percent implemented deducts its full point value, exactly like one that was never started. The only two exceptions are multi-factor authentication (3.5.3), which deducts 3 points instead of 5 if MFA covers remote and privileged users but not all users, and FIPS-validated encryption (3.13.11), which deducts 3 points instead of 5 if encryption is in place but not FIPS-validated. Everything else is binary. One further prerequisite catches people out: a System Security Plan (3.12.4) must exist at the time of assessment. Without an SSP describing how each requirement is met, the assessment cannot be completed at all, and the absence is treated as non-compliance with DFARS 252.204-7012 rather than as a scoring deduction. CMMC Score Requirements by Level Scoring works differently at each of the three CMMC levels, and the term passing score means something different at each.  Level 1 Level 1 sits apart from both Level 2 and Level 3: it requires an annual self-assessment of just 15 basic safeguarding requirements, carries no numeric score, permits no POA&Ms, and requires only an annual affirmation. There is no minimum number to hit because the assessment is pass/fail on each individual requirement. Level 2 At Level 2, the 110-point methodology applies in full. A score of 110 earns Final Level 2 status. A score of at least 88, where every unmet requirement is POA&M-eligible under 32 CFR 170.21, earns Conditional Level 2 status — but only as a temporary bridge to the full 110. At  Level 3 Level 3, the bar rises further: organizations must first hold Final Level 2 status from a C3PAO assessment, then undergo a DIBCAC-led assessment against the 24 enhanced requirements drawn from NIST SP 800-172 requirements, each worth a single point. The Level 2 thresholds deserve emphasis because they are widely misread. A score of 88 does not mean you passed. It means you are eligible for Conditional Level 2 status, and only if every unmet requirement is one the rule allows on a POA&M. Conditional status starts a 180-day clock. Final Level 2 status requires the full 110, achieved either at the initial assessment or at the POA&M closeout assessment. How to Calculate Your CMMC Score The most reliable way to calculate your score is