Security

EU AI Act Article 12 record-keeping for high-risk AI, plus ISO 42001 logging, and why that design still helps non-high-risk agents.

Production AuthZ needs four pillars: enforce at every sensitive action, fine grain, realtime revoke/sync, and auditable decisions. Control plane → OPAL → PDP → PEP → logs is the architecture that makes them work together.

AI agent audit logs need about twelve fields: identity, delegation, tool, resource, policy, decision, HITL, and outcome.

An AI agent audit trail binds identity, delegation, tool, resource, policy, allow/deny, HITL, and outcome. Tool traces are not enough.

SOC 2 CC6 and ISO 27001 access control checklist for AI agents: what controls assumed, how agents break them, evidence to produce.

Regulators’ “prove it” maps to PEP + PDP + decision logs: enforce in the app, decide in a local PDP synced by OPAL, and keep explainable allow/deny evidence.

DORA and NIST do not prescribe a vendor. They expect scoped least-privilege access and attributable logs, including for NHIs and agents. Application FGA with decision logs is how product teams produce that evidence.

AI agent permissions usually inherit the user OAuth token. That fails least privilege. Give the agent its own role at each tool call.

Your authorization model shapes least-privilege evidence in access reviews. Role assignments, attribute conditions, and relationship tuples each prove different things.

Hybrid authorization by default: RBAC for org roles, ABAC for context, ReBAC for sharing graphs—one check API across models. How to pick a stack before role explosion, and why least privilege needs explainable entitlements.

Authentication (AuthN) is who you are; authorization (AuthZ) is what you're allowed to do. Learn 401 vs 403, why IdPs don't replace app AuthZ, and how to externalize permissions.

SOC 2-style access reviews need more than IdP login events. Explainable allow and deny decision logs — decision provenance from identity to policy to resource — are the authorization evidence that makes application-level access controls concrete.

Every authorization decision should be explainable. Authorization observability is not more logs — it is decision provenance. Here is how to build an audit trail that answers why access was allowed or denied.

Fine-grained authorization belongs in a dedicated control plane—not scattered if-statements. Learn when to externalize authorization and stop rebuilding DIY RBAC in application code.

MCP servers are now operational control surfaces for cloud and API platforms. This article explains the trust model, control stack, and audit architecture enterprises need before AI agents can safely execute infrastructure actions.

A practical review guide for security, privacy, and procurement teams evaluating whether an MCP gateway can meet SOC 2, HIPAA, and privacy requirements — with concrete examples from Permit MCP Gateway.