IR.L2-3.6.2 · NIST SP 800-171 3.6.2

Incident Reporting

Track, document, and report incidents to designated officials and/or authorities both internal and external to the organization.

5 points if not metMust be fully met, cannot POA&M6 assessment objectives

What an assessor scores, the objectives

IR.L2-3.6.2 is met only when every one of these 6 objectives, from NIST SP 800-171A, is satisfied. A single missed objective makes the whole requirement not met.

  • 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.identified authorities are notified of incidents
  • f.identified organizational officials are notified of incidents

How a C3PAO checks it

NIST SP 800-171A defines three assessment methods. For IR.L2-3.6.2, an assessor uses these:

Examine

Incident response policy; procedures addressing incident monitoring; incident response records and documentation; procedures addressing incident reportin g; incident reporting records and documentation; incident response plan; system security plan; other relevant documents or records

Interview

Personnel with incident monitoring responsibilities; personnel with incident reporting responsibilities; personnel who have or should have reported incidents; personnel (authorities) to whom incident information is to be reported; personnel with information security responsibilities

Test

Incident monitoring capability for the organization; mechanisms supporting or implementing tracking and documenting of system security incidents; organizational processes for incident reporting; mechanisms supporting or implementing incident reporting

What it means, in context

Tracking and documenting system security incidents includes maintaining records about each incident, the status of the incident, and other pertinent information necessary for forensics, evaluating incident details, trends, and handling . Incident informatio n can be obtained from a variety of sources including incident reports, incident response teams, audit monitoring, network monitoring, physical access monitoring, and user/administrator reports. Reporting incidents addresses specific incident reporting requirements within an organization and the formal incident reporting requirements for the organization. Suspected security incidents may also be reported and include the receipt of suspicious email communications that can potentially contain malicious code. The types of security incidents reported, the content and timeliness of the reports, and the designated reporting authorities reflect applicable laws, Executive Orders, directives, regulations, and policies. NIST SP 800-61 provides guidance on incident handling.

Incident handling is the actions the organization takes to prevent or contain the impact of an incident to the organization while it is occurring or shortly after it has occurred. The majority of the process consists of incident i dentification, containment, eradication, and recovery. During this process, it is essential to track the work processes required in order to effectively respond. Designate a central hub to serve as the point to coordinate, communicate, and track activities. The hub should receive and document information from system administrators, incident handlers, and others involved throughout the process . As the incident process moves toward eradication, executives, affected business units , and any required external stakeholders should be kept aware of the incident in order to make decisions affecting the business. Report to designated authorities, taking into account applicable laws, directives, regulations, and other guidance. Specify staff responsible for communicating about the incident to internal and external stakeholders. Example You notice unusual activity on a server and determine a potential security incident has occurred. You open a tracking ticket with the Security Operations Center (SOC) , which assigns an incident handler to work the ticket [a]. The handler investigates and documents initial findings, which lead to a determination that unauthorized access occurred on the server [b]. The SOC establishes an incident management team consis ting of se curity, database, network, and system administrators. The team meets daily to update progress and plan courses of action to contain the incident [a]. At the end of the day , the team provides a status report to IT executives [d,f]. Two days later, the team declares the incident contained. The team produces a final report as the database system is rebuilt and placed back into operation. Potential Assessment Considerations • Is there an incident response policy that directs the establishment of requirements for tracking and reporting of incidents involving CUI to appropriate officials [a,d]? • Is cybersecurity incident information promptly reported to management [e,f]?

What passing evidence looks like

The incident tracking log, the documented reporting chain (internal roles, the prime, and DoD at dibnet.dod.mil within 72 hours per DFARS 252.204-7012), and one tracked entry showing report fields.

Common ways contractors fail IR.L2-3.6.2

  • !The 72 hour DoD reporting clock from DFARS 7012 is the detail assessors probe. Your plan must name dibnet.dod.mil, the 72 hours, and who owns the submission, and note that a Medium Assurance Certificate is needed ahead of time to file.

The step by step walkthrough for Microsoft 365 GCC High, Google Workspace, and on premises setups, plus the exact evidence to capture, lives inside the Level 2 Accelerator.

Prove IR.L2-3.6.2, and the other 109

The Level 2 Accelerator walks all 110 requirements with you, generates your SSP, POA&M, and Audit Room from real evidence, includes the full Level 1 platform, and puts a credentialed officer alongside you for 180 days. Filed in 180 days, or we work free until you are.

No credit card. Phase 2 begins Nov 10, 2026, when applicable DoD solicitations start requiring a current Level 2 status to win the award.

IR.L2-3.6.2 questions, answered

How many points is CMMC requirement IR.L2-3.6.2 worth?+

IR.L2-3.6.2 is worth 5 points in the CMMC Level 2 score under 32 CFR 170.24. If it is not met, you lose 5 from your total of 110.

Can IR.L2-3.6.2 be placed on a POA&M?+

No. IR.L2-3.6.2 must be fully met before you can file. It cannot be deferred to a POA&M, so it is a gate on your assessment.

What family does IR.L2-3.6.2 belong to?+

IR.L2-3.6.2 is in the Incident Response (IR) family, one of the 14 families of NIST SP 800-171 that make up CMMC Level 2.

Key references
  • NIST SP 800-171 Rev. 2 3.6.2