Audit Trail
Immutable audit events for every privileged action — who, what, when, where, why. Sealed audit path, exportable for compliance reviews.
When a regulator or your client asks 'who changed this employee's compensation last June?', you need an answer in minutes — not a forensic week. FrontLine writes an audit event for every privileged action: changes, approvals, denials, exports, role grants, IdP rotations. Events are immutable and tamper-evident.
Sealed at the database, queryable when auditors arrive
Audit events are emitted from the API service via an append-only write path to a dedicated audit table. Each event captures: actor (user + role + IdP), tenant + client + LOB scope, action verb, target entity, before/after values for changes, request ID, IP, user agent, and timestamp. The table is enforced append-only at the database level — no UPDATE or DELETE statements are permitted, even by the application role. Event retention defaults to 7 years and is configurable per regulatory regime.
What's covered out of the box
Audit-ready artifacts your reviewers can lean on
- SOC 2 Type II — change management + monitoring
- PIPEDA accountability principle
- ISO/IEC 27001 A.12.4 Logging and monitoring
- Default 7-year retention; configurable per jurisdiction
What security and compliance reviewers actually ask
Can audit events be modified or deleted?+
How long are audit events retained?+
Can we stream audit events to our SIEM?+
Are PII access events distinguishable from regular activity?+
Run this past your security team
We share security overviews, RLS policy DDL, audit-event schemas, and SOC 2 progress on request. Book a 30-minute security review with the founders.