cm/controlmapping
Sources
ISO 27001 · A.8 Technological controls
A.8.28

Secure coding

frameworkISO/IEC 27001:2022 sectionA.8 Technological controls csf 2.0PR.PS-06 topicsSecure Development frameworks6 2 0 5
Official text · not licensableTitle: Secure coding. The control text is ISO's copyright; see ISO/IEC 27001:2022.

Wrong or missing mapping? Report it

Equivalents of A.8.28 in other frameworks
FrameworkRequirementTitleLinkSource / reason
NIST CSF 2.0PR.PS-06Secure software development practices are integrated, and their performance is monitored throughout the software development life cycleCrosswalkSame topic: Secure Development
CIS v8.1CIS 16.1CIS 16.2CIS 16.3CIS 16.5CIS 16.8CIS 16.9CIS 16.11CIS 16.12CIS 16.13CIS 16.14Establish and Maintain a Secure Application Development Process; Establish and Maintain a Process to Accept and Address Software Vulnerabilities…CrosswalkSame topic: Secure Development
3 loosely related (not mappings)
CIS 9.3 Maintain and Enforce Network-Based URL Filters Loosely related
Only shares CSF PR.PS-06: related, not a mapping
CIS 13.10 Perform Application Layer Filtering Loosely related
Only shares CSF PR.PS-06: related, not a mapping
CIS 16.10 Apply Secure Design Principles in Application Architectures Loosely related
Only shares CSF PR.PS-06: related, not a mapping
SOC 2CC8.1Change management for infrastructure, data and softwareEditorialSame topic: Secure Development (editorial pick)
1 loosely related (not mappings)
CC6.6 Protection against threats from outside system boundaries Loosely related
Only shares CSF PR.PS-06: related, not a mapping
PCI DSS6.2.26.2.36.2.1Developers trained in secure software development; Custom code reviewed before release…CrosswalkSame topic: Secure Development
5 loosely related (not mappings)
6.3.2 Inventory of custom software and its components Loosely related
Only shares CSF PR.PS-06: related, not a mapping
11.4.4 Penetration test findings corrected and retested Loosely related
Only shares CSF PR.PS-06: related, not a mapping
6.2.4 Coding techniques prevent common software attacks Loosely related
Only shares CSF PR.PS-06: related, not a mapping
6.4.1 Public web applications protected against attacks Loosely related
Only shares CSF PR.PS-06: related, not a mapping
6.4.3 Payment page scripts authorised and integrity-checked Loosely related
Only shares CSF PR.PS-06: related, not a mapping
CMMCSC.L2-3.13.2Security EngineeringCrosswalkSame topic: Secure Development
800-53SA-3SA-8SA-11SA-15SA-4SA-10System Development Life Cycle; Security and Privacy Engineering Principles…CrosswalkSame topic: Secure Development
NIST SP 800-53 → ISO 27001 mapping
3 loosely related (not mappings)
SA-17 Developer Security and Privacy Architecture and Design Loosely related
Only shares CSF PR.PS-06: related, not a mapping
SA-24 Design For Cyber Resiliency Loosely related
Only shares CSF PR.PS-06: related, not a mapping
SI-10 Information Input Validation Loosely related
Only shares CSF PR.PS-06: related, not a mapping
HIPAA—No requirementNo mapping in our dataNo mapping in our data.
GDPRArt.25(1)Data protection by design and by defaultEditorialSame topic: Secure Development (editorial pick)
NIS26.2Secure development life cycleCrosswalkSame topic: Secure Development
Essential Eight—No requirementNo mapping in our dataNo mapping in our data (Essential Eight links are editorial only).
DORA—No requirementNo mapping in our dataNo mapping in our data (DORA links are editorial, and its technical standards are not mapped).
CPS 234—No requirementNo mapping in our dataNo mapping in our data (CPS 234 is principles-based and its links are editorial).
Cyber Essentials—No requirementNo mapping in our dataNo 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 · Loosely related 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.