User and Process Activity Tracking
You'll learn how to associate audit events with specific users and processes to track who did what on your system.
What's the Goal?
Tracking what happened on a system is useful, but security requires knowing who did it and which process was involved. User and process activity tracking links audit events to user IDs, session IDs, and process identifiers, creating an accountability trail that answers: "Which user ran this command, from which session, and what process executed it?"
Think of it like a workplace security badge system that doesn't just log "door opened" but records "Jane Smith (badge #4372) opened Lab Door B at 2:15 PM."
Core Components
User identification in audit logs captures:
- User ID (UID) and effective user ID
- Login username and originating session
- Terminal or remote connection details
Process tracking records:
- Process ID (PID) and parent process ID (PPID)
- Process executable path and command line
- Process owner and effective permissions
Session association links related events:
- Login session ID
- Command execution within that session
- Process spawning chains (parent-child relationships)
Why It Matters
When a security incident occurs, you need to trace the entire chain: user logged in → spawned shell → executed suspicious command → that process modified sensitive file. Without user and process context, you have disconnected events that can't prove malicious intent or identify the responsible party.
Audit rules can target specific users (-F uid=1000) or track all process executions (-a exit,always -F arch=b64 -S execve), creating detailed activity timelines.
Key Takeaway:
User and process activity tracking transforms raw audit events into an accountability trail by recording who executed what, through which process, and from which session—essential for incident investigation and forensic analysis.