NIST CSF 2.0 · Protect (PR)
PR.PS-06
Secure software development practices are integrated, and their performance is monitored throughout the software development life cycle
frameworkNIST Cybersecurity Framework 2.0
sectionProtect (PR)
topicsSecure Development, Web Security, API Security
frameworks6 2 5
Wrong or missing mapping? Report it
| Framework | Requirement | Title | Link | Source / reason |
|---|---|---|---|---|
| ISO 27001 | A.8.5A.8.25A.8.26A.8.28A.8.29 | Secure authentication; Secure development life cycle… | Crosswalk | Same topic: API Security, Secure Development, Web Security1 loosely related (not mappings)A.8.31 Separation of development, test and production environments Only shares CSF PR.PS-06: related, not a mapping |
| CIS v8.1 | CIS 16.1CIS 9.3CIS 13.10CIS 16.2CIS 16.3CIS 16.5CIS 16.8CIS 16.9CIS 16.10CIS 16.11CIS 16.12CIS 16.13CIS 16.14 | Establish and Maintain a Secure Application Development Process; Maintain and Enforce Network-Based URL Filters… | Crosswalk | Same topic: Secure Development, Web Security, API Security |
| SOC 2 | CC6.6CC8.1 | Protection against threats from outside system boundaries; Change management for infrastructure, data and software | Editorial | Same topic: Web Security, Secure Development (editorial pick) |
| PCI DSS | 6.2.26.2.36.2.16.2.46.4.16.4.3 | Developers trained in secure software development; Custom code reviewed before release… | Crosswalk | Same topic: Secure Development, API Security, Web Security |
| CMMC | SC.L2-3.13.1SC.L2-3.13.2 | Boundary Protection; Security Engineering | Crosswalk | Same topic: Web Security, Secure Development |
| 800-53 | IA-9SA-3SA-8SA-11SA-15SC-5SC-7SI-10 | Service Identification and Authentication; System Development Life Cycle… | Crosswalk | Same topic: API Security, Secure Development, Web Security3 loosely related (not mappings)SA-17 Developer Security and Privacy Architecture and Design Only shares CSF PR.PS-06: related, not a mapping |
| HIPAA | — | No requirement | No mapping in our data | No mapping in our data. |
| GDPR | Art.25(1) | Data protection by design and by default | Editorial | Same topic: Secure Development (editorial pick) |
| NIS2 | 6.2 | Secure development life cycle | Crosswalk | Same topic: Secure Development |
| Essential Eight | — | No requirement | No mapping in our data | No mapping in our data (Essential Eight links are editorial only). |
| DORA | — | No requirement | No mapping in our data | No mapping in our data (DORA links are editorial, and its technical standards are not mapped). |
| CPS 234 | — | No requirement | No mapping in our data | No mapping in our data (CPS 234 is principles-based and its links are editorial). |
| Cyber Essentials | — | No requirement | No mapping in our data | No mapping in our data (Cyber Essentials covers five technical controls only). |
Crosswalk a published crosswalk (NIST, ENISA, CIS, PCI SSC) makes the link · Editorial ControlMapping's judgement where no crosswalk exists; the reason is shown · only shares a CSF 2.0 outcome: worth checking, not a mapping · No mapping in our data nothing mapped in our data; often new work, but check the coverage notes. How links are sourced.