C5 (Germany)
C5: Operations

C5 (Germany) C5-OPS-22: Testing and Documentation of known Vulnerabilities

Check production system components automatically for known vulnerabilities at least once a month under the vulnerability handling rules, assess severity against defined criteria and initiate remediation or mitigation within the time window that severity carries.

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

What else in your programme already covers this

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

CIS Controls v8 · 5 controls

  • CIS-18.3 Remediate Penetration Test Findings
  • CIS-7.2 Establish and Maintain a Remediation Process
  • CIS-7.5 Perform Automated Vulnerability Scans of Internal Enterprise Assets
  • CIS-7.6 Perform Automated Vulnerability Scans of Externally-Exposed Enterprise Assets
  • CIS-7.7 Remediate Detected Vulnerabilities

Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 · 5 controls

FedRAMP High · 5 controls

  • CA-5 Plan of Action and Milestones
  • CA-8 Penetration Testing
  • RA-5 Vulnerability Monitoring and Scanning
  • SI-2 Flaw Remediation
  • SI-2(3) Flaw Remediation | Time to Remediate Flaws and Benchmarks for Corrective Actions (SI-2(3))

FedRAMP Moderate · 5 controls

  • CA-5 Plan of Action and Milestones
  • CA-8 Penetration Testing
  • RA-5 Vulnerability Monitoring and Scanning
  • SI-2 Flaw Remediation
  • SI-2(3) Flaw Remediation | Time to Remediate Flaws and Benchmarks for Corrective Actions (SI-2(3))

CMMC 2.0 · 4 controls

NIST SP 800-218 · 4 controls

NIST SP 800-53 Rev 5 · 4 controls

PCI DSS 4.0 · 4 controls

  • 11.3.1 11.3.1 Quarterly internal vulnerability scans
  • 11.3.2 11.3.2 Quarterly ASV external vulnerability scans
  • 11.4.4 11.4.4 Correct exploitable findings from penetration tests
  • 6.3.3 6.3.3 Timely installation of security patches

ACSC Essential Eight · 3 controls

  • E8-PATCHAPP-ML1 Patch Applications (ML1)
  • E8-PATCHAPP-ML2 Patch Applications (ML2)
  • E8-PATCHOS-ML1 Patch Operating Systems (ML1)

AWS Well-Architected Security Pillar · 3 controls

  • SEC04-BP04 Initiate remediation for non-compliant resources
  • SEC06-BP01 Perform vulnerability management
  • SEC11-BP02 Automate testing throughout the development and release lifecycle

NIST SP 800-171 Rev 3 · 3 controls

UK Cyber Essentials · 3 controls

  • CE-SU.2 Automatic Updates Enabled Where Possible
  • CE-SU.3 Critical and High Updates within 14 Days
  • CE-SU.5 Firmware Updates

ASD Strategies to Mitigate Cyber Security Incidents · 2 controls

  • ASD37-02 Patch applications (Essential)
  • ASD37-19 Patch operating systems (Essential)

Azure Security Benchmark · 2 controls

  • ASBv3-PV-6 Rapidly and automatically remediate vulnerabilities
  • PV-5 Perform vulnerability assessments

NIST SP 800-161 Rev 1 · 2 controls

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

  • ANSSI-HYG-34 Define an Update Policy for Information System Components

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

DORA · 1 control

ISO 22301:2019 · 1 control

  • 10.1 Nonconformity and corrective action

ISO 27001:2022 · 1 control

  • 8.8 Management of technical vulnerabilities

ISO 27002:2022 · 1 control

  • 8.8 Management of technical vulnerabilities

ISO 27701:2019 · 1 control

  • 6.9.6 Technical vulnerability management

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 SP 800-172 · 1 control

  • 3.12.1e Penetration Testing by Independent Agents

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: Operations

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

C5 (Germany) C5-OPS-22 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.

If you hold Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.178.5% covered · 26 gapsIf you hold NIST SP 800-53 Rev 572.7% covered · 33 gapsIf you hold FedRAMP Moderate71.1% covered · 35 gapsIf you hold ISO 27002:202267.8% covered · 39 gapsIf you hold ISO 27001:202257% covered · 52 gapsIf you hold NIST SP 800-171 Rev 350.4% covered · 60 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. 0 were rejected on the Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 pair alone.

See the released pairs, $299 eachBrowse the graph free

Query this from an agent

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

MCP endpointAll C5 (Germany) controls