Boab import path
Bring in Boab JSON, Markdown readiness reports and CycloneDX 1.6 CBOM outputs so cryptographic assets become part of the assurance record.
Compliance On DemandMenu
Post-quantum readiness
Post-quantum readiness evidence for Australian assurance teams
Compliance On Demand uses Boab as the cryptographic inventory source for post-quantum readiness work. Teams can review vulnerable algorithms, TLS endpoints, certificates, PQC status, priority scores, migration tiers and ASD milestone plans inside the same self-hosted assurance workspace.
What this page covers
Specific product capability, without vague compliance automation claims.
Import Boab PQC inventory outputs, surface quantum-vulnerable assets, track ASD LATICE tiers and keep CBOM evidence beside control work.
ASD LATICE planning
Track priority, triage tier and migration windows against the 2026 transition plan, 2028 implementation and 2030 completion milestones.
Evidence for review
Keep PQC status, quantum-vulnerable counts, asset type mix and recommended actions visible for internal reviews and assessor conversations.
Operational proof
What buyers and assessors should be able to verify.
These are the concrete operating claims this page should support in search results, sales calls and evaluator conversations.
01
Boab scans codebases, TLS endpoints and certificate stores for cryptographic inventory
02
Boab classifies assets as quantum-vulnerable, PQ/T hybrid, PQC-resistant, symmetric OK or unknown
03
Reports can include JSON, CycloneDX 1.6 CBOM and board-ready Markdown outputs
04
Priority scoring can reflect algorithm vulnerability, harvest-now-decrypt-later exposure, data sensitivity, system criticality and migration difficulty
05
ASD-aligned milestones cover refined transition planning by end of 2026, implementation by 2028 and completion by 2030
Questions
Common questions about post-quantum readiness.
What is Boab used for?
Boab is used as the PQC inventory source. It scans codebases, TLS endpoints and certificate stores, deduplicates cryptographic assets, scores them and exports JSON, CycloneDX CBOM and Markdown readiness reports.
Does this replace cryptographic migration work?
No. It helps teams see and evidence the work. Migration decisions, vendor upgrades, certificate replacement and implementation remain controlled change activities.
Why keep PQC readiness inside Compliance On Demand?
Post-quantum readiness affects controls, risks, vendors, evidence and audit conversations. Keeping Boab outputs in the same self-hosted workspace gives assessors context without moving cryptographic inventory into a SaaS control plane.
Product briefing
Bring this assurance work into a self-hosted product review.
Share your deployment boundary, frameworks and evidence workflow, and we will talk through fit without generic compliance theatre.