Notifications
Clear all
Topic starter
02/08/2026 11:34 am
TL;DR: Most organisations have AI acceptable-use policies, but very few can enforce them because LLM inputs, personal accounts, and agentic workflows evade traditional logging and access models, according to Cyberhaven. The governance gap is now an identity and data control problem, not just a visibility problem.
NHIMG editorial — based on content published by Cyberhaven: LLM Access Controls and Audit Logging for Security Teams, a Practitioner's Guide
By the numbers:
- Cyberhaven Labs data shows enterprise AI adoption grew 509% year-over-year between February 2025 and February 2026.
- Roughly 44% of AI use happens through personal accounts where visibility is more limited.
Questions worth separating out
Q: How should security teams audit LLM usage without missing sensitive input data?
A: They should log at the interaction layer, not only the application layer.
Q: Why do personal AI accounts create so much risk in enterprise environments?
A: Personal accounts bypass enterprise identity controls, so security teams lose visibility into who authorised access, what scopes were granted, and whether the session can be revoked.
Q: What breaks when agentic AI inherits a user's full access profile?
A: The blast radius expands beyond what the organisation intended.
Practitioner guidance
- Implement interaction-layer logging Capture prompt inputs, file uploads, session identifiers, tool identity, account type, and data lineage so investigators can reconstruct what entered the AI workflow.
- Enforce role-scoped AI access Limit coding assistants and high-risk AI tools to documented business roles, and separate corporate account access from personal account usage on managed devices.
- Treat agent permissions as delegated identities Review the data scope granted to agentic AI workflows before deployment and avoid inheriting the full access profile of the human who configured them.
What's in the full article
Cyberhaven's full post covers the operational detail this post intentionally leaves for the source:
- Practical logging fields for AI interactions, including prompt content, session continuity, and data lineage, that security teams can use in an investigation workflow
- Endpoint and browser detection patterns for personal AI account usage on corporate devices, which are central to enforceable policy coverage
- A minimum viable audit trail structure for sensitive-data interactions, useful when moving from visibility to evidence retention
- Role-scoping guidance for coding assistants and third-party LLM APIs, including how to separate corporate and personal account context
👉 Read Cyberhaven's practitioner guide to LLM access controls and audit logging →
LLM audit logging and access controls: are your controls keeping up?
Explore further
02/08/2026 12:48 pm
LLM access control is now a data governance problem disguised as an identity problem. The article shows that policy language alone does not control what employees paste into AI tools or what session context accumulates over time. That means the control boundary has shifted from application access to interaction governance. Practitioners should treat prompt input, account context, and data lineage as first-class control points.
A question worth separating out:
Q: Which frameworks help govern LLM access controls and audit logging?
A: NIST CSF and NIST SP 800-53 are the best broad fit for access control, monitoring, and evidence handling, while OWASP Agentic AI Top 10 helps when AI tools can act autonomously. For organisations using agentic workflows, NHI governance should be added to IAM and PAM controls so delegated permissions are reviewable and constrained.
👉 Read our full editorial: LLM access controls and audit logging need endpoint visibility
