Vulnerability Management Lab with Tenable

Practical, cloud-hosted lab to internalize the vulnerability management lifecycle — baseline scanning, intentional misconfiguration, remediation, and validation — using Tenable's cloud VM platform and Azure infrastructure.

1. 01Cloud environment: provisioned Microsoft Azure VMs — one hosting the Tenable Scan Engine, another as the Windows 10 Scan Target. Interfaced with the Tenable Vulnerability Management cloud console.
2. 02Scan configuration: authored a credentialed Tenable scan combining a basic vulnerability policy with DISA Windows 10 STIG v3r2 compliance checks.
3. 03Baseline (Scan 1): established a documented vulnerability + compliance baseline. Focus STIGs — WN10-AU-000505 (Security Event Log size), WN10-SO-000025 (Rename Guest Account), WN10-SO-000010 (Disable Guest Account).
4. 04Intentional vulnerability (Scan 2): installed an outdated Firefox v110 and enabled the Guest Account (forcing WN10-SO-000010 to fail). Rescanned and confirmed Tenable detected both changes.
5. 05Remediation (Scans 3–4): uninstalled Firefox, modified the registry to increase Security Event Log size, disabled and renamed the Guest Account, and fully patched Windows. Two rescans confirmed the vulnerability trend dropping.

• Four-scan workflow that clearly maps a vulnerability from baseline → introduction → partial mitigation → full remediation, with annotated screenshots at every stage in the repo.
• Hands-on operation of Tenable's cloud VM console, credentialed scanning, and DISA Windows 10 STIG v3r2 compliance checking.
• Reproducible, evidence-first process — the same shape of work I apply to real vulnerability management at LOG(N) Pacific and UF Health.

“The lab isn't the point — the workflow is. Scan, remediate, verify, evidence. Repeat until the baseline is boring.”