Verify Safely
Confirm or reject findings on YOUR $LAB_ASSETS — version checks and banners, no exploit PoCs.
Visual · t18_verify_safely
Lab: safe verification on owned hosts only. Original Cyberlium.
Verify with ssh and package queries — not with exploit modules aimed at someone else's server.
Safe verification on $LAB_ASSETS you own: read installed package version (dpkg -l, rpm -q), check listening port with local netstat/ss, review config file cited by plugin, compare to vendor advisory fixed version. For web findings, curl -I headers on YOUR lab URL only — no injection payloads on stranger sites. Mark finding Confirmed, False Positive, or Needs Patch with one evidence line each. chmod 600 notes under $HOME/cyberlium-lab. NEVER use exploit PoCs, Metasploit confirm modules, or credential brute force on unauthorized targets to 'verify' scanner rows.
1. Safe checks
Package manager version vs advisory — primary FP killer on lab Linux VMs.
Service banner and config path read — document command output redacted.
Command guide
Try these commands — Safe checks
═══ LINUX / KALI (Penetration Testing & Service Audit) ═══
Port scan and service banner grabbing against authorized target
Command — copy this
nmap -sV -sC -Pn -T4 -p 21,22,80,443,445,3389 ${LAB_HOST:-127.0.0.1}Enumerate web directories and hidden endpoints
Command — copy this
gobuster dir -u http://${LAB_HOST:-127.0.0.1} -w /usr/share/wordlists/dirb/common.txt -q -t 20 2>/dev/null || head -5 /etc/hostsMetasploit framework module inspection (Safe lab syntax)
Command — copy this
msfconsole -q -x "use auxiliary/scanner/portscan/tcp; set RHOSTS 127.0.0.1; set PORTS 80,443; run; exit" 2>/dev/null || echo "Run in Kali msfconsole"
═══ WINDOWS (Audit Target) ═══ Enumerate open listening ports with process mappings
Command — copy this
netstat -ano | findstr /i "LISTENING"
Primary tools to practice this lesson: python3, jq. Reference sites: False positives (https://docs.tenable.com/); Greenbone triage (https://docs.greenbone.net/). Run every command in the box — install first, then the usage lines — only on YOUR lab / program scope.
2. Status labels
Confirmed: version vulnerable and exposed per RoE threat path.
False Positive: version patched or service not present. Needs Patch: confirmed, fix pending.
3. Hard refusal
No exploit PoCs on any host outside $LAB_ASSETS inventory.
No 'quick nmap' on classmate IP because plugin said so — stay in RoE.
4. What you ship: verification table
Five findings with status + evidence command/output summary — chmod 600.
5. What you record before the next lesson
Verify safely table 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: Run exploit module against café POS system to confirm Critical plugin.
- Right: Safe verification on $LAB_ASSETS. Next: risk priority.
Mission: verify five findings
1) Pick five scan rows from $LAB_ASSETS. 2) Safe-check each; assign status. 3) Write NEVER exploit PoC verification.
Stuck? Ask Cyberlium AI Mentor
Ask Mentor: “When banner check enough vs patch test?”
APPLY: Safe verification includes:
APPLY: True or False: Metasploit confirm on unauthorized host is VA lab.
APPLY: Status False Positive needs:
Risk Priority
Part of Vulnerability Assessment — False Positives and Triage.
Triage Lab
Part of Vulnerability Assessment — False Positives and Triage.
Quiz — False Positives and Triage
Part of Vulnerability Assessment — False Positives and Triage.