PERF · ASSURANCE PLATFORM / MANAGED SERVICE

QuantumSafe Benchmark Center
Available

Measure latency, throughput, object size, memory and network impact for classical, hybrid and PQC profiles.

CUSTOMER PROBLEM

Measure latency, throughput, object size, memory and network impact for classical, hybrid and PQC profiles.

PQC performance claims are meaningless without a reproducible environment, parameter set, sample count and distribution statistics.

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

PRODUCT-SPECIFIC IMPLEMENTATION FLOW

How QuantumSafe Benchmark Center operates from input to evidence.

Token, HSM, server, client, network and document test environments. Test methodology, environment manifest, raw results, charts and decision summary.

01

Freeze hardware and software manifest

Key generation, KEM, sign and verify measurements

02

Warm up and calibrate test harness

P50/P95/P99 latency and throughput

03

Run repeated cryptographic workloads

Key, ciphertext, signature and certificate sizes

04

Capture latency, throughput and sizes

TLS/CMS/PDF payload impact

05

Analyze percentiles and resource use

Token, HSM, server and client profiles

06

Publish raw data, method and limits

Raw data, method and limitations publication

NAMED COMPONENTS AND RESPONSIBILITIES

What QuantumSafe Benchmark Center contains and what each component does.

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

01

Key generation, KEM, sign and verify measurements

Measures key generation, encapsulation, decapsulation, sign and verify with explicit algorithm, parameter, backend and concurrency settings.

02

P50/P95/P99 latency and throughput

Reports P50, P95 and P99 latency together with throughput, error rate, warm-up, run count and statistical treatment.

03

Key, ciphertext, signature and certificate sizes

Records public/private key, ciphertext, signature, certificate and protocol-object sizes to expose storage and network consequences.

04

TLS/CMS/PDF payload impact

Measures how profiles change TLS handshakes, CMS/PDF objects, memory use, CPU, connection rate and application response time.

05

Token, HSM, server and client profiles

Runs separate token, HSM, server and client profiles so hardware latency is not hidden inside aggregate application results.

06

Raw data, method and limitations publication

Publishes test method, environment manifest, raw data, charts, limitations and enough scripts to reproduce the reported figures.

CUSTOMER OUTCOMES
  • P50/P95/P99 metrics
  • Size and capacity model
  • Deployment sizing recommendation
INTEGRATION BOUNDARY

Token, HSM, server, client, network and document test environments.

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
  • Test methodology, environment manifest, raw results, charts and decision summary.
  • Version and configuration manifest for: Token, HSM, server, client, network and document test environments.
  • Negative, failure and recovery tests for “Analyze percentiles and resource use” and “Publish raw data, method and limits”.
  • Signed acceptance record, accountable owner, published limitations and next review date.
STANDARDS & PROFILES
  • Reproducible benchmarking
  • Statistical distribution reporting
  • Environment manifest
  • Classical / hybrid / PQC comparison

PRODUCT-SPECIFIC BOUNDARIES

Conditions that must remain true for QuantumSafe Benchmark Center.

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

NEXT STEP

Request a product workshop: QuantumSafe Benchmark Center

Review the exact operating model, interfaces and evidence needed for deployment.