Protected-field selection
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.
| Dimension | Current public statement | Publication rule |
|---|---|---|
| Input / artifact formats | JavaScript/WebAssembly SDK, REST/OpenAPI, Email/file connector | Declared in public profile |
| Runtime / platform | Project-specific | Must be fixed in the evaluation manifest |
| Cryptographic profile | Versioned project profile | No blanket PQC support claim |
| Evidence output | JSON/CSV/PDF or product-specific artifact | Must include profile ID and test time |
| Independent assessment | Not published unless explicitly linked | Publication gate remains open |
REFERENCE TEST CORPUS
Product-specific acceptance scenarios.
Origin and transaction binding
Replay and nonce rejection
Recipient-key rotation
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.
