PCI DSS 4.0
Req 12: Information Security Policies

PCI DSS 4.0 12.6.1: 12.6.1 Formal security awareness program

A formal security awareness program must be in place so that all personnel know the entity's security policy and its procedures, and understand their own part in protecting cardholder data. The guidance notes that without such education, safeguards may be undermined by accidental mistakes or deliberate acts. Customized approach objective: personnel understand the threat landscape and their duties in operating relevant security controls, and can obtain help and guidance when they need it.

Maintained by Gerard BlokdykControl text last updated

What else in your programme already covers this

This control maps to 60 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.

SOC 2 · 7 controls

  • SOC2-CC4.2 CC4.2 Evaluating and communicating control deficiencies (COSO principle 17)
  • SOC2-CC5.1 CC5.1 Selecting control activities that mitigate risk (COSO principle 10)
  • SOC2-CC5.2 CC5.2 General controls over technology (COSO principle 11)
  • SOC2-CC6.8 CC6.8 Preventing and detecting unauthorised or malicious software
  • SOC2-CC7.1 CC7.1 Detecting configuration changes and new vulnerabilities
  • SOC2-CC8.1 CC8.1 Managing changes to procedures, software, data and infrastructure
  • SOC2-CC9.1 CC9.1 Mitigating risks of business disruption

CIS Controls v8 · 4 controls

  • CIS-16.2 Establish and Maintain a Process to Accept and Address Software Vulnerabilities
  • CIS-7.1 Establish and Maintain a Vulnerability Management Process
  • CIS-7.5 Perform Automated Vulnerability Scans of Internal Enterprise Assets
  • CIS-7.7 Remediate Detected Vulnerabilities

HIPAA Security Rule · 4 controls

ISO 27001:2022 · 4 controls

  • 5.23 Information security for use of cloud services
  • 8.25 Secure development life cycle
  • 8.8 Management of technical vulnerabilities
  • 8.9 Configuration management

ISO 27002:2022 · 4 controls

  • 5.23 Information security for use of cloud services
  • 8.25 Secure development life cycle
  • 8.8 Management of technical vulnerabilities
  • 8.9 Configuration management

NIST Cybersecurity Framework 2.0 · 4 controls

  • NIST-CSF-DE.CM-09 Computing hardware and software, runtime environments, and their data are monitored to find potentially adverse events
  • NIST-CSF-GV.SC-05 Requirements to address cybersecurity risks in supply chains are established, prioritized, and integrated into contracts and other types of agreements with suppliers and other relevant third parties
  • 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 SP 800-53 Rev 5 · 4 controls

NIST SP 800-66 Rev 2 · 4 controls

APRA CPS 234 · 2 controls

  • CPS234-15 Information Security Capability
  • CPS234-P19 Policy Direction to All Responsible Parties

ASD Strategies to Mitigate Cyber Security Incidents · 2 controls

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

  • CCM-TVM-01 Threat and Vulnerability Management Policy and Procedures
  • CCM-TVM-03 Vulnerability Remediation Schedule

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

ISO 27701:2019 · 2 controls

  • 6.4.2 During employment
  • 6.9.6 Technical vulnerability management

NIST SP 800-181 · 2 controls

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

  • ANSSI-HYG-02 Raise User Awareness of Basic Security Practice

Australia Consumer Data Right - Banking (CDR) · 1 control

  • AUCDR-IS-6 Information security training and awareness program

Authorised Economic Operator (AEO) Programmes - Global Standards · 1 control

  • AEO-10 Education, Training and Awareness

C5 (Germany) · 1 control

  • C5-HR-03 Security training and awareness programme

CFTC System Safeguards (17 CFR 37, 38, 39, 49) · 1 control

CMMC 2.0 · 1 control

NIS2 Directive · 1 control

  • Art.20.2 Train the management body, and offer equivalent training to staff on a regular basis

NIST SP 800-161 Rev 1 · 1 control

NIST SP 800-171 Rev 3 · 1 control

  • 03.02.01 Literacy Training and Awareness

NIST SP 800-172 · 1 control

  • 3.2.1e Provide Awareness Training on Advanced Persistent Threat

PCI 3DS Core Security Standard · 1 control

  • P1-1.3.1 P1-1.3.1 Security awareness programme in operation

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

MCP endpointAll PCI DSS 4.0 controls