Security

Executing CLI commands without password

cwacha
Path Finder

We are currently creating a Disaster Recovery guide for our Splunk installation that must contain all steps necessary to fail over splunk in our environment. One task is to roll all hot buckets to warm. Obviously we need to be "logged in" on the CLI before we can execute this step. The problem is that we need to use a username and password that exists in splunk to get this done and we would have to add that username and password to the DR guide as well to make sure in case of a disaster anyone with basic system knowledge would be able to execute the steps.

What is the best way to do this?

  • Can we disable the password functionality on the CLI?
  • should we put the admin users credentials into the DR guide?
0 Karma

gkanapathy
Splunk Employee
Splunk Employee

No you can not disable this functionality. It's up to you where you document admin passwords required for DR, but I would imagine that Splunk passwords are not the only ones needed. Another thing you could do it provide steps to reset the default admin password by replacing the etc/passwd file.

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!

Your Feedback. Our Roadmap. Visit the PX Feedback Booth at .conf26

You use Splunk every day, come and help shape what's next.  Save Your Seat: Product-Focused Sessions at ...

Agentic SOC Triage: Investigating Splunk ES Notables with MCP Server and a Local LLM

The Problem: Too Many Alerts, Too Little Context Security operations teams running Splunk Enterprise Security ...

Painting a Clearer Picture: Creating Cross-Domain Visibility with AI Canvas

Watch Now Painting a Clearer Picture: Creating Cross-Domain Visibility with AI Canvas     Do you ever feel ...