As quantum computing advances, organizations can no longer view post-quantum cryptography as a future project. In this episode of Shielded: The Last Line of Cyber Defense, Konstantinos Karagiannis, Director of Quantum Computing Services at Protiviti, lays out a practical and attacker-focused perspective on preparing for the quantum era. Konstantinos explains why the industry’s fixation on harvest-now-decrypt-later misses the most serious exposure: harvest-now-forge-later, where quantum capability targets the foundation of digital trust through attacks on code signing, software update channels, and blockchain consensus mechanisms. He introduces the emerging Five-Day Rule, informed by recent research indicating that a cryptographically relevant quantum machine could break RSA-2048 in roughly five days, reshaping assumptions about risk and timelines. The discussion expands to the potential instability of blockchain networks, such as proof-of-stake systems reliant on BLS signatures, and the broader implications for market integrity and digital identity. Konstantinos outlines the steps security leaders must take now: identify crown-jewel assets, conduct a full cryptographic inventory, evaluate exposure windows, and demand clear post-quantum plans from vendors. The lesson here is post-quantum migration is a core cyber resilience program that must begin immediately, supported by real posture measurement and actionable timelines.

What You’ll Learn:

• The difference between harvest-now-decrypt-later and harvest-now-forge-later
  
  
• Why code signing and supply-chain trust models are the most critical targets
  
  
• How the five-day rule reframes attacker capability planning
  
  
• Why blockchain & BLS signatures represent high-impact quantum risk
  
  
• Why cryptographically relevant machines will be operated by nation states and major crime rings
  
  
• How PQC migration aligns with existing cyber resilience practices
  
  
• Why crown jewel analysis and crypto inventory must start immediately

• How to evaluate vendors and avoid vague timelines

• Why PQC will become invisible infrastructure within the next few years
  
  

Konstantinos Karagiannis is the Director of Quantum Computing Services at Protiviti, where he leads efforts helping organizations develop real quantum use cases in optimization, machine learning, and simulation, and build realistic paths toward post-quantum cryptography migration. He has been with Protiviti for more than six years, serving previously as Associate Director of Quantum Computing Services. Before Protiviti, Konstantinos spent 13 years at BT, where he served as CTO of the Security Consulting Practice for BT Americas, and earlier as Global Technical Lead for Ethical Hacking, leading red-team operations and advanced cryptographic security testing.

He is the host of Protiviti’s “Post Quantum World” podcast, recently featured at DEFCON with his talk Post-Quantum Panic: When will the cracking begin, and can we detect it? His work focuses on building real quantum computing solutions today while preparing enterprises for the accelerating risks of Q-Day.

Your Roadmap to Quantum Resilience

[05:26] Step 1: Separate HNDL from HNFL -

Konstantinos reframes quantum risk by challenging the narrow industry focus on harvest-now-decrypt-later (HNDL). Decrypting old emails years from now is far less damaging than the real threat: harvest-now-forge-later (HNFL), where attackers use quantum capability to forge identities, break code-signing foundations, and compromise the software supply chain. This shifts the threat from exposure of data to the collapse of trust. When an attacker becomes the authoritative sender such as Microsoft, Apple, a firewall vendor, or a banking platform, the attack scales instantly, bypasses controls, and moves invisibly. This is not about curiosity or espionage; it is about control and reach, where one forged update compromises millions of systems in minutes.
Key Question: Where does your organization implicitly trust signed updates or machine identities, and who validates the integrity of that trust boundary today?

[07:34] Step 2: Apply the Five-Day Rule -

Konstantinos introduces what he calls the Five-Day Rule, based on recent research suggesting that a cryptographically relevant quantum computer could break RSA-2048 using roughly 1,399 logical qubits in around five days. This turns timelines from theoretical decades into an operational window that security and architecture teams must model now. Five days changes the logic of risk, pushing leaders to assess which secrets, keys, and operational identities remain valuable within that timeframe. Financial transactions may expire quickly, but the keys protecting critical infrastructure, identity infrastructures, government systems, long-life intellectual property, or blockchain consensus remain valuable long after they are created.
Key Question: If a key protecting your most sensitive systems could be broken in five days, what response tempo, controls, and contingency paths would you rely on?

[13:28] Step 3: Model Code-Signing Blast Radius -

In his offensive-security perspective, Konstatinos explains that attackers will go after code-signing keys and update channels first, because those are the levers that unlock systemic access. Compromising a single vendor’s signing key turns a routine software update into a global breach. Unlike decrypting a single intercepted email, forging an update affects entire fleets of devices at once, laptops, networking gear, operational systems, and cloud workloads. Supply-chain attacks such as SolarWinds and ShadowHammer demonstrated the scale of trust-based compromise without any quantum capability. Quantum only removes the barrier of needing privileged access. The blast radius is not linear; it grows exponentially.
Key Question: If a major vendor in your environment silently lost control of its signing key, which systems would accept the update without verification, and how quickly would you detect the first signal of compromise?

[16:27] Step 4: Include Blockchain and Market Stability -

Konstantinos expands the discussion beyond enterprise IT into blockchain and digital asset ecosystems. Vulnerable Bitcoin wallets using reused or exposed addresses could be drained by reversing private keys. More significantly, proof-of-stake networks such as Ethereum rely on BLS signatures to establish validator identity and consensus. Breaking those signatures enables attackers to hijack consensus, manipulate network governance, or destabilize price confidence. The consequences go far beyond theft. The damage includes global market volatility, reputational collapse, and loss of institutional trust. Even the credible announcement that such capability exists could move markets, without a full attack ever executing.
Key Question: Where is your organization exposed, directly or indirectly, to digital assets, transaction flows, or reputational dependence on market stability?

[30:53] Step 5: Turn Quantum Risk Into Cyber Resilience -

Konstantinos emphasises that preparing for post-quantum migration begins with security fundamentals: catalogue your cryptography, identify crown-jewel systems, evaluate exposure lifespans, and map relationships between systems, third parties, and identity flows. This reframes PQC from a cryptographic experiment into a disciplined cyber resilience program grounded in visibility and sequencing. Teams must understand what they protect, how long those assets remain valuable, and where control layers converge. This requires more than technical transition; it demands ownership, governance, and prioritisation. A successful roadmap depends on clarity of dependencies before cryptography is swapped.
Key Question: Can you produce a precise and current map of every key, certificate, algorithm, and dependency protecting your core services, and prioritise change based on exposure rather than convenience?

[33:27] Step 6: Demand Specifics from Vendors -

Third-party vendors are central to PQC readiness, but vague statements such as “investigating PQC” provide no protection. Konstatinos urges organizations to demand version-level commitments, timelines, supported PQC algorithms, and attestation paths. Roadmaps must include implementation dates, hybrid-mode support windows, and performance characteristics. Accountability now sits across the entire supply chain, and cryptographic dependencies extend far beyond internal engineering. This is a procurement, legal, and architectural negotiation that requires clarity and documentation, not aspiration. Silence is risk; specificity is control.
Key Question: Do your vendor agreements require measurable and dated PQC milestones, or do you rely on trust without validated evidence?

Episode Resources

• Konstantinos Karagiannis on LinkedIn
  
  
• Protiviti Website

• Johannes Lintzen on LinkedIn 
  
  
• PQShield Website 
  
  

Want exclusive insights on quantum migration?  Stay ahead of the curve. Subscribe to Shielded: The Last Line of Cyber Defense on Apple Podcasts, Spotify, or YouTube Podcasts.
✔ Get insider knowledge from leading cybersecurity experts.

✔ Learn practical steps to future-proof your organization.

✔ Stay updated on regulatory changes and industry trends.


Need help subscribing? Click here for step-by-step instructions.

Quantum computing is coming faster than most organizations are ready for. In this episode of Shielded: The Last Line of Cyber Defense, Kevin Reifsteck, Director for Critical Infrastructure Protection at Microsoft, joins Jo Lintzen to unpack how Microsoft is building a coordinated roadmap toward quantum-safe security and why governments and enterprises must start acting now. Kevin explains how Microsoft’s Quantum Safe Program connects engineering, compliance, and policy under one strategy, with a clear commitment to deliver customer-ready capabilities by 2029 and complete the global transition by 2033. He shares how this plan balances scale with flexibility, empowering each product group to define its path while keeping the company aligned to a shared goal. He outlines why post-quantum migration must move beyond “code swaps” to address real-world complexities like data-center encryption, operational technology that runs for decades, and global interoperability. Kevin also highlights the role of government action, appointing accountable leaders, aligning regulations across borders, and prioritizing sectors such as healthcare and finance where long-term data protection is critical.

What You’ll Learn

How Microsoft’s Quantum Safe Program sets 2029 and 2033 milestones for migration readiness.
Why accountability and leadership drive progress more than technology alone.
How to identify and protect systems and data with long-term exposure risk.
Why global alignment through NIST, ISO, and IETF matters for interoperability.
How governments can accelerate national readiness through coordinated action.
Why post-quantum migration must include hardware, policy, and operations - not just software updates.
Practical first steps for organizations to begin their own quantum-safe transition today.

Kevin Reifsteck is the Director for Critical Infrastructure Protection at Microsoft, where he leads global strategy across cybersecurity policy, quantum-safe readiness, and public–private sector collaboration. His work bridges engineering and regulation, helping Microsoft’s product teams align with evolving post-quantum cryptography standards while advising governments on how to prioritize critical systems and national resilience. Before joining Microsoft, Kevin served as Director for Critical Infrastructure Cybersecurity at the National Security Council, The White House, where he shaped U.S. policy for securing essential services and modernizing cyber risk management. Today, Kevin plays a central role in driving Microsoft’s Quantum Safe Program, which sets clear timelines for transitioning products and services to post-quantum cryptography and helping customers worldwide prepare for the quantum era. Known for his strategic clarity and cross-sector insight, he continues to champion global alignment, government readiness, and responsible innovation in securing the foundations of the digital world.

Your Roadmap to Quantum Resilience

[01:25] Step 1: Set Accountability and Direction –
Every successful migration begins with ownership. Kevin explains how Microsoft anchored its transition by naming accountable leaders and setting measurable goals across its entire product ecosystem. The company’s Quantum Safe Program unites engineering, policy, and compliance within one vision, ensuring that strategy translates into coordinated action. Each product group defines its own plan within shared milestones, creating focus without friction. This balance of central direction and local execution allows a company as large as Microsoft to move with precision. Leadership commitment is the engine that turns post-quantum awareness into measurable progress.
Key Question: Who owns your quantum-safe migration, and what milestones define success?

[04:29] Step 2: Establish a Timeline Customers Can Trust –Microsoft’s roadmap defines clear signposts: customer-facing capabilities by 2029 and full transition across products and services by 2033. These dates are not abstract; they give structure to engineering priorities, regulatory engagement, and customer planning cycles. Kevin shares that transparency in scheduling helps align suppliers, cloud partners, and governments around a shared sense of urgency. It signals that the migration window is already open, and that early action reduces future cost and complexity. By publishing its timelines, Microsoft creates both accountability and confidence within the broader ecosystem. Timelines build trust, and trust accelerates adoption.
Key Question: Have you defined a clear migration timeline that aligns your teams, vendors, and customers?

[07:29] Step 3: Make Policy an Enabler, Not a Barrier –Governments set the tempo of readiness. Kevin emphasizes that effective policy should create alignment, not administrative drag. Microsoft advocates for each nation to name a responsible authority, establish a post-quantum plan within its national cybersecurity strategy, and allocate the resources to act on it. Awareness programs and sector-specific guidance can turn compliance from a burden into an accelerator, especially for industries like healthcare and energy where expertise is scarce. The key is partnership; policymakers and private industry moving in rhythm toward the same standards and timelines. Well-crafted regulation builds the runway for secure innovation.
Key Question: How can your policy environment encourage rather than slow down quantum-safe adoption?

[09:26] Step 4: Move Beyond the “Algorithm Swap” Mindset –True migration reaches beyond code. Kevin outlines how large-scale infrastructures rely on encryption embedded deep within hardware, network layers, and operational systems that may run for decades. In cloud environments, encryption depends on specialized chips, data flow, and power efficiency, all of which must adapt to larger keys and new computational demands. In critical infrastructure, replacing or reconfiguring operational technology requires careful planning and years of lead time. Treating PQC as a systemic evolution ensures that migration strengthens, rather than disrupts, core services. Preparation today prevents technical and operational lock-in tomorrow.
Key Question: Which parts of your infrastructure demand more than a code update to achieve quantum resilience?


[12:32] Step 5: Protect Long-Lived Data and Systems –Some data loses value in weeks; other data must stay confidential for decades. Kevin draws attention to sectors where this matters most: finance, healthcare, and government, where exposure to “harvest-now, decrypt-later” attacks could have generational consequences. The first step is to identify which assets would still cause harm if exposed ten or fifteen years from now. Protecting those systems early not only reduces risk but avoids future regulatory and operational strain. Microsoft’s guidance encourages leaders to focus first on the information and services that define their long-term trust relationship with customers. Longevity determines priority in the quantum transition.
Key Question: Which information or systems in your organization will still matter a decade from now?

[14:50] Step 6: Align Through Global Standards –Quantum resilience depends on collaboration that crosses borders. Kevin explains how Microsoft works within NIST, ISO, and IETF to ensure that algorithms and protocols mature together, preventing regional fragmentation that could slow the entire ecosystem. When nations align on standards, organizations can innovate confidently, knowing their systems will interoperate securely worldwide. The goal is a consistent framework that supports both national security and commercial continuity. Alignment builds momentum, and momentum ensures no critical infrastructure is left behind. The post-quantum era will reward those who plan globally and execute locally.
Key Question: How well are your systems and partners aligned with emerging global post-quantum standards?

Episode Resources

• Kevin Reifsteck on LinkedIn

• Microsoft Website

• Johannes Lintzen on LinkedIn 

• PQShield Website 

Want exclusive insights on quantum migration?


Stay ahead of the curve. Subscribe to Shielded: The Last Line of Cyber Defense on Apple Podcasts, Spotify, or YouTube Podcasts.


✔ Get insider knowledge from leading cybersecurity experts.


✔ Learn practical steps to future-proof your organization.


✔ Stay updated on regulatory changes and industry trends.


Need help subscribing? Click here for step-by-step instructions.

As quantum computing advances, organisations can no longer treat hardware migration as a secondary task. Thalia Laing, Principal Cryptographer at HP Security Lab, explains how HP adopted a hardware-first approach to post-quantum security by launching the world’s first quantum-safe Secure Boot for business PCs ahead of NIST standards. She describes how HP integrated hybrid RSA + LMS signatures to preserve certification assurance and user performance while adding quantum-safe protection at power-on. Thalia outlines the operational design behind LMS state management, parameter selection, and cross-team testing to ensure verification speed and long-term reliability. She details why many enterprises overlook hardware-implemented cryptography in their inventories and how this blind spot undermines migration plans. She highlights how securing firmware integrity extends device lifespan and builds measurable confidence across product lines. The discussion reinforces that protecting the hardware root of trust is the first step toward true post-quantum resilience.

What You’ll Learn:

• How HP built quantum-safe Secure Boot into production PCs before PQC standards were finalised.

• Why hybrid RSA + LMS signatures bridge certification and quantum resilience.
  
  
• How LMS state and parameters are managed for predictable, verifiable signing.
  
  
• Why hardware-level cryptography must be included in every crypto inventory.

• How securing firmware integrity extends device lifetime and compliance value.
  
  
• How to prioritise long-lived, hard-to-update products in PQC migration plans.
  
  
• Why crypto agility begins in design, not deployment.
  
  
• Why starting with the hardware root of trust reduces cost, risk, and time pressure later.

Thalia Laing is the Principal Cryptographer and Security Researcher at HP Security Lab, where she leads research and implementation initiatives in post-quantum cryptography, hardware-based security, and trusted computing. She has played a key role in HP’s development of quantum-safe Secure Boot for business PCs and printers, integrating hybrid RSA + LMS architectures that strengthen firmware integrity and protect devices throughout their lifecycle. Over nearly eight years at HP, she has contributed to advancing cryptographic standards, security innovation, and enterprise readiness for the quantum era.

Thalia holds a PhD in Cyber Security from Royal Holloway, University of London, where her research on enhanced threshold schemes explored the balance between security and efficiency in distributed cryptographic systems. A member of the NIST NCCoE Migration to PQC Project, she continues to collaborate across industry and academia to accelerate the adoption of quantum-resistant security technologies. Known for her rigour and clarity in applying cryptography to real-world engineering, Thalia focuses on designing security foundations that endure across generations of hardware and emerging post-quantum standards.


Your Roadmap to Quantum Resilience


[05:58] Step 1: Protect the Root of Trust First –Quantum resilience begins where trust begins, which is in hardware. Thalia explains why HP started its post-quantum journey by redesigning the Secure Boot process, the first code executed when a device powers on. This verification chain is baked into silicon and cannot be patched in the field, making it the single most critical layer to protect against future quantum attacks. By introducing quantum-safe verification at this immutable level, HP ensured that even if traditional cryptography were compromised, the foundation of every PC would remain secure. The result is a hardware-anchored assurance model that outlasts software cycles and supports long-term device integrity.

Key Question: Which hardware-anchored components in your systems would compromise everything if their signatures failed?

[08:58] Step 2: Combine Proven and Post-Quantum Assurance –Migration to post-quantum cryptography doesn’t mean abandoning what already works. HP adopted a hybrid RSA + LMS model to secure its business PCs, combining the certification maturity of RSA with the forward security of LMS. Both signatures must verify before a device will boot, and a nested design ensures consistency: the firmware is first signed with LMS, then the firmware and LMS signature are signed again with RSA. This dual chain preserves compatibility for existing customers while introducing quantum-safe protection seamlessly. It also satisfies regional and industry assurance requirements, an essential bridge between today’s standards and tomorrow’s mandates.

Key Question: Where could a hybrid model strengthen your cryptographic assurance without disrupting certification or performance?


[11:53] Step 3: Manage LMS with Precision and Predictability –LMS is powerful but operationally demanding. Thalia outlines how HP engineered its signing infrastructure to prevent state reuse, manage signature limits, and tune the Winternitz parameter, a key setting that trades verification speed for computational effort. Because firmware signing happens predictably and infrequently, HP could model the entire lifecycle of each key, ensuring that verification remains fast and the state never exhausts. Extensive cross-testing between the signing infrastructure and endpoint firmware teams helped find the optimal balance between performance and endurance. The result is a proven framework for implementing post-quantum signatures in live production environments.

Key Question: Have you built the operational discipline to manage state, limits, and parameters before scaling PQC deployments?


[21:16] Step 4: Close the Hardware Inventory Gap –Visibility drives every successful migration, yet most crypto inventories overlook what’s embedded in hardware. Thalia emphasises that many scanning tools capture software libraries and network protocols but miss firmware-level cryptography entirely. Secure Boot keys, embedded verification logic, and hardware root certificates often sit outside conventional monitoring systems. HP encourages organisations to supplement automated scans with manual verification and vendor collaboration to document these hidden elements. Only by mapping cryptography end-to-end, from cloud to chip, can enterprises manage risk and sequence migration effectively.

Key Question: Does your cryptographic inventory capture the unseen hardware roots that define your trust boundary?


[25:32] Step 5: Build for Physical Resilience –Quantum safety is only part of the equation, physical resilience completes it. Thalia explains how HP integrates side-channel and fault-injection protections into hardware designs, preventing attackers from bypassing verification steps or manipulating power and timing behaviour. Since such defences cannot be retrofitted after deployment, they must be planned at the design phase alongside cryptographic migration. The goal is not just mathematical security but operational assurance, devices that remain trustworthy even under physical access or lab-level attack.

Key Question: How aligned are your hardware-level countermeasures with the cryptographic strength you rely on?


[18:21] Step 6: Prioritise Long-Lived, Hard-to-Update Devices –Every device has a lifespan; cryptography often does not. HP’s migration strategy focuses on hardware that will remain in service for years, business PCs, printers, and embedded peripherals. By upgrading these devices first, HP reduces exposure to the “harvest now, decrypt later” threat and avoids expensive retrofits when new standards become mandatory. Thalia calls this “future-proofing at the factory”: designing security that endures as algorithms evolve and threats mature. Prioritising longevity over convenience transforms security investment into measurable business value.Key Question: Which products in your portfolio will still be operational when quantum attacks become real, and are they ready today?

Episode Resources

• Thalia Laing on LinkedIn
  
  
• HP Website
  
  
• Johannes Lintzen on LinkedIn 

• PQShield Website 
  
  

Want exclusive insights on quantum migration?  Stay ahead of the curve. Subscribe to Shielded: The Last Line of Cyber Defense on Apple Podcasts, Spotify, or YouTube Podcasts.

✔ Get insider knowledge from leading cybersecurity experts.


✔ Learn practical steps to future-proof your organization.


✔ Stay updated on regulatory changes and industry trends.


Need help subscribing? Click here for step-by-step instructions.

As quantum computing accelerates, organizations can no longer treat cryptographic migration as a distant technical task. Dr Richard Searle of Fortanix explains how confidential computing and a software-first model enable enterprises to adopt post-quantum cryptography (PQC) rapidly while maintaining control, compliance, and agility. He describes how Fortanix integrates standardized PQC algorithms within trusted execution environments to protect data in use, at rest, and in motion, providing a verifiable layer of defense against quantum-era threats. Richard clarifies that crypto agility, not a one-off migration, is the real target, enabling algorithm rotation and policy enforcement as new standards evolve. He also outlines how global companies must account for regional algorithm preferences, such as those emerging in Europe and Asia, without fragmenting global operations. Through examples from finance and technology sectors, he highlights how auditability, attestation, and workload geolocation now define compliance readiness across DORA, GDPR, and CNSA 2.0 frameworks. The discussion reinforces that migration is as much about policy, inventory, and evidence as it is about cryptography itself. The lesson is direct: begin the transition now, build measurable posture, and design architectures that can adapt before regulators and attackers dictate the timeline.


What You’ll Learn:

• How confidential computing underpins a secure execution base for PQC migration.
• Why crypto agility, not one-off migration, defines long-term resilience.
• How to manage regional algorithm differences while maintaining global compatibility.
• How attestation, geolocation, and immutable logs turn compliance into proof of control.
• The role of inventory management and performance assessment in sequencing PQC rollout.
• How to balance human approval with machine-based cryptographic execution through APIs.
• Why finance and technology are leading sectors in post-quantum adoption.
• Why starting now lowers cost, builds capability, and prevents a rushed, regulator-driven scramble.

Dr Richard Searle is the Chief AI Officer at Fortanix, a global leader in confidential computing and data security. He leads Fortanix’s strategy at the intersection of cryptography, AI security, and post-quantum readiness, helping enterprises protect data across hybrid multi-cloud environments. With a background in systems engineering and safety-critical design, Richard brings more than two decades of experience in building secure, compliant, and resilient systems for both private and public sectors. Before becoming Chief AI Officer, Richard served as Fortanix’s Vice President of Confidential Computing and played a pivotal role in advancing the company’s confidential computing platform, which secures data in use through trusted execution environments. He has also served as the Chair of the End-User Advisory Council and General Members’ Representative to the Governing Board of the Confidential Computing Consortium under the Linux Foundation.


A Doctor of Business Administration from Henley Business School, University of Reading, Richard continues to contribute to research in AI and defense security. He serves as Principal Investigator for Fortanix within the U.S. NIST AI Safety Institute Consortium (AISIC) and the UK Integrated Quantum Network (IQN) Hub. Known for his clarity and discipline in security architecture, Richard focuses on helping global enterprises design for crypto agility, regulatory assurance, and quantum-safe innovation.


Your Roadmap to Quantum Resilience

[03:14] Step 1: Establish a Confidential Computing Base -Quantum resilience begins with protecting what matters most, which is “data in use.” Richard explains how trusted execution environments create an invisible shield around sensitive workloads, keeping information safe even while it is being processed. Fortanix’s software-first foundation allows this protection to extend across cloud and on-premises systems, without the delays of hardware dependencies. Establishing this base gives enterprises the confidence to deploy new algorithms, test PQC performance, and maintain control wherever their data flows.Key Question: Which of your workloads process the most sensitive data and need in-use protection today?


[05:45] Step 2: Design for Crypto Agility from Day One -Every organization entering the quantum era must prepare for change. Richard highlights the need to design systems that can adapt, rotating algorithms, refreshing keys, and updating parameters through policy rather than rebuilds. This mindset transforms cryptography from a fixed asset into a flexible service that evolves alongside emerging standards. By embedding agility from the start, enterprises can move with the pace of regulation and innovation instead of reacting to it.

Key Question: How easily can your teams change algorithms when new standards arrive?


[09:10] Step 3: Plan for Regional Algorithm Variants -Global operations demand awareness of regional differences in cryptographic policy. While NIST drives the global baseline, Europe and Asia are advancing their own approaches, such as Classic McEliece and FrodoKEM, to strengthen local sovereignty. Fortanix addresses this diversity through a single control plane that can manage multiple algorithms while maintaining unified governance. Organizations that prepare for regional variance today will stay compliant and operationally aligned as new mandates emerge.

Key Question: Are your policies ready to accommodate regional algorithm choices without breaking global consistency?


[16:15] Step 4: Turn Compliance into Evidence -Compliance becomes a source of trust when it can be proven. Richard shows how attestation and workload geolocation enable enterprises to demonstrate exactly where and how data was processed. Immutable logs and signed records create a transparent audit trail, satisfying frameworks like GDPR, DORA, and CNSA 2.0. This approach shifts compliance from a reporting exercise to a living proof of security discipline and accountability.

Key Question: Can you present verifiable proof of control, location, and authorization for sensitive workloads?


[19:22] Step 5: Inventory, Evaluate Performance, and Sequence by Exposure -A strong migration plan begins with visibility. Richard outlines how teams can build an accurate inventory of keys, certificates, and machine identities, then analyze which are most exposed or critical to business continuity. Fortanix’s data security platform supports this assessment, enabling phased implementation that balances performance with risk. By starting with the systems that face customers and regulators, organizations gain both resilience and credibility in their transition to PQC.

Key Question: Which high-exposure services in your organization should move first toward PQC?


[21:01] Step 6: Govern with Humans, Execute with Machine Identities -As automation expands, clarity of control becomes vital. Richard describes how Fortanix maintains human oversight through quorum approvals while allowing machine identities to perform cryptographic operations within defined boundaries. This structure preserves accountability and enables scale, empowering secure automation for code signing, data exchange, and AI workflows. True governance lies in this balance, human intent directing machine execution through policy and precision.

Key Question: Where can you introduce automation that enhances control rather than replacing it?


Episode Resources

• Richard Searle on LinkedIn
• Fortanix Website
• Johannes Lintzen on LinkedIn 
• PQShield Website 

Want exclusive insights on quantum migration?  Stay ahead of the curve. Subscribe to Shielded: The Last Line of Cyber Defense on Apple Podcasts, Spotify, or YouTube Podcasts.


✔ Get insider knowledge from leading cybersecurity experts.
✔ Learn practical steps to future-proof your organization.

✔ Stay updated on regulatory changes and industry trends.


Need help subscribing? Click here for step-by-step instructions.

Hardware security modules (HSMs) sit at the core of digital trust, protecting transactions, PKI systems, and authentication. As quantum computing approaches, traditional HSMs face limits that can’t be solved by patching old hardware. In this episode of Shielded: The Last Line of Cyber Defense, host Johannes Lintzen speaks with Bruno Couillard, CEO and co-founder of Crypto4a and co-creator of the Luna HSM, about building quantum-safe HSMs. Bruno explains the difference between PQC-ready and PQC-providing, warning that retrofitting classic devices is not enough. He highlights PKI as the no-regret first step and shows how hybrid models let organizations bridge classic and post-quantum algorithms. Cloud adoption and scalability challenges demand modular, cloud-aligned HSMs instead of isolated, priest-only boxes.Bruno’s message is that HSMs are the foundation of digital security, and crypto-agility is now essential for surviving the quantum era.
What You’ll Learn

• The origin story of the Luna HSM and why it shaped modern key management
• Why SSL in 1995 marked the “Big Bang” of the digital economy
• PQC-ready vs. PQC-providing: the critical distinction vendors don’t always make
• Why firmware updates can’t turn classic HSMs into true quantum-safe systems
• How hybrid approaches allow gradual migration from RSA/ECC to PQC algorithms
• Why PKI is the best “no-regret” first step in any migration plan
• The cloud challenge: why HSMs must evolve from priest-only boxes to scalable, modular systems
• The future of cryptography: crypto-agility as a permanent requirement, not a one-off project
• Why cryptography is back at the forefront and ripe for young talent

Bruno Couillard is the CEO and co-founder of Crypto4a Technologies, where he leads the development of quantum-safe, crypto-agile products like the QxHSM and QxEDGE. With nearly four decades of experience in cryptography, key management, and cybersecurity, Bruno has shaped the hardware security module (HSM) landscape from its origins to its next evolution. Earlier in his career, Bruno cofounded Chrysalis-ITS and co-designed the original Luna HSM, a product that remains foundational to global PKI systems and is now part of the Thales portfolio. He also contributed to the creation of the PKCS#11 standard and served as a cryptographic evaluator for the Canadian government, where he assessed and architected high-assurance military security products, including the Canadian Cryptographic Modernization Program.
Today, Bruno sits on the board of Quantum Industry Canada (QIC), co-chairs the Quantum Industry Developers and Users Working Group, and serves on Canada’s National Quantum Strategy committee, actively shaping the country’s quantum-safe cybersecurity ecosystem. Known for his clear perspective, he emphasizes the urgent need for crypto-agility, the distinction between PQC-ready and PQC-providing systems, and the modernization of HSMs to meet cloud and scalability demands.
Your Roadmap to Quantum Resilience


[04:59]  Step 1: Learn from the Past
HSMs were originally designed in an era when cryptographic officers were treated as “priests,” entrusted with near-sacred responsibilities. The Luna HSM grew out of this mindset with hardware built for isolation, secrecy, and manual control. This legacy explains why many devices remain difficult to use and poorly adapted to modern environments. What worked in the 1990s no longer fits a world where security must be deployed at scale and managed across distributed teams. The first step is recognizing if your current systems are still locked in a pre-cloud, pre-scale paradigm.


[09:58] Step 2: Understand the Big Bang of Digital Trust
The arrival of SSL in 1995, combined with PKI and HSMs, triggered what Bruno calls the “Big Bang of the digital economy.” That triad enabled secure transactions and authentication, paving the way for today’s digital commerce, which is now one-third of global GDP. The takeaway is that cryptography is not a side issue but the fabric of the digital economy. If the integrity of this foundation collapses under quantum pressure, every layer of commerce, government, and communication is at risk. Leaders must weigh whether they are underestimating just how central cryptography is to their business model.


[12:39] Step 3: Separate PQC-Ready from PQC-Providing
Bruno stresses that an HSM must be internally quantum-safe, not just capable of handing PQC algorithms to external applications. Firmware updates, key exchanges, attestation signatures, and sibling-to-sibling communication inside the HSM all rely on its own cryptography. If that internal layer remains classical, the entire system is compromised even if it outwardly “provides” PQC algorithms. Many vendors blur this line, leaving buyers exposed. Organizations need to question their suppliers if they are only PQC-providing, or if they are truly PQC-ready inside and out?


[17:38] Step 4: Don’t Believe in Magic Wands
Classic HSMs cannot be turned into quantum-safe devices with a firmware patch. Bruno compares this to painting stripes on a horse and calling it a zebra. It may look different, but the foundation hasn’t changed. Once RSA and ECC are deprecated, patched boxes will collapse under the weight of new requirements. Leaders need to ask now whether their existing fleet can actually survive deprecation, or if they are investing in assets destined for the scrapheap. Betting on retrofits is a costly illusion that will leave organizations scrambling.


[21:41] Step 5: Secure Your PKI First
Among the many cryptographic systems to protect, PKI stands out as the crown jewel. Amazon has publicly called it a “no-regret” migration step, since nearly all systems depend on certificates and keys issued there. Crypto4a’s approach allows hybrid use, binding classical and PQC algorithms in the same machine, so organizations can transition without rebuilding from scratch. By starting with PKI, enterprises set a quantum-safe anchor that supports a gradual rollout elsewhere. It’s a step that prevents wasted effort and ensures early moves don’t need to be undone later.


[26:23] Step 6: Modernize and Build for Agility
While computing infrastructure has become modular, scalable, and cloud-aligned, most HSMs are still boxy appliances requiring physical keys and human rituals. This mismatch slows deployment and makes cryptography harder to manage at enterprise scale. Bruno argues HSMs must evolve to cloud-native, modular architectures that operators can provision and control without specialized ceremonies. Equally, systems must be designed for crypto-agility, the ability to swap algorithms through policy updates rather than rewriting code. Without agility and modernization, organizations will find themselves locked into brittle systems just as cryptography enters its most turbulent era.


Episode Resources

• Bruno Couillard on LinkedIn
• Crypto4A Technologies Website
• Johannes Lintzen on LinkedIn 
• PQShield Website 

Want exclusive insights on quantum migration?  Stay ahead of the curve. Subscribe to Shielded: The Last Line of Cyber Defense on Apple Podcasts, Spotify, or YouTube Podcasts.
✔ Get insider knowledge from leading cybersecurity experts.
✔ Learn practical steps to future-proof your organization.
✔ Stay updated on regulatory changes and industry trends.


Need help subscribing? Click here for step-by-step instructions.

As industries continue to treat cryptography as invisible plumbing, the risk of systemic disruption is growing. In this episode of Shielded: The Last Line of Cyber Defense, host Johannes Lintzen speaks with Mike Silverman, Chief Strategy & Innovation Officer at FS-ISAC, about why complacency is more dangerous than quantum itself. Mike explains how decades of one-off migrations have left organisations brittle, why inventories and risk models are the essential starting point, and how cryptographic agility must become both a design principle and an organisational mindset. They discuss why timelines like 2030 and 2035 demand phased action, how vendor and supply chain readiness can make or break success, and why PKI standards and certificate interoperability are the hidden dependencies no one can ignore. From embedding PQC into normal app modernisation cycles to reframing the conversation for the boardroom, Mike delivers a pragmatic warning: you don’t need to boil the ocean, but you must start now.


What You’ll Learn:

• Mindset Shift: Why the biggest risk isn’t “quantum” per se, it’s assuming cryptography can be ignored until the next crisis.
• True Crypto-Agility: Minimal downtime, minimal (ideally zero) code changes, policy-driven selection, and ecosystem readiness.
• Inventory First: How key discovery, asset metadata, and process mapping create a measurable, fundable scope of work.
• Risk-Based Priorities: Protect crown-jewel data and long-lived assets first; accept there will be legacy tails.
• Ecosystem Dependencies: Why vendors, PKI standards, certificate profiles, FIPS-validated libraries and supply chains dictate your timeline.
• Board Framing: Position PQC as business continuity and trust preservation, embedded in regular tech refresh, not a one-off cost centre.
• 2030/2035 in Practice: Read timelines as phase gates (inventory + highest-risk migrations first; wider coverage later), not a big-bang cutover.

Mike Silverman is Chief Strategy & Innovation Officer at FS-ISAC, the global, member-driven consortium dedicated to collective defense in financial services. In this role, he leads forward-looking initiatives on post-quantum cryptography, AI risks, cloud security, and sector resilience, helping financial institutions anticipate and prepare for the threats shaping tomorrow’s trust landscape.

With a career shaped by crisis response and industry collaboration, Mike has been at the center of efforts to align governments, regulators, and enterprises on how to secure financial systems under pressure, from pandemic coordination to the emerging quantum challenge. His work focuses on reframing cryptography as a first-class citizen, embedding it into inventories, risk models, and long-term technology refresh cycles that extend beyond any single algorithm.

Known for his pragmatic perspective, Mike stresses that the real danger is complacency, not just quantum breakthroughs. He argues that cryptographic agility is the only sustainable defense, that timelines like 2030 and 2035 demand phased and realistic planning, and that collective readiness across vendors and supply chains is non-negotiable. His message is clear: organisations don’t need to panic, but they do need to start now.
Your Roadmap to Crypto-Agility

[03:52] Step 1: Stop Treating Crypto as Plumbing

For decades, cryptography has been invisible, assumed to “just work” in the background. Mike argues this is the biggest blind spot. Every major migration, from DES to AES or from RSA-1024 to RSA-2048, has been treated as a painful one-off. That approach leaves organisations brittle and unprepared for the next wave of change. The lesson is clear: cryptography must be treated as a first-class citizen in security planning, with visibility, budget, and executive attention. Key Question: Are you still assuming crypto will take care of itself, or are you elevating it to a first-class security discipline in your organisation?

[09:58] Step 2: Define What Crypto-Agility Really Means

Mike recalls sitting in industry meetings where “crypto-agility” meant wildly different things to different stakeholders. FS-ISAC responded by publishing a sector-wide definition: the ability to swap algorithms (A→B) with minimal downtime, minimal disruption, and ideally no code changes. Achieving this requires both architectural foresight (decoupling crypto from applications) and organisational alignment (governance, vendor contracts, policy-driven controls). Key Question: If you had to change cryptography tomorrow, would it take a simple policy update or a rewrite across every app and vendor system?


[15:39] Step 3: Build Your Inventory and Risk Model

Silverman stresses a basic truth: you can’t secure what you can’t see. Few CISOs could raise their hand if asked, “Do you know where 100% of your keys are?” An accurate inventory, where keys live, how they’re managed, which systems depend on them, creates the foundation for prioritisation. Layering risk on top ensures crown-jewel systems and long-lived data are addressed first. Without this visibility, organisations risk wasting resources on the wrong assets. Key Question: Do you know where all your cryptographic keys and algorithms are, and which assets pose the highest risk if migration lags?

[20:15] Step 4: Plan for Legacy and External Dependencies

Even with a ten-year runway, Mike believes there will be legacy systems left behind. Large institutions with acquisitions face inconsistent policies, while smaller firms rely heavily on vendor products. Dependencies extend beyond the enterprise, supply chains, PKI standards, certificate profiles, FIPS-validated libraries all dictate what’s feasible. Success depends on coordinated timelines with vendors and regulators, not just internal willpower.Key Question: Are you aligning your migration plans with vendor readiness and global standards, or assuming you can solve it all in-house?

[26:31] Step 5: Embed PQC into Normal Modernisation Cycles

Boards balk at funding PQC as a standalone project. Mike reframes it: cryptographic upgrades should be part of ongoing app modernisation and lifecycle refresh. From mainframes and point-of-sale systems to operating systems and middleware, modernisation already happens in cycles. The right approach is to bake PQC into those existing refreshes, so cost and disruption are absorbed by processes organisations already budget for.Key Question: Are you presenting PQC as an extra burden, or embedding it naturally into technology refresh cycles your board already funds?

[36:46] Step 6: Act Now, Without Fearmongering

Mike is clear: the sky isn’t falling. But the longer organisations delay, the harder and costlier the transition will be. Starting small, augmenting asset management, training staff, asking vendors the right questions, creates momentum without overwhelming the business. Crypto-agility is a journey measured in years, not months, and the best way to reduce fear is to begin.Key Question: Are you waiting for the “perfect moment” to start, or taking small, practical steps today that build toward crypto-agility?

Episode Resources

• Mike Silverman on LinkedIn
• FS-ISAC Website
• FS-ISAC Linkedin
• FS-ISAC X
• FS-ISAC Cryptographic Agility White Paper (TLP:WHITE)
• Quantum Safe Financial Forum (QSFF) – EU Initiative
• Johannes Lintzen on LinkedIn 
• PQShield Website 

Want exclusive insights on quantum migration?  Stay ahead of the curve. Subscribe to Shielded: The Last Line of Cyber Defense on Apple Podcasts, Spotify, or YouTube Podcasts.
✔ Get insider knowledge from leading cybersecurity experts.

✔ Learn practical steps to future-proof your organization.

✔ Stay updated on regulatory changes and industry trends.


Need help subscribing? Click here for step-by-step instructions.

As regulators publish guidance and timelines tighten, organizations can’t treat quantum readiness as a “future-us” problem. Will Collison details HSBC’s approach: begin the migration now, build crypto agility into architecture, and manage both internal upgrades and external dependencies across vendors, partners, and customers. He clarifies where PQC (for everyone) and QKD (for select high-assurance links) fit, and why identity (public-key) mechanisms not symmetric crypto like AES, are the primary risk from quantum computing. Will also reframes “legacy” systems as revenue-critical systems that demand careful, early planning, and he lays out a pragmatic cost model: if you wait, you’ll lose the ability to go slow, forcing a fast (and expensive) scramble. The mandate is simple: start now, measure progress, and design for change so you can swap algorithms when needed.
What You’ll Learn

• How early action lowers cost and risk while keeping quality high.
• PQC vs. QKD vs. Quantum Computing: Clear roles, overlaps, and where to invest first
• Why quantum threatens public-key identity mechanisms more than symmetric encryption.
• Crypto Agility as the Goal: Build systems that can swap algorithms when standards evolve.
• Prioritization Framework: Tackle internet-facing and revenue-critical services early, even if they’re “legacy.”
• Vendor & Partner Readiness: How to pressure-test your supply chain and avoid being the weak link.
• Executive Buy-In: Talk tracks that move the conversation from “someday” to funded roadmap.
• Regulatory Reality: Don’t wait for “R-Day” (regulator day); show posture now to customers and supervisors.

Will Collison is the Interim Global Head of Cryptography at HSBC, where he leads the bank’s global cryptography strategy across 60 markets. A CISSP-qualified consultant with two decades of experience, he specializes in public key infrastructure (PKI), cryptography standards, and the automation of trust. Over his seven-plus years at HSBC, Will has served as Technical Director of Cryptography, Global Head of Cryptography Standards and Enforcement, and PKI Specialist, building frameworks for machine and digital identity and driving large-scale remediation programs.
Prior to HSBC, he founded Secmundi Limited, advising international banks on cryptography strategy and operating models, and worked as a Trust Consultant at Barclays, guiding PKI implementations and automation of certificate issuance. Known for combining deep technical expertise with pragmatic execution, Will has long been a voice for crypto agility, helping organizations modernize securely while preparing for future shifts. Today, his focus is clear: ensuring enterprises can meet the challenges of post-quantum cryptography (PQC) and build a quantum-safe future.
Your Roadmap to Quantum Resilience
[06:20] Step 1: Build Awareness and Executive Buy-In -The first barrier isn’t technology, it’s leadership alignment. Will emphasizes that cryptographers alone cannot drive PQC migration; it requires CIOs, CEOs, and developer communities to take ownership. At HSBC, demonstrating early trials with quantum key distribution (QKD) helped leadership see quantum as real and urgent, not distant theory. By pairing opportunity narratives (business applications) with security risks (broken RSA), Will built credibility and won support across the C-suite. Without this awareness step, migrations stall, as PQC remains “just a cryptography issue” instead of a business priority.Key Question: Do your executives see PQC as an organizational shift, or just another crypto upgrade?
[10:44] Step 2: Separate the Quantum Trio (PQC, QKD, Quantum Computing) -Confusion often slows action: leaders lump quantum computing, post-quantum cryptography (PQC), and QKD into one bucket. Will makes the distinction clear, PQC is mandatory for everyone, QKD is optional for select high-assurance links, and quantum computing is the attacker capability on the horizon. PQC secures identity mechanisms that quantum computers can break; symmetric algorithms like AES remain largely safe. For organizations, this clarity avoids wasted investment and helps focus resources on the universal priority: PQC. QKD may add value in specific backbone use cases, but it’s not a substitute for PQC adoption.Key Question: Does your roadmap clearly differentiate between PQC (a must-do) and QKD (a niche add-on)?
[15:15] Step 3: Prioritize Critical and Revenue-Generating Systems -Migration is not just about legacy; it’s about revenue-critical systems that are hardest to touch. Will highlights that the most important services, core banking, internet-facing platforms, high-value transaction systems, are also the most delicate. These cannot be treated as “old and optional”; they need careful, phased planning. Starting with these systems ensures resilience where risk and business impact are highest. At HSBC, prioritizing internet-facing services and those with zero downtime tolerance became the backbone of the PQC roadmap. Organizations should resist the temptation to defer these systems, as they represent both the highest stakes and the longest lead times.Key Question: Have you identified which systems are both critical and hardest to migrate and started with them?
[18:10] Step 4: Engineer for Cryptographic Agility -Will posits that PQC migration isn’t a one-and-done fix. Because cryptography is open to attack and algorithms are deliberately stress-tested by academics, today’s standards may not be tomorrow’s. The real goal is crypto agility, building systems that can switch algorithms without costly rewrites. This means designing pluggable crypto frameworks, modular architecture, and future-ready PKI. Organizations that treat PQC as a single migration will find themselves repeating the pain in a few years; those that embed agility now will be able to adapt at the push of a button. Agility turns a crisis response into a strategic advantage.Key Question: If the next PQC algorithm is broken tomorrow, could your systems swap it out without disruption?
[27:15] Step 5: Start Now to Control Cost and Compliance -Waiting only makes migration harder and more expensive. Will lays out the math: if you start today, you can go slow and control costs; if you wait for Q-Day or R-Day (when regulators mandate action), you lose the option of “slow” and are forced into expensive, rushed remediation. Early investment also lets you train in-house talent instead of competing in a skills-short market later. Regulators and peers are already moving, meaning inaction risks reputational damage as much as security exposure. The smartest play is to begin now, measure progress, and use the lead time to stay ahead of both attackers and regulators.Key Question: Are you starting early enough to spread cost and build skills, or setting yourself up for a rushed, expensive scramble later?
Episode Resources

• Will Collison on LinkedIn
• HSBC Website
• Johannes Lintzen on LinkedIn 
• PQShield Website 

Want exclusive insights on quantum migration?  Stay ahead of the curve. Subscribe to Shielded: The Last Line of Cyber Defense on Apple Podcasts, Spotify, or YouTube Podcasts.
✔ Get insider knowledge from leading cybersecurity experts.✔ Learn practical steps to future-proof your organization.✔ Stay updated on regulatory changes and industry trends.

Need help subscribing? Click here for step-by-step instructions.

As executives continue to postpone action, the window for preparing secure systems in the quantum era is rapidly closing. In this episode of Shielded: The Last Line of Cyber Defense, host Johannes Lintzen speaks with Adrian Neal, Senior Director and Global Lead for Post-Quantum Cryptography at Capgemini, about the real timelines and challenges of PQC migration. Adrian explains why a “three-to-five-year” plan is unrealistic, why organizations should expect closer to eight years, and how unprepared boards risk panic and triage once the first quantum breakthrough hits. They discuss why crown-jewel systems must be prioritized, how banks and governments face different pressures, and why performance under PQC will shock existing infrastructure, illustrated by tests where an HSM fell from 10,000 transactions per second to just 200. From regulatory pressure that may be needed to drive boardroom buy-in to the hard truth that today’s algorithms may not last, Adrian delivers a candid warning: apathy will kill you. The time to act is now.
What You’ll Learn

• Y2K vs. Y2Q: Why “non-event” thinking is dangerous without upfront work
• Timelines that hold: Why “3–5 years” is best-case and ~8 years is realistic at enterprise scale
• Performance truth: How PQC can crush TPS and impact SLAs, capacity, and cost models
• Crypto-agility: Abstract crypto from apps, enable policy-driven selection, and automate swap-outs
• Governance first: Why poor implementations, not just algorithms, will break your security
• Regulatory unlock: How mandates/bodies (BIS, NCSC, sector groups) drive C-suite action
• Where to start: Crown-jewel systems, dependency mapping, and critical-path scheduling

Adrian Neal is Senior Director and Global Lead for Post-Quantum Cryptography at Capgemini, where he advises governments, financial institutions, and global enterprises on preparing for the quantum era. With nearly four decades of experience spanning banking, defense, telecoms, and startups, Adrian has been at the center of major security transformations, from the early days of PKI to today’s post-quantum migration programs. His work focuses on helping organizations identify critical systems, manage dependencies, and design long-term strategies that combine technical execution with board-level buy-in.

Known for his candid perspective, Adrian warns that migration is closer to an eight-year journey than a three-year sprint, that crypto-agility is the only sustainable defense as algorithms evolve, and that apathy will kill you. His message is clear: the sooner organizations begin planning, the better chance they have to avoid panic, triage, and systemic disruption when the first quantum “black swan” arrives.
Your Roadmap to Quantum Resilience

[04:17] Step 1: Accept the Real Timeline

The biggest misconception Adrian encounters is the idea of a “three-to-five-year” migration. As he bluntly states, that only works if everything goes perfectly and in the real world, it never does. Organizations must plan for eight years at best, with the expectation of mid-course corrections and even emergency triage when hidden dependencies surface. Late action only makes the crunch sharper, as boards suddenly realize time has run out. Key Question: Are you planning for an idealized three-year sprint, or budgeting for the reality of an eight-year marathon?
[07:18] Step 2: Watch for External Signals

Quantum risk can feel abstract until regulators, supervisors, or global bodies spell out the consequences. Adrian points to the Bank of International Settlements, which recently warned of systemic financial collapse if banks fail to act. Similarly, the UK surveyed CISOs not to congratulate them, but to ask why nothing was happening. These signals are the early tremors  and ignoring them risks being blindsided when regulation becomes mandatory. Key Question: Are you treating industry warnings as background noise, or as early instructions to act before mandates arrive?
[12:23] Step 3: Stress-Test Your Infrastructure

Benchmarks on paper rarely match performance under real load. Adrian recalls a test where a PQC algorithm dropped a hardware security module from 10,000 transactions per second to just 200. That kind of shock will ripple through SLAs, capacity planning, and cost models. Enterprises can’t wait for standards alone, they need to start testing now to understand what PQC will mean for their unique environments. Key Question: Have you run PQC under production-like loads, or are you still trusting theoretical benchmarks?
[31:23] Step 4: Start With the Crown Jewels

When mapping a migration, not all systems are equal. Adrian insists the first priority must be crown-jewel systems, the assets so critical that losing them could put you out of business. By identifying these early and mapping their dependencies, organizations can build a critical-path plan, sequencing work in the right order and avoiding surprises later. Everything not on the critical path can be parallelized, but the critical path itself must be guarded fiercely. Key Question: Do you know which systems are truly crown jewels, and how delays there will cascade across your migration?
[34:17] Step 5: Design for Crypto-Agility

Even if today’s algorithms are standardized, Adrian cautions they may not last. History has already shown finalists falling apart late in the NIST process, and cryptographers warn that vulnerabilities may be found within five years. That means crypto-agility is no longer optional: organizations must decouple applications from crypto libraries, move to policy-driven controls, and be ready to swap algorithms without rewriting code. Governance is equally critical, because poor implementation, not just weak algorithms, will be the Achilles’ heel. Key Question: Can you change cryptography across your systems with a policy update, or would it take a rewrite in every app?
[21:38] Step 6: Leverage Regulation for Buy-In

For many CISOs, the hardest part isn’t technical, it’s convincing the board. Adrian highlights how legislation may actually be a friend, giving executives the leverage to unlock budgets by framing PQC as a compliance necessity. Without that pressure, boards tend to see migration as a cost center with no immediate revenue benefit. By aligning to regulatory timelines, CISOs can turn PQC from a “someday project” into a non-negotiable investment. Key Question: Are you waiting for regulators to force your hand, or using regulation as a tool to unlock boardroom commitment today?
Episode Resources

• Adrian Neal on LinkedIn
• Capgemini Post-Quantum Cryptography Resources
• European Union Qprep Initiative
• Johannes Lintzen on LinkedIn 
• PQShield Website 

Want exclusive insights on quantum migration?  Stay ahead of the curve. Subscribe to Shielded: The Last Line of Cyber Defense on Apple Podcasts, Spotify, or YouTube Podcasts.
✔ Get insider knowledge from leading cybersecurity experts.

✔ Learn practical steps to future-proof your organization.

✔ Stay updated on regulatory changes and industry trends.

Need help subscribing? Click here for step-by-step instructions.

OpenSSL has secured the internet for over 25 years, but how does a project with such deep legacy prepare for the quantum future? In this episode of Shielded: The Last Line of Cyber Defense, host Johannes Lintzen speaks with Tomáš Mráz, Director of the OpenSSL Foundation, and Jon Ericson, the Foundation’s Community Manager. Together they explore the shift from the old engine model to providers in OpenSSL 3.0, the rollout of NIST-approved post-quantum algorithms in 3.5, and what’s on the horizon with 3.6. They also dive into the realities of FIPS certification, the importance of diversified funding, and how community contributions sustain the world’s most widely used cryptographic library. From surprising “OpenSSL in the Wild” use cases to the first-ever OpenSSL Conference in Prague, this episode offers a rare inside look at how OpenSSL is evolving to keep global infrastructure secure in the quantum era. OpenSSL is evolving to keep the digital world safe.
What You’ll Learn

• How OpenSSL evolved from engines to providers, enabling faster adoption of new cryptographic standards
• Why community contributions, from bug fixes to corporate sponsorships, remain critical to OpenSSL’s future
• The significance of OpenSSL 3.5 and what to expect in the upcoming 3.6 release
• How the Foundation approaches FIPS 140-3 certification and the challenges of validating post-quantum algorithms
• Why hybrid cryptography and TLS-style agility are central to migration planning
• The importance of funding diversification and how organizations can contribute
• What to expect at the first OpenSSL Conference in Prague
• OpenSSL’s three-to-five-year outlook on PQC adoption, performance, and global standards alignment

Tomáš Mráz is the Director of the OpenSSL Software Foundation and a long-time contributor to the project. After years at Red Hat maintaining OpenSSL packages and serving on the OpenSSL Technical Committee, Tomáš now leads both governance and technical efforts for the Foundation. He has played a key role in transitioning OpenSSL to a provider-based model and integrating post-quantum cryptography support. 

Jon Ericson is the Community Manager at the OpenSSL Software Foundation. With a background in programming and community building, Jon works to strengthen the connection between OpenSSL’s global user base and its core developers. From GitHub sponsorships to community use case surveys, he ensures that OpenSSL remains responsive to the evolving needs of its contributors and stakeholders.

With the shift to post-quantum cryptography accelerating, Tomáš Mráz and Jon Ericson’s message is clear: OpenSSL’s future will be defined by community, funding, and cryptographic agility, ensuring the internet’s most trusted library stays secure in the quantum era.
Your Roadmap to Quantum Resilience
[02:30] Step 1: Build Through Community, Not Just Code

From the very beginning, OpenSSL’s strength has been its community. As Jon Ericson explains, many contributions still come from volunteers fixing bugs or adding features because they personally rely on the library. This model means OpenSSL doesn’t evolve in isolation, it reflects the real-world needs of users across industries. Without this constant input, critical flaws might linger and adoption of new features would stall. Community-driven resilience is what has kept OpenSSL relevant for more than 25 years, and it’s also the key to surviving the quantum shift. Key Question: Is your organization contributing back to the open-source tools it depends on, or just consuming them?
[15:40] Step 2: Embrace the Provider Model for Agility

Tomáš Mráz highlights that OpenSSL 3.0’s provider architecture was a complete rewrite of the library’s internals. Unlike the old engine system, providers allow new algorithms, including post-quantum candidates, to be plugged in without altering the core code. This design foresight meant OpenSSL could quickly integrate PQC once NIST finalized its standards in 2024, instead of waiting years for structural changes. Agility in cryptography isn’t an abstract idea here, it’s a practical necessity, and the provider model gives OpenSSL the flexibility to adapt faster than ever. Key Question: Is your cryptographic infrastructure designed for future upgrades, or locked into a rigid model?
[24:45] Step 3: Prepare for 3.6 With Discipline, Not Deadlines

While many in the industry chase feature lists, OpenSSL takes a different approach. As Tomáš explains, new releases are time-based (April and October), but features are only merged when they are truly ready. Current work spans QUIC improvements, zero-RTT support, timing side-channel protections, and potential PQC enhancements, but nothing will be rushed to hit an arbitrary date. This discipline has allowed OpenSSL to remain the backbone of secure communications globally, trusted by billions of devices and applications. For organizations planning their upgrades, the message is clear: align to OpenSSL’s stable releases, don’t gamble on unfinished code. Key Question: Are your upgrade plans aligned with proven releases, or are you rushing ahead of the standards?
[27:50] Step 4: Navigate the FIPS 140-3 Challenge

Certification is one of the hardest parts of cryptography. OpenSSL 3.1 achieved FIPS 140-3 validation, a first in its history, and the 3.5 version is already in review to bring NIST’s post-quantum algorithms into scope. Tomáš admits the process is long, political, and outside of the Foundation’s control, with heavy negotiations between NIST, labs, and implementers. But without certification, many governments and enterprises simply cannot adopt PQC at scale. The lesson for security leaders: you can’t shortcut compliance, and you need realistic timelines to plan migrations. Key Question: Is your compliance roadmap realistic about how long certifications actually take?
[30:30] Step 5: Stay Engaged With OpenSSL’s Future

OpenSSL is everywhere, often in places you’d never expect. Jon recounts a developer securing serial devices with TLS, and even Mercedes vehicles using OpenSSL in their apps to lock and unlock doors. These surprising “in the wild” stories show why upgrading matters: outdated versions leave unseen risks in everyday systems. Looking ahead, the Foundation is also launching its first-ever OpenSSL Conference in Prague, bringing together experts, contributors, and industry voices to shape the next phase. Between new funding streams, hiring developers, and expanding global engagement, OpenSSL’s next 25 years will be as pivotal as its first.Key Question: Do you know where OpenSSL runs in your stack — and are you keeping pace with its evolution?
Episode Resources

• Tomáš Mráz on LinkedIn
• Jon Ericson on LinkedIn
• OpenSSL Foundation Website
• OpenSSL GitHub Sponsors
• Johannes Lintzen on LinkedIn 
• PQShield Website 

Want exclusive insights on quantum migration?  Stay ahead of the curve. Subscribe to Shielded: The Last Line of Cyber Defense on Apple Podcasts, Spotify, or YouTube Podcasts.
✔ Get insider knowledge from leading cybersecurity experts.

✔ Learn practical steps to future-proof your organization.

✔ Stay updated on regulatory changes and industry trends.


Need help subscribing? Click here for step-by-step instructions.

As governments and regulators accelerate PQC adoption timelines, the urgency for organizations to act has never been greater. In this episode of Shielded: The Last Line of Cyber Defense, host Jo Lintzen speaks with Kevin Hilscher, Senior Director of Product Management at DigiCert, to explore the practical first steps of post-quantum cryptography adoption. They discuss why upgrading to TLS 1.3 is a non-negotiable starting point, how discovery of crypto assets lays the groundwork for any migration, and what enterprises should know about hybrid cryptography and its competing standards. From fragmented global regulations to aggressive timelines and the looming challenges of vendor readiness, Kevin provides a candid, real-world perspective on how organizations can build a quantum-ready roadmap before regulatory deadlines and quantum breakthroughs arrive.
What You’ll Learn

• Why TLS 1.3 is the non-negotiable first step for PQC readiness
• How to approach crypto asset discovery across software, hardware, and vendors
• The difference between hybrid key exchange vs. hybrid certificates (and why it matters)
• Why regulatory timelines (EU 2030, CNSA 2027) may be more ambitious than reality
• The challenge of fragmented algorithms across geographies and what it means for interoperability
• How Falcon (FNDSA) could benefit resource-constrained IoT devices
• Where vendors are leading (crypto SDKs) vs. lagging (enterprise apps and infrastructure)
• Kevin’s advice for CISOs: why awareness, discovery, and vendor engagement must start now

Kevin Hilscher is Senior Director of Product Management at DigiCert, where he leads the device trust product team and oversees PQC readiness across the company’s portfolio. With a background at Microsoft and deep experience working with OEMs, banks, healthcare providers, and defense organizations, Kevin has been at the forefront of preparing enterprises for the quantum era. His focus spans securing connected devices, enabling regulatory compliance, and helping global customers prepare for the transition to PQC. Known for his pragmatic approach, Kevin bridges the gap between evolving cryptographic standards and real-world business needs, helping organizations take the first steps toward a secure, quantum-ready future.

With the shift to post-quantum cryptography accelerating, Kevin’s message is clear: early discovery and TLS 1.3 readiness, not just new algorithms, will define the path to a quantum-ready future.
Your Roadmap to Quantum Resilience
[06:17] Step 1: Build Awareness and Secure Buy-In - 

For many industries, the first challenge isn’t technical; it’s awareness. Kevin explains that cybersecurity teams often have to “sell upwards,” using the right data, talk tracks, and materials to educate leadership about PQC and secure sponsorship. Without this “step zero,” projects stall before they begin. Education is critical, not just inside your own enterprise, but across vendors and partners who may not even know what PQC is yet. Key Question: Do your executives and stakeholders truly understand the urgency of PQC, or are they still in denial?
[07:18] Step 2: Discover Your Crypto Assets - 

The foundation of every migration is discovery. Kevin stresses the importance of cataloging where and how cryptography is used, TLS versions, crypto libraries, SDKs, and source code. For banks, that means checking third-party apps and firewalls. For OEMs, it’s embedded devices still running RSA or ECC. Discovery reveals not just internal risks but also gaps in vendor readiness, enabling informed conversations about timelines and support. Key Question: Have you mapped your crypto landscape, from TLS versions to third-party dependencies, so you know what needs to change?
[09:25] Step 3: Upgrade to TLS 1.3 Today - 

Before PQC algorithms even come into play, enterprises must meet the TLS prerequisite. As Kevin notes, the IETF has been blunt: quantum-safe algorithms will only be supported in TLS 1.3 and above. Yet many organizations are still stuck on TLS 1.2 in legacy apps and infrastructure. Migrating now means you can act independently of PQC timelines while also future-proofing your systems for what’s next. Key Question: Are you still relying on TLS 1.2, or have you taken the first real step toward a quantum-ready foundation?
[12:30] Step 4: Navigate Hybrid Cryptography with Clarity - 

“Hybrid” is one of the most confusing terms in PQC. Kevin highlights the difference between hybrid key exchange (pairing a PQC algorithm with RSA or ECC for TLS handshakes) and hybrid certificates (dual-signed X.509s). While hybrid key exchange is standardized and deployable today, hybrid certificates remain stalled by competing standards like composite, Chimeria, and Chameleon. Without clarity, organizations risk paralysis. Key Question: Do you know which type of hybrid you’re preparing for, and are you moving ahead where standards are ready today?
[22:14] Step 5: Plan Realistically for Timelines and Vendor Readiness - 

Global regulators are setting ambitious deadlines, 2030 in the EU, 2027 for U.S. federal procurement. Kevin warns that critical systems like SCADA, SAP, and ERP will struggle to meet those dates, especially with legacy TLS and outdated infrastructure. While crypto SDKs are ahead, enterprise apps and HSM certifications will lag. Organizations must pressure vendors for roadmaps while also preparing for phased upgrades.Key Question: Are you planning your migration based on regulatory optimism, or on the real pace of vendor and infrastructure readiness?
Episode Resources

• Kevin Hilscher on LinkedIn
• DigiCert PQC Resources
• DigiCert PQC Lab Site
• Johannes Lintzen on LinkedIn 
• PQShield Website 

Want exclusive insights on quantum migration?  Stay ahead of the curve. Subscribe to Shielded: The Last Line of Cyber Defense on Apple Podcasts, Spotify, or YouTube Podcasts.
✔ Get insider knowledge from leading cybersecurity experts.
✔ Learn practical steps to future-proof your organization.

✔ Stay updated on regulatory changes and industry trends.

Need help subscribing? Click here for step-by-step instructions.