06Blog
What we learn
Field notes.
What we learn keeping businesses running, written down so you don’t have to learn it the hard way.
06.1The notes
Short, practical, written down.
One problem per note, the way we would explain it across a table. Filed under the letter of our name it answers to.
- The first hour of an incident decides the next month.What you do in the first sixty minutes of a security incident shapes how long it lasts and what it costs. A plain first-hour plan — who decides, what to contain, what not to touch, and who to call.
- Your customer data lives in more places than you think.Ask where your customer data is and most businesses name one system. The real answer is closer to a dozen. How to map it in two weeks, and why the map matters most on the day something leaks.
- Your network trusts everything that’s plugged into it.On most business networks, one compromised laptop can reach every server. Why flat networks turn small incidents into big ones, and how to take the trust out of the wiring in ninety days.
- Your team is already pasting company data into AI.People use AI because it helps them. The risk isn’t the tool — it’s the data they give it and the access it inherits. How to find what’s in use, set three rules people will follow, and fix the permissions an assistant would expose.
- The most dangerous account is the one nobody closed.People leave; their access often doesn’t. Why leavers keep their keys, and a thirty-minute review that finds them.
- You can’t patch what you can’t see.Most update problems are inventory problems. How to build an asset inventory in a week, and the four columns that make it useful.
- A backup isn’t a plan until you’ve restored from it.Backups fail quietly, and you find out on the worst day. How to rehearse recovery, and the two numbers every business should know.