syscall export creates a portable evidence package for one session. It reads the source database read-only and writes a new file atomically.
Export a session
The destination directory must already exist. The package is written atomically through a temporary file in that directory, fsynced, and renamed. It is created with mode
0600. Export refuses to overwrite an existing file unless --force is explicit.
Package contents
export_format_version is currently syscall-export/v2.
Only the requested session is included. Unrelated sessions are excluded. No file contents, packet payloads, DNS names, or environment variables are present.
Determinism
For identical recorded evidence:- Components are serialized with stable key ordering and stable event and process ordering.
- Analysis is deterministic for the default export configuration.
- The embedded verification timestamp is normalized to
0. metadata.export_timestamp_nsis the only value expected to change between exports of the same evidence.
Integrity manifest
The manifest contains:manifest_version: currently2.hash_algorithm:sha256.entries: component name, component version, lowercase SHA-256 digest, byte length.note: the integrity semantics.
0 when valid and 1 when invalid.
Analysis failure
Analysis is a required component. If it cannot complete during export, the package includes:Privacy and redaction
Session arguments are exported as recorded.- If
--redact-argswas used, redacted placeholders are preserved and original values are absent. - File paths can reveal sensitive names and directory structure.
- Network events reveal destination addresses and ports.
- There are no file contents, packet payloads, DNS names, or environment variables.
- Activity limitations remain in the record: paths may be relative or truncated, source addresses may be null, and connect events are attempts.
Verify an exported package
--json for automation. A failed verification means the package changed or was malformed after export; it does not by itself identify who changed it.
Versioning
export_format_version identifies the package structure. manifest_version identifies the manifest shape. The analysis component carries its own schema version.
Future changes must increment the relevant version and preserve the ability to interpret prior packages where practical. Legacy v1 packages remain inspectable; their manifest self-entry is reported as a warning.
Related pages
Export format reference
Field order, manifest rules, and compatibility details.
Verification
Session consistency checks and assessment codes.
Evidence model
Accounting, completeness, and authenticity boundaries.
Security
Data handling, permissions, and privilege boundaries.