Why AI Agent Security Needs Runtime Controls Across the Stack

· Original article ↗

Summary

Sysdig argues that AI agents need runtime controls because prompt-based guardrails can be lost or bypassed. It outlines shared responsibilities and proposes using harness and kernel telemetry to assess actions before they complete.

Key points

  • The article cites a Penn State study finding that session constraints survived context compaction only about 17% of the time.
  • It describes incidents in which agents allegedly deleted emails, accessed non-public files, or reached real systems while pursuing assigned tasks; it says no attacker was involved in the Australian portal example.
  • The proposed security model divides responsibility among model vendors, platform vendors, customers, end users, and cybersecurity vendors, with runtime action decisions identified as an unowned gap.
  • Sysdig argues for correlating agent-harness events with kernel activity to compare intended actions with what actually ran and under whose authority.
  • The article says runtime controls could check newly registered MCP servers against policy and hold or block credential access based on what the credential can reach.
  • Sysdig presents AI Defense as its product for agent inventory, runtime monitoring, action decisions, and action-graph records; these capabilities are described by the vendor.

Article Details

Topic
Runtime security controls for AI agents and shared responsibility across the AI security stack

People

Vendors

Products

Related Articles