2025 Impact Summary is now live (12/16/25)
[RRCoP Question and Use Cases] [View & Download Full Fraizer & Deeter Responses]
How does the general assessment process go from that initial approach through a final certification?
INITIAL APPROACH
At what point in time should a university approach a C3PAO? What should the university have already
completed or be prepared for that initial meeting or intake? What happens if the C3PAO determines that the university is not prepared?
JUST BEFORE THE ASSESSMENT
If the university has “passed” the initial conversation with the C3PAO and negotiated terms, pricing and schedule, what should the university have prepared for the actual assessment?
DURING THE ASSESSMENT
What should the university expect during the assessment? What if an objective is NOT MET? What if the university disagrees with the finding, what is the best way to discuss or approach that disagreement?
AFTER THE ASSESSMENT
What should the university expect after the assessment? How long should the university expect to wait for their final certification to appear in SPRS?
For more information, Contact: Bob Woosley | Frazier & Deeter National Practice Leader | bob.woosley@frazierdeeter.com
Readiness is not defined by future plans or partial implementations, but by demonstrable, operational controls supported by accurate documentation and informed personnel. The framework below reflects assessor expectations and highlights the foundational steps a university should have completed prior to engaging a Certified Third Party Assessment Organization (C3PAO).
Establishing Applicability and Defining Scope: CMMC readiness begins with clarity— does CMMC apply? And if so, which contracts and what environments? Assessment-ready institutions have correctly scoped their FCI and/or CUI environment, including a complete asset inventory (systems, applications, networks, facilities, staff, etc.) within the defined boundaries. For areas that are considered out of scope, these are explicitly documented with justification.
Identifying Controlled Unclassified Information (CUI): Universities must demonstrate a clear understanding of what CUI they are receiving, generating, processing, storing, and/or transmitting. Establishing consistent labeling and designation practices should be followed.
Policies, Procedures, and Governance: Documentation is a critical role in the CMMC assessment. Policies and procedures should align with all applicable domains and operational practices. Additionally, any exceptions or compensating controls should also be well documented.
Technical Controls: CMMC technical controls should be implemented, properly configured, and operating effectively, with sufficient evidence available to demonstrate their existence and effectiveness.
Completion of Core CMMC Artifacts: Certain artifacts are foundational to a Level 2. CMMC assessment and must be finalized prior to assessment. These include:
System Security Plan
Plan of Action and Milestones (POA&M) if any remaining gaps exist
Current network diagrams, data flow diagrams, and asset inventories
Readiness Assessment or Mock Assessment: Universities should validate their CMMC posture before engaging with a C3PAO through a formal readiness assessment or mock audit. This step provides an objective evaluation of the institution’s maturity and helps counter common tendencies to overestimate control effectiveness due to internal ownership. Skipping this validation often results in unexpected gaps and preventable failures during the initial certification attempt; engaging a qualified, independent expert can significantly reduce this risk.
Leadership and Subject Matter Expert (SME) Buy-In and Preparation: CMMC readiness within a university setting cannot be achieved through IT or compliance teams alone. Meaningful engagement from executive leadership, research leadership, and key subject matter experts (SMEs) is essential to both assessment success and long-term sustainability.
True readiness for a C3PAO assessment is demonstrated not by plans or partial implementations, but by the ability to withstand an assessment-like evaluation. Organizations that are prepared for certification have completed a formal readiness review and mock assessment that mirrors the structure and rigor of a C3PAO engagement. This includes validating assessment scope, confirming that controls are fully implemented and operating, and ensuring that documentation—particularly the System Security Plan (SSP)—accurately reflects the environment. A mock assessment allows organizations to identify gaps, inconsistencies, and misunderstandings before they become formal findings.
Equally important, readiness assessments test people and processes, not just technology. Through interviews, evidence reviews, and technical walkthroughs, organizations can evaluate whether subject matter experts, leadership, and system users can clearly explain how controls function in practice and how CUI is protected. Mock assessments frequently surface issues such as undocumented workarounds, unclear ownership, or misalignment between policy and operational reality—issues that are difficult to detect through self attestation alone.
Organizations that complete a mock assessment and remediate identified gaps enter the C3PAO assessment with confidence and stability. Scope is locked, evidence is organized, and personnel understand their roles in the assessment process. From an assessor’s perspective, this level of preparedness signals program maturity and significantly reduces assessment friction, delays, and the risk of unsuccessful certification on the first attempt.
At intake, the C3PAO is validating whether the institution is positioned to proceed with a formal assessment—not identifying gaps or providing guidance. Universities should be prepared to present a finalized assessment scope, including in-scope systems, research environments, and personnel, along with confirmation of the applicable CMMC level. Additionally, the university should demonstrate organizational readiness. This includes identifying assessment points of contact, confirming leadership sponsorship, and ensuring that key subject matter experts can participate in interviews and walkthroughs. If the C3PAO determines during intake or early assessment activities that the university is not prepared, the engagement typically cannot proceed as planned. The C3PAO may recommend postponing the assessment until readiness gaps are addressed, resulting in delays to certification timelines and additional cost. In some cases, if an assessment proceeds and significant deficiencies are identified, the outcome may be an unsuccessful assessment requiring remediation and reassessment. These additional remediation and reassessment activities come with increased cost and hours that are in addition to the agreed upon assessment fees.
During a C3PAO assessment, universities should expect a structured, evidence-driven evaluation of both technical controls and organizational processes. The assessment is designed to verify that all in-scope systems, personnel, and practices meet the requirements of the applicable CMMC level. It is not a consultative review—the assessor will not provide remediation guidance—and outcomes are based solely on the evidence presented and the demonstration of operational controls. Key elements of the assessment typically include:
Opening Briefing: An initial meeting with university leadership and key stakeholders to review scope, schedule, and logistics. This sets expectations for interviews, evidence review, and demonstrations.
Documentation Review: Assessors will examine the System Security Plan (SSP), policies, procedures, network diagrams, asset inventories, and other supporting artifacts. Documentation must align with operational reality.
Interviews: Faculty, researchers, IT staff, and leadership may be interviewed to confirm understanding of roles, responsibilities, and how CUI is protected. Assessors evaluate whether personnel follow documented procedures and can explain implemented controls.
Technical Walkthroughs and Demonstrations: In-scope systems and controls will be demonstrated to show they operate as described. This may include access control mechanisms, encryption, logging, monitoring, incident response procedures, and other security practices.
Observation and Evidence Validation: Assessors may request logs, reports, and other evidence to validate that controls are not only implemented but consistently operational.
Closing Briefing: At the conclusion of the assessment, the assessor typically summarizes preliminary observations, clarifies evidence gaps, and outlines next steps, although formal findings are documented separately.
A “Not Met” finding does not automatically result in a failed CMMC assessment; however, it affects the overall score and may be eligible for remediation through a Plan of Action and Milestones (POA&M), depending on the specific control. All POA&Ms must be completed and closed within 180 days of the Conditional CMMC Status Date. It is important to note that higher- weight controls, such as those assigned 3- or 5-point values, are not eligible for POA&M remediation and must be fully implemented to achieve certification.
When there is a disagreement with a finding, it is important to address the issue promptly to avoid delays in the assessment process. The best time to address minor disagreements with the assessment team is during daily checkpoints, where the university should be prepared to provide clear, immediate evidence to support its position. During the assessment, any disputed objective can be revisited by presenting supporting evidence and demonstrating how the practice satisfies the requirement. If the issue cannot be resolved through the C3PAO’s review process, the university has the option to submit a formal appeal to the CMMC Accreditation Body.
Following the completion of a C3PAO assessment, the assessor compiles the results and submits them into the CMMC-related instance of eMASS. Once submitted, the results are transmitted to the Supplier Performance Risk System (SPRS), which serves as the authoritative public reference for the organization’s CMMC status. Most organizations see their status reflected in SPRS within days to a couple of weeks after submission.
The CMMC status is recorded with a “CMMC Status Date,” which serves as the official starting point for certification. If any deficiencies are identified that are eligible for remediation through a Plan of Action and Milestones (POA&M), the university will receive a Conditional Level 2 certification, which initiates a 180-day remediation window. If all requirements are initially met— or once the POA&M is successfully closed within the 180-day period—the organization will be awarded a Final Level 2 certification.
After certification, the university must continue to demonstrate compliance and provide an annual affirmation of continued adherence to maintain its CMMC status. This ensures that controls remain operational, CUI is properly protected, and the institution remains eligible to participate in DoD contracts that require CMMC compliance.