PCI DSS 4.0
Req 2: Secure Configurations

PCI DSS 4.0 2.3.2: 2.3.2 Wireless encryption keys changed on triggers

For wireless environments that connect to the CDE or carry account data, wireless encryption keys must be changed: (a) whenever someone who knows the key leaves the company or leaves the role for which that knowledge was needed; and (b) whenever compromise of a key is known or suspected. Applicability: no special notes; applies to every assessed entity. Customized approach objective: knowing a wireless encryption key cannot give anyone unauthorised access to wireless networks.

Maintained by Gerard BlokdykControl text last updated

What else in your programme already covers this

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

SOC 2 · 4 controls

  • SOC2-CC5.2 CC5.2 General controls over technology (COSO principle 11)
  • SOC2-CC6.1 CC6.1 Logical access security over protected information assets
  • SOC2-CC7.1 CC7.1 Detecting configuration changes and new vulnerabilities
  • SOC2-CC8.1 CC8.1 Managing changes to procedures, software, data and infrastructure

ISO 27001:2022 · 3 controls

  • 5.17 Authentication information
  • 6.5 Responsibilities after termination or change of employment
  • 8.24 Use of cryptography

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

FedRAMP High · 2 controls

  • AC-18(1) Authentication and Encryption
  • SC-12 Cryptographic Key Establishment and Management

FedRAMP Moderate · 2 controls

  • AC-18(1) Authentication and Encryption
  • SC-12 Cryptographic Key Establishment and Management

HIPAA Security Rule · 2 controls

NIST SP 800-171 Rev 3 · 2 controls

  • 03.09.02 Personnel Termination and Transfer
  • 03.13.10 Cryptographic Key Establishment and Management

NIST SP 800-66 Rev 2 · 2 controls

ANSSI Guide d'hygiene informatique (42 mesures, v2.0) · 1 control

  • ANSSI-HYG-20 Secure Wi-Fi Access Networks and Separate Usage

CMMC 2.0 · 1 control

ISO 27002:2022 · 1 control

  • 8.24 Use of cryptography

ISO 27701:2019 · 1 control

  • 6.7.1 Cryptographic controls

NIST Cybersecurity Framework 2.0 · 1 control

  • NIST-CSF-PR.DS-02 The confidentiality, integrity, and availability of data-in-transit are protected

NIST SP 800-53 Rev 5 · 1 control

  • NIST800-SC-12 SC-12 Cryptographic Key Establishment and Management

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 2: Secure Configurations

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

PCI DSS 4.0 2.3.2 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 280 PCI DSS 4.0 controls already carry evidence.

If you hold ISO 27001:202249.6% covered · 141 gapsIf you hold FedRAMP Moderate49.3% covered · 142 gapsIf you hold NIST SP 800-53 Rev 547.5% covered · 147 gapsIf you hold ISO 27002:202243.2% covered · 159 gapsIf you hold CIS Controls v838.2% covered · 173 gapsIf you hold Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.136.4% covered · 178 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 25 it maps to, and the evidence behind each claim, over MCP and REST.

MCP endpointAll PCI DSS 4.0 controls