The Sentinel works in silence and writes in the third person:
anonymized incident stories, lab-recreated techniques, and plain
talk about the security industry. Every claim sourced. Every story
disclosed. Nothing posted before it was safe to post.
The Sentinel stands up GoPhish in an isolated home lab — no real sending, no real targets — to show defenders what phishing infrastructure looks like from the receiving side, and how SPF, DKIM, and DMARC are the tripwires that actually fire.
A composite case file: the MFA-fatigue vishing call that almost enrolled an attacker's phone onto an executive's identity, and the verification procedure the Sentinel rebuilt from the wreckage.
The Sentinel's first defensive case file documents this very site: the exact Content-Security-Policy, HSTS, and hardening headers quietsentinelshadow.com serves, each verified live and cited to the specification that defines it.
A composite incident file: the ransomware engagement where every backup reported green, the restore had never been tested, and the Sentinel learned what 3-2-1 was supposed to have meant all along.
What the Sentinel covers
Incident stories
Composite, anonymized accounts of real incidents — what broke, who noticed, what it cost, what changed.
Lab techniques
Offensive concepts rebuilt safely in home labs. Nothing published before the fix has shipped.
Defense that holds
Hardening notes tested on this very site — headers, CSP, and the boring controls that actually work.
Industry, plainly
Third-person commentary on the work itself: burnout, bug bounties, disclosure politics, and the trade's quiet corners.
Subscribe to the newsletter
Case files land in your inbox roughly twice a month — no
tracking pixels, one-click unsubscribe. RSS
(feed) remains available for the
old-fashioned.