syscall export produces a single JSON package. The current format is syscall-export/v2; the manifest schema is version 2.
The source database is opened read-only. The package is written atomically with mode 0600 and is never overwritten without explicit --force.
Top-level structure
Metadata
metadata contains:
export_timestamp_ns: when the package was created.database_path: the source path as provided.session_id: the exported session.syscall_versionandsyscall_buildwhen available.limitations: explicit package limitations.
Session and processes
session preserves recorded metadata and counters, including redacted arguments when redaction was used. Unrelated sessions are excluded.
process_instances is reconstructed from recorded events in stable order. It includes unresolved and provisional identity evidence rather than filling gaps.
Events
events contains every recorded event for the requested session in:
null and are noted in limitations.
Analysis component
analysis carries the syscall-analysis/v1 report:
- Session summary.
- Evidence completeness.
- Evaluated rule metadata.
- Findings and original event IDs.
- Limitations.
Verification component
verification carries the read-only verification report. If verification cannot complete, the package preserves an explicit failure or unavailable outcome and records a limitation.
For deterministic exports of identical evidence, verification_timestamp_ns is normalized to 0. The actual export action time remains in metadata.export_timestamp_ns.
Determinism
Evidence components are serialized with stable key ordering and stable ordering of processes and events. Analysis is deterministic for identical evidence and the default configuration. For identical recorded evidence:session,process_instances,events,analysis, andverificationshould be byte-stable after canonical serialization.metadata.export_timestamp_nscan change.- The embedded verification timestamp is normalized.
Manifest
The manifest contains:
Each entry contains:
The manifest is not hashed into itself.
Hashing method
For each component:Verification
- Package format and manifest version.
- Duplicate or missing component entries.
- Byte lengths.
- SHA-256 hashes.
Legacy v1 packages containing a manifest self-entry are reported as warnings rather than silently accepted.
Integrity semantics
Verification of the session and verification of the export answer different questions:
Neither proves that the kernel observed every relevant event.
Privacy
- Arguments are exported as recorded; redacted arguments remain redacted.
- File paths can reveal sensitive names and directory structure.
- Connect events reveal destination addresses and ports.
- Source addresses may be null.
- No file contents, packet payloads, DNS names, environment variables, or unrelated sessions are included.
- Paths may be relative or truncated; connect events remain attempts.
Versioning
v2 stopped hashing the manifest into itself and introduced manifest schema 2. Existing v1 packages remain inspectable. Future changes must increment the relevant version and document compatibility.
See Export evidence for the command workflow.