Security

How do I ensure one active session per user?

andrewtrobec
Motivator

Hello All,

My goal is to stop users from sharing credentials (local authentication) which is a potentially useless endeavour, but I see two possible courses of action:

  1. ACTIVE: Set a limitation through a .conf (authentication.conf?) file that doesn't permit multiple sessions for a given local account
  2. PASSIVE: Run a search to identify whether an account has more than 1 active session with successive witch hunt

Are either of these possible?

Thanks!

Andrew

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!

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 ...

All Work and No Play? Not at .conf26! Unwind at These Evening Events

Between hands-on technical sessions, keynote reveals, and diving into live architectures, .conf26 is packed ...

Join the Hackathon at .conf26 and build a No-Code AI agent

Join us for the AI Agent Buildathon, an in-person, three-hour hands-on Hackathon where you’ll use Splunk Agent ...