C5 (Germany)
C5: Product Safety and Security

C5 (Germany) C5-PSS-02: Identification of Vulnerabilities of the Cloud Service

Build vulnerability detection into the software development process for the service, using a risk based mix of static and dynamic application security testing, expert code review and monitoring of confirmed flaws in third party libraries, then rate severity and remediate or mitigate immediately.

Maintained by Gerard BlokdykVerified against the published standard Control text last updated

What else in your programme already covers this

This control maps to 39 controls across 18 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-218 · 7 controls

FedRAMP High · 5 controls

  • RA-5 Vulnerability Monitoring and Scanning
  • RA-5(11) Vulnerability Monitoring and Scanning | Public Disclosure Program (RA-5(11))
  • SA-11 Developer Testing and Evaluation
  • SA-11(1) Developer Testing and Evaluation | Static Code Analysis (SA-11(1))
  • SA-11(2) Developer Testing and Evaluation | Threat Modeling and Vulnerability Analyses (SA-11(2))

FedRAMP Moderate · 5 controls

  • RA-5 Vulnerability Monitoring and Scanning
  • RA-5(11) Vulnerability Monitoring and Scanning | Public Disclosure Program (RA-5(11))
  • SA-11 Developer Testing and Evaluation
  • SA-11(1) Developer Testing and Evaluation | Static Code Analysis (SA-11(1))
  • SA-11(2) Developer Testing and Evaluation | Threat Modeling and Vulnerability Analyses (SA-11(2))

CIS Controls v8 · 3 controls

  • CIS-16.1 Establish and Maintain a Secure Application Development Process
  • CIS-16.2 Establish and Maintain a Process to Accept and Address Software Vulnerabilities
  • CIS-7.6 Perform Automated Vulnerability Scans of Externally-Exposed Enterprise Assets
  • SEC11-BP02 Automate testing throughout the development and release lifecycle
  • SEC11-BP04 Conduct code reviews
  • ASBv3-DS-4 Integrate static application security testing into DevOps pipeline
  • DS-2 Ensure software supply chain security

ISO 27001:2022 · 2 controls

  • 8.29 Security testing in development and acceptance
  • 8.8 Management of technical vulnerabilities

PCI DSS 4.0 · 2 controls

  • 6.2.3 6.2.3 Code review before release
  • 6.3.1 6.3.1 Vulnerability identification and risk ranking
  • AUCDR-IS-4 Formal vulnerability management program

CMMC 2.0 · 1 control

ISO 27002:2022 · 1 control

  • 8.29 Security testing in development and acceptance

NIS2 Directive · 1 control

  • Art.21.2.e Security in acquisition, development and maintenance, including vulnerability handling and disclosure
  • 03.11.02 Vulnerability Monitoring and Scanning

SOC 2 · 1 control

  • SOC2-CC7.1 CC7.1 Detecting configuration changes and new vulnerabilities

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.

Other controls in C5: Product Safety and Security

You are reading one control. How much of C5 (Germany) have you already done?

C5 (Germany) C5-PSS-02 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of C5 (Germany) your existing evidence covers. Hold Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 and 95 of 121 C5 (Germany) controls already carry evidence.

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. 0 were rejected on the Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 pair alone.

Query this from an agent

The graph holds this control, the 39 it maps to, and the evidence behind each claim, over MCP and REST.