Mobile-ID Quantum Safe
Open Demo Lab

PRODUCT MANUAL

QuantumSafe Evidence Shield
Technical usage guide

Augment existing PDF, CMS, XML and software artifacts with versioned quantum-safe evidence while preserving the original business object and verification history.

Open demoProduct profile

OVERVIEW

QuantumSafe Evidence Shield

Long-lived documents and software may need to remain verifiable after classical signatures, certificates or timestamp profiles are no longer acceptable.

WORKFLOW

  1. 01 Inspect the original artifact and existing signatures
  2. 02 Build a canonical hash and evidence manifest
  3. 03 Apply approved hybrid/PQC signature or evidence augmentation
  4. 04 Add trusted time, certificate status and policy identifiers
  5. 05 Package original object plus renewal-ready evidence
  6. 06 Verify now and schedule evidence renewal before expiry

COMPONENT REFERENCE

COMPONENT ARCHITECTURE

Preserve the original artifact while assurance evidence evolves over time.

Inspection, canonical binding, quantum-safe evidence, trusted time and independent verification remain separately identifiable and renewable.

SOURCE INPUTS
PDFXMLCMSSoftware artifact
01

Artifact Inspector

Examines the original object, existing signatures, certificate path and current validation state.

SOURCE BOUNDARY
02

Canonical Evidence Manifest

Binds object hashes, identifiers, signer intent, transaction context and policy under a versioned manifest.

BINDING LAYER
03

Hybrid/PQC Evidence Layer

Adds project-approved classical, hybrid or PQC evidence without silently changing the original business object.

EVIDENCE LAYER
04

Trusted Time & Validation Collector

Collects RFC 3161 time, certificate chain, OCSP/CRL and verifier facts from approved trust services.

EXTERNAL TRUST
Protected evidence package
05

Renewal Scheduler

Monitors evidence lifetime and creates controlled renewal events before validation material becomes insufficient.

PRESERVATION CONTROL
06

Independent Verification Portal

Replays verification independently, exposes evidence facts and exports a signed validation report.

INDEPENDENT PATH
GOVERNED OUTPUTS
Verification reportRenewal eventArchive-ready export

INTERFACES

  • PDF/PAdES
  • CMS/CAdES
  • XML/XAdES
  • ASiC containers
  • RFC 3161 / OCSP / CRL
  • Verification REST API

LIMITATIONS & ACCEPTANCE

  • The public site describes the evidence architecture; exact augmentation format is release-profile specific.
  • Adding evidence does not retroactively strengthen the original signer authentication or eliminate the need to preserve original validation material.
  • Legacy verifier behavior must be tested for every target document and software ecosystem.