The Terminal Is a Conversation
My first Linux distribution no longer exists. I mention that because it lands two points at once: Linux is old enough to have history, and the skills transfer anyway...
My first Linux distribution no longer exists. I mention that because it lands two points at once: Linux is old enough to have history, and the skills transfer anyway...
After years of working, teaching, writing in this field, the pattern I see most in newcomers is not lack of ability. It is freezing...
I spend my working hours telling teams how to do security well. Segment the network. Write the change down. Model the threat before you build the control. Then I go home, and if I am honest with myself, the temptation is to cut every one of those corners because it is "just the lab."
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.
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...
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.
The Second Edition of the Cybersecurity Architect's Handbook: An Architect's Guide to Designing, Building, and Defending the Modern Enterprise is now available for pre-order on Amazon.
This "Deep Dive," generated through AI in a podcast style, provides a review of the main themes and important ideas presented in the "Cybersecurity Architect's Handbook."