Skip to main content
Prove it

The audit trail

The audit trail records who did what in AI Governance, to what, and why. It cannot be edited. Use it to answer an auditor, to see who looked at a person's data, and to prove that a record was not…

Written By Christopher Scaminaci

Last updated 4 days ago

The audit trail records who did what in AI Governance, to what, and why. It cannot be edited. Use it to answer an auditor, to see who looked at a person's data, and to prove that a record was not changed.

At a glance

  • What it does: keeps a tamper-evident record of every change and every look at sensitive data.
  • Plan: every plan.
  • Who: Administrator or Auditor.
  • Where: AI Governance → Compliance → Audit trail.
  • Needs: nothing. StackJack writes entries on its own.

What is recorded

Each entry says who did what, to what, and why. Examples are a role given, a setting changed, a text opened with a reason, a name revealed, a settings file or a data export downloaded, and a person erased. Times are in UTC.

The trail cannot be edited. Each entry is chained to the one before it, and a daily integrity record is stored separately. StackJack keeps the trail for six years, longer than other records, and it is kept after you close AI Governance. If your own organization has a main store that runs, StackJack keeps the last 400 days and that storage holds the older days (see below). See Capture levels and what your employer sees.

Find entries

Choose All entries or About a person.

All entries. Use Find entries:

FilterWhat it does
PeriodLatest entries, Last 7 days, Last 30 days, Last 90 days, or Pick dates with From and To.
Action starts withThe start of an action name.
Actor kindWho acted: Person, StackJack operator or System.
Target type and Target idWhat was acted on.

With a filter, a search covers at most 90 days. Pick the dates, or the search uses the last 90 days.

About a person. Choose the Person and select Show. You see everything recorded about that person, including who looked at their data. This is the answer to "who has seen my data?" when a person asks.

Select Search to run a search and Clear to reset. The Entries panel shows 50 entries a page. Columns are Time, Done by, Action and reason, Target and Detail.

When the dates of About a person start before the first entry StackJack holds, the page says: "This list and its export start on . The entries before it are in your storage. Read an older day under the list."

Export

Select Export CSV to download the entries you see. It holds the entries StackJack holds. When your dates start earlier, the foot of the list says from which day StackJack holds entries and that the older entries are in your storage.

Check that the trail is intact

Select Check the chain. StackJack checks every link.

  • All is well: "The trail is intact ( entries checked)."
  • Something is wrong: "The trail was changed at entry . Contact StackJack support."

The readiness view has a signal for this check. See Compliance readiness and the frameworks.

Older entries in your own storage

The audit trail is one record for your whole account, so it follows the main store of your own organization. While that main store runs, StackJack keeps the last 400 days of the audit trail. Older days are in your storage, one file per day. StackJack removes its copy of a day only after the whole day is proven in your storage, and it checks the day in your storage once more just before it removes its copy. If your storage lost the day, StackJack writes it there again. If your storage holds another file in its place, or does not answer, StackJack does not remove that day or any later day, and the storage's card on Storage archive says that the trim is held and why. A legal hold stops StackJack from removing anything. While StackJack keeps less, the rail card What StackJack keeps says so.

Without a main store of your own organization nothing changes: StackJack keeps six years.

To read an older day:

  1. Under the list, the panel says Entries before are in your storage, with the name of your storage. Pick a Day. Only the days your storage holds can be picked.
  2. Select Show the day. StackJack reads the day from your storage and checks it against the daily integrity record it keeps.

What you can see:

  • From your storage. Checked against the daily integrity record. The entries are listed below, 50 at a time (Show more).
  • These entries do not match the record StackJack kept. The page says why, and shows the entries as your storage holds them.
  • StackJack could not read your storage. Select Try again, or Open Storage archive to check the storage.
  • The storage was removed. StackJack can no longer read the day; the file is still in that storage.

A day read from your storage changes nothing and is not written to the trail. It is not part of the CSV export. A person who sees only some organizations sees only those organizations' entries of a day.

The files are under <folder>/<account id>/<organization id>/records/audit/<year>/<day>.jsonl in your storage: plain text, one entry per line. You can keep, copy and read them without StackJack. See Using your own storage as the main store.

What you will see

  • Your own actions, with the reason you gave.
  • An entry for each time text was opened, a name was revealed or a download was made.
  • For text, an entry when you start a reveal session, change its reason or end it, and one entry for every text you open inside it (each carries the session and your reason).
  • Actions by a StackJack operator or by the system, marked as such.

Troubleshooting

What you seeWhat to check
"No entries match."Widen the period or loosen a filter.
A search is slow or refusedA filtered search covers at most 90 days. Narrow it.
You cannot see the pageThe page is for Administrators and Auditors.
"The audit trail could not be loaded. Reload the page to try again."Reload. If it persists, contact support.
"StackJack could not read" your storageSelect Try again in a few minutes. Check the storage on Storage archive.
"These entries do not match the record StackJack kept."The file in your storage is not the file StackJack wrote there. The entries are shown as your storage holds them.

Next