Kubernetes Nginx Ingress LFI
The following analytic detects local file inclusion (LFI) attacks targeting Kubernetes Nginx ingress controllers. It leverages Kubernetes logs, parsing fields such as `request` and `status` to identify suspicious…
Description
The following analytic detects local file inclusion (LFI) attacks targeting Kubernetes Nginx ingress controllers. It leverages Kubernetes logs, parsing fields such as `request` and `status` to identify suspicious patterns indicative of LFI attempts. This activity is significant because LFI attacks can allow attackers to read sensitive files from the server, potentially exposing critical information. If confirmed malicious, this could lead to unauthorized access to sensitive data, further exploitation, and potential compromise of the Kubernetes environment.
Detection logic
Detection requirements
- Platform
- Identity ProviderLinuxmacOSWindows
The rule states no platform. This is derived from the ATT&CK technique it maps to.
Known benign triggers
- No false positives have been identified at this time.
MITRE ATT&CK mappings
0 exclusive techniques.This is coverage no other published rule has; it is not this rule's total technique count.
References
| Reference | Cited by |
|---|---|
| github.com/splunk/splunk-connect-for-kubernetes | 3 |
| www.offensive-security.com/metasploit-unleashed/file-inclusion-vulnerabilities/ | Only this detection cites it |
From the source
- At source
- Open at source
- Upstream identifier
- 0f83244b-425b-4528-83db-7a88c5f66e48
- Tagged by the source as
- Dev Sec OpsKubernetescloudSplunk CloudSplunk EnterpriseSplunk Enterprise Securitynetwork
Licence
- Published under
- Apache License 2.0Read the licence
- Attribution
- Required
- Obtained under
- Apache-2.0Read the origin licence
Authorship
- Written by
- Published
- Oct 6, 2026
- Version
- 2