감사 추적 및 변조 감지 로그

Ordinary logs help debugging; an audit trail is a structured, durable record of security-relevant actions: who did what, when, and from where. Audit trails support investigations, compliance, and accountability.

Record events that matter for security and compliance:

• Authentication: logins, logouts, failures
• Authorization changes: role and permission edits
• Sensitive data access and exports
• Configuration and admin actions

Do not log secrets, passwords, or full card numbers.

A good audit record is structured and complete enough to reconstruct what happened.

Attackers who gain access often try to erase their tracks. A tamper-evident log makes any modification or deletion detectable, so you can trust the trail during an incident.

Audit logs should be append-only. Write them to storage that disallows edits and deletes: WORM buckets, append-only tables, or a separate logging service the application cannot modify after writing.

Hash chaining links each record to the previous one by including the prior record's hash. Altering any earlier entry breaks the chain, making tampering obvious.

To verify integrity, recompute the chain from the start and compare against stored hashes. The first mismatch points to the tampered record.

Ship audit logs off the host that generates them, to a SIEM or central log store. If an attacker compromises a server, the off-host copy remains intact for investigation.

Accurate, synchronized clocks (NTP) are essential. Correlating events across systems during an incident depends on consistent timestamps; always store time in UTC with timezone info.

Define how long audit data is kept based on compliance needs, and protect it with strict access control. Reading the audit trail should itself be audited.

• Set a clear retention policy
• Restrict who can read audit data
• Audit access to the audit log

Pair audit trails with monitoring so suspicious patterns, like repeated permission grants or bulk exports, trigger alerts in near real time rather than being discovered weeks later.

Test your understanding of tamper-evident logging.

You learned how audit trails differ from debug logs, what to record, and how to make them tamper-evident with append-only storage and hash chaining. Ship logs off-host, synchronize clocks, set retention, and alert on anomalies so your trail is trustworthy when it matters.