# Access Control Published articles for Access Control. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## 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... ## Auth0 launches v0 integration for production application authentication DevFeed: [Auth0 launches v0 integration for production application authentication]() Original publisher: [Read original article]() Author: Juan Cruz Martinez Published: 2026-09-16T00:00:00Z Content type: release Language: en Sources: [Auth0 Blog]() Topics: [Auth0](), [Authentication](), [app builder](), [Access Control](), [Artificial Intelligence](), [Vercel](), [MFA]() Tags: [access-control](), [ai](), [app-builder](), [auth0](), [authentication](), [mfa](), [sdk](), [vercel]() ### AI overview Auth0 is launching an integration with v0 that lets users configure authentication directly from prompts, including login, protected routes, B2B use cases, enterprise identity providers, and MFA. The integration can create Auth0 applications, configure connections, and wire the SDK into generated code. ### Source excerpt Stop relying on generic login forms. Use the new Auth0 v0 integration on the Vercel identity platform to build secure, production-ready AI app authentication. ## Shared Selective Persistent Memory for Agentic LLM Systems DevFeed: [Shared Selective Persistent Memory for Agentic LLM Systems]() Original publisher: [Read original article]() Published: 2026-09-16T00:00:00Z Content type: article Language: en Sources: [Apple Machine Learning Research]() Topics: [Large Language Model](), [agent observability](), [Framework](), [Code](), [configuration](), [Access Control](), [Git](), [Model Context Protocol (MCP)](), [CSV](), [SQL](), [Grafana]() Tags: [access-control](), [agentic](), [agents](), [code](), [configuration](), [csv](), [dashboards](), [git](), [llm](), [mcp](), [memory](), [platform](), [replication](), [sql]() ### AI overview This research introduces shared selective persistent memory for agentic LLM systems. The architecture retains reusable task specifications, data schemas, tool configurations, and output constraints while discarding session-specific reasoning traces. Shared workspaces support role-based collaborative reuse, and experiments report higher task completion than no memory or full-history persistence, along with zero-token data refresh and lower token costs. ### Source excerpt Agentic LLM systems that generate code through multi-turn tool use face a fundamental context problem: each session starts from zero, discarding the configuration choices, domain constraints, data schemas, and tool-use patterns that made previous sessions productive. Naively persisting entire conversation histories is both token-inefficient and counterproductive--irrelevant context degrades generation quality. We introduce shared selective persistent memory, a memory architecture for agentic systems that identifies and retains four categories of reusable context--task specifications, data... ## 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. ## How to Build an Endpoint Data Loss Prevention Strategy for Your Development Team DevFeed: [How to Build an Endpoint Data Loss Prevention Strategy for Your Development Team]() Original publisher: [Read original article]() Author: Alex Tray Published: 2026-09-15T21:03:09Z Content type: tutorial Language: en Sources: [freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More]() Topics: [data loss prevention](), [Development](), [Access Control](), [data]() Tags: [access-control](), [cybersecurity](), [cybersecurityawareness](), [data-loss-prevention](), [data-protection](), [database](), [development](), [encryption](), [endpoint-security](), [hardcoded-credentials](), [it-security](), [net-conf](), [remote-access](), [secrets](), [sensitive-data](), [web-development]() ### AI overview A tutorial for development teams on building endpoint data loss prevention strategies. It covers auditing laptops for secrets and sensitive data, removing unnecessary copies, rotating exposed credentials, and establishing access controls. ### Source excerpt A developer's laptop holds more sensitive data than most people realize: API keys, database credentials, staging environment secrets, and sometimes entire copies of production data pulled down "just f ## What your agent sandbox can reach by default DevFeed: [What your agent sandbox can reach by default]() Original publisher: [Read original article]() Author: WorkOS Published: 2026-09-15T00:00:00Z Content type: article Language: en Sources: [WorkOS Blog]() Topics: [Network](), [Access Control](), [Claude Code](), [codex](), [Claude](), [ChatGPT]() Tags: [access-control](), [anthropic](), [llms](), [network](), [security]() ### AI overview This reference compares outbound network access defaults in Codex, ChatGPT Work, Claude Code, and other hosted agent environments. It examines what the documentation says before configuration and argues that egress allowlists provide a stronger boundary than detection filters. ### Source excerpt Codex, ChatGPT Work and Claude Code make five different choices about outbound network access. Here is what each one allows before you configure anything, what the docs publish, and where the boundary does not reach. ## AWS Security Reference Architecture: A deep dive into PCI DSS compliance DevFeed: [AWS Security Reference Architecture: A deep dive into PCI DSS compliance]() Original publisher: [Read original article]() Author: Avik Mukherjee Published: 2026-09-14T17:46:56Z Content type: article Language: en Sources: [AWS Security Blog]() Topics: [Amazon Web Services](), [Security](), [Architecture & Design](), [Network Segmentation](), [Encryption](), [Logging](), [Access Control](), [Cloud]() Tags: [access-control](), [amazon-web-services](), [announcements](), [architecture](), [compliance](), [encryption](), [foundational-100](), [logging](), [network-segmentation](), [pci-dss](), [security](), [security-blog](), [security-identity-compliance]() ### AI overview AWS announces the AWS Security Reference Architecture (AWS SRA) PCI DSS Deep Dive, a guide that extends the core AWS SRA with prescriptive architecture-level guidance for organizations handling cardholder data on AWS. It explains how AWS SRA patterns address PCI DSS concerns including account scoping, network segmentation, encryption, logging, and access control. ### Source excerpt Amazon Web Services (AWS) is excited to announce the publication of the AWS Security Reference Architecture (AWS SRA) Payment Card Industry (PCI) Data Security Standard (DSS) Deep Dive. This new guide extends the core AWS SRA to provide prescriptive, architecture-level guidance for organizations that store, process, or transmit cardholder data on AWS. Organizations subject to [...] ## KCP: How to Migrate to Confluent Cloud in Days, Not Weeks DevFeed: [KCP: How to Migrate to Confluent Cloud in Days, Not Weeks]() Original publisher: [Read original article]() Author: Ahmed Saef Zamzam Published: 2026-09-14T07:00:00Z Content type: tutorial Language: en Sources: [Confluent: Data in motion]() Topics: [Kafka](), [migration](), [Confluent Cloud](), [Replication](), [Infrastructure as code](), [Provisioning](), [Access Control](), [Structured-data]() Tags: [access-control](), [confluent](), [confluent-cloud](), [data-replication](), [infrastructure-as-code-iac](), [kafka](), [migration](), [open-source](), [provisioning](), [replication](), [schema]() ### AI overview The article explains how Confluent's open source KCP tool automates migration from Amazon MSK to Confluent Cloud. KCP supports discovery, infrastructure provisioning, ACL and schema mapping, and migration, while Cluster Linking provides offset-preserving data replication. Support for self-managed Kafka migrations is described as coming soon. ### Source excerpt Use Kafka Copy Paste (KCP) to automate Kafka migration with infrastructure generation, ACL and schema mapping, and offset-preserving data replication. ## 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. ## Who can use which model? Teams, Catalogs, and the two-step everybody expects to be one DevFeed: [Who can use which model? Teams, Catalogs, and the two-step everybody expects to be one]() Original publisher: [Read original article]() Author: Hal Tyk's tutorial bot Published: 2026-09-08T11:07:00Z Content type: tutorial Language: en Sources: [Tyk API Management]() Topics: [Tutorial](), [Authorization](), [Language models]() Tags: [access-control](), [ai](), [ai-gateway](), [ai-studio](), [api-management](), [api-platform-teams](), [article](), [developer](), [governance](), [llm](), [llm-governance](), [tutorial](), [uncategorized]() ### AI overview This tutorial explains how to govern which users can access language models and other resources in Tyk AI Studio. It distinguishes catalogs, which determine what users can see, from privacy levels, which determine what they may combine, and highlights that new users may inherit broad access through the Default team. ### Source excerpt Hello. I'm Hal, Tyk's tutorial bot, and today's assignment is a slightly different sort of thing. Every other article in this series governs requests -- which models may be called, what may be sent to them, what it costs. This one governs people. By the end, one person in this organisation will be able to [...] The post Who can use which model? Teams, Catalogs, and the two-step everybody expects to be one appeared first on Tyk API Management. ## Video Streaming Technology: Protocols, Codecs, CDNs, and 2026 Trends DevFeed: [Video Streaming Technology: Protocols, Codecs, CDNs, and 2026 Trends]() Original publisher: [Read original article]() Author: Jon Whitehead Published: 2026-09-08T01:00:42Z Content type: tutorial Language: en Sources: [DaCast]() Topics: [Streaming](), [5G](), [Artificial Intelligence](), [Low Latency](), [real-time](), [WebRTC](), [Virtual reality]() Tags: [access-control](), [ai](), [cdn](), [encryption](), [guide](), [latency](), [low-latency](), [streaming](), [technology](), [the-video-experts-blog](), [video](), [video-streaming]() ### AI overview This guide explains how video streaming works, covering data encoding, delivery through content delivery networks, decoding by video players, streaming protocols, codecs, and security. It also discusses AI-driven tools, low-latency streaming, 5G, edge computing, virtual reality, and business applications in 2026. ### Source excerpt By Dacast Editorial Team | Reviewed by Jon Whitehead, COO at Dacast | Updated September 2026 Video streaming technology has revolutionized the way businesses and individuals share and consume content. Whether it's live streaming a product launch, hosting virtual events, delivering training sessions, or providing entertainment through on-demand video services, streaming technology is now an [...] The post The Definitive Guide to Video Streaming Technology in 2026 appeared first on Dacast. ## OpenAI GPT-6 Astra Hits GA in Microsoft Foundry: Computer Use, Agentic Execution, and $10 to $75 per Million Tokens DevFeed: [OpenAI GPT-6 Astra Hits GA in Microsoft Foundry: Computer Use, Agentic Execution, and $10 to $75 per Million Tokens]() Original publisher: [Read original article]() Author: Harold Fritts Published: 2026-09-05T17:09:34Z Content type: news Language: en Sources: [StorageReview.com]() Topics: [Microsoft](), [OpenAI](), [computer-use](), [Azure](), [Generative AI](), [Frontier Model](), [Security](), [Authorization](), [cloud-infrastructure](), [Software Engineering](), [pull-requests](), [dashboards]() Tags: [access-control](), [agentic](), [ai](), [apis](), [azure](), [computer-use](), [enterprise](), [frontier-model](), [generative-ai](), [governance](), [microsoft](), [openai](), [pull-requests](), [security]() ### AI overview Microsoft announced the general availability of OpenAI GPT-6 Astra in Microsoft Foundry on Azure. The frontier model is intended to support autonomous agentic workflows through multi-step planning, decision support, cross-application tool execution, and computer use. It can operate approved software interfaces, generate structured business artifacts, and assist with software engineering, dashboard creation, record updates, form processing, and interface testing. Microsoft Foundry provides scoped credentials, role-based access control, human-approval checkpoints, and identity controls for containment. ### Source excerpt Microsoft announced the general availability of GPT-6 Astra within Microsoft Foundry on Azure. The frontier model is engineered to transition enterprise generative AI from interactive chat interfaces toward autonomous agentic workflows, providing multi-step planning, deliberate decision support, and cross-application tool execution. OpenAI calls Astra its most aligned model to date, and Microsoft says it is The post OpenAI GPT-6 Astra Hits GA in Microsoft Foundry: Computer Use, Agentic Execution, and $10 to $75 per Million Tokens appeared first on StorageReview.com. ## How Identity Federation Empowers Partner API Strategy DevFeed: [How Identity Federation Empowers Partner API Strategy]() Original publisher: [Read original article]() Author: Kristopher Sandoval Published: 2026-09-01T07:00:00Z Content type: article Language: en Sources: [Nordic APIs]() Topics: [API](), [Security](), [Authorization]() Tags: [access-control](), [api](), [api-governance](), [api-integration](), [api-security](), [api-strategy](), [authentication](), [authorization](), [b2b](), [blog](), [governance](), [identity](), [identity-control](), [security](), [strategy]() ### AI overview The article explains how business-to-business identity federation can strengthen partner API security, access control, governance, and identity lifecycle management. It discusses the risks and integration complexity enterprises face when connecting with many partners. ### Source excerpt Business identity is a complex issue rife with risks across the board. Large enterprises often require deep, flexible integrations with dozens or hundreds of partners, but this comes with significant risk -- between the potential for information leakage, concerns around replays or data usage for continued insecure access, and the sheer friction of such a ... ## Mintlify introduces instant rollbacks for Enterprise deployments DevFeed: [Mintlify introduces instant rollbacks for Enterprise deployments]() Original publisher: [Read original article]() Author: David Isquick Published: 2026-08-31T00:00:00Z Content type: release Language: en Sources: [Mintlify Blog]() Topics: [Deployment](), [audit](), [Pull Request](), [GitHub](), [GitLab](), [bitbucket]() Tags: [access-control](), [announcements](), [audit](), [configuration](), [deployment](), [pull-request](), [rollback]() ### AI overview Mintlify has introduced instant rollbacks for Enterprise customers, allowing them to restore one of their last 10 successful builds from the dashboard in seconds. Rollbacks are recorded in audit logs and currently support non-authenticated pages. ### Source excerpt Instant rollbacks are now live for Mintlify Enterprise customers. You can roll back to a known good deployment in seconds, without waiting on a full rebuild. ## Curating queues beats approving actions DevFeed: [Curating queues beats approving actions]() Original publisher: [Read original article]() Author: WorkOS Published: 2026-08-27T14:28:13Z Content type: opinion Language: en Sources: [WorkOS Blog]() Topics: [Authorization](), [Access Control](), [Security]() Tags: [access-control](), [agent](), [permission](), [queue](), [security]() ### AI overview This opinion article argues that continuous agents make one-action-at-a-time permission prompts impractical. For reversible work, it proposes generating a surplus of candidates, placing them in a queue, and having a human select which work to pursue. ### Source excerpt The permission prompt breaks down once an agent works continuously. What replaces it is curation: a surplus of candidates, a queue, and a human who picks. ## State divergence enables unauthorized access DevFeed: [State divergence enables unauthorized access]() Original publisher: [Read original article]() Author: "Paweł Płatek"; "Denys Pakizh" Published: 2026-08-25T11:00:00Z Content type: article Language: en Sources: [The Trail of Bits Blog](), [The Trail of Bits Blog]() Topics: [bug](), [Blockchain](), [Authorization](), [Transactions](), [SDKs]() Tags: [2026](), [access-control](), [audits](), [authorization](), [blockchain](), [bug](), [financial-services](), [module](), [tokens](), [transactions](), [vulnerabilities]() ### AI overview The article describes a Provenance Blockchain authorization bug that allowed users to grant themselves admin control over marker accounts without holding tokens. The flaw affected non-fixed-supply markers because the access check read a stale zero-valued supply field instead of the live circulating supply. The issue was mitigated in v1.28.0 and fixed in v1.29.0. ### Source excerpt We found and reported a bug in Provenance Blockchain, a public proof-of-stake chain built on Cosmos SDK, that lets any user grant themselves admin control over marker accounts without holding a single token. Provenance covers a range of financial services, including on-chain tokenized loans, private equity tokens, bridged assets, and asset registries. Our bug affected 82 markers representing live financial assets on mainnet. We found the bug, which affects versions before 1.28.0, in March 2026, and reported it to Provenance on April 1. It was mitigated in PR #2627 (commit c81fd65), which shipped in v1.28.0 on May 1, 2026, and fixed in PR #2734, which shipped in v1.29.0 on June 8, 2026. What is a marker? The marker module is Provenance's core primitive for fungible tokens. Chain participants can issue a new asset on Provenance by submitting a MsgAddMarkerRequest transaction; the chain creates a dedicated account for that asset, called a marker. Each marker is a special account type that controls: A denomination (e.g., uusd.trading, cusd.deposit, cguaranteedrateomni) An access control list governing who can mint, burn, withdraw, deposit, or administer the token A supply field recording the canonical token count An escrow balance (the marker account can hold any asset, not just its own denomination) Markers are either supply_fixed (the supply field is enforced as a hard cap) or non-fixed (the bank module is the source of truth; the supply field is informational). This distinction is central to the bug. The bug: An access check anyone can pass AddAccess is the Cosmos SDK message handler that processes requests to modify a marker's access control list. It checks whether the caller is authorized using three conditions, any one of which is sufficient: The caller is the marker's designated manager and the marker is in Finalized state. The caller already holds ACCESS_ADMIN on the marker. The caller controls 100% of the marker's circulating supply. case types.StatusFinalized, ## Access control for AI agents on Rails: gating SQL with Action Policy DevFeed: [Access control for AI agents on Rails: gating SQL with Action Policy]() Original publisher: [Read original article]() Author: Travis Turner (richardturner@evilmartians.com) Published: 2026-08-25T00:00:00Z Content type: tutorial Language: en Sources: [Evil Martians]() Topics: [Access Control](), [Authorization](), [Rails](), [SQL](), [agent observability]() Tags: [access-control](), [agents](), [ai](), [ai-agents](), [llms](), [open-source](), [prompt-injection](), [rails](), [ruby](), [sql]() ### AI overview This article explains how Evil Martians protected sensitive data in an internal Rails AI assistant that uses open-ended SQL analytics. It describes moving authorization from prompts into Action Policy so read-only database access also respects which rows and fields an employee may reveal. ### Source excerpt Our Rails AI assistant had read-only SQL access and could still return peer review scores. Learn how we kept open-ended analytics in an in-app AI assistant while making database access honor application permissions. ## Fine-Grained Access Control Now Available for All Heroku Customers DevFeed: [Fine-Grained Access Control Now Available for All Heroku Customers]() Original publisher: [Read original article]() Author: Alberto Sigismondi Published: 2026-08-21T17:07:29Z Content type: release Language: en Sources: [Heroku]() Topics: [Heroku](), [Access Control](), [Security](), [IAM](), [Zero Trust](), [legacy]() Tags: [access-control](), [deploy](), [heroku](), [iam](), [identity-and-access-management](), [least-privilege](), [legacy](), [news](), [permissions](), [pipelines](), [security](), [security-compliance](), [zero-trust]() ### AI overview Heroku announces that Fine-Grained Access Control is available to all customers. The feature replaces fixed legacy roles with capability-based roles and app-specific permissions for roles such as view, deploy, operate, and manage. ### Source excerpt Fine-Grained Access Controls is now available to all Heroku customers. Heroku's legacy system gave you predefined roles like admin, member, or collaborator, each with a fixed bundle of permissions. It replaces that system with fine-grained roles like view, deploy, operate, and manage, with specific capability sets. Access control is managed at an app-specific layer, giving [...] The post Fine-Grained Access Control Now Available for All Heroku Customers appeared first on Heroku. ## Amazon EKS is replacing the deprecated aws-auth ConfigMap for IAM-to-cluster permission mapping DevFeed: [Amazon EKS is replacing the deprecated aws-auth ConfigMap for IAM-to-cluster permission mapping]() Original publisher: [Read original article]() Author: Yannick Struyf Published: 2026-08-19T18:59:54Z Content type: article Language: en Sources: [Kubernetes Overview, News and Trends | The New Stack]() Topics: [Amazon EKS](), [Kubernetes](), [AWS IAM](), [Access Control](), [Amazon Web Services](), [Cloud](), [migration]() Tags: [access-control](), [amazon-eks](), [aws](), [cloud](), [cloud-native](), [deprecated](), [iam](), [kubernetes](), [migration](), [nutanix](), [platform-engineering](), [post](), [report](), [security](), [sponsor-nutanix](), [sponsored](), [sponsored-post]() ### AI overview The article examines security challenges in Kubernetes and cloud-native infrastructure, focusing on Amazon EKS's replacement of the deprecated aws-auth ConfigMap with an API-driven method for mapping IAM identities to cluster permissions. It also explains how Kubernetes security spans code, containers, clusters, and cloud infrastructure. ### Source excerpt The migration to Kubernetes and cloud native infrastructure has been one of the defining IT trends of the past decade. The post AWS deprecated this EKS auth method. 81% of clusters still run it. appeared first on The New Stack. ## Propagate user authorization context in AI agents with Amazon Bedrock AgentCore DevFeed: [Propagate user authorization context in AI agents with Amazon Bedrock AgentCore]() Original publisher: [Read original article]() Author: Anshu Bathla Published: 2026-08-19T17:24:15Z Content type: article Language: en Sources: [AWS Security Blog]() Topics: [Amazon Bedrock AgentCore](), [AI Agent](), [Authorization](), [AWS Identity and Access Management (IAM)](), [Amazon Bedrock Knowledge Bases](), [Amazon DynamoDB](), [Amazon S3](), [prompt injection](), [Amazon Web Services](), [Software as a service]() Tags: [access-control](), [advanced-300](), [ai-agents](), [amazon-bedrock](), [amazon-bedrock-agentcore](), [amazon-bedrock-knowledge-bases](), [amazon-dynamodb](), [amazon-s3](), [artificial-intelligence](), [authorization](), [aws](), [prompt-injection](), [security-blog](), [security-identity-compliance](), [technical-how-to]() ### AI overview This article explains how to propagate user authorization context through AI agents built with Amazon Bedrock AgentCore. It presents a pattern for enforcing least-privilege access in downstream data services and infrastructure, so agents can access DynamoDB, Bedrock Knowledge Bases, S3-backed documents, and other sources only within the requesting user's permissions. ### Source excerpt Many teams now deploy AI agents that pull from Amazon DynamoDB tables, document repositories, software as a service (SaaS) platforms, and internal knowledge bases to answer questions and automate workflows. A key risk in these deployments is that the agent has no awareness of who's asking, so it might return data the user shouldn't see. [...] ## Flare now uses OAuth for MCP, the CLI, and API DevFeed: [Flare now uses OAuth for MCP, the CLI, and API]() Original publisher: [Read original article]() Author: Freek Van der Herten (freek@spatie.be) Published: 2026-08-15T10:30:29Z Content type: release Language: en Sources: [freek.dev - all blogposts]() Topics: [Model Context Protocol](), [OAuth](), [Access Control](), [API](), [Command-line interface]() Tags: [access-control](), [api](), [authentication](), [cli](), [flare](), [mcp](), [oauth](), [security]() ### AI overview Flare now uses OAuth to connect MCP clients, its CLI, and its API with scoped permissions rather than broad long-lived tokens. The flow supports read-only and project-level access control and centralizes connection management. ### Source excerpt We explain how Flare now uses OAuth to connect MCP clients, the CLI, and the API with scoped permissions instead of broad long-lived tokens. The new flow makes setup faster, adds read-only and project-level access control, and gives you one place to manage every connection. Read more ## How to Prevent RBAC Role Explosion with Nested Access Lists DevFeed: [How to Prevent RBAC Role Explosion with Nested Access Lists]() Original publisher: [Read original article]() Author: info@goteleport.com (Paul Curtis) Published: 2026-08-13T00:00:00Z Content type: tutorial Language: en Sources: [Teleport]() Topics: [Access Control](), [Authorization](), [Development]() Tags: [access-control](), [development](), [how-to](), [permissions](), [teams]() ### AI overview This tutorial explains RBAC role explosion, how repeated role changes create inflexible and duplicated roles, and how nested access lists can apply inherited permissions while keeping roles fixed. ### Source excerpt Learn how to use access lists to prevent RBAC role explosion. ## netlab 26.08: ArcOS, VPP (FD.io), ACLs, and DNS DevFeed: [netlab 26.08: ArcOS, VPP (FD.io), ACLs, and DNS]() Original publisher: [Read original article]() Published: 2026-08-10T09:58:00Z Content type: release Language: en Sources: [ipSpace.net blog]() Topics: [Release notes](), [networking](), [Containers](), [configuration](), [Routing (disambiguation)](), [Authorization]() Tags: [access-control](), [configuration](), [dns](), [getting-started](), [github](), [gre](), [installation](), [ipv4](), [ipv6](), [netlab](), [podman](), [release](), [release-notes](), [routing]() ### AI overview netlab 26.08 adds ArcOS support, VPP with FRR or BIRD control planes, SONiC containers, IPv4/IPv6 access control lists, DNS client and server configuration, GRE and WireGuard tunnel support, and Podman support for the clab provider. The article also notes bug fixes, configuration-template changes, upgrade guidance, and documentation for new users. ### Source excerpt netlab release 26.08 brings a few humongous additions: ArcOS support by @roc-ops VPP (FD.io) with FRR or BIRD control plane by @jbemmel SONiC containers (also by @roc-ops) IPv4/IPv6 access control lists in the routing module by @DanPartelly But wait, there's more: Read more ... ## The day RBAC stops scaling: role explosion and what comes after DevFeed: [The day RBAC stops scaling: role explosion and what comes after]() Original publisher: [Read original article]() Author: WorkOS Published: 2026-08-06T00:18:10Z Content type: article Language: en Sources: [WorkOS Blog]() Topics: [Authorization](), [Access Control](), [Graphs]() Tags: [access-control](), [authorization](), [graph]() ### AI overview The article explains how per-resource permissions cause role explosion in growing B2B applications. It describes the operational and cognitive costs of increasingly complex RBAC models and presents Zanzibar's relationship-based graph model as an alternative. ### Source excerpt Role-based access control breaks when roles outnumber users. Why per-resource permissions cause role explosion, and how to move past it without a rewrite. [Next page]()