Quantum Threat Briefing
$5,000
Fixed fee · 90-min session · 1-week delivery
- Executive briefing document (10 pages)
- Board-ready slide deck
- Live Q&A session with the advisory team
- Threat exposure summary for your sector
Quantum Threat Briefing, Crypto-Agility Audit, and separately scoped ongoing advisory. Defined materials, documented findings, and practical migration priorities.
A briefing for your board, an inventory for your engineers, or guidance for the next phase of migration. Start with the questions your team needs to answer.
Defined scope. Clear boundaries. Our offered assessments are passive or offline and report-only. Live scanning and exploitation are outside this scope. Controlled demonstrations are distinct from production findings; live quantum hardware requires separate written authorization.
$5,000
Fixed fee · 90-min session · 1-week delivery
$25,000
Fixed fee · 3-week engagement · full estate
Scoped
After assessment · Monthly or quarterly cadence
Assessment scope, authority, data handling, and deliverables are agreed before work begins. Follow-on advisory is separately scoped; no outcome or compliance guarantee is implied.
Review agreed architecture documentation and cryptographic materials: TLS configurations, signing systems, storage encryption, and third-party dependencies.
Relate data retention needs and cryptographic dependencies to modeled quantum risk. Make assumptions and limits visible.
Document the in-scope algorithms, key sizes, dependencies, and owners.
Develop a prioritized roadmap mapped to NIST ML-KEM, ML-DSA, and SLH-DSA standards.
A technical report for engineers and an executive summary for decision-makers, followed by a 30-day review session.
Quantum Penetration Test · $25,000 fixed · up to 60 days. Controlled circuit demonstrations and documented exposure modeling. Live QPU validation requires a signed addendum and provider authorization.
$750 fixed · one week. The full fee credits toward the $2,500 founding / $5,000 standard Governance & Workflow Sprint if the diagnostic surfaces work in that scope.
Internal hardware validation and provider routing are distinct from customer findings or production-key attacks. Public artifacts describe their own methods and assumptions.