Export CSAF Documents

Export all stored CSAF documents to the filesystem with sidecar hash files. Each document is validated and its csaf_version is rewritten to match the currently active CSAF mode.

Note: Export directory: ./data_export
CSAF mode (written into files): 2.1
Documents to export: 113
SHA-256 sidecars: enabled
SHA-512 sidecars: enabled
SHA3-512 sidecars: enabled
BLAKE3-512 sidecars: enabled
SHAKE256-512 sidecars: enabled

Dump Database

Snapshot the live csaf.redb and csaf.sqlite databases into the configured Dump Directory with matching SHA-256, SHA-512, SHA3-512, BLAKE3-512 and SHAKE256-512 hash sidecars — whichever of the five are enabled in Settings. The sqlite snapshot uses the online-backup API so writes in flight are not lost, and the redb copy is pinned by an MVCC read transaction for the duration of the copy.

Note: Dump directory: ./data_dump
SHA-256 sidecars: enabled
SHA-512 sidecars: enabled
SHA3-512 sidecars: enabled
BLAKE3-512 sidecars: enabled
SHAKE256-512 sidecars: enabled

Export Audit Log

Export every row of the audit_log table (CRUD, settings changes, import / export events) in four formats, each with matching hash sidecars. Outputs land in the Export Directory under an ISO-8601 timestamp stem: audit-YYYY-MM-DDTHH-MM-SSZ.{md,csv,json,sarif}. SARIF 2.1.0 output is self-validated before write.

Note: Export directory: ./data_export
SHA-256 sidecars: enabled
SHA-512 sidecars: enabled
SHA3-512 sidecars: enabled
BLAKE3-512 sidecars: enabled
SHAKE256-512 sidecars: enabled

Are you sure?