If you are running services and don't yet have an easy way to react to these things with swift process defined, I hope you don't like to sleep.
I dont think my security posture is all that much different than it was last year. Use a Secret Manager and or encryption, have backups, strong firewall rules, use canaries of some kind.
If anything llms are making security worse because there's more people offloading their thinking on llms, or people that skipped some steps in their learning journey because they just ask the llm to do everything. I dont think its necessarily because attackers have llms now, but that contributes.
Edit:
Damn Im getting mega downvoted for saying this. So are people of just at a consensus that there's nothing you can do? That we're in security armagedon???
Have you ever thought to consider that security took hit along with the general degradation of software because of AI??
To speak to your edit: this is false equivalency. You can still decrease the odds of being hit. There are still better and worse ways to address security.
Once you declare the incident, the process includes these status page updates, alongside equivalent internal status updates.
In this case, they probably wanted to maximise coordination, so used the process designed for that.
I left because I didn't like the pressure / pager duty, but I seriously respect how smooth and well thought out their operations were.
Your intuition that this can be balanced out is wrong. When you have a CVE in your TCP stack, your vault unlocks and you're fucked, it's done. My dude, there is never going to be AIs scanning every incoming packet for signs of a 0day, and deciding whether to, uhh, cut it up with a lightsaber and shoot it with a laser pistol. Your options are to have a stack so secure that it can't be targeted, or to disconnect all network cables.
It is possible to write more secure software[0], companies just choose not to prioritize security.
Don't use MPTCP is the first mitigation, but my understanding is this might be exploitable without MPTCP.
I don't see how web services proceed like business is normal.
- Tell HNN: pets.com was *not* owned today
- Tell HNN: about:blank was safe, too
- Show HNN: my new gopher protocol project—no currently known CVE 10's
Imagine swarms of abliterated frontier AI models that reach >20,000 TPS. As I said before [0] you are going to have to hire specialized security engineers or technical bodyguards from the senior to senior staff level using AI agents to protect your entire business.
Otherwise you are cooked.
Is that really the best way to do things? I’m not really sure what an agent offers here does it just look at logs and do actions? I would not really feel safe if that’s my service’s answer to security.
I could see it maybe as a really smart filter to block ips that are sending probing requests but I don’t really see that as a good reason to have an agent be sitting 24/7 looking at logs.
Thanks god, you are not a wacko thinking qwen3.0-1.5B-abliterated would hack a goverment.