TL;DR: Identity context and runtime behaviour matter more than file-only detection, Pluto Security says, as AI-assisted development and browser-based agents push endpoint protection beyond legacy models. Endpoint controls need to correlate user, workload, and session signals to govern AI tools and high-risk devices.
Editorial analysis by NHI Mgmt Group, based on content published by Pluto Security: “Next-Gen Endpoint Protection vs. Modern AI Risks: What Security Teams Are Missing”.
By the numbers:
- Pluto is officially out of stealth, with $42 million in total funding.
Key questions
Q: Why do AI-enabled endpoints increase identity risk beyond traditional endpoint compromise?
A: Because the endpoint is no longer just a device, it is where identity, session context, and workload behaviour converge.
Q: How do security teams know whether endpoint protection is actually working against modern threats?
A: They know it is working when it detects and contains behaviour, not merely when it recognises known samples.
Q: What breaks when agent security is covered only by endpoint tools?
A: Endpoint-only coverage leaves SaaS-embedded agents and custom cloud agents outside the security view, so the organisation sees activity on laptops but not the wider execution surface.
Practitioner guidance
- Inventory AI tooling on endpoints Track local models, browser agents, plugins, and other AI-enabled execution paths across managed and unmanaged devices so they are visible in policy and incident response.
- Shift detection away from file-only metrics Measure process chains, memory activity, script execution, and abnormal system calls so attacks that use legitimate tools do not disappear from your telemetry.
- Integrate endpoint and identity controls Correlate device telemetry with session and privilege signals so that suspicious endpoint behaviour can trigger access restriction before data exposure spreads.
Bottom line: AI-assisted development and browser-based agents are making endpoint protection a governance issue as much as a technical one.
Glossary terms: Next-Generation Endpoint Protection, Behavioral Detection, Browser Agent, Endpoint-Identity Integration
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
Endpoint trust is no longer a device-only question. AI-assisted work has made endpoint control inseparable from identity context, because browser sessions, tokens, and local automation now move together. If the control plane does not understand who or what is acting from the endpoint, it will miss the real boundary being crossed. Practitioners should treat endpoint trust as a joint device, identity, and session problem.
A few things that frame the scale:
- Claude Code-assisted commits leaked secrets at a rate of 3.2%, more than double the human-only baseline of 1.5%, with peaks reaching 31 secrets per 1,000 commits in August 2025, according to the State of Secrets Sprawl 2026.
A question worth separating out:
A: Yes. When AI-assisted work is already reaching endpoints, the gap between device controls and identity controls becomes a direct risk multiplier. Organisations should make sure they can correlate endpoint behaviour with user, workload, and session context before allowing AI-driven workflows to scale, especially on developer and contractor devices.
👉 Read our full editorial: Next-gen endpoint protection is now a governance issue for AI risk