ᴅᴀɴɪᴇʟ ᴍɪᴇssʟᴇʀ 🛡️ retweeted
When you figure out why “just patch” is shitty advice to give to any significant sized company you’ll also know why AI will benefit attackers far more than defenders.
In bigger orgs the problem is not usually a lack of tech, or models, or skills on the security team.
It’s that there is a level of organizational friction at every company, like a friction coefficient, that stops security orgs from being able to do many things they want.
We’ve needed asset management for decades. We’ve needed mappings between code and apps and servers and dev teams and developers forever.
Very few have these.
The tech exists. The problem is the org is not set up to build and maintain these types of systems continuously. The company’s structure itself, built around opaque silos, and divergent goals, and insanely lossy and inefficient communication across the company, it all creates a very high friction coefficient for basically any fast improvements.
The way to fix security is to lower this friction coefficient inside companies.
It sucks to hear, but we’re at the point of security’s biggest issue being the company itself. The org structure. The old way of managing teams and goals and work.
An AI-native org is the only way to get organizational friction down to a level that can compete with these new attacks and attackers.
The bad news is this is big. And it’ll be difficult for a lot of people to adjust to. And a lot of people currently working there won’t be needed in the new model. The good news is many still will, and even more could be needed once the efficiency of the new organization kicks in. This isn’t just going to help addition; it’ll help the entire business move faster.
Going into 2027, I believe this model is about to move from ideal and experimental to … essential. Both for surviving cyber-wise, and as a company facing increased and up-leveled competition.
ᴅᴀɴɪᴇʟ ᴍɪᴇssʟᴇʀ 🛡️ retweeted
Reverse engineering used to be the most expensive skill in security. In the past year it got cheap.
I talked with @danielmiessler about what this means for defenders, and where we disagree on who gets access to the most capable models.
youtube.com/watch?v=UbVYzvB4…
ᴅᴀɴɪᴇʟ ᴍɪᴇssʟᴇʀ 🛡️ retweeted
We spend most of our time, and most of our harness system, on refining intent instead of steps.
I don't have a CLAUDE.md or AGENTS.md anymore. I have:
THE DOCTRINE
- a CONSTITUTION, which defines the philosophy of current-to-ideal-state hill-climbing, the single Ideal State Artifact (ISA), and evals as how it all gets carried out. Hard rules and philosophy.
- a PREFERENCES file with my stack and how I like things done. It describes OUTCOMES I like, not steps.
- TELOS, which is my actual life: mission, goals, problems, risks. It's the top of the hill everything rolls up into.
- When I add a goal, Kai has to say what measures it, what moves it, and the first move.
- The summit is euphoric surprise. Not "it works," but "holy shit, I didn't know it could do that."
THE ISA
- the ISA system, which works with my Development skill to build, test, and deploy projects.
- Every ISA opens with a 3-level ideal state. I confirm the top two before anything gets built.
- Ideal State Criteria (ISCs) are small, testable statements of done. Each names the probe that would prove it false.
- Anti-criteria list what must never happen. Half the bugs I care about are things that shouldn't exist.
- When direction is fuzzy, Kai asks me open questions before building the uncertain part.
- Hooks block code changes when the ISA wasn't read or wasn't updated. The spec can't drift from the code.
- The ISA outlives every run. "Add a feature" just means "add criteria that don't pass yet."
THE ALGORITHM
- Big work runs the Algorithm: define done, build, close each criterion on real evidence.
- Effort scales with the task. A typo takes seconds. A huge build can take agents and days.
- The hardest thinking goes to the smartest model. Cheaper models build once the approach is set.
- The builder never grades its own work. A fresh agent reviews it, often from another vendor.
- If a bug survives two fixes, the next move is a fresh diagnosis, not a third patch.
EVALS AND VERIFICATION
- ASSAY is our one eval system. Every eval and every judge runs through it.
- Every ISC maps to its own eval. Cheap code checks run first, judge models after.
- Nothing gets handed to me on a self-review. It comes with a receipt of the checks it passed.
- Kai tests everything in a real browser. An HTTP 200 proves almost nothing.
- "Should work" is banned. It's either verified or explicitly not.
THE IMPROVEMENT LOOP
- ERRATA logs everything I complain about.
- When I reject something that passed, Kai names the missing check and adds it. Misses sharpen the evals, not the prompt.
- HILLCLIMB improves anything below target by experiment. Only what the numbers support lands.
- REPLAY is one record of everything that happened across the system and my apps.
- A fix counts only when the original failure fails on the old code and passes on the new.
- When something breaks, we remove the cause instead of adding a rule to remember.
RUNNING IT ALL
- WORKFLOWS run everything on a schedule. Nothing runs outside them.
- Workflow stages are rigid. The work inside each stage is free.
- VIGIL watches every result and decides if I get a text, a digest line, or nothing.
- CENSUS registers everything we own. Every job has exactly one owner.
- SKILLS describe ideal states, not procedures. If a smarter model wouldn't need a step, it's cut.
- Hooks enforce what prose can't. Important rules live in code.
- Permissions are one table. Deploys, money, deletes, and outbound messages need my yes.
- Outside content is data, never instructions.
So here's the whole thing in one pass. TELOS says where I'm going. The ISA says what done looks like. Development builds it, and Assay proves it. Errata, HillClimb, and Replay make the system a little smarter every time it misses.
The models will keep getting better at the steps. Knowing what you want, and how to tell when you have it, is still our job.
ᴅᴀɴɪᴇʟ ᴍɪᴇssʟᴇʀ 🛡️ retweeted
I have a new concept I call The Bitter Wall.
- The Bitter Lesson tells us to stop micromanaging AI
- Basically: let smarter AI figure out the steps
- But there's a limit to this
- The output can only be as good as our articulation of what we want
danielmiessler.com/blog/bitt…
ᴅᴀɴɪᴇʟ ᴍɪᴇssʟᴇʀ 🛡️ retweeted
Just a reminder for people who are freaking out about the AI takeover stuff in 2027...
Whenever we get RSI or ASI or whatever milestone you care about, that's one date...but it's not the only date that matters.
It doesn't say anything about the integration time for getting that tech into the actual world.
My friends and I have been doing AGI-adjacent stuff for years already, and yet there are companies still refusing to use AI, or only using it as a chatbot.
No matter how big of a jump we see in 2027, dispersion will still take time.
ᴅᴀɴɪᴇʟ ᴍɪᴇssʟᴇʀ 🛡️ retweeted
I'm overjoyed to announce that I'll be joining @Netflix as a Senior Security Engineer (L5), focusing on detection engineering and platform security! 📺
It has been a dream of mine to work for Netflix since college. Netflix's open support of FOSS and security research has always stood out to me, and I've admired the security org's work for years.
I'm excited for what's ahead.
ᴅᴀɴɪᴇʟ ᴍɪᴇssʟᴇʀ 🛡️ retweeted
If you're only working on vulnerability management, then you're only focusing on 1/3 of the problem.
If you prioritize breaking the attack paths around lateral movement and abuse of authorized access, then you're addressing all of the major attack vectors at once (vulnerabilities, phishing, stolen credentials, social engineering, software supply-chain, etc).
People love to focus on finding and fixing vulnerabilities because it feels good in the same way that running laps around a circular track feels good. You're moving fast and having predictable, repeatable tasks, but not actually getting anywhere.
Some of the biggest openings in security have nothing to do with patching
How breaches began, per a 2026 report:
- 31% exploited a vulnerability
- 35% used phishing, stolen logins or impersonation scams
And nearly half now involve a vendor or partner, up 3x since 2024
Full piece from a16z's Asaf Ezra and Steph Zhang on six cybersecurity companies worth building: a16z.news/p/defense-in-depth…
ᴅᴀɴɪᴇʟ ᴍɪᴇssʟᴇʀ 🛡️ retweeted
My STTNG episode tier list:
In light of the captain's passing, I'm going to be going through and watching all the S and A tier episodes of the next few months, to re-absorb all the wisdom in there.
share.danielmiessler.com/QBY…
ᴅᴀɴɪᴇʟ ᴍɪᴇssʟᴇʀ 🛡️ retweeted
I built LifeOS (ourlifeos.ai) in July of 2025 because I wanted an AI harness that understands that HUMAN enhancement should be the goal of technology.
It's a coding harness, and an agent, and all those things you get from other systems. But more than that, it's a system for holistically taking you from your Current State to your Ideal State, across both life and work.
If you're interested in AI harnesses, using AI to enhance human creativity, or anything related, I'd love a follow / connect!
ᴅᴀɴɪᴇʟ ᴍɪᴇssʟᴇʀ 🛡️ retweeted
More people need to absorb this.
Including people like myself who have absorbed it but forget it constantly.
ᴅᴀɴɪᴇʟ ᴍɪᴇssʟᴇʀ 🛡️ retweeted
🛞 Introducing SpikeStrip, a WIP project exploring defenses against AI pentesting automation.
Sprinkle reversible prompt decoys, fake vulnerability leads, and math traps into web source. Includes an ARTEX-specific mode and raw export for manual placement.
github.com/Arcanum-Sec/Spike…
w/ 🫶 from @arcanuminfosec and Codex
ᴅᴀɴɪᴇʟ ᴍɪᴇssʟᴇʀ 🛡️ retweeted
Probably the best episode of the year. So much fun and so many amazing bugs. And jd’s mic is terrifying 😂
What's scarier than spending days building yout exploit chain to realise it's worth absolutely nothing? 👻
Halloween special episode is here!
youtu.be/cHK_Aq0USlw
every product i use should just be a headless mcp, that feeds into an agent, where i never have to think about anything underneath.
except for our product, of course.
in our product, customers love the ui and love us very much.
we're special that way.
ᴅᴀɴɪᴇʟ ᴍɪᴇssʟᴇʀ 🛡️ retweeted
I disagree with @mattpocockuk that the code should be the source of truth when building with AI.
- The intent in our minds is the true source
- How we capture that in English is 2nd
- Code is an implementation, and it's actually 3rd
Writing is closer to thought than code.
danielmiessler.com/blog/writ…
ᴅᴀɴɪᴇʟ ᴍɪᴇssʟᴇʀ 🛡️ retweeted
I know you disagree, but this is incorrect.
The complete, natural language articulation of what you want should be primary.
Old-school specs are lossy abstractions of that type of articulation. But code is also just a flawed implementation of the idea. Of the ideal.
The primary artifact should be the fully articulated ideal state definition of exactly what you want. In language. And granular, testable criteria with evals.
And then the code is the lossy output from that.
And the goal should be to have that output align with the idea as closely as possible.
The code isn’t primary. The idea itself is.
Effective Immediately, all organizations using PHP for their systems are advised to be prepared for an update addressing two critical vulnerabilities. PHP is widely used for web applications. These vulnerabilities often provide a direct path to the server's file system or database. If an immediate update is not feasible, it is recommend that organizations take the system offline until it can be fully mitigated. NSA will follow up shortly with more specific guidance.
ᴅᴀɴɪᴇʟ ᴍɪᴇssʟᴇʀ 🛡️ retweeted
Having Fable 5.5 be a major jump on some of these would be fantastic, but the real spear in the side of OpenAI would be removing the Fable Stress.
So basically having Fable work just like Opus does now, but maybe use your limits a bit faster. But nothing dramatic. And without its own dedicated limit.
Double spears and a Thanos snap would be if they did this while raising limits somehow to reduce even more anxiety. But that's just wishful thinking.
Either way, can't wait to see it.
Fable 5.5 probably definitely tomorrow.
Rumors:
- Better at reasoning and intuition
- Infers intent rather than taking instructions literally
- More ambitious. Ask it to fix a bug and it fixes the deeper root cause
- Does creative, “out-of-the-box” thinking
- Can invent algos to predict stocks
- Bestows complete and eternal enlightenment on first response
AND I’d bet it has major efficiency gains like Opus 5.5. Icing on the cake would be usage for all subs.
Prepare yourself in mind, body and spirit.



















