Topic starter
01/08/2026 8:59 pm
TL;DR: AI security tools reached a $35.40 billion market in 2026, but the source article argues the category still splits between systems that secure AI itself and tools that use AI to find code flaws, with traditional SAST missing broken access control and privilege chains that affect 100% of tested apps, according to Gecko Security. The practical issue is not more scanning, but better reasoning about application intent, trust boundaries, and false positives.
Editorial analysis by NHI Mgmt Group, based on content published by Gecko Security: “14 Best AI Security Tools for April 2026: Features, Pricing, and Comparisons”.
Key questions
Q: What breaks when AI security tools cannot reason about broken access control?
A: They miss the defects that depend on application intent, object scope, and service-to-service authorisation rather than known code patterns.
Q: Why do microservices make privilege escalation harder for scanners to detect?
A: Because the authorisation decision is often distributed across several services instead of living in one obvious code location.
Q: How do security teams know if an AI scanner is missing real authorisation flaws?
A: Look for repeated misses on representative tests such as IDOR, object access bypasses, and service-to-service escalation paths.
Practitioner guidance
- Prioritise semantic reasoning for authorisation-heavy code Evaluate scanners against workflows where access decisions depend on business context, not just known bad patterns.
- Map service-to-service trust boundaries Document where each internal call makes an access decision, then check whether that decision is enforced consistently at the service, API, and object level.
- Test for false negatives on broken access control Build validation cases for IDOR, privilege escalation, and missing object checks, then compare scanner output against the expected control path.
Bottom line: AI security tooling still splits between protecting AI systems and finding application flaws, and those are not interchangeable problems.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
01/08/2026 9:06 pm
Broken access control is the defining blind spot in many AI security tools. The market may be crowded, but crowding does not equal coverage. Tools that excel at pattern detection often underperform when the risk depends on application intent, object ownership, or service-to-service authorisation. For practitioners, that means the decision is no longer about scan volume but about whether the platform can reason across trust boundaries.
A few things that frame the scale:
- Only 23% of IT leaders were very confident in their organisation's ability to manage security and governance for GenAI deployments, according to a 2025 Gartner survey of 360 IT leaders.
A question worth separating out:
Q: Should teams use the same tooling for AI system security and code vulnerability detection?
A: No. AI-system security tools focus on prompt injection, model misuse, and pipeline abuse, while code security tools need to reason about authorisation, business logic, and trust boundaries in applications. Conflating the two leads to gaps because the underlying control questions are different, even when the vendor marketing makes them sound adjacent.
👉 Read our full editorial: AI security tools still miss access flaws that break real apps