Web Server Potential Spike in Error Response Codes
This rule detects unusual spikes in error response codes (500, 502, 503, 504) from web servers, which may indicate reconnaissance activities such as vulnerability scanning or fuzzing attempts by adversaries. These…
Description
This rule detects unusual spikes in error response codes (500, 502, 503, 504) from web servers, which may indicate reconnaissance activities such as vulnerability scanning or fuzzing attempts by adversaries. These activities often generate a high volume of error responses as they probe for weaknesses in web applications. Error response codes may potentially indicate server-side issues that could be exploited.
Detection logic
Its licence does not clear it for publishing here
Sunturai publishes a detection's own text where the licence it arrived under has been reviewed and permits it, and Elastic License 2.0 has not. The query as its source wrote it, its canonical form and the hash that pins this revision are in the workspace record.
Detection requirements
- Platform
- PRE
The rule states no platform. This is derived from the ATT&CK technique it maps to.
MITRE ATT&CK mappings
0 exclusive techniques.This is coverage no other published rule has; it is not this rule's total technique count.
No references are available for this detection.
From the source
- At source
- Open at source
- Upstream identifier
- 6fa3abe3-9cd8-41de-951b-51ed8f710523
- Tagged by the source as
- Data Source: ApacheData Source: Apache TomcatData Source: IISData Source: NginxData Source: TraefikDomain: WebNoise: HighPerformance: FastProfile: AggressiveResources: Investigation GuideRule Type: ES|QLService: Apache HTTP ServerService: Apache TomcatService: IISService: NginxTactic: ReconnaissanceThreat: Web Application AttackUse Case: Threat Detection
Licence
- Published under
- Elastic License 2.0Read the licence
- Attribution
- Required
Authorship
- Written by
- Published
- Sep 20, 2026
- Version
- 3