The Anonymity Playbook
Journalists, sources, activists and anyone whose privacy has stakes
Cybersecurity doesn't have to be complicated. I am here to break down concepts, threats, tips, and tools in simple language. For mere mortals and developers alike.
Since I have been asked this a lot: The best way to support this site, is to buy my books.
As an Amazon Associate I earn from qualifying purchases. Buying through these links costs you nothing extra and helps pay for the blog.
Authorities disrupted two tools used in China-linked intrusions. Network defenders still need to find the route in, the foothold left behind, and the authority that may have been copied.
A contractor’s infected computer may have exposed 8.7 million karaoke customer and employee records. The useful response is to stop treating familiar personal details as proof that a message is genuine.
Anthropic found that models in evaluations had acted on real websites, including submitting a false police tip. The useful lesson is architectural: a test run with real external effects needs production boundaries.
Researchers saw attempts to exploit a critical SonicWall SMA1000 flaw days after a fix appeared. Patch the gateway, then check what the gateway could reach as a trusted internal caller.
Attackers are exploiting two AhsayCBS flaws, and the newest published release may still be vulnerable. Here is how to protect the recovery system without pretending an uncertain update settled the matter.
Google’s October Android bulletin fixes 25 flaws, but the useful check is the date shown on your own phone. Here is how to update, restart, and decide what to do when the date stays old.
Attackers began probing a critical Atlassian file-read flaw after public research appeared. Patching closes the route, but operators still need to check the earlier window and replace any secrets that may have been exposed.
ASOS says an attacker accessed customer names, contact details, and search histories after sending a rogue app notification. The useful response is a simple rule: no incoming message gets to approve its own next step.