Watching the Network You Built - Network Security Part 2
Part 2 puts the security in motion: services, the monitoring pipeline your log lines feed, wireless done currently, safe remote access, and where it all leads.
Part 2 puts the security in motion: services, the monitoring pipeline your log lines feed, wireless done currently, safe remote access, and where it all leads.
Yesterday I wrote about moving autonomous-agent secrets out of a flat .env file. Why I kept Vaultwarden for people and recovery, added HashiCorp Vault for workloads, and treated identity, audit, PKI, and tested recovery as part of the deployment rather than follow-up work.
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."
Welcome back to the Basics Series. In Basics Series - #3 we compared the firewall market, picked OPNsense for the lab, and installed it as a VM. In Basics Series - #4 we worked through the traditional vs. transparent-bridged decision and I promised a configuration walkthrough. This is that post...
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...
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....
Alongside the printed edition, the book's associated GitHub repository holds over 700 more pages of supplementary content and hands-on labs...
I'm thrilled to share that the second edition of the Cybersecurity Architect's Handbook is officially out in the world.
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.