Learn the concept.
Logs are observations about activity. Useful security events help you reconstruct what happened, but they need context and protection.
Capture meaningful context
Look for when, where, who, and what: timestamps, the system, the identity, the action, and the outcome.
Protect the record
Restrict access and guard against unauthorized changes. Logs can contain sensitive information.
Do not create another leak
Avoid recording passwords, access tokens, and other secrets. More data is not always better data.
Field example01 / A
Put it in context
A fictional record says “login failed.” A record that also includes the account, time zone, source, application, and result gives an investigator more useful context.
A log you can investigate
One synthetic sign-in event, shown as labeled fields.
- When09:45:02 UTC
Retain the time zone.
- Who / whereanalyst01 · 203.0.113.24
Link the identity and source to the event.
- What / resultSign-in · failed
Describe the action and outcome.
- Keep outPasswords and access tokens
Do not create a new credential leak in the log.
Read the visualWhat is missing from a record that only says “login failed”?
The time context, account, source, and system or application needed to investigate the event.
Make a decision.
Use what you just learned. A correct answer lets you save this lesson to your progress.
Take this with you.
Good evidence is relevant, interpretable, and protected.
Next lesson: An alert is a starting point