The Post-AI Security Floor

What to lock down first during The Hackening
November 1, 2026

Hand-drawn diagram titled The Post-AI Security Floor with three numbered steps: know everything you have shipped, get it off the open internet, and lean on big vendors instead of small ones

I have some critical recommendations that I think every person and company should follow as we all go through The Hackening together.

1. Have a full list of everything you have shipped online ​

Every website, every app, every API, every database, every container, etc. Don’t worry about a fancy database if you don’t have one already. Just get the stuff in a Markdown file. Or a spreadsheet. Whatever you’re most comfortable with.

Attackers are already using AI to do 24/7 recon on everything you have. The old staging server and the API you never turned off are what they find first.

2. Remove as much of your exposure as possible from “the internet” ​

The unique thing about the current agentic / swarm hacking situation is that it’s a nasty mix of extreme persistence + the ability to actually write new exploits. In the olden days you could just put everything behind a VPN, or SSH, or a proxy of some sort. Nobody should be trusting anything right now. Or at least as little as possible.

A charcoal firestorm of purple flame burns exposed server cabinets on the left, while on the right a person hauls a heavy stone vault door shut, their own server rack safe inside

Two solutions I really like for this are Tailscale, and Cloudflare Tunnels. Can they be hacked too? Sure they can, but it’s likely that many people would know very quickly if they were, and in the meantime you won’t have all your apps and APIs and services flapping in the internet wind while this fire is blazing.

3. Reduce your reliance on small security vendors with tons of people’s credentials ​

They are the dangerous combination of being too small and underfunded to counter agentic and nation state attackers + being extremely juicy as targets. That is not the place to be right now.

Go down the vendor column from step 1 and ask what you lose if each one gets popped tomorrow. Move what you can to the big platforms you already use, like your OS or your cloud provider, and cut the rest down to the minimum.

Summary ​

  1. Make a list of everything you've shipped online, even if it's just a Markdown file
  2. Take as much of it off the open internet as you can, with something like Tailscale or Cloudflare Tunnels
  3. Get your most sensitive credentials away from small vendors that are juicy targets and badly outmatched
  4. I'll keep adding to this list as the fire keeps burning

Notes

  1. 🤖 AIL 2: Daniel wrote the original recommendations in this post. I (Kai, his AI assistant) added a few lines to each section, the links, asides, callout and tutorial, made the header diagram, bolded key statements, joined short paragraphs, wrote the subtitle and summary, and made the fire illustration. Learn more about AIL.