Response playbooks, investigation guides, and Atomic Red Team tests are Pro-only. Upgrade to unlock the full detection package for THREAT-Recon-AutomatedVulnScannerSweep.

Upgrade to Pro
THREAT-Recon-AutomatedVulnScannerSweep Sumo Logic CSE · Sumo

Detect Automated Vulnerability Scanner Sweep Against External Attack Surface in Sumo Logic CSE

Before exploitation, most intrusions begin with active scanning of the target's external attack surface using automated vulnerability scanning tools such as sqlmap, Nikto, Nuclei, Acunetix, Nessus, OpenVAS, or WPScan. Attackers run these tools against internet-facing web applications, APIs, and edge devices to fingerprint software versions, enumerate misconfigurations, and identify exploitable CVEs before committing to an intrusion attempt. This scanning is typically noisy at the HTTP layer: high-volume requests for known vulnerable paths (e.g. /.env, /.git/config, /wp-login.php, /actuator/health, /phpmyadmin), distinctive scanner user-agent strings, and rapid sequential probing of many distinct URIs from a single source in a short window. Nation-state actors such as Volt Typhoon and APT41 routinely scan edge devices and web infrastructure ahead of exploitation attempts, while eCrime groups like FIN7 and Scattered Spider use commodity scanning frameworks to identify soft targets at scale. Detecting the scanning phase gives defenders a window to harden or patch before the attacker moves to Initial Access.

MITRE ATT&CK

Tactic
Reconnaissance

Sumo Detection Query

Sumo Logic CSE (Sumo)
sql
// Alert 1: Known vulnerability scanner signature
(_sourceCategory="waf/f5" OR _sourceCategory="waf/imperva" OR _sourceCategory="waf/fortiweb" OR _sourceCategory="waf/akamai" OR _sourceCategory="waf/cloudflare" OR _sourceCategory="waf/netscaler")
| where (match_regex(http_user_agent, /(?i)(sqlmap|nikto|nuclei|acunetix|nessus|openvas|wpscan|dirbuster|gobuster)/) or uri_path in ("/.env","/.git/config","/wp-login.php","/actuator/env","/phpmyadmin","/.aws/credentials"))
| fields _messageTime, src_ip, dest_ip, uri_path, http_user_agent
| sort by _messageTime

// Alert 2: Behavioral URI enumeration sweep
(_sourceCategory="waf/f5" OR _sourceCategory="waf/imperva" OR _sourceCategory="waf/fortiweb" OR _sourceCategory="waf/akamai" OR _sourceCategory="waf/cloudflare" OR _sourceCategory="waf/netscaler")
| timeslice 5m
| stats count as TotalRequests, dcount(uri_path) as DistinctURIs, count_if(status_code=404) as NotFoundCount by src_ip, dest_ip, _timeslice
| where DistinctURIs >= 25 and TotalRequests >= 30
| where (NotFoundCount / TotalRequests) >= 0.5
| sort by DistinctURIs desc
medium severity medium confidence

Two-part Sumo Logic detection: known scanner user-agent/sensitive-path signature matching, plus a behavioral aggregation flagging a single source IP enumerating 25+ distinct URIs with a majority-404 ratio within a 5-minute window across WAF sourceCategories.

Data Sources

F5 ASMImperva WAFFortiWebAkamai Kona Site DefenderCloudflare WAFCitrix NetScaler AppFirewall

Required Tables

waf/f5waf/impervawaf/fortiwebwaf/akamaiwaf/cloudflarewaf/netscaler

False Positives & Tuning

  • Authorised DAST/vulnerability scanning tools not yet allowlisted
  • Synthetic monitoring or health-check services hitting many endpoints
  • Single-page applications generating high legitimate 404 rates from client-side routes
  • Search engine crawlers hitting stale sitemap entries

Other platforms for THREAT-Recon-AutomatedVulnScannerSweep


Testing Methodology

Validate this detection against 3 adversary techniques from Atomic Red Team. Each test below lists the behaviour to exercise and the telemetry you should expect to see. Executable commands and cleanup steps are available with Pro.

  1. Test 1Vulnerability Scanner User-Agent Simulation via curl

    Expected signal: WAF/reverse-proxy logs record inbound requests with the scanner user-agent strings in the Message or http_user_agent field.

  2. Test 2Sensitive Path Probing Simulation

    Expected signal: WAF/reverse-proxy logs show requests to each sensitive path, mostly resulting in 404 responses.

  3. Test 3Behavioral URI Enumeration Simulation via ffuf-style Loop

    Expected signal: WAF/reverse-proxy logs record 40 distinct URIs requested from the test source IP within a single 5-minute window, nearly all returning 404.

Unlock playbooks & atomic tests with Pro

Get the full detection package for THREAT-Recon-AutomatedVulnScannerSweep — response playbook and atomic red team tests, plus investigation guidance and hunting queries.

df00tech Pro — £29/user/month

Response PlaybookInvestigation GuideHunting QueriesAtomic Red Team TestsTuning Guidance

Related Detections