The Identity Thread by Entrust

The episode covers substantive technical ground - harvest-now-decrypt-later attacks, Shor's algorithm, crypto agility, PKI strategy, and the complexities of cryptographic infrastructure migration - but much of the discussion is explanatory rather than novel. Dr. Mayes provides some concrete learnings from CBP's proof-of-concept work (latency surprises, the pervasiveness of cryptography), but the core insights are fairly well-established in security circles. The discussion of prioritization and the blocking-and-tackling nature of most organizations is useful but not deeply original.

“we discovered as a whole was you, you, you, you know, you go into something and you start notice, like unraveling a ball of yarn and you think, you know, where all the strings go, right? But what you find out with, you know, uh, cryptography, right, and encryption is, it's everywhere.”

“organizations have got to start moving faster uh, and thinking broader uh, when it comes to here's what good looks like and here's what the capabilities are that they need to have in place to deal with the threats of the day.”

The framing around post-quantum cryptography readiness is timely given the recent executive order, and Dr. Mayes's anecdote about CBP's cloud journey parallels are reasonably illustrative. However, the core arguments - the urgency of quantum threats, the need for crypto agility, the importance of workforce development, the concept of zero trust - are well-trodden in the security industry. Alice's mention of China's quantum key distribution leadership is valuable context, but overall the episode recycles established frameworks without significant contrarian or first-principles thinking.

“this is a threat, uh, where we are now that unlike anything that we've seen in probably 50 years, we've been living using the same sort of encryption techniques for the past 34 years.”

“there's good news here and that is that the technology exists.”

Dr. Ed Mayes is a strong guest - Deputy Assistant Commissioner at CBP with direct operational responsibility for cryptography migration and clear evidence of hands-on leadership. Alice Fakir brings IBM's federal security services perspective and NIST collaboration credibility. Michael Kleiman, as VP of Data Security at Entrust, has vendor-side expertise but is also the show's producer, which introduces a conflict-of-interest dynamic. The guests are substantive practitioners, though Kleiman's dual role slightly weakens the perceived independence of analysis.

“Dr. Ed Mayes, Deputy Assistant Commissioner, Infrastructure and Support Services and Chief Enterprise infrastructure officer at U.S. customs and Border Protection.”

“Alice Fakir, senior partner and Vice President of cybersecurity services for IBM's US federal market.”

The episode includes concrete details: CBP's 50 million patches per year, the 2028-2029 quantum compute capacity timeline, summer 2026 endpoint readiness from a vendor, 4-5 trillion in trade commerce handled by ACE, IBM's $10 billion quantum investment, and Executive Order 14,409. Dr. Mayes's 'hello world' proof-of-concept and mainframe decryption example ground the discussion. However, many claims lack supporting data: the scale of harvest-now-decrypt-later threats, specific metrics on crypto agility implementation difficulty, and concrete numbers on the migration cost and timeline are absent.

“we did our first proof of concept, right, with uh, using the early NIST algorithms, that sort of thing. And we uh, literally put like an envelope around an application, a small application. Right. Um, and we, you know, we wanted to verify that we could transmit data information from a quantum encrypted environment to um, another device.”

“I do about 50 million patches a year, right? 50 million.”

Host Ken Cadet asks open-ended setup questions and allows guests to speak at length, which builds narrative coherence but limits interrogation. Follow-ups are rare and mostly affirmative ("Right", "Absolutely"). There is minimal pushback or productive disagreement. When Dr. Mayes claims vendors should improve software quality and asks why industry doesn't help, Michael Kleiman validates rather than challenges. Alice's point about learning fast by failing is left unexamined. The conversation feels more like curated perspectives than a sharp journalistic or analytical interrogation.

“Absolutely. Um, Alice, where are you seeing things across, um, across the federal government?”

“Right. Um, M. Michael, maybe talk a little bit more about where this is headed and what kind of challenges we're seeing out there.”