Lifecycle
- Maintain asset and service visibility
- Discover vulnerabilities through multiple sources
- Validate findings and exposure
- Prioritize using exploitability, reachability, business consequence, and control context
- Remediate, mitigate, accept, or remove exposure
- Verify results and monitor recurrence
Why severity alone is insufficient
A high technical severity on an isolated test system may be less urgent than a moderately rated weakness on an internet-facing identity service. Context changes priority.
Operational dependency
Remediation depends on ownership, testing, change windows, business continuity, vendor support, and evidence. A scanner report by itself is not a vulnerability-management program.
Measure the system
Useful measures examine coverage, age, recurrence, exploitable exposure, failed remediation, exceptions, and the time between discovery and verified risk reduction.
BMC v0.2.2 cornerstone expansion
Start analysis of Vulnerability Management with the mission or business outcome, then identify assets, identities, data, trust boundaries, dependencies, expected behavior, and credible failure or abuse cases.
Translate those observations into preventive, detective, responsive, and recovery controls. A mature explanation states not only what the concept is, but also how a practitioner demonstrates that it is working under normal, abnormal, and recovery conditions.
Evidence of effective implementation
- Documented ownership, scope, decision criteria, and permitted exceptions.
- Configuration or architectural evidence tied to a clear control objective.
- Operational telemetry showing expected and unexpected behavior.
- Testing that covers normal use, abuse cases, failure, rollback, and recovery.
- Exceptions that are approved, time bounded, monitored, and revisited.
- Lessons learned that result in updated designs, procedures, detections, or training.
Questions for learners
- Which security properties and business outcomes does Vulnerability Management support?
- What assumptions must remain true for the control or process to work safely?
- What could an attacker, insider, failure, or design error do at each trust boundary?
- Which evidence would prove that controls work continuously rather than only on paper?
- How would the organization respond, restore service, and re-establish trust after failure?
Certification relevance
This subject appears in or supports the following certification bodies of knowledge: