What it asks for. Audit records must contain enough information to establish what type of event occurred, when and where it occurred, its source, its outcome and the identity of any individuals, subjects or objects involved.
In practice. This means checking that log formats from key systems include timestamps with time zone, user and system identifiers, source addresses and success or failure fields, and normalising them in the logging platform. Synchronised time across systems is essential. Auditors look for sample records, parsing configurations and time synchronisation settings. Privacy rules should guide what personal data appears in logs.
Common gaps. Logs from custom applications often lack user identity or outcome. Inconsistent time zones and unsynchronised clocks make event correlation unreliable. Logs may also contain too much, such as passwords or personal data.