Vulnerability › Module 9 › Lesson 1
Patch Compensate Accept
Remediation options on YOUR lab findings — patch first, compensate when needed, accept with ticket.
Visual · t18_patch_compensate_accept
Every open finding gets patch, compensate, or accept — documented. Original Cyberlium.
Opening
Accepting risk without a ticket is not a strategy — it is how lab VMs become lesson plans for attackers.
Remediation paths for confirmed findings on $LAB_ASSETS: Patch (apply vendor fix), Compensate (WAF rule, disable service, segmentation until patch), Accept (document risk with approver and review date — lab scenario only). Prefer patch when fix available and testable on YOUR VM. Compensating controls must be specific. Accept is last resort with expiry — not 'ignore scanner forever.' Never plan remediation for stranger infrastructure you scanned without authorization. No exploit validation step — retest with scan or safe version check.
1. Patch path
Identify fixed version from advisory; test on lab clone; schedule maintenance window.
Record KB/advisory link and rollback note for lab VM snapshot.
Command guide
Try these commands — Patch path
═══ TOOLS & WEBSITES ═══ Browse / read these (authorized learning only — stay in YOUR lab / program scope)
Remediation planning — https://www.cisa.gov/topics/cybersecurity-best-practices Patch management — https://nvd.nist.gov
═══ INSTALL ═══
Linux (Debian/Ubuntu):
Command — copy this
sudo apt install python3 sudo apt install curl
macOS:
Command — copy this
brew install python3
Windows: Download https://python.org/downloads/ Built-in (PowerShell: Invoke-WebRequest)
═══ LINUX / macOS ═══
Command — copy this
python3 -c "print('Treatment: patch | compensate | accept — with owner + due date')"
curl -sS https://nvd.nist.gov/vuln/search | head -3Primary tools to practice this lesson: python3, curl. Reference sites: Remediation planning (https://www.cisa.gov/topics/cybersecurity-best-practices); Patch management (https://nvd.nist.gov). Run every command in the box — install first, then the usage lines — only on YOUR lab / program scope.
2. Compensate path
Temporary: firewall rule, disable vulnerable module, remove exposure.
Document compensating control ID and retest date — not permanent silence.
3. Accept path
Lab only: business justification, approver name placeholder, review date 90 days.
NEVER accept Critical on internet-facing production you do not own — out of scope.
4. What you ship: remediation option matrix
Patch/Compensate/Accept definitions + one example each from lab report.
5. What you record before the next lesson
Remediation matrix path.
6. Wrong vs right: stranger nets vs YOUR lab assets
Worked failure — same MSF word, opposite target. Right never needs a café Wi-Fi or classmate laptop.
Wrong
Mark all employer prod findings Accepted without ticket or authority.
Right
Name three remediation paths. Next: owners and dates.
Mission: remediation matrix
1) Define Patch Compensate Accept. 2) Assign path to three lab findings. 3) Write NEVER remediate unauthorized targets.
Stuck? Ask Cyberlium AI Mentor
Ask Mentor: “When compensate beats emergency patch?”
Knowledge Check
APPLY: Preferred remediation:
Multiple choice
Knowledge Check
APPLY: True or False: Accept without ticket is fine.
True or False
Knowledge Check
APPLY: Compensating control:
Multiple choice