The Defense Compliance ReportCMMC 2.0 & the Defense Industrial Base
DRAFT PREVIEW — NOT PUBLISHED — PUBLICATION DATE PENDING

Free editorial worksheets · September 25, 2026

ESP Evidence Pack: CRM Starters & Scoping Worksheet

Three Customer Responsibility Matrix (CRM) starters, a service description outline, a scoping worksheet, and prospect-response scripts. Everything is available on this page without an email gate. Print the worksheets or download each CRM starter as a CSV.

Editorial worksheets, not official Cyber AB or DoD forms or a compliance determination. Do not submit CUI or client details to receive them. Fill these out offline; validate service-specific scope and responsibilities with your client. These domain-level rows are starting points, not a requirement-by-requirement assessment.

For the underlying three-gate analysis, read CMMC for Cybersecurity Companies.

CRM starter: Non-CSP ESP handling CUI

Use one copy per service and client boundary. Fill in and validate each applicable requirement with the client; a domain row is not a completed CRM.

Service name:  
Path: Non-CSP ESP handling CUI
Rule basis: 32 CFR 170.19(c)(2)(i)–(ii), Table 4; 32 CFR 170.4
Version/date:  
DomainProvider responsibilityClient (OSA) responsibilityShared — how splitEvidence the assessor may requestNotes
Access ControlWhich service activities, if any?
 
Which client activities, if any?
 
Where does each party's work begin and end?
 
Which artifacts, interviews, or tests may be relevant?
 
Which requirements and service boundaries need review?
 
Awareness and TrainingWhich service activities, if any?
 
Which client activities, if any?
 
Where does each party's work begin and end?
 
Which artifacts, interviews, or tests may be relevant?
 
Which requirements and service boundaries need review?
 
Audit and AccountabilityWhich service activities, if any?
 
Which client activities, if any?
 
Where does each party's work begin and end?
 
Which artifacts, interviews, or tests may be relevant?
 
Which requirements and service boundaries need review?
 
Configuration ManagementWhich service activities, if any?
 
Which client activities, if any?
 
Where does each party's work begin and end?
 
Which artifacts, interviews, or tests may be relevant?
 
Which requirements and service boundaries need review?
 
Identification and AuthenticationWhich service activities, if any?
 
Which client activities, if any?
 
Where does each party's work begin and end?
 
Which artifacts, interviews, or tests may be relevant?
 
Which requirements and service boundaries need review?
 
Incident ResponseWhich service activities, if any?
 
Which client activities, if any?
 
Where does each party's work begin and end?
 
Which artifacts, interviews, or tests may be relevant?
 
Which requirements and service boundaries need review?
 
MaintenanceWhich service activities, if any?
 
Which client activities, if any?
 
Where does each party's work begin and end?
 
Which artifacts, interviews, or tests may be relevant?
 
Which requirements and service boundaries need review?
 
Media ProtectionWhich service activities, if any?
 
Which client activities, if any?
 
Where does each party's work begin and end?
 
Which artifacts, interviews, or tests may be relevant?
 
Which requirements and service boundaries need review?
 
Personnel SecurityWhich service activities, if any?
 
Which client activities, if any?
 
Where does each party's work begin and end?
 
Which artifacts, interviews, or tests may be relevant?
 
Which requirements and service boundaries need review?
 
Physical ProtectionWhich service activities, if any?
 
Which client activities, if any?
 
Where does each party's work begin and end?
 
Which artifacts, interviews, or tests may be relevant?
 
Which requirements and service boundaries need review?
 
Risk AssessmentWhich service activities, if any?
 
Which client activities, if any?
 
Where does each party's work begin and end?
 
Which artifacts, interviews, or tests may be relevant?
 
Which requirements and service boundaries need review?
 
Security AssessmentWhich service activities, if any?
 
Which client activities, if any?
 
Where does each party's work begin and end?
 
Which artifacts, interviews, or tests may be relevant?
 
Which requirements and service boundaries need review?
 
System and Communications ProtectionWhich service activities, if any?
 
Which client activities, if any?
 
Where does each party's work begin and end?
 
Which artifacts, interviews, or tests may be relevant?
 
Which requirements and service boundaries need review?
 
System and Information IntegrityWhich service activities, if any?
 
Which client activities, if any?
 
Where does each party's work begin and end?
 
Which artifacts, interviews, or tests may be relevant?
 
Which requirements and service boundaries need review?
 

CRM starter: SPD-only service assessed as Security Protection Assets

Use one copy per service and client boundary. Fill in and validate each applicable requirement with the client; a domain row is not a completed CRM.

Service name:  
Path: SPD-only service assessed as Security Protection Assets
Rule basis: 32 CFR 170.19(c)(2)(i), Table 4; 32 CFR 170.4
Version/date:  
DomainProvider responsibilityClient (OSA) responsibilityShared — how splitEvidence the assessor may requestNotes
Access ControlWhich service activities, if any?
 
Which client activities, if any?
 
Where does each party's work begin and end?
 
Which artifacts, interviews, or tests may be relevant?
 
Which requirements and service boundaries need review?
 
Awareness and TrainingWhich service activities, if any?
 
Which client activities, if any?
 
Where does each party's work begin and end?
 
Which artifacts, interviews, or tests may be relevant?
 
Which requirements and service boundaries need review?
 
Audit and AccountabilityWhich service activities, if any?
 
Which client activities, if any?
 
Where does each party's work begin and end?
 
Which artifacts, interviews, or tests may be relevant?
 
Which requirements and service boundaries need review?
 
Configuration ManagementWhich service activities, if any?
 
Which client activities, if any?
 
Where does each party's work begin and end?
 
Which artifacts, interviews, or tests may be relevant?
 
Which requirements and service boundaries need review?
 
Identification and AuthenticationWhich service activities, if any?
 
Which client activities, if any?
 
Where does each party's work begin and end?
 
Which artifacts, interviews, or tests may be relevant?
 
Which requirements and service boundaries need review?
 
Incident ResponseWhich service activities, if any?
 
Which client activities, if any?
 
Where does each party's work begin and end?
 
Which artifacts, interviews, or tests may be relevant?
 
Which requirements and service boundaries need review?
 
MaintenanceWhich service activities, if any?
 
Which client activities, if any?
 
Where does each party's work begin and end?
 
Which artifacts, interviews, or tests may be relevant?
 
Which requirements and service boundaries need review?
 
Media ProtectionWhich service activities, if any?
 
Which client activities, if any?
 
Where does each party's work begin and end?
 
Which artifacts, interviews, or tests may be relevant?
 
Which requirements and service boundaries need review?
 
Personnel SecurityWhich service activities, if any?
 
Which client activities, if any?
 
Where does each party's work begin and end?
 
Which artifacts, interviews, or tests may be relevant?
 
Which requirements and service boundaries need review?
 
Physical ProtectionWhich service activities, if any?
 
Which client activities, if any?
 
Where does each party's work begin and end?
 
Which artifacts, interviews, or tests may be relevant?
 
Which requirements and service boundaries need review?
 
Risk AssessmentWhich service activities, if any?
 
Which client activities, if any?
 
Where does each party's work begin and end?
 
Which artifacts, interviews, or tests may be relevant?
 
Which requirements and service boundaries need review?
 
Security AssessmentWhich service activities, if any?
 
Which client activities, if any?
 
Where does each party's work begin and end?
 
Which artifacts, interviews, or tests may be relevant?
 
Which requirements and service boundaries need review?
 
System and Communications ProtectionWhich service activities, if any?
 
Which client activities, if any?
 
Where does each party's work begin and end?
 
Which artifacts, interviews, or tests may be relevant?
 
Which requirements and service boundaries need review?
 
System and Information IntegrityWhich service activities, if any?
 
Which client activities, if any?
 
Where does each party's work begin and end?
 
Which artifacts, interviews, or tests may be relevant?
 
Which requirements and service boundaries need review?
 

CRM starter: CSP holding CUI

Use one copy per service and client boundary. Fill in and validate each applicable requirement with the client; a domain row is not a completed CRM.

Service name:  
Path: CSP holding CUI
Rule basis: DFARS 252.204-7012; 32 CFR 170.19(c)(2)(i), Table 4; DoD CIO February 2025 Technical Application guidance
Version/date:  
DomainProvider responsibilityClient (OSA) responsibilityShared — how splitEvidence the assessor may requestNotes
Access ControlWhich service activities, if any?
 
Which client activities, if any?
 
Where does each party's work begin and end?
 
Which artifacts, interviews, or tests may be relevant?
 
Which requirements and service boundaries need review?
 
Awareness and TrainingWhich service activities, if any?
 
Which client activities, if any?
 
Where does each party's work begin and end?
 
Which artifacts, interviews, or tests may be relevant?
 
Which requirements and service boundaries need review?
 
Audit and AccountabilityWhich service activities, if any?
 
Which client activities, if any?
 
Where does each party's work begin and end?
 
Which artifacts, interviews, or tests may be relevant?
 
Which requirements and service boundaries need review?
 
Configuration ManagementWhich service activities, if any?
 
Which client activities, if any?
 
Where does each party's work begin and end?
 
Which artifacts, interviews, or tests may be relevant?
 
Which requirements and service boundaries need review?
 
Identification and AuthenticationWhich service activities, if any?
 
Which client activities, if any?
 
Where does each party's work begin and end?
 
Which artifacts, interviews, or tests may be relevant?
 
Which requirements and service boundaries need review?
 
Incident ResponseWhich service activities, if any?
 
Which client activities, if any?
 
Where does each party's work begin and end?
 
Which artifacts, interviews, or tests may be relevant?
 
Which requirements and service boundaries need review?
 
MaintenanceWhich service activities, if any?
 
Which client activities, if any?
 
Where does each party's work begin and end?
 
Which artifacts, interviews, or tests may be relevant?
 
Which requirements and service boundaries need review?
 
Media ProtectionWhich service activities, if any?
 
Which client activities, if any?
 
Where does each party's work begin and end?
 
Which artifacts, interviews, or tests may be relevant?
 
Which requirements and service boundaries need review?
 
Personnel SecurityWhich service activities, if any?
 
Which client activities, if any?
 
Where does each party's work begin and end?
 
Which artifacts, interviews, or tests may be relevant?
 
Which requirements and service boundaries need review?
 
Physical ProtectionWhich service activities, if any?
 
Which client activities, if any?
 
Where does each party's work begin and end?
 
Which artifacts, interviews, or tests may be relevant?
 
Which requirements and service boundaries need review?
 
Risk AssessmentWhich service activities, if any?
 
Which client activities, if any?
 
Where does each party's work begin and end?
 
Which artifacts, interviews, or tests may be relevant?
 
Which requirements and service boundaries need review?
 
Security AssessmentWhich service activities, if any?
 
Which client activities, if any?
 
Where does each party's work begin and end?
 
Which artifacts, interviews, or tests may be relevant?
 
Which requirements and service boundaries need review?
 
System and Communications ProtectionWhich service activities, if any?
 
Which client activities, if any?
 
Where does each party's work begin and end?
 
Which artifacts, interviews, or tests may be relevant?
 
Which requirements and service boundaries need review?
 
System and Information IntegrityWhich service activities, if any?
 
Which client activities, if any?
 
Where does each party's work begin and end?
 
Which artifacts, interviews, or tests may be relevant?
 
Which requirements and service boundaries need review?
 

Service description outline

Create one description per service line and client boundary. Record the actual delivery arrangement, not marketing copy.

  1. Service name, version/date, client identifier, and service owner
  2. What the service delivers, where it operates, and the client functions it supports
  3. People, systems, facilities, and third-party services that deliver the service
  4. Data touched: CUI, SPD (including logs, configurations, and credentials), or neither; where it flows and is retained
  5. Tenant licensing and ownership, provider-managed components, and client/provider boundary
  6. Access paths, admin credentials, isolation, and relevant shared infrastructure
  7. What the provider performs, what the client performs, and how shared actions are validated in the CRM
  8. Evidence contacts, artifacts, interview availability, and review/update date

Scoping worksheet — repeat per service line

Run all gates; more than one path may apply. Use the completed answers to confirm which starter needs tailoring.

  1. Service line and client (use an internal identifier, not CUI on this page)
  2. Executed contract, purchase order, task order, amendment, and applicable clauses (Gate 1)
  3. Which CUI or Security Protection Data touches provider people, systems, or facilities? How is it processed, stored, or transmitted?
  4. Which assets hold logs, configuration or vulnerability data, alerts, or admin credentials?
  5. Who owns or licenses the cloud tenant: client or provider? Is a cloud service modified or subdivided for client use?
  6. Which provider-owned laptops, VPNs, password vaults, ticketing systems, servers, or shared infrastructure touch this service?
  7. Which people, systems, and facilities are in the proposed boundary? What isolation exists between client environments?
  8. Who owns each action, who can supply evidence, and who validates the boundary with the client?

Prospect-response scripts

Choose only the answer that is true for your actual scope. Replace brackets with verified facts; do not claim an assessment or status you do not hold.

“Are you CMMC certified?”
“Our CMMC Status is Final Level 2 (C3PAO) for [named scope], assessed [date] by [C3PAO name]. Our service description and Customer Responsibility Matrix for [service] are attached.” Use only if true and supported by your records.
“Do you have a self-assessment status?”
“Our CMMC Status is Final Level 2 (Self) for [named scope], self-assessed [date], with the required affirmation submitted [date].” Use only if true.
“What if you have no CMMC Status for this service?”
“We don’t hold a CMMC Status for this service. Based on our current service architecture, 32 CFR 170.19 places this service inside your assessment scope rather than requiring a separate provider status. We provide a service description and Customer Responsibility Matrix for review, and our people are available for assessment interviews.” Confirm this classification against the actual service and contract before using it.
“Can you guarantee our assessment outcome?”
“No. We can identify the service boundary, document our assigned responsibilities, and provide available evidence for your assessment team to examine.”

Rule context and citations: CMMC for Cybersecurity Companies.