Security

Password hashing in Splunk

anandhalagaras1
Contributor

In one of the file the password seems to be present and the same has been getting ingested into Splunk. So is there any way to hash the password for that field so that it wont be visible in Splunk during searching eventhough it is present in the logs.

Tags (1)
0 Karma

woodcock
Esteemed Legend

Moving forward, you can use SEDCMD to strip it:
https://docs.splunk.com/Documentation/Splunk/latest/Data/Anonymizedata
or INGEST_EVAL to hash it (I would not bother):
https://splunkonbigdata.com/2019/03/22/ingest_eval/
Moving backward, you will have to reprocess it from original raw events OR use collect to re-index from existing events (then go back and delete the old evetns):
https://docs.splunk.com/Documentation/Splunk/latest/SearchReference/Collect

0 Karma

PavelP
Motivator

I don't think it is possible, but I can suggest a workaround:
You can mask passwords with SEDCMD command during the ingestion and send it to one index and send unmodified events into other index, which can be accessed by you only.

Let me know if it solves your question. If not - try to describe your use case so may be somebody can give your better solution.

0 Karma
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Vibe-coding, AI, and Splunkcraft: Highlights from the .conf26 Builder Bar

If you stopped by the Builder Bar at .conf26, thank you! This year, we brought ...

Thanks for the Memories: .conf26 Took Learning to New Heights

Thank you, Splunk Community, for making .conf26 in Denver one for the books. From packed Splunk University ...

Best Practices: Splunk auto adjust pipeline queue

When you enable autoAdjustQueue in Splunk, maxSize should be understood as the queue size Splunk starts with ...