Study guide

8.3 Incident Response (IR), System Integrity (SI) & Risk Assessment (RA/CA) Domains

CMMC Certified CMMC Professional CCP

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: Introduction & Exam Logistics

1.1 Exam Structure, Current Logistics & Official Blueprint 1.2 Eligibility, Training, Retakes & Certification Maintenance 1.3 Study Strategy, Blueprint Mapping & Authoritative Sources

2 Chapter 2: The CMMC Ecosystem & Stakeholder Roles

2.1 Governance & Oversight: DoD, DIBCAC, Cyber AB & ISACA 2.2 Industry Roles: C3PAOs, OSCs, Consultants, ATPs & APPs 2.3 Assessor Roles: CCP, CCA, Lead CCA, QA & Certifying Official

3 Chapter 3: Code of Professional Conduct & Ethics

3.1 Applying the CMMC Code of Professional Conduct 3.2 Conflicts of Interest, Independence & Consulting vs Assessment Boundaries 3.3 Confidentiality, Incident Escalation & Misconduct Reporting

4 Chapter 4: Legal Authorities, Federal Rules & Standards

4.1 FCI vs CUI: Statutory Foundations, E.O. 13556 & 32 CFR Part 2002 4.2 FAR, DFARS & 32 CFR Part 170 4.3 NIST Standards Hierarchy: SP 800-171, SP 800-171A & SP 800-172

5 Chapter 5: CMMC Model Architecture & Maturity Levels

5.1 CMMC Three-Level Architecture, Assessment Types & Affirmation 5.2 Level 1: 15 FAR Safeguarding Requirements & Annual Self-Assessment 5.3 Level 2 & Level 3: CUI Protection and Assessment Authority

6 Chapter 6: CMMC Domains: Access Control, Identity & Boundary Defense

6.1 Access Control (AC) Domain: 22 Practices & Core Implementation 6.2 Identification & Authentication (IA) Domain: MFA & Credential Management 6.3 System & Communications Protection (SC) Domain: Boundary Defense & Cryptography

7 Chapter 7: CMMC Domains: Audit, Configuration, Maintenance & Media

7.1 Audit & Accountability (AU) Domain: Logging, Review & Non-Repudiation 7.2 Configuration Management (CM) Domain: Baselines, Changes & Least Functionality 7.3 Maintenance (MA) & Media Protection (MP) Domains: Sanitization & Tool Control

8 Chapter 8: CMMC Domains: People, Physical, Incident Response & Integrity

8.1 Awareness & Training (AT) & Personnel Security (PS) Domains: Screening & Training 8.2 Physical Protection (PE): Level 1 FAR Requirements & Level 2 Mapping 8.3 Incident Response (IR), System Integrity (SI) & Risk Assessment (RA/CA) Domains

9 Chapter 9: CMMC Scoping Methodology & Boundary Definition

9.1 Scoping Fundamentals: Organizational Scope, Level 1 & Level 2 9.2 The 5 Asset Categories: CUI, SPA, CRMA, Specialized & Out-of-Scope 9.3 Boundary Definition, Data Flow Diagrams & Secure Enclave Isolation

10 Chapter 10: Cloud Service Providers, ESPs & Supply Chain Flowdown

10.1 Cloud Service Providers (CSPs): FedRAMP Moderate Equivalency & DFARS 7012 10.2 External Service Providers (ESPs/MSPs/MSSPs) & Shared Responsibility Matrices 10.3 Subcontractor Flow-Down, Supply Chain Governance & SPRS Scoring

11 Chapter 11: CMMC Assessment Process (CAP): Planning & Evidence Gathering

11.1 CAP Preliminary Proceedings & Phase 1 Pre-Assessment 11.2 CAP Phase 2: Assess Conformity to Security Requirements 11.3 Assessment Objectives, Evidence Sufficiency & Limited Correction

12 Chapter 12: CMMC Assessment Process (CAP): Reporting, POA&M & Closeout

12.1 CAP Phase 3: Complete and Report Assessment Results 12.2 Level 2 POA&M Rules, Exclusions & 180-Day Closeout 12.3 CAP Phase 4: Certificate Issuance & POA&M Closeout

8.3 Incident Response (IR), System Integrity (SI) & Risk Assessment (RA/CA) Domains

Key Takeaways Explain This Topic AI

Incident Response has three Level 2 requirements for operational handling, tracking/reporting, and periodic testing; DFARS 252.204-7012 is the separate source for covered 72-hour DoD reporting and 90-day preservation.

System and Information Integrity has seven Level 2 requirements; four—3.14.1, 3.14.2, 3.14.4, and 3.14.5—also map to Level 1.

Risk Assessment covers periodic risk assessment, vulnerability scanning, and risk-based remediation; Security Assessment covers requirement assessment, operational plans of action, monitoring, and the SSP.

The operational plan of action used for temporary deficiencies under CA.L2-3.12.2 is not the same as an assessment POA&M supporting Conditional status under §170.21.

CMMC does not prescribe one SIEM, scanner, exercise type, patch deadline, or universal evidence artifact; the organization-defined periodic interval cannot exceed one year under §170.14(d).

Last updated: August 2026

Incident Response, System Integrity, Risk & Security Assessment

IR, SI, RA, and CA form a cycle: prepare for incidents, detect flaws and attacks, assess risk and implementation, correct problems, monitor performance, and maintain the SSP. Their CMMC objectives are separate from contract incident reporting and from the limited assessment POA&M process.

Incident Response

The IR family has three Level 2 requirements:

3.6.1 establishes an operational incident-handling capability including preparation, detection, analysis, containment, recovery, and user response.

3.6.2 tracks, documents, and reports incidents to designated officials and/or authorities inside and outside the organization.

3.6.3 tests the organizational incident-response capability.

The organization selects test methods appropriate to its environment, such as a tabletop, simulation, or functional exercise. Under 32 CFR §170.14(d), an organization-defined value described as “periodically” may be no longer than one year. The rule does not mandate one exercise scenario, participant list, or after-action template.

Separate DFARS duties

When DFARS 252.204-7012 applies and the contractor discovers a cyber incident affecting a covered contractor information system or the covered defense information residing in it, or affecting required operationally critical support, the contractor reviews the compromise and rapidly reports within 72 hours through DIBNet. The clause requires the contractor or subcontractor to have a DoD-approved medium-assurance certificate for reporting.

The contractor preserves and protects images of all known affected information systems identified through the required review, plus relevant monitoring and packet-capture data, for at least 90 days after submission of the incident report . The text does not say to create a new complete forensic disk image of every enterprise device. When malicious software is discovered and isolated in connection with a reported incident, it is submitted according to DC3 or contracting-officer instructions; it is not sent to the contracting officer.

The IR CMMC objectives and DFARS report support one another, but a CMMC assessment team does not submit the OSC’s incident report or administer containment. A reported incident alone is not automatic proof that every CMMC requirement is NOT MET.

System and Information Integrity

The SI family has seven Level 2 requirements. Four also map to Level 1: 3.14.1, 3.14.2, 3.14.4, and 3.14.5 .

Requirement Result

3.14.1 Identify, report, and correct system flaws in a timely manner.

3.14.2 Provide malicious-code protection at appropriate locations.

3.14.3 Monitor security alerts and advisories and take action in response.

3.14.4 Update malicious-code protection mechanisms when new releases are available.

3.14.5 Perform periodic scans and real-time scans of files from external sources as they are downloaded, opened, or executed.

3.14.6 Monitor systems, including inbound and outbound traffic, to detect attacks and indicators of potential attacks.

3.14.7 Identify unauthorized use of organizational systems.

“Timely” remediation is risk-based and organization-defined. CMMC does not publish universal 14-, 30-, or 60-day patch deadlines. A SIEM, EDR, IDS, antivirus product, or managed service may implement objectives, but none is universally mandated. The team evaluates coverage and operation across the actual scope.

Risk Assessment

The RA family contains three requirements. 3.11.1 periodically assesses risk to operations, assets, and individuals from operating systems and processing, storing, or transmitting CUI. 3.11.2 scans organizational systems and hosted applications periodically and when new vulnerabilities affecting them are identified and reported. 3.11.3 remediates vulnerabilities according to risk assessments.

Credentialed scanning often provides useful host visibility, but the requirement does not prescribe one scanner or say every asset always uses the same scan method. Specialized assets, applications, cloud responsibilities, network devices, and provider services may need different evidence. Scan coverage, authentication success, exclusions, false-positive handling, prioritization, and verified remediation matter more than a dashboard total.

Security Assessment and the two plan concepts

The CA family contains four requirements:

3.12.1 periodically assesses security requirements to determine whether they are effective in their application.

3.12.2 develops and implements plans of action designed to correct deficiencies and reduce or eliminate vulnerabilities.

3.12.3 monitors security requirements on an ongoing basis for continued effectiveness.

3.12.4 develops, documents, and periodically updates the SSP, including system boundaries, operating environment, implementation of requirements, and relationships or connections to other systems.

32 CFR part 170 clarifies that the operational plan of action associated with CA.L2-3.12.2 addresses temporary vulnerabilities and deficiencies as threats and systems change. The OSA chooses its format, and the definition does not impose the assessment POA&M’s 180-day remediation timeline.

An assessment POA&M under §170.21 is different. It exists only after an assessment supports Conditional status, is restricted by the score ratio, point rule, narrow SC.L2-3.13.11 exception, and named exclusions, and must close within 180 days. Level 1 permits no assessment POA&M. Do not reject an operational plan merely because it contains an item that could not appear on an assessment POA&M; first identify which plan the scenario describes.

Evidence sequence

Trace incident roles, records, testing, and any applicable DFARS reporting path.

Sample flaw, malware, alert, scan, attack-monitoring, and unauthorized-use evidence across the scope.

Compare vulnerability findings with risk decisions and completed remediation.

Review periodic assessment and ongoing monitoring results.

Reconcile the SSP with the inventory, network diagram, providers, and current implementation.

Classify each plan correctly as operational or assessment-related before applying deadlines or exclusions.

This evidence chain prevents attractive but wrong shortcuts: every incident is not a CMMC failure, every vulnerability is not due in 30 days, and every item called a POA&M is not governed by the Conditional-status rules.