ASD Strategies to Mitigate Cyber Security Incidents
Limiting the Extent of Cyber Security Incidents

ASD Strategies to Mitigate Cyber Security Incidents ASD37-19: Patch operating systems (Essential)

Patch/mitigate computers (including network devices) with extreme risk vulnerabilities within 48 hours. Use the latest version of operating systems. Don't use unsupported versions.

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

What else in your programme already covers this

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

CIS Controls v8 · 4 controls

  • CIS-12.1 Ensure Network Infrastructure is Up-to-Date
  • CIS-2.2 Ensure Authorized Software is Currently Supported
  • CIS-7.3 Perform Automated Operating System Patch Management
  • CIS-7.7 Remediate Detected Vulnerabilities

UK Cyber Essentials · 4 controls

  • CE-SU.1 Software Licensed and Supported
  • CE-SU.3 Critical and High Updates within 14 Days
  • CE-SU.4 Remove Out-of-Support Software
  • CE-SU.5 Firmware Updates

ACSC Essential Eight · 3 controls

  • E8-PATCHOS-ML1 Patch Operating Systems (ML1)
  • E8-PATCHOS-ML2 Patch Operating Systems (ML2)
  • E8-PATCHOS-ML3 Patch Operating Systems (ML3)
  • AM-3 Ensure security of asset lifecycle management
  • ASBv3-PV-6 Rapidly and automatically remediate vulnerabilities
  • PV-5 Perform vulnerability assessments

CMMC 2.0 · 3 controls

  • NIST-CSF-ID.RA-01 Vulnerabilities in assets are identified, validated, and recorded
  • NIST-CSF-PR.PS-02 Software is maintained, replaced, and removed commensurate with risk
  • NIST-CSF-PR.PS-03 Hardware is maintained, replaced, and removed commensurate with risk

NIST SP 800-161 Rev 1 · 3 controls

PCI DSS 4.0 · 3 controls

  • 12.3.4 12.3.4 Annual review of hardware and software technologies
  • 6.3.1 6.3.1 Vulnerability identification and risk ranking
  • 6.3.3 6.3.3 Timely installation of security patches
  • ANSSI-HYG-34 Define an Update Policy for Information System Components
  • ANSSI-HYG-35 Anticipate the End of Maintenance of Software and Systems

C5 (Germany) · 2 controls

  • C5-OPS-18 Managing Vulnerabilities, Malfunctions and Errors - Concept
  • C5-OPS-22 Testing and Documentation of known Vulnerabilities

FedRAMP High · 2 controls

  • RA-5 Vulnerability Monitoring and Scanning
  • SI-2 Flaw Remediation

FedRAMP Moderate · 2 controls

  • RA-5 Vulnerability Monitoring and Scanning
  • SI-2 Flaw Remediation

NIST SP 800-171 Rev 3 · 2 controls

NIST SP 800-53 Rev 5 · 2 controls

ISO 27001:2022 · 1 control

  • 8.8 Management of technical vulnerabilities

ISO 27002:2022 · 1 control

  • 8.8 Management of technical vulnerabilities

SOC 2 · 1 control

  • SOC2-CC7.1 CC7.1 Detecting configuration changes and new vulnerabilities

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 Limiting the Extent of Cyber Security Incidents

You are reading one control. How much of ASD Strategies to Mitigate Cyber Security Incidents have you already done?

ASD Strategies to Mitigate Cyber Security Incidents ASD37-19 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of ASD Strategies to Mitigate Cyber Security Incidents your existing evidence covers. Hold NIST SP 800-53 Rev 5 and 32 of 37 ASD Strategies to Mitigate Cyber Security Incidents controls already carry evidence.

Each report names every control your existing framework evidences, every one it does not, the reasoning behind each claim, and the claims that were argued against and rejected. 0 were rejected on the NIST SP 800-53 Rev 5 pair alone.

Query this from an agent

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