CSR and profile validation
TEST CORPUS & COMPATIBILITY
QuantumSafe Certificate Fabric
QS-CF-2026.07
Exact PQC/hybrid profile support depends on approved standards, HSM/provider and relying-party versions.
COMPATIBILITY MANIFEST
Every result is bound to an exact version and environment.
| Dimension | Current public statement | Publication rule |
|---|---|---|
| Input / artifact formats | X.509 / PKIX, CMP / EST / SCEP / ACME profiles, OCSP / CRL | 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.
Certificate issuance and chain building
CRL/OCSP freshness and status
Timestamp and LT/LTA integration
Relying-party parser compatibility
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
Exact PQC/hybrid profile support depends on approved standards, HSM/provider and relying-party versions.
Certificate-profile and PKI integration assessment is project-specific; no blanket PQC validation claim.
CLOSE THE GATE
QuantumSafe Certificate Fabric
Run the evaluation pack, publish the manifest and map every support claim to evidence.
