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

Upgrade to Pro
THREAT-Recon-DistributedVulnScanBurst Splunk · SPL

Detect Distributed Vulnerability Scanning Burst Against Web Infrastructure in Splunk

Adversaries and access brokers run automated vulnerability scanners against externally-facing web infrastructure to fingerprint exposed technology and locate exploitable misconfigurations before initial access. Two patterns dominate: a concentrated burst, where a single source IP fires a wide diversity of scanner-signature requests (config file probes, admin panel paths, framework actuator endpoints, path traversal, webshell probes) at a target within minutes; and a low-and-slow variant, where a small rotating pool of source IPs within the same /24 subnet or hosting-provider ASN spreads the same signature diversity across a much longer window to stay under per-IP rate-limit thresholds. Both patterns are typically observed in WAF, reverse-proxy, or perimeter firewall logs rather than endpoint telemetry, since the target is the externally-facing HTTP surface itself. Detection prioritises the diversity of distinct scanner-signature categories touched per source (or per rotating subnet) over raw request volume, since volume alone is indistinguishable from normal crawler/bot traffic while signature diversity is not.

MITRE ATT&CK

Tactic
Reconnaissance

SPL Detection Query

Splunk (SPL)
spl
index=waf OR index=firewall OR sourcetype=cisco:asa OR sourcetype=f5:bigip:asm OR sourcetype=fortinet:fortiweb
(uri_path="*.env*" OR uri_path="*.git*" OR uri_path="*wp-login*" OR uri_path="*wp-admin*" OR uri_path="*xmlrpc.php*" OR uri_path="*actuator*" OR uri_path="*phpmyadmin*" OR uri_path="*solr/admin*" OR uri_path="*manager/html*" OR uri_path="*../../*" OR uri_path="*shell.php*" OR uri_path="*eval-stdin*" OR http_user_agent="*sqlmap*" OR http_user_agent="*Nikto*" OR http_user_agent="*Nessus*" OR http_user_agent="*Acunetix*" OR http_user_agent="*masscan*" OR http_user_agent="*zgrab*" OR http_user_agent="*Nuclei*" OR http_user_agent="*dirbuster*" OR http_user_agent="*gobuster*" OR http_user_agent="*wpscan*" OR http_user_agent="*OpenVAS*" OR http_user_agent="*Qualys*")
| eval MatchedSignature=case(like(uri_path,"%.env%"),".env", like(uri_path,"%.git%"),".git", like(uri_path,"%wp-login%") OR like(uri_path,"%wp-admin%"),"wordpress_admin", like(uri_path,"%xmlrpc.php%"),"xmlrpc", like(uri_path,"%actuator%"),"spring_actuator", like(uri_path,"%phpmyadmin%"),"phpmyadmin", like(uri_path,"%solr/admin%"),"solr_admin", like(uri_path,"%manager/html%"),"tomcat_manager", like(uri_path,"%../..%"),"path_traversal", like(uri_path,"%shell.php%") OR like(uri_path,"%eval-stdin%"),"webshell_probe", like(http_user_agent,"%sqlmap%") OR like(http_user_agent,"%Nikto%") OR like(http_user_agent,"%Nessus%") OR like(http_user_agent,"%Acunetix%") OR like(http_user_agent,"%masscan%") OR like(http_user_agent,"%zgrab%") OR like(http_user_agent,"%Nuclei%") OR like(http_user_agent,"%dirbuster%") OR like(http_user_agent,"%gobuster%") OR like(http_user_agent,"%wpscan%") OR like(http_user_agent,"%OpenVAS%") OR like(http_user_agent,"%Qualys%"),"scanner_useragent", true(),"other_scanner_signature")
| eval Subnet24=replace(src_ip,"^(\d+\.\d+\.\d+)\.\d+$","\1.0/24")
| stats dc(MatchedSignature) AS DistinctSignatures, dc(uri_path) AS DistinctPaths, dc(src_ip) AS DistinctSourceIPs, count AS TotalRequests, min(_time) AS FirstSeen, max(_time) AS LastSeen, values(MatchedSignature) AS Signatures BY Subnet24, src_ip
| eval BurstDurationMinutes=round((LastSeen-FirstSeen)/60,1)
| eval DetectionType=if(DistinctSourceIPs<=1,"ConcentratedBurst","LowAndSlowSubnetRotation")
| eval RiskScore=case(DistinctSignatures>=15,95, DistinctSignatures>=10,86, DistinctSignatures>=6,76, true(),50)
| where DistinctSignatures>=6 AND (DistinctPaths>=10 OR DistinctSourceIPs>=3)
| sort - RiskScore
high severity medium confidence

SPL equivalent of the KQL detection. Matches scanner-signature paths and known scanner User-Agent strings, categorises the matched signature per request, computes a /24 subnet grouping via regex replace on src_ip, then aggregates distinct signature/path/source-IP counts to distinguish a single-IP ConcentratedBurst from a multi-IP LowAndSlowSubnetRotation within the same subnet.

Data Sources

WAF logs (F5 BIG-IP ASM, Fortinet FortiWeb)Perimeter firewall logs (Cisco ASA)Reverse proxy access logs

Required Sourcetypes

f5:bigip:asmfortinet:fortiwebcisco:asawafnginx:plus:kv

False Positives & Tuning

  • Authorized internal or contracted vulnerability management scans (Qualys, Nessus, Tenable, Rapid7) running against production on an approved scanning schedule
  • Bug bounty researchers or penetration testers operating within an approved rules-of-engagement window
  • Uptime/synthetic monitoring services (Pingdom, UptimeRobot, StatusCake) or health-check bots hitting many paths from a small set of monitoring IPs
  • SEO crawlers, CDN health probes, or archival bots (Googlebot, Bingbot, Wayback Machine) traversing many URL paths that incidentally overlap scanner signature patterns
  • Load testing tools or CI/CD smoke tests hitting numerous endpoints rapidly from a shared build-agent IP address

Other platforms for THREAT-Recon-DistributedVulnScanBurst


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 1Scanner Signature Path Sweep (Concentrated Burst)

    Expected signal: WAF/reverse-proxy logs show >=10 distinct scanner-signature paths requested within seconds from the tester's single source IP, User-Agent 'AtomicTest-VulnScan/1.0'.

  2. Test 2Known Scanner Tool User-Agent Sweep

    Expected signal: WAF logs show dozens of distinct paths (config, admin, CGI, backup file probes) and User-Agent containing 'Nikto' from the tester's source IP within minutes.

  3. Test 3Low-and-Slow Subnet-Rotated Scan Simulation

    Expected signal: WAF logs show 4 distinct source IPs within 198.51.100.0/24, each issuing 2 scanner-signature requests spread across several hours, collectively covering >=8 distinct signature categories.

Unlock playbooks & atomic tests with Pro

Get the full detection package for THREAT-Recon-DistributedVulnScanBurst — 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