Administration
Audit log
See who changed what in your organisation, filter and export the log, and check that it has not been altered.
The audit log records who did what in your organisation and when: sign-ins, changes to people and settings, triage decisions, runs that were started, and what Nullgap's own systems and staff did. Entries cannot be edited, and they are kept when other data is deleted. Only deleting the workspace removes the log.
In the console it is under Settings, Audit log.
#Who can do what
| Action | Who |
|---|---|
| Read and filter the log | Every member; any API key |
| Export the log | Admin; an API key with the admin scope |
| Verify the log's integrity | Admin; an API key with the admin scope |
#An entry
{
"id": "aud_5k2m9x",
"at": "2026-11-16T09:30:00.000Z",
"actor": "dana@acme.example",
"action": "member.role",
"target": "sam@acme.example",
"detail": "admin",
"seq": 418,
"hash": "9f2c...e1"
}
| Field | Meaning |
|---|---|
at | When it happened, in UTC |
actor | Who did it. See the table below |
action | What happened, as area.event |
target | What it was done to: an e-mail address, a repository, a finding's title, a host name. May be null |
detail | Extra context in plain words, such as the new role or the names of the settings that changed. May be null. Secrets, tokens and codes are never written here |
seq | The entry's position in the organisation's chain, counting from 1 |
hash | A hash of this entry and of the one before it. See the tamper-evident chain |
#Actors
| Actor | Meaning |
|---|---|
| An e-mail address | A signed-in person |
api-key: followed by a key's name | An API key |
scim | Your identity provider, through SCIM |
nullgap | Nullgap's own automation: retention, automatic seat assignment, a finding raised again, a stopped run |
system | The daily domain re-check and related checks |
anonymous | A single sign-on attempt that was refused before anyone was identified |
Nullgap support | A member of Nullgap staff changing something about your workspace |
Nullgap researcher | A member of Nullgap staff reading or deciding a finding during human validation |
operator | A maintenance action on the service that touched your organisation's stored secrets |
#What is recorded
Events about a person's account (sign-ins, second-factor changes, sessions) are written to the log of every organisation that person is a member of.
#Sign-in and sessions
| Action | When |
|---|---|
auth.signin | A sign-in completed. detail names the method, and the second step if there was one |
auth.signin_failed | A wrong second-factor code, or a passkey that was not accepted, at sign-in |
auth.signout | A person signed out |
auth.sso_failed | A single sign-on attempt was refused |
session.revoked, session.revoked_others | A person ended one of their sessions, or all their other sessions |
session.revoked_all | An admin signed everyone out |
#Second factor
| Action | When |
|---|---|
mfa.enrol_started, mfa.enabled, mfa.disabled | Authenticator set-up started, confirmed, or turned off |
mfa.code_rejected, mfa.locked | A wrong code, or a code refused during a lockout |
mfa.recovery_code_used, mfa.recovery_codes_replaced | A recovery code was used; a new set was created |
passkey.added, passkey.removed | A passkey was added or removed |
#People, seats and provisioning
| Action | When |
|---|---|
invitation.created, invitation.accepted, invitation.revoked, invitation.replaced | Invitations. invitation.replaced is written when a new invitation to the same address replaces a pending one |
member.role, member.removed | A role was changed; a member was removed |
member.joined_sso | A person joined by signing in through single sign-on for the first time |
member.provisioned, member.deprovisioned, scim.user_deleted | SCIM added, deactivated or deleted a user |
seat.assigned, seat.removed | A review seat was assigned (by a person or automatically) or removed |
#Organisation, access and settings
| Action | When |
|---|---|
org.created, org.updated | The organisation was created; its name or address changed |
settings.updated | Settings changed. detail lists which, never their values |
settings.unverified_fixes | Whether a fix may be proposed without proof was switched on or off. detail says which |
sso.updated, sso.removed | Single sign-on was saved or removed. detail lists which settings changed |
sso.domain_verified, sso.domain_check_failed | A domain check passed or failed |
sso.domain_claim_attempt | Another organisation published a verification record for a domain you hold, and was refused |
sso.domain_verification_lapsed | A domain's record was missing for seven days |
scim.enabled, scim.token_replaced, scim.disabled | SCIM provisioning |
apikey.created, apikey.rotated, apikey.revoked | API keys |
billing.trial_started | The trial was started |
#Code hosts, repositories and applications
| Action | When |
|---|---|
connection.created, connection.updated, connection.removed | A code-host connection |
connection.claim_refused | Someone tried to link a GitHub installation they do not administer |
connection.webhook_secret_rotated | A connection's webhook secret was rotated |
repositories.synced | The repository list was refreshed |
repository.enabled, repository.disabled | Pull request review switched on or off for a repository |
repository.added_by_address, repository.uploaded, repository.removed | A public repository was added, an archive uploaded, a repository removed |
application.created, application.updated, application.regenerate, application.deleted | Applications and their threat models |
#Reviews, pentests and fixes
| Action | When |
|---|---|
review.requested | A person or a key asked for a review of a pull request |
pentest.started, pentest.retest_started, pentest.cancelled | Pentests |
pentest.access_checked | The sign-in check for live testing ran. detail is passed or failed |
pentest.state_changing_allowed | State-changing live tests were allowed for a pentest |
schedule.created, schedule.updated, schedule.deleted | Pentest schedules |
remediation.started | A fix run was started |
automation.created, automation.updated, automation.deleted, automation.skipped | Automations. skipped means a run did not start for lack of automation credits |
custom_check.created, custom_check.updated, custom_check.deleted | Custom checks |
job.retried | An admin retried a background job |
security.zero_retention_unconfirmed | A run was stopped because zero data retention could not be confirmed for an AI request |
#Findings
| Action | When |
|---|---|
finding.open, finding.patched, finding.accepted_risk, finding.false_positive | A finding's state changed. detail carries the reason and, when it was not done in the console, the channel |
finding.unsuppressed | Findings that an earlier dismissal was holding back were raised |
finding.confirmed | A finding was confirmed as valid from the code host |
finding.note_added | A note was added |
finding.issue_created, finding.issue_updated | An issue was created in a tracker, or kept in step with it |
findings.exported | Findings were exported |
report.shared, report.unshared | A report's share link was created or removed |
#Integrations
| Action | When |
|---|---|
integration.connected, integration.disconnected | Slack notifications, Jira or Linear |
integration.status_sync_on, integration.status_sync_off, integration.webhook_secret_rotated | Jira status sync |
webhook.created, webhook.updated, webhook.secret_rotated, webhook.redelivered, webhook.deleted | Outbound webhooks |
slack_assistant.created, slack_assistant.connected, slack_assistant.secret_rotated, slack_assistant.removed | The Slack assistant |
slack.linked, slack.unlinked | A member linked or unlinked their Slack user |
#Data
| Action | When |
|---|---|
data.exported | An owner exported everything |
data.erased | An owner erased data. target is the scope, detail counts what was removed |
data.retention | The automatic purge deleted something. detail counts what |
audit.exported | The audit log itself was exported |
#Skills and support
| Action | When |
|---|---|
skill.enabled, skill.disabled | A skill was switched on or off, for the organisation or for one repository (named in detail) |
skills.settings_updated | The per-repository overrides, the permitted tools or the pentest switch for built-in skills were changed |
skills.builtin_in_pentests_on, skills.builtin_in_pentests_off | An admin switched "Run built-in skills in pentests" on or off |
skill.created, skill.imported, skill.updated, skill.deleted | A custom skill was written, uploaded, edited or deleted. The entry names the skill; its text is not copied into the log |
skill.run_started | Someone started a skill on demand |
skill.artefact_uploaded | A file was uploaded for a comparison of two versions |
support.request_opened, support.request_resolved, support.request_reopened | A member opened, resolved or reopened a support request. The text of messages is never logged |
support.access_granted, support.access_revoked | An admin let Nullgap support view the workspace, or the access ended |
#What Nullgap staff did
| Action | Actor | When |
|---|---|---|
finding.viewed_for_validation | Nullgap researcher | A researcher opened one of your findings. Written on every read |
finding.validation_confirmed, finding.validation_adjusted | Nullgap researcher | A researcher confirmed a finding, or changed its severity |
finding.false_positive | Nullgap researcher | A researcher rejected a finding; it is closed with their reason |
platform.plan_changed, platform.suspended, platform.resumed | Nullgap support | Your plan was changed; the workspace was suspended or resumed |
platform.limits_changed, platform.credits_adjusted | Nullgap support | Your monthly usage ceiling or a credit balance was changed |
platform.validation_enabled, platform.validation_disabled | Nullgap support | Human validation was switched on or off for your workspace |
support.access_used | Nullgap support | Support opened a page of your workspace while an admin had allowed it. Written on every read, with what was opened. See the support channel |
org.created, platform.client_created, platform.client_invitation_resent | Nullgap support | Nullgap set the workspace up for you, or sent the first owner's invitation again |
secrets.erased | operator | Your organisation's stored secrets were removed in a maintenance action |
Each staff change carries the reason the member of staff gave, in detail. See the audit log as a security control.
#Filters
| Console field | Query parameter | Matches |
|---|---|---|
| Person | actor | The actor, exactly |
| Action starts with | action | Actions that start with the text: auth. or member., for example |
| From | from | Entries at or after this time |
| To | to | Entries at or before this time |
from and to take any date or date-time; a value that is not a date answers 400. In the console, dates are whole days in UTC.
The list is newest first and is paged with limit (1 to 200, default 50) and offset.
curl -s -H "Authorization: Bearer $NULLGAP_API_KEY" \
"$NULLGAP_URL/api/orgs/$NULLGAP_ORG/audit?action=member.&from=2026-11-01&limit=20"
The answer is { "items": [...], "total": n }.
#Export
Export CSV and Export JSON download everything that matches the current filters, not only the page on screen.
curl -s -H "Authorization: Bearer $NULLGAP_API_KEY" \
"$NULLGAP_URL/api/orgs/$NULLGAP_ORG/audit/export?format=json&from=2026-11-01" \
-o audit.json
| Fact | Value |
|---|---|
format | csv (the default) or json |
| Filters | The same four as the list |
| Largest export | 100,000 entries. Use from and to to export a longer log in parts |
| CSV columns | seq, at, actor, action, target, detail, hash |
| JSON | An array of entries as shown above |
| Needs | Admin, or an API key with the admin scope |
A CSV cell that starts with =, +, - or @ is prefixed with an apostrophe, so that a spreadsheet does not treat it as a formula.
Each export is itself recorded as audit.exported, with the format and the number of entries.
#The tamper-evident chain
Each entry carries a hash computed over its own contents and the hash of the entry before it. The hash of the newest entry is also stored separately. Changing, removing or inserting an entry therefore breaks the chain from that point on, and removing the newest entries no longer matches the stored head.
#Verify
In the console, choose Verify integrity under Integrity. Through the API:
curl -s -H "Authorization: Bearer $NULLGAP_API_KEY" \
"$NULLGAP_URL/api/orgs/$NULLGAP_ORG/audit/verify"
Verification walks the whole log from the oldest entry and reports the first place the chain does not hold.
A successful verification:
{ "ok": true, "checked": 418, "unchained": 0, "firstBreak": null }
The console shows "Verified through event 418": all 418 chained entries link to the one before them, so none has been changed or removed.
A failed verification:
{
"ok": false,
"checked": 211,
"unchained": 0,
"firstBreak": { "id": "aud_7h3k2p", "at": "2026-09-03T14:21:07.000Z", "seq": 212 }
}
The console shows "The log does not verify from event 212". That entry, or one next to it, was changed or removed after it was written. Entries before it verified.
| Field | Meaning |
|---|---|
ok | Whether the whole chain holds |
checked | How many chained entries verified before the check ended |
unchained | Entries recorded before chaining existed. They are not covered by the check |
firstBreak | The first entry whose link does not match, or null. An id of chain-head means the entries themselves link up but the newest ones are missing: the stored head points past the last entry found |
If verification fails, export the log, note the firstBreak, and contact Nullgap. See getting help.
#What verification does not prove
The check detects an entry that was changed, removed or inserted. It cannot rule out someone with direct access to the database rewriting the entire log and its head consistently. If you need that assurance, export the log regularly and keep the exports somewhere Nullgap cannot reach: an old export's seq and hash values must still match the live log. The audit log as a security control shows how to check an export on your own machine.
#Retention of the log
The audit log is not subject to the organisation's retention period and is not removed by erasing data, in either scope. See retention, export and erase.
It is included in the owner's full export, and in the audit export described above.
Nullgap documentation