About the AI Coding Agent Security category
What belongs in this category
The AI Coding Agent Security category is about securing AI: here the agents themselves are the risk. Coding agents can read a whole repository, run shell commands, install packages, call MCP servers (connectors that give an agent tools and data) and push code, often with the developer's own credentials. Hidden instructions in a README, issue or tool description can steer them. Typical entries find the coding agents, editor extensions, MCP servers and agent instruction files in use, and flag risky settings such as commands approved automatically. They check each command, file access, package install and network call against policy before it runs, alert when a control is switched off, and send agent activity to the SIEM.
Fixing flaws in agent-written code fits AI Code Security and Remediation, and deciding which AI tools developers may use fits AI Usage Control. A product that also secures agents acting in business systems can enter Agentic AI Security, and the credentials an agent runs with fit AI Agent Identity Security. A product that secures the MCP connections coding agents use can also enter MCP Security, and any entry can be repeated in Security for AI. Endpoint products with coding agent controls can enter here for that capability.
This category matches a category in the AI Security Market Map by Cybersecurity Insiders, which describes what buyers need from these products and how to test them.
Related categories to enter
Each category is judged separately, so you can enter a product in every category that matches what it does, with a separate nomination for each. Tailor each nomination to that category's focus. Entering several related categories gives the product more than one chance to be recognized.
How entries are judged
An independent jury of security practitioners, analysts and CISOs scores each nomination on leadership, innovation and impact. Each nomination competes in its category against organizations of similar size and region, so a mid-sized firm is not ranked against a global enterprise. Your entry package, any sponsorship and public votes do not affect the jury's scores.
Strong entries in this category show:
- Leadership — the coding agents the product covers: agents and editors supported, developer machines and build pipelines protected, and engineering teams that use it.
- Innovation — a coding agent problem solved in a new way, such as stopping a risky command before it runs, controls developers cannot quietly switch off, or spotting instructions planted in repositories and tool descriptions.
- Impact — results for customers: more coding agents inventoried, risky settings fixed, unsafe actions blocked before they ran, time to notice a disabled control cut. Give figures from customers or controlled tests.
The jury awards Gold, Silver or Bronze, or a Finalist badge, and results are published on this site and announced to the 600,000+ member Cybersecurity Insiders community. Every approved nomination also enters the separate Community Choice award, decided by public votes.
How to enter
A vendor can enter its own product or service, and a PR agency can enter it on a client's behalf. The nomination form has a confidential field for detail that is shared with the judges and not published, such as customer names, deployment figures or roadmap. Deadlines, pricing and entry steps are on the How it Works page.