Platform Documentation

Continuous Cryptographic Posture Management

QuantumBlue is not just a scanner. It is an operational platform that discovers your cryptographic assets, prioritizes HNDL risk, blocks new debt at the source, orchestrates reversible migrations, and generates the Proof of Migration your auditors need.

The 4 Capabilities That Differentiate QuantumBlue

CAPABILITY 1Zero-Instrumentation Runtime Discovery (eBPF)

Most competitors build CBOMs by scanning source code, file systems, or network traffic — which is blind to what's actually executing in production. QuantumBlue's eBPF-based runtime sensor hooks into the Linux kernel to observe real cryptographic library calls (OpenSSL, BoringSSL, Java Crypto) as they happen, without requiring developers to install language-specific agents or alter their code.

Why this matters:
  Static scanners guess based on code on disk.
  eBPF proves what is actually running in production.
  The resulting Cryptographic Asset Graph is undeniable evidence
  for auditors, CISOs, and migration planning.}
eBPF kernel probeNo code changes requiredOpenSSL / BoringSSL / Java CryptoCryptographic Asset GraphProduction ground truth
CAPABILITY 2Shift-Left Cryptographic Guardrail (CI/CD Blocker)

While you're mapping production debt, developers are writing new code with hardcoded RSA-2048. QuantumBlue integrates directly with GitHub and GitLab to block pull requests that introduce legacy cryptography — before it ever reaches production. Become the tool that prevents cryptographic debt from entering your codebase, not just the dashboard that reports on it after the fact.

Supported integrations:
  GitHub App — blocks PRs introducing RSA-2048, ECDSA, SHA-1, etc.
  GitLab MR integration — same gate for GitLab-based workflows
  CLI in CI — qb guardrail --source . for any pipeline
  Configurable policy — fail on legacy, warn on deprecated, allow PQC

Phased rollout: Phase 1 blocks PRs with legacy crypto.
Phase 2 adds auto-remediation suggestions via the AI Copilot.}
GitHub integrationGitLab integrationCLI CI modePR blockingPrevents new debtPhase 4: AI auto-remediation
CAPABILITY 3Automated Rollback — Fearless, Reversible Migration

The biggest fear enterprise IT has about PQC migration isn't algorithm strength — it's that ML-KEM or ML-DSA certificates (with massive key sizes) will break legacy load balancers, drop packets, or crash applications. QuantumBlue integrates with Envoy, Istio, and Kong to dynamically route traffic to PQC endpoints, then monitors error rates in real time. If error thresholds spike, one click reverts to ECDSA/RSA — instantly.

Supported gateways:
  Envoy Proxy — route PQC traffic, monitor 5xx/error rates
  Istio — service mesh PQC rollout with automatic rollback triggers
  Kong — API gateway PQC tunnel management

Rollback safety net:
  Real-time error rate monitoring
  One-click revert to classical algorithms
  Migration campaign audit trail
  Proof of Migration artifact for every completed migration

Positioning: "Fearless, reversible migration wins enterprise deals
faster than compliance checklists."
Envoy integrationIstio integrationKong integrationReal-time error monitoringOne-click rollbackProof of MigrationPhase 3: Migration campaigns
CAPABILITY 4DSPM Integration for Automated HNDL Prioritization

HNDL prioritization is only as good as the data-sensitivity data behind it. QuantumBlue integrates with leading Data Security Posture Management (DSPM) tools via API. When the DSPM flags a database as containing "PII with 10-year compliance retention," QuantumBlue automatically ingests that tag, sees the database is using AES-128, and elevates it to a P0 HNDL risk. No manual tagging required.

How it works:
  1. DSPM flags asset: "PII, 10-year retention, regulated"
  2. QuantumBlue ingests the sensitivity tag via API
  3. QuantumBlue checks the encryption in use (e.g. AES-128)
  4. Risk score = Data Sensitivity × Retention × Weakness
  5. Asset is elevated to P0 HNDL priority in the dashboard

Why this matters:
  HNDL exposure = Data value × Time-to-quantum × Retention
  Manual tagging stalls. DSPM integration automates it.
  The result is a prioritized migration queue that reflects
  real business risk, not just cryptographic weakness.

Phase 4: AI Copilot enriches this with remediation guidance.}
DSPM API integrationPII auto-taggingRetention-aware riskHNDL prioritizationP0 risk elevationPhase 4: AI Copilot

Core Platform

Quantum-Safe Core

NIST-approved ML-DSA-65 (FIPS 204) and ML-KEM-768 (FIPS 203) for signatures, key encapsulation, and hybrid transitional architectures.

Immutable Audit Logs

Every cryptographic operation immutably logged. RFC 3161 trusted timestamping. Chain-of-custody continuity for compliance and evidentiary workflows.

Cryptographic Asset Graph

eBPF runtime discovery builds an undeniable graph of what crypto is actually running in production — not what static analysis guesses is there.

CBOM Pipeline

Automated Cryptographic Bill of Materials generation. CycloneDX 1.6 schema. Source scanning plus runtime discovery for complete coverage.

Shift-Left Guardrail

GitHub/GitLab integration blocks PRs that introduce legacy cryptography. Stop the bleeding before new debt reaches production.

Migration Engine + Rollback

Orchestrate PQC migrations across Envoy, Istio, and Kong with real-time error monitoring and one-click rollback safety nets.

API & CLI

POST/api/pqc-keys

Generates a pure ML-DSA-65 (NIST FIPS 204) public and private keypair for post-quantum digital signatures, or hybrid X25519MLKEM768 keypairs for key encapsulation.

curl -X POST https://quantum-blue.in/api/pqc-keys \
  -H "Authorization: Bearer ***" \
  -H "Content-Type: application/json"
SPECQuantumBlue Envelope Format V4 (0x04)

QuantumBlue's authenticated file format combines Cloudflare CIRCL X25519MLKEM768 hybrid key encapsulation (1,120 bytes), RFC 5869 HKDF-SHA256 key derivation with canonical length-prefixing, AES-256-GCM symmetric encryption, and finalized NIST FIPS 204 ML-DSA-65 digital signatures (3,309 bytes).

• Total Wire Size: 4,462 + N bytes (for plaintext length N)
• Bytes 0–3: Magic "PQC!" (0x50 0x51 0x43 0x21)
• Byte 4: Envelope Version 0x04 (strict dispatch, zero cross-version fallback)
• Bytes 5–1092: ML-KEM-768 Ciphertext (1,088 bytes, NIST FIPS 203)
• Bytes 1093–1124: Ephemeral X25519 Public Key (32 bytes)
• Bytes 1125–1136: Master AES-GCM Nonce (12 bytes)
• Bytes 1137 onward: AES-256-GCM Payload + 16-byte Tag
• Final 3,309 Bytes: ML-DSA-65 Signature over complete body (NIST FIPS 204)

Notice: QuantumBlue implements the NIST FIPS 203 and FIPS 204 algorithm standards. Algorithm standard implementation is distinct from FIPS 140-3 laboratory cryptographic module certification.

POST/api/sign

Cryptographically signs a payload using your ML-DSA-65 private key. Supports hybrid signatures (ML-DSA-65 + Ed25519) for classical verification compatibility.

curl -X POST https://quantum-blue.in/api/sign \
  -H "Authorization: Bearer ***" \
  -H "Content-Type: application/json" \
  -d '{"data": "base64_payload", "private_key": "your_private_key"}'
POST/api/verify

Verifies a digital signature against the original payload and public key. Supports both pure PQC and hybrid signature verification.

curl -X POST https://quantum-blue.in/api/verify \
  -H "Authorization: Bearer ***" \
  -H "Content-Type: application/json" \
  -d '{"payload": "original_data", "signature": "sig", "public_key": "pub"}'
POST/api/cbom

Generates a Cryptographic Bill of Materials (CBOM) by scanning source code for legacy primitives. Combines static analysis with eBPF runtime discovery data when available.

curl -X POST https://quantum-blue.in/api/cbom \
  -H "Authorization: Bearer ***" \
  -H "Content-Type: application/json" \
  -d '{"source": "/path/to/code", "runtime": true}'

Roadmap — CCPM Rollout Phases

Phase 1External Attack Surface ScannerLive now

Lead-generation engine. Anyone types in a domain and gets a terrifyingly accurate TLS/Certificate posture report with HNDL risk grading. Free, no login required. This is the top of the funnel.

LiveLead-genTLS scanningHNDL grading
Phase 2eBPF Runtime Discovery + Cryptographic Asset GraphIn development

Prove your tech is superior to legacy scanners. The eBPF sensor hooks into the Linux kernel to observe real cryptographic library calls in production — no agents, no code changes. Combined with the Cryptographic Asset Graph, this delivers undeniable ground truth that static tools can't match.

eBPFAsset GraphRuntime discoveryNo instrumentation
Phase 3Migration Engine + Proof of Migration + Automated RollbackPlanned

Orchestrate PQC migrations across Envoy, Istio, and Kong with one-click rollback safety nets. Generate Proof of Migration artifacts for every completed migration — the evidence your auditors and CISOs need to close the loop.

MigrationRollbackProof of MigrationEnvoy/Istio/Kong
Phase 4AI Copilot + DSPM Integrations + Shift-Left CI/CD BlockersPlanned

Expand into the AI Copilot for remediation guidance, DSPM API integrations for automated HNDL prioritization, and GitHub/GitLab shift-left blockers that prevent new cryptographic debt from entering production. The platform becomes an essential developer security tool, not just an auditing dashboard.

AI CopilotDSPMGitHub/GitLabShift-leftCI/CD

Ready to map your cryptographic posture?

Start with the free External Attack Surface Scanner. Then sign up for the full CCPM platform.