Skip to main content

Sysdig Adds Runtime to Secure AI Coding Agents

Sysdig this week at the RSA Conference (RSAC) revealed it has created a runtime that makes it possible to securely deploy artificial intelligence (AI) coding tools.

Jonas Rosland, director of the open source program for Sysdig, said the runtime makes it possible to monitor the activity of AI coding agents in real time, including potential credential risks. It also enables investigation of incidents involving AI agent activity, he added.

Additionally, AI agents can be prevented from opening sensitive files or bypassing credential controls. Risky command-line arguments that weaken safeguards, such as allowing unrestricted file writes, are also prevented.

Dangerous activity with developer environments, including reverse shells, binary tampering, and persistence mechanisms, can also be prevented.

As AI coding tools are made available to both professional and citizen-developers alike, the likelihood of a cybersecurity incident involving these tools continues to rise. DevSecOps teams need to enable application developers to safely add plug-ins and skills to these tools. The challenge is that skills can also include a malicious prompt that could potentially instruct an AI agent to, for example, delete a database running in a production environment, noted Rosland.

The only way to prevent those types of attacks is to be able to observe what an AI agent is doing at a granular level, he added. Otherwise, the speed at which AI agents are able to access directories, files and external resources will overwhelm and bypass existing safeguards, said Rosland.

Each application development team will need to determine to what degree to invest in AI coding tools, but a recent Futurum Group survey finds a full 60% of respondents reporting their organization is now actively using AI to build and deploy software.

Mitch Ashley, vice president and practice lead for software lifecycle engineering for the Futurum Group, said AI coding agents operating in development environments have created a runtime threat surface that governance policy alone cannot contain. Sysdig’s agent runtime signals that controlling AI coding tool behavior requires execution-layer enforcement to provide real-time visibility into agent activity, he added.

For DevSecOps teams extending AI tools to citizen developers, the risk is concrete, noted Ashley. Malicious skills can instruct agents to access unauthorized credentials, tamper with binaries, or delete production data. Runtime enforcement is the control layer that determines what agents can actually execute, said Ashley.

No one knows for sure how proactive DevSecOps teams will be when it comes to securing AI coding tools. It may require a few more major incidents until the full scope of the threat is fully appreciated. In the meantime, DevSecOps teams should remind application developers who experiment with emerging technologies of the potential risks. The more isolated the application development environment being used to write code using AI agents the better. After all, the danger only really manifests when AI agents start accessing every data source available so the most important thing may be to create a sandbox where they are contained to the fullest extent possible.



from DevOps.com https://ift.tt/ohi6RIk
Labels:

Comments

Post a Comment

Popular posts from this blog

Cursor’s New SDK Turns AI Coding Agents Into Deployable Infrastructure

For most of its life, Cursor has been an IDE. A very good one. But with the public beta of the Cursor SDK, the company is making a different kind of move — one that should get the attention of DevOps teams. The Cursor SDK is a TypeScript library that gives engineers programmatic access to the same runtime, models, and agent harness that power Cursor’s desktop app, CLI, and web interface. In short, the agents that used to live inside an editor can now be invoked from anywhere in your stack. That’s a meaningful shift in how AI coding tools fit into software delivery pipelines. From the Editor to the Pipeline If you’ve used Cursor before, the workflow is familiar — you interact with an agent in real time, asking it to write functions, fix bugs, or review code. The SDK breaks that dependency on interactive use. Now you can call those same agents programmatically, from a CI/CD trigger, a backend service, or embedded inside another tool. Getting started is a single inst...
Post a Comment
Read more

Mistral Moves Coding Agents to the Cloud — and Gets Out of Your Way

For the past year or so, AI coding agents have been tethered to your local machine. You kick off a task, watch the terminal, and babysit every step. It works — but it’s not exactly hands-free. Mistral just changed that. On April 29, the Paris-based AI company announced remote coding agents for its Vibe platform, powered by a new model called Mistral Medium 3.5. The idea is simple: Instead of running coding sessions on your laptop, they now run in the cloud — asynchronously, in parallel, and without you watching over them. What’s Actually New Coding sessions can now work through long tasks while you’re away. Many can run in parallel, and you no longer become the bottleneck at every step the agent takes. That’s the core pitch. You start a task from the Mistral Vibe CLI or directly from Le Chat — Mistral’s AI assistant — and the agent handles the rest. When it’s done, it opens a pull request on GitHub and notifies you, so you review the result inste...
Post a Comment
Read more

OpenAI Debuts Symphony to Orchestrate Coding Agents at Scale

OpenAI has unveiled Symphony, an open-source specification that shifts how software development teams deploy AI in workflows, moving from interactive coding assistance toward continuous orchestration of autonomous agents. Symphony reframes project management tools as operational hubs for AI-driven coding. Rather than prompting an assistant for individual tasks, developers assign work through issue trackers, allowing agents to execute tasks in parallel and deliver outputs for human review. The change reflects a trend in enterprise AI in which systems are increasingly embedded into production pipelines rather than used as standalone tools. Symphony emerged from internal experimentation at   OpenAI , where engineers attempted to scale the use of   Codex   across multiple concurrent sessions. While the agents proved capable, human operators became the limiting factor. Engineers found they could only manage a handful of sessions before coordination overhead offset pro...
Post a Comment
Read more