Topic starter
11/06/2026 12:02 am
TL;DR: LLM applications introduce prompt injection, model drifting, and resource abuse risks that traditional deterministic AppSec was not built to handle, according to Lasso Security. The governance gap is not just data leakage but application manipulation, where system prompts become a security boundary that must be treated as part of the control plane.
Editorial analysis by NHI Mgmt Group, based on content published by Lasso Security: “New Challenges for AppSec: Securing LLM-based Applications and System Prompts”.
Key questions
Q: What breaks when agent prompts are treated like ordinary text?
A: When prompts are treated as ordinary text, the system has no reliable way to distinguish authorised directives from injected, replayed, or modified instructions.
Q: Why do LLM applications create new data leakage risks for identity teams?
A: LLM applications can expose sensitive data when users paste secrets, when agents retrieve privileged context, or when responses echo internal material back to users.
Q: What are the signs that guardrails are failing in an LLM application?
A: Guardrails are likely failing when the model returns unsafe, off topic, or unstructured responses that bypass policy checks.
Practitioner guidance
- Define prompts as governed security artefacts Put system prompts under version control, peer review, and formal approval so changes are treated as security-relevant configuration changes.
- Test for instruction override paths Create adversarial test cases that try to override system instructions, extract hidden context, and force unsafe behavioural changes.
- Set runtime limits on model execution Constrain token budgets, recursion-like loops, and repeated tool-triggered actions to reduce denial-of-service and wallet abuse risk.
Bottom line: LLM applications now create manipulation risk, not just leakage risk, because prompt content can alter model behaviour at runtime.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
This topic was modified 2 days ago by NHI Mgmt Group
12/06/2026 6:33 am
LLM application security is no longer a leakage-only problem. The industry’s early focus on accidental data exposure was too narrow for the runtime reality of generative AI. Once the model can be steered through prompt content, the security question becomes whether the application can be manipulated at all. Practitioners should now treat manipulation risk as the primary AppSec problem for LLM-based systems.
A few things that frame the scale:
- AI-related credential leaks surged 81.5% year-over-year in 2025, with the surrounding AI infrastructure leaking 5x faster than core LLM providers, according to the State of Secrets Sprawl 2026.
A question worth separating out:
Q: How should security teams govern AI prompts that include sensitive data?
A: Treat the browser as a control point, not just an interface. Inspect the sensitivity of the data, the identity of the user, and the context of the session before the prompt leaves enterprise control. That lets teams allow useful AI use while blocking risky disclosure paths without relying only on after-the-fact DLP.
👉 Read our full editorial: LLM app security is shifting from leakage to manipulation risk
This post was modified 2 days ago by NHI Mgmt Group