October 2026 Summaries

18 posts from Permit.io

Filter
Month: Year:
Post Summaries Back to Blog
OpenFGA is a CNCF Incubating, Apache 2.0-licensed authorization system based on Zanzibar-style relationship-based access control (ReBAC), supporting RBAC and limited attribute-based patterns through contextual and conditional tuples. Its alternatives span relationship-focused tools such as SpiceDB, which emphasizes configurable consistency through ZedTokens, and policy-focused engines including Cerbos, OPA, and Cedar, which are generally better suited to conditional, attribute-heavy authorization rules. Permit.io is presented as a managed control plane that combines RBAC, ReBAC, ABAC, and policy-based approaches while generating policies for engines such as OPA and Cedar and offering management interfaces and local decision points. The post recommends selecting systems based on whether access derives primarily from resource relationships, attributes and conditions, AWS integration, formal verification requirements, or operational preferences. It also reports Permit’s early-access Nexus PDP benchmarks of 5.6 ms P99 server-side RBAC checks on a two-CPU pod, while noting that these are vendor measurements rather than direct comparisons with OpenFGA or SpiceDB and should be validated against individual workloads.
Oct 30, 2026 1,920 words in the original blog post.
WorkOS Fine-Grained Authorization, launched in February 2026, extends WorkOS RBAC with hierarchical, resource-scoped permissions that automatically inherit through structures such as workspaces, projects, and applications, while integrating with WorkOS SSO, Directory Sync, and AuthKit. Permit.io presents itself as a broader managed authorization platform supporting RBAC, relationship-based, attribute-based, and policy-based access control, with policies generated in open languages such as Rego or Cedar and decision points available either in its cloud or as self-hosted Edge PDPs. The comparison emphasizes WorkOS FGA’s suitability for organizations already using the WorkOS ecosystem and needing cloud-hosted hierarchical authorization, while positioning Permit.io for teams requiring portable policy code, local authorization decisions, complex relationship graphs, GitOps workflows, or embedded interfaces for access management. WorkOS reports sub-50 ms p95 authorization checks, whereas Permit cites a 5.6 ms p99 benchmark for server-side RBAC checks, though deployment conditions and workload differences may affect direct comparisons. Pricing is not directly comparable because WorkOS does not publish separate FGA rates, while Permit offers a free Community tier and usage-based paid plans. The post recommends testing production-like rules in both products, including outage behavior, policy deployment processes, and explainability of access decisions, before making a selection.
Oct 29, 2026 1,531 words in the original blog post.
Australia’s APP 1.7–1.9 automated decision-making transparency obligations will begin on 10 December 2026, requiring covered organizations to disclose in their privacy policies the types of personal information used by computer programs and the kinds of decisions those programs make or substantially assist. The checklist recommends that product, security, privacy, and platform teams build evidence-backed inventories of automated and computer-assisted decision systems, including APIs, models, workflows, rules engines, and data-access points, rather than focusing only on AI models. It organizes implementation around four areas: identifying enforcement points where decisions occur, mapping personal-information categories to resources, actions, tenants, and decision types, preventing disclosure statements from becoming outdated as systems and permissions change, and maintaining logs and exports that document decision context, data use, versions, and outcomes. The material emphasizes that this is an engineering-oriented framework rather than legal advice, arguing that reliable transparency depends on being able to demonstrate where decisions are enforced, what information may influence them, how changes propagate, and what audit records establish.
Oct 28, 2026 1,100 words in the original blog post.
Australia’s APP 1.7, commencing 10 December 2026 under the Privacy and Other Legislation Amendment Act 2024, requires covered APP entities to update their privacy policies when they use personal information in computer programs that make or substantially and directly assist decisions likely to significantly affect individuals’ rights or interests. The required disclosures cover the kinds of personal information used and the kinds of solely automated or automation-assisted decisions involved, including beneficial, adverse, refused, or failed decisions; the obligation applies beyond AI to rules engines, scoring systems, workflows, and agentic systems. The post argues that while legal counsel should determine policy wording and applicability, organizations need engineering evidence to support accurate disclosures, including inventories of decisioning systems, mappings between personal-information categories and authorized resources or actions, runtime enforcement at data-access and decision-action points, granular permissions for humans and non-human agents, synchronized policy changes, and auditable authorization records. It notes that APRA-regulated organizations face related, though separate, expectations around AI governance, operational resilience, and non-human identity management. Permit.io presents its authorization platform, hybrid policy decision point architecture, OPAL synchronization layer, and audit logs as tools that can support this evidence-gathering process, alongside a suggested 90-, 60-, and 30-day preparation timeline before commencement.
Oct 27, 2026 2,429 words in the original blog post.
EN 18286:2026 is the first harmonised EU AI Act standard, translating Article 17 quality management system requirements for providers of high-risk AI systems into auditable processes and offering a presumption of conformity for covered requirements. Approved by CEN in July 2026 and referenced in the EU Official Journal in October, it is designed to complement frameworks such as ISO/IEC 42001 and ISO 9001 while addressing risk management, human oversight, data quality, cybersecurity, leadership, planning, and documentation. Although the standard does not specifically address AI agents, authorization, or Model Context Protocol, the article argues that agentic systems need controls that document what agents can do, why actions are permitted, and what oversight occurred. It criticizes the common practice of allowing agents to inherit all user permissions through OAuth tokens, proposing instead that agents have separate identities, undergo policy checks for each tool call, require human approval for sensitive actions, and generate detailed decision logs. The article presents Permit.io’s policy engine, approval workflows, audit logs, and MCP Gateway as one possible implementation for creating evidence that supports compliance and incident reconstruction, while noting that EN 18286 applies only to Article 17 requirements and does not alone guarantee full AI Act compliance.
Oct 22, 2026 1,592 words in the original blog post.
NIST NCCoE’s February 2026 concept paper on software and AI agent identity and authorization highlights identification, authorization, access delegation, and logging as key areas for securing AI agents, while seeking feedback rather than establishing a standard or certification framework. The proposed engineering mapping calls for each agent to have a distinct non-human identity, narrowly scoped policy-based permissions, explicit and revocable human-to-agent delegation grants, and detailed decision logs that record the agent, human principal, tool, resource, action, tenant, policy rationale, and allow-or-deny outcome. Because agents can invoke tools, access changing contexts, and operate with partial autonomy, authorization decisions should be fine-grained across resources, tenants, environments, relationships, and approval states, with controls such as trust ceilings and human-in-the-loop review for high-risk actions. The guidance is intended as a design-review aid, particularly for MCP and tool-calling systems, emphasizing that agents should be treated as privileged identities and that application-level policy enforcement must occur before tools execute.
Oct 21, 2026 1,130 words in the original blog post.
AI agents that access enterprise tools, sensitive data, or operational systems should be governed as distinct privileged non-human identities rather than through shared API keys, service accounts, or borrowed human sessions. The recommended model gives each agent and session a separate identity, grants least-privilege permissions scoped by tool, resource, tenant, and time, and uses explicit, revocable human-to-agent delegation where effective access is limited by the human’s rights, the agent’s grants, and administrative trust ceilings. Authorization should be evaluated at every sensitive tool call rather than only at login, with human approval treated as an auditable policy requirement for high-risk actions such as exporting data, submitting payments, deleting resources, or modifying production systems. The article links this approach to emerging NIST NCCoE and APRA attention to agent identity, authorization, delegation, and logging, while emphasizing that this alignment is not a compliance certification. It also argues that OAuth or client authentication for MCP tool connections does not replace per-tool authorization, recommending policy enforcement points at MCP gateways, APIs, service layers, or workflow runners. Permit.io positions its hybrid policy decision point, OPAL distribution system, decision logs, and MCP Gateway as tools for implementing this architecture, which should provide forensic evidence of who delegated authority, which agent acted, what it accessed, whether it was allowed or denied, and why.
Oct 20, 2026 2,405 words in the original blog post.
Permit.io and Cerbos are authorization platforms with open-source decision points but different default operating models: Permit.io centers on a managed control plane with visual policy editing, embeddable administration components, and locally deployable Edge PDPs, while Cerbos emphasizes a self-hosted, stateless PDP using YAML or JSON policies with CEL and offers Cerbos Hub as an optional management layer. Permit.io is positioned for organizations where product teams, support staff, or customers need to manage access without code releases, particularly for combined RBAC, ABAC, and relationship-based authorization with policy and data synchronization, whereas Cerbos is suited to engineering-led workflows that favor policy files, CI-based review, air-gapped operation, and query planning for database filtering. Both can continue making local decisions when their policies are already available, though their approaches to policy distribution, decision-time data, auditing, UI components, and on-premise deployment differ. The comparison notes that Permit generates Rego or Cedar policies and charges primarily by monthly active users, while Cerbos uses its own policy schema with CEL, provides a free standalone PDP, and prices Hub by monthly active principals. It recommends evaluating each system through a production-like proof of concept that tests policy changes, outages, auditing, deployment topology, and operational costs, while suggesting graph-focused systems such as OpenFGA or AuthZed for workloads requiring large-scale Zanzibar-style relationship consistency.
Oct 15, 2026 3,864 words in the original blog post.
Human-to-agent delegation requires an audit trail that establishes who authorized an agent, which agent and tools acted, what resources or data were involved, the applicable policy decision and rationale, and any human approval or consent. The article distinguishes authorization evidence from ordinary AI telemetry such as prompts, tool calls, and token usage, arguing that operational traces cannot prove whether an action was permitted under a specific person’s authority. It recommends recording this information at the Policy Enforcement Point where an agent invokes a sensitive tool, API, or MCP server, with a Policy Decision Point evaluating the human, agent, tool, resource, and contextual delegation limits before execution. This approach supports least privilege, revocation, accountability, and incident reconstruction while applying the same authorization standards expected for human actions to agent-driven workflows. It notes that such records alone do not ensure regulatory compliance, but they provide the evidence reviewers need to determine who authorized an action, under which policy, and against which resource.
Oct 14, 2026 1,212 words in the original blog post.
Permit.io’s migration guide advises Oso Cloud customers to reassess their authorization infrastructure following Tiny Ltd.’s October 2026 acquisition of Oso Cloud and the departure of most of its engineering team to Temporal, while noting that Oso Cloud has said it will continue operating normally. It explains that Oso’s deprecated standalone Polar engine and uncertain long-term maintenance may create risks for production users, then maps Polar’s RBAC, relationship-based access control, and attribute-based access control concepts to Permit.io resources, roles, relationships, condition sets, and API checks. The guide recommends inventorying existing policies, recreating them in Permit.io through its UI, APIs, or Terraform, running both systems in parallel to identify decision mismatches, cutting over only after reaching parity, and validating audit logging. It also presents Permit’s local PDP sidecar as an alternative to Oso’s embedded local authorization mode, says its underlying policy engines support open standards such as Rego and Cedar, and offers eligible former Oso customers temporary quota increases and migration assistance.
Oct 14, 2026 2,248 words in the original blog post.
AI agents increase authorization demands by enabling high volumes of multi-step, potentially consequential actions across tools and systems, rather than reducing existing security requirements. The article argues that effective agent authorization must explicitly account for the human delegator, the agent identity, delegated scope, target resource, and contextual conditions, using short-lived, revocable credentials instead of standing access to user accounts. It recommends per-action policy checks to address prompt injection, changing intent, and session drift; least-privilege permissions and trust ceilings for individual tools and data; enforcement gateways in front of MCP servers and APIs; and detailed decision logs that record the delegation chain, policy rationale, and any human approval. It also describes agent identity handshakes, declared-intent validation, and monitoring or “judge” agents as mechanisms for detecting behavior that departs from authorized purposes. Permit.io presents its MCP Gateway and real-time policy synchronization architecture as an implementation approach for applying fine-grained authorization, revocation, consent, and auditing to agent tool calls.
Oct 13, 2026 2,299 words in the original blog post.
ISO/IEC 42001:2023 is an international standard for AI management systems (AIMS), and certification requires an external, preferably accredited certification body to audit an organization’s governance processes rather than ISO itself issuing a certificate. The standard applies to organizations that develop, provide, or use AI systems and requires a continual management cycle covering scope, leadership, AI risk and impact assessments, operational controls, documentation, monitoring, internal audits, management review, and corrective improvement. Audits typically proceed through a documentation and readiness-focused stage 1, an implementation and effectiveness-focused stage 2, and continuing surveillance audits during a three-year certification cycle. Annex A contains 38 selectable controls whose applicability must be justified through risk treatment and a Statement of Applicability, with agent-related priorities often including intended-use restrictions, accountability, tool-call event logging, and third-party responsibilities. Authorization platforms such as Permit can provide supporting evidence through policy decisions, tool-call logs, approval records, and version-controlled policy changes, but they cannot replace broader requirements such as leadership oversight, impact assessments, data governance, model documentation, internal audits, or certification-body review.
Oct 09, 2026 2,707 words in the original blog post.
EU AI Act Article 12 requires high-risk AI systems to support automatic event logging throughout their lifetime to enable risk detection, post-market monitoring, and operational oversight, while it does not automatically apply to all AI agents, internal assistants, or MCP-based tools. The discussion argues that agents capable of accessing data or producing real-world side effects should log authorization decisions at tool-call boundaries, rather than relying solely on model prompts, outputs, or application errors. ISO/IEC 42001 similarly calls for organizations to determine when event logging is needed across an AI system’s lifecycle, with logging during active use as a minimum, although certification under the standard does not itself establish AI Act compliance. Recommended records connect agent and user identities, delegation context, requested actions, affected resources, policy versions, allow or deny decisions, approvals, execution results, and correlation identifiers, while minimizing sensitive data through redaction, hashes, and metadata. For high-risk systems, the AI Act generally requires providers and deployers to retain relevant logs for at least six months, subject to other applicable privacy or national laws. The piece presents centralized policy management, distributed authorization enforcement, and structured decision logs as a practical governance approach, while emphasizing that such tools can support evidence and control requirements but cannot independently guarantee regulatory compliance.
Oct 08, 2026 3,006 words in the original blog post.
Production-grade application authorization is presented as relying on four interconnected pillars: enforcement of permission checks at every sensitive action, granularity that accounts for tenants, resources, actions, relationships, and attributes, realtime synchronization of policy and access-data changes to support rapid revocation, and auditability through explainable decision records. The discussion distinguishes authentication from authorization and argues that checks limited to login, user-interface controls, or broad global roles can leave APIs, data queries, background jobs, and AI-agent tool calls vulnerable. It recommends combining RBAC, ABAC, and relationship-based access controls as needed, using policy enforcement points near application actions and policy decision points to evaluate centralized rules locally. A hybrid architecture involving a control plane, OPAL for near-real-time distribution, local PDPs, PEPs, and administrative and runtime decision logs is proposed to balance governance, low latency, resilience, and evidence requirements. The framework is positioned as particularly relevant to multi-tenant SaaS, AI agents, and regulated environments, while simpler internal applications with only a few static roles may not require the full approach.
Oct 06, 2026 2,558 words in the original blog post.
Authorization as a service centralizes decisions about what authenticated users, services, or agents may do, separating this function from authentication and application code. The vendor-written comparison evaluates Permit.io, Oso Cloud, Cerbos, AuthZed SpiceDB, Auth0 FGA, WorkOS FGA, and AWS Verified Permissions by access model, deployment, policy language, open-source availability, and pricing approach, emphasizing that choices depend primarily on who manages policies, where authorization decisions must run, and whether access needs are role-, attribute-, or relationship-based. It presents Permit.io as a managed control plane with cloud or locally deployed PDPs, policy management interfaces, and support for RBAC, ReBAC, and edge-based ABAC; Cerbos as a self-hosted, policy-as-code PDP; AuthZed and Auth0 FGA as relationship-graph-focused options; WorkOS FGA for hierarchical resource-scoped roles; AWS Verified Permissions for AWS-native Cedar policies; and Oso Cloud for declarative logic and database filtering. The comparison also highlights operational considerations such as resilience during control-plane outages, policy and data synchronization, audit-log exports, latency, and whether applications themselves must determine fail-open or fail-closed behavior when a PDP is unavailable.
Oct 05, 2026 3,806 words in the original blog post.
AI agent audit logs provide evidence that tool-using or data-changing agents acted with appropriate authorization, going beyond identity-provider and application logs by recording the decision context, delegation, policy, and resulting side effect. A practical record should capture twelve core elements: the agent identity, human authority or delegation chain, tool and relevant parameters, resource, action, policy ID and version, allow-or-deny decision with an explanation, any human approval, timestamp, request or trace ID, tenant and environment, and the final outcome. The approach aligns with NIST audit-record principles while adding agent-specific details needed to explain why an action was permitted or blocked. Organizations are advised to log denied attempts as well as successful ones, avoid unnecessarily storing sensitive prompts, retain and protect logs according to risk and compliance needs, and correlate authorization records with identity, application, tool, and downstream-system events. Such evidence can support SOC 2 and ISO 27001 logging discussions, though the proposed schema is an engineering pattern rather than a formal compliance requirement.
Oct 05, 2026 2,650 words in the original blog post.
An AI agent audit trail should provide authorization evidence for each sensitive action, showing the agent identity, the human user or delegation chain, tool and resource details, policy version, allow-or-deny decision and reason, approvals, timestamps, correlation IDs, and the eventual side-effect outcome. While LLM and tool-call traces help diagnose model behavior and execution, they do not prove that access controls were enforced under the applicable policy. The recommended approach is to log decisions at an authorization boundary such as a policy decision point or MCP gateway before tools execute, then correlate those records with tool traces and downstream changes. Auditors assessing standards such as SOC 2 and ISO 27001 may examine whether agent permissions are limited, denials are recorded, approvals are documented, logs are protected, and decisions can be reconstructed later. Human-in-the-loop approvals should be incorporated into the same evidence chain, and replaying an action should reconstruct the authorization decision from immutable records rather than rerun the language model.
Oct 02, 2026 1,186 words in the original blog post.
AI agents complicate SOC 2 CC6 and CC7 and ISO 27001 access-control evidence because they can act continuously, use delegated credentials, chain tools, and trigger side effects that are not fully captured by traditional login, OAuth, or shared-service-account logs. The article argues that organizations should preserve OAuth for authentication and delegation but enforce deterministic authorization at the actual action boundary, such as an MCP tool call, API endpoint, workflow step, or data operation. It recommends assigning distinct identities to agents, recording their human or service delegators, explicitly managing and periodically reviewing agent entitlements, identifying privileged tools, and requiring approvals for high-risk actions. To support controls covering logical access, monitoring, privileged access, and logging, organizations should retain decision-level records containing the agent, delegator, resource, action, policy version, context, approval status, and allow-or-deny outcome, with links to broader application and SIEM logs. The proposed architecture combines RBAC, ABAC, and relationship-based policies with a policy decision point near the side effect, real-time policy updates, and auditable approval workflows, while emphasizing that such an authorization layer supports compliance evidence rather than independently guaranteeing SOC 2 or ISO 27001 certification.
Oct 01, 2026 2,893 words in the original blog post.