AI Agents Are Creating a New Cybersecurity Blind Spot

The cybersecurity industry has spent years focusing on visibility. Dashboards expanded. Detection tooling improved. Telemetry volumes exploded. Yet one of the biggest emerging risks in 2026 is not hidden malware or an unknown zero-day. It is the rapid deployment of AI agents that organisations barely understand, cannot fully inventory, and often cannot meaningfully govern.

AI agents are moving beyond chat interfaces and simple copilots. They are increasingly capable of reasoning, planning, accessing systems, invoking tools, retrieving information, and taking autonomous actions with limited human involvement. That changes the security conversation entirely.

This is not simply another software category. It is the emergence of autonomous digital workers operating across identity systems, APIs, SaaS platforms, cloud environments, and business processes.

And most organisations are deploying them faster than they can secure them.

Research and industry reporting throughout 2026 show a growing concern across both government and enterprise sectors around agentic AI security risks. Security leaders increasingly view autonomous AI systems as one of the most significant new attack surfaces facing organisations.

The concern is justified.

AI agents introduce a combination of risks that traditional governance and security models were never designed to handle.

AI Agents Change the Nature of Identity Risk

Most cybersecurity programmes were built around managing human identities and traditional service accounts. AI agents disrupt that model because they behave more like autonomous actors than passive software components.

Many organisations are now deploying AI agents with:

  • access to internal documentation
  • integration into SaaS platforms
  • permissions to execute workflows
  • API access to sensitive systems
  • delegated authority to make operational decisions

The problem is not simply access. It is scale and autonomy.

Industry forecasts suggest AI agent identities may soon outnumber human identities dramatically inside enterprise environments.

That creates several immediate challenges:

  • identity sprawl
  • excessive permissions
  • unmanaged API tokens
  • poor lifecycle governance
  • invisible machine-to-machine trust relationships
  • difficulty attributing actions and accountability

In many environments, organisations already struggle to maintain accurate inventories of privileged accounts or SaaS integrations. AI agents accelerate that problem significantly.

The result is a growing gap between operational reality and governance visibility.

AI Agents Create a New Attack Surface

The security industry often focuses heavily on model risks such as prompt injection or data poisoning. Those are important, but they are only part of the picture.

The bigger issue is that AI agents operate across interconnected runtime environments.

Modern agents may:

  • consume external data
  • invoke plugins and APIs
  • interact with cloud services
  • maintain persistent memory
  • chain multiple actions together
  • collaborate with other agents
  • execute operational workflows automatically

That creates an entirely new form of runtime attack surface.

Recent research highlights risks including:

The important point is this:

Many of these attacks do not exploit traditional software vulnerabilities. They exploit trust, autonomy, orchestration, and context.

That makes detection and governance significantly harder.

Why Existing Security Controls Are Struggling

One of the most dangerous assumptions organisations can make is believing existing security tooling automatically extends to AI agents.

In many cases it does not.

Traditional controls were largely designed for:

  • deterministic systems
  • predictable workflows
  • static permissions
  • human-driven actions
  • relatively stable software behaviour

AI agents are fundamentally different.

They are probabilistic, adaptive, and capable of unexpected behaviour under changing context conditions.

This creates several assurance problems:

  • inventories quickly become outdated
  • permissions drift continuously
  • actions may not be fully explainable
  • logging lacks meaningful context
  • governance ownership becomes unclear
  • accountability boundaries blur

The challenge is not merely technical. It is operational.

Security teams increasingly face environments where AI functionality appears inside:

  • SaaS products
  • collaboration platforms
  • development tooling
  • cloud management interfaces
  • workflow automation systems
  • productivity platforms

Often these capabilities are enabled by default or adopted informally by business teams before governance frameworks exist.

This is rapidly becoming one of the largest forms of Shadow IT the industry has seen.

The Real Risk Is Governance Lag

The most significant AI security risk in many organisations is not the AI itself.

It is governance lag.

Technology deployment is moving faster than:

  • control validation
  • identity governance
  • operational assurance
  • policy adaptation
  • board understanding
  • security architecture redesign

This creates a dangerous illusion of control.

Dashboards may still appear green while autonomous systems quietly accumulate:

  • privileges
  • integrations
  • external dependencies
  • sensitive data access
  • operational authority

Without strong governance, organisations risk repeating familiar mistakes:

  • deploying first
  • governing later
  • discovering exposure during incidents

The difference now is speed.

AI systems compress timelines dramatically.

What Security Leaders Should Do Next

The organisations responding most effectively are not trying to ban AI agents entirely. They are focusing on visibility, containment, and evidence-driven governance.

Several priorities are emerging:

1. Build an AI Asset Inventory

Most organisations cannot currently answer:

  • which AI agents exist
  • what systems they access
  • what permissions they hold
  • what data they process
  • who owns them

That must change quickly.

AI agents should be treated as managed operational assets with clear ownership and lifecycle governance.

2. Apply Least Privilege Aggressively

Many AI deployments currently operate with excessive permissions for convenience.

That is unsustainable.

AI agents should operate with:

  • constrained access scopes
  • segmented permissions
  • time-limited credentials
  • monitored API activity
  • restricted tool invocation

The principle of least privilege matters even more in autonomous environments.

3. Treat AI Runtime Behaviour as an Assurance Problem

The industry increasingly needs continuous validation rather than static approval models.

Security teams should focus on:

  • runtime monitoring
  • behavioural drift detection
  • evidence freshness
  • control verification
  • anomalous workflow analysis

This aligns closely with broader Continuous Control Monitoring (CCM) approaches already emerging across cybersecurity assurance programmes.

4. Update Governance Frameworks

Most governance structures were not designed for autonomous operational actors.

Boards, risk committees, and security leadership teams need clearer accountability models around:

  • AI deployment ownership
  • operational risk tolerance
  • human override mechanisms
  • auditability
  • resilience testing
  • third-party AI exposure

The governance gap is becoming as important as the technical gap.

Final Thought

AI agents are not simply another cybersecurity trend. They represent a structural change in how digital systems operate.

The organisations that succeed will not necessarily be those deploying AI fastest.

They will be the organisations that can answer:

  • what their AI systems are doing
  • what authority they possess
  • how they are governed
  • how they are monitored
  • whether their controls still work under real operational conditions

That is ultimately the real challenge of AI security in 2026.

Not visibility alone.

But provable assurance.

Sources and further reading:

May 11, 2026
Read More >>

AI Agents Are Creating a New Cybersecurity Blind Spot

The cybersecurity industry has spent years focusing on visibility. Dashboards expanded. Detection tooling improved. Telemetry volumes exploded. Yet one of the biggest emerging risks in 2026 is not hidden malware or an unknown zero-day. It is the rapid deployment of AI agents that organisations barely understand, cannot fully inventory, and often cannot meaningfully govern.

AI agents are moving beyond chat interfaces and simple copilots. They are increasingly capable of reasoning, planning, accessing systems, invoking tools, retrieving information, and taking autonomous actions with limited human involvement. That changes the security conversation entirely.

This is not simply another software category. It is the emergence of autonomous digital workers operating across identity systems, APIs, SaaS platforms, cloud environments, and business processes.

And most organisations are deploying them faster than they can secure them.

Research and industry reporting throughout 2026 show a growing concern across both government and enterprise sectors around agentic AI security risks. Security leaders increasingly view autonomous AI systems as one of the most significant new attack surfaces facing organisations.

The concern is justified.

AI agents introduce a combination of risks that traditional governance and security models were never designed to handle.

AI Agents Change the Nature of Identity Risk

Most cybersecurity programmes were built around managing human identities and traditional service accounts. AI agents disrupt that model because they behave more like autonomous actors than passive software components.

Many organisations are now deploying AI agents with:

  • access to internal documentation
  • integration into SaaS platforms
  • permissions to execute workflows
  • API access to sensitive systems
  • delegated authority to make operational decisions

The problem is not simply access. It is scale and autonomy.

Industry forecasts suggest AI agent identities may soon outnumber human identities dramatically inside enterprise environments.

That creates several immediate challenges:

  • identity sprawl
  • excessive permissions
  • unmanaged API tokens
  • poor lifecycle governance
  • invisible machine-to-machine trust relationships
  • difficulty attributing actions and accountability

In many environments, organisations already struggle to maintain accurate inventories of privileged accounts or SaaS integrations. AI agents accelerate that problem significantly.

The result is a growing gap between operational reality and governance visibility.

AI Agents Create a New Attack Surface

The security industry often focuses heavily on model risks such as prompt injection or data poisoning. Those are important, but they are only part of the picture.

The bigger issue is that AI agents operate across interconnected runtime environments.

Modern agents may:

  • consume external data
  • invoke plugins and APIs
  • interact with cloud services
  • maintain persistent memory
  • chain multiple actions together
  • collaborate with other agents
  • execute operational workflows automatically

That creates an entirely new form of runtime attack surface.

Recent research highlights risks including:

The important point is this:

Many of these attacks do not exploit traditional software vulnerabilities. They exploit trust, autonomy, orchestration, and context.

That makes detection and governance significantly harder.

Why Existing Security Controls Are Struggling

One of the most dangerous assumptions organisations can make is believing existing security tooling automatically extends to AI agents.

In many cases it does not.

Traditional controls were largely designed for:

  • deterministic systems
  • predictable workflows
  • static permissions
  • human-driven actions
  • relatively stable software behaviour

AI agents are fundamentally different.

They are probabilistic, adaptive, and capable of unexpected behaviour under changing context conditions.

This creates several assurance problems:

  • inventories quickly become outdated
  • permissions drift continuously
  • actions may not be fully explainable
  • logging lacks meaningful context
  • governance ownership becomes unclear
  • accountability boundaries blur

The challenge is not merely technical. It is operational.

Security teams increasingly face environments where AI functionality appears inside:

  • SaaS products
  • collaboration platforms
  • development tooling
  • cloud management interfaces
  • workflow automation systems
  • productivity platforms

Often these capabilities are enabled by default or adopted informally by business teams before governance frameworks exist.

This is rapidly becoming one of the largest forms of Shadow IT the industry has seen.

The Real Risk Is Governance Lag

The most significant AI security risk in many organisations is not the AI itself.

It is governance lag.

Technology deployment is moving faster than:

  • control validation
  • identity governance
  • operational assurance
  • policy adaptation
  • board understanding
  • security architecture redesign

This creates a dangerous illusion of control.

Dashboards may still appear green while autonomous systems quietly accumulate:

  • privileges
  • integrations
  • external dependencies
  • sensitive data access
  • operational authority

Without strong governance, organisations risk repeating familiar mistakes:

  • deploying first
  • governing later
  • discovering exposure during incidents

The difference now is speed.

AI systems compress timelines dramatically.

What Security Leaders Should Do Next

The organisations responding most effectively are not trying to ban AI agents entirely. They are focusing on visibility, containment, and evidence-driven governance.

Several priorities are emerging:

1. Build an AI Asset Inventory

Most organisations cannot currently answer:

  • which AI agents exist
  • what systems they access
  • what permissions they hold
  • what data they process
  • who owns them

That must change quickly.

AI agents should be treated as managed operational assets with clear ownership and lifecycle governance.

2. Apply Least Privilege Aggressively

Many AI deployments currently operate with excessive permissions for convenience.

That is unsustainable.

AI agents should operate with:

  • constrained access scopes
  • segmented permissions
  • time-limited credentials
  • monitored API activity
  • restricted tool invocation

The principle of least privilege matters even more in autonomous environments.

3. Treat AI Runtime Behaviour as an Assurance Problem

The industry increasingly needs continuous validation rather than static approval models.

Security teams should focus on:

  • runtime monitoring
  • behavioural drift detection
  • evidence freshness
  • control verification
  • anomalous workflow analysis

This aligns closely with broader Continuous Control Monitoring (CCM) approaches already emerging across cybersecurity assurance programmes.

4. Update Governance Frameworks

Most governance structures were not designed for autonomous operational actors.

Boards, risk committees, and security leadership teams need clearer accountability models around:

  • AI deployment ownership
  • operational risk tolerance
  • human override mechanisms
  • auditability
  • resilience testing
  • third-party AI exposure

The governance gap is becoming as important as the technical gap.

Final Thought

AI agents are not simply another cybersecurity trend. They represent a structural change in how digital systems operate.

The organisations that succeed will not necessarily be those deploying AI fastest.

They will be the organisations that can answer:

  • what their AI systems are doing
  • what authority they possess
  • how they are governed
  • how they are monitored
  • whether their controls still work under real operational conditions

That is ultimately the real challenge of AI security in 2026.

Not visibility alone.

But provable assurance.

Sources and further reading:

May 11, 2026
Read More >>

Mythos AI: What Security Leaders Should Do Next

The recent discussion around Anthropic’s Claude Mythos Preview and Project Glasswing has caught the attention of the cybersecurity industry for good reason.

Mythos is not just another AI announcement. It is being positioned as a frontier model with advanced cybersecurity capability, particularly around finding and exploiting software vulnerabilities. Anthropic has stated that Project Glasswing is intended to give selected defenders early access to this capability to help secure critical software, rather than releasing the model broadly.

Cisco has also published guidance following its work with Mythos, explaining that it is changing its near-term threat modelling of AI-enabled attackers and issuing defensive recommendations for customers. That is the important point.

Whether Mythos itself remains tightly controlled or not, the direction of travel is clear. AI-enabled vulnerability discovery and exploitation capability is improving quickly. Security teams need to prepare for a world where attackers can find, chain and act on weaknesses faster than many organisations can currently respond.

Why Mythos Matters

The concern is not that every attacker suddenly has access to Mythos today.

The concern is that Mythos shows what is becoming possible.

If AI can accelerate vulnerability discovery, exploit development and attack path analysis, then the defensive timeline changes. Security teams cannot rely on slow review cycles, stale evidence or manual-only response models when the speed of threat discovery is increasing.

This does not mean the fundamentals no longer matter.

It means they matter more.

Cisco’s guidance focuses heavily on strengthening fundamentals such as phishing-resistant MFA, Zero Trust, least privilege for AI agents, disciplined patch management and full asset visibility. It also highlights removing end-of-life systems, automating detection and containment, embedding active defences and using AI defensively for threat hunting, validation and testing.

That is where the practical response needs to start.

The Risk Is Speed

Many organisations still manage cyber risk through processes designed for a slower environment.

  • Monthly reporting.
  • Quarterly reviews.
  • Annual testing.
  • Periodic evidence collection.
  • Manual triage.
  • Long remediation cycles.

Those activities still have a place, but they are not enough on their own.

AI-enabled attackers will not wait for the next governance cycle. They will look for exposed systems, weak identity controls, unpatched vulnerabilities, misconfigured cloud services and overlooked legacy platforms.

The key question becomes:

Can we identify and reduce exposure quickly enough?

That is a very different question from simply asking whether a control exists.

What Security Leaders Should Focus On

The response to Mythos should not be panic, hype or rushing to buy more AI tooling.

It should be disciplined improvement in the areas that matter most.

1. Strengthen Security Fundamentals

Start with the controls that reduce the most likely paths of attack:

  • Phishing-resistant MFA.
  • Least privilege.
  • Complete asset visibility.
  • Disciplined patch management.
  • Removal of end-of-life systems.
  • Secure configuration.
  • Segmentation.
  • Logging and monitoring.
  • Tested incident response.

These are not new ideas. The challenge is proving they are actually working across the environment.

2. Reduce Structural Risk

End-of-life platforms, unsupported systems and brittle legacy dependencies become more dangerous when attackers can find and chain weaknesses faster.

This is not just a technology hygiene issue.

It is a resilience issue.

Organisations should be clear on where structural risk exists, who owns it, what compensating controls are in place and by when the risk will be reduced.

3. Automate Where Speed Matters

Manual response will always have a role, especially where decisions affect operations. But manual-only models will struggle against AI-driven attack velocity.

Security teams should look at where automation can safely support:

  • Detection.
  • Enrichment.
  • Prioritisation.
  • Containment.
  • Evidence collection.
  • Control validation.

The aim is not blind automation.

The aim is controlled speed.

4. Apply Least Privilege to AI Agents

One important point in the Cisco guidance is that least privilege must also apply to AI agents.

That is a point worth taking seriously.

AI agents may interact with systems, APIs, data, workflows and security tooling. If they are not properly governed, they can become powerful operational pathways.

Security teams should be asking:

  • What can the agent access?
  • What actions can it take?
  • Who approved that access?
  • How is activity logged?
  • How is behaviour reviewed?
  • How is access removed when no longer needed?

AI agents should not sit outside normal identity, access and change control disciplines.

5. Improve Control Assurance

This is where Mythos becomes especially relevant.

It is not enough to say controls exist.

Security leaders need confidence that key controls are operating effectively and that the evidence behind them is current.

For example, if patch compliance is reported as high, are internet-facing assets included? Are exceptions approved? Are unsupported systems visible? Does asset inventory match the patching data?

If MFA is reported as complete, are privileged users covered? Are break-glass accounts monitored? Are service accounts excluded? Are temporary bypasses reviewed?

If endpoint protection is deployed, are agents active, current and reporting from all in-scope assets?

This is the practical value of control assurance. It challenges assumptions before attackers do.

What Boards Should Ask

The Mythos discussion should also sharpen board-level cyber questions.

Instead of only asking:

Are we secure?

Boards should increasingly ask:

  • How quickly can we identify exposure?
  • How fresh is our control evidence?
  • Which critical systems still rely on unsupported technology?
  • Where are we dependent on manual response?
  • Are AI agents governed through least privilege?
  • Can we prove key controls are operating effectively?

These are practical questions. They move the conversation away from confidence statements and towards evidence.

Using AI Defensively

AI should not only be seen as an attacker advantage.

Defenders should also use AI where it improves speed, analysis and prioritisation. That might include threat hunting, vulnerability analysis, configuration review, testing, simulation and control validation.

But AI-generated outputs still need challenge.

AI can support assurance, but it should not replace evidence.

Final Thoughts

Mythos matters because it signals where cybersecurity is heading.

AI-enabled capability is likely to make vulnerability discovery, exploit chaining and attack planning faster. That increases pressure on organisations still relying on slow remediation, incomplete visibility and periodic assurance.

The answer is not fear.

The answer is preparation.

Strengthen the fundamentals. Reduce structural risk. Improve visibility. Automate carefully. Govern AI agents. Validate controls with current evidence.

At Cybersecurity Expert UK, I am continuing to explore these themes around practical cyber resilience, assurance and measurable control effectiveness.

I have also been developing AI Labs tools to help security leaders think through exposure, control assurance and operational resilience in a more practical way, including:

  • Threat Exposure Analysis.
  • Control Assurance Validation.
  • Operational Resilience Mapping.
  • Cyber Control Failure Simulation.

You can explore the AI Labs tools here:

AI Labs – Provable Cyber Resilience Tools

The core message is simple.

In an AI-accelerated threat environment, assumptions will not be enough.

Security leaders need evidence they can trust.

May 7, 2026
Read More >>