The audit log

A permanent, searchable record of who did what in Aegis, and when — the trail you reach for when an auditor asks a question or something on screen does not look right.

Everything that happens in Aegis is written to the audit log (a record of every action that touches the system). Whenever someone creates, edits or deletes a record, changes a status, signs in, or even opens a page, an entry is written. The log is always on, and no role escapes it — an administrator's actions are recorded the same as anyone else's. You reach it from the sidebar under AUDIT → Audit Log, or directly at /log.

Why the trail matters

Most compliance frameworks expect you to show who has access, what they did and when. ISO 27001 and NIS2 (a European cybersecurity law) both set out audit-logging requirements, and SOC 2 (a US assurance standard, on the Aegis roadmap rather than shipped) expects the same. Because Aegis records every action by design, the record is already there when someone asks — you search it rather than reconstruct it.

Who uses it

Reading the log is open to every role. Viewer, Contributor, Manager and Admin all hold the audit-read permission, so all four can open /log, search it and filter it — the screenshot below was captured by a Contributor. What nobody can do here is change anything: the page is read-only for every role.

Every role opens the same page, but not every role sees every entry or every field:

Hidden entries are left out before the list is counted, so neither the search box nor the entry count in the pagination bar gives them away. Two people looking at /log at the same moment can therefore see different totals, and both are correct for their role.

Downloading a copy is separate and licensed. The Export button is rendered only when your plan includes audit export — the Professional and Enterprise tiers — so on Essentials you see the full table but no download button.

What's on this screen

The page opens on the whole log, newest entry first. Along the top sits the heading Audit Log with the line "View all system activities and changes.", and — where your plan allows it — a dark blue Export button with a download arrow at the far right. Directly beneath it is a row of four controls that narrow the list:

The table below has five columns:

Column What it shows
Timestamp The date and time of the action, in your own local time and in the date format of your interface language.
Actor Who acted, with a letter badge for the actor type — U person, S system, W workflow, A API, C scheduler — then the name or email address.
Action What was done, colour-coded: green creates, amber updates, red deletes, blue sign-in and sign-out. The word carries the meaning; the colour only helps you scan.
Target The record affected: its type, a slash, then its name — for example Policy / Remote Working Policy in the captured screen. Where no name can be resolved, the stored identifier appears in a monospaced font instead, as it does for page views. A Trust Center access request is never named here; where the requester's details have been erased it reads Requester redacted.
Description A one-line summary such as "Created policy: Remote Working Policy", cut short with an ellipsis if it is long. Where the stored text holds a record's identifier, Aegis shows the record's name in its place.

Every row is clickable, and the timestamp in each row is also a button, so you can reach an entry's details with the keyboard as well as the mouse. At the foot is a pagination bar reading Showing … to … of … entries, with Previous, numbered pages and Next; the list loads 50 entries at a time. The captured screen shows the log narrowed to Create: a run of new risks, policies, procedures and an incident, created by several people over the preceding weeks. With the filters cleared, a busy log is mostly View rows, because Aegis records page views as well as changes. If nothing matches, the table is replaced by the line No audit log entries found. The figure in the next section shows the whole screen, its four callouts matching the four steps that come before it.

Searching and filtering the log

Open /log from the sidebar. The search box and the three dropdowns combine: set as many as you like and the list narrows to entries matching all of them at once.

  1. Type a word or two into the Search description... box. A moment after you stop typing the table redraws with only the matching entries, and the count in the pagination bar drops to match. Clear the box to bring everything back.
  2. Narrow the list further with the three dropdowns beside the search box — All Actions, All Types, All Actors. Each choice reloads the rows straight away and returns you to page one; use Previous and Next at the foot of the table to move through older activity, and Clear filters beneath the filter row to start again.
  3. Read down the rows: time, actor, action, target and description, so a whole row reads at a glance. Select a row, or its timestamp, to open its full details in a dialog.
  4. Select Export at the top right to download what you are looking at. The file follows your active search and filters, so a table narrowed to deletions gives a file of deletions, and a message confirms the download.
The audit log narrowed to Create actions, with its search box, filters, activity table and Export button — /log.
The audit log narrowed to Create actions, with its search box, filters, activity table and Export button — /log.

Reading a single entry

Selecting a row opens a dialog headed Audit Log Details over the list, setting out the entry field by field:

Close the dialog to return to the list with your filters still in place; if the entry fails to load, the dialog shows the error with a Retry button rather than closing on you. The payload is what makes the log useful after the fact — a delete entry still names the record that was removed, and an edit entry still names the fields that moved, after the record itself has gone. For the record's full contents at that moment, go to the module's own history where it keeps one.

Exporting a slice for an auditor

The Export button produces a CSV (spreadsheet) file named audit-log- plus the date, with eleven columns: timestamp, action, target type, target id, target name, description, actor id, name and email, IP address and user agent. The description in the file has record identifiers swapped for names, the same way the table does. The file follows the same visibility rules as the screen: entries you cannot see are not in it, and the IP address and user agent columns are empty unless you are a Manager or Admin.

  1. Narrow the table first, until it shows exactly the activity you want to hand over. The export follows the same search and filters.
  2. Select Export. The button reads Exporting... and is disabled while the file is prepared, then your browser downloads it.
  3. Read the message that appears. Audit log exported means the file holds every matching entry. A Partial export warning means the result was too large — one export holds at most 50,000 entries — so only the most recent entries were written, and it states how many of how many. If the download fails, an Export failed. Please try again. message says so rather than leaving you waiting.
Check the message before you hand the file over

A truncated export looks like a complete one once it is on disk. If the Partial export warning appeared, split the job by action, type or period and export each part rather than passing on what you have.

The export is itself recorded in the log as an Export action, so the fact that someone took a copy is part of the trail too.

Everyday uses

Tips and limits

Where this connects

The log records the actions of every role, so it sits alongside What each role can do, which sets out who is permitted to do what in the first place. Anomalies watches the same activity for unusual patterns; following its link to an entry opens this page scoped to that one entry by the address, which the filter controls cannot widen — open Audit Log from the sidebar again to come back to the whole log. In the same way, the Audit trail link on a Trust Center access request opens this page on that one request's entries. The Dashboard's recent-activity feed links here for the full history. Audits and Audit readiness are where an export from here usually ends up. If something on this page does not behave as described, Getting help explains how to reach support.