Navigate the audit trail
The audit trail is at Security & Risk → Audit & Forensics → Audit trail. The page title is Audit & Reports.
Every view of the page is itself logged as AUDIT_LOG_VIEWED.
| Role | What they see |
|---|---|
| Compliance Officer, CISO, Super Admin | The whole trail |
| Identity Admin, Tenant Owner, Security Analyst, PAM Admin, Agent Engineer, External Auditor | The whole trail, read-only |
| Manager | Events for their direct reports only |
| End User | No access |
Find events
Use the Filters card above the table:
| Filter | What it does |
|---|---|
| Search | Free text matched against the action, actor name, resource ID, resource type and agent name |
| Category | Provisioning, Entitlement, Certification, PAM, Agent, Policy, System, Reconciliation or API Hub. Each category matches by action-name prefix. |
| Actor Type | Human, Agent or System |
| From / To | Date range. To includes the whole day. |
Agent Activity (90d) is a shortcut: it shows events by AI agents over the last 90 days. Clear resets every filter. Click the Actor, Action, Resource or When column header to sort. The table shows 50 events per page. Columns hides or shows columns, and your choice is remembered in your browser.
Links from other pages, such as a user’s or an agent’s page, open the trail already filtered to one actor, resource, action type, request or trace. A Showing only: bar appears, with Show the whole log to remove that filter.
There is no outcome or IP-address filter. Action names follow DOMAIN_OBJECT_VERB, for example LOGIN_SUCCESS,
ENTITLEMENT_REVOKED, JML_LEAVER_TRIGGERED and SOD_RULE_CREATED. The table shows a readable label for each.
One quirk: the Certification category matches CAMPAIGN_* actions only, so CERT_CAMPAIGN_* events appear
under System. Use Search to find them.
Read a record
Click a row, or press Enter on it, to expand it. Event Details shows the Event ID, Action Type, Resource ID, Timestamp (UTC) and Actor Type. Below that is the raw JSON of the state recorded with the event. The actor’s name is the name they had when the action happened. Actors erased under GDPR show “(redacted per GDPR)”. The Action Type is the event’s name — the same name in the CSV export, the audit API and your SIEM; every one is listed in the audit event reference.
The page does not show a before/after comparison, the IP address or user agent, or the hash values. The public
API (GET /api/v1/audit, API-key scope read:audit_logs) returns previous_state and ip_address where they were
recorded.
Export
Export CSV downloads the events currently on screen: one page, up to 50 rows. It is not the whole filtered
result. Every export is logged as AUDIT_LOG_EXPORTED before the file is created. If that log entry cannot be
written, the download is stopped and you see “Export blocked”. For larger extracts, use one of these:
GET /api/v1/audit: filter byaction_type,resource_type,sinceanduntil, up to 100 rows per page.- Forensics tab: signed JSON or PDF evidence exports. These need Identity Admin, Tenant Owner, CISO, External Auditor or Super Admin.
- SIEM Export (Platform Config → Integrations & API): sends new audit events to your SIEM every five minutes.
Check the chain
Every event is hashed into a tamper-evident chain. Compliance Officers and Super Admins see a chain banner at the top of the page. Its buttons are Verify now, Re-check and Re-verify. A check covers the latest 500 entries and reports one of these:
- Audit chain intact — tamper-evident: all good.
- Audit chain tampered — review immediately: an entry no longer matches its hash.
- Audit chain — records require review: there is a gap in the sequence.
- Audit chain intact — benign historical rows noted: old rows have known, harmless issues.
AtmanID also checks the chain on its own:
| Check | When (UTC) | What it covers |
|---|---|---|
| Nightly | 02:30 daily | The latest 500 entries. Writes AUDIT_CHAIN_VERIFIED, or AUDIT_CHAIN_BROKEN on failure. |
| Weekly | Sunday 03:30 | The whole chain, plus every signed anchor |
| Anchor signing | Every 5 minutes | Signs the chain head. Anchors are mirrored offsite. |
If a check fails, Super Admins, Identity Admins, CISOs and Compliance Officers get an Audit integrity alert notification that links back to this page. See Audit chain for how the chain works.
Evidence for auditors
- Give an outside auditor time-limited, read-only access in Security & Risk → Compliance → Auditor access. The auditor then works from the Auditor Portal.
- Compliance → Evidence packs builds a pack for a period and framework: SOX (ITGC), ISO 27001, SOC 2 (TSC) or All Sections. Click Generate Pack, then Print / Save as PDF or Download JSON.
Retention
Super Admins can set an Audit trail retention period on the GDPR erasure page (Platform Config → Administration): 730 days by default, between 365 and 2555. The period is recorded but not yet enforced; old audit events are not deleted today.
© AtmanID · Privacy