3.6.2Track and report incidents in Rev. 3
Reworded: 03.06.02 Incident Monitoring, Reporting, and Response Assistance. Gains organization-defined parameters.
Status as of 2026-09-08
Rev. 2 is what a contract requires today. DFARS 252.204-7012 and the CMMC rule at 32 CFR 170 point at NIST SP 800-171 Rev. 2, and a standing DoD class deviation keeps it there. NIST has published Rev. 3, but publishing a revision does not change an obligation. A move to Rev. 3 would arrive through the Department's reform process and formal rulemaking, a change to that deviation or an amendment to the rule, not through publication. The Department has published its organization-defined parameter values for Rev. 3 in preparation; that is groundwork, not adoption.
Side by side
Rev. 2 · in force 3.6.2 Incident Reporting
Assessment objectives · 800-171A
- [a] incidents are tracked
- [b] incidents are documented
- [c] authorities to whom incidents are to be reported are identified
- [d] organizational officials to whom incidents are to be reported are identified
- [e] incidents are reported to identified authorities
- [f] incidents are reported to identified organizational officials
Rev. 3 · not adopted 03.06.02 Incident Monitoring, Reporting, and Response Assistance
a. Track and document system security incidents.
b. Report suspected incidents to the organizational incident response capability within [Assignment: organization-defined time period].
c. Report incident information to [Assignment: organization-defined authorities].
d. Provide an incident response support resource that offers advice and assistance to system users on handling and reporting incidents.
Determination statements · 800-171A Rev. 3
- 03.06.02.a[01] system security incidents are tracked.
- 03.06.02.a[02] system security incidents are documented.
- 03.06.02.b suspected incidents are reported to the organizational incident response capability within <A.03.06.02.ODP[01]: time period>.
- 03.06.02.c incident information is reported to <A.03.06.02.ODP[02]: authorities>.
- 03.06.02.d an incident response support resource that offers advice and assistance to system users on handling and reporting incidents is provided.
Organization-defined parameters
- A.03.06.02.ODP[01] the time period to report suspected incidents to the organizational incident response capability is defined.
- A.03.06.02.ODP[02] authorities to whom incident information is to be reported are defined.
Draws on Rev. 2 3.6.2.
Left: NIST SP 800-171 Rev. 2 and 800-171A, verbatim. Right: NIST SP 800-171 Rev. 3 and 800-171A Rev. 3, verbatim, with organization-defined blanks highlighted.
Word by word
The Rev. 2 requirement compared with its Rev. 3 successor. A mechanical comparison of the two verbatim texts, not an interpretation.
removed in Rev. 3 added in Rev. 3
Rev. 2 3.6.2 → Rev. 3 03.06.02 Incident Monitoring, Reporting, and Response Assistance
8 words kept, 9 removed, 38 added. Rev. 3 statement labels omitted for the comparison.
What NIST says changed
- New security requirement title
- Aligned with SP 800-53, Rev 5 to provide more comprehensive detail on and foundational tasks for incident monitoring, reporting and response assistance
- Added new ODP: authorities to report incident information to
- Added requirement item for incident response support resource (part d)
NIST, SP 800-171 Rev. 2 to Rev. 3 change analysis, class “Significant change”. At adoption, Bedrock files this under “Rework”.
NIST's Rev. 3 discussion for 03.06.02
Documenting incidents includes maintaining records about each incident, the status of the incident, and other pertinent information necessary for forensics as well as evaluating incident details, trends, and handling. Incident information can be obtained from many sources, including network monitoring, incident reports, incident response teams, user complaints, supply chain partners, audit monitoring, physical access monitoring, and user and administrator reports. <a href="#/cprt/framework/version/SP_800_171_3_0_0/home?element=03.06.01">03.06.01</a> provides information on the types of incidents that are appropriate for monitoring. The types of incidents reported, the content and timeliness of the reports, and the reporting authorities reflect applicable laws, Executive Orders, directives, regulations, policies, standards, and guidelines. Incident information informs risk assessments, the effectiveness of security assessments, the security requirements for acquisitions, and the selection criteria for technology products. Incident response support resources provided by organizations include help desks, assistance groups, automated ticketing systems to open and track incident response tickets, and access to forensic services or consumer redress services, when required.
What this means for you now
Nothing changes in what you are assessed against until a class deviation or a published rule adopts Rev. 3. Keep meeting 3.6.2 as written in Rev. 2, and if you already choose a value for the parameters above in practice, write it down where your system security plan can find it.
Bedrock CMMC shows this same comparison against your own package, with your current status on the Rev. 2 side, so the day adoption lands the migration is a review, not a rewrite.
Where this page's facts come from
- Rev. 2 text and objectives
- bedrock-cmmc-api@89b8e8e:migrations/004_reference_requirements.sql#Requirement.basicRequirement@rev2; bedrock-cmmc-api@89b8e8e:migrations/005_reference_objectives.sql#AssessmentObjective.description@rev2
- Mapping and change class
- bedrock-cmmc-api@89b8e8e:docs/reference/nist-800-171-rev3/normalized/r2_r3_transition_map.json#r2_to_r3
- Rev. 3 03.06.02
- bedrock-cmmc-api@89b8e8e:docs/reference/nist-800-171-rev3/normalized/rev3.json#requirements[]