Glossary

Audit log

Audit trail

Definition

A record of events showing actions taken in a system, such as sign-ins, permission changes or access to information.

An audit log records selected system activity for later review. Its usefulness depends on event coverage, trustworthy timestamps, retention and protection from alteration.

A customer may include “Audit log” in a supplier security questionnaire or spreadsheet. They want to understand whether this topic affects the service you provide and what safeguards or evidence support your answer.

An audit log records selected actions in a system so someone can later establish what happened. Depending on the service, it may identify an account, the action, its target, the time and whether it succeeded. Sign-ins, permission changes and document access are common examples.

If a small firm's shared folder is unexpectedly made public, an audit log may help identify when the sharing setting changed and which account made the change. That does not automatically identify the human responsible: an account may have been shared or compromised.

Log coverage varies. A service might record administrator changes but not individual file downloads, or make detailed events available only under a particular subscription. Short retention can remove the record before anyone discovers a problem. Logs can also contain personal data and secrets if collection is poorly designed.

Choose events that would help investigate likely incidents, protect logs from alteration, keep clocks aligned and set a retention period that covers the time before issues are discovered. Logging preserves records; monitoring is the separate work of reviewing events and responding. Avoid collecting secrets or unnecessary personal data.

Sources

NCSC: introduction to logging for security purposes