💼 6.2.2 Software development personnel working on bespoke and custom software are trained at least once every 12 months.
- ID:
/frameworks/pci-dss-v4.0/06/02/02
Description​
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.
Similar​
- Sections
/frameworks/pci-dss-v3.2.1/06/05/frameworks/pci-dss-v4.0.1/06/02/02
- Internal
- ID:
dec-c-4a3a4cd3
- ID:
Similar Sections (Take Policies From)​
| Section | Sub Sections | Internal Rules | Policies | Flags | Compliance |
|---|---|---|---|---|---|
| 💼 PCI DSS v3.2.1 → 💼 6.5 Address common coding vulnerabilities in software-development processes. | 10 | 5 | no data | ||
| 💼 PCI DSS v4.0.1 → 💼 6.2.2 Software development personnel working on bespoke and custom software are trained at least once every 12 months. | no data |
Similar Sections (Give Policies To)​
| Section | Sub Sections | Internal Rules | Policies | Flags | Compliance |
|---|---|---|---|---|---|
| 💼 PCI DSS v3.2.1 → 💼 6.5 Address common coding vulnerabilities in software-development processes. | 10 | 5 | no data | ||
| 💼 PCI DSS v4.0.1 → 💼 6.2.2 Software development personnel working on bespoke and custom software are trained at least once every 12 months. | no data |
Sub Sections​
| Section | Sub Sections | Internal Rules | Policies | Flags | Compliance |
|---|