security made simple
This installment goes in a different direction. Where the last post zoomed all the way in — past the running host, past the alert, down to a single line of source...stepping away from individual controls entirely and asks about the distributed, multi-platform enterprise the cloud produced.
We've climbed through the rings of the architecture... This installment goes further upstream than any of them. It steps back to the code itself — and asks how you find the flaw while it's still cheap to fix and it hasn't shipped yet. That's the domain at the heart of Application Security Testing.
This installment does something different. Every domain we've covered so far — even the unglamorous hygiene loop — was, at bottom, an attempt to keep the bad day from arriving. This one starts the morning after it did...
I've been working through the second edition of the Cybersecurity Architect's Handbook's "secret menu" one domain at a time...the controls that still mean something after everything else has fallen. This installment does something different...it looks down at the ground all of them are standing on.
Every control we design as architects ultimately serves one of two questions. Who is allowed to do what — and is the data still protected ... Access control answers the first. Data protection answers the second. Together they form the innermost ring of a defense-in-depth architecture...
This installment goes in a different direction. Where the last post zoomed all the way in — past the running host, past the alert, down to a single line of source...stepping away from individual controls entirely and asks about the distributed, multi-platform enterprise the cloud produced.
We've climbed through the rings of the architecture... This installment goes further upstream than any of them. It steps back to the code itself — and asks how you find the flaw while it's still cheap to fix and it hasn't shipped yet. That's the domain at the heart of Application Security Testing.
This installment does something different. Every domain we've covered so far — even the unglamorous hygiene loop — was, at bottom, an attempt to keep the bad day from arriving. This one starts the morning after it did...
My lab runs Debian 13 as the primary environment, so when a 356-page Ubuntu book landed on my desk, my first instinct was to skim it, nod politely... Instead I read the whole thing — and I'm giving it five stars...
I've been working through the second edition of the Cybersecurity Architect's Handbook's "secret menu" one domain at a time...the controls that still mean something after everything else has fallen. This installment does something different...it looks down at the ground all of them are standing on.
Every control we design as architects ultimately serves one of two questions. Who is allowed to do what — and is the data still protected ... Access control answers the first. Data protection answers the second. Together they form the innermost ring of a defense-in-depth architecture...
Every query a device makes is a statement of intent — what it wanted to reach, when, and how often — and once you're logging them, you're no longer just blocking bad names. You're watching behavior....
Before we get into the core of the article — a quick, time-bound note. Packt is sponsoring a giveaway on my LinkedIn channel...This post moves to the first place that thinking touches wire: Category 2, Network Security Controls...
"Instead of just rehashing abstract theory, it bridges the gap between high-level security principles and real-world execution. It's practical, actionable, and a great tool for anyone designing or engineering modern infrastructure."
In the last post I gave you the tour — the foundational labs, the eight operational categories...So let's start where the whole discipline starts: Category 1, Threat Modeling and Risk Assessment.
In the last post, I jumped straight to the top of the spire — the AI Security Automation capstone. But a capstone, by definition, sits on top of something. You can't appreciate the spire if you've never seen the cathedral....
Alongside the printed edition, the book's associated GitHub repository holds over 700 more pages of supplementary content and hands-on labs...
