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

Security Controls

Map risks, target controls, owners and security-acceptance evidence for each LTANS deployment.

From risk to control evidence

This is a control design and acceptance checklist. Organizational ISO certification does not replace LTANS control-enforcement evidence for a specific environment.

RiskTarget controlOwnerRequired evidence
Cross-tenant accessOwning-service object authorization, beyond the gateway.Identity + service ownerValid-token cross-tenant access must be denied; retain decision, not token.
SSRF through dataReference/webhookPolicy allowlist, destination IP and redirects; recheck at connection.Storage / Webhook + networkBlock unauthorized internal destinations and out-of-scope DNS/redirects; no backend test supplied.
Bytes changed after freezeDigest actual bytes and use revisioned object references.Archive + StorageOne-byte modification fails reconciliation; never update the digest to hide edits.
Privileged misuseSeparate author/approve, scope and decision audit.Policy owner + securityTest self-approval/scope escalation; claim enforcement only after environment acceptance.
Data/key disclosureStore authorization, externalized secrets and minimized logs.Storage + key custodianReview logs/exports, key grants and authorized decryption recovery.
Evidence-history lossImmutable revisions and consistent recovery points.Evidence + OperationsRestore history/digests/material, not merely server uptime.
Replay/out-of-order deliveryWebhook signatures, inbox and current-state reconciliation.Webhook + receiverOne eventId cannot repeat effects; old events cannot regress state.

Complete security due diligence

Next steps

Search LTANS documentation

Expanded illustration