A part of the SD Occasions 100 2026 collection. See the full SD Occasions 100 2026 listing for each class and honoree.
Software safety has spent years maturing round a comparatively secure assumption: a human wrote the code, a human might be educated to write down it extra securely, and instruments exist to catch what people miss. That assumption is below actual strain in 2026. A rising share of code now originates from AI assistants and autonomous brokers, open-source dependencies stay a major assault vector, and AI methods themselves have launched solely new classes of danger that didn’t exist a number of years in the past. The Safety, Belief & Governance class on this 12 months’s SD Occasions 100 displays an business working to catch as much as all three realities without delay.
For improvement leaders, this class is now not one thing handy off solely to a safety workforce and test in on quarterly. Safety, software danger, and AI governance have turn out to be shut sufficient to core engineering issues that the best organizations deal with them as a shared duty between safety and engineering management, not a handoff between two separate worlds.
Why This Class Issues Now
AI-generated code wants totally different safety scrutiny than human-written code. AI coding assistants can introduce delicate vulnerabilities, insecure default patterns realized from coaching information, or outright incorrect logic that appears believable. Safety tooling and practices constructed across the assumption of human authorship want actual adjustment, together with scanning approaches and evaluation processes particularly tuned to the failure patterns AI-generated code tends to supply.
Software program provide chain danger has solely intensified. Open-source dependency danger, software program invoice of supplies necessities, and the broader software program provide chain safety dialog that’s been constructing for years has not slowed down, and if something has gained urgency as AI instruments pull in dependencies and packages sooner than human reviewers can all the time vet them.
AI governance and mannequin danger administration are actually distinct disciplines. Deploying an AI mannequin or function into manufacturing introduces dangers that conventional software safety tooling wasn’t constructed to catch: mannequin bias, hallucination, immediate injection, information leakage by mannequin outputs, and explainability necessities that matter for each regulatory compliance and primary belief. This has created actual demand for tooling purpose-built round AI mannequin observability and governance, distinct from conventional appsec.
Entry governance has to increase to each people and AI brokers. As AI brokers are given the power to take motion, generally autonomously, the query of who or what is permitted to do what has expanded properly past conventional human role-based entry management, requiring extra granular, dynamic authorization fashions that may scope an agent’s permissions tightly and regulate them primarily based on context.
The Completely different Segments Inside This Class
Cloud-native software safety. Aqua Safety anchors this phase, securing containerized and cloud-native purposes throughout the construct, deploy, and runtime lifecycle, an space that’s solely grown extra advanced as extra workloads, together with AI inference workloads, run in containerized cloud environments.
Software safety posture administration. ArmorCode represents a phase targeted on aggregating and correlating findings throughout the numerous particular person safety instruments a corporation runs, giving safety and engineering leaders a unified, prioritized view of danger relatively than a dozen disconnected instrument dashboards.
AI-native safety and governance. AISLE displays the latest wave on this class: safety tooling constructed particularly for the dangers launched by AI methods themselves, an space nonetheless actively defining its personal greatest practices because the threats it addresses are nonetheless being found in actual time.
Static and dynamic software safety testing. Checkmarx and Veracode anchor the standard core of software safety testing, scanning code for vulnerabilities earlier than and after deployment. Each have invested considerably in adapting their scanning approaches particularly to catch the patterns of vulnerability that AI-generated code tends to introduce.
Runtime software safety. Distinction Safety occupies a definite place, specializing in instrumenting purposes to detect and block assaults in actual time as they run, relatively than solely scanning code earlier than deployment, which gives a complementary layer of protection in opposition to vulnerabilities that static evaluation alone can miss.
Developer-first vulnerability administration. Snyk constructed its repute particularly on integrating safety scanning instantly into developer workflows relatively than treating safety as a separate gate, a philosophy that’s turn out to be the default expectation throughout this class broadly.
Open-source and software program composition evaluation. Sonatype and BlackDuck anchor the phase targeted particularly on understanding and securing the open-source parts and dependencies that make up the massive majority of most fashionable codebases, an space of sustained significance as provide chain safety necessities (together with SBOM technology) have turn out to be commonplace follow or regulatory requirement in lots of industries.
Safety info and occasion administration. Splunk represents the broader safety operations and observability layer, correlating safety sign throughout a corporation’s full expertise footprint, with rising emphasis on utilizing AI to assist safety groups triage the identical quantity and complexity challenges that operations groups face.
Safe coding schooling. Safety Journey (2026 Addition) focuses on constructing safe coding talent and consciousness instantly into developer coaching, on the idea that stopping vulnerabilities on the level of creation is extra environment friendly than catching them downstream.
AI mannequin observability and belief. Fiddler AI (2026 Addition) addresses the mannequin governance facet of this class instantly: monitoring AI fashions in manufacturing for bias, drift, and explainability, giving organizations the power to know and belief what their AI methods are literally doing.
Fantastic-grained authorization. Allow.io represents a phase with renewed relevance particularly due to AI brokers: offering the fine-grained, dynamic authorization infrastructure wanted to manage exactly what a human person or an autonomous agent is allowed to do, in environments the place coarse role-based entry management isn’t exact sufficient.
The clearest sample in mature safety practices is shifting safety scanning earlier and making it steady relatively than gate-based, embedding scanning instantly into developer workflows and CI/CD pipelines relatively than treating safety evaluation as a separate, sequential step. This sample predates the present AI wave however has turn out to be extra necessary as code velocity will increase.
A genuinely new sample is the emergence of devoted evaluation and scanning particularly for AI-generated code, recognizing that the vulnerability patterns it tends to introduce differ considerably from typical human-introduced vulnerabilities. Some organizations now flag AI-generated parts of a change explicitly so reviewers and automatic instruments can apply extra scrutiny.
On the AI governance facet, organizations deploying AI options into regulated or delicate contexts are constructing formal mannequin danger administration practices, generally for the primary time, borrowing construction from current danger and compliance capabilities however adapting it for AI-specific issues like hallucination, bias, and explainability.
Lastly, authorization structure is being actively rebuilt in lots of organizations particularly to accommodate AI brokers as actors that want scoped, auditable permissions, relatively than retrofitting current human-oriented entry management methods and hoping they generalize safely.
- Does it have a selected reply for AI-generated code, or is that an afterthought? Ask distributors instantly how their scanning or detection method accounts for the vulnerability patterns widespread in AI-generated code, relatively than assuming conventional scanning generalizes completely.
- How properly does it combine into current developer workflows? Safety instruments that require a separate, disconnected evaluation course of are inclined to get bypassed or deprioritized below deadline strain. Instruments embedded instantly into the event workflow get used constantly.
- Does authorization prolong cleanly to non-human actors? As AI brokers tackle extra autonomous duties, authorization and entry governance tooling must deal with agent identities and scoped permissions as a first-class case, not a workaround.
- What’s the precise signal-to-noise ratio? Safety tooling that generates extreme false positives trains each safety and engineering groups to disregard alerts, which is its personal important danger. Ask for actual buyer information on resolved-versus-dismissed discovering charges.
The 2026 Honorees in Safety, Belief & Governance
- Aqua Safety — Cloud-native software safety throughout construct, deploy, and runtime.
- ArmorCode — Software safety posture administration unifying findings throughout instruments.
- AISLE — AI-native safety and governance for dangers launched by AI methods.
- Checkmarx — Static and dynamic software safety testing platform.
- Distinction Safety — Runtime software safety and assault detection.
- Snyk — Developer-first vulnerability administration built-in into workflows.
- Sonatype — Open-source software program composition evaluation and provide chain safety.
- Splunk — Safety info, occasion administration, and observability platform.
- BlackDuck — Software program composition evaluation and open-source danger administration.
- Veracode — Software safety testing throughout the software program improvement lifecycle.
- Safety Journey (2026 Addition) — Safe coding schooling and developer safety coaching.
- Fiddler AI (2026 Addition) — AI mannequin observability, bias detection, and explainability platform.
- Allow.io — Fantastic-grained, dynamic authorization infrastructure for customers and AI brokers.
Regularly Requested Questions
Does AI-generated code really introduce totally different vulnerabilities than human-written code? Analysis and subject expertise each counsel AI-generated code can introduce particular recurring patterns, resembling insecure defaults realized from coaching information or subtly incorrect logic that appears superficially appropriate, that will not be the identical patterns conventional safe coding coaching and evaluation processes have been tuned to catch. That is an lively and evolving space, and safety tooling distributors are actively adapting scanning approaches accordingly.
What’s the distinction between software program composition evaluation and conventional software safety testing? Software program composition evaluation focuses particularly on the open-source and third-party parts and dependencies inside an software, figuring out recognized vulnerabilities and license dangers in code a corporation didn’t write itself. Conventional static and dynamic software safety testing focuses on vulnerabilities within the customized code a corporation really wrote.
What does “AI governance” imply in sensible phrases for an engineering workforce? It usually means having an outlined course of and tooling for monitoring AI fashions and options in manufacturing for points like bias, inaccurate or dangerous output, information leakage, and explainability, together with clear possession for who’s accountable when one thing goes improper. For regulated industries, it more and more additionally means documentation and audit trails ample to fulfill exterior compliance necessities.
Why does authorization infrastructure want to alter for AI brokers particularly? Conventional role-based entry management was designed round a comparatively small, secure set of human roles. AI brokers might have dynamic, context-dependent permissions that change primarily based on the precise process they’re performing, and organizations want fine-grained authorization methods able to expressing and imposing these extra advanced guidelines in actual time.
How can we keep away from safety tooling fatigue when adopting extra instruments on this class? Prioritize instruments that combine instantly into current developer and safety workflows relatively than requiring separate dashboards and processes, and consolidate findings right into a unified view the place attainable, since safety groups that should test a dozen disconnected instruments every day are inclined to develop the identical fatigue and missed-signal issues as builders going through too many disconnected alerts.
This text is a part of the SD Occasions 100 2026 collection exploring the classes and corporations shaping software program improvement this 12 months. Learn the full SD Occasions 100 2026 listing for the entire roundup.
