CIS Controls v8
CIS Control 16: Application Software Security

CIS Controls v8 CIS-16.3: Perform Root Cause Analysis on Security Vulnerabilities

Analyse the root causes of security vulnerabilities. In reviewing vulnerabilities, root cause analysis looks at the underlying problems that give rise to flaws in code, so development teams can go further than patching each vulnerability as it appears.

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

What else in your programme already covers this

This control maps to 26 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 · 4 controls

NIST SP 800-53 Rev 5 · 4 controls

  • NIST-CSF-ID.IM-02 Improvements are identified from security tests and exercises, including those done in coordination with suppliers and relevant third parties
  • NIST-CSF-ID.IM-03 Improvements are identified from execution of operational processes, procedures, and activities
  • NIST-CSF-RS.AN-08 An incident's magnitude is estimated and validated
  • SEC10-BP08 Establish a framework for learning from incidents
  • ISM-1909 Root cause analysis of vulnerabilities
  • ASBv3-IR-7 Post-incident activity - conduct lesson learned and retain evidence

C5 (Germany) · 1 control

  • C5-OPS-20 Managing Vulnerabilities, Malfunctions and Errors - Measurements, Analyses and Assessments of Procedures

FedRAMP High · 1 control

  • SI-2 Flaw Remediation

FedRAMP Moderate · 1 control

  • SI-2 Flaw Remediation

ISO 22301:2019 · 1 control

  • 10.2 Continual improvement

ISO 27001:2022 · 1 control

  • 5.27 Learning from information security incidents

ISO 27002:2022 · 1 control

  • 5.27 Learning from information security incidents

ISO 27701:2019 · 1 control

  • 5.8.1 Nonconformity and corrective action

ISO/IEC 42001:2023 · 1 control

  • 10.2 Nonconformity and corrective action

PCI DSS 4.0 · 1 control

  • 6.3.1 6.3.1 Vulnerability identification and risk ranking

SOC 2 · 1 control

  • SOC2-CC7.5 CC7.5 Recovering from security incidents

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 CIS Control 16: Application Software Security

You are reading one control. How much of CIS Controls v8 have you already done?

CIS Controls v8 CIS-16.3 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of CIS Controls v8 your existing evidence covers. Hold ISO 27001:2022 and 102 of 153 CIS Controls v8 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. 240 were rejected on the ISO 27001:2022 pair alone.

Query this from an agent

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