Audit and recovery evidence
General Enterprise audit logging is planned. The released CLI does not implement
enterprise.audit destinations, access-attempt auditing or configuration-change
audit events. Do not configure those fields or rely on them for compliance.
Evidence available today
- Operational logs: use
--log-format jsonfor structured CLI logs. Logs go to stderr; command output remains on stdout. Route and retain them through your own logging system. - Restore-time erasure reports: suppression counts and the erasure-list checksum identify the list applied during recovery. See erasure.
- MSK migration evidence: finalization produces a signed evidence bundle with migration transitions and validation results. This is specific to the migration workflow. See MSK migration.
The upcoming authorization recovery workflow adds versioned snapshots, checksum-bound plans, operation journals and partial verification reports. That workflow remains under qualification; it does not provide universal effective-access equivalence or general audit logging.
Keep release versions, redacted configuration, record/schema checks and independent allowed/denied application probes with a recovery rehearsal. Exclude credentials and customer-bearing licence files. Use your storage and platform controls for evidence retention and access.