Blog

Analysis on enterprise AI governance, inline policy enforcement, agentic AI security, and regulatory compliance.

Notion AI Security: What Page Permissions, the Audit Log, and Workspace Controls Cover

Notion AI answers from the pages a user can already open, so its exposure is the existing permission graph rather than a new one. Enterprise workspaces add an audit log with 365-day retention across eight event categories, CSV export, and real-time SIEM streaming by webhook. Notion states it does not use customer data to train models. What none of those controls do is evaluate a specific prompt against a policy before it reaches a model.

Platform & Architectureai-securityaudit-logsidentity-and-authorizationshadow-aicompliance
Read post →

n8n Security: What Project RBAC, External Secret Stores, and Log Streaming Cover

n8n Enterprise groups workflows into projects, assigns access by project role, pulls credentials from external secret stores, and streams events to syslog, a webhook, or Sentry. Those controls decide who may edit a workflow and where its secrets come from. When an AI Agent node calls a model, the model receives the workflow credential, so the human who triggered the run leaves no identity on the request.

Platform & Architectureai-securityidentity-and-authorizationagentic-aiaudit-logsarchitecture
Read post →

Mistral Security: What Workspaces, SCIM, and Admin-Role API Keys Cover

Mistral organizes access around an organization containing workspaces, with roles, groups, SCIM provisioning, and SAML single sign-on managed from the Admin Panel. Workspaces carry their own usage limits and rate tiers, and Admin API calls require a key held by an Admin-role user. All of that governs who joins the account and which workspace they land in. The inference request itself authenticates with a bearer key that names no human.

Platform & Architectureai-securityidentity-and-authorizationllm-securityzero-trustarchitecture
Read post →

Mistral Audit Logs Record Who Changed the Account, Not Who Called the Model

Mistral ships audit logs on Enterprise plans, enabled by default for every workspace with no setup required. Each entry carries a timestamp, an actor that can be a user or an API credential, an event, a target resource, and metadata. The documented event list covers authentication, credential management, workspace changes, user management, and settings. Inference requests are absent from that list, and log export is not supported.

Platform & Architectureai-securityaudit-logscompliancellm-securityidentity-and-authorization
Read post →

Microsoft 365 Copilot Security: What Entra ID, Sensitivity Labels, and XPIA Classifiers Cover

Microsoft 365 Copilot inherits the tenant permission model rather than introducing a new one. The Semantic Index honors the user identity-based access boundary, Purview Information Protection encryption and usage rights are respected, and XPIA classifiers screen for cross-prompt injection before model execution. Each of those controls answers a question about the data. None of them evaluates whether a permitted user should be making this particular request.

Platform & Architectureai-securitymicrosoft-365identity-and-authorizationprompt-injectionzero-trust
Read post →

Microsoft 365 Copilot Audit Logs: What a CopilotInteraction Record Actually Contains

Microsoft Purview writes a CopilotInteraction record every time a user prompts Microsoft 365 Copilot, with no configuration required beyond having auditing turned on. The record names the user, the host app, the model provider, every resource Copilot touched, and the sensitivity label on each one. The prompt and response text sit somewhere else entirely, and third-party AI apps land in a different record type on pay-as-you-go billing.

Platform & Architectureai-securityaudit-logsmicrosoft-365complianceshadow-ai
Read post →

LlamaIndex Audit Logs: What the Instrumentation Module Records and What LlamaCloud Adds

LlamaIndex ships two different record-keeping systems and neither one is an audit log in the sense a compliance team means. The open-source instrumentation module emits Spans and Events through a dispatcher for developer observability. LlamaCloud adds organization-level audit logs and SSO on Enterprise plans, covering administrative actions. Between those two sits the retrieval request itself, which carries no authenticated identity in either record.

Platform & Architectureai-securityaudit-logsragllm-securityobservability
Read post →

Vertex AI Gateway Patterns: Governing Gemini Traffic on Google Cloud

Teams front Vertex AI with a gateway for three jobs: token quotas and cost attribution, regional routing for data residency, and content screening on prompts through Model Armor. This article walks the patterns engineers run on Apigee in front of Gemini, shows where Model Armor sits, and marks the line between screening scoped to Google Cloud and the identity-bound payload governance a mixed model estate needs.

Platform & Architectureai-securityarchitecturezero-trustllm-securityinline-enforcementidentity-and-authorization
Read post →

Llama Security: What Llama Guard, IAM Scoping, and the License Actually Cover

Securing a Llama deployment layers three separate mechanisms: Llama Guard and Prompt Guard filtering content, cloud-native IAM or RBAC scoping which identity can call the model, and Meta'"'"'s Acceptable Use Policy setting legal boundaries on use. None of the three evaluates a specific request against an enterprise'"'"'s own policy at the moment it is made. Two 2026 CVEs in the serving layer underneath Llama show what that gap costs.

Platform & Architectureai-securityllm-securityidentity-and-authorizationzero-trustarchitecture
Read post →

Llama Audit Logs Depend Entirely on Which Hosting Layer You Picked

Llama is an open-weight model with no logging of its own, so audit logging for a Llama deployment depends entirely on the hosting layer. AWS Bedrock offers detailed model invocation logging that ships disabled by default. Azure AI Foundry routes similar detail through diagnostic settings that must be explicitly configured. Self-hosted deployments on vLLM or TGI have no audit logging at all until a team builds it. This article separates the three paths.

Platform & Architectureai-securityllm-securityauditcloud-securityarchitecture
Read post →

LangChain and LangSmith Audit Logs: Why the User ID Field Is Not an Identity Check

LangSmith traces every LangChain LLM call in detail: messages, tool calls, token counts, and custom metadata. The user_id and session_id fields that group those traces into threads are optional strings a developer chooses to attach, not values LangSmith verifies against an identity provider. This article separates trace completeness from identity verification and lists what a security review should check before relying on either.

Platform & Architecturellm-securityai-securityauditidentity-and-authorizationinline-enforcement
Read post →