Splunk Enterprise

LOGON Issue after applying STIG

kchongMITRE
Observer

Hi,

After applying STIG settings, I am no longer able to logon to the web console using AD or local admin account. I tried 1). renamed passwd file in etc folder and restarted Splunk service, 2) renamed passwd file in etc folder and created user-seed.conf file in etc\system\local folder but I still can't logon.  Anyone has this issue and know how to fix it?  One of the STIG requires me to set the password complexity and lockout and change the permission on Splunk.

Thanks in advance!  

Labels (1)
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!

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...

Skip the Awkward Silence: Have a .conf-ersation at .conf26

Picture this. You arrive at .conf26 already having your socializing and networking plans mapped out. No ...

Rethinking Zero Trust: From Product Purchases to Logical Control Evidence

Implementing Zero Trust (ZT) across complex environments often falters at the very beginning due to a ...