Splunk Linux Use Case

Who Broke the Box?

Change & identity forensic trails

The scenario

The server is acting strange and nobody changed anything - which is true at the human level and false at the physical level. Someone plugged a Wi-Fi adapter into the rack PDU switch port's management VLAN. A cron entry appeared in root's crontab. `PermitRootLogin` quietly became `yes`. The audit log you needed did not exist because nothing was watching for change. These apps *are* the watchers, and the deltas they emit are timeline evidence on your side.

The app recipe

TA-devfleet PCI/USB inventory signatures + device_delta events - physical config drift
TA-baseline Security settings drift: Secure Boot, sshd config, shadow policy, auditd
TA-authid Identity path drift: nsswitch order, SSSD state, Kerberos ticket caches
TA-cronbeat Scheduled-job inventory - the crontab you never approved
TA-journald Log-plane health: is the evidence being collected at all

Problems this kills

Killer searches

Who this is for

Security-minded sysadmins, incident responders with no SIEM budget, and anyone who has ever asked "when did that USB drive appear?" to an empty room.

Next

All Use Cases Browse All Apps