# Authorization Authorization is the decision to permit or deny a subject access to system objects such as networks, data, applications, and services. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## datasette 0.65.5 DevFeed: [datasette 0.65.5]() Original publisher: [Read original article]() Author: Simon Willison Published: 2026-09-16T23:51:08Z Content type: release Language: en Sources: [Simon Willison's Weblog]() Topics: [Security](), [Authorization]() Tags: [bypass](), [datasette](), [datasette-1-544](), [issue](), [permissions](), [release](), [security](), [security-636]() ### AI overview Datasette 0.65.5 is a security release fixing an issue in which a trailing newline in a requested table name could bypass table permissions and expose private rows. ### Source excerpt Release: datasette 0.65.5 Security fix for an issue where a trailing newline in a requested table name could bypass table permissions and expose private rows, reported by dpfkdlemtp in GHSA-h547-rmjf-5m2m. Tags: security, datasette ## sem-ai 0.4.0: smaller responses, safer access, and pre-flight checks DevFeed: [sem-ai 0.4.0: smaller responses, safer access, and pre-flight checks]() Original publisher: [Read original article]() Author: Pete Miloravac Published: 2026-09-16T12:01:04Z Content type: release Language: en Sources: [Semaphore Engineering]() Topics: [AI-assisted coding](), [Claude Code](), [Command-line interface](), [Authorization](), [API](), [configuration]() Tags: [ai-coding-agents](), [api](), [audio](), [claude-code](), [command-line](), [configuration](), [permissions](), [pipelines](), [product-news](), [release](), [video]() ### AI overview Semaphore's sem-ai 0.4.0 release adds more compact workflow and pipeline responses, context switching across organizations and credentials, and support for managing pre-flight checks. The update is aimed at reducing context usage and enabling more targeted permissions for AI coding agents. ### Source excerpt AI coding agents work best when they receive the right information without unnecessary noise. They also need clearly defined permissions and reliable safeguards for the changes they make. sem-ai 0.4.0 improves all three areas. The release introduces more compact pipeline responses, flexible context switching, and support for Semaphore pre-flight checks. Watch Nick demonstrate the new [...] The post sem-ai 0.4.0: smaller responses, safer access, and pre-flight checks appeared first on Semaphore. ## New SymfonyCasts Course: Symfony Security - The Basics DevFeed: [New SymfonyCasts Course: Symfony Security - The Basics]() Original publisher: [Read original article]() Author: Kevin Bond Published: 2026-09-16T09:34:00Z Content type: release Language: en Sources: [Symfony Blog]() Topics: [Symfony](), [Security](), [Authentication](), [Authorization](), [firewalls]() Tags: [access-control](), [authentication](), [authorization](), [controllers](), [firewalls](), [forms](), [passwords](), [security](), [security-events](), [symfony]() ### AI overview SymfonyCasts announces a new course covering the fundamentals of Symfony Security. The course builds an authentication and authorization system with Symfony 8, and the material also works with Symfony 7. ### Source excerpt Authentication, authorization, roles, voters, firewalls... there's a lot happening inside Symfony's Security system. But once you understand how the pieces fit together, it's a powerful and flexible system for answering two fundamental questions: who is this... ## How to tell agent traffic from user traffic DevFeed: [How to tell agent traffic from user traffic]() Original publisher: [Read original article]() Author: WorkOS Published: 2026-09-16T00:00:00Z Content type: tutorial Language: en Sources: [WorkOS Blog]() Topics: [JSON Web Tokens](), [audit trail](), [audit](), [Security](), [Authorization]() Tags: [agent](), [audit](), [audit-trail](), [auth](), [how-to](), [logs](), [security]() ### AI overview This tutorial explains how to distinguish agent traffic from user traffic in access and audit logs. It describes identifying agent tokens with a claim, separating the acting agent from the delegating user, and recording both identities so automated changes can be queried accurately. ### Source excerpt Your access logs probably say a person did something an agent did. Four claims fix that, and one of them exists for exactly this purpose. ## How to study for the MCPA security and governance domain DevFeed: [How to study for the MCPA security and governance domain]() Original publisher: [Read original article]() Author: WorkOS Published: 2026-09-16T00:00:00Z Content type: tutorial Language: en Sources: [WorkOS Blog]() Topics: [Model Context Protocol](), [Security](), [Authorization](), [OAuth]() Tags: [agent](), [agentic](), [audit](), [authorization](), [model-context-protocol](), [oauth](), [security]() ### AI overview A study guide for the security and governance domain of the Model Context Protocol Associate exam. It explains trust boundaries, token audience validation, token handling between MCP servers and upstream APIs, and the distinction between consent and authorization. ### Source excerpt Security and governance is 24% of the new Model Context Protocol Associate exam. Here is what each competency actually covers in the 2026-07-28 spec, and the distinctions candidates get wrong. ## Building an AI-native data & insights operating system at Webflow DevFeed: [Building an AI-native data & insights operating system at Webflow]() Original publisher: [Read original article]() Author: Ashwini Chaube Published: 2026-09-16T00:00:00Z Content type: article Language: en Sources: [Webflow Blog]() Topics: [data](), [Artificial Intelligence](), [Platform Engineering](), [Data Science](), [decision-making](), [Authorization]() Tags: [agentic](), [ai](), [data](), [data-insights](), [inside-webflow](), [permissions](), [review](), [self-service](), [skills]() ### AI overview Webflow describes how its Data & Insights team built an AI-native operating system for trusted self-service analytics. The approach combines governed data, encoded business context, reusable skills and agents, permissions, architectural controls, review practices, and human judgment, while also changing how the team works through agent-first workflows, learning, and experimentation. ### Source excerpt How we built the governed foundations for trusted self-service analytics while transforming the way our own team works. ## How to test an AI agent policy before enforcing it DevFeed: [How to test an AI agent policy before enforcing it]() Original publisher: [Read original article]() Author: WorkOS Published: 2026-09-15T22:03:24Z Content type: tutorial Language: en Sources: [WorkOS Blog]() Topics: [AI Agent](), [Authorization](), [Testing](), [Access Control](), [Linear]() Tags: [access-control](), [ai-agent](), [authorization](), [how-to](), [testing]() ### AI overview This guide explains how to test authorization policies for AI agents before enforcing them. It presents reusable tests for role-based access control, task intent, organizational rules, and approval requirements, with checks against the connected service. ### Source excerpt Design and test AI agent policies that block unsafe actions and keep useful work moving. Learn to test intent, RBAC, and approvals, or try WorkOS Airlock. ## From Atlas experiment to Airlock: extracting agent governance into a product DevFeed: [From Atlas experiment to Airlock: extracting agent governance into a product]() Original publisher: [Read original article]() Author: WorkOS Published: 2026-09-15T15:35:36Z Content type: article Language: en Sources: [WorkOS Blog]() Topics: [Authorization](), [Security](), [Artificial Intelligence](), [App](), [Linear](), [Slack]() Tags: [agent](), [ai](), [ai-agents](), [authorization](), [email](), [integrations](), [linear](), [permission](), [policy](), [product](), [security](), [slack]() ### AI overview The article explains how WorkOS's Airlock grew from the Atlas experiment into a standalone authorization product for governing AI-agent actions in company tools. A demonstration shows policies blocking emails containing financial information and requiring approval for unfamiliar distribution lists. ### Source excerpt Airlock grew out of Atlas to give IT and security teams a shared way to govern agent actions. Aaron Tainter's Agent Night demo shows how it works. ## Let coding agents review PRs without giving them unrestricted merge access DevFeed: [Let coding agents review PRs without giving them unrestricted merge access]() Original publisher: [Read original article]() Author: WorkOS Published: 2026-09-15T15:29:00Z Content type: tutorial Language: en Sources: [WorkOS Blog]() Topics: [AI-assisted coding](), [Code review](), [GitHub](), [Authorization](), [Pull Request](), [pull-requests]() Tags: [ai-code-review](), [authorization](), [code-review](), [coding-agents](), [github](), [reviews]() ### AI overview This guide explains how to let coding agents review GitHub pull requests without granting unrestricted merge access. It recommends separate review and merge credentials, explicit merge assignments governed by WorkOS Airlock, required checks and reviews, and reapproval when the reviewed commit changes. ### Source excerpt Set GitHub permissions for AI code review, govern merges with Airlock, and prevent agents from merging code that changed after approval. ## MCP authorization: governing tool calls beyond OAuth DevFeed: [MCP authorization: governing tool calls beyond OAuth]() Original publisher: [Read original article]() Author: WorkOS Published: 2026-09-15T15:04:00Z Content type: tutorial Language: en Sources: [WorkOS Blog]() Topics: [Model Context Protocol](), [Authorization](), [MCP OAuth](), [MCP Server](), [OAuth]() Tags: [authorization](), [mcp](), [mcp-server](), [oauth](), [permissions](), [policy](), [scope](), [scopes]() ### AI overview This guide explains why OAuth scopes alone cannot govern the content and destination of MCP tool calls. It presents server- or gateway-side policy enforcement before execution, including request-content inspection, approval handling, and testing for data leakage. ### Source excerpt Secure MCP tool calls beyond OAuth scopes. Learn where to enforce tool permissions, check request content, and test for data leakage with Airlock. ## AI agent approval workflows: handling edits and retries DevFeed: [AI agent approval workflows: handling edits and retries]() Original publisher: [Read original article]() Author: WorkOS Published: 2026-09-15T15:02:39Z Content type: tutorial Language: en Sources: [WorkOS Blog]() Topics: [AI Agent](), [Authorization](), [Tool]() Tags: [agent](), [authorization](), [execution](), [how-to](), [retry](), [review](), [server](), [tool](), [workflows]() ### AI overview This guide explains how to add human approval to AI agent tool calls with WorkOS Airlock. It covers binding approval to an exact request, persisting the proposed action, resuming execution after approval, and recovering when a provider response is uncertain. ### Source excerpt Add human approval to AI agent tool calls. Learn how to review exact requests, resume execution, and handle edits and retries with Airlock. ## DigiCert's AI Trust framework for governing enterprise AI agents and models DevFeed: [DigiCert's AI Trust framework for governing enterprise AI agents and models]() Original publisher: [Read original article]() Author: Robin Birtstone Published: 2026-09-15T15:00:00Z Content type: article Language: en Sources: [www.theregister.com - Articles]() Topics: [ai-governance](), [AI Agent](), [Authorization](), [Security](), [data]() Tags: [agents](), [ai](), [ai-governance](), [authorization](), [data](), [security](), [sponsored]() ### AI overview This sponsored feature presents DigiCert's AI Trust framework for governing enterprise AI agents. The framework uses public key infrastructure, DNS, and attestation to help organizations identify agents, track data and credentials, stop compromised agents, and reconstruct incidents. ### Source excerpt SPONSORED FEATURE: DigiCert wants to hand every agent a passport, complete with an expiry date and a named human owner ## Give every teammate and agent the right level of access to your Workers DevFeed: [Give every teammate and agent the right level of access to your Workers]() Original publisher: [Read original article]() Author: Visal In Published: 2026-09-15T13:00:00Z Content type: release Language: en Sources: [Cloudflare Blog]() Topics: [Workers](), [Authorization](), [Developer Platform](), [debug]() Tags: [agent](), [api](), [cloudflare](), [debug](), [developer](), [developer-platform](), [developers](), [identity](), [least-privilege](), [logs](), [metrics](), [monitor](), [product-news](), [scope](), [security](), [traces](), [workers](), [workflows]() ### AI overview Cloudflare now lets teams scope access to individual Workers and assign narrower Developer Platform roles. Teammates, CI tokens, and agents can receive only the permissions needed to debug, deploy, or monitor safely. ### Source excerpt You can now scope access to individual Workers and assign narrower Developer Platform roles, so teammates, CI tokens, and agents get only the access they need to debug, deploy, or monitor safely. ## How to Run Codex in an Ubuntu Virtual Machine on Proxmox DevFeed: [How to Run Codex in an Ubuntu Virtual Machine on Proxmox]() Original publisher: [Read original article]() Author: Travis Henderson Published: 2026-09-15T12:00:11Z Content type: tutorial Language: en Sources: [Atomic Object]() Topics: [AI-assisted coding](), [codex](), [Linux](), [Ubuntu](), [Proxmox](), [OpenSSH](), [Authorization]() Tags: [ai-agent](), [ai-for-developers](), [codex](), [coding-agents](), [development](), [linux](), [openssh](), [permissions](), [proxmox](), [sandbox](), [ubuntu]() ### AI overview This guide explains how to isolate Codex in a headless Ubuntu virtual machine running on Proxmox, using a separate Linux account and OpenSSH. The setup limits the files, dependencies, and network access available to the agent while keeping administrator tasks separate, but it does not eliminate risks from credentials, network access, or mistakes pushed to GitHub. ### Source excerpt The more useful coding agents become, the more access they tend to need. Installing dependencies, running commands, changing files, and generally more autonomy are part of the appeal. They're also the point where I start thinking about what else the coding agent can reach, especially while these tools are changing so quickly. My answer is [...] The post Your Coding Agent Should be in Jail. Here's Why and How. appeared first on Atomic Spin. ## Agent session chains that can't escalate DevFeed: [Agent session chains that can't escalate]() Original publisher: [Read original article]() Author: WorkOS Published: 2026-09-15T00:00:00Z Content type: article Language: en Sources: [WorkOS Blog]() Topics: [Authorization](), [API](), [API keys](), [systems]() Tags: [agent](), [api](), [auth](), [authorization](), [backend](), [multi-agent](), [multi-agent-systems](), [permission](), [server](), [systems]() ### AI overview The article explains how Agent Auth session chaining lets an agent create separately scoped child sessions for subtasks. Each child records its parent, uses its own access and single-use refresh tokens, can be revoked independently, and cannot outlive the root session. The supplied text also states that the backend creates the chain server-side using an API key. ### Source excerpt An agent can open a child session of itself for a sub-task. The chain re-derives authority at every hop and can never outlive its root. ## A Case Study: Building an EN 18031-Compliant IoT Solution with ESP32-C5 and ESP RainMaker DevFeed: [A Case Study: Building an EN 18031-Compliant IoT Solution with ESP32-C5 and ESP RainMaker]() Original publisher: [Read original article]() Author: John Lee Published: 2026-09-14T00:00:00Z Content type: article Language: en Sources: [Blog on Developer Portal]() Topics: [ESP32](), [Internet of things](), [Security](), [Cloud](), [Security & Privacy](), [Espressif](), [Authentication](), [Authorization]() Tags: [access-control](), [authentication](), [blog](), [compliance](), [connectivity](), [cryptographic](), [data](), [data-management](), [documentation](), [en-18031](), [esp-rainmaker](), [esp32-c5](), [espressif](), [eu](), [firmware](), [iot](), [privacy](), [rainmaker](), [regulatory](), [security](), [standards](), [storage]() ### AI overview This case study describes an ESP32-C5 and ESP RainMaker device-to-cloud IoT implementation assessed against EN 18031 cybersecurity and privacy requirements for products targeting the EU market. ### Source excerpt This case study assesses device-to-cloud IoT implementation of products based on ESP32-C5 and ESP RainMaker against the EN 18031 security requirements for the EU market. ## How to add WorkOS AuthKit to a Ruby on Rails app DevFeed: [How to add WorkOS AuthKit to a Ruby on Rails app]() Original publisher: [Read original article]() Author: WorkOS Published: 2026-09-14T00:00:00Z Content type: tutorial Language: en Sources: [WorkOS Blog]() Topics: [Rails](), [Authentication](), [Ruby](), [Command-line interface](), [Authorization](), [password reset]() Tags: [authentication](), [building](), [cli](), [how-to](), [password-reset](), [production](), [ruby](), [sign-in]() ### AI overview A tutorial on adding WorkOS AuthKit to a Ruby on Rails application. It explains how the CLI sets up the integration, how the sealed-cookie session layer is refreshed in a Rails before_action, and how Redirect URI, Initiate login URL, and Sign-out URI settings affect authentication flows and production logout. ### Source excerpt The CLI gets you signed in. This is the session layer underneath it: what the sealed cookie holds, how to refresh it inside a before_action, and the three dashboard settings that break logout in production. ## AP2 Protocol Explained: How Agent Payments Get Authorized DevFeed: [AP2 Protocol Explained: How Agent Payments Get Authorized]() Original publisher: [Read original article]() Author: Ayush Agarwal Published: 2026-09-13T00:00:00Z Content type: article Language: en Sources: [Dodo Payments Blog]() Topics: [Authorization](), [AI Agent](), [Artificial Intelligence](), [JSON Web Tokens](), [Google]() Tags: [agent](), [agentic](), [ai](), [authentication](), [cryptographic](), [google](), [payments](), [tokens]() ### AI overview A practical explanation of AP2, an authorization and evidence protocol for AI agent payment transactions. It describes cryptographic proof, verifiable digital credentials, SD-JWTs, and separate checkout and payment mandates. ### Source excerpt A practical guide to AP2, the Agent Payments Protocol: checkout and payment mandates, open versus closed authorization, verifiable digital credentials, and what it means for merchants. ## AI Coding Tip 036 - Grant AI the Least Privilege Possible DevFeed: [AI Coding Tip 036 - Grant AI the Least Privilege Possible]() Original publisher: [Read original article]() Author: Maxi Contieri Published: 2026-09-12T15:51:59Z Content type: tutorial Language: en Sources: [Maximiliano Contieri - Software Design]() Topics: [Artificial Intelligence](), [AI Agent](), [Authorization](), [API](), [systems]() Tags: [ai](), [ai-agent](), [api](), [authorization](), [least-privilege](), [systems]() ### AI overview This developer tip explains why AI agents should receive only the access required for their tasks. It describes how overly broad API permissions, shared credentials, compromised context, and external models connected through MCP can turn routine automation into unauthorized actions. ### Source excerpt Deny by default, or watch your API become someone else's playground. TL;DR: Give every AI agent only the access its task needs, and watch for the intrusion nobody granted. Common Mistake ❌ You wire ## Why MCP security is about permissions overhaul DevFeed: [Why MCP security is about permissions overhaul]() Original publisher: [Read original article]() Author: Mohit Bansal Published: 2026-09-12T15:00:00Z Content type: article Language: en Sources: [The New Stack]() Topics: [Model Context Protocol](), [Authorization](), [GitHub](), [anthropic]() Tags: [ai-agent](), [ai-agents](), [github](), [mcp](), [model-context-protocol-mcp](), [post-contributed](), [security](), [sponsor-webflow](), [sponsored-post-contributed](), [webflow]() ### AI overview The article argues that MCP security problems are fundamentally permission problems, not merely infrastructure flaws. It calls for compartmentalized, task-scoped access to reduce risks such as prompt injection, tool poisoning, and excessive inherited trust. ### Source excerpt Anthropic's Model Context Protocol (MCP) went into production in late 2024. It spread rapidly after that. Since then, thousands of The post Why MCP security is about permissions overhaul appeared first on The New Stack. ## CrowdStrike Announces Agentic Identity Provider DevFeed: [CrowdStrike Announces Agentic Identity Provider]() Original publisher: [Read original article]() Author: Ryan Terry Published: 2026-09-12T11:17:51.295154Z Content type: release Language: en Sources: [Blog]() Topics: [AI Agent](), [Next-Gen Identity Security](), [Authorization](), [Security](), [Authentication]() Tags: [2026](), [agentic](), [ai](), [ai-agent](), [api-keys](), [applications](), [authentication](), [authorization](), [cloud-infrastructure](), [code](), [enterprise](), [identity](), [identity-control](), [next-gen-identity-security](), [saas](), [security]() ### AI overview CrowdStrike announces Agentic Identity Provider, a capability in CrowdStrike Falcon Next-Gen Identity Security that gives AI agents trusted identities and continuously controls their access according to real-time security and business context. The announcement also covers expanded privileged access across SaaS applications, endpoints, code repositories, and cloud infrastructure. ### Source excerpt CrowdStrike gives every AI agent a trusted identity and controls their access based on real-time context, and expands modern privileged access. ## Forgejo 16.0.4 and 15.0.8 Fix Critical Repository Template RCE DevFeed: [Forgejo 16.0.4 and 15.0.8 Fix Critical Repository Template RCE]() Original publisher: [Read original article]() Author: Christian Rakoot Published: 2026-09-12T06:40:18Z Content type: article Language: en Sources: [Self Host Lab]() Topics: [vulnerability](), [releases](), [Security](), [Template](), [Authorization](), [API](), [Git]() Tags: [api](), [docker-containers](), [docker-containers-news](), [forgejo](), [git](), [news](), [release](), [security](), [self-hosted](), [update](), [vulnerability]() ### AI overview Forgejo 16.0.4 and 15.0.8 fix a critical remote code execution vulnerability in repository-template creation, along with an API authorization bypass. The article explains how malicious template variables could restore a .git directory with executable hooks and urges affected self-hosted instances to update. ### Source excerpt Forgejo 16.0.4 and 15.0.8 patch a critical remote code execution vulnerability in repository templates, tracked as CVE-2026-89094 with a CVSS score of 9.9, plus a narrower API permission bypass. Any instance on 16.0.3 or earlier, or 15.0.7 or earlier on the LTS branch, is vulnerable. Here's what happened, why it matters, and how to update. ## The hard part of an MCP gateway is auth DevFeed: [The hard part of an MCP gateway is auth]() Original publisher: [Read original article]() Author: WorkOS Published: 2026-09-11T15:22:28Z Content type: opinion Language: en Sources: [WorkOS Blog]() Topics: [MCP Server](), [Authorization](), [Model Context Protocol](), [Artificial Intelligence]() Tags: [audit](), [auth](), [github](), [integration](), [mcp](), [mcp-gateway](), [mcp-server](), [salesforce](), [scopes](), [slack](), [warehouse]() ### AI overview The article examines Sierra's internal MCP gateway and argues that its most difficult challenges are authentication, identity, per-tool scopes, consent, and audit rather than MCP protocol design. It also discusses integration work and the lack of standardized gateway behavior. ### Source excerpt Sierra's MCP gateway iceberg is a field report on agent auth: identity, per-tool scopes, consent, and audit are the submerged mass, and they ship off the shelf. ## Introducing automatic remediation policies with Cloudflare CASB DevFeed: [Introducing automatic remediation policies with Cloudflare CASB]() Original publisher: [Read original article]() Author: Abe Carryl Published: 2026-09-11T13:00:00Z Content type: release Language: en Sources: [Cloudflare Blog]() Topics: [Software as a service](), [Cloudflare One](), [Orchestration](), [Authorization]() Tags: [automation](), [casb](), [cloudflare](), [cloudflare-one](), [event-driven](), [oauth](), [orchestration](), [policy](), [reactive](), [saas](), [security](), [security-operations-center](), [zero-trust]() ### AI overview Cloudflare introduces CASB policies that automatically remediate SaaS security findings, including revoking risky file shares and sending webhooks after a finding is detected. ### Source excerpt Cloudflare CASB policies introduce a native automation engine built directly on the Cloudflare developer platform to remediate SaaS risks automatically. Security teams can now design event-driven logic to revoke risky file shares and send webhooks without manual intervention. [Next page]()