Weekly Security Briefing
News, vendor watch, and the open-source tools worth knowing about — plus a dedicated eye on cloud security and hardening. Curated for practitioners, not headline chasers.
Free weekly. No spam. Unsubscribe anytime.How to give GitHub Actions workflows access to AWS, Azure, and Google Cloud without long-lived keys, and why trust conditions should name immutable IDs, not repository names. A 23-item checklist.
The third cheat sheet in the set: a checklist for locking down Google Cloud Storage, from public access prevention and uniform bucket-level access to encryption, recovery, and logging, plus a gotcha where enforcement masks public grants instead of removing them.
Why identity is the real perimeter now, per Verizon's 2026 breach data — the access-control mandate, where key vaults fit in, and a real comparison of AWS, Azure, and GCP's secrets managers
Why encryption isn't optional — IBM's 2026 breach numbers make the case — plus the tradeoffs nobody mentions: key loss, encryption ≠ access control, and the post-quantum gap almost nobody's closing.
The AWS S3 checklist's Azure counterpart — access, network, encryption, and recovery controls for Blob Storage, plus a static-website gotcha that quietly undermines 'anonymous access disabled.'
A practical checklist for locking down S3 buckets — access control, encryption, versioning, logging, and detection — mapped to the exact CIS Foundations Benchmark controls each one satisfies.
Misconfigurations, CSPM findings, IaC security, and hardening checklists — covered evenly across AWS, Azure, and GCP.
Biweekly →Launches, acquisitions, funding, and notable threat research from prominent vendors — read with healthy skepticism of the hype.
As-needed →Smaller, often-overlooked open-source scanners and hardening scripts that don't get mainstream coverage.
Biweekly →Longer original analysis — a technique explained, a breach post-mortem, a tool walkthrough. Published monthly.
Coming soon