← All posts

Platform & Architecture

338 posts on platform & architecture.

Databricks Mosaic AI Audit Logs at the Request Boundary

Databricks Mosaic AI audit logs need to do more than retain prompts and responses. A reviewable record connects an HTTP model request to the originating identity, route, evaluated policy, response outcome, and timestamp. This article separates Databricks-native usage records from independent request-boundary evidence for mixed model deployments.

ai-securityllm-securityauditforensic-auditinline-enforcementpolicy-enforcement
Read post →

Cursor Security at the AI Request Boundary

Cursor security depends on knowing which authenticated actor sent each AI request, which policy applied, and which evidence survives a later review. This article maps provider records, request-layer controls, and the HTTP boundary that regulated enterprise teams can verify.

ai-securityllm-securityauditinline-enforcementpolicy-enforcement
Read post →

CrewAI Audit Logs and Per-Request Evidence

CrewAI teams need evidence that connects each AI request to an authenticated actor, policy decision, and timestamp. This article separates provider administration records from independent request-layer evidence and maps the HTTP controls that regulated enterprises can verify during a security review.

ai-securityllm-securityauditinline-enforcementpolicy-enforcement
Read post →

Cohere Security for Enterprise AI Traffic

Cohere teams need evidence that connects each AI request to an authenticated actor, policy decision, and timestamp. This article separates provider administration records from independent request-layer evidence and maps the HTTP controls that regulated enterprises can verify during a security review.

ai-securityllm-securityauditinline-enforcementpolicy-enforcement
Read post →

Cohere Audit Logs for Enterprise AI Requests

Cohere teams need evidence that connects each AI request to an authenticated actor, policy decision, and timestamp. This article separates provider administration records from independent request-layer evidence and maps the HTTP controls that regulated enterprises can verify during a security review.

ai-securityllm-securityauditinline-enforcementpolicy-enforcement
Read post →

Canva AI Security and Prompt-Level Data Controls

Canva AI teams need evidence that connects each AI request to an authenticated actor, policy decision, and timestamp. This article separates provider administration records from independent request-layer evidence and maps the HTTP controls that regulated enterprises can verify during a security review.

ai-securityllm-securityauditinline-enforcementpolicy-enforcement
Read post →

Amazon Q Audit Logs at the AI Request Boundary

Amazon Q teams need evidence that connects each AI request to an authenticated actor, policy decision, and timestamp. This article separates provider administration records from independent request-layer evidence and maps the HTTP controls that regulated enterprises can verify during a security review.

ai-securityllm-securityauditinline-enforcementpolicy-enforcement
Read post →

Box AI Security: What the New Agent Controls Cover, and What They Do Not

Box announced prompt injection detection and MCP guardrails for AI agents on July 22, 2026, plus audit trails covering more than 300 admin actions. The controls secure what happens inside Box and what external agents may do to Box content. They do not evaluate outbound calls an application makes from Box data to an external LLM API.

ai-securityauditforensic-auditllm-securityagentic-aiarchitecture
Read post →

Azure AI Foundry Audit Logs: What Tracing and Monitoring Actually Record

Azure AI Foundry traces LLM calls, tool invocations, and agent decisions through OpenTelemetry integrated with Azure Monitor Application Insights. The tracing captures the Entra ID identity or managed identity making the call, not necessarily the end user a multi-tenant application serves. This piece maps what Foundry observability records and where the identity gap sits.

ai-securityauditforensic-auditllm-securitycompliancearchitecture
Read post →

Atlassian Intelligence Security: Evidence for AI Actions in SaaS

Atlassian Intelligence operates inside Atlassian cloud products and acts on the content and permissions available in those products. A sound security review maps the identity, data, feature, audit, and connector boundaries for the selected use case. This article distinguishes SaaS application controls from direct LLM API request policy.

ai-securityagentic-aiauditidentity-and-authorizationpolicy-enforcementzero-trust
Read post →

Claude Connectors Audit Logs: Evidence for Remote MCP Tool Calls

Claude connectors let Claude call approved remote MCP servers. Audit evidence for that flow must distinguish the Claude request, the connector authorization, the remote tool action, and the application record. This article shows what each system can prove and where an independent request-level policy record fits.

ai-securityagentic-aiauditforensic-auditidentity-and-authorizationpolicy-enforcement
Read post →

AI Agent Observability: Traces, Decisions, and Debuggable Behavior

AI agent observability needs a trace for each model call, tool handoff, retrieval result, and policy decision. This guide defines the signals, OpenTelemetry fields, correlation IDs, and retention split that make autonomous behavior reviewable.

ai-agent-observabilityai-agent-securityopentelemetryai-securityagentic-aitraces
Read post →