Operations | Monitoring | ITSM | DevOps | Cloud

Last week we moved every certificate in one of our products to a new CA in 10 minutes. It was six certificates and 18 deployments. I said issuance was the part that slows down, because most CAs limit how fast you can order, and then I waved it off. A reader did the math for me. Some organizations run 30,000 certificates, they claimed, and that’s common at MSPs, telcos, and government agencies. Google Trust Services takes 100 orders an hour by default.

The Apache ActiveMQ Jolokia endpoint has been the route to remote code execution in three separate years. In 2023, it was reflection into the JVM. In 2024, a default configuration left it without a login. In 2026, it was the broker's own management operations, patched in March, exploited in April, and reopened three more times by summer.

In short, in the five weeks to 27th October 2026, Okta, Satya Nadella, the Cloud Security Alliance and Salesforce each put the words “kill switch” or “emergency brake” next to AI agents, and the AI Kill Switch Act, introduced in the US House on 23rd July, would require the largest model providers to be able to throttle, suspend or shut their systems down on order. Every one of those switches stops something, and none of them stops the same thing.

TL;DR On October 29, 2026, attackers drained about $6.3 billion in crypto assets from Binance’s hot wallets, the largest crypto theft on record. Binance says the incident may have started with a compromised laptop, but its investigation has since found additional points of breach, and the root cause is still being confirmed. For engineering and security teams, the lesson is about how quickly you can reconstruct what happened across many systems once something goes wrong. In this post.