Writing
Practical articles on offensive techniques, architecture, detection, and the real-world mindset behind secure systems.
Most organisations map the assets they know about. Attackers map everything else — forgotten subdomains, shadow IT, third-party integrations, and the APIs your developers spun up on a personal AWS account last Tuesday.
Phishing is no longer a badly-worded email from a Nigerian prince. This deep dive walks through target selection, domain spoofing, credential harvesting proxies, and the post-capture automation attackers use to monetise stolen sessions in real time.
Broken Access Control jumped to #1, Cryptographic Failures was renamed, and Insecure Design appeared for the first time. Here's what every developer and assessor needs to understand about the shift.
Vendors sell 'zero trust solutions.' What they won't tell you is that zero trust is an architectural principle — one that requires re-examining implicit trust relationships that have accumulated over years of infrastructure growth.
After initial access, attackers rarely stop. Pass-the-hash, Kerberoasting, WMI, and living-off-the-land techniques allow adversaries to pivot through a network systematically. Understanding their playbook is prerequisite to detecting it.
The biggest breaches did not come from magical zero-days alone. Reused credentials, weak identity controls, cloud misconfigurations, and delayed detection still drive most large-scale impact.
Ransomware groups operate like businesses: access brokers, specialist affiliates, and negotiation teams. Defenders need equally structured preparation across prevention, detection, and recovery.
APIs power modern products, but many still fail on basic authorization, token handling, and data exposure controls. Here are the recurring issues teams can eliminate quickly.
Every major cloud incident revives the same conversation: public storage, broad IAM permissions, exposed admin endpoints, and missing monitoring. This article focuses on prevention that scales.
AI can accelerate detection triage and analyst productivity, but unmanaged adoption creates new attack and compliance surfaces. Effective teams govern model usage with the same rigor as code deployment.