CS

Chris Swan

Things Chris Says on Podcasts

Where to Find Them

Chris Swan has been a guest on The InfoQ Podcast (2 times) .

Recently: “Future Cybersecurity: Hardware Memory Safety, Automated Governance and Post-Quantum Cryptography” on The InfoQ Podcast (October 2026); “Chris Swan on DevOps and NoOps, plus Operations and Code Validation in a Serverless Environment” on The InfoQ Podcast (January 2018).

What They Said

“If you look at the post-mortem of the Hugging Face incident, it was described ... as I think like having 10,000 drunk house robbers show up all at once. And that sounds like a very chaotic scene. But I think that might kind of perfectly encapsulate where we are at the moment.” — Chris Swan, The InfoQ Podcast

Swan is passing on a description he attributes to the company's own security chief, of an attack carried out by AI agents. His point is that the attack surface is the same for humans and agents, but the scale is not, and scale causes trouble even when each attacker isn't very capable.

The InfoQ Podcast · 2026-10-05 Permalink → Listen →
The InfoQ Podcast Around 22:50 into the episode
Speaker 3

…problem. It's a hairy one to manage. And we don't want to be kind of manually thinking about this stuff. And so we now kind of get into the sort of Auroburro thing of we need an AI to help us manage the permissions that we're giving to our agents because otherwise it just becomes unmanageable.

Speaker 2

…more teasers about next year, but for me, two points. Well, you mentioned one, and that's post-quantum computing or post-quantum cryptography. That's something that you have on your mind. You did mention some kind of security net for agents. Is there anything else that you would like to tease?

Speaker 3

…the moment is about how do we defend systems from humans and agents. And I think actually there's a common convergence there that the attack surface area is the same, whether it's a human or an agent. The nature of the attack and the scale of the attack is probably very different between human and agent. If you look at the post-mortem of the hugging face incident, it was described by their siteo as I think like having 10,000 drunk house robbers show up all at once. And that sounds like a very chaotic scene. But I think that might kind of perfectly encapsulate where we are at the moment. And even if each individual attacker in that case isn't particularly capable, just the sheer scale brings a whole bunch of problems on its own. So I think I'd like to get a talk that sort of looks at that aspect of what we're confronting. But I want to kind of ground it in the reality of if you're doing a good job of defense, then that's going to defend against the human attacker, the AI. Agent…

Speaker 2

Okay, just to summarize the points that I think I heard, going to lower level might help us as an industry, given that that will provide a better foundation. And hence, the ripple effect will be a lot broader, probably, and help different points, regardless if we are discussing about agents or…

Speaker 3

Yes.

Speaker 2

Okay. Is there anything else?

Speaker names come from our own diarization. The position is estimated from where the line sits in the episode.
“We've also seen projects where rewrites in Rust have introduced new logical flaws because, okay, you get memory safety, but it doesn't mean that everything's invulnerable. ... Getting memory safety from the hardware is ultimately going to be a lot cheaper than redoing all of the software.” — Chris Swan, The InfoQ Podcast

Swan is explaining a research project that puts memory safety into the chip, so existing C code can be recompiled instead of rewritten. He puts open source C at billions of lines against tens of millions of lines of Rust, and says rewriting it all would take almost impossibly long even with AI help.

The InfoQ Podcast · 2026-10-05 Permalink → Listen →
The InfoQ Podcast Around 06:14 into the episode
Speaker 3

…done. But this can't keep going forever. And so at some point, we'll find ourselves in a situation where there'll just be fewer vulnerabilities left to discover. And that should be a happier place for all of us to exist in because we won't be worrying as much about zero days and their exploitation.

Speaker 2

Okay. Well, you mentioned Sherry and the fact that both Android and iPhones are looking into adopting this model. Maybe we can allocate a couple of minutes to get more details to our listeners and understand what Sherry actually is. Maybe we inspire other folks to adopt it.

Speaker 3

…is, oh, just rewrite it all in Rust. But if you look at the size of the problem, there's something like five and a half billion lines of open source C C and something like 70 million lines of Rust at the moment. And so if we were to plot our course of how long it would take humanity to rewrite all of that C and C into Rust, even with AI assistance, it's almost an impossibly long duration. And we've also seen projects where rewrites in Rust have introduced new logical flaws because, okay, you get memory safety, but it doesn't mean that everything's invulnerable. You still have to think through the other ways that systems can be attacked. The rewrite of some of the core utils into Rust has unfortunately thrown away decades of hardware experience about what can go wrong with applications. You end up with functionally equivalent replacements, but that have some new bugs in them. They might be not memory safety bugs, but they're still potentially security…

Speaker 2

Given the points that you had, having it in Android and iOS will have a very wide span, given the OUB-COTUS nature of the mobile phone. It would be to have a magic wand and you should pick another platform that would have it tomorrow. Which one would that be?

Speaker 3

So it would be RISC-V. And I say that because RISC-V is still nascent as an instruction set architecture in terms of its adoption. It's still standards-wise, a little bit more malleable than the x86 and the ARM stuff that we've all become accustomed to. And I think having the Cherry instructions in…

Speaker 2

Yeah, probably given the open source nature of RISC-V, we'll have maybe hopefully a better blast radius. But fingers crossed that we get closer to having a more memory-safe ecosystem.

Speaker names come from our own diarization. The position is estimated from where the line sits in the episode.

Collections They Appear In