defend-audit report turns the device’s audit records into a single signed evidence ZIP for any past period, ready to hand to an auditor. It is the command behind Compliance Reporting.
Where to run it: open Device → Terminal in the web interface, and run it with
sudo: it needs to read the audit records under/opt/data/auditor/.
| File | What it is |
|---|---|
events.csv |
Every IDS event in the period |
decisions.csv |
Every CrowdSec decision in the period |
dns_events.csv / file_events.csv / tls_events.csv |
Ransomware indicators (DGA-like DNS, transferred-file hashes, suspicious TLS) |
config-snapshot.tar.gz |
The Suricata, CrowdSec, nftables, ulogd, chrony and node-exporter configuration at the time of the report |
manifests/MANIFEST-YYYY-MM-DD.json |
The daily Ed25519-signed manifest for every day in the period |
chrony-logs/ |
NTP attestation: proof that the device clock was kept in sync |
manifest.pubring.json |
The device’s signing-key ring, for offline verification |
chain-of-custody.json |
An Ed25519-signed list of every other file in the ZIP, with its SHA-256 |
The ZIP is written with mode 0640, owned by root. It is safe to copy to a USB drive, attach to a ticket, or upload to a compliance portal.
sudo defend-audit report --from YYYY-MM-DD --to YYYY-MM-DD [--out PATH] [--no-config-snapshot] [--json]
| Option | Required | Default | Effect |
|---|---|---|---|
--from YYYY-MM-DD |
Yes | First day of the period, in UTC | |
--to YYYY-MM-DD |
Yes | Last day of the period, in UTC. Must be on or after --from |
|
--out PATH |
No | ./defend-o-tron-audit-FROM-to-TO.zip |
Where to write the ZIP. The folder must already exist |
--no-config-snapshot |
No | off | Leave out config-snapshot.tar.gz, for example when the auditor only needs the events |
--json |
No | off | Print a JSON result for scripts |
An evidence pack for the second quarter:
$ sudo defend-audit report --from 2026-04-01 --to 2026-06-30 --out /home/admin/q2-evidence.zip
wrote /home/admin/q2-evidence.zip (events=14827 decisions=4113 dns=248 files=31 tls=19 manifests=91 chrony=26)
The line names the ZIP and counts what went into it: the rows of each table, the daily manifests, and the chrony log files.
One month, for an insurance review:
sudo defend-audit report --from 2026-05-01 --to 2026-05-31 --out ~/insurance-review.zip
A single day, for an incident timeline:
sudo defend-audit report --from 2026-05-14 --to 2026-05-14 --out ~/incident-2026-05-14.zip
For a script:
sudo defend-audit report --from 2026-05-01 --to 2026-05-31 --out /tmp/may.zip --json
| Exit code | Meaning |
|---|---|
0 |
The ZIP was written |
1 |
audit.conf could not be read |
2 |
Wrong usage, or a bad date (for example --to before --from) |
3 |
No events store yet: the audit collector has not run |
4 |
No signing key on the device |
5 to 13 |
A later step failed (exporting a table, the snapshot, the manifests, the chrony logs, the key ring, signing or writing the ZIP). The message says which |
chain-of-custody.json, so the auditor can see what the pack was made for.chain-of-custody.json is signed with the device’s key that is active when you make the pack. If the key was rotated since a day’s manifest was signed, that manifest still verifies against its older key, which stays in the key ring. See defend-audit key-rotate..tsr files). They stay on the device, where defend-audit verify and the hourly self-check use them.