Nessus/OpenVAS Named
Name Nessus and OpenVAS concepts — enterprise scanners on $LAB_HOST scope, lab-safe literacy.
Visual · nessus_openvas_named
Nessus/OpenVAS named literacy. $LAB_HOST only. Original Cyberlium.
Nessus and OpenVAS are named scanner platforms — not excuses to scan networks you do not operate.
Tenable Nessus (commercial/professional tiers) and Greenbone OpenVAS (open-source stack) are widely taught VA platforms: policies, plugin feeds, schedules, and report exports. Both require license/feeds, scope imports, and analyst triage — concepts Cyberlium names on $LAB_HOST job planning without mandating production installs or stranger targets. You will NOT download crack licenses, scan internet ranges because plugins updated, or treat OpenVAS as 'free pass' on dorm LANs. Next: Scanner Lab.
1. Shared scanner concepts
Policy/template (e.g., basic network, web app), plugin feed updates, scan zone tied to scope CSV, report formats (PDF/CSV) for triage. Nessus uses.nessus policies; OpenVAS uses configs and port lists — vocabulary aligns for analysts.
On $LAB_HOST plan: policy name, target=$LAB_HOST, output=$HOME/cyberlium-lab/reports/ chmod 600.
Command guide
Try these commands — Shared scanner concepts
═══ 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: curl, nmap. Reference sites: Greenbone OpenVAS (https://www.greenbone.net/en/openvas/); Tenable Nessus (https://www.tenable.com/products/nessus); Nmap vuln scripts (https://nmap.org/nsedoc/categories/vuln.html). Run every command in the box — install first, then the usage lines — only on YOUR lab / program scope.
2. Lab-safe literacy without reckless defaults
Courses may use local OpenVAS appliance or Nessus Essentials on lab VLAN — still only $LAB_HOST in target field. 'Safe checks' does not mean 'any IP.'
Cracked enterprise feeds and pirated plugins are out — use vendor-legitimate lab installs only.
3. Reports feed Module 5+ — not exploit queues
Export lists CVE references for NVD reading — no Metasploit module required per finding. Analyst voice: verify, prioritize, assign owner on $LAB_HOST.
Ship: Nessus vs OpenVAS one-line each + planned job fields for $LAB_HOST. Next: Scanner Lab.
4. What you ship: Nessus/OpenVAS concept note for $LAB_HOST job
Name both platforms. Policy, target=$LAB_HOST, report path. No stranger scans. chmod 600.
5. What you record before the next lesson
Date. Nessus/OpenVAS concepts. Planned job for $LAB_HOST. File t18-m04-l03-nessus-openvas-named.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: Scan 0.0.0.0/0 with OpenVAS 'essentials.' Use pirated Nessus feed on dorm LAN.
- Right: Document scanner platform concepts for $LAB_HOST job plan. Next: Scanner Lab.
Mission: name scanner platforms on scope
1) One sentence each for Nessus and OpenVAS role. 2) List policy, target, report path for $LAB_HOST. 3) NEVER stranger ranges. Optional local install only if brief provides lab appliance.
Stuck? Ask Cyberlium AI Mentor
Ask Mentor about policy templates — not targets for café Wi-Fi.
APPLY: Nessus and OpenVAS are:
APPLY: True or False: OpenVAS 'free' status authorizes dorm LAN scanning.
APPLY: Scanner report CVE references feed: