ANSSI Guide d'hygiene informatique (42 mesures, v2.0)
ANSSI Hygiene VIII: Keep the Information System Up to Date (measures 34 and 35)

ANSSI Guide d'hygiene informatique (42 mesures, v2.0) ANSSI-HYG-34: Define an Update Policy for Information System Components

Define a policy for updating the components of the information system and apply it so that corrections are deployed within defined timescales.

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

What else in your programme already covers this

This control maps to 52 controls across 21 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 · 5 controls

  • CIS-12.1 Ensure Network Infrastructure is Up-to-Date
  • CIS-7.1 Establish and Maintain a Vulnerability Management Process
  • CIS-7.2 Establish and Maintain a Remediation Process
  • CIS-7.3 Perform Automated Operating System Patch Management
  • CIS-7.4 Perform Automated Application Patch Management
  • NIST-CSF-ID.RA-01 Vulnerabilities in assets are identified, validated, and recorded
  • NIST-CSF-ID.RA-06 Risk responses are chosen, prioritized, planned, tracked, and communicated
  • 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

UK Cyber Essentials · 4 controls

  • CE-MP.2 Anti-Malware Signatures Updated
  • CE-SU.2 Automatic Updates Enabled Where Possible
  • CE-SU.3 Critical and High Updates within 14 Days
  • CE-SU.5 Firmware Updates
  • ASBv3-GS-5 Define and implement security posture management strategy
  • ASBv3-PV-6 Rapidly and automatically remediate vulnerabilities
  • PV-5 Perform vulnerability assessments

C5 (Germany) · 3 controls

  • C5-DEV-03 Policies for changes to information systems
  • C5-OPS-18 Managing Vulnerabilities, Malfunctions and Errors - Concept
  • C5-OPS-22 Testing and Documentation of known Vulnerabilities

CMMC 2.0 · 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

ACSC Essential Eight · 2 controls

  • E8-PATCHAPP-ML1 Patch Applications (ML1)
  • E8-PATCHOS-ML1 Patch Operating Systems (ML1)
  • ASD37-02 Patch applications (Essential)
  • ASD37-19 Patch operating systems (Essential)

FedRAMP High · 2 controls

  • SI-2 Flaw Remediation
  • SI-2(2) Automated Flaw Remediation Status

FedRAMP Moderate · 2 controls

  • SI-2 Flaw Remediation
  • SI-2(2) Automated Flaw Remediation Status

ISO 27001:2022 · 2 controls

  • 8.32 Change management
  • 8.8 Management of technical vulnerabilities

NIST SP 800-161 Rev 1 · 2 controls

NIST SP 800-171 Rev 3 · 2 controls

NIST SP 800-53 Rev 5 · 2 controls

SOC 2 · 2 controls

  • SOC2-CC7.1 CC7.1 Detecting configuration changes and new vulnerabilities
  • SOC2-CC8.1 CC8.1 Managing changes to procedures, software, data and infrastructure
  • CPS230-P25 Information and Technology Capability and Asset Health

APRA CPS 234 · 1 control

  • CPS234-P17 Active Maintenance of Capability Against Change

ISO 27002:2022 · 1 control

  • 8.8 Management of technical 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 ANSSI Hygiene VIII: Keep the Information System Up to Date (measures 34 and 35)

You are reading one control. How much of ANSSI Guide d'hygiene informatique (42 mesures, v2.0) have you already done?

ANSSI Guide d'hygiene informatique (42 mesures, v2.0) ANSSI-HYG-34 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of ANSSI Guide d'hygiene informatique (42 mesures, v2.0) your existing evidence covers. Hold FedRAMP Moderate and 35 of 42 ANSSI Guide d'hygiene informatique (42 mesures, v2.0) 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 FedRAMP Moderate pair alone.

Query this from an agent

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