Bot intelligence record
Nessus
Review firstNessus is a security scanner from Tenable used for security scanning, malware checks, vulnerability assessment, certificate review; it appears in server logs as `Nessus`.
User-Agent Pattern
TenableNessus
User-agent strings are identification signals, not proof of identity. Confirm important allow, block, or rate-limit decisions with logs, DNS or IP evidence, request behavior, or operator documentation when available.
Robots.txt Snippet
Click snippet to copyUser-agent: Nessus
Disallow: /Click the snippet to copy it, or highlight the text manually.
Handling Guidance
MonitorUse this record as bot intelligence, then verify the request source and behavior before allowing, blocking, or rate limiting.
Nessus is used for security scanning, malware checks, vulnerability assessment, certificate review, and site-safety analysis.
Record Details
Structured data- Operator
- Tenable
- Family
- Tenable
- Purpose
- Vulnerability Scanning
- Identity type
- Documented
- Confidence
- Medium
- Last verified
- 2026-06-22
- Last checked
- 2026-06-22
- Source type
- Observed
- Verification
- Verify Nessus by matching `Nessus` to Tenable evidence, then checking reverse DNS, source-network ownership, signed request data, or published crawler documentation when available.
- Spoofing risk
- Nessus has medium spoofing risk because user-agent strings can be copied; pair the match with DNS, IP, behavior, or operator evidence.
Notes
- Nessus is a security scanner from Tenable used for security scanning, malware checks, vulnerability assessment, certificate review, and site-safety analysis.
- Its primary user-agent pattern is
Nessus. - Nessus is verified with Medium confidence. The identity type is Documented, and the evidence basis is observed traffic patterns and user-agent evidence.
- Nessus does not have confirmed robots.txt behavior in the available public evidence.
- Nessus should be monitored first, then rate-limited or blocked if the crawl rate, paths, or behavior are unwanted.
Evidence and Source
- Verify Nessus by matching `Nessus` to Tenable evidence, then checking reverse DNS, source-network ownership, signed request data, or published crawler documentation when available.
- Nessus traffic is primarily detected by the `Nessus` user-agent pattern. Compare source IPs, reverse DNS, request paths, and crawl cadence with Tenable infrastructure before trusting the traffic.
- Nessus is used for security scanning, malware checks, vulnerability assessment, certificate review, and site-safety analysis.
- Nessus has medium spoofing risk because user-agent strings can be copied; pair the match with DNS, IP, behavior, or operator evidence.
Monitor This Bot In Edge
Botcrawl EdgeUse Botcrawl Edge to see matching traffic, identify related datacenter activity, and create allow, block, rate-limit, or log rules across connected sites.