Salt Security has launched Salt Code, a product the company says applies policy-driven security controls inside AI coding assistants and across AI-generated code workflows. The company says the tool supports assistants including Claude, Cursor, GitHub Copilot, Windsurf, Codex and Gemini CLI, and is part of its Agent...
Salt Security launched Salt Code on June 1, 2026, describing it as a component of its Agentic Security Platform for applying security policies inside AI coding assistants.
In its June 1 press release, Salt Security said Salt Code is designed to enforce security policy across AI-generated code created with tools including Claude, Cursor, GitHub Copilot, Windsurf, Codex and Gemini CLI. The company said the product is available now.
PR Newswire’s version of the release states that Salt Code applies “policy-driven security” from the developer prompt through pipeline and runtime. Salt Security’s product page similarly describes the product as enforcing an organization’s security policies inside AI coding assistants, rather than waiting until later review stages.
The stated aim is to give security teams a way to govern how AI coding assistants are used during software development. Salt Security frames the product around a single policy model that can apply across code, Model Context Protocol integrations, APIs and agents, according to the company’s product page.
AI coding assistants are increasingly used to generate, modify and review code, which can change how security controls are applied in development environments. Salt Security’s release positions Salt Code as a response to that shift: instead of treating AI-generated code as just another artifact to scan after creation, the company says its product applies policies within the assistant workflow itself.
That distinction is important because AI coding assistants can influence code before it reaches conventional testing, review or deployment systems. According to PR Newswire’s publication of the Salt Security announcement, the product is meant to apply controls from prompt through runtime. Salt Security’s own materials also emphasize governance across both the code and the connected systems that AI agents may use.
Salt Security names Claude, Cursor, GitHub Copilot, Windsurf, Codex and Gemini CLI among the AI coding assistants Salt Code is intended to support. The company also says the product provides one policy model across code, MCP integrations, APIs and agents.
The company’s product page describes this as a way for organizations to apply consistent controls across AI-assisted development and related integrations. The sources do not provide independent performance benchmarks, customer deployment details or technical evaluation results, so claims about effectiveness should be treated as Salt Security’s product positioning unless further third-party evidence becomes available.
PR Newswire’s release says Salt Code is available today, while Salt Security’s press release identifies the launch date as June 1, 2026. Salt Security is presenting Salt Code as part of its broader Agentic Security Platform, rather than as a standalone point tool.
For security and development teams evaluating AI coding assistants, the announcement reflects a growing vendor focus on policy enforcement earlier in the software creation process. Based on Salt Security’s published materials, Salt Code is aimed at organizations that want centralized governance for AI-generated code and for the agentic systems connected to that code.
Salt Security launched Salt Code on June 1, 2026, describing it as a component of its Agentic Security Platform for applying security policies inside AI coding assistants.
PR Newswire’s version of the release states that Salt Code applies “policy driven security” from the developer prompt through pipeline and runtime.
Salt Security’s product page similarly describes the product as enforcing an organization’s security policies inside AI coding assistants, rather than waiting until later review stages.
Continue reading
