Sign in Get started

Back to results

MediumSplunk security content Rod Soto +2Threat hunting

Splunk Sensitive Information Disclosure in DEBUG Logging Channels

In Splunk versions 9.3, 9.2, 9.1, 9.1.5 Applications which have been enabled with logging level DEBUG may write sensitive information such as keys, tokens, or other sensitive strings into the internal index.

Detection logic

Detection requirements

Platform: Containers IaaS Identity Provider Linux macOS Network Devices Office Suite SaaS Windows
The rule states no platform. This is derived from the ATT&CK technique it maps to.
Log source category: splunk

Known benign triggers

There will be false positives as not every message to the DEBUG log will expose sensitive information, such as keys or other secrets.

References

Links the source published beside this detection. Reference is the link the source wrote, unmodified. Class is decided by this catalogue from the host and path, not stated by the source. Cited by counts published detections citing the same resource, including this one, and the sources beneath it count the repositories this catalogue ingests, which is not the same as independent research.
Reference	Class	Cited by
advisory.splunk.com/advisories/SVD-2024-0301	Unclassified	2
advisory.splunk.com/advisories/SVD-2024-1008	Unclassified	Only this detection cites it
advisory.splunk.com/advisories/SVD-2024-1009	Unclassified	Only this detection cites it

Detections can measure how the public catalogue is used — which detections people look for, and which pages bring them here. It sets a cookie that recognises this browser for 180 days. It is never linked to an account and never follows you to other sites. Privacy notice