A conversation with Rich from 2GuysTek about the Cybersecurity Architect's Handbook, the fundamentals that still matter, and how architects should approach AI, zero trust, quantum readiness, and legacy systems.
A practical policy and configuration guide for detecting prompt injection and jailbreak attempts before inference, then blocking unsafe content and sensitive-data disclosure before model output reaches a user, tool, or application.
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.
For a long time, my autonomous agent found credentials the same way many applications do. Why I replaced a flat environment file with scoped Vaultwarden access, short-lived agent sessions, and a verified audit trail that now reaches Graylog and Wazuh.
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."
I have taught this material before as two sessions, and I usually open each session the same way: this is not a tool class. Tools get named below, plenty of them, but every one is an implementation of the same pipeline, and the pipeline is what transfers to whatever product your employer bought...
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...