Overview
TruU IDV records every meaningful action (verification activity, help desk agent actions, admin configuration changes, and console access) as structured audit events in a tenant-scoped, append-only trail. The trail is the system of record: the Activity page in the IDV Console, the request timeline in the help desk app, and every export are projections of the same source, so what your SOC receives matches what an admin sees. Activity presents the trail in two tabs: Audit for control-plane actions (configuration changes, access, administration) and Events for data-plane activity (the verification lifecycle). Both offer category and outcome filters, search, and export.Event families
Events use stable, lowercase dotted names. Names never change once shipped, and schema evolution is additive.
The help desk is where social-engineering attacks happen. If an agent is convinced to search a user, preview contact methods, send a link, or cancel a request, that full sequence is reconstructable from
helpdesk.* events. Configuration changes carry a structured before and after diff, so “who changed the use case and what exactly changed” is answerable from one event.
What each event records
Every event answers four questions with distinct fields:- Actor: who did it (an admin, an agent, the end user, an API client, or the system).
- User: the workforce identity being verified or affected. Actor and user are deliberately separate: for
helpdesk.request_created, the actor is the agent and the user is the caller. - Target: the object acted on (a verification request, a flow, a use case, a membership record).
- Outcome: success, failure, or denial, with a machine-readable reason code such as
OTP_MISMATCH.
Example event payload
API access and export
Programmatic access uses an API client with the audit scopes:GET /admin/audit/events supports cursor pagination and time-range filters for incremental SIEM ingestion. GET /admin/audit/export produces CSV (default) or NDJSON. See Authentication for creating clients and requesting scopes, and Send to your SIEM for a collector pattern.
Every export is itself recorded as an audit event: who exported, with what filters, and how many events.
Redaction
Audit events exclude PII. The stored event carries identifiers and masked display fields only; where an event’s full payload contains sensitive detail, that payload is held in controlled storage referenced by the event, under the same tenant isolation and encryption as other verification assets. The trail never stores submitted one-time codes, document images, or biometric templates. Phone numbers and email addresses are masked, face outcomes appear as confidence bands rather than scores, and each event carries apii_redacted flag. See Data handling.
Immutability
The audit trail is append-only:- There is no API to update or delete audit events, and the console cannot modify them.
- Exports are replayable, so a downstream copy can always be reconciled against the source.
Reconstructing an incident
Events that share a verification request are linked, so a reviewer can read a complete sequence as a timeline:Access and retention
Owners and Admins can search the workspace trail and run exports. Agents see request-scoped events only. Sensitive fields are masked regardless of role. Retention in TruU is set by your agreement; export on a schedule to keep long-term history in your SIEM or data lake.Related pages
Event export and SIEM
Collector pattern for Splunk, Sentinel, and data lakes.
Authentication
API clients and the audit scopes.
Permissions and roles
Who can see and export the trail.
Compliance
Using the trail as evidence.

