BaselineWatch
Desk
Your fleet and your work Fleetyour releases and the hardware they run onTriagewhat needs a decisionWatchlistthe products and platforms you runSaved searchesthe lists you come back to
This instance Sourceswhat is read, how often, under what termsDigestthe daily or weekly summary, and alerts
How it is drawn Appearancethe look and the colour schemeBrandingthe mark this instance wears
Owner sign-in

VDR-CSO-RES Vulnerability Response

FedRAMP Consolidated Rules (2026) 2026.10.13.01 against 2026.10.08.01
All changes in this version
modified VDR: Vulnerability Detection and Response
Why it changed, in the publisher's words

2026-10-13: Updated control mappings: added au-5.2, ir-4.11, ir-9.3, ra-7, si-2, si-3.

https://github.com/FedRAMP/rules/commits/main/fedramp-consolidated-rules.json

Title

Vulnerability Response

Control

Providers MUST systematically, persistently, and promptly track, evaluate, monitor, mitigate, remediate, assess exploitation of, report, and otherwise manage all detected vulnerabilities within their cloud service offering; this process is called vulnerability response.

Discussion

If it is not possible to fully mitigate vulnerabilities or remediate vulnerabilities, providers SHOULD instead partially mitigate vulnerabilities promptly, progressively, and persistently.
FedRAMP does not use the terms "mitigation" and "remediation" interchangeably. Mitigation is the process of reducing the risk and impact of a vulnerability through partial mitigation and even full mitigation; remediation is the process of entirely eliminating the vulnerability. A fully mitigated vulnerability will still exist (with negligible risk) until it has been remediated. This separation is based on the plain language definitions of these words.
Please refer to FedRAMP Definitions for strict interpretation in the FedRAMP context.

Related controls changed

Before · 2026.10.08.01

After · 2026.10.13.01

au-5.2, ir-4.11, ir-9.3, ra-7, si-2, si-3