Performing Vulnerability Scanning With Nessus
Overview
Cybersecurity skill for performing vulnerability scanning with nessus. Follows industry best practices and security standards.
When to Use
Trigger phrases:
"performing vulnerability scanning with nessus"
"Performs authenticated and unauthenticated vulnerability scanning using Tenable "
Conducting initial vulnerability assessment during the reconnaissance phase of a penetration test
Performing periodic vulnerability scans to maintain compliance with PCI-DSS (requirement 11.2), HIPAA, or SOC 2 standards
Validating that remediation efforts have successfully addressed previously identified vulnerabilities
Establishing a baseline of known vulnerabilities before targeted manual exploitation
Auditing patch compliance and configuration drift across server and workstation fleets
Do not use as a substitute for manual penetration testing, against systems without written authorization, or against fragile systems (medical devices, legacy SCADA) where scanning may cause service disruption.
When NOT to Use
- When you lack proper authorization for testing
- For production systems without change management
- When the task requires legal or compliance expertise beyond technical scope
Prerequisites
- Tenable Nessus Professional or Nessus Expert with current plugin updates (plugins should be less than 24 hours old)
- Network connectivity to all target hosts on all ports (no firewall restrictions between scanner and targets)
- Administrative credentials for authenticated scanning (domain admin or local admin for Windows, root/sudo for Linux, SNMP community strings for network devices)
- Target IP ranges and hostnames documented in the scope agreement
- Change management approval for scanning during authorized windows
Workflow
# Example: IOC detection
import re
IOC_PATTERNS = {
"ip": r"\b(?:\d{1,3}\.){3}\d{1,3}\b",
"domain": r"\b[a-z0-9-]+\.[a-z]{2,}\b",
"hash_md5": r"\b[a-f0-9]{32}\b",
"hash_sha256": r"\b[a-f0-9]{64}\b",
}
def extract_iocs(text: str) -> dict:
return {k: re.findall(v, text) for k, v in IOC_PATTERNS.items()}
- Plan Operations — Define objectives, scope, and success criteria for vulnerability scanning operations.
- Prepare Environment — Set up tools, access, and data sources required for vulnerability scanning.
- Execute Core Workflow — Use nessus to perform vulnerability scanning operations following established procedures.
- Validate Results — Verify that results meet quality standards and objectives.
- Report Findings — Document results, observations, and recommendations.
- Follow Up — Track remediation actions and verify fixes where applicable.
Tools
- nessus — Primary tool for this skill
- Analysis Platform — Data processing and visualization
- Collaboration Tools — Team coordination and knowledge sharing
Process
- Reconnaissance — Gather target information, identify attack surface, enumerate services
- Analysis/Exploitation — Execute the technique, analyze results, document findings
- Reporting — Document IOCs, write findings, provide remediation recommendations
Verification
Anti-Rationalization Table
| Rationalization |
Reality |
| "We are too small to be targeted" |
Automated attacks target everyone. Size does not matter. |
| "Security slows us down" |
A breach slows you down 100x more. Build security in from the start. |
| "We will fix it after launch" |
Vulnerabilities in production are exploited within hours. Fix before deploy. |
1---2name: performing-vulnerability-scanning-with-nessus3description: Use when performing authenticated and unauthenticated vulnerability scanning4 using Tenable Nessus to identify known vulnerabilities, misconfigurations, default5 credentials, and missing patches across network infrastructure, servers, and applications.6 The scanner correlates findings with CVE databases and CVSS scores to produce prioritized7 remediation guidance. Activates for requests involving vulnerability scanning, Nessus8 assessment, patch compliance checking, or automated vulnerability dete...9domain: cybersecurity10tags:11- vulnerability-scanning12- Nessus13- CVE14- patch-management15- Tenable16subdomain: penetration-testing17version: 1.0.018author: oyi7719license: Apache-2.020nist_csf:21- ID.RA-0122- ID.RA-0623- GV.OV-0224- DE.AE-0725category: cybersecurity26metadata:27 source: https://skillmd.com/skills/oyi77/performing-vulnerability-scanning-with-nessus28---2930# Performing Vulnerability Scanning With Nessus3132## Overview3334Cybersecurity skill for performing vulnerability scanning with nessus. Follows industry best practices and security standards.3536## When to Use37**Trigger phrases:**38- "performing vulnerability scanning with nessus"39- "Performs authenticated and unauthenticated vulnerability scanning using Tenable "404142- Conducting initial vulnerability assessment during the reconnaissance phase of a penetration test43- Performing periodic vulnerability scans to maintain compliance with PCI-DSS (requirement 11.2), HIPAA, or SOC 2 standards44- Validating that remediation efforts have successfully addressed previously identified vulnerabilities45- Establishing a baseline of known vulnerabilities before targeted manual exploitation46- Auditing patch compliance and configuration drift across server and workstation fleets4748**Do not use** as a substitute for manual penetration testing, against systems without written authorization, or against fragile systems (medical devices, legacy SCADA) where scanning may cause service disruption.495051## When NOT to Use5253- When you lack proper authorization for testing54- For production systems without change management55- When the task requires legal or compliance expertise beyond technical scope565758## Prerequisites5960- Tenable Nessus Professional or Nessus Expert with current plugin updates (plugins should be less than 24 hours old)61- Network connectivity to all target hosts on all ports (no firewall restrictions between scanner and targets)62- Administrative credentials for authenticated scanning (domain admin or local admin for Windows, root/sudo for Linux, SNMP community strings for network devices)63- Target IP ranges and hostnames documented in the scope agreement64- Change management approval for scanning during authorized windows6566## Workflow6768```python69# Example: IOC detection70import re7172IOC_PATTERNS = {73 "ip": r"\b(?:\d{1,3}\.){3}\d{1,3}\b",74 "domain": r"\b[a-z0-9-]+\.[a-z]{2,}\b",75 "hash_md5": r"\b[a-f0-9]{32}\b",76 "hash_sha256": r"\b[a-f0-9]{64}\b",77}7879def extract_iocs(text: str) -> dict:80 return {k: re.findall(v, text) for k, v in IOC_PATTERNS.items()}81```82831. **Plan Operations** — Define objectives, scope, and success criteria for vulnerability scanning operations.842. **Prepare Environment** — Set up tools, access, and data sources required for vulnerability scanning.853. **Execute Core Workflow** — Use nessus to perform vulnerability scanning operations following established procedures.864. **Validate Results** — Verify that results meet quality standards and objectives.875. **Report Findings** — Document results, observations, and recommendations.886. **Follow Up** — Track remediation actions and verify fixes where applicable.8990## Tools9192- **nessus** — Primary tool for this skill93- **Analysis Platform** — Data processing and visualization94- **Collaboration Tools** — Team coordination and knowledge sharing959697## Process98991. **Reconnaissance** — Gather target information, identify attack surface, enumerate services1001. **Analysis/Exploitation** — Execute the technique, analyze results, document findings1011. **Reporting** — Document IOCs, write findings, provide remediation recommendations102103## Verification104105- [ ] All vulnerability scanning procedures executed completely and documented106- [ ] Findings validated against multiple data sources107- [ ] False positives identified and filtered108- [ ] Results documented with evidence and timestamps109- [ ] Recommendations provided with risk-based prioritization110111## Anti-Rationalization Table112113| Rationalization | Reality |114|---|---|115| "We are too small to be targeted" | Automated attacks target everyone. Size does not matter. |116| "Security slows us down" | A breach slows you down 100x more. Build security in from the start. |117| "We will fix it after launch" | Vulnerabilities in production are exploited within hours. Fix before deploy. |