upvote
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.

reply
maybe today, you cant keep up, 2 year later, AI rewrite everything safe in rust, you wont need patch everday
reply
Hahahahaha
reply
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.
reply
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'.

reply
I agree that patching is just plugging holes in the dam with your fingers. I think the only viable defense is something more low level in the kernel. SELinux, eBPF, or something new and more sophisticated than those. A lightweight agent passively monitoring system calls and detecting anomalies perhaps?
reply
And what would that solve?
reply
> there's no way to guarantee that your application code can't be exploited in some novel way

As a thought experiment if this hypothetical application code were written in something resembling haskell I suspect it would actually prove fairly difficult if not impossible to find novel ways to exploit it. I think at that point an attackers only options are logical inconsistencies in the underlying business logic (see that one NASA rocket) or bugs in the compiler and runtime.

reply
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.
reply
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.
reply
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 be 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.
reply
This is very reactive though -- imagine you were a business. You'd be screwed. Your data is already gone.
reply
You're still helpless, since you didn't do what you should have done (format).
reply