MOBILE-ID · TRUSTED LTANS

Trust service providers

Preserve CA/TSA/signing requests and transaction batches without including private keys in logs.

Problem and records to preserve

Operational logs alone do not provide independent preservation evidence across service generations.

SYNTHETIC CASE

Synthetic trust-transaction batch

TRUST-SYN-001

Element	Illustrative scope
Decision makers / users	CA, TSA, remote-signing providers and trust-service operators
Source system	CA / TSA / signing system
Revision	Bind batch ID, transaction range and policy; exclude secret keys.
Record relationship	Retain source transaction IDs, policy references and permitted material.

Sector-specific record journey

Close batch

Freeze authorized CA/TSA/signing transaction sets and relevant policy revisions.

Minimize data

Remove secrets/unnecessary data before sealing; exclude private keys and access tokens.

Preserve

Preserve authorized output bytes and validation material; provider certification does not certify LTANS.

Reconcile source IDs

Map source transaction IDs to archiveId; detect missing/duplicate batches independently of filenames.

Audit export

Export assessment-scoped samples with policy/context; conformance requires separate assessment.

Delivered artifacts

Recipient	Artifact
Source system	Intake receipts, source/revision-to-`archiveId`/`jobId` mappings and per-item errors.
Package recipient	Transaction inventory, record mapping and assessment package.
Record owner / operations	Completed/outstanding inventory, applied decisions and report references; no automatic legal conclusion.

Rights, retention and deployment

Private keys and access tokens are excluded from preserved records.

CP/CPS and TSA policies belong to source services; LTANS preservation policy defines a separate responsibility layer.

Retention authority and exit

The owner must approve the retention authority and trigger for this record class: A closed CA/TSA/signing transaction batch approved for preservation.

Archival Period & Retention Legal Hold Deployment Model Comparison

Sample dossier and tests

Synthetic text files exercise inventory and hashing; they are not signed contracts, real records or ERS/XMLERS.

Download synthetic dossier

Test	Expected outcome
Intact	File inventory, size and SHA-256 match the manifest.
Missing / changed bytes	The verifier rejects the package without claiming inventory success.
Sector business case	Exported samples trace to transactions/old policies without exposing secrets.

Sample package and independent checks Integration test plan

Scope a PoC for this dossier

Test missing batches, missing validation material and policy-controlled TSA changes; retain time-specific trust-context results.

Prepare a sector-specific request

Trust Infrastructure CA, TSA and preservation policies

Finalization point and specific acceptance

Control point	Requirement
Source event	A closed CA/TSA/signing transaction batch approved for preservation.
Revision / decision	Bind batch ID, transaction range and policy; exclude secret keys.
Test and expected result	Detect transaction-range gaps; sample logs contain no tokens or private keys.

Sample inventory/hashing checks bytes only. Authorization, decision and state cases must run in the provisioned test environment before business acceptance.

End-to-end reference dossier Integration test plan Design a Trusted LTANS PoC

Source-system handoff record

Information	Value / decision
Record	TRUST-SYN-001
Source system	CA / TSA / signing system
Revision relationship	Retain source transaction IDs, policy references and permitted material.
Recipient and output	Transaction inventory, record mapping and assessment package.
Rights and authority	Private keys and access tokens are excluded from preserved records.
Required rejection test	Exported samples trace to transactions/old policies without exposing secrets.

Sector information is source business metadata, not automatically new REST fields. Agree field mapping and ownership before a PoC.