Remix.run Logo
▲ shepherdjerred 4 hours ago

It feels to me the only way to beat LLMs finding vulnerabilities is to have LLMs (or LLMs paired with other AI methods) constantly monitor your infrastructure, traffic, database, etc. to ensure that nothing out of the ordinary is happening

▲tptacek 4 hours ago | parent | next [-]

I think so too; I think apart from pushing vulnerability research forward (which is important on its own merits just for computer science reasons), the major engineering challenge of this moment is figuring out how to make platforms resilient without rewriting everything; that could be better live-patching, it could be some weird monitoring thing, it could be automatic segregation and workload isolation.

It's not "just keep up with the patches". That's going to be a losing strat.

▲fauchletenerum 2 hours ago | parent | prev | next [-]

I'm not sure how cost effective or even viable that option would be. I think the only practical defense is some kind of baseline hardening at the OS or application level. Something like eBPF rules i.e. what Cilium Tetragon policies provide. Basically it seems like there's no way to guarantee that your application code can't be exploited in some novel way so your best option is to restrict them as much as possible.

▲shepherdjerred 19 minutes ago | parent [-]

I'm really just talking as a layman here.

My feeling is that if we use traditional security approaches that seems like a losing strategy. You cannot just keep patching. I mean obviously you should, but that is not enough.

LLMs are finding zero days in operating systems, language runtimes, everything. They will definitely be finding holes in your API. It is not a question of 'if'.

▲leptons 41 minutes ago | parent | prev [-]

When Plex got hacked and my linux server had a cryptominer installed, I had no clue where to start fixing it. I loaded up Claude to analyze the system logs, and it told me what commands to run (and why) and the infection was gone in about 10 minutes. There's no way I would have known the many things I needed to do to fix and secure the system. I'm fairly new to Linux, and without the AI I would be helpless with some of the tricky things.

▲kryptiskt 19 minutes ago | parent | next [-]

The right thing to do in that case is to save whatever data you need from the server and then nuke it thoroughly, which means all the disks should be wiped, don't keep the old UEFI partition around, and reinstall. It would preferable to skip the first step and get the data from a source that wasn't compromised, but sometimes you have bring out the hazmat suits to recover stuff from compromised systems.

▲shepherdjerred 17 minutes ago | parent | prev [-]

This is very reactive though -- imagine you were a business. You'd be screwed. Your data is already gone.