DevSecOps for AI Agents
DevSecOps brings security, development, and operations teams together to build secure software from design to deployment.
DevSecOps brings security, development, and operations teams together to build secure software from design to deployment.
AI agents are becoming a core part of how teams build and run applications. They're the ones coordinating workflows, making sense of inputs, and taking action across different systems — all while doing it autonomously. At the same time, 53% of IT security leaders aren’t sure they can deploy AI agents in compliance with regulations and standards.
As AI’s role expands, it demands a shift in security strategy: looking past the code and defending the infrastructure, data, and logic that power it. Aspects like who can access the data, how the model behaves, and what automated decisions are being made are now all firmly within the security scope.
DevSecOps for AI agents is all about applying those familiar DevSecOps ideas to these new systems by embedding security right into how AI is designed, tested, and rolled out. For AI agents, this structure gives us the necessary safety checks to handle these changes without hitting the brakes on progress.
First, there was DevOps, which created a shared system for developer and operations teams to deliver software. Then emerged DevSecOps, which expanded that by pulling security into those same pipelines and processes. Now, with DevSecOps for AI, it’s all about integrating security into the full AI development lifecycle. It treats protection as part of how models are built and deployed rather than a separate review step. Security checks are applied alongside development and release workflows so AI systems evolve within defined guardrails.
AI introduces new kinds of security threats compared to traditional software. The risks go beyond just the code because AI relies on training data, the inputs it gets, and the sometimes unpredictable, probabilistic outputs it generates. AI agents add another layer of complexity: they can take actions across systems, call APIs, trigger workflows, and make decisions based on new information. That expanded autonomy increases the risk of a mistake or malicious prompt.
DevSecOps addresses that complexity by extending DevSecOps practices to cover data handling, model changes, and automated decision paths. This reflects how DevSecOps has matured to meet modern development demands, where security work runs in parallel with delivery instead of trailing behind it.
AI in DevSecOps changes how risk shows up in production. Unlike traditional applications, AI models are constantly learning and changing based on the data and inputs they get. This means their behavior can actually shift without anyone touching the code. That adaptability, while incredibly useful, makes AI more susceptible to manipulation, especially when inputs are intentionally crafted to do damage.
AI agents also operate closer to sensitive data. An agent might routinely process customer records, internal documents, and operational signals to generate decisions or trigger actions. Without strict controls around access, encryption, and usage tracking, that data exposure can spread quickly across training pipelines and runtime interactions. For teams adopting AI for DevSecOps, security has to account for how learning systems behave in real conditions, not just how they were designed to work.
AI agents introduce security challenges because they operate dynamically across systems rather than within a fixed path. They retrieve data, invoke services, and make decisions based on changing inputs. Each interaction expands the surface area that needs protection, especially when agents are granted autonomy to act without manual approval.
As automation increases, governance becomes just as important as technical controls. AI-driven actions must be traceable, attributable, and reviewable to meet regulatory expectations and internal policies. Without consistent monitoring, even well-designed agents can create blind spots as their scope grows.
DevSecOps protects AI agents by embedding security into how models are developed, released, and operated. Late-stage reviews don’t cut it. By having security checks run alongside development workflows, risks can be addressed as systems change. This approach is especially important for AI since behavior can shift even when application code stays the same.
In a DevSecOps pipeline for AI, data handling is treated as a first-class concern. Training and inference data are governed with strict access controls and encryption to reduce exposure as models evolve. Model artifacts are versioned and validated to prevent unauthorized changes, while deployment pipelines apply policy checks before agents are promoted into higher, more sensitive environments.
Ongoing oversight completes the picture. Monitoring focuses on how AI agents behave in production, including unexpected outputs, abnormal access patterns, or policy violations. By integrating these safeguards into everyday workflows, DevSecOps provides a practical way to manage AI risk while still leveraging the benefits of AI to the fullest.
Salesforce applies DevSecOps principles directly within the platform — you can use AI systems with security and governance built into everyday development work. AI security and protections are woven into how data is handled and how changes move through environments.
Within Salesforce DevSecOps, you can support AI development by bringing consistency to how models and automation are tested, released, and then observed. Security policies travel with the work itself, so you’ll see fewer risky gaps between experimentation and production use.
Building AI agents you can trust requires application development platforms that treat security as a core design principle. Salesforce brings governance, data protection, and deployment together so that you can test and deploy AI-driven applications with consistent control from day one. As AI systems expand in scope, that consistency means that you can manage change while maintaining total visibility into how agents access data and take action.
Explore how the Agentforce 360 Platform supports secure AI development with built-in DevSecOps capabilities.
Try Agentforce 360 Platform Services for 30 days. No credit card, no installations.
Tell us a bit more so the right person can reach out faster.
Get the latest research, industry insights, and product news delivered straight to your inbox.
AI is a big part of modern DevSecOps, where you can look at all the security signals as projects are developed and deployed. This is especially important because environments are getting more complicated and releases are happening much faster now.
Inside DevSecOps, AI can spot unusual behavior in the build pipelines, flag configuration changes that might cause trouble, and connect the dots across different logs — tasks that would consume a lot of work hours when done by hand.
When it comes to the AI agents themselves, DevSecOps rules are used to make sure the models and data they use are properly governed, along with how that data and those models are actually put to use.
Absolutely. DevOps practices are already common in AI development for managing how models and related assets are versioned, tested, and deployed. AI teams depend on these repeatable pipelines to move models across different environments and keep track of changes as their systems evolve. DevSecOps takes this foundation and integrates security and compliance checks directly into those same workflows. This integration is essential, especially when AI systems are interacting with live production data and core business processes.
DevOps is not being replaced by AI. AI is becoming part of how DevOps operates. AI-driven workflows can improve monitoring, testing, and risk detection, but DevOps is still built on a human element. Experts still need to collaborate and maintain operational consistency, and human judgment still plays a central role in defining policies, reviewing outcomes, and responding to incidents. AI may support those efforts, but it can’t take them over.
The three pillars of DevSecOps are development, security, and operations. Development focuses on building and releasing changes, security defines how risk is managed throughout the lifecycle, and operations is responsible for reliability in production. DevSecOps works when all three are applied together in the same workflows, so security and operational requirements are addressed as changes are made rather than after deployment.