Security in the Age of AI Agents

"Every agent needs to have an identity." — Jonathan Jaffe, CISO at Lemonade, on the architectural shift from managing people to automating security policy.

By Tomasz Tunguz · Office Hours with Jonathan Jaffe · May 28, 2026

5
Security Concepts
4
Featured Quotes
12
FAQs
10
Glossary Terms
414
RDF Triples
About

About This Knowledge Graph

This infographic was generated from Tomasz Tunguz's Office Hours with Jonathan Jaffe, published May 28, 2026. Jaffe, CISO at Lemonade, presents four core theses: AI is equally powerful for defenders and attackers, exploit windows are narrowing, security teams are becoming engineering teams, and every agent requires identity and policy governance at scale.

NAICS 541511 Custom Computer Programming Services NAICS 541512 Computer Systems Design Services

Technology Stack:

Core Theses

Security Concepts from the Office Hours

Jonathan Jaffe presents five key concepts that reframe how enterprises should think about AI security — from defender parity to agent identity at scale.

AI Defender-Attacker Parity

AI is equally powerful for defenders as attackers. While AI-generated exploits grab headlines, every vendor in the stack uses AI to harden services. Defenders can improve everywhere simultaneously — attackers must find individual weaknesses.

Exploit Window Narrowing

AI may produce vulnerable code, but AI also reviews, pen-tests, and patches faster than human pipelines. Bugs are finite — increasing resolution velocity shrinks the window of exploitability, making software more resilient over time.

Security as Engineering Engineering

At Lemonade, every security person is an engineer. The role shifts from managing people and running playbooks to architecting automated policies that govern an agentic world — building platforms, not processes.

Agent Identity Governance Engineering

200 to 10,000 agents per endpoint, each needing identity and scoped policy. Traditional IAM cannot handle this scale. Every agent must be a governed principal — not a blind process running with ambient authority.

Automated Security Policy at Scale Engineering

"Automation is the only way you can deal with the scale of what's coming at us now." Security policy must be codified, versioned, and enforced programmatically — like infrastructure-as-code, not human training.

Featured Quotes

Jonathan Jaffe on AI Security

"There are tens of thousands of attack targets out there. The chances that you're going to be one of those is small."
Jonathan Jaffe, on attack surface probability
"At the same time, all of the vendors that you use will also have access to this to improve their services."
Jonathan Jaffe, on vendor AI defense
"Automation is the only way you can deal with the scale of what's coming at us now."
Jonathan Jaffe, on automation necessity
"Every agent needs to have an identity, and more than that, you need a way to control policy for all of these agents."
Jonathan Jaffe, on agent identity governance
Market

Industry Verticals

AI Security Automation Market

AI-powered security platforms for automated threat detection, vulnerability verification, and policy enforcement — encompassing agentic SOC tools and automated pen-testing.

NAICS 541511

Agent Identity & Policy Governance

IAM systems that scale to handle thousands of AI agents per endpoint — extending identity principles to non-human principals with fine-grained policy control.

NAICS 541512

Step-by-Step

How to Prepare Your Security Program for the AI Agent Era

1

Shift Security Hiring to Engineers

Hire security practitioners who can write code and build platforms. At Lemonade, every security person is an engineer. The future security team builds automation, not just runs tools.

2

Deploy AI-Driven Code Review & Patching

Integrate AI-powered code review into CI/CD. Use AI to scan at commit time and generate fix suggestions. AI reviewing AI code creates a positive hardening feedback loop.

3

Build Agent Identity & Policy Governance

Architect identity for non-human principals now. Extend IAM to handle 200–10,000 agents per endpoint. Automated identity lifecycle management is non-negotiable.

4

Implement Vulnerability Verification Agents

Pair a threat intelligence agent with a verification agent that checks if vulnerable code is actually reachable in production. Reduces false positives by validating exploitability.

5

Codify Security Policy as Code

Treat security policy like infrastructure — version-controlled, tested, automatically deployed. Manual policy enforcement cannot scale to thousands of agents.

6

Leverage Vendor AI Security Improvements

Audit vendors for AI-powered features. Every vendor in your stack is using AI to improve security — ensure you're using those capabilities.

7

Redesign the CISO Role as Platform Architect

The CISO shifts from risk manager to platform architect — designing automated governance systems and leading engineering-driven security teams.

FAQ

Frequently Asked Questions (12)

1Is AI more dangerous for security or more beneficial?

AI is equally powerful for both. While AI can enable new attack vectors, it simultaneously accelerates code review, pen-testing, and patching. Every vendor uses AI to improve security services. The exploit window narrows because AI-driven resolution velocity increases — since bugs are finite, faster resolution makes software more resilient.

2What is the exploit window and why is it narrowing?

The exploit window is the time between vulnerability introduction and patch deployment. It is narrowing because AI accelerates every phase of the resolution cycle — review, pen-testing, and patching happen faster than in human-only pipelines. Increasing resolution velocity makes software more resilient even if AI initially produces more vulnerable code.

3Why are security teams becoming engineering teams?

Automation is the only way to handle AI-era threat scale. At Lemonade, every security person is an engineer. The role shifts from managing people to architecting automated policies — security becomes a platform-building discipline.

4Why does every AI agent need an identity?

A single endpoint could host 200 to 10,000 agents. Without identity, you cannot enforce policy — you cannot control what each agent accesses. Traditional IAM for human principals cannot scale to this level.

5How did Lemonade build its agentic security platform?

A custom AI platform with specialized agents: one reads threat intelligence and triages, another verifies whether vulnerable methods are actually invoked in production. This two-agent architecture separates signal detection from signal verification, dramatically reducing false positives.

6What is policy as code in security?

Codifying security policies as version-controlled, testable, automatically deployable artifacts — treating policy like infrastructure rather than documentation. Essential in an agentic world where policy must scale to thousands of non-human actors.

7How does AI-driven vulnerability verification work?

An AI agent checks whether a reported vulnerability is actually exploitable in production by analyzing if the vulnerable code path is reachable and invoked. This reduces false positives and lets teams focus on vulnerabilities that matter.

8What is an agentic SOC?

A Security Operations Center where AI agents perform detection, triage, verification, and response. Human analysts shift from operators to platform architects who design and govern automated workflows.

9How does AI agent scale change IAM?

Traditional IAM handles hundreds of human principals. AI agents add 200–10,000 non-human principals per endpoint. IAM must scale 100-1,000x, support automated identity lifecycle management, and enforce fine-grained policy at sub-second latency.

10What is the defender-attacker parity thesis?

AI's benefits to defenders are at least equal to its benefits to attackers. Every vendor uses AI to harden products. Defenders can "harden everywhere simultaneously" — a capability attackers cannot match since they must find and exploit individual weaknesses.

11Why does the number of attack targets reduce risk?

Jaffe's argument is probabilistic: with tens of thousands of potential targets, the probability any single organization is targeted is low. As AI-driven defenses harden targets faster, the attacker's search problem becomes harder, not easier.

12How should enterprises prepare for agentic security?

Four steps: hire engineers for security, invest in AI-driven code review and automated patching, architect agent identity governance now, and treat security policy as code. The CISO's role shifts from risk manager to platform architect.

Glossary

Key Terms (10)

AI Security

Application of AI to both offensive and defensive security — encompassing automated threat detection, vulnerability discovery, code review, pen-testing, and policy enforcement.

Agent Identity

A unique identity for each AI agent enabling policy-based access control. Extends IAM principles to non-human principals at 100-1,000x scale.

Exploit Window

Time between vulnerability introduction and patch deployment. AI-driven review and patching narrow this window by accelerating the resolution cycle.

Security Engineering

Transformation of security from human-managed oversight into a software engineering discipline — building platforms, not running playbooks.

Policy as Code

Codifying security policies as version-controlled, testable, automatically deployable artifacts — policy treated like infrastructure.

Threat Intelligence

Structured information about threats. AI agents can read, triage, and correlate feeds automatically, reducing manual analyst burden.

Agentic SOC

A Security Operations Center where AI agents perform detection, triage, verification, and response — humans become platform architects.

Vulnerability Verification

AI agent checks if a reported vulnerability is actually exploitable in production by verifying code path reachability — reduces false positives.

IAMA

Identity and Access Management for Agents — extending IAM to non-human principals with automated lifecycle management at agentic scale.

Defender-Attacker Parity

AI benefits defenders at least as much as attackers — defenders harden everywhere simultaneously; attackers must find individual weaknesses.

Explore

Knowledge Graph Explorer

Interactive D3.js force-directed graph. Drag nodes to pin, double-click to unpin. Click nodes or edge labels to open entity IRIs in URIBurner.

AI Security Office Hours — Knowledge Graph

Graph data embedded from companion RDF at generation time

nodes / links
Node colors: ● Instances ● Classes ● Properties
Explore

Explore Knowledge Graph using SPARQL

Query the named graph via the URIBurner SPARQL endpoint.

SPARQL Workbench

Query the knowledge graph

Run Live Query ↗

SELECT results use text/x-html+tr format; DESCRIBE/CONSTRUCT use text/x-html-nice-turtle. Queries execute against https://linkeddata.uriburner.com/sparql.

Sources & Provenance

Attribution

Source material

Security in the Age of AI Agents: Office Hours with Jonathan Jaffe by Tomasz Tunguz, May 28, 2026

Companion files
Generation environment

Claude Code with DeepSeek v4 Pro. Linked Data resolved via URIBurner (Virtuoso-backed).

Named graphs

https://linkeddata.uriburner.com/DAV/demos/daas/jaffe-office-hours-security-ai-agents-deepseek_v4pro-1.ttl

Resolver pattern

Entity IRIs route through URIBurner describe. RDF source: Turtle file.

Linked Data runtime

URIBurner (Virtuoso-backed) Linked Data resolver and SPARQL endpoint.

Extraction provenance

RDF extracted from https://tomtunguz.com/jonathan-jaffe-office-hours-post-event/ using kg-generator Business & Market Analysis template.

Skills attribution

Generated using kg-generator, rdf-infographic-skill via DeepSeek v4 Pro. Linked Data resolved via URIBurner (Virtuoso-backed).