Audit trail

Spec sheet // Glossary // AUDIT TRAIL
Glossary / A / Audit trail
Glossary · GRC and resilience

Audit trail

Also called audit log, activity log

Definition

An audit trail is a time-stamped record showing who did what, when and in which system. It captures actions such as creating, changing, approving or deleting a record or transaction. Firms use audit trails to prove that controls worked, to investigate incidents and to let supervisors reconstruct events after the fact.

USER ACTIONLOG ENTRYLOCKED RECORDREVIEW
Fig. 1 · Audit trail
SEC Rule 17a-4 amendments · NYDFS Part 500, section 500.6 · MiFID II Article 16(6)
Key rulesSEC Rule 17a-4 amendments · NYDFS Part 500, section 500.6 · MiFID II Article 16(6)
Applies toBroker-dealers
RegionsUK · EU · US
01

How it works

Systems write a log entry each time a user or process acts on data. A good entry records the user or system identity, the date and time, the action taken, the record affected and, for changes, the value before and after. Entries are protected from editing or deletion, often by write-once storage or cryptographic hashing, so the trail itself can be trusted as evidence.

Compliance teams rely on audit trails across the business: case management decisions on alerts, changes to screening rules and thresholds, payment approvals, trading activity and access to customer data. Internal audit and regulators sample the trail to test whether controls ran as designed. Firms set retention periods to match their record-keeping rules and review logs for unusual access or changes.

Step 1CaptureLog each user and system action as it happens.
Step 2Time-stampAttach a reliable date, time and user identity.
Step 3ProtectLock entries against editing or deletion.
Step 4RetainKeep logs for the period the rules require.
Step 5ReviewSample and monitor the trail for gaps or misuse.
02

The rules

US · Adopted 12 October 2022; effective 3 January 2023; broker-dealer compliance 3 May 2023SEC Rule 17a-4 amendmentsAmendments to Exchange Act Rule 17a-4 on electronic recordkeeping, Release No. 34-96034

Lets broker-dealers keep electronic records in a system with a complete audit trail as an alternative to write-once storage; the trail must record each modification or deletion, its date and time and the person responsible.

Broker-dealers
US · Compliance required from 3 September 2018NYDFS Part 500, section 500.623 NYCRR 500.6 Audit trail, Cybersecurity Requirements for Financial Services Companies

Requires systems that can reconstruct material financial transactions, kept for five years, and audit trails to detect and respond to cybersecurity events, kept for three years.

Entities licensed by the New York Department of Financial Services
EU · 3 January 2018MiFID II Article 16(6)Article 16(6) of Directive 2014/65/EU on markets in financial instruments

Requires firms to keep records of all services, activities and transactions sufficient for the competent authority to supervise them and check compliance with the directive.

Investment firms
03

Common questions

What should an audit trail record?

At a minimum, the identity of the user or system, the date and time, the action taken and the record affected. For changes, it should also show the value before and after, so a reviewer can rebuild exactly what happened.

How long must audit trails be kept?

It depends on the rule. NYDFS Part 500 sets five years for transaction records and three years for cybersecurity logs. Firms map each log type to the longest retention period that applies to it.

Why do regulators care about audit trails?

An audit trail is the evidence that a control ran and that a decision was made by an authorised person. Without one, a firm cannot show supervisors or auditors how an alert was closed, a payment approved or a record changed.