Mobile-ID · Long-term digital evidence preservation
Customers and partnersWorkflow demoContact
Trusted LTANS
Evaluate
MOBILE-ID · TRUSTED LTANS

Log Archiving

Preserve closed log sets with source-event links and missing/duplicate checks before deposit.

VI–EN terminology

Outcome and scope

Preserve closed log windows with checks for missing, duplicated or misattributed source records.

Documentation scope Workflow design and integration contract; operational configuration is confirmed per environment.
PrepareReceive
Minimized transaction, API-gateway or business-system logs.An immutable batch with time range, inventory, count and evidence reference.

Participants: SOC, source-system administrators and auditors.

Workflow and decision points

01

Minimize at source

Remove tokens, keys and unnecessary sensitive data before sealing; do not edit sealed content to hide source mistakes.

02

Close window

Retain start/end times, time zone, source, sequence range and row count; distinguish late arrivals.

03

Reconcile inventory

Check sequence gaps, duplicate batches and file digests. The design uses Kafka for events/references, not implicitly for entire logs.

04

Link traceability

Link source batch ID to archiveId and evidence. Corrective batches use new IDs linked to predecessors.

States, guards and authority

CurrentGuardActorNextArtifact / recovery
Open window [model]Freeze source, sequence and timeSOC / source systemClosed batch [model]Retain sequence range/count; source time is not inherently trusted.
Closed batch [model]Complete inventory and matching digestsBatch intakeAccepted / quarantined [model]Sequence gaps differ from duplicates; retain distinct reasons.
Preserved [model]Late data or source correctionLog ownerSupplemental batch [model]New batch links the old; sealed bytes are never overwritten.

Exceptions and controls

SituationActionBoundary
Sequence gapQuarantine for source reconciliation.A digest does not establish completeness.
Late arrivalCreate a linked supplemental batch.Do not overwrite an evidenced batch.
Source clock skewRetain source and intake times separately.Do not treat source time as trusted time.
Authorization, approval and recovery

Seal before hashing; retain time zone and source order. Kafka carries events and references, not binary archive payloads by default.

Quarantine missing or duplicate batches for source reconciliation. Issue a corrected batch with a new ID linked to the previous one.

Reconciliation artifacts and acceptance

Reconcile source sequence, time zone, window, row count and batch ID; corrected batches use new IDs linked to predecessors.

Integration and data contract

APIApplication scopeDocumentation
POST /v1/archivesarchives:writeArchive API
GET /v1/archivesarchives:readArchive API
GET /v1/archives/{archiveId}archives:readArchive API
GET /v1/archives/{archiveId}/statusarchives:readArchive API
Technical input and references
ElementDefinition
InputClosed log batch, time range, source, record count, manifest and sensitive-data minimization policy.
OutputEvidence for an immutable batch with source-event to archiveId traceability; an open log stream is not a finalized batch.

Execute and reconcile a scenario

ElementAction
Synthetic IDlog-window-test-001
TaskClose window/source sequence range; record timezone, checkpoint and batch members.
Acceptance caseDetect sequence gaps/duplicate batches even when remaining files hash correctly.

These are business test criteria; synthetic packages alone do not establish backend execution or valid ERS.

Next steps

Search LTANS documentation

Expanded illustration