CIS Controls v8 CIS-16.6: Establish and Maintain a Severity Rating System and Process for Application Vulnerabilities
Set up and keep a system and process for rating the severity of application vulnerabilities, so the order in which found vulnerabilities are fixed can be prioritised. The process sets a minimum security bar that code or applications must meet before release. Severity ratings give a structured way to triage vulnerabilities, strengthen risk management and help make sure the worst bugs are fixed first. Revisit the system and process each year.
Maintained by Gerard Blokdyk·Verified against the published standard ·Control text last updated
What else in your programme already covers this
This control maps to 35 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-CSF-GV.RM-06 A standardized method for calculating, documenting, categorizing, and prioritizing cybersecurity risks is established and communicated
NIST-CSF-ID.RA-01 Vulnerabilities in assets are identified, validated, and recorded
NIST-CSF-ID.RA-04 Potential impacts and likelihoods of threats exploiting vulnerabilities are identified and recorded
NIST-CSF-ID.RA-05 Threats, vulnerabilities, likelihoods, and impacts are used to understand inherent risk and inform risk response prioritization
You are reading one control. How much of CIS Controls v8 have you already done?
CIS Controls v8 CIS-16.6 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.