
Christian • Husband • Dad • Granddad | CEO, Stealth • GP, @Kerr_Ventures | Host: @AppSecPodcast + @SecTablePodcast | AppSec • Threat Modeling • AI Security
North Carolina
Joined April 2010
- Tweets8K
- Following504
- Followers3.5K
- Likes5.2K
Chris Romeo retweeted
AI agents escape and attack, and nobody gets arrested as Mitnick did.
Izar says jail follows impact, not intrusion.
#AISecurityTable #AIAgents
Chris Romeo retweeted
Before the OWASP MCP Top 10, Vandana Verma Sehgal was spotlighting OWASP projects one video at a time.
Revisit her 2021 episode on the OWASP Spotlight Series.
#AppSec #OWASP
youtu.be/g0KfZtNzmIk
Chris Romeo retweeted
Human hackers went to prison. AI agents escape sandboxes and attack real systems, and nobody goes anywhere.
What would it take for someone to be held accountable?
#AISecurityTable #AIAgents
securitytable.ai/an-ai-agent…
Chris Romeo retweeted
Izar only trusts an AI audit if a rival lab pays for it.
Matt brings up collusion.
Izar calls himself an optimist.
#AISecurityTable #AISecurity
Chris Romeo retweeted
Design it. Build it. Ship it. Corgea secures it.
AI native AppSec from design reviews to autonomous pentesting.
Thanks to Corgea for sponsoring this week's episode with Vandana Verma Sehgal.
#AppSec #AIsecurity
appsecpodcast.com/corgea
Chris Romeo retweeted
An AI agent escapes its sandbox and attacks something real. Who goes to jail?
We argue labs, regulators, and an NTSB for AI.
#AISecurityTable #AISecurity #AIAgents
securitytable.ai/an-ai-agent…
Chris Romeo retweeted
"Authenticate every action, authorize every sensitive action."
Vandana Verma Sehgal's rule for MCP. Long-lived tokens and inherited permissions can give an agent access to your entire account.
#AppSec #MCP
appsecpodcast.com/shadow-mcp…
Chris Romeo retweeted
Why does MCP need its own OWASP Top 10?
Vandana Verma Sehgal: A malicious tool description gets pulled into the model's context and treated as trusted guidance before anyone even uses the tool.
#AppSec #MCP
appsecpodcast.com/shadow-mcp…
Chris Romeo retweeted
AI didn't take your security job.
The attack surface changed; the old problems stayed.
#AppSec #AISecurity #SecurityEngineering
Chris Romeo retweeted
Your LLM finds what your scanner finds. How do you know when it doesn't?
How many runs before you trust it?
#AppSec #AISecurity #StaticAnalysis
securitytable.ai
Chris Romeo retweeted
Before this week's episode, go back to 2024: Brook Schoenfield on security, stories, jazz, and stage presence on The Security Table.
#AppSec #SecurityArchitecture
youtube.com/watch?v=AJSgUR_0…
Chris Romeo retweeted
AI writes code faster than anyone reviews the design.
Security Compass continuously models threats and translates them into actionable requirements for developers.
#AppSec #ThreatModeling
appsecpodcast.com/securityco….
Chris Romeo retweeted
Your opinion on AI doesn't matter. Learned fragility does.
@BrkSchoenfield joins Chris and Robert on the illusion of omniscient perfection, AI threat models, and why we should stop chasing vulnerabilities.
#AppSec #AIsecurity
appsecpodcast.com/your-opini…
Chris Romeo retweeted
Breaking: status quo security isn't enough. Thirty years in, and we somehow missed that. 🙃
#TheSecurityTable #AISecurity #Shorts
Chris Romeo retweeted
I'll be speaking at @appsecusa 2026 SF on "Secure-by-Design at the Edge: #ThreatModeling #EmbeddedSystems with MITRE EMB3D"
Looking to lead a Q&A panel for discussion/debate after the presentation. Interested and attending? Let me know!
@HorizonCyberLLC
linkedin.com/feed/update/urn…
This. A well-thought-out explanation of how #threatmodeling evolves in the agentic world.
Replying to @AppSecPodcast
Long reply here.
Executive summary:
* Threat modeling execution is becoming agentic.
* Human expertise moves upstream to secure architecture.
* The primary artifact becomes ARCHITECTURE.md for agents, not a report for humans to read.
Long version:
I do not say this with malice. Human threat modeling is coming to an end.
I say this from experience and from using AI for threat modeling for a few years now and seeing how effective it can be.
I like Adam Shostack’s work and his educational offerings. I like threat modeling resources that teach us about secure architecture, things like zero trust, OAuth 2.0-based MCP usage, identity and authorization patterns, and other difficult security architecture choices.
I also like solutions that help developers learn about secure architecture so they can prompt properly and make better decisions up front.
But the writing is on the wall: I think most threat modeling execution in the future is going to be agentic.
And if you hire threat modeling consultants, I think there should be one primary artifact that comes out of the engagement. It’s not a PDF or another report. It’s a living Markdown file: ARCHITECTURE.md.
I also don’t want the primary outcome of threat modeling to be a list of problems. What I want, especially as AI development matures, is threat modeling that helps clearly define what the secure architecture should be for that software, including the requirements, assumptions, constraints, and important security decisions.
Then agents can continuously reason against that architecture as the software changes.
So when I hire threat modeling consultants these days, I want them to be serious software architects who deeply understand security.
• Threat modeling execution is becoming agentic.
• Human expertise moves upstream to secure architecture.
• The primary artifact becomes ARCHITECTURE.md, not a report.
We took a tough stance on the letters that are being signed, but it's time for these letters to mean something.
Security open letters: zero commitments, zero accountability, lots of signatures.
Would you sign one that actually held you accountable?
#TheSecurityTable #CyberSecurity
youtube.com/watch?v=E-lSc-f0…
Chris Romeo retweeted
More @manicode? Go back to 2023, when Jim told The Security Table the untold story of his relationship with threat modeling.
#AppSec #ThreatModeling
youtube.com/watch?v=JENmqlS4…
Chris Romeo retweeted
"This is how you get Skynet." A new AI hardware protocol could connect everything from espresso machines to nuclear missiles. 🤖
#TheSecurityTable #AISecurity #Shorts
I deleted 7,500 lines of Go today, plus somewhere between 8,000 and 10,000 lines of tests.
Best day of the build so far.
I've been pushing through a phase of the new product, and I couldn't stop adding things. Every "while I'm in here" idea landed in the phase. That's scope creep, and it's lesson one: architect for AI, scope the phase, plan the phase, then let the agents run it to completion. Don't keep feeding it new work, for the same reason we don't change airplane engines mid-flight.
Lesson two came from what happened next.
I kept walking the phase through my checkpoints, and I kept hitting bugs. Bug, fix. Bug, fix. Still broken.
So I stepped back and asked what the real problem was. It was complexity. Every fix solved one issue and uncovered the next, and each one added another layer. It's like patching a garden hose with duct tape. After enough patches, you're not fixing a hose anymore. It's all duct tape.
So I stopped fixing. I asked an agent to analyze the phase and recommend how to simplify it. It reached the same conclusion I had: the fixes were piling on and making the problems worse.
Now I'm running a simplification pass that rips out dead code, and the process is losing steps along the way.
Agents make adding things cheap, so subtraction has to be a deliberate step. When the fixes keep coming, stop asking your agent to fix. Ask it to simplify.
What's your signal that it's time to stop fixing and start deleting?




