A row was removed from the scan report.
Operations / 09
Vulnerability lifecycle
Connect scan findings to risk, remediation and a same-scope retest.
This work is currently open on this device. Sign in to save it and continue on another device.
Sign inA severity score alone does not determine business priority. Combine asset criticality, exposure, exploitation evidence and existing controls. CISA KEV informs prioritization of exploited vulnerabilities; US federal deadlines do not automatically apply to every organization. This pack extends the scanning guide into finding management.
Map the process
0 / 4 steps reviewed.Step 1 / 4
Validate the finding
Record asset, version, scan time and authorization. Support false-positive decisions with evidence. Distinguish authenticated scan coverage from external observation.
Expected evidence
Asset-bound validation
One control, three perspectives
Did remediation work?
Retest the same scope.
Before/after resultEvaluate evidence
Claim: The vulnerability was remediated.
What evidence would you request before closing this claim?
Decision desk
A medium-score finding affects a critical exposed asset and appears in KEV.
First decision?
Worked example
This record is fictional. Do not treat sample results as evidence for your own work.
| Asset | Finding | Business impact | Priority rationale | Owner / action | Retest |
|---|---|---|---|---|---|
| TEST-WEB-01 | Fictional version finding | Customer portal | Exposure + critical service | Application owner / patch | Same permission and scope pending |
Closure checklist
0 / 4Checks on this screen last for this session only; they do not create closure evidence or compliance approval. Keep organizational records in the downloaded workpaper.
Take it to work
Files in the selected language. The workbook includes blank records, a worked example and a checklist.
Keep learning
Explore related Academy coursesSources and edition
Checked: 2026-10-21 · Edition 2026.10