What this family supports.
Quantum-safe migration instruments for crypto inventories, CBOM drafts, protocol pressure, suppliers and roadmap evidence.
Quantum-safe migration instruments for crypto inventories, CBOM drafts, protocol pressure, suppliers and roadmap evidence.
Quantum-safe migration instruments for crypto inventories, CBOM drafts, protocol pressure, suppliers and roadmap evidence.
Inputs are user-entered assumptions or evidence states. The tools do not verify live systems, datasets, vendors, clinical claims, vulnerabilities or scientific measurements.
Outputs are preliminary orientation artifacts for human review. They are not certification, legal advice, medical advice, engineering sign-off or compliance approval.
Classifies quantum-safe readiness stage and identifies the first evidence actions for post-quantum transition.
Maps user-entered assets, algorithms, protocols and data lifetimes into a quantum-vulnerable dependency inventory.
Builds a manual cryptographic bill of materials draft with algorithms, operations, owners, evidence and migration candidates.
Estimates harvest-now-decrypt-later urgency from confidentiality lifetime, capture feasibility and migration lead time.
Creates a phased post-quantum migration roadmap from inventory, supplier, protocol and governance inputs.
Generates supplier questions and evidence requests for post-quantum readiness and crypto-agility.
Produces a maturity-band view of quantum-safe readiness with an unknown-evidence penalty and confidence level.
Scores protocol migration pressure from exposure, difficulty, business criticality and data lifetime.
Distinguishes PQC migration, QKD infrastructure assessment and specialized hybrid scenarios.
Compares vendor evidence for crypto inventory, algorithm agility, hybrid support, testing and contractual commitments.
Creates PQC-related contract language themes and evidence topics for legal and procurement review.
Version policy: each instrument has a version, maturity state, assumptions, limitations, example input, example output and export formats. Method notes should be updated when scoring logic, input taxonomy or source families change.