
Or Weis
Announcing Permit MCP Gateway
Announcing Permit MCP Gateway, a new trust and enforcement layer for MCP that brings identity, consent, fine-grained authorization, auditability, and runtime control to AI agent actions.


Featured Stories

Or Weis
Announcing Permit MCP Gateway, a new trust and enforcement layer for MCP that brings identity, consent, fine-grained authorization, auditability, and runtime control to AI agent actions.

Gabriel L. Manor
The new Permit.io CLI brings developer-first workflows to access control. Define, test, deploy, and enforce fine-grained authorization using AI, CI/CD, GitOps, and OpenAPI — all from your terminal

Or Weis
AI agent authorization checks every agent action against policy, delegation, resource and context. Add per-action checks, trust ceilings and decision logs.

Or Weis
What ISO 42001 certification involves: the AI management system, accredited certification bodies, stage 1 and 2 audits, Annex A controls, and agent evidence.

Or Weis
EU AI Act logging requirements under Article 12 for high-risk AI systems, log retention rules (at least six months for deployers under Article 26(6)), ISO 42001 A.6.2.8, and practical logging design for AI agents.

Daniel Bass & Or Weis
What an authorization service does, when to use one instead of building your own, and a 2026 comparison of 7 authorization as a service providers: Permit.io, Cerbos, AuthZed, Auth0 FGA and more.

Or Weis
Production authorization enforcement requires four pillars: a policy decision at every sensitive action, granular policy models, realtime revocation, and auditable decisions. Control plane to OPAL to PDP to PEP to logs is the architecture that makes them work together.

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

Or Weis
AI agent audit trail guide: record identity, delegation, tool, resource, policy version, allow or deny, HITL approval and outcome for every agent action. Tool traces are not enough.

Or Weis
SOC 2 CC6.1 access control checklist for AI agents: what CC6 and CC7 assume, how agents break them, ISO 27001 mapping, and the evidence to produce.

Or Weis
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.

Or Weis
DORA vs NIST on access control: both point to least privilege and attributable logs, for NHIs and AI agents too. Decision logs turn access control into evidence.

Or Weis
AI agents get their own IdP token, separate from the user session. OAuth scopes are too coarse for resource-level rules; check agent role at each tool call.

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