Notifications
Clear all
Topic starter
19/08/2026 3:33 pm
TL;DR: LLM discovery, MCP exposure, and testing gaps are turning AI-enabled application security into a broader governance problem, according to Pynt. Published research shows 98% of organisations are adopting LLMs into apps while only 24% have onboarded security tools, and the security model is shifting from static application testing to continuous discovery, access control, and runtime validation.
NHIMG editorial — based on content published by Pynt: The Next Big Thing in AppSec: LLM Discovery and Security Testing
By the numbers:
- 98% are adopting LLMs into apps, while only 24% have onboarded security tools.
- Only 24% have onboarded security tools for LLM-enabled applications.
Questions worth separating out
Q: What breaks when AI agents are discovered too late or not at all?
A: When agents are not discovered early, teams cannot assign ownership, set scope, or prove what systems the agent can reach.
Q: Why do LLM applications create governance problems for IAM and security teams?
A: LLM applications create governance problems because they can turn untrusted input into live system behaviour.
Q: How can teams tell whether AI security workflows are actually reliable?
A: Check whether the workflow produces consistent results from the same underlying evidence and whether it preserves the relationship between findings, identities, and assets.
Practitioner guidance
- Implement continuous LLM and MCP discovery Create a living inventory of every AI-enabled application, agent, retrieval source, and tool endpoint.
- Scope MCP tool permissions as privileged access Review each tool-call path as if it were a privileged workload.
- Add adversarial runtime tests for AI workflows Test prompt injection, retrieval poisoning, and tool misuse in the same way you would test abuse paths in a high-risk application.
What's in the full article
Pynt's full article covers the operational detail this post intentionally leaves for the source:
- Specific findings from its LLM security research and the testing patterns it used to surface risk
- More detail on Pynt's product-led approach to discovery and testing across AI-enabled applications
- Examples of the application security use cases and control gaps the article highlights for practitioners
👉 Read Pynt's analysis of LLM discovery and MCP security risks →
LLM security and MCP risk: what appsec teams need to do now?
Explore further
19/08/2026 4:15 pm
LLM discovery is now an identity governance problem, not just an AppSec hygiene task. When AI features can retrieve data and call tools, the real question is which identities, secrets, and permissions sit behind the model. Discovery therefore becomes a control boundary for IAM and PAM teams, because unmanaged AI workflows behave like shadow workloads with delegated authority. Practitioners should treat hidden AI integrations as part of the governed identity estate.
A question worth separating out:
Q: Should organisations treat MCP-connected AI systems like privileged workloads?
A: Yes. MCP-connected systems can invoke tools, reach data, and trigger actions, which means they function more like privileged workloads than passive applications. They need least privilege, logging, access review, and clear ownership. If a model can act on behalf of a user or service, its permissions deserve the same scrutiny as any elevated account.
👉 Read our full editorial: LLM discovery and MCP security are becoming core AppSec issues
