Audit log

Audit log

The Audit log is the record of who changed your controls and incidents, and when. This page explains what is recorded, how to search and filter the log, and how to export it as a spreadsheet or as a signed, tamper-evident file for an auditor.

Who uses it

RoleWhat they do here
AdminReads the log, exports it as CSV, and makes a signed export
Auditor, Policy editor and Incident responderRead the log and export it as CSV

Nobody can add, change or remove entries. Command writes them itself.

What is recorded

Command records these events automatically, with the person who did it and the time:

ObjectEvents
ControlsCreated, saved, published, unpublished and deleted, with the control's title
IncidentsDeclared, with the severity, and resolved, with the incident's title. Opening an investigation is recorded as a declaration too.

Changes to the implementation score are not recorded, because Command calculates the score itself. The stage changes, clocks and explanations of a case are recorded on that case's own timeline. See Incidents.

Read the log

1
Click Audit log in the top navigation.
2
Entries are grouped by day: Today, Yesterday, and earlier days by date, each with its number of entries.
3
Each entry shows how long ago it happened (point at it for the exact time), who did it, what they did, the object and a short summary.
4
Click a control in an entry to open it on the Controls page.
The Audit log with control and incident events grouped by day
User: show only one person's entries, or All users.
Object: All objects, Controls or Incidents.
Event: show one kind of event, or All events.
Search audit log…: find entries by the name of their object, for example a control's title or an incident's title.
Group similar events: switched on by default. Repeated events by the same person on the same object within an hour are combined into one row, with how many times and across how many minutes. Click Show {n} events to see them all.

When nothing matches, the log says No events match these filters.

Export the log

Export as CSV

Click Export CSV. Command downloads the file audit-log.csv and shows Exported {n} events to CSV.

The file contains the whole log, whatever filters you have set, with the time, actor, action, object type, object and summary of each event. Open it in any spreadsheet application.

Make a signed export

A signed export lets an auditor check that the log has not been changed after you exported it.

Who can do thisAdmin.
1
Click Signed export.
2
Command downloads audit-log.signed.json, signed by Soveryne, and shows Signed, tamper-evident export generated.

The same entries always produce the same signature, so any change to the exported file breaks it. An export made after more events were logged has a new signature.

How Command protects you

The audit trail is written by the server. Nobody can add, skip or change an entry from the browser.
The signed export is signed by Soveryne and is available to administrators only, because it contains the full trail of all users.

Troubleshooting

What you seeWhat it meansWhat to do
Signed export failed: followed by a reasonThe signed export could not be made, for example because your role is not AdminAsk an Admin to make the signed export
No events match these filters.No entry matches your filters or searchSet the filters back to All users, All objects and All events, and clear the search
An action you took is not in the logOnly the events listed above are recordedCheck the case timeline for incident details, or the control's version history for approvals