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-2: Ensure Proper Configuration and Patch Management

Run a configuration/patch management program built on an accurate baseline and asset inventory, prioritising PC-architecture machines (HMI, database server, engineering workstation roles). Limit connection of external laptops, prefer known-good vendor laptops, and test updates on an isolated system with malware detection before operational deployment. Obtain updates from authenticated vendor sites and validate authenticity via digital signatures or out-of-band hashes.

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

What else in your programme already covers this

This control maps to 3 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 SP 800-53 Rev 5 · 2 controls

  • NIST-CSF-PR.PS-02 Software is maintained, replaced, and removed commensurate with risk

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 3 it maps to, and the evidence behind each claim, over MCP and REST.