Vulnerability Management

A four-tier practitioner course — scan, triage, prioritise, ticket, verify and report in an enterprise-style VM console, graded against a hidden truth table.

About 19 hours · 26 modules · 43 labs · certificate on completion · Security operations

For: analyst, engineer

Skills: vulnerability-management, cvss, prioritisation, remediation-tracking

What the course covers

  1. 1. The VM lifecycle and the role — Follow one finding from discovery to verified closure and learn who owns each step. (2 labs)
  2. 2. Asset discovery and inventory — Find what is really on the network, reconcile it with the CMDB, and flag what nobody owns. (2 labs)
  3. 3. CVE, CVSS, CWE, CPE and the NVD — Read a CVE record, decode a CVSS vector, and map a CPE to installed software. (2 labs)
  4. 4. Patching basics on Linux and Windows — Read installed versions, update history and pending reboots on Linux and Windows hosts. (2 labs)
  5. 5. First scans — Run Nmap and a network vulnerability scan against a segment, and read the report. (2 labs)
  6. 6. Authenticated scanning and agents — Compare credentialed, uncredentialed and agent views of one host, and fix a failed credentialed scan. (2 labs)
  7. 7. Triage and false positives — Confirm or reject findings with evidence from the host, and merge duplicates. (2 labs)
  8. 8. Risk-based prioritization — Rank a large backlog using CVSS, EPSS, KEV, exposure and asset criticality, and defend the order. (2 labs)
  9. 9. Remediation tickets and SLAs — Write tickets owners can act on, assign the right owner, set the due date, and handle pushback. (2 labs)
  10. 10. Verification and rescans — Prove fixes with rescans and host evidence, and reopen tickets that only look resolved. (2 labs)
  11. 11. Reporting and KPIs — Compute SLA compliance, remediation rate, coverage, recurrence and overdue count, and write the weekly note. (2 labs)
  12. 12. Patch management and change control — Plan a patch around maintenance windows, dependencies and CAB approval, and write a change request that passes. (2 labs)
  13. 13. Configuration assessment — Assess hosts against hardening profiles with OpenSCAP and Lynis, and apply only the fixes that are safe. (2 labs)
  14. 14. Cloud and container exposure — Scan images with Trivy and triage cloud findings, prioritizing exposed, runtime-loaded packages. (2 labs)
  15. 15. Application dependencies and SBOM — Generate an SBOM, scan it, trace transitive dependencies, and ticket the fix in the right place. (2 labs)
  16. 16. Exceptions and risk acceptance — Judge exception requests against policy, require real compensating controls, and set expiries. (2 labs)
  17. 17. Emergency response to an exploited vulnerability — When a KEV entry drops mid-shift, find the exposure fast with an incomplete inventory, work with the SOC, and run an emergency change. (2 labs)
  18. 18. Automation and APIs — Script the morning routine: pull findings, join CMDB and KEV, and open tickets without creating duplicates. (2 labs)
  19. 19. Scan program engineering — Design scan policies, schedules and credentials that reach coverage targets, and keep the scanners healthy. (2 labs)
  20. 20. Metrics, risk and executive communication — Turn quarterly data into a true exposure trend, name the misleading metric, and brief the CISO in five minutes. (2 labs)
  21. 21. Compliance and audit evidence — Map vulnerability work to PCI DSS, ISO/IEC 27001, NIST SP 800-40 and SOC 2, and assemble a traceable evidence pack. (2 labs)
  22. 22. Capstone — Take over a broken vulnerability management program for 30 days and leave it measurably better. (1 lab)
  23. 23. Web application and API vulnerabilities — Scan web applications and APIs with the right coverage, triage findings by replaying them, and hand developers fixes they can merge.
  24. 24. Network edge, OT and IoT — Manage vulnerabilities on firewalls, VPN gateways and appliances, and on operational technology that must not be probed or stopped.
  25. 25. Attack surface, exposure management and testers — Find the internet-facing assets nobody listed, fix cheap exposures fast, think in attack paths, and bring penetration test findings into the same process.
  26. 26. Influence, communication and your career — Get findings fixed by people you do not manage, negotiate dates without giving away the risk, write messages that get acted on, and turn this course into a portfolio, interview answers and a first 90 days.

Free with an account.

Start for free