Vulnerability › Module 8 › Lesson 1
Report Audience
Executive vs technical readers — tailor VA reports from YOUR lab work, not stranger dumps.
Visual · t18_report_audience
Audience sets depth, tone, and action items. Original Cyberlium.
Opening
The CFO needs counts and risk — the sysadmin needs plugin ID and patch KB — same lab data, two lenses.
VA reports serve different audiences: executives want risk trend, top P1 count, and remediation ETA; technical owners want CVE, affected host, proof line, and fix command; compliance wants mapping to control frameworks. Write both a one-paragraph executive summary and technical appendix from YOUR $LAB_ASSETS triage lab — never fabricate findings from unauthorized scans or paste Shodan screenshots as 'engagement evidence.' Original Cyberlium: report what you measured on owned lab assets under RoE only.
1. Executive summary
Scope sentence ($LAB_ASSETS), scan date, confirmed vs FP counts, top three P1 themes.
No exploit video links — risk language and next steps only.
Command guide
Try these commands — Executive summary
═══ TOOLS & WEBSITES ═══ Browse / read these (authorized learning only — stay in YOUR lab / program scope)
OWASP VA tools — https://owasp.org/www-community/Vulnerability_Scanning_Tools
═══ INSTALL ═══
Linux (Debian/Ubuntu):
Command — copy this
sudo apt install nmap sudo apt install python3
macOS:
Command — copy this
brew install nmap brew install python3
Windows:
Command — copy this
choco install nmap # or download https://nmap.org/download.html
Download https://python.org/downloads/
═══ LINUX / macOS ═══
Command — copy this
source "$HOME/cyberlium-lab/t18-lab.env" 2>/dev/null || LAB_HOST=127.0.0.1 nmap -sV --top-ports 15 -oG - "$LAB_HOST" | head -20 printf 'title: asset: lab evidence: severity: fix: ' > "$HOME/cyberlium-lab/t18-finding-outline.txt"
Primary tools to practice this lesson: nmap, python3. Reference sites: OWASP VA tools (https://owasp.org/www-community/Vulnerability_Scanning_Tools). Run every command in the box — install first, then the usage lines — only on YOUR lab / program scope.
2. Technical appendix
Per-finding: title, CVE, CVSS, host, status, evidence, recommendation.
Cross-reference triage workbook row IDs for traceability.
3. Scope honesty
State RoE limits: lab VLAN only, no production, no third parties.
Never imply coverage of networks you did not scan with authorization.
4. What you ship: audience outline
Executive summary bullets + technical appendix TOC + RoE scope sentence.
5. What you record before the next lesson
Report audience outline 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
Executive summary citing vulns from unauthorized internet-wide scan.
Right
Name audience needs. Next: finding structure.
Mission: audience outline
1) Write exec summary bullets for lab triage. 2) List technical appendix fields. 3) Write RoE scope sentence.
Stuck? Ask Cyberlium AI Mentor
Ask Mentor: “One-page exec max length?”
Knowledge Check
APPLY: Executive summary emphasizes:
Multiple choice
Knowledge Check
APPLY: True or False: Shodan paste counts as VA scope.
True or False
Knowledge Check
APPLY: Technical appendix includes:
Multiple choice