Sovereign cryptographic assurance · Roadmap
Discover where cryptography is used, connect assets to owners and dependencies, prioritise exposure, and manage an evidence-based transition towards customer-approved post-quantum or hybrid protocol profiles.
Status: Roadmap. This application is being developed for open-source release. Its repository, OSI-approved software licence, model-specific terms, version, provenance and supported deployment modes will be published with the applicable release.
Planned replacement scope
Roadmap scope: designed to replace or consolidate cryptographic asset-inventory, certificate and key-management visibility, protocol-governance and post-quantum migration-planning tools. Inventory and migration evidence would support decisions; the product would not by itself make an unassessed system quantum-safe.
Core capabilities
Exact coverage, deployment requirements and limitations are documented for the selected version and use case.
Discover and catalogue relevant algorithms, libraries, protocols, certificates, keys, endpoints and dependencies with owners and deployment context.
Connect cryptographic use to applications, data, suppliers and lifecycle constraints so teams can identify migration blockers and priorities.
Define organisation-approved post-quantum or hybrid protocol profiles, permitted transitions, exceptions and target deployment states.
Plan, test, approve, stage and track replacements with evidence, accountable ownership and rollback conditions.
Reassess authorised environments for outdated or unexpected cryptography and produce reviewable status and exception evidence.
Product boundary
PQC manages cryptographic inventory and migration evidence. AI Defense contributes relevant asset and supply-chain context. Identity & Access Management and application owners remain responsible for operational key, certificate and access controls.
Adoption outcome
Start with a bounded system, validate discovery coverage, identify dependencies and approved target profiles, then test migration and rollback before production change.
Sovereignty matrix
Product-specific answers are established through the deployment architecture and dated evidence record.
Connected Roadmap capabilities
Every connected capability shown here is part of the current Roadmap.
A practical first step
Start with a bounded system, validate discovery coverage, identify dependencies and approved target profiles, then test migration and rollback before production change.
