Topic starter
24/06/2026 11:47 pm
TL;DR: Model risk now includes access control, misuse, and auditability across the AI lifecycle, according to WitnessAI. AI endpoints need explicit ownership and separate lifecycle controls so influence, logging, and revocation do not collapse into one weak gate.
Editorial analysis by NHI Mgmt Group, based on content published by WitnessAI: “AI Model Security: Safeguarding the Core of Intelligent Systems”.
Key questions
Q: Why is prompt injection a governance problem as well as a technical one?
A: Prompt injection is a governance problem because the harm depends on who gave the agent authority, what tools it can use, and how much data it can reach.
Q: What are the signs that model access is too broad?
A: Common signs include many unrelated applications calling the same model, weak logging, unclear ownership, and no documented reason for access.
Q: How should security teams govern AI models that can call tools and access data?
A: Security teams should govern AI models as non-human identities with named owners, limited scope, short-lived credentials, and continuous authorization.
Practitioner guidance
- Define model access as a privileged identity surface Classify model endpoints, orchestration hooks, and inference APIs as governed assets with named owners, explicit entitlements, and revocation procedures.
- Separate controls for prompts, data, and artefacts Apply different validation and approval checks to runtime prompts, training datasets, and model files so one trust decision does not cover all three.
- Inventory model exposure across internal and external callers Map every application, workflow, and automation that can reach a model, then remove access paths that are not tied to a documented business need.
Bottom line: AI model security now spans access, influence, and auditability, not just output correctness or adversarial robustness.
Glossary terms: AI Model Security, Prompt Injection (Agentic), Data Poisoning, Model Extraction
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
This topic was modified 1 day ago by NHI Mgmt Group
25/06/2026 8:42 am
AI model security is now an identity governance problem, not only a model integrity problem. Access, audit, and privilege boundaries increasingly determine whether a model can be trusted in production. If teams only test model behaviour and ignore who can reach it, they leave the governance layer undefended. Practitioners should treat model access as a governed identity surface.
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: What should organisations do when AI access and AI safety are owned by different teams?
A: They should define a shared governance model with separate control objectives. The identity team should own provisioning, authorization, auditability and revocation, while the AI assurance team should own adversarial testing, runtime monitoring and failure-mode analysis. Common reporting helps, but the controls should not collapse into one programme because they answer different risk questions.
👉 Read our full editorial: AI model security now requires identity controls and auditability
This post was modified 1 day ago by NHI Mgmt Group