PCI DSS 4.0
Req 6: Secure Systems and Software

PCI DSS 4.0 6.2.2: 6.2.2 Annual secure software training for developers

Staff who develop bespoke and custom software must receive training at least every 12 months that: addresses software security relevant to their job and to the development languages they use; covers techniques for secure coding and for designing secure software; and, where security testing tools are in use, explains how to operate those tools to find vulnerabilities in software. It applies to all entities with in-house or contracted developers of bespoke and custom software. Objective under the customized approach: developers stay current on secure development practice, software security and attacks aimed at the languages, frameworks or applications they build, 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 32 controls across 22 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.

NIST SP 800-53 Rev 5 · 4 controls

CIS Controls v8 · 2 controls

  • CIS-14.9 Conduct Role-Specific Security Awareness and Skills Training
  • CIS-16.9 Train Developers in Application Security Concepts and Secure Coding

FedRAMP High · 2 controls

  • AT-3 Role-Based Training
  • AT-4 Training Records

FedRAMP Moderate · 2 controls

  • AT-3 Role-Based Training
  • AT-4 Training Records

ISO 27701:2019 · 2 controls

  • 5.5.2 Competence
  • 6.11.2 Security in development and support processes

NIST Cybersecurity Framework 2.0 · 2 controls

  • NIST-CSF-PR.AT-01 Personnel are provided with awareness and training so that they possess the knowledge and skills to perform general tasks with cybersecurity risks in mind
  • NIST-CSF-PR.AT-02 Individuals in specialized roles are provided with awareness and training so that they possess the knowledge and skills to perform relevant tasks with cybersecurity risks in mind

NIST SP 800-181 · 2 controls

SOC 2 · 2 controls

  • SOC2-CC1.4 CC1.4 Attracting, developing and retaining competent people (COSO principle 4)
  • SOC2-CC5.1 CC5.1 Selecting control activities that mitigate risk (COSO principle 10)

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

  • ANSSI-HYG-01 Train Operational Teams in Information System Security

AWS Well-Architected Security Pillar · 1 control

C5 (Germany) · 1 control

  • C5-DEV-04 Safety training and awareness programme regarding continuous software delivery and associated systems, components or tools

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

  • CFTC-SS-5 Systems Development and Quality Assurance Category

CMMC 2.0 · 1 control

Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 · 1 control

ISO 22301:2019 · 1 control

ISO 27001:2022 · 1 control

  • 6.3 Information security awareness, education and training

ISO 27002:2022 · 1 control

  • 6.3 Information security awareness, education and training

ISO/IEC 42001:2023 · 1 control

NIST SP 800-161 Rev 1 · 1 control

NIST SP 800-171 Rev 3 · 1 control

NIST SP 800-218 · 1 control

PCI 3DS Core Security Standard · 1 control

  • P1-3.1.2 P1-3.1.2 Developers trained in secure development

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 6: Secure Systems and Software

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

PCI DSS 4.0 6.2.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 32 it maps to, and the evidence behind each claim, over MCP and REST.

MCP endpointAll PCI DSS 4.0 controls