VERIFY · ASSURANCE PLATFORM / MANAGED SERVICE

QuantumSafe Verification Portal
Solution architecture

Inspect certificates, signatures, timestamps, chains, status evidence and algorithm identifiers.

CUSTOMER PROBLEM

Inspect certificates, signatures, timestamps, chains, status evidence and algorithm identifiers.

Relying parties need a neutral interface to inspect certificates, algorithms, signatures, timestamps and evidence without trusting a marketing statement.

Solution architecture
Portfolio class
Assurance platform / managed service
Public profile
2026.07
Version rule
Confirmed in quotation / release record

PRODUCT-SPECIFIC IMPLEMENTATION FLOW

How QuantumSafe Verification Portal operates from input to evidence.

Certificates, PDF/CMS/XML, OCSP/CRL, timestamps and approved validation engines. Signed verification report, engine/version record, policy result and limitation disclosure.

01

User uploads artifact or certificate

Certificate, chain and OID inspection

02

Portal identifies format and algorithm OIDs

Classical, hybrid and approved PQC verification

03

Validation engine builds chain and status context

Timestamp, OCSP and CRL validation

04

Verifier checks signature, timestamp and policy

Artifact and environment manifest display

05

Portal explains failures and interoperability

Machine-readable and human-readable reports

06

Signed report is issued with engine manifest

Known-limitations and verifier-behavior disclosure

NAMED COMPONENTS AND RESPONSIBILITIES

What QuantumSafe Verification Portal contains and what each component does.

The descriptions below state concrete technical behaviour rather than generic support language.

01

Certificate, chain and OID inspection

Parses certificates and chains to display subject, issuer, key type, parameter set, extensions, policy OIDs and trust-anchor decision.

02

Classical, hybrid and approved PQC verification

Runs only registered verification profiles for classical, hybrid or approved PQC artifacts and identifies each component result separately.

03

Timestamp, OCSP and CRL validation

Validates timestamps, OCSP and CRL responses against the recorded validation time, nonce, issuer and freshness policy.

04

Artifact and environment manifest display

Shows artifact hash, parser version, validation engine, trust list, policy, environment and external evidence used for the decision.

05

Machine-readable and human-readable reports

Produces a human explanation and a signed machine-readable report so users and systems can consume the same verification outcome.

06

Known-limitations and verifier-behavior disclosure

Discloses unsupported formats, parser limits, policy uncertainty and differences observed between external verifiers instead of returning a generic pass/fail.

CUSTOMER OUTCOMES
  • Human-readable verification
  • Machine-verifiable report
  • Interoperability diagnostics
INTEGRATION BOUNDARY

Certificates, PDF/CMS/XML, OCSP/CRL, timestamps and approved validation engines.

DEPLOYMENT PATTERNS

Customer test environment

The customer supplies the exact manifest and target artifacts; results remain scoped to that environment.

Joint assurance lab

Mobile-ID and product owners execute reproducible tests, triage findings and approve publication together.

Managed evidence service

Scheduled verification, benchmark, evidence refresh and reporting operate under defined retention and access policy.

EVIDENCE REQUIRED
  • Signed verification report, engine/version record, policy result and limitation disclosure.
  • Version and configuration manifest for: Certificates, PDF/CMS/XML, OCSP/CRL, timestamps and approved validation engines.
  • Negative, failure and recovery tests for “Portal explains failures and interoperability” and “Signed report is issued with engine manifest”.
  • Signed acceptance record, accountable owner, published limitations and next review date.
STANDARDS & PROFILES
  • X.509 / PKIX
  • CMS / PDF / XML signatures
  • RFC 3161
  • OCSP / CRL

PRODUCT-SPECIFIC BOUNDARIES

Conditions that must remain true for QuantumSafe Verification Portal.

These points come from the product profile, not from a shared disclaimer.

NEXT STEP

Review the solution architecture: QuantumSafe Verification Portal

Confirm trust boundaries, interfaces, threat model and productization path.