alt Hacker Newsif a CVE drops at 23pm, attackers have at least 8 hours before someone in the office has a possibility to take a look at it. nowadays, that seems to be plenty.
i don't have a solution.
Replies
Have on-call sysadmins or have them work in a three-shift schedule. That way there's always someone there to fix stuff as it happens, including deploying security patches or worst case taking affected systems offline until they can be patched
This used to be common before devops and cloud took over. Looks like it might make a comeback. Maybe with a new fancier job title
There's a really simple solution that people will hate: server goes offline at night.
I've seen this a few times, and it's pretty annoying as a user, but ultimately it's not that bad usually. If you are ordering something at 3am, the physical shipment still occurs during daylight hours. Many banking operations are not actually instantaneous, they settle in a batch job overnight.
And this doesn't have to be binary. Providing a read-only interface provides lots of value while having a reduced attack surface.
low attack surface applications is the future.
People are gonna hate this but: we’ll need agents ready and waiting to autonomously patch and deploy instantly
23 pm where? Simple answer is distributed teams.
I think "good security/engineering practices" still has a chance.
Things like--
All software has flaws and it's now easier than ever to find and exploit them, but this disproportionately hurts people who were only putting on a show of security and relying on a single layer or two of defense instead of developing a robust insider threat model (which helps with both insider threats and threats that get inside) and defense in depth.