scanning-infrastructure-with-nessus
Tenable Nessus is the industry-leading vulnerability scanner used to
v1.02 instalações+2 em 7 dias36,3 mil EstrelasApache-2.0sincronizado há 12 horas
Instalar
Ainda não tem a CLI da NotHoly? Instale primeiro.
$ curl -fsSL https://notholy.com/install.sh | sh$ notholy skills install mukul975/scanning-infrastructure-with-nessusGrava em ~/.notholy/skills depois de conferir a assinatura e o SHA-256.
AssinaturaAssinado, ed25519
Pacote1a354dce…8c7b79f6
1a354dce6212…6f878c7b79f68 arquivos · 17.3 KBVarreduraMédio4 achados
- command.persistenceSKILL.md:76
- Script executável junto com a skillscripts/agent.py
- Script executável junto com a skillscripts/process.py
Fontegithub.com/mukul975/Anthropic-Cybersecurity-Skills/tree/main/skills/scanning-infrastructure-with-nessus@54a7988
Este item ainda não foi escrito no seu idioma, então aparece em English.
Nesta página
Overview
Tenable Nessus is the industry-leading vulnerability scanner used to identify security weaknesses across network infrastructure including servers, workstations, network devices, and operating systems. This skill covers configuring scan policies, running authenticated and unauthenticated scans, interpreting results, and integrating Nessus into continuous vulnerability management workflows.
When to Use
- When conducting security assessments that involve scanning infrastructure with nessus
- When following incident response procedures for related security events
- When performing scheduled security testing or auditing activities
- When validating security controls through hands-on testing
Prerequisites
- Nessus Professional or Essentials license installed and activated
- Network access to target systems (firewall rules allowing scanner IP)
- Administrative credentials for authenticated scanning
- Understanding of TCP/IP networking and common services
- Written authorization for scanning target environments
Core Concepts
Nessus Architecture
Nessus operates as a client-server application where the Nessus scanner engine runs as a service (nessusd) on the host system. It uses a plugin-based architecture with over 200,000 plugins updated weekly by Tenable's research team. Each plugin tests for a specific vulnerability, misconfiguration, or compliance check.
Scan Types
- Host Discovery - Identifies live hosts using ICMP, TCP, UDP, and ARP
- Basic Network Scan - Default policy covering common vulnerabilities
- Advanced Scan - Custom policy with granular plugin selection
- Credentialed Patch Audit - Authenticated scan checking installed patches
- Web Application Tests - Scans for web-specific vulnerabilities
- Compliance Audit - Checks against CIS, DISA STIG, PCI DSS benchmarks
Plugin Families
Nessus organizes plugins into families including:
- Operating Systems: Windows, Linux, macOS, Solaris
- Network Devices: Cisco, Juniper, Palo Alto, Fortinet
- Web Servers: Apache, Nginx, IIS, Tomcat
- Databases: Oracle, MySQL, PostgreSQL, MSSQL
- Services: DNS, SMTP, FTP, SSH, SNMP
Workflow
Step 1: Initial Configuration
# Start Nessus service
sudo systemctl start nessusd
sudo systemctl enable nessusd
# CLI management with nessuscli
/opt/nessus/sbin/nessuscli update --all
/opt/nessus/sbin/nessuscli fix --list
# Verify plugin count
/opt/nessus/sbin/nessuscli update --plugins-onlyStep 2: Create Scan Policy
Configure a custom scan policy through the Nessus web UI at https://localhost:8834:
- Navigate to Policies > New Policy > Advanced Scan
- Configure General settings: name, description, targets
- Set Discovery settings:
- Host Discovery: Ping methods (ICMP, TCP SYN on ports 22,80,443)
- Port Scanning: SYN scan on common ports or all 65535 ports
- Service Discovery: Probe all ports for services
- Configure Assessment settings:
- Accuracy: Override normal accuracy (reduce false positives)
- Web Applications: Enable if scanning web servers
- Select Plugin families relevant to target environment
Step 3: Configure Credentials
For authenticated scanning, configure credentials under the Credentials tab:
- SSH: Username/password or SSH key pair
- Windows: Domain credentials via SMB, WMI
- SNMP: Community strings (v1/v2c) or USM credentials (v3)
- Database: Oracle, MySQL, PostgreSQL connection strings
- VMware: vCenter or ESXi credentials
Step 4: Run the Scan
# Using Nessus REST API via curl
# Authenticate and get token
curl -k -X POST https://localhost:8834/session \
-d '{"username":"admin","password":"password"}' \
-H "Content-Type: application/json"
# Create scan
curl -k -X POST https://localhost:8834/scans \
-H "X-Cookie: token=<TOKEN>" \
-H "Content-Type: application/json" \
-d '{
"uuid": "<TEMPLATE_UUID>",
"settings": {
"name": "Infrastructure Scan Q1",
"text_targets": "192.168.1.0/24",
"enabled": true,
"launch": "ON_DEMAND"
}
}'
# Launch scan
curl -k -X POST https://localhost:8834/scans/<SCAN_ID>/launch \
-H "X-Cookie: token=<TOKEN>"
# Check scan status
curl -k -X GET https://localhost:8834/scans/<SCAN_ID> \
-H "X-Cookie: token=<TOKEN>"Step 5: Analyze Results
Nessus categorizes findings by severity:
- Critical (CVSS 9.0-10.0): Immediate remediation required
- High (CVSS 7.0-8.9): Remediate within 7-14 days
- Medium (CVSS 4.0-6.9): Remediate within 30 days
- Low (CVSS 0.1-3.9): Remediate during next maintenance window
- Informational: No immediate action required
Step 6: Export and Report
# Export via REST API
curl -k -X POST "https://localhost:8834/scans/<SCAN_ID>/export" \
-H "X-Cookie: token=<TOKEN>" \
-H "Content-Type: application/json" \
-d '{"format":"nessus"}'
# Supported formats: nessus (XML), csv, html, pdfBest Practices
- Schedule scans during maintenance windows to minimize production impact
- Use authenticated scanning for 45-60% more vulnerability detection
- Exclude fragile systems (medical devices, legacy SCADA) from aggressive scans
- Maintain separate scan policies for different network segments
- Update plugins before every scan to catch recently disclosed CVEs
- Validate critical findings manually before escalating to remediation teams
- Implement scan result trending to track remediation progress over time
- Store scan results in Tenable.sc or Tenable.io for centralized management
Common Pitfalls
- Running unauthenticated scans only (misses 45-60% of vulnerabilities)
- Scanning without written authorization (legal and ethical violations)
- Ignoring scan performance impact on production systems
- Failing to tune plugins leading to excessive false positives
- Not validating scanner network connectivity before launching scans
- Using default scan policies without customization for the environment
Related Skills
- performing-authenticated-vulnerability-scan
- prioritizing-vulnerabilities-with-cvss-scoring
- implementing-continuous-vulnerability-monitoring
- performing-network-vulnerability-assessment
Arquivos desta versão
assets/13.6 KB
- template.md3.6 KB
references/38.2 KB
- api-reference.md1.9 KB
- standards.md1.9 KB
- workflows.md4.4 KB
scripts/226.9 KB
- agent.py6.1 KB
- process.py20.8 KB
- LICENSE11.0 KB
- SKILL.md6.7 KB
Permissões
| Permissão | Declarada | Encontrada na varredura |
|---|---|---|
| Lê arquivos | Não | Não |
| Grava arquivos | Sim | Sim |
| Roda comandos no shell | Sim | Sim |
| Usa a rede | Sim | Sim |
| Usa conectores | Não | Não |
| Controla um navegador | Não | Não |
Achados da varredura
Revisado em 13 de nov. de 2026
- MédiaComando · command.persistenceSKILL.md:76
- MédiaArquivo · Script executável junto com a skillscripts/agent.py
- MédiaArquivo · Script executável junto com a skillscripts/process.py
- InfoLink · Links para domínios externos
Uma varredura limpa reduz o risco, mas não prova que o pacote é seguro. Leia o que você instala.
| Versão | Publicada em | Commit | SHA-256 | Assinatura | Mudança de permissão |
|---|---|---|---|---|---|
| v1.0 | 13 de nov. de 2026 | 54a7988 | 1a354dce | Assinada | – |
Mais de mukul975
Tudo deste publicador- testing-for-xml-injection-vulnerabilitiesmukul975/testing-for-xml-injection-vulnerabilities5
- testing-for-sensitive-data-exposuremukul975/testing-for-sensitive-data-exposure5
- performing-jwt-none-algorithm-attackmukul975/performing-jwt-none-algorithm-attack5
- detecting-aws-credential-exposure-with-trufflehogmukul975/detecting-aws-credential-exposure-with-trufflehog5
Mais em Engenharia reversa e fuzzing
Ver a categoriaPergunte tudo o que o seu escopo permite.
Crie a conta, adicione créditos e faça a primeira pergunta no chat ou no terminal.
- 1/3
Crie a conta
Individual ou empresa. Dá para virar empresa depois sem perder saldo nem chaves.
Pessoa físicaEmpresa - 2/3
Adicione créditos
No cartão. Você paga por token, sem assinatura.
$5.00recarga mínima - 3/3
Pergunte
No chat, ou instale o CLI e rode notholy login no terminal.
$ notholy login