⛏️GetSplunky!
Lv.1Intern
0 XP
0
Home Map Stats Drill Board Log In
CoursesArticlesSPL Cheat SheetCertification PathAboutPrivacyTerms

Splunky is an independent, free study resource. It is not affiliated with, endorsed by, or sponsored by Splunk or Cisco. Splunk, SPL and related marks are trademarks of Splunk, a Cisco company, and are used here only to identify the certifications this site helps you study for.

© 2026 Splunky

Back to Floor
The Access Bastion • Room 4

SPL Lab: Auditing Admin Changes & Logins

Security compliance in Splunk Cloud requires auditing administrative actions and authentication attempts. Splunk logs configuration edits, role changes, and login attempts into index=_audit.

Administrative edits carry action="edit_*" (such as edit_user, edit_roles, or edit_indexes) along with user and object fields, while authentication events record action="login attempt" and info (succeeded or failed).

Write an SPL query in _audit to summarize administrative edit events by user, action, and object.

Auditing admin edits and login attempts
index=_audit action="edit_*"
| stats count by user, action, object

index=_audit action="login attempt"
| stats count by user, info, src
Schedule a saved alert on action="edit_*" for sensitive objects like sc_admin or token creation so unauthorized configuration drift is flagged immediately.

Knowledge Check

Prove your understanding to clear the room (Rewards XP)
Write an SPL query searching index=_audit for action="edit_*" and aggregating count by user, action, and object.
Splunk Search Bar
>