CYBERJA · PRACTICE GUIDE

Vulnerability & Remediation Management Hub

Use synthetic evidence. Enter your own observations, then compare them with the worked direction below.

Open the tool · Open this file in a browser or print it to PDF.

Practice scenario

A scanner reports a CVE on a public customer portal.

Record the assessment

Open Connected Workspaces and select Vulnerability management. Use the assessment form to work through these prompts.

CVE / scanner reference — Record the CVE identifier or scanner finding ID, affected product, version and observation date. Confirm the finding applies.

CVSS severity score (0–10) — Use the score and version from a reliable source. Severity alone does not determine business priority.

Exposure — State how an attacker could reach the affected service; do not assume every vulnerability is remotely exploitable.

Known exploitation evidence — Check CISA KEV or vendor advisories. A No value means no evidence recorded, not proof that exploitation is impossible.

Business criticality — Use process dependencies and service impact, rather than the system name alone.

Finding applicability and validation — Document the affected version, scan date, evidence source and checks that rule out a false positive. Avoid intrusive testing without authorisation.

Patch / mitigation / rollback plan — Record the vendor fix, prerequisites, change window, backup/rollback plan, business owner and interim protections.

Retest method and result — Describe the test that will confirm the fix and attach a dated result when performed. Proposed tests are not verification.

Worked direction

Compare the installed build against a vendor advisory and document exposure, ownership, fix deadline and post-change rescan.

Review your work

Confirm the asset and affected version.

Check known exploitation and business exposure.

Plan patching or a justified interim mitigation.

Retest and record evidence before closing the action.

Evidence and handoff

Capture a mock evidence reference and its limitations. Record the finding, accountable owner and next review. Where a material risk remains, record it in the shared risk register and schedule a follow-up.

Reference: CISA Known Exploited Vulnerabilities (KEV) catalogue — https://www.cisa.gov/known-exploited-vulnerabilities-catalog

Continue with the community

Compare your practice approach with other CyberJA Connect members.

Join CyberJA Connect ↗