I hope some of these backdoors and/or 0-days being kept under wraps by nation states or corporate espionage companies (Pegasus et al) are being found incidentally through all this.
It’s frustrating to have all these 0days and CVEs to patch for now, but in the long run perhaps we’ll leave with more robust software.
syshyk 39 seconds ago [-]
Hopefully we'll also see us back to KISS principles too. But who am I kidding
getfacl 1 minutes ago [-]
Having worked on both sides of the table, the reality is that it is far too easy to game certs like ISO27001. The risk calculation by companies taking that route is changing right out from under them thanks to Ai tools.
sva_ 6 minutes ago [-]
Better sooner than later, to be honest.
jareklupinski 2 minutes ago [-]
personally have started going the other way: AI-assisted microkernels, and only the programming that is actually needed for the problem at hand
my webserver never needed a million lines of code just to pass bytes to other people
sevenzero 1 minutes ago [-]
While we're at it, I'd appreciate easy secure authentication of a device without having to pull in a third party authentication provider. Thanks.
LoboxPlatform 6 minutes ago [-]
The PHP2Shell incident highlights something important: AI is making it easier to discover vulnerabilities, but fixing legacy security issues still requires time, expertise, and resources.
For businesses, this is a reminder that cybersecurity cannot be treated as a one-time task. Regular updates, security audits, and responsible maintenance matter just as much as adopting new technology.
As professional communities become more connected, sharing technical knowledge and learning from security experts will become increasingly valuable. That's also why platforms like Lobox focus on bringing professionals together to exchange knowledge, build connections, and discover relevant communities.
The bigger question is: are organisations investing enough in fixing their existing technical debt before adopting more AI-powered systems?
LoganDark 1 minutes ago [-]
The PHP situation was particularly bad because the people handling it made some very inappropriate choices, like being way too attached to the embargo even once the complete reproduction was circulating publicly on Twitter. That's not inherent to the security patch process, that's just people being stupid.
With that said, I'm sure the defender community will eventually come up with a way to patch security vulnerabilities just about as fast as they can be discovered and exploited.
Rendered at 12:19:26 GMT+0000 (Coordinated Universal Time) with Vercel.
It’s frustrating to have all these 0days and CVEs to patch for now, but in the long run perhaps we’ll leave with more robust software.
my webserver never needed a million lines of code just to pass bytes to other people
For businesses, this is a reminder that cybersecurity cannot be treated as a one-time task. Regular updates, security audits, and responsible maintenance matter just as much as adopting new technology.
As professional communities become more connected, sharing technical knowledge and learning from security experts will become increasingly valuable. That's also why platforms like Lobox focus on bringing professionals together to exchange knowledge, build connections, and discover relevant communities.
The bigger question is: are organisations investing enough in fixing their existing technical debt before adopting more AI-powered systems?
With that said, I'm sure the defender community will eventually come up with a way to patch security vulnerabilities just about as fast as they can be discovered and exploited.