PCI DSS 4.0
Req 12: Information Security Policies

PCI DSS 4.0 12.3.4: Hardware and software technologies reviewed annually

Hardware and software technologies in use are reviewed at least once every 12 months to confirm vendor support and address end-of-life or unsupported components.

What else in your programme already covers this

This control maps to 49 controls across 26 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-16.5 Use Up-to-Date and Trusted Third-Party Software Components
  • CIS-2.2 Ensure Authorized Software is Currently Supported
  • CIS-9.1 Ensure Use of Only Fully Supported Browsers and Email Clients

ISO 27001:2022 · 4 controls

  • 5.22 Monitoring, review and change management of supplier services
  • 7.13 Equipment maintenance
  • 8.19 Installation of software on operational systems
  • 8.8 Management of technical vulnerabilities

NIST SP 800-53 Rev 5 · 4 controls

NIST Cybersecurity Framework 2.0 · 3 controls

  • NIST-CSF-ID.AM-08 Systems, hardware, software, services, and data are managed throughout their life cycles
  • 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

ACSC Essential Eight · 2 controls

ANSSI Guide d'hygiene informatique (42 mesures, v2.0) · 2 controls

  • ANSSI-HYG-34 Define an Update Policy for Information System Components
  • ANSSI-HYG-35 Anticipate the End of Maintenance of Software and Systems

CMMC 2.0 · 2 controls

Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 · 2 controls

FedRAMP High · 2 controls

  • CM-8 System Component Inventory
  • SA-22 Unsupported System Components. a. Replace system components when support for the components is no longer available from the developer, vendor, or manufacturer; or b. Provide the following options for alternative sources for continued support

FedRAMP Moderate · 2 controls

  • CM-8 System Component Inventory
  • SA-22 Unsupported System Components. a. Replace system components when support for the components is no longer available from the developer, vendor, or manufacturer; or b. Provide the following options for alternative sources for continued support

ISO 27002:2022 · 2 controls

  • 5.9 Inventory of information and other associated assets
  • 8.8 Management of technical vulnerabilities

NIST SP 800-161 Rev 1 · 2 controls

NIST SP 800-53 Rev 5 LOW · 2 controls

  • CM-8 System Component Inventory
  • SA-22 Unsupported System Components. a. Replace system components when support for the components is no longer available from the developer, vendor, or manufacturer; or b. Provide the following options for alternative sources for continued support

NIST SP 800-53 Rev 5 MODERATE · 2 controls

  • CM-8 System Component Inventory
  • SA-22 Unsupported System Components. a. Replace system components when support for the components is no longer available from the developer, vendor, or manufacturer; or b. Provide the following options for alternative sources for continued support

NIST SP 800-53 Revision 5.1 HIGH · 2 controls

  • CM-8 System Component Inventory
  • SA-22 Unsupported System Components. a. Replace system components when support for the components is no longer available from the developer, vendor, or manufacturer; or b. Provide the following options for alternative sources for continued support

UK Cyber Essentials · 2 controls

  • CE-SU.1 Software Licensed and Supported
  • CE-SU.4 Remove Out-of-Support Software

APRA CPS 234 · 1 control

  • CPS234-P17 Active Maintenance of Capability Against Change

ASD Strategies to Mitigate Cyber Security Incidents · 1 control

  • ASD37-19 Patch operating systems (Essential)

AWS Well-Architected Security Pillar · 1 control

  • SEC01-BP08 Evaluate and implement new security services and features regularly

C5 (Germany) · 1 control

ISO 27701:2019 · 1 control

  • 6.9.6 Technical vulnerability management

NIS2 Directive · 1 control

  • Art.21.3 Take account of supplier-specific vulnerabilities and of Union coordinated supply chain risk assessments

NIST SP 800-171 Rev 3 · 1 control

NIST SP 800-172 · 1 control

  • 3.11.5e Assess Effectiveness of Security Solutions

NIST SP 800-218 · 1 control

SOC 2 · 1 control

  • SOC2-CC5.2 COSO principle 11: Selects and develops general controls over technology

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 Req 12: Information Security Policies

You are reading one control. How much of PCI DSS 4.0 have you already done?

PCI DSS 4.0 12.3.4 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of PCI DSS 4.0 your existing evidence covers. Hold ISO 27001:2022 and 139 of 249 PCI DSS 4.0 controls already carry evidence.

If you hold ISO 27001:202255.8% covered · 110 gapsIf you hold FedRAMP Moderate55.4% covered · 111 gapsIf you hold NIST SP 800-53 Rev 553.4% covered · 116 gapsIf you hold ISO 27002:202248.6% covered · 128 gapsIf you hold CIS Controls v843% covered · 142 gapsIf you hold Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.141% covered · 147 gaps

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. 415 were rejected on the ISO 27001:2022 pair alone.

See the released pairs, $299 eachBrowse the graph free

Query this from an agent

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

MCP endpointAll PCI DSS 4.0 controls