Freeze hardware and software manifest
Key generation, KEM, sign and verify measurements
PERF · ASSURANCE PLATFORM / MANAGED SERVICE
Measure latency, throughput, object size, memory and network impact for classical, hybrid and PQC profiles.
CUSTOMER PROBLEM
PQC performance claims are meaningless without a reproducible environment, parameter set, sample count and distribution statistics.
PRODUCT-SPECIFIC IMPLEMENTATION FLOW
Token, HSM, server, client, network and document test environments. Test methodology, environment manifest, raw results, charts and decision summary.
Key generation, KEM, sign and verify measurements
P50/P95/P99 latency and throughput
Key, ciphertext, signature and certificate sizes
TLS/CMS/PDF payload impact
Token, HSM, server and client profiles
Raw data, method and limitations publication
NAMED COMPONENTS AND RESPONSIBILITIES
The descriptions below state concrete technical behaviour rather than generic support language.
Measures key generation, encapsulation, decapsulation, sign and verify with explicit algorithm, parameter, backend and concurrency settings.
Reports P50, P95 and P99 latency together with throughput, error rate, warm-up, run count and statistical treatment.
Records public/private key, ciphertext, signature, certificate and protocol-object sizes to expose storage and network consequences.
Measures how profiles change TLS handshakes, CMS/PDF objects, memory use, CPU, connection rate and application response time.
Runs separate token, HSM, server and client profiles so hardware latency is not hidden inside aggregate application results.
Publishes test method, environment manifest, raw data, charts, limitations and enough scripts to reproduce the reported figures.
Token, HSM, server, client, network and document test environments.
The customer supplies the exact manifest and target artifacts; results remain scoped to that environment.
Mobile-ID and product owners execute reproducible tests, triage findings and approve publication together.
Scheduled verification, benchmark, evidence refresh and reporting operate under defined retention and access policy.
PRODUCT-SPECIFIC BOUNDARIES
These points come from the product profile, not from a shared disclaimer.
NEXT STEP
Review the exact operating model, interfaces and evidence needed for deployment.