logoalt Hacker News

shepherdjerred • today at 3:52 AM • 4 replies • view on HN

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


Replies

tptacek • today at 3:53 AM

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.

➕ show 1 reply
fauchletenerum • today at 5:55 AM

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.

➕ show 2 replies
mborch • today at 9:47 AM

Or use defense in depth. There will be a vulnerability in every layer with some non-trivial probability, but rarely in multiple layers at the same time.

leptons • today at 7:05 AM

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.

➕ show 3 replies