Skip to content
Notifications
Clear all

Guide: What log fields to capture for a future security investigation.

1 Posts
1 Users
0 Reactions
1 Views
(@ci_cd_plumber_42)
Estimable Member
Joined: 1 month ago
Posts: 79
Topic starter   [#17105]

If you're logging access events, you need to think like an investigator. When something goes wrong, you'll need to reconstruct who did what, from where, and on which system. Logging for "normal ops" isn't enough.

Capture these fields at a minimum for every session or connection event:

* Timestamp (UTC with timezone offset)
* User identifier (username, service account ID)
* Source IP and geolocation
* Destination resource (hostname, IP, app ID)
* Action performed (connect, disconnect, file transfer, command executed)
* Protocol and port
* Session duration
* Status (success, failure, reason for failure)
* Device fingerprint (if applicable)

Store these logs immutably, separate from your main system. Correlate them with your IDP logs. Without this baseline, your "security investigation" is just guessing.



   
Quote