Core Verification
Cobalt PQC
Your quantum migration — formally verified.
Formal verification of post-quantum cryptography implementations against NIST FIPS 203/204/205 specifications. Cobalt PQC proves that Kyber, Dilithium, and Falcon implementations are parameter-correct, constant-time, and safe from timing side-channels. Built for the mandatory migration that governments cannot afford to get wrong.
FIPS 203/204/205
NIST Standards
3
Algorithms
DND/CSEC
Primary Target
§ SPECIFICATION
Input
- C/C++ PQC implementation source
- Target algorithm + variant (kyber768, dilithium3, falcon512, etc.)
- Optional: FIPS compliance scope
Constraints Verified
- Modulus q must match NIST specification exactly
- Polynomial degree n conformance
- No branching on secret material (timing side-channel)
- CSPRNG required for key generation
- Bounded rejection sampling loops
Output
- Parameter correctness proof per constant (q, n, sigma)
- Constant-time violation findings with witness
- RNG quality assessment
- Rejection sampling DoS detection
- FIPS 203/204/205 compliance certificate
§ SAMPLE PROOF ARTIFACT
ARTIFACT // CPQC-KYBER-01FAILURE DETECTED
// SAMPLE PROOF — COBALT PQC ENGINE
Kyber768 — KYBER_Q mismatch detected
TargetCustom Kyber implementation
Condition
KYBER_Q = 3328 ≠ 3329 (FIPS 203 spec)VerdictSAT
SummaryOff-by-one on modulus. Decryption failure rate non-negligible. Breaks IND-CCA2 security proof.
StatusReview-ready
§ FIELD VALIDATION
| # | Target | Vulnerability Class | Status |
|---|---|---|---|
| 01 | Custom Kyber768 Param Mismatch | Param Mismatch | Z3 Certified |
| 02 | Dilithium3 impl Timing Side-Channel | Timing Side-Channel | Detected |
| 03 | Falcon512 impl Unbounded Loop | Unbounded Loop | DoS Risk |
Run Cobalt PQC on your system.
Formal engagement starts with a technical intake. We scope, configure, and deliver a proof artifact within the agreed SLA.