800-53 · SA System and Services Acquisition
SA-15
Development Process, Standards, and Tools
frameworkNIST SP 800-53 Rev 5.2
sectionSA System and Services Acquisition
csf 2.0ID.RA-01 ID.RA-09 PR.PS-04 PR.PS-06
topicsSecure Development
frameworks6 2 0
Official texta. Require the developer of the system, system component, or system service to follow a documented development process that:
1. Explicitly addresses security and privacy requirements;
2. Identifies the standards and tools used in the development process;
3. Documents the specific tool options and tool configurations used in the development process; and
4. Documents, manages, and ensures the integrity of changes to the process and/or tools used in development; and
b. Review the development process, standards, tools, tool options, and tool configurations [Assignment: organization-defined frequency] to determine if the process, standards, tools, tool options and tool configurations selected and employed can satisfy the following security and privacy requirements: [Assignment: organization-defined organization-defined security and privacy requirements].NIST SP 800-53 Rev 5.2 control statement (public domain)
1. Explicitly addresses security and privacy requirements;
2. Identifies the standards and tools used in the development process;
3. Documents the specific tool options and tool configurations used in the development process; and
4. Documents, manages, and ensures the integrity of changes to the process and/or tools used in development; and
b. Review the development process, standards, tools, tool options, and tool configurations [Assignment: organization-defined frequency] to determine if the process, standards, tools, tool options and tool configurations selected and employed can satisfy the following security and privacy requirements: [Assignment: organization-defined organization-defined security and privacy requirements].NIST SP 800-53 Rev 5.2 control statement (public domain)
Wrong or missing mapping? Report it
| Framework | Requirement | Title | Link | Source / reason |
|---|---|---|---|---|
| NIST CSF 2.0 | PR.PS-06 | Secure software development practices are integrated, and their performance is monitored throughout the software development life cycle | Crosswalk | Same topic: Secure Development3 loosely related (not mappings)ID.RA-01 Vulnerabilities in assets are identified, validated, and recorded Only shares CSF ID.RA-01: related, not a mapping ID.RA-09 The authenticity and integrity of hardware and software are assessed prior to acquisition and use Only shares CSF ID.RA-09: related, not a mapping PR.PS-04 Log records are generated and made available for continuous monitoring Only shares CSF PR.PS-04: related, not a mapping |
| ISO 27001 | A.8.25A.8.26A.8.28A.8.29A.5.8A.8.30 | Secure development life cycle; Application security requirements… | Crosswalk | Same topic: Secure Development NIST SP 800-53 → ISO 27001 mapping 7 loosely related (not mappings)A.5.19 Information security in supplier relationships Only shares CSF ID.RA-09: related, not a mapping A.5.20 Addressing information security within supplier agreements Only shares CSF ID.RA-09: related, not a mapping A.5.22 Monitoring, review and change management of supplier services Only shares CSF ID.RA-09: related, not a mapping 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 16.2CIS 16.3CIS 16.5CIS 16.8CIS 16.9CIS 16.11CIS 16.12CIS 16.13CIS 16.14 | Establish and Maintain a Secure Application Development Process; Establish and Maintain a Process to Accept and Address Software Vulnerabilities… | Crosswalk | Same topic: Secure Development23 loosely related (not mappings)CIS 7.1 Establish and Maintain a Vulnerability Management Process Only shares CSF ID.RA-01: related, not a mapping CIS 7.5 Perform Automated Vulnerability Scans of Internal Enterprise Assets Only shares CSF ID.RA-01: related, not a mapping CIS 7.6 Perform Automated Vulnerability Scans of Externally-Exposed Enterprise Assets Only shares CSF ID.RA-01: related, not a mapping CIS 8.1 Establish and Maintain an Audit Log Management Process Only shares CSF PR.PS-04: related, not a mapping …and 15 more in the downloads |
| SOC 2 | CC8.1 | Change management for infrastructure, data and software | Editorial | Same topic: Secure Development (editorial pick) |
| PCI DSS | 6.2.26.2.36.2.1 | Developers trained in secure software development; Custom code reviewed before release… | Crosswalk | Same topic: Secure Development18 loosely related (not mappings)6.3.2 Inventory of custom software and its components Only shares CSF ID.RA-01, PR.PS-06: related, not a mapping 6.4.3 Payment page scripts authorised and integrity-checked Only shares CSF ID.RA-09, PR.PS-06: related, not a mapping 11.4.4 Penetration test findings corrected and retested Only shares CSF ID.RA-01, PR.PS-06: related, not a mapping …and 10 more in the downloads |
| CMMC | SC.L2-3.13.2 | Security Engineering | Crosswalk | Same topic: Secure Development15 loosely related (not mappings)…and 7 more in the downloads |
| HIPAA | §164.308(a)(1)(ii)(D)§164.308(a)(1)(ii)(A)§164.308(a)(1)(ii)(B)§164.308(a)(5)(ii)(C) | Information System Activity Review; Risk Analysis… | No mapping. Only shares CSF ID.RA-01, PR.PS-04: related, not a mapping+11 more loosely related (not mappings)§164.308(b)(4) Written Contract or Other Arrangement Only shares CSF ID.RA-09: related, not a mapping …and 7 more in the downloads | |
| GDPR | Art.25(1) | Data protection by design and by default | Editorial | Same topic: Secure Development (editorial pick)2 loosely related (not mappings) |
| NIS2 | 6.2 | Secure development life cycle | Crosswalk | Same topic: Secure Development4 loosely related (not mappings)6.1 Security in acquisition of ICT services, ICT systems or ICT products Only shares CSF ID.RA-09: related, not a mapping |
| Essential Eight | ISM-0304ISM-1407ISM-1501ISM-1509 | Applications other than office productivity suites, web browsers and their extensions…; The latest release, or the previous release, of operating systems are used… | No mapping. Only shares CSF ID.RA-01, PR.PS-04: related, not a mapping+30 more loosely related (not mappings)ISM-1623 PowerShell module logging, script block logging and transcription events are centrally… Only shares CSF PR.PS-04: related, not a mapping ISM-1660 Allowed and blocked application control events are centrally logged Only shares CSF PR.PS-04: related, not a mapping ISM-1683 Successful and unsuccessful multi-factor authentication events are centrally logged Only shares CSF PR.PS-04: related, not a mapping ISM-1690 Patches, updates or other vendor mitigations for vulnerabilities in online services are applied within two weeks of… Only shares CSF ID.RA-01: related, not a mapping …and 26 more in the downloads | |
| DORA | Art.8(2)Art.10(3)Art.25(1)Art.26(1) | Identification; Detection… | No mapping. Only shares CSF ID.RA-01, PR.PS-04: related, not a mapping+4 more loosely related (not mappings)Art.27(1) Requirements for testers for the carrying out of TLPT Only shares CSF ID.RA-01: related, not a mapping Art.29(1) Preliminary assessment of ICT concentration risk at entity level Only shares CSF ID.RA-09: related, not a mapping Art.29(2) Preliminary assessment of ICT concentration risk at entity level Only shares CSF ID.RA-09: related, not a mapping | |
| CPS 234 | Para 16Para 17Para 22Para 27 | Assess third parties' information security capability; Keep capability current as threats and vulnerabilities change… | No mapping. Only shares CSF ID.RA-09, ID.RA-01: related, not a mapping+1 more loosely related (not mappings)Para 30 Testing by skilled, functionally independent specialists Only shares CSF ID.RA-01: related, not a mapping | |
| Cyber Essentials | CE 3 | Security Update Management | No mapping. Only shares CSF ID.RA-01: related, not a mapping |
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.