Building Your PQC Lab: Trust But Verify Your PQC Ecosystem
summary
Concrete steps for a PQC test environment: run crypto discovery across code, SharePoint and device fleets to inventory PKI, TLS, code‑signing and IoT keys; prioritize high‑risk apps and shift budget to iterative pilots; vet vendors with third‑party attestation and audits (expect SAS‑style accountability); stage implementations slowly—QKD is deferred while hybrid PQC algorithms and HSM integrations roll out. Example numbers: a large bank program cites 22 post‑quantum patents and vendors report hundreds‑to‑thousand percent increases in PQC inquiries. The posture is trust but verify with measured, auditable pilots.
AI-written summary · about
chapters (12)
- 0:00Welcome
- 1:07Introduction
- 2:36Need for PQC lab
- 8:14PQC standards adoption
- 12:49Act now on PQC
- 15:58Best practices for PQC
- 18:48Standards bodies in PQC
- 20:53Wells Fargo PQC case
- 23:19Trust but verify PQC
- 25:08Q&A: PQC action
- 27:36Q&A: PQC budget
- 28:58Closing
related talks
39mPQC in Action: From Global Standards to Secure Deployments
33mExtending or Evolving: Choosing the Path to Quantum Readiness
28mHow The Canadian Government is preparing for PQC
55mPQC in Practice: Why This, Not That?
48mPreparing for Quantum: A Pragmatic Approach towards Readiness
31m2025 is Here - How to get your PQC Readiness Plan Underway
27mThe PQC Landscape: Protocols and Standards
15mOne App at a Time: DigiCert's Practical Playbook for the Post-Quantum Transition