Vulnerability › Module 2 › Lesson 2
Pentest Contrast
Pentest proves exploit paths under tight scope — contrast with VA breadth on $LAB_HOST literacy.
Visual · pentest_contrast
Pentest contrast literacy. $LAB_HOST only. Original Cyberlium.
Opening
Pentest asks 'can an attacker get in?' VA asks 'what is wrong and how urgent?' — both need written scope.
Penetration testing simulates adversaries to validate controls: chained exploits, lateral movement, data access proof — under narrow scope and strict RoE. VA casts a wide net for misconfigs and CVEs without necessarily proving exploitation. Cyberlium teaches the contrast in vocabulary — Topic 19 covers pentest; here you name differences on $LAB_HOST planning notes only. You will NOT run Metasploit on classmate VMs 'because pentest is next,' or confuse VA scanner output with pentest reports. Next: When Which.
1. Depth vs breadth
VA: many assets, automated scans, CVE mapping, triage at scale. Pentest: fewer critical paths, manual chaining, evidence of impact, often after VA backlog is understood.
On $LAB_HOST notes, write two columns: VA finds 'Apache outdated' — pentest might prove 'RCE on lab web tier under scope.'
Command guide
Try these commands — Depth vs breadth
═══ TOOLS & WEBSITES ═══ Browse / read these (authorized learning only — stay in YOUR lab / program scope)
Tenable Nessus — https://www.tenable.com/products/nessus (authorized targets only) Greenbone GVM — https://www.greenbone.net/en/ (open-source VA stack)
═══ INSTALL ═══
Linux (Debian/Ubuntu):
Command — copy this
sudo apt install python3 sudo apt install nmap
macOS:
Command — copy this
brew install python3 brew install nmap
Windows: Download https://python.org/downloads/
Command — copy this
choco install nmap # or download https://nmap.org/download.html
═══ LINUX / macOS ═══
Command — copy this
python3 -c "print('VA: breadth + compliance; Pentest: exploit chain proof — both need RoE')"
source "$HOME/cyberlium-lab/t18-lab.env"; nmap -Pn -sn "$LAB_HOST"Primary tools to practice this lesson: python3, nmap. Reference sites: Tenable Nessus (https://www.tenable.com/products/nessus); Greenbone GVM (https://www.greenbone.net/en/). Run every command in the box — install first, then the usage lines — only on YOUR lab / program scope.
2. Different audiences and artifacts
VA reports feed patch teams and CMDB owners with prioritized lists. Pentest reports feed executives and architects with attack narratives and control gaps — both require evidence hygiene.
Using pentest tools on stranger production without engagement is illegal — not contrast homework.
3. Cyberlium boundary
Topic 18 stays VA: scanners, CVE, CVSS, triage, reporting on $LAB_HOST. Exploit PoCs on strangers stay out — even when pentest is named for contrast.
Ship: VA vs pentest comparison table (3 rows). Next: When Which.
4. What you ship: VA vs pentest contrast table
Three-row table: goal, depth, typical output. $LAB_HOST planning only. chmod 600.
5. What you record before the next lesson
Date. Contrast table. No exploit runs on strangers. File t18-m02-l02-pentest-contrast.txt chmod 600.
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 modules on café Wi-Fi 'to contrast VA.' Label any nmap sweep as pentest.
Right
Document contrast on paper for $LAB_HOST scope. Next: When Which.
Mission: contrast VA and pentest on paper
1) Write goal/depth/output for VA in one row. 2) Same for pentest in one row. 3) Note both require written RoE. Never exploit strangers for contrast.
Stuck? Ask Cyberlium AI Mentor
VA finds the door unlocked; pentest walks through — under signed scope only.
Knowledge Check
APPLY: Pentest primarily differs from VA by:
Multiple choice
Knowledge Check
APPLY: True or False: Running Metasploit on classmate VMs is acceptable VA contrast homework.
True or False
Knowledge Check
APPLY: A VA output typically includes:
Multiple choice