My newsletter, Frankly Speaking, is back! I'm launching a freemium version but with more consistent articles and hot takes on my experience as an engineer and former VC working in cybersecurity: franklyspeaking.substack.com…
Subscribe here: franklyspeaking.substack.com…
Who actually gets cheaper security from AI? (in partnership with @Proton_Pass)
AI makes writing a security fix easier. That doesn’t help if nobody knows whether the fix is safe to deploy, who owns the system, or what will break when it changes.
A few thoughts on how AI shifts security costs:
Cheaper work ≠ smaller bills: A team that understands its systems can test and deploy AI-assisted fixes immediately. A team with fragile legacy apps gets the exact same patch and can’t safely touch it.
Architecture beats company size: A 20-person startup with a simple stack and strong engineers can move faster than an enterprise with fragmented ownership and years of accumulated technical debt.
Startups spend earlier: Automated scans aren't new, but following up on them is getting cheaper. Startups can't easily defer baseline security anymore, though doing it well early remains a real sales differentiator.
Subscription cost vs. operational cost: If an AI tool leaves all the configuration, triage, and deployment on the customer, it’s still expensive to own. Vendors have to remove actual work.
Security as infrastructure: Organizations below the cybersecurity poverty line (schools, local hospitals) lack the capacity to operationalize new tools. Baseline defense has to come with the platforms they already use.
franklyspeaking.substack.com…
What makes a security tool actually worth keeping?
Parallel bake-offs: People are the most expensive part of procurement. Running two tools side by side and cutting one is cheaper than paying engineers to debate vendor RFPs for three months.
Critical path, non-strategic: The keepers sit in the critical path (like proxies) where outages break things, but internal maintenance isn't a good use of security's time.
The cost divide: Modern tools make deployment and agent-assisted customization faster, but only for teams with the talent to use them. The security cost spectrum is widening.
Kill the dashboard: Seeing a problem isn't solving it. Tools that survive will automate the mechanical triage and push actions into developer workflows, reserving human judgment for ambiguous edge cases.
Full post: franklyspeaking.substack.com…
I've been cooking on this post for a bit, but with the cyber security events of this week I had to ship it:
Long-live static credentials must die. We never want to rotate API keys again.
Turns out only 8% of cloud and SaaS vendors support secure alternative. This is our call to action to change this AND our commitment to do our part:
- We are requiring vendors on our marketplace to support OIDC
- We shipped @shadcn components to make it easier to ship OIDC configuration
- We are expanding OIDC support on our own platform
The last generation got the web from HTTP to HTTPS. It is on us to move past API keys.
vercel.com/blog/death-to-lon…
Why security teams almost never turn a tool off:
The counterfactual trap: If you keep a useless tool, nobody notices. If you turn it off and an incident happens nearby, you're on the hook. Teams keep shelfware out of self-preservation.
The clean-slate test: When you start over without many tools, you realize how much software you don't actually need. Most teams inherit bloated stacks and never reassess them.
The risk trap: If "risk management" just means avoiding all possible bad outcomes, removing any tool seems irrational.
The real definition of security: It’s not abstract risk matrices. It's introducing calculated short-term disruption to prevent catastrophic long-term disruption. If daily maintenance friction exceeds the blast radius it prevents, sunset it.
franklyspeaking.substack.com…
Security still has too many tools.
Two years into the AI boom, instead of consolidating our stack, we just got a dozen new AI security categories.
A few thoughts on why this keeps happening:
Theoretical risks: Teams buy products based on slick vendor demos of hypothetical attack paths, instead of looking at their own past incident data.
The SIEM myth: The pitch was "cross-source correlation." The reality is that 90% of investigations happen in a single tool (Datadog, EDR, email). SIEMs are mostly expensive workarounds for 30-day SaaS retention policies.
Cheap storage: Modern read-only analytical databases have made long-term log retention cheap. Security buyers just haven't caught up.
The engineering shift: Security was locked out of engineering tools because they couldn't be trusted with production consoles. AI makes querying those tools simple and safe.
Security work is moving into engineering platforms. We don't need another dashboard.
Full piece: franklyspeaking.substack.com…
Does a CISO need to ship code?
I’ve argued that AI will favor technical, hands-on security leaders. But technical work becoming more important doesn’t guarantee the person doing it gets the CISO job.
Engineering could absorb more security work. A risk-focused CISO could remain useful alongside a strong engineering leader.
That would challenge part of my argument, and I should be willing to admit it.
Where I could be wrong: franklyspeaking.substack.com…
How technical does the CISO personally need to be?
OpenAI talking about rogue AIs communicating through fancy temperature side channels, when they can’t even install a recent Linux kernel on their sandboxes. 🙄
it's hard to be strategic in security or even any other part of engineering without being hands on, but it's easier than ever to be hands on.
it'll expose people who aren't strong technically. if you don't know what's technically possible, how can you be strategic?
Top-down security strategy is dead. The future belongs to the technical doer. 🧵
Ten months of autonomous coding tools have completely broken enterprise annual planning. If you spent Q4 drafting a 2026 roadmap, it was obsolete by February.
Here is how the fundamental risk calculus in security has permanently shifted:
1️⃣ The Compressed Timeline: When software moves at machine speed, the luxury of finding a flaw, filing a ticket, and waiting three months for a fix is gone. Latent architectural debt compounds instantly.
2️⃣ Minimal Disruption Fixes: Historically, fixing structural security issues required high developer friction. Today, AI flips that trade-off. Armed with terminal coding agents, security can generate patches, validate against test harnesses, and draft PRs in minutes without disrupting product teams.
3️⃣ Drop the Boundaries: Security cannot be an arm's-length auditing committee. Having rigid boundaries doesn't help. Security must be part of the engineering team, taking direct ownership of code fixes.
4️⃣ Sprints Are Dumb: Tying security to rigid two-week sprints or quarterly epics is broken. Teams must be dynamic and ready to pivot monthly or weekly as models and threats evolve.
5️⃣ How Leaders Stay Technical: Stop reading executive summaries. Read systems architecture docs. Use AI coding agents to submit real PRs. Shadow how your product engineers actually prompt and build.
If you can't read the code, you can't calculate the risk.
Full analysis on the practitioner's edge: franklyspeaking.substack.com…
Enterprise cybersecurity is no longer one market. 🧵
The biggest takeaway from @blackhatevents US 2026 is that the industry has permanently split in two:
1️⃣ The Infrastructure Divergence: When everyone had on-prem servers and corporate laptops, security was predictable. Today, an AI-native company deploying code at machine speed has completely different risks than a legacy firm managing physical infrastructure.
2️⃣ Dashboards vs. Platforms: Risk managers at legacy firms want visual dashboards and compliance reports. Technical leaders at AI companies want programmable APIs and open context layers that integrate directly into their CI/CD pipelines. One product cannot serve both.
3️⃣ The GTM Mismatch: Sales reps running 2010s playbooks (headcount qualification, 8-week procurement cycles, gated pricing) fall flat with AI startups that want a 3-day self-serve PoC.
4️⃣ The Booth Illusion: Spending $100k+ on trade show booths made sense when software required in-person installations. Today, pipeline moves over Zoom and Slack via API keys. The opportunity cost of booth spend is massive compared to investing in product velocity.
5️⃣ The Rise of Specialized Events: Catch-all conferences are losing relevance. High-signal, practitioner-driven events (like @unpromptedconf and @defcon villages) are replacing monolithic trade shows.
Stop trying to build security products for "everyone." The future belongs to specialized architectures.
Full analysis on the fragmentation of defense: franklyspeaking.substack.com…#Cybersecurity#Infosec#SecurityEngineering#AI#Startups#TechStrategy#DevSecOps