TEST CORPUS & COMPATIBILITY

QuantumSafe Data Shield
QS-DSS-2026.07

Browser, mobile, gateway, email and HSM combinations require release-specific validation.

COMPATIBILITY MANIFEST

Every result is bound to an exact version and environment.

DimensionCurrent public statementPublication rule
Input / artifact formatsJavaScript/WebAssembly SDK, REST/OpenAPI, Email/file connectorDeclared in public profile
Runtime / platformProject-specificMust be fixed in the evaluation manifest
Cryptographic profileVersioned project profileNo blanket PQC support claim
Evidence outputJSON/CSV/PDF or product-specific artifactMust include profile ID and test time
Independent assessmentNot published unless explicitly linkedPublication gate remains open

REFERENCE TEST CORPUS

Product-specific acceptance scenarios.

01

Protected-field selection

02

Origin and transaction binding

03

Replay and nonce rejection

04

Recipient-key rotation

05

No-plaintext gateway logging

REQUIRED MANIFEST FIELDS

  • Product and public-profile ID
  • Component, firmware, SDK and API versions
  • Operating system, runtime, browser or appliance version
  • Algorithm/profile identifiers and parameter sets
  • Input corpus checksum and expected result
  • Tester, timestamp, environment and evidence links

KNOWN BOUNDARY

Browser, mobile, gateway, email and HSM combinations require release-specific validation.

Independent penetration test and source review are not yet published.

CLOSE THE GATE

QuantumSafe Data Shield

Run the evaluation pack, publish the manifest and map every support claim to evidence.