The control boundary has moved
Prompt injection, manipulated instructions, excessive agency and unauthorised tool use can affect downstream systems. Monitoring after the event does not prevent the action.
The control needs to sit in the live path between the model and the system it can affect.
Protection and governance belong together
Security checks protect the input and execution path. Governance then determines which requirement applies, whether the output may proceed and when a person must review it.
Separating those questions creates gaps. The same path should protect, govern, escalate and record the decision.
A controlled action leaves a record
For every consequential output, the organisation should be able to identify the model context, applied control, verdict, reviewer and resulting action.
That record turns a security claim into something that can be inspected after the event.
OWASP LLM Top 10 · OWASP Agentic Security Initiative · NIST AI RMF