Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 CCM-AIS-04: Secure Application Design and Development

What else in your programme already covers this

This control maps to 64 controls across 24 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.

NIST SP 800-53 Rev 5 · 7 controls

NIST800-PL-8 PL-8 Security and Privacy Architectures
NIST800-SA-15 SA-15 Development Process, Standards, and Tools
NIST800-SA-17 SA-17 Developer Security and Privacy Architecture and Design
NIST800-SA-22 SA-22 Unsupported System Components
NIST800-SA-3 SA-3 System Development Life Cycle
NIST800-SA-8 SA-8 Security and Privacy Engineering Principles
NIST800-SI-10 SI-10 Information Input Validation

FedRAMP High · 5 controls

PL-8 Security and Privacy Architectures
SA-15 Development Process, Standards, and Tools (SA-15)
SA-3 System Development Life Cycle
SA-8 Security and Privacy Engineering Principles
SI-10 Information Input Validation

FedRAMP Moderate · 5 controls

PL-8 Security and Privacy Architectures
SA-15 Development Process, Standards, and Tools (SA-15)
SA-3 System Development Life Cycle
SA-8 Security and Privacy Engineering Principles
SI-10 Information Input Validation

NIST SP 800-218 · 5 controls

SP800-218-PO.1.2 Implement Security Requirements in the Toolchain
SP800-218-PW.1.1 Design Software to Meet Security Requirements
SP800-218-PW.2.1 Qualified Review of Software Design
SP800-218-PW.4.2 Maintain Well-Secured In-House Components
SP800-218-PW.5.1 Secure Coding Practices

CIS Controls v8 · 4 controls

CIS-16.1 Establish and Maintain a Secure Application Development Process
CIS-16.10 Apply Secure Design Principles in Application Architectures
CIS-16.14 Conduct Threat Modeling
CIS-16.9 Train Developers in Application Security Concepts and Secure Coding

ISO 27001:2022 · 4 controls

5.8 Information security in project management
8.25 Secure development life cycle
8.27 Secure system architecture and engineering principles
8.28 Secure coding

ISO 27002:2022 · 4 controls

5.8 Information security in project management
8.25 Secure development life cycle
8.27 Secure system architecture and engineering principles
8.28 Secure coding

NIST SP 800-161 Rev 1 · 4 controls

161R1-SA-15 Development Process, Standards, and Tools
161R1-SA-17 Developer Security and Privacy Architecture and Design
161R1-SA-3 System Development Life Cycle
161R1-SA-8 Security and Privacy Engineering Principles

AWS Well-Architected Security Pillar · 3 controls

SEC01-BP07 Identify threats and prioritize mitigations using a threat model
SEC11-BP02 Automate testing throughout the development and release lifecycle
SEC11-BP04 Conduct code reviews

Azure Security Benchmark · 3 controls

ASBv3-DS-1 Conduct threat modeling
ASBv3-GS-10 Define and implement DevOps security strategy
DS-6 Enforce security of workload throughout DevOps lifecycle

SOC 2 · 3 controls

SOC2-PI1.2 PI1.2 Controls over system inputs
SOC2-PI1.3 PI1.3 Controls over system processing
SOC2-PI1.4 PI1.4 Controls over output delivery

C5 (Germany) · 2 controls

C5-DEV-01 Policies for the development/procurement of information systems
C5-DEV-06 Testing changes

CNCF Security Technical Advisory Group (TAG) · 2 controls

CNCF-4C-CODE Code Layer Security
CNCF-SA-THREATMODEL Threat Modeling

EU AI Act · 2 controls

EUAI-Art.15 Accuracy, robustness and cybersecurity
EUAI-Art.17 Quality management system

PCI DSS 4.0 · 2 controls

6.2.1 6.2.1 Secure development of bespoke and custom software
6.2.4 6.2.4 Engineering techniques against common software attacks

ANSSI Guide d'hygiene informatique (42 mesures, v2.0) · 1 control

ANSSI-HYG-01 Train Operational Teams in Information System Security

Australia Consumer Data Right - Banking (CDR) · 1 control

AUCDR-IS-4 Formal vulnerability management program

CFTC System Safeguards (17 CFR 37, 38, 39, 49) · 1 control

CFTC-SS-5 Systems Development and Quality Assurance Category

CMMC 2.0 · 1 control

SC.L2-3.13.2 Security Engineering

ISO 27701:2019 · 1 control

6.11.2 Security in development and support processes

NIS2 Directive · 1 control

Art.21.2.e Security in acquisition, development and maintenance, including vulnerability handling and disclosure

NIST Cybersecurity Framework 2.0 · 1 control

NIST-CSF-PR.PS-06 Secure software development practices are integrated, and their performance is monitored throughout the software development life cycle

NIST SP 800-171 Rev 3 · 1 control

03.16.01 Security Engineering Principles

NIST SP 800-172 · 1 control

3.13.2e Introduce Unpredictability into System Operations

Every mapping shown was judged rather than inferred from wording similarity, and the ones that failed review are published too. See the coverage reports and what was rejected.

You are reading one control. How much of Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 have you already done?

Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 CCM-AIS-04 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 your existing evidence covers. Hold NIST SP 800-53 Rev 5 and 140 of 197 Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 controls already carry evidence.

If you hold NIST SP 800-53 Rev 571.1% covered · 57 gaps If you hold FedRAMP Moderate60.4% covered · 78 gaps If you hold PCI DSS 4.060.4% covered · 78 gaps If you hold C5 (Germany)58.4% covered · 82 gaps If you hold ISO 27001:202256.3% covered · 86 gaps If you hold ISO 27002:202256.3% covered · 86 gaps

Each report names every control your existing framework evidences, every one it does not, the reasoning behind each claim, and the claims that were argued against and rejected. 12 were rejected on the NIST SP 800-53 Rev 5 pair alone.

See the released pairs, $299 each Browse the graph free