6.2.2 Software development personnel working on bespoke and custom software are trained
Defined Approach Requirements
6.2.2 Software development personnel working on bespoke and custom software are trained at least once every 12 months as follows:
- On software security relevant to their job function and development languages.
- Including secure software design and secure coding techniques.
- Including, if security testing tools are used, how to use the tools for detecting vulnerabilities in software.
Customized Approach Objective
Software development personnel remain knowledgeable about secure development practices; software security; and attacks against the languages, frameworks, or applications they develop. Personnel are able to access assistance and guidance when required.
Defined Approach Testing Procedures
6.2.2.a Examine software development procedures to verify that processes are defined for training of software development personnel developing bespoke and custom software that includes all elements specified in this requirement.
6.2.2.b Examine training records and interview personnel to verify that software development personnel working on bespoke and custom software received software security training that is relevant to their job function and development languages in accordance with all elements specified in this requirement.
Purpose
Having staff knowledgeable in secure coding methods, including techniques defined in Requirement 6.2.4, will help minimize the number of security vulnerabilities introduced through poor coding practices.
Good Practice
Training for developers may be provided in-house or by third parties.
Training should include, but is not limited to, development languages in use, secure software design, secure coding techniques, use of techniques/methods for finding vulnerabilities in code, processes to prevent reintroducing previously resolved vulnerabilities, and how to use any automated security testing tools for detecting vulnerabilities in software.
As industry-accepted secure coding practices change, organizational coding practices and developer training may need to be updated to address new threats.
purpose
Ensure all system components and software are supported by the vendor and receive security updates.
compliance strategies
- Patch management program
- Vendor support tracking
typical policies
- Patch Management Policy
common pitfalls
- Unsupported systems in use
- Missed end-of-life notifications
type
Technical/Process Control
difficulty
Moderate
key risks
- Unpatched vulnerabilities
recommendations
- Automate end-of-life tracking and patch reminders
Eligible SAQ
- SAQ-A-EP
- SAQ-C
- SAQ-D MERCHANT
- SAQ-D SERVICE PROVIDER
Your perspective on this PCI DSS requirement matters! Share your implementation experiences, challenges, or questions below. Your insights help other organizations improve their compliance journey and build a stronger security community.Comment Policy