CISA Industrial Control Systems (ICS) Security Guidance
CISA ICS: Seven Steps to Effectively Defend ICS

CISA Industrial Control Systems (ICS) Security Guidance CISA-ICS-7S-7: Monitor and Respond

Actively monitor for adversarial penetration in five key places (IP traffic on ICS boundaries; IP traffic within the control network; host-based detection; login analysis for stolen-credential use; account/user-administration actions) and maintain a prepared response plan (disconnect, scoped malware search, disable affected accounts, isolate systems, full password reset, escalation) and a restoration plan including gold disks to restore systems to known-good states.

Maintained by Gerard BlokdykVerified against the published standard Control text last updated

What else in your programme already covers this

This control maps to 4 controls across 2 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.

NIST Cybersecurity Framework 2.0 · 2 controls

  • NIST-CSF-DE.CM-01 Networks and network services are monitored to find potentially adverse events
  • NIST-CSF-RS.MA-01 The incident response plan is executed in coordination with relevant third parties once an incident is declared

NIST SP 800-53 Rev 5 · 2 controls

Every mapping shown was judged rather than inferred from wording similarity, and the ones that failed review are published too. See the coverage reports and what was rejected.

Other controls in CISA ICS: Seven Steps to Effectively Defend ICS

Query this from an agent

The graph holds this control, the 4 it maps to, and the evidence behind each claim, over MCP and REST.

MCP endpointAll CISA Industrial Control Systems (ICS) Security Guidance controls