Skip to content
Cyber60

Fortune Cyber60

CISO Survey

Welcome to the Cyber60

Fourth Edition

At Lightspeed, we’ve been investing in enterprise founders for over 25 years. Cybersecurity investing is one of the pillars of our global enterprise practice, and a focus area of deep immersion and commitment.

This report also shares the results of our annual CISO survey, conducted once again with Wakefield Research. Wakefield surveyed 200 chief information security officers (CISOs) at U.S. companies with $500 million or more in revenue. Several questions repeat from last year so we can track changes. Most are new, with a focus on AI agents and the controls companies use to govern them.

A year ago we asked CISOs about AI as a threat and a tool. This year we asked them about AI agents: software that can take actions inside the enterprise. Agents are already in production at 77% of the companies we surveyed. Among companies using or exploring agents, only one in five say they have a full inventory of them, and a quarter use or would use human credentials to authenticate agents. Across the full sample, 88% already let AI take at least some response actions with no human in the loop.

Security is formally involved in AI governance at 78% of these companies, down from 87% last year. The share where security leads the process fell from a third to a fifth. Confidence that in-house teams can handle AI-specific risk fell too. Budgets are still going up, and 85% of CISOs plan to hire or reskill for AI security within the year.

The survey shows where CISOs plan to spend and hire, and where they need better tools.

Lightspeed is proud to build with several of the companies recognized in this report.
We congratulate every company in the 2026-27 Cyber 60 for their contributions to safeguarding our world.

The Cyber60 Podcast

Episode

The Cyber60 Podcast:
Meet the Minds Forging Security for an AI-Powered World

Listen and follow

CISO Survey

Securing the Agent Enterprise

The 2026-27 Lightspeed Cyber 60 CISO survey finds that companies are deploying AI agents while still building the controls to govern them. Our survey of 200 CISOs at companies with $500M+ in annual revenue shows agents running in production at 77% of organizations. Among companies using or exploring agents, only a third use or would use dedicated agent identities with scoped permissions. Compromised or hijacked agents now tie AI-generated phishing and deepfakes as the top AI threat, and agent identity and access governance is the tool category CISOs most plan to evaluate in the year ahead.

79% of CISOs report a confirmed or suspected AI-related incident in the past 12 months, up from 75%. Confidence that in-house teams can assess and mitigate AI risk dropped from 71% to 55%. Spending continues, with 85% expecting budgets to rise and 82% committing more than 5% of the security budget to AI.

  • 77% have AI agents in production
  • 79% experienced a confirmed or suspected AI-related security incident in the past 12 months
  • 88% already allow AI to execute at least some response actions without human approval
  • 55% are fully or mostly confident in their team’s in-house AI security skills, down from 71% last year

AI Threat Landscape

AI-Related Security Incidents (Past 12 Months)

AI-related security incidents, 2026 vs. 2025

  • Yes, at least one confirmed incident 16% in 2026 37% in 2025
  • Yes, at least one suspected incident (unconfirmed) 63% in 2026 38% in 2025
  • No, but we have detected AI-related attacks or attempts 20% in 2026 16% in 2025
  • No, and we have not detected any attacks or attempts 1% in 2026 9% in 2025

Critical Finding

79% of CISOs report a confirmed or suspected AI-related incident in the past year, up from 75%, and 99% have at least detected AI-related attack attempts. Confirmed incidents fell from 37% to 16%, while suspected-but-unconfirmed incidents rose from 38% to 63%. Another 20% detected AI-related attack attempts without reporting an incident, leaving just 1% reporting neither. Within the incident total, confirmed incidents fell from 37% to 16%, while suspected but unconfirmed incidents rose from 38% to 63%.

Perceived Threat Level of AI Attacks (Next 12 Months)

Threat posed by AI-generated or AI-augmented attacks, 2026 vs. 2025

  • Severe threat 15% in 2026 10% in 2025
  • Moderate threat 56% in 2026 57% in 2025
  • Minimal threat 29% in 2026 32% in 2025
  • No meaningful threat 1% in 2026 2% in 2025

Key Insight

71% of CISOs rate AI-driven attacks a moderate or severe threat for the coming year, up from 67%. The share calling the threat severe rose by half, from 10% to 15%.

Top AI-Related Threat Vectors

AI-related threat vectors of greatest concern (select up to 5)

  • AI-generated phishing / deepfakes 51%
  • Compromised or hijacked AI agents acting inside our environment 51%
  • Shadow AI / unsanctioned employee usage 42%
  • Ungoverned non-human identities / agent credentials 41%
  • Agent tool and integration supply chain (e.g., MCP servers, plugins, connectors) 40%
  • Prompt injection / jailbreaks 36%
  • Synthetic identity fraud 34%
  • Data poisoning 32%
  • Model exfiltration 31%

Key Insight

Last year’s list focused on phishing, synthetic identities, and LLM-powered malware. This year, compromised or hijacked agents tie AI-generated phishing and deepfakes at 51%. Three of the top five concerns involve agents: hijacking, ungoverned agent credentials (41%), and the tool and integration supply chain (40%). Prompt injection, which can be used to hijack agents, sits at 36%.

Concern about ungoverned non-human identities runs higher among CISOs who say a vendor’s AI strategy is very or critically important to them (48%) than among those who say it matters less (27%).

“CISOs are worried about agents they deployed in their own environments being turned against them. Hijacked agents now rank alongside AI-generated phishing and deepfakes as their top concern. Confirmed incidents fell while suspected incidents rose sharply. To me, that raises a question about how well security teams can establish when AI was involved.”
Tal Morgenstern Partner, Lightspeed

Agents in the Enterprise

Current Use of AI Agents

Which statement best describes your company’s current use of AI agents today?

  • AI agents are in production across multiple business functions 21%
  • AI agents are in production in a limited set of functions 56%
  • Exploring or piloting AI agents, but nothing is in production yet 22%
  • Not currently pursuing any initiatives related to AI agents 2%

Key Insight

Agents are in production at 77% of surveyed companies, and 98% are using, piloting, or exploring them. Only 2% have no agent initiative at all. For most, deployment is still contained to a limited set of functions (56%); one in five runs agents across multiple business functions.

Companies whose security teams are mostly or fully confident in their AI skills are further along: 85% have agents in production, against 66% of companies with less confident teams.

Agent Inventory

Does your organization maintain (or plan to maintain) an inventory of the AI agents operating in your environment? (Asked among those exploring agents or with agents in production, n=196)

  • Yes, a complete inventory 20%
  • Yes, a partial inventory 74%
  • No, but we are building one 5%
  • No, and we have no current plans to 0%
  • No, we do not plan to do this 1%

Key Insight

Nearly every company using or exploring agents keeps some inventory (94%), but only one in five calls it complete. Three in four are working from a partial list. Security teams need to know which agents are operating before they can govern their access.

How Agents Authenticate

Which best describes how AI agents authenticate (or would authenticate) to systems in your environment? (Asked among those exploring agents or with agents in production, n=196)

  • Dedicated per-agent identities with scoped permissions 34%
  • A mix of the above 26%
  • Human user credentials passed to agents 26%
  • Shared service accounts 15%

Critical Finding

Only a third of companies using or exploring agents select dedicated per-agent identities with scoped permissions as their current or intended approach. A quarter use or would use human credentials, which can give an agent the user’s access and make its actions harder to distinguish in an audit log. Another 15% select shared service accounts, and 26% use a mix. Agent identity governance is the category CISOs most plan to evaluate this year (55%).

“A quarter of these companies use or would use human credentials for agents. That can give the agent the person’s permissions and leave security teams struggling to tell who did what. Agents need their own identities and limits on what they can access. CISOs put identity governance first on their list of tools to evaluate.”
Guru Chahal Partner, Lightspeed

Organizational Context and Governance

Security Team Size

Full-time security personnel, 2026 vs. 2025

  • Less than 25 29% in 2026 20% in 2025
  • 25 to 49 35% in 2026 29% in 2025
  • 50 to 99 34% in 2026 32% in 2025
  • 100 or more 3% in 2026 20% in 2025

Key Insight

This year’s respondents run smaller security teams than last year’s: a median of 35 full-time security staff, against 50 in 2025, and only 3% with 100 or more. Nearly two-thirds (64%) run teams of under 50. Companies at $1B+ in revenue report a median of 50; those between $500M and $1B, 25.

Role of Security in AI Governance

Which best describes the role of the cybersecurity function in your company’s AI governance? 2026 vs. 2025

  • Security is driving the governance process 21% in 2026 33% in 2025
  • Security is one voice among many (e.g. compliance, data, legal) 57% in 2026 54% in 2025
  • Security is not formally involved in AI governance 21% in 2026 13% in 2025
  • We do not have AI governance policies 1% in 2026 1% in 2025

Critical Finding

Security is losing ground in AI governance. The share of companies where security drives the process fell from 33% to 21%, while the share where it is not formally involved rose from 13% to 21%. A year ago we wrote that security needed to move from participant to leader. This year, 57% describe security as one voice among many, alongside functions such as legal, compliance, and data.

Among CISOs who report no confirmed or suspected AI-related incident in the past year, 48% say security drives AI governance, against 13% of those who report one. Among CISOs whose teams are mostly or fully confident in their AI skills, 31% say security leads, against 9% of less confident teams. Security leadership is associated with fewer reported incidents and greater confidence; the survey can’t establish whether it causes either.

“When I look at how enterprises buy, the org chart tells you more than the budget line. This year, fewer CISOs say security leads AI governance, and at a fifth of these companies it isn’t formally involved. Companies where security leads also report fewer incidents. For a founder selling into this market, one of the first questions should be who owns AI risk at the account.”
Justin Shen Partner, Lightspeed

AI in Security Operations

Current AI Tool Deployment in the Security Stack

Which areas of your security stack are already leveraging AI tools internally? (Select all that apply)

  • AI security posture management (AI-SPM) 43%
  • SOC / SIEM (e.g., threat detection, log triage) 42%
  • Vulnerability management 42%
  • Identity and access management 38%
  • Endpoint protection / XDR 37%
  • Application security 36%
  • DSPM / data security 34%
  • Insider threat detection 33%
  • Agentic SOC (AI analysts performing autonomous triage or investigation) 30%
  • Non-human identity management 26%
  • None of these 1%

Key Insight

AI is in use somewhere in the security stack at 99% of companies. AI-SPM leads at 43%, just ahead of SOC/SIEM and vulnerability management (42% each). Agentic SOC, where AI analysts triage and investigate on their own, is running at 30%. Non-human identity management has the lowest adoption at 26%, despite CISOs’ concern about agent credentials.

CISOs with confident teams are ahead on AI-SPM (49%, versus 34% of less confident teams), and CISOs who say they have had no AI incident are more likely to run AI in vulnerability management (55%) and IAM (57%).

Planned AI Security Tool Evaluations (Next 12 Months)

Categories of AI security tools planned for evaluation in the next 12 months (Select all that apply)

  • Agent identity, authorization, and access governance 55%
  • AI-powered risk scoring / behavior analytics 49%
  • Runtime guardrails for AI agents in production 48%
  • Model firewalls / API layer security 46%
  • LLM red teaming / jailbreaking tools 44%
  • Secure inference platforms (e.g. sandboxed LLMs) 43%
  • Autonomous pen testing / AI red team agents 40%

Future Focus

Every CISO surveyed plans to evaluate at least one category of AI security tool this year. Agent identity, authorization and access governance leads at 55%, followed by AI-powered risk scoring and behavior analytics at 49% and runtime guardrails for agents at 48%. Identity and runtime controls address the access and visibility gaps in the agent findings. Last year’s leading categories were model access governance and secure inference.

AI-Generated Code and Application Security Workload

How has the growth of AI-generated code changed your application security workload?

  • Increased it significantly 20%
  • Increased it somewhat 67%
  • No meaningful change 8%
  • Decreased it somewhat 5%
  • Decreased it significantly 0%

Critical Finding

AI-generated code has added to the application security workload at 87% of companies, and for one in five the increase is significant. No CISO reported a significant decrease, and none said their company does not deploy AI-generated code. Among companies with agents in production, 92% report more AppSec work, against 70% of those still piloting. Only 36% of companies use AI in application security.

“The speed at which AI agents can infiltrate an environment demands a fundamental change in how security teams detect and respond to attacks. CISOs need to rethink how quickly their teams can identify a threat, investigate it and take action. There's a significant opportunity for tools that shorten the time from detection to containment.”
Anoushka Vaswani Partner, Lightspeed

Autonomous Response

AI Executing Response Actions Without Human Approval

Are any security response actions (e.g. blocking traffic, isolating endpoints, revoking credentials) executed autonomously by AI in your environment today, without prior human approval?

  • Yes, broadly across our response workflows 17%
  • Yes, for a narrow set of low-risk actions 71%
  • No, a human approves every response action 12%
  • No, and we have no plans to allow it 1%

Critical Finding

AI is already taking response actions without human sign-off at 88% of companies. Most (71%) limit that autonomy to a narrow set of low-risk actions, while 17% allow it broadly across their response workflows. Only 12% require a human to approve every action, and 1% have ruled autonomy out.

Companies with confident teams appear to allow more autonomy (92% versus 82%), and the share requiring human approval for every action is more than twice as high among teams that emerge less confident (18% versus 7%).

What It Would Take

We asked CISOs, in their own words, what would have to be true for them to let an AI agent take containment or response actions without human approval. In a rough tally of the 200 answers, six in ten named proven accuracy, a track record or testing. Roughly three in ten named scoped permissions or predefined limits on what the agent can touch, about a quarter named audit logs and monitoring, and about one in five named rollback or reversibility.

Selected responses

  • “Only with bounded low-impact blast radiuses, deterministic rollbacks, strict scope constraints, real-time logging, and exceptionally low false positive error rates.”
  • “Agent can only act within a narrow scope like isolating a compromised endpoint or blocking malicious traffic. Anything bigger still needs human approval.”
  • “The agent would need to prove its decisions are safer than waiting for a human analyst.”
  • “The AI’s handling logic is completely transparent and explainable; the scope of risk impact is strictly limited; and all AI operations can be terminated with a single click in the event of an anomaly.”
  • “It would have to achieve a proven zero false-positive track record during a long trial period in our sandbox.”
  • “Reversibility is very important. If the AI could be undone, or didn’t have a large effect on something, then I would be more willing to let it automate some tasks.”
  • “There should be clear rules for high-risk situations. I’d be comfortable with automatic containment for obvious threats, but anything involving sensitive data or major business impact should still require a human.”
  • “Containment must be strictly isolated from physical machinery control, preventing any automated response from halting factory lines.”
  • “Actions must be confined entirely to sandboxed builds, revoking malicious artifacts without blocking core CI/CD release pipelines.”
  • “Safe autonomous response capabilities should be verified by independent validation.”
  • “Vendor accepts liability for any agent-caused damage.”

Vendor Strategy and Procurement

Importance of a Vendor’s AI Strategy

How important will a vendor’s AI strategy be in your evaluation process in 2026-27? 2026 vs. 2025

  • Critically important 13% in 2026 23% in 2025
  • Very important 52% in 2026 59% in 2025
  • Somewhat important 34% in 2026 19% in 2025
  • Not too important 2% in 2026 0% in 2025
  • Not important at all 0% in 2026 0% in 2025

Key Insight

A vendor’s AI strategy still matters to nearly every CISO (98% call it at least somewhat important), but it matters less than it did. The share rating it very or critically important fell from 82% to 65%, and the share calling it critically important dropped from 23% to 13%. CISOs may now expect AI capability from every vendor, or they may be more skeptical of vendors’ claims. The survey doesn’t establish why the ratings fell.

CISOs at larger companies assign less importance to vendor AI strategy: 57% of those at companies with 2,500 or more employees rate it very or critically important, against 72% at smaller companies. CISOs with confident teams are more likely to give those ratings (78%) than those with less confident teams (48%).

Consolidation vs. Point Solutions

Are you more likely to consolidate vendors or adopt new point solutions in response to AI-driven needs? 2026 vs. 2025

  • 53% Adopt AI-native point solutions 2025: 53%
  • 48% Consolidate into fewer platforms 2025: 47%

Split Strategy

CISOs remain almost evenly divided between AI-native point solutions (53%) and consolidation into fewer platforms (48%). Preferences differ by incident history: 60% of CISOs who report a confirmed or suspected AI-related incident favor point solutions, while 73% of those who report neither favor consolidation. Among consolidators, 25% call the AI threat severe, compared with 6% of point-solution buyers.

“The consolidation-versus-point-solution split has barely moved in a year. About half of CISOs still favor specialist products, and that rises to 60% among those who report an AI incident. CISOs who report no incident are more likely to favor consolidation. There’s room to build a large company on either side, as long as you know which buyer you’re selling to.”
James Ephrati Partner, Lightspeed

Budget and Investment Outlook

Cybersecurity Budget Changes (Next 12 Months)

Expected change in cybersecurity budget over the next 12 months, 2026 vs. 2025

  • Increase significantly 12% in 2026 20% in 2025
  • Increase moderately 73% in 2026 68% in 2025
  • Stay flat 13% in 2026 10% in 2025
  • Decrease moderately 3% in 2026 2% in 2025
  • Decrease significantly 0% in 2026 0% in 2025

Budget Momentum

85% of CISOs expect their budgets to grow in the next 12 months, down slightly from 88%. The shift is from significant to moderate growth: the share expecting a significant increase fell from one in five to 12%. Only 3% expect any cut. Smaller companies are more bullish, with 91% of those under 2,500 employees expecting an increase against 77% of larger ones, and 92% of companies between $500M and $1B in revenue against 79% of those at $1B+.

AI Budget Allocation (% of Security Budget)

Percent of security budget allocated to AI-related tools or initiatives, 2026 vs. 2025

  • None 0% in 2026 0% in 2025
  • 1%-5% 18% in 2026 15% in 2025
  • 6%-10% 52% in 2026 59% in 2025
  • 11%-25% 29% in 2026 24% in 2025
  • More than 25% 2% in 2026 3% in 2025

Key Insight

Every CISO surveyed allocates some security budget to AI, and 82% allocate more than 5%. The 6%-10% band shrank from 59% to 52%, while the share allocating more than 10% rose from 27% to 31% and the share at 5% or under rose from 15% to 18%. Confident teams are more likely to commit over 5% (89%) than less confident ones (73%).

“From my conversations with CISOs, I expect security budgets to increase substantially as boards grow more concerned about AI-driven attacks. The survey captures current expectations, but the urgency I'm hearing suggests spending could rise much faster as companies respond to these threats.”
Anoushka Vaswani Partner, Lightspeed

Skills and Talent

Confidence in In-House AI Security Skills

Confidence that the team has the in-house skills to assess and mitigate AI-specific security risks, 2026 vs. 2025

  • Fully confident 9% in 2026 16% in 2025
  • Mostly confident 47% in 2026 55% in 2025
  • Somewhat confident 43% in 2026 29% in 2025
  • Not too confident 3% in 2026 1% in 2025
  • Not confident at all 0% in 2026 1% in 2025

Confidence Gap

55% of CISOs are fully or mostly confident their team can assess and mitigate AI-specific risk, down from 71%. The share fully confident dropped from 16% to 9%, and the share only somewhat confident rose from 29% to 43%. Confidence is lower at larger companies (47% of those with 2,500+ employees are fully or mostly confident, versus 62% of smaller ones) and much lower among companies still piloting agents (35%) than those with agents in production (61%).

Hiring and Reskilling Plans for AI Security

Are you planning to hire or re-skill staff specifically for AI-related security work?

  • We already have 12%
  • Yes, within 6 months 38%
  • Yes, within 12 months 48%
  • Yes, longer than a year from now 3%
  • No plans to 1%

Talent Urgency

99% of CISOs have hired or reskilled for AI security or plan to, and 85% plan to do so within the next 12 months. Only 12% say they already have. Half have already acted or plan to within six months. CISOs who have already hired or reskilled are concentrated among confident teams (17%, versus 6% of less confident teams) and companies with agents in production (16%, versus none of those still piloting).

“I think some of the drop in confidence may come from CISOs getting a clearer view of what their teams can’t do yet. Nearly all have hired or reskilled for AI security, or plan to. Having built an enterprise infrastructure company myself, I’d look for products that give a 35-person security team access to expertise it can’t easily hire.”
Guru Chahal Partner, Lightspeed

In Their Own Words

What CISOs Wish Vendors and Startups Were Solving

We asked: “What’s one AI-related security challenge you wish vendors or startups were solving today?” In a rough tally of the 200 answers, about three in ten were about agents: their access, their permissions, their identities, and what they do when nobody is watching. About a quarter were about sensitive data leaking through AI tools. Prompt injection, AI-generated phishing and deepfakes, and visibility into what AI is doing each drew roughly one in ten.

Selected responses:

  • “Easier management of agent identities and permissions so AI agents only access the systems and data they actually need.”
  • “Better controls are needed to prevent AI agents from gradually expanding their access beyond their original permissions.”
  • “As multiple AI agents start working together, I think there needs to be more focus on securing those interactions. One compromised agent shouldn’t be able to influence or compromise the others.”
  • “Securing dynamic agentic workflows by providing real-time runtime authorization and access control for multi-agent API calls and tools.”
  • “I wish vendors had better tools for monitoring AI agents in real time without creating more noise for security teams.”
  • “Vendors using real behavior to calculate agent trust scores.”
  • “Better safeguards against malicious instructions hidden inside documents, emails, and webpages.”
  • “AI models and datasets should live in a trusted library like an app store where each one has a clear seal of authenticity so we know it’s safe and untampered.”
  • “Automated software bill of materials and supply chain integrity attestation for open-weight model weights, dependencies and fine-tuning datasets.”
  • “Robust guardrails and telemetry for third-party plugins and connectors operating within OT/legacy SCADA interfaces.”
  • “Automatically identifying vulnerabilities created by AI-generated code before deployment.”
  • “Secure data governance for AI tools used across hotel operations. Many teams adopt generative AI to draft guest communications and operational reports, creating risks of exposing PII and guest private data. We want vendors to build lightweight controls that prevent sensitive hotel guest data leakage into large language models.”
  • “I wish they would build tools that can accurately spot deepfake audio and video clones before they fool our team.”
  • “Knowing when to trust an AI alert and when it’s just noise is still a real challenge.”
  • “Vendors should be more open about the hazards associated with their own AI agents.”

The AI Security Opportunity Map

Where CISO Pain Points Signal Market Needs

Last year’s map identified five areas where CISOs needed better tools. Three of them, governance automation, workforce augmentation and shadow AI, remain concerns. This year, agents are in production at three in four companies, and CISOs rank hijacked agents alongside AI-generated phishing and deepfakes as their top threat. Among companies using or exploring agents, only one in five has a complete inventory and only a third select dedicated identities with scoped permissions. We see six areas for builders to help address these needs.

Six High-Priority Opportunity Areas

  1. Agent Identity and Access Governance
  2. Agent Runtime Security
  3. Trusted Autonomous Response
  4. Application Security for AI-Generated Code
  5. AI Data Leakage and Shadow AI Control
  6. Defense Against AI-Generated Deception

1. Agent Identity and Access Governance

The Gap

Among companies using or exploring agents, 34% use or would use dedicated identities with scoped permissions. 26% select human credentials, 15% shared service accounts, and 26% a mix. 41% of CISOs name ungoverned non-human identities and agent credentials among their top threat vectors. Only 26% use AI in non-human identity management, the lowest of any category in the security stack.

Market Opportunity

  • Identity providers and directories built for agents, with per-agent credentials issued and revoked automatically
  • Scoped, just-in-time authorization for agent actions, enforced at the tool and API layer
  • Identity graphs that map which humans, services and agents can reach which data
  • Detection of permission creep, where an agent’s access expands past its original grant
  • Attribution that separates agent actions from the human whose credentials it may be using

Validation

Agent identity, authorization and access governance is the top category CISOs plan to evaluate in the next 12 months, at 55%. In the rough tally of open-ended responses, agent access and permissions was the most common request.

2. Agent Runtime Security

The Gap

51% of CISOs rank compromised or hijacked agents acting inside their environment among their top threats, tied for first. 40% cite the agent tool and integration supply chain (MCP servers, plugins, connectors), and 36% cite prompt injection. Only 20% of companies using or exploring agents have a complete inventory.

Market Opportunity

  • Discovery and inventory of agents, including those deployed outside the security function’s view
  • Runtime guardrails that constrain what an agent can do regardless of what it is told
  • Prompt injection detection for indirect attacks arriving through documents, email and web content
  • Security for the agent supply chain: vetting, sandboxing and monitoring of MCP servers, plugins and connectors
  • Behavioral monitoring and trust scoring for agents, including agent-to-agent interactions

Validation

48% plan to evaluate runtime guardrails for agents in production, 46% model firewalls and API-layer security, and 44% LLM red teaming tools. CISOs asked, in their own words, for “guardrails and telemetry for third-party plugins and connectors” and for ways to ensure “one compromised agent shouldn’t be able to influence or compromise the others.”

3. Trusted Autonomous Response

The Gap

88% of companies already let AI take some response actions without human approval, but 71% limit it to a narrow set of low-risk actions. Asked what they would require for autonomous response, CISOs named proven accuracy and a track record (cited by roughly six in ten), scoped and predefined actions, audit trails, and reversibility. 30% already run an agentic SOC.

Market Opportunity

  • Autonomous response platforms with built-in blast-radius limits, rollback and one-click termination
  • Confidence scoring and evidence trails that explain each action before and after it is taken
  • Simulation and sandbox environments where an agent earns autonomy on recorded performance
  • Independent validation and benchmarking of autonomous response accuracy
  • Policy engines that define which actions an agent may take alone and which escalate to a human

Validation

Only 12% of CISOs require a human to approve every response action, and 1% have ruled out autonomy. Vendors can address CISOs’ stated conditions for autonomous response by demonstrating accuracy, logging and reversibility.

4. Application Security for AI-Generated Code

The Gap

87% of CISOs say AI-generated code has increased their application security workload, 20% significantly. None reported that their company does not deploy AI-generated code. Only 36% use AI in application security.

Market Opportunity

  • Code review and vulnerability detection tuned to the failure modes of AI-generated code
  • Security checks embedded in AI coding tools, so flaws are caught where the code is written
  • Provenance tracking that records which code was generated, by what, from what prompt
  • Policy enforcement for what AI-generated code may touch before it ships
  • AI-driven AppSec that scales review capacity with the volume of code arriving

Validation

More CISOs report increased AppSec work at companies with agents in production (92%) than at those still piloting (70%). One CISO described the need as “Automatically identifying vulnerabilities created by AI-generated code before deployment.”

5. AI Data Leakage and Shadow AI Control

The Gap

42% of CISOs name shadow AI and unsanctioned employee usage among their top threat vectors. In the open-ended responses, sensitive data leaking through AI tools was the second most common challenge CISOs wished vendors would solve, after agent access. 34% have AI applied to DSPM and data security.

Market Opportunity

  • Discovery and control of employee AI tool usage across browsers, endpoints and SaaS
  • Data loss prevention built for prompts, uploads and agent tool calls
  • Policy enforcement for what data may reach which models, including third-party and self-hosted
  • Monitoring of what agents read, retain and send to outside systems
  • Lightweight controls for regulated data in industries where frontline teams have adopted generative AI

Validation

CISOs described the problem in specific operational terms, from “stopping sensitive business data from leaking through AI tools without employees realizing it” to preventing hotel guest data from reaching large language models.

6. Defense Against AI-Generated Deception

The Gap

AI-generated phishing and deepfakes tie with hijacked agents as the top threat category at 51%. Synthetic identity fraud is at 34%. Concern about phishing and deepfakes is highest among CISOs who report no confirmed or suspected AI incident (68%).

Market Opportunity

  • Detection of AI-generated email, voice and video at the point of contact
  • Identity verification that holds up against cloned voices and synthetic documents
  • Behavioral analysis that distinguishes human from synthetic traffic and interaction
  • Human risk platforms that train and test employees against AI-crafted social engineering
  • Protection for high-value workflows (payments, access requests, executive communications) where impersonation pays

Validation

49% plan to evaluate AI-powered risk scoring and behavior analytics in the next 12 months. CISOs asked for tools that “accurately spot deepfake audio and video clones before they fool our team” and that detect “highly convincing AI-generated phishing emails that easily bypass traditional spam filters.”

Cross-Cutting Themes

Agent controls need to work together. Identity, runtime security and autonomous response all require teams to know which agents are operating, what they can access and how to limit their actions. AI-generated code and data leakage add to the workload.

Confident teams report more adoption and investment. CISOs with confident teams are further along on agents (85% in production), more likely to have security leading governance (31%), more likely to run AI-SPM (49%) and more likely to have already hired or reskilled for AI security (17%). The survey doesn’t establish whether those steps built confidence or confidence made them easier to take.

Buying preferences differ by incident history. The near-even split between point solutions and platforms has barely changed in a year. CISOs who report an AI incident favor specialists; those who report none favor consolidation.

Most autonomous response remains limited. 88% already allow some autonomous response, 71% narrowly. CISOs most often named accuracy, scope, logging and reversibility as conditions for allowing AI to act without approval.

Implications for Innovation

  • Address the agent risks CISOs identify. Hijacked agents (51%), ungoverned agent credentials (41%) and the agent supply chain (40%) concern two in five or more CISOs.
  • Understand the buyer’s incident history. CISOs who report an incident are more likely to favor a point solution (60%), to have hired or reskilled for AI security or plan to within six months (54%), and to already run an agentic SOC (35%).
  • Build in controls for autonomous actions. Include the audit, rollback and scope controls CISOs named as preconditions.
  • Help smaller teams handle the work. Median security headcount in this sample is 35, and 99% have hired or reskilled for AI or plan to.
  • Show what the product does. The share of CISOs who rate a vendor’s AI strategy critically important fell from 23% to 13%.
“The survey gives founders specific problems to work on: identifying agents, controlling what they can access, detecting when they’re compromised and deciding which actions they can take alone. CISOs have named the tools they plan to evaluate. I’d start with those requirements.”
Tal Morgenstern Partner, Lightspeed

Key Conclusions and Implications

Agent deployment is widespread; controls are incomplete. 77% of companies run AI agents in production. Among companies using or exploring agents, 20% have a complete inventory; 34% use or would use dedicated per-agent identities, and 26% select human credentials. CISOs rank hijacked agents alongside AI-generated phishing and deepfakes as their top threat and make agent identity governance their top evaluation priority.

Security leads AI governance at fewer companies. The share where security drives the process fell from 33% to 21%, and the share where it is not formally involved rose from 13% to 21%. Security leadership is associated with fewer reported incidents and greater confidence.

More incidents are suspected; fewer are confirmed. 79% report a confirmed or suspected AI-related incident, up from 75%, and 99% have at least detected attempts. Confirmed incidents fell from 37% to 16% while suspected ones rose from 38% to 63%. 71% rate the coming year’s AI threat moderate or severe, and the share calling it severe rose from 10% to 15%.

Most companies allow limited autonomous response. 88% already let AI take response actions without human approval; 71% only for low-risk actions. CISOs named accuracy, scoped permissions, audit trails, and reversibility as conditions for autonomous response.

Confidence in AI security skills fell. 55% of CISOs are fully or mostly confident in their team’s skills, down from 71%. 99% have hired or reskilled for AI security or plan to, and 85% plan to within the year. Teams are smaller than in last year’s sample, with a median of 35 security staff.

Budgets continue to grow, mostly at a moderate pace. 85% expect budget growth (down from 88%), with fewer expecting significant increases. 82% commit more than 5% of the security budget to AI, and the share committing more than 10% rose to 31%. The share rating a vendor’s AI strategy very or critically important fell from 82% to 65%.

Strategic Imperatives for 2027

Inventory every agent and give each its own identity. Only one in five companies using or exploring agents has a complete inventory. A third select dedicated identities with scoped permissions as their current or intended authentication approach. Establish which agents are running and what each can access.

Put security in the lead on AI governance. The share of companies where security leads fell from 33% to 21%, and at 21% it is not formally involved. Give security responsibility for agent permissions, monitoring and response.

Test controls before expanding autonomy. Require proven accuracy, scoped actions, full logging and rollback before allowing agents to take on more response work.

Plan for AI-generated code as the default. 87% of security teams are carrying more AppSec work because of it. Review capacity has to scale with code volume.

Hire or reskill for the work ahead. 85% of CISOs plan to hire or reskill for AI security within the year. Identify the expertise the team needs to govern agents and review AI-generated code.

Methodology

The Lightspeed CISO Survey was conducted by Wakefield Research among 200 U.S. CISOs at companies with a minimum of $500M in annual revenue, between September 4th and September 14th, 2026, using an email invitation and an online survey. Where year-over-year comparisons appear, 2025 figures are from the Lightspeed CISO Survey conducted by Wakefield Research between July 29th and August 6th, 2025, among 200 U.S. CISOs at companies with a minimum of $500M in annual revenue.

Results of any sample are subject to sampling variation. The magnitude of the variation is measurable and is affected by the number of interviews and the level of the percentages expressing the results. For the interviews conducted in this study, the chances are 95 in 100 that a survey result does not vary, plus or minus, by more than 6.9 percentage points from the result that would be obtained if interviews had been conducted with all persons in the universe represented by the sample. Subgroup findings with base sizes under 100 are directional.

Open-ended responses quoted in this report are lightly edited for spelling and punctuation.