IR-6: INCIDENT REPORTINGE
TAILORED FOR INDUSTRIAL CONTROL SYSTEMS
ICS Control Baselines:
- Low
- Moderate
- High
The organization:
- a. Requires personnel to report suspected security incidents to the organizational incident response capability within [Assignment: organization-defined time period]; and
- b. Reports security incident information to [Assignment: organization-defined authorities].
SUPPLEMENTAL GUIDANCE
The intent of this control is to address both specific incident reporting requirements within an organization and the formal incident reporting requirements for federal agencies and their subordinate organizations. Suspected security incidents include, for example, 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 federal laws, Executive Orders, directives, regulations, policies, standards, and guidance. Current federal policy requires that all federal agencies (unless specifically exempted from such requirements) report security incidents to the United States Computer Emergency Readiness Team (US-CERT) within specified time frames designated in the US-CERT Concept of Operations for Federal Cyber Security Incident Handling.
ICS SUPPLEMENTAL GUIDANCE
The organization should report incidents on a timely basis. The DHS National Cybersecurity & Communications Integration Center (NCCIC), http://www.dhs.gov/about-national-cybersecurity- communications-integration-center, serves as a centralized location where operational elements involved in cybersecurity and communications reliance are coordinated and integrated. The Industrial Control Systems Cyber Emergency Response Team (ICS-CERT) http://ics-cert.us-cert.gov/ics-cert/, collaborates with international and private sector Computer Emergency Response Teams (CERTs) to share control systems-related security incidents and mitigation measures.
RELATED CONTROLS: IR-6
CONTROL ENHANCEMENTS
IR-6 (1) INCIDENT REPORTING | AUTOMATED REPORTING
ICS Control Baselines:
- Moderate
- High
The organization employs automated mechanisms to assist in the reporting of security incidents.
Supplemental Guidance: NONE
ICS Supplemental Guidance:
The automated mechanisms used to support the incident reporting process are not necessarily part of, or connected to, the ICS.
RELATED CONTROLS: IR-6 (1)
IR-6 (2) INCIDENT REPORTING | VULNERABILITIES RELATED TO INCIDENTS
NOT SELECTED FOR THE NIST ISC CONTROL SET
The organization reports information system vulnerabilities associated with reported security incidents to [Assignment: organization-defined personnel or roles].
Supplemental Guidance: NONE
IR-6 (3) INCIDENT REPORTING | COORDINATION WITH SUPPLY CHAIN
NOT SELECTED FOR THE NIST ISC CONTROL SET
The organization provides security incident information to other organizations involved in the supply chain for information systems or information system components related to the incident.
Supplemental Guidance:
Organizations involved in supply chain activities include, for example, system/product developers, integrators, manufacturers, packagers, assemblers, distributors, vendors, and resellers. Supply chain incidents include, for example, compromises/breaches involving information system components, information technology products, development processes or personnel, and distribution processes or warehousing facilities. Organizations determine the appropriate information to share considering the value gained from support by external organizations with the potential for harm due to sensitive information being released to outside organizations of perhaps questionable trustworthiness.
REFERENCES:
- NIST Special Publication 800-82
- NIST Special Publication 800-61
- http://www.us-cert.gov