# rbac

Role-based access control (RBAC) is a security mechanism that mediates resource access through organizational roles.

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

## Security advisory permissions are now generally available

DevFeed: [Security advisory permissions are now generally available](<https://devfeed.tech/articles/security-advisory-permissions-are-now-generally-available-146994.md>)

Original publisher: [Read original article](<https://github.blog/changelog/2026-11-20-security-advisory-permissions-are-now-generally-available>)

Author: Allison

Published: 2026-11-20T21:49:29Z

Content type: release

Language: en

Sources: [GitHub Changelog](<https://devfeed.tech/sources/github-changelog.md>)

Topics: [rbac](<https://devfeed.tech/topics/rbac.md>), [Security](<https://devfeed.tech/topics/security.md>), [GitHub](<https://devfeed.tech/topics/github.md>)

Tags: [enterprise-management-tools](<https://devfeed.tech/tags/enterprise-management-tools.md>), [github](<https://devfeed.tech/tags/github.md>), [github-enterprise-cloud](<https://devfeed.tech/tags/github-enterprise-cloud.md>), [improvement](<https://devfeed.tech/tags/improvement.md>), [organization](<https://devfeed.tech/tags/organization.md>), [permissions](<https://devfeed.tech/tags/permissions.md>), [private](<https://devfeed.tech/tags/private.md>), [repositories](<https://devfeed.tech/tags/repositories.md>), [repository](<https://devfeed.tech/tags/repository.md>), [roles](<https://devfeed.tech/tags/roles.md>), [security](<https://devfeed.tech/tags/security.md>), [security-advisories](<https://devfeed.tech/tags/security-advisories.md>), [security-advisory](<https://devfeed.tech/tags/security-advisory.md>), [supply-chain-security](<https://devfeed.tech/tags/supply-chain-security.md>), [vulnerability-reports](<https://devfeed.tech/tags/vulnerability-reports.md>)

### AI overview

Organization owners can grant repository-scoped access to security advisories and private vulnerability reports through four new custom-role permissions, without making users repository administrators or organization-wide security managers. "View" grants access to draft advisories, status, and comments; "Create, Edit, and Manage" adds advisory editing, collaboration management, comments, and temporary private fork creation. Accepting private reports or closing and reopening advisories, and publishing advisories or requesting CVEs, each require either View or Create, Edit, and Manage. The permissions apply only to assigned repositories. Merging changes from a temporary private fork still requires an administrator or security manager, and permission holders cannot delete such forks. Confidential comments require Create, Edit, and Manage plus repository write access. Availability depends on a plan that supports custom repository roles.

### Source excerpt

Organization owners can now let people work on repository security advisories, including private vulnerability reports, through custom repository roles. You no longer have to make them repository administrators or give... The post Security advisory permissions are now generally available appeared first on The GitHub Blog.

## CVE-2026-133874 - Iceburg CRM through 5.0.0 Authorization Bypass via Record Save

DevFeed: [CVE-2026-133874 - Iceburg CRM through 5.0.0 Authorization Bypass via Record Save](<https://devfeed.tech/articles/cve-2026-133874-iceburg-crm-through-5-0-0-authorization-bypass-via-record-save-146411.md>)

Original publisher: [Read original article](<https://cvefeed.io/vuln/detail/CVE-2026-133874>)

Author: CVEFEED.io; vulncheck.com

Published: 2026-11-20T17:18:24Z

Content type: article

Language: en

Sources: [Latest High/Critical Vulnerabilitiy Feed](<https://devfeed.tech/sources/latest-high-critical-vulnerabilitiy-feed.md>)

Topics: [Authorization](<https://devfeed.tech/topics/authorization.md>), [Access Control](<https://devfeed.tech/topics/access-control.md>), [rbac](<https://devfeed.tech/topics/rbac.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [admin](<https://devfeed.tech/tags/admin.md>), [authorization](<https://devfeed.tech/tags/authorization.md>), [bypass](<https://devfeed.tech/tags/bypass.md>), [crm](<https://devfeed.tech/tags/crm.md>), [cve](<https://devfeed.tech/tags/cve.md>), [cve-2026-133874](<https://devfeed.tech/tags/cve-2026-133874.md>), [iceburgcrm](<https://devfeed.tech/tags/iceburgcrm.md>), [save](<https://devfeed.tech/tags/save.md>)

### AI overview

Iceburg CRM through version 5.0.0 has an authorization flaw in Module::saveRecord() that can let authenticated users write to modules they are not authorized to access. The excerpt says an attacker with write access to one module can prefix request body keys with another module's ID and send a crafted POST to /data/save or PUT to /api/crm/{id}; this may allow setting their role_id to Admin and accessing administrative data. The listed severity is 8.6 (High).

### Source excerpt

CVE ID :CVE-2026-133874 Published : Nov. 20, 2026, 5:18 p.m. | 18 minutes ago Description :Iceburg CRM through 5.0.0 contains an incorrect authorization vulnerability in Module::saveRecord() that allows authenticated users to write to unauthorized modules by prefixing request body keys with another module id. Attackers with write access to one module can submit crafted requests to POST /data/save or PUT /api/crm/{id} to set their role_id to Admin and access administrative data. Severity: 8.6 | HIGH Visit the link for more details, such as CVSS details, affected products, timeline, and more...

## ASUS warns of critical hard-coded key flaw in Control Center Express

DevFeed: [ASUS warns of critical hard-coded key flaw in Control Center Express](<https://devfeed.tech/articles/asus-warns-of-critical-hard-coded-key-flaw-in-control-center-express-144371.md>)

Original publisher: [Read original article](<https://www.bleepingcomputer.com/news/security/asus-warns-of-critical-hard-coded-key-flaw-in-control-center-express/>)

Author: Bill Toulas

Published: 2026-11-19T21:15:59Z

Content type: news

Language: en

Sources: [BleepingComputer](<https://devfeed.tech/sources/bleepingcomputer.md>)

Topics: [ASUS](<https://devfeed.tech/topics/asus.md>), [hardcoded credentials](<https://devfeed.tech/topics/hardcoded-credentials.md>), [Access Control](<https://devfeed.tech/topics/access-control.md>), [Authentication](<https://devfeed.tech/topics/authentication.md>), [rbac](<https://devfeed.tech/topics/rbac.md>)

Tags: [administrator](<https://devfeed.tech/tags/administrator.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [armoury-crate](<https://devfeed.tech/tags/armoury-crate.md>), [asus](<https://devfeed.tech/tags/asus.md>), [authorization](<https://devfeed.tech/tags/authorization.md>), [business](<https://devfeed.tech/tags/business.md>), [central](<https://devfeed.tech/tags/central.md>), [computer-help](<https://devfeed.tech/tags/computer-help.md>), [computer-security](<https://devfeed.tech/tags/computer-security.md>), [computers](<https://devfeed.tech/tags/computers.md>), [control-center-express](<https://devfeed.tech/tags/control-center-express.md>), [critical](<https://devfeed.tech/tags/critical.md>), [critical-vulnerabilities](<https://devfeed.tech/tags/critical-vulnerabilities.md>), [cryptographic](<https://devfeed.tech/tags/cryptographic.md>), [cve](<https://devfeed.tech/tags/cve.md>), [cve-2026-112115](<https://devfeed.tech/tags/cve-2026-112115.md>), [cve-2026-114202](<https://devfeed.tech/tags/cve-2026-114202.md>), [devices](<https://devfeed.tech/tags/devices.md>), [hardcoded-key](<https://devfeed.tech/tags/hardcoded-key.md>), [infosec](<https://devfeed.tech/tags/infosec.md>), [infosec-computer-security](<https://devfeed.tech/tags/infosec-computer-security.md>), [it](<https://devfeed.tech/tags/it.md>), [linux](<https://devfeed.tech/tags/linux.md>), [mac](<https://devfeed.tech/tags/mac.md>), [malware](<https://devfeed.tech/tags/malware.md>), [malware-removal](<https://devfeed.tech/tags/malware-removal.md>), [management](<https://devfeed.tech/tags/management.md>), [remote](<https://devfeed.tech/tags/remote.md>), [remote-monitoring-and-management](<https://devfeed.tech/tags/remote-monitoring-and-management.md>), [security](<https://devfeed.tech/tags/security.md>), [spyware](<https://devfeed.tech/tags/spyware.md>), [support](<https://devfeed.tech/tags/support.md>), [tech-support](<https://devfeed.tech/tags/tech-support.md>), [technical-support](<https://devfeed.tech/tags/technical-support.md>), [virus](<https://devfeed.tech/tags/virus.md>), [virus-removal](<https://devfeed.tech/tags/virus-removal.md>), [vulnerabilities](<https://devfeed.tech/tags/vulnerabilities.md>), [vulnerability](<https://devfeed.tech/tags/vulnerability.md>), [windows](<https://devfeed.tech/tags/windows.md>)

### AI overview

ASUS Control Center Express v1.7.29 fixes three critical flaws that could enable administrative control of the management console or managed devices. CVE-2026-114202 (CVSS 10.0) is the most severe: an unauthenticated remote attacker can forge an authentication token and gain administrator privileges without user interaction. CVE-2026-114204 requires low privileges and a recently logged-in account; CVE-2026-114205 requires a low-privileged account to create an administrator account. ASUS says versions before v1.7.29 are affected, while CVE records list versions through v1.7.27, leaving v1.7.28 unclear. ASUS advises installing v1.7.29, updating managed-device agents through Select Function -> Client Agent Updater, and verifying their versions.

### Source excerpt

ASUS released Control Center Express v1.7.29 to fix three critical vulnerabilities that could let remote attackers gain administrative control of the management console and the devices it manages. [...]

## CVE-2026-132229 - Hypershift-addon: hypershift-addon: overly permissive clusterrolebinding allows any authenticated user to modify and delete managed clusters

DevFeed: [CVE-2026-132229 - Hypershift-addon: hypershift-addon: overly permissive clusterrolebinding allows any authenticated user to modify and delete managed clusters](<https://devfeed.tech/articles/cve-2026-132229-hypershift-addon-hypershift-addon-overly-permissive-clusterrolebinding-allows-any-authenticated-user-to-modify-and-delete-managed-clusters-141026.md>)

Original publisher: [Read original article](<https://cvefeed.io/vuln/detail/CVE-2026-132229>)

Author: CVEFEED.io; redhat.com

Published: 2026-11-18T18:19:15Z

Content type: news

Language: en

Sources: [Latest High/Critical Vulnerabilitiy Feed](<https://devfeed.tech/sources/latest-high-critical-vulnerabilitiy-feed.md>)

Topics: [rbac](<https://devfeed.tech/topics/rbac.md>), [Access Control](<https://devfeed.tech/topics/access-control.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [access-control](<https://devfeed.tech/tags/access-control.md>), [addon](<https://devfeed.tech/tags/addon.md>), [all](<https://devfeed.tech/tags/all.md>), [alter](<https://devfeed.tech/tags/alter.md>), [authorization](<https://devfeed.tech/tags/authorization.md>), [can](<https://devfeed.tech/tags/can.md>), [cluster](<https://devfeed.tech/tags/cluster.md>), [clusters](<https://devfeed.tech/tags/clusters.md>), [configuration](<https://devfeed.tech/tags/configuration.md>), [cve](<https://devfeed.tech/tags/cve.md>), [cve-2026-132229](<https://devfeed.tech/tags/cve-2026-132229.md>), [delete](<https://devfeed.tech/tags/delete.md>), [managed](<https://devfeed.tech/tags/managed.md>), [multicluster-engine](<https://devfeed.tech/tags/multicluster-engine.md>), [multicluster-engine-for-kubernetes](<https://devfeed.tech/tags/multicluster-engine-for-kubernetes.md>), [permissions](<https://devfeed.tech/tags/permissions.md>), [rbac](<https://devfeed.tech/tags/rbac.md>), [redhat](<https://devfeed.tech/tags/redhat.md>), [role-based-access-control](<https://devfeed.tech/tags/role-based-access-control.md>), [service](<https://devfeed.tech/tags/service.md>), [user](<https://devfeed.tech/tags/user.md>), [users](<https://devfeed.tech/tags/users.md>)

### AI overview

CVE-2026-132229 is an RBAC authorization flaw in hypershift-addon, rated 8.1 (HIGH). The cluster role binding grants access to all authenticated users instead of limiting permissions to the addon service. As a result, a low-privileged authenticated user can view, modify, or delete managed cluster resources, potentially disrupting clusters across the managed fleet. The supplied excerpt does not identify affected versions or provide remediation steps.

### Source excerpt

CVE ID :CVE-2026-132229 Published : Nov. 18, 2026, 6:19 p.m. | 31 minutes ago Description :A flaw was found in hypershift-addon. Due to an overly permissive role-based access control (RBAC) configuration that grants permissions to all authenticated users rather than restricting them to the addon service, a low-privileged authenticated user can view, modify, or delete managed cluster resources. This improper authorization allows unauthorized users to alter or disrupt clusters across the entire managed fleet. Severity: 8.1 | HIGH Visit the link for more details, such as CVSS details, affected products, timeline, and more...

## Announcing Role-based Access Control

DevFeed: [Announcing Role-based Access Control](<https://devfeed.tech/articles/announcing-role-based-access-control-141887.md>)

Original publisher: [Read original article](<https://www.port.io/blog/announcing-role-based-access-control>)

Author: Dudi Elhadad

Published: 2026-11-18T06:28:07Z

Content type: article

Language: en

Sources: [Port](<https://devfeed.tech/sources/developer-experience-platform-engineering-blog-port.md>)

Topics: [rbac](<https://devfeed.tech/topics/rbac.md>), [Access Control](<https://devfeed.tech/topics/access-control.md>), [internal developer platform](<https://devfeed.tech/topics/internal-developer-platform.md>), [least privilege](<https://devfeed.tech/topics/least-privilege.md>)

Tags: [access-control](<https://devfeed.tech/tags/access-control.md>), [ai-software-factory](<https://devfeed.tech/tags/ai-software-factory.md>), [anthropic](<https://devfeed.tech/tags/anthropic.md>), [asset](<https://devfeed.tech/tags/asset.md>), [audit-log](<https://devfeed.tech/tags/audit-log.md>), [backstage](<https://devfeed.tech/tags/backstage.md>), [bucket](<https://devfeed.tech/tags/bucket.md>), [catalog](<https://devfeed.tech/tags/catalog.md>), [ci-cd-pipelines](<https://devfeed.tech/tags/ci-cd-pipelines.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [data](<https://devfeed.tech/tags/data.md>), [data-engineer](<https://devfeed.tech/tags/data-engineer.md>), [databases](<https://devfeed.tech/tags/databases.md>), [developer-experience](<https://devfeed.tech/tags/developer-experience.md>), [developer-portal](<https://devfeed.tech/tags/developer-portal.md>), [devops](<https://devfeed.tech/tags/devops.md>), [enterprise](<https://devfeed.tech/tags/enterprise.md>), [environments](<https://devfeed.tech/tags/environments.md>), [groups](<https://devfeed.tech/tags/groups.md>), [internal-developer-platform](<https://devfeed.tech/tags/internal-developer-platform.md>), [product-news](<https://devfeed.tech/tags/product-news.md>), [role-based-access-control](<https://devfeed.tech/tags/role-based-access-control.md>)

### AI overview

Port describes a no-code RBAC approach that combines users and teams inherited from an SSO provider with teams created by administrators when needed. Admins can do anything; moderators can operate on specific asset types and related entities; users have read-only access and/or permission to run selected actions. Read and write permissions can be set by user or team, down to an asset type or property. Policies can control who runs self-service actions, require manual approval, limit action frequency, and tailor input fields by user. Port also describes ownership-aware access and an audit log covering entity changes, self-service actions, status, and machine interactions. The excerpt does not provide implementation steps.

### Source excerpt

Controlling authorizations is at the center of a good internal developer platform implementation. Read more here.

## Improved governance for your docs: reviews and expanded roles

DevFeed: [Improved governance for your docs: reviews and expanded roles](<https://devfeed.tech/articles/improved-governance-for-your-docs-reviews-and-expanded-roles-141885.md>)

Original publisher: [Read original article](<https://www.mintlify.com/blog/improved-governance>)

Author: David Isquick

Published: 2026-11-18T00:00:00Z

Content type: release

Language: en

Sources: [Mintlify Blog](<https://devfeed.tech/sources/mintlify-blog.md>)

Topics: [rbac](<https://devfeed.tech/topics/rbac.md>), [branch protection rules](<https://devfeed.tech/topics/branch-protection-rules.md>), [Pull Request](<https://devfeed.tech/topics/pull-request.md>), [Claude](<https://devfeed.tech/topics/claude.md>)

Tags: [announcements](<https://devfeed.tech/tags/announcements.md>), [docs](<https://devfeed.tech/tags/docs.md>), [editor](<https://devfeed.tech/tags/editor.md>), [enterprise](<https://devfeed.tech/tags/enterprise.md>), [governance](<https://devfeed.tech/tags/governance.md>), [live](<https://devfeed.tech/tags/live.md>), [review](<https://devfeed.tech/tags/review.md>), [reviews](<https://devfeed.tech/tags/reviews.md>), [roles](<https://devfeed.tech/tags/roles.md>)

### AI overview

Mintlify Enterprise adds editor-based review and expanded roles for controlling who can write, approve, and publish. Teams can keep reviewing through GitHub pull requests or request reviews in Mintlify, where reviewers inspect a diff and approve; only a publisher or admin can then publish. Requiring review disables auto publish. Admins can set approval counts and require reapproval after edits. On GitHub deployment branches with branch protection, reviews move to a branch, publishing requires review, and a reviewer with a connected GitHub account also approves the pull request; GitHub merge checks still apply. Without branch protection, admins can publish their own changes without review. New built-in roles include owner, publisher, and commenter; owners and admins can create custom roles, and roles can differ by site. Review requirements are in beta, require a GitHub docs repo, and are available on Enterprise; GitLab and Bitbucket support is in development.

### Source excerpt

Mintlify Enterprise now has stronger governance built into the editor. Require a review before any change goes live, and use expanded roles to control who can write, approve, and publish.

## CVE-2026-69187 - WeGIA: Authenticated Privilege Escalation due to Missing Action-level Authorisation

DevFeed: [CVE-2026-69187 - WeGIA: Authenticated Privilege Escalation due to Missing Action-level Authorisation](<https://devfeed.tech/articles/cve-2026-69187-wegia-authenticated-privilege-escalation-due-to-missing-action-level-authorisation-138620.md>)

Original publisher: [Read original article](<https://cvefeed.io/vuln/detail/CVE-2026-69187>)

Author: CVEFEED.io; github.com

Published: 2026-11-17T22:19:21Z

Content type: news

Language: en

Sources: [Latest High/Critical Vulnerabilitiy Feed](<https://devfeed.tech/sources/latest-high-critical-vulnerabilitiy-feed.md>)

Topics: [permission](<https://devfeed.tech/topics/permission.md>), [rbac](<https://devfeed.tech/topics/rbac.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [cve](<https://devfeed.tech/tags/cve.md>), [cve-2026-69187](<https://devfeed.tech/tags/cve-2026-69187.md>), [labredescefetrj](<https://devfeed.tech/tags/labredescefetrj.md>), [privilege-escalation](<https://devfeed.tech/tags/privilege-escalation.md>), [wegia](<https://devfeed.tech/tags/wegia.md>)

### AI overview

Before WeGIA 3.9.1, authorization for FuncionarioControle requests checked only whether an authenticated employee had a permission row for resource 11 or 91; MiddlewareDAO::verificarPermissao() did not validate id_acao or authorize the requested method. With any such permission and a valid CSRF token from their own session, an employee could add, alter, or delete permissions for arbitrary roles. This could grant higher action levels, expose or modify sensitive data, or disrupt access. The issue is fixed in version 3.9.1.

### Source excerpt

CVE ID :CVE-2026-69187 Published : Nov. 17, 2026, 10:19 p.m. | 1 hour, 9 minutes ago Description :WeGIA is a web manager for charitable institutions. Prior to 3.9.1, web/controle/control.php authorizes FuncionarioControle requests only by checking whether an authenticated employee has a permission row for resource 11 or 91, while MiddlewareDAO::verificarPermissao() does not compare the stored id_acao value or authorize the requested method. An employee with any such permission and a valid CSRF token from the employee's own session can invoke FuncionarioControle::adicionarPermissao, FuncionarioControle::alterarPermissao, or FuncionarioControle::excluirPermissao to add, change, or remove permissions for arbitrary roles. This can grant higher action levels over sensitive resources, expose or modify protected employee, patient, configuration, and administrative data, or disrupt legitimate access by changing other roles. This issue is fixed in version 3.9.1. Severity: 8.8 | HIGH Visit the link for more details, such as CVSS details, affected products, timeline, and more...

## AI agent security guide: controls for coding agents, MCP and Kubernetes agents

DevFeed: [AI agent security guide: controls for coding agents, MCP and Kubernetes agents](<https://devfeed.tech/articles/ai-agent-security-guide-controls-for-coding-agents-mcp-and-kubernetes-agents-135243.md>)

Original publisher: [Read original article](<https://nirmata.com/2026/11/17/ai-agent-security-guide/>)

Author: Ritesh Patel

Published: 2026-11-16T12:00:48.928398Z

Content type: article

Language: en

Sources: [Nirmata](<https://devfeed.tech/sources/nirmata.md>)

Topics: [AI Agent](<https://devfeed.tech/topics/ai-agent.md>), [Claude Code](<https://devfeed.tech/topics/claude-code.md>), [rbac](<https://devfeed.tech/topics/rbac.md>), [Kyverno](<https://devfeed.tech/topics/kyverno.md>), [Access Control](<https://devfeed.tech/topics/access-control.md>), [Threat monitoring](<https://devfeed.tech/topics/threat-monitoring.md>)

Tags: [admission](<https://devfeed.tech/tags/admission.md>), [agent](<https://devfeed.tech/tags/agent.md>), [agent-security](<https://devfeed.tech/tags/agent-security.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agent](<https://devfeed.tech/tags/ai-agent.md>), [ai-agent-security](<https://devfeed.tech/tags/ai-agent-security.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [ai-governance](<https://devfeed.tech/tags/ai-governance.md>), [coding](<https://devfeed.tech/tags/coding.md>), [coding-agents](<https://devfeed.tech/tags/coding-agents.md>), [control](<https://devfeed.tech/tags/control.md>), [controls](<https://devfeed.tech/tags/controls.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [layer](<https://devfeed.tech/tags/layer.md>), [mcp](<https://devfeed.tech/tags/mcp.md>), [mcp-servers](<https://devfeed.tech/tags/mcp-servers.md>), [rbac](<https://devfeed.tech/tags/rbac.md>), [security](<https://devfeed.tech/tags/security.md>), [servers](<https://devfeed.tech/tags/servers.md>), [settings](<https://devfeed.tech/tags/settings.md>), [threat](<https://devfeed.tech/tags/threat.md>)

### AI overview

AI agent security relies on controls at three enforcement points: developer-machine coding agent settings, MCP servers and gateways, and Kubernetes admission and RBAC. On developer machines, combine permission rules, shell sandboxing, hooks, managed settings, and per-developer credentials; each covers different risks. Claude Code checks deny, then ask, then allow; a hook exit code 2 can block before those rules, but cannot remove a deny. Bash rules may miss alternate command forms, requiring hooks or sandboxing. For MCP, approve servers and tools individually, classify tools, and apply server-side input validation, access controls, rate limits, output sanitization, and logging; clients should prompt for sensitive operations and log usage. Give each agent a revocable identity with least privilege; Kubernetes RBAC has no deny rules, so begin with an empty role and grant explicitly. Admission policies such as Kyverno can reject noncompliant pods before persistence, while runtime tool calls need separate controls. Audit agent actions and policy decisions across the machine, MCP, and cluster. AIControls capabilities stated here include gateway routing for Claude Code, per-user tokens,;

### Source excerpt

Map each AI agent threat to the control that stops it and the layer that enforces it: coding agent settings, MCP servers, Kubernetes admission and RBAC.

## One Identity Unveils Active Roles 8.6 with Enhanced Security and Administration

DevFeed: [One Identity Unveils Active Roles 8.6 with Enhanced Security and Administration](<https://devfeed.tech/articles/one-identity-unveils-active-roles-8-6-with-enhanced-security-and-administration-127824.md>)

Original publisher: [Read original article](<https://www.cio.com/article/4247172/one-identity-unveils-active-roles-8-6-with-enhanced-security-and-administration-2.html>)

Author: CIO

Published: 2026-11-11T04:44:23Z

Content type: release

Language: en

Sources: [CIO](<https://devfeed.tech/sources/cio.md>)

Topics: [active directory](<https://devfeed.tech/topics/active-directory.md>), [identity and access management](<https://devfeed.tech/topics/identity-and-access-management.md>), [REST API](<https://devfeed.tech/topics/rest-api.md>), [saml](<https://devfeed.tech/topics/saml.md>), [rbac](<https://devfeed.tech/topics/rbac.md>), [Entra ID](<https://devfeed.tech/topics/entra-id.md>), [microsoft 365](<https://devfeed.tech/topics/microsoft-365.md>), [PowerShell](<https://devfeed.tech/topics/powershell.md>)

Tags: [active-directory](<https://devfeed.tech/tags/active-directory.md>), [administration](<https://devfeed.tech/tags/administration.md>), [administrator](<https://devfeed.tech/tags/administrator.md>), [api](<https://devfeed.tech/tags/api.md>), [api-access](<https://devfeed.tech/tags/api-access.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [capabilities](<https://devfeed.tech/tags/capabilities.md>), [console](<https://devfeed.tech/tags/console.md>), [edition-us](<https://devfeed.tech/tags/edition-us.md>), [entra-id](<https://devfeed.tech/tags/entra-id.md>), [flexible](<https://devfeed.tech/tags/flexible.md>), [identity](<https://devfeed.tech/tags/identity.md>), [integration](<https://devfeed.tech/tags/integration.md>), [interface](<https://devfeed.tech/tags/interface.md>), [language-en](<https://devfeed.tech/tags/language-en.md>), [management](<https://devfeed.tech/tags/management.md>), [microsoft](<https://devfeed.tech/tags/microsoft.md>), [microsoft-365](<https://devfeed.tech/tags/microsoft-365.md>), [powershell](<https://devfeed.tech/tags/powershell.md>), [rest-api](<https://devfeed.tech/tags/rest-api.md>), [roles](<https://devfeed.tech/tags/roles.md>), [security](<https://devfeed.tech/tags/security.md>), [storytype-press-release](<https://devfeed.tech/tags/storytype-press-release.md>)

### AI overview

Active Roles 8.6 combines a fix for an RSTS configuration security issue with cumulative features, enhancements and resolved issues from the intervening releases after 8.2.1 SP6, superseding versions 8.3, 8.4 and 8.5. The cumulative release line adds the Active Roles REST API and Redistributable Secure Token Server capabilities for API access and SAML 2.0 federated authentication. The excerpt characterizes the change as an administration and integration upgrade, not a visual redesign. It describes a configurable thick-client UI modeled on Microsoft Active Directory, one console for Active Directory, Microsoft Entra ID and Microsoft 365, and support for PowerShell and VBScript. PeerSpot figures and rankings are also reported, based on 92 reviews.

### Source excerpt

Active Roles 8.6: Cumulative security, feature and administration upgrades One Identity has introduced Active Roles 8.6, strengthening secure and streamlined Active Directory administration with cumulative platform improvements, expanded API capabilities and greater authentication flexibility. Active Roles 8.6, updated July 27, 2026, focuses on security and cumulative platform improvements. It fixes an RSTS configuration security issue and supersedes versions 8.3, 8.4 and 8.5. Compared with Active Roles 8.2.1 SP6, One Identity says 8.6 incorporates the features, enhancements and resolved issues delivered across that intervening release line. See the Active Roles 8.6 Release Notes. The recent improvements are therefore best described as an administrator and integration experience upgrade, rather than a new visual redesign. The cumulative release line adds capabilities including the Active Roles REST API, as well as Redistributable Secure Token Server capabilities supporting API access and SAML 2.0 federated authentication. Active Roles 8.6: Familiar Administration Meets Greater Flexibility and Consolidation Those upgrades complement one of Active Roles' most recognizable usability strengths: a flexible, configurable UI that can be tailored to individual users and personas. Its thick-client interface is designed to resemble the familiar Microsoft Active Directory experience, helping reduce the learning curve for experienced AD administrators. The broader experience centers on consolidation, with a single console spanning Active Directory, Microsoft Entra ID and Microsoft 365 helping administrators avoid constantly switching between separate management environments. Together with PowerShell and VBScript support, the product keeps familiar tools and interaction patterns at the center of the administrator experience. This combination of configurable views, familiar administration and centralized control supports Active Roles' position among top Active Directory managemen

## One Identity Unveils Active Roles 8.6 with Enhanced Security and Administration

DevFeed: [One Identity Unveils Active Roles 8.6 with Enhanced Security and Administration](<https://devfeed.tech/articles/one-identity-unveils-active-roles-8-6-with-enhanced-security-and-administration-127612.md>)

Original publisher: [Read original article](<https://hackernoon.com/one-identity-unveils-active-roles-86-with-enhanced-security-and-administration?source=rss>)

Author: CyberNewswire

Published: 2026-11-10T19:33:39Z

Content type: release

Language: en

Sources: [HackerNoon](<https://devfeed.tech/sources/hackernoon.md>)

Topics: [active directory](<https://devfeed.tech/topics/active-directory.md>), [rbac](<https://devfeed.tech/topics/rbac.md>), [saml](<https://devfeed.tech/topics/saml.md>), [Security](<https://devfeed.tech/topics/security.md>)

Tags: [access-control](<https://devfeed.tech/tags/access-control.md>), [access-management](<https://devfeed.tech/tags/access-management.md>), [account-management](<https://devfeed.tech/tags/account-management.md>), [active-directory](<https://devfeed.tech/tags/active-directory.md>), [administration](<https://devfeed.tech/tags/administration.md>), [api](<https://devfeed.tech/tags/api.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [automated-user-provisioning](<https://devfeed.tech/tags/automated-user-provisioning.md>), [cyber-attack](<https://devfeed.tech/tags/cyber-attack.md>), [cyber-security-awareness](<https://devfeed.tech/tags/cyber-security-awareness.md>), [cyber-threats](<https://devfeed.tech/tags/cyber-threats.md>), [cybercrime](<https://devfeed.tech/tags/cybercrime.md>), [cybersecurity](<https://devfeed.tech/tags/cybersecurity.md>), [cybersecurity-awareness](<https://devfeed.tech/tags/cybersecurity-awareness.md>), [cybersecurity-tips](<https://devfeed.tech/tags/cybersecurity-tips.md>), [entra-id](<https://devfeed.tech/tags/entra-id.md>), [good-company](<https://devfeed.tech/tags/good-company.md>), [highlights](<https://devfeed.tech/tags/highlights.md>), [hybrid](<https://devfeed.tech/tags/hybrid.md>), [identity](<https://devfeed.tech/tags/identity.md>), [identity-governance-and-administration](<https://devfeed.tech/tags/identity-governance-and-administration.md>), [identity-security](<https://devfeed.tech/tags/identity-security.md>), [roles](<https://devfeed.tech/tags/roles.md>), [security](<https://devfeed.tech/tags/security.md>)

### AI overview

Active Roles 8.6 is a cumulative security and administration update that fixes an RSTS configuration security issue and supersedes versions 8.3, 8.4 and 8.5. One Identity says it includes changes delivered since 8.2.1 SP6, including the Active Roles REST API and Redistributable Secure Token Server capabilities for API access and SAML 2.0 federation. The product pairs these updates with a configurable thick-client interface modeled on the familiar Active Directory experience and a single console for Active Directory, Microsoft Entra ID and Microsoft 365, alongside PowerShell and VBScript support. The supplied press release excerpt reports PeerSpot's #1 category ranking and 8.5/10 rating based on 92 reviews; it does not provide independent technical validation.

### Source excerpt

Active Roles 8.6, updated July 27, 2026, focuses on security and cumulative platform improvements. It fixes an RSTS configuration security issue and supersedes

## One Identity Unveils Active Roles 8.6 with Enhanced Security and Administration

DevFeed: [One Identity Unveils Active Roles 8.6 with Enhanced Security and Administration](<https://devfeed.tech/articles/one-identity-unveils-active-roles-8-6-with-enhanced-security-and-administration-127002.md>)

Original publisher: [Read original article](<https://www.techrepublic.com/article/one-identity-unveils-active-roles-8-6-with-enhanced-security-and-administration/>)

Author: CyberNewsWire

Published: 2026-11-10T15:38:31Z

Content type: release

Language: en

Sources: [TechRepublic](<https://devfeed.tech/sources/techrepublic.md>)

Topics: [active directory](<https://devfeed.tech/topics/active-directory.md>), [identity and access management](<https://devfeed.tech/topics/identity-and-access-management.md>), [Entra ID](<https://devfeed.tech/topics/entra-id.md>), [Authentication](<https://devfeed.tech/topics/authentication.md>), [rbac](<https://devfeed.tech/topics/rbac.md>), [Single sign-on (SSO)](<https://devfeed.tech/topics/sso.md>), [Security](<https://devfeed.tech/topics/security.md>)

Tags: [access-control](<https://devfeed.tech/tags/access-control.md>), [access-management](<https://devfeed.tech/tags/access-management.md>), [active-directory](<https://devfeed.tech/tags/active-directory.md>), [administration](<https://devfeed.tech/tags/administration.md>), [api](<https://devfeed.tech/tags/api.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [identity](<https://devfeed.tech/tags/identity.md>), [press-release](<https://devfeed.tech/tags/press-release.md>), [roles](<https://devfeed.tech/tags/roles.md>), [security](<https://devfeed.tech/tags/security.md>)

### AI overview

Active Roles 8.6 fixes an RSTS configuration security issue and includes the features, enhancements and resolved issues from versions 8.3-8.5, superseding those releases. One Identity describes the update as a cumulative administrator and integration upgrade, not a visual redesign. The release line adds a REST API and Redistributable Secure Token Server capabilities for API access and SAML 2.0 federated authentication. The product also offers a configurable thick-client UI modeled on the familiar Active Directory experience, a console spanning Active Directory, Microsoft Entra ID and Microsoft 365, and PowerShell and VBScript support. The supplied text does not detail individual API changes or compare 8.6 with other products.

### Source excerpt

One Identity has introduced Active Roles 8.6, strengthening secure and streamlined Active Directory administration with cumulative platform improvements, expanded API capabilities and greater authentication flexibility. The post One Identity Unveils Active Roles 8.6 with Enhanced Security and Administration appeared first on TechRepublic.

## Self-Service Namespace Onboarding on Amazon EKS: Automating Access Entries and RBAC with GitHub...

DevFeed: [Self-Service Namespace Onboarding on Amazon EKS: Automating Access Entries and RBAC with GitHub...](<https://devfeed.tech/articles/self-service-namespace-onboarding-on-amazon-eks-automating-access-entries-and-rbac-with-github-127576.md>)

Original publisher: [Read original article](<https://blog.devops.dev/self-service-namespace-onboarding-on-amazon-eks-automating-access-entries-and-rbac-with-github-74f0347e71e2?source=rss----33f8b2d9a328---4>)

Author: Oleh Adam Dubnytskyy

Published: 2026-11-10T09:42:12Z

Content type: tutorial

Language: en

Sources: [DevOps.dev](<https://devfeed.tech/sources/devops-dev.md>)

Topics: [rbac](<https://devfeed.tech/topics/rbac.md>), [Amazon Elastic Kubernetes Service](<https://devfeed.tech/topics/amazon-elastic-kubernetes-service.md>), [Access Control](<https://devfeed.tech/topics/access-control.md>), [Authorization](<https://devfeed.tech/topics/authorization.md>), [GitHub Actions](<https://devfeed.tech/topics/github-actions.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [AWS Security Token Service](<https://devfeed.tech/topics/aws-security-token-service.md>), [AWS IAM](<https://devfeed.tech/topics/aws-iam.md>), [self-service](<https://devfeed.tech/topics/self-service.md>), [internal developer platform automation](<https://devfeed.tech/topics/internal-developer-platform-automation.md>), [GitHub](<https://devfeed.tech/topics/github.md>)

Tags: [admin](<https://devfeed.tech/tags/admin.md>), [amazon-eks](<https://devfeed.tech/tags/amazon-eks.md>), [amazon-web-services](<https://devfeed.tech/tags/amazon-web-services.md>), [api](<https://devfeed.tech/tags/api.md>), [api-server](<https://devfeed.tech/tags/api-server.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [authorization](<https://devfeed.tech/tags/authorization.md>), [automation](<https://devfeed.tech/tags/automation.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-eks](<https://devfeed.tech/tags/aws-eks.md>), [ci](<https://devfeed.tech/tags/ci.md>), [cluster](<https://devfeed.tech/tags/cluster.md>), [credentials](<https://devfeed.tech/tags/credentials.md>), [devops](<https://devfeed.tech/tags/devops.md>), [eks](<https://devfeed.tech/tags/eks.md>), [github](<https://devfeed.tech/tags/github.md>), [github-actions](<https://devfeed.tech/tags/github-actions.md>), [iam](<https://devfeed.tech/tags/iam.md>), [job](<https://devfeed.tech/tags/job.md>), [keys](<https://devfeed.tech/tags/keys.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [onboarding](<https://devfeed.tech/tags/onboarding.md>), [rbac](<https://devfeed.tech/tags/rbac.md>), [self-service](<https://devfeed.tech/tags/self-service.md>)

### AI overview

The excerpt describes namespace onboarding on Amazon EKS as two coordinated permission updates: an EKS access policy scope and Kubernetes RBAC. GitHub Actions authenticates through OIDC and temporary IAM role credentials. The EKS authorizer and RBAC authorizer can each allow a request, so effective permissions are their union; a restrictive custom RBAC role cannot narrow permissions already granted by a broader managed policy. The proposed setup uses separate workflows: one applies ClusterRoles and per-namespace RoleBindings, while another updates the access entry's namespace scope from files in a namespaces directory. The scripts validate namespace names, reject empty desired scopes, skip unchanged access-policy updates, and optionally prune stale managed RoleBindings. The excerpt notes that RBAC synchronization requires cluster-scoped rights and that missing namespaces are skipped with a warning before the workflow reports an error. The supplied text ends after describing this implementation and its pull request workflow.

### Source excerpt

Self-Service Namespace Onboarding on Amazon EKS: Automating Access Entries and RBAC with GitHub ActionsTwo authorization layers on Amazon EKS Every call my pipeline makes to the cluster's Kubernetes API server passes through two authorizers: Kubernetes RBAC and EKS access policies. Authentication: the access entry says who you are The pipeline never holds long-lived AWS keys. A GitHub Actions job gets an OIDC token, exchanges it for temporary credentials of an IAM role, and calls the cluster with them. More details on how it works can be seen here. Layer 1: Kubernetes RBAC RBAC is the standard Kubernetes model: Roles and ClusterRoles define rules, and RoleBindings attach them to a user or group. These objects live inside the cluster. You can write any rule you need, including rules for custom resources such as KEDA ScaledObject. Layer 2: EKS access policies Access policies are permission sets that AWS manages and that you attach to an access entry through the EKS API. They mirror the Kubernetes user-facing roles: AmazonEKSEditPolicy corresponds to edit, AmazonEKSAdminPolicy to admin, and so on. Each association has a scope: the whole cluster (type=cluster) or a list of namespaces (type=namespace). You can't modify an access policy or create your own. When the managed policies don't fit, more control can be configured by leveraging Kubernetes RBAC objects instead. How the two layers combine The API server chains its authorizers. The RBAC authorizer runs first and returns immediately if it allows the request. If RBAC has no opinion, the request goes to the EKS authorizer, which checks the access policies. If neither allows it, the request is denied. The access entry only establishes who the caller is; RBAC and access policies each get one chance to allow the request. Both authorizers can only allow or pass, so the effective permissions of ci-github-actions in a namespace are the union of both layers. That has two consequences for the automation: Onboarding a namespace

## PRISM: Causal Counterfactual Minimization of Agent Tool Privileges via Information Bottleneck Role Induction

DevFeed: [PRISM: Causal Counterfactual Minimization of Agent Tool Privileges via Information Bottleneck Role Induction](<https://devfeed.tech/articles/prism-causal-counterfactual-minimization-of-agent-tool-privileges-via-information-bottleneck-role-induction-125408.md>)

Original publisher: [Read original article](<https://arxiv.org/abs/2611.11539>)

Author: Yang Luo, Qingni Shen, Tairui Wang, Jiajun Li, Zhonghai Wu

Published: 2026-11-10T05:00:00Z

Content type: article

Language: en

Sources: [arXiv: Artificial Intelligence](<https://devfeed.tech/sources/arxiv-artificial-intelligence.md>), [arXiv: Cryptography and Security](<https://devfeed.tech/sources/arxiv-cryptography-and-security.md>), [arXiv: Machine Learning](<https://devfeed.tech/sources/arxiv-machine-learning.md>)

Topics: [rbac](<https://devfeed.tech/topics/rbac.md>), [Access Control](<https://devfeed.tech/topics/access-control.md>), [causality](<https://devfeed.tech/topics/causality.md>), [Machine learning](<https://devfeed.tech/topics/machine-learning.md>), [Representation learning](<https://devfeed.tech/topics/representation-learning.md>), [Large Language Model](<https://devfeed.tech/topics/llm.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [agents](<https://devfeed.tech/tags/agents.md>), [authorization](<https://devfeed.tech/tags/authorization.md>), [bench](<https://devfeed.tech/tags/bench.md>), [benchmarks](<https://devfeed.tech/tags/benchmarks.md>), [blast-radius](<https://devfeed.tech/tags/blast-radius.md>), [cs-ai](<https://devfeed.tech/tags/cs-ai.md>), [cs-cr](<https://devfeed.tech/tags/cs-cr.md>), [cs-lg](<https://devfeed.tech/tags/cs-lg.md>), [flow](<https://devfeed.tech/tags/flow.md>), [generative](<https://devfeed.tech/tags/generative.md>), [induction](<https://devfeed.tech/tags/induction.md>), [language-model](<https://devfeed.tech/tags/language-model.md>), [large-language-model](<https://devfeed.tech/tags/large-language-model.md>), [llm](<https://devfeed.tech/tags/llm.md>), [llm-agents](<https://devfeed.tech/tags/llm-agents.md>), [mcp](<https://devfeed.tech/tags/mcp.md>), [model](<https://devfeed.tech/tags/model.md>), [model-context-protocol-mcp](<https://devfeed.tech/tags/model-context-protocol-mcp.md>), [pruning](<https://devfeed.tech/tags/pruning.md>), [roles](<https://devfeed.tech/tags/roles.md>), [sandbox](<https://devfeed.tech/tags/sandbox.md>), [tool](<https://devfeed.tech/tags/tool.md>)

### AI overview

PRISM aims to reduce over-authorization of LLM agents with Model Context Protocol (MCP) tools by learning which tools are causally necessary for each task. It uses structured interventions in a sandbox to estimate counterfactual necessity, compresses task trajectories into discrete roles with an information bottleneck, selects the role count from the rate-distortion curve, and frames privilege pruning as a bilevel Stackelberg game whose candidate solutions are sampled by a generative flow network. Across AgentDojo, τ-bench and ToolEmu, the paper reports 78.3% fewer authorized tools per role, 78.2% task success, 88.7% counterfactual necessity accuracy and a 15.9% blast radius.

### Source excerpt

arXiv:2611.11539v1 Announce Type: cross Abstract: This paper shifts the object of role engineering from human users to large language model (LLM) agents, and proposes PRISM to address the over-authorization that arises when an agent obtains full tool privileges through the Model Context Protocol (MCP). PRISM formulates whether a tool is necessary for a task as an intervenable causal proposition, and applies structured interventions in a sandbox to learn a counterfactual necessity model. It then compresses trajectories into discrete latent variables through an information bottleneck, and determines the number of roles from the knee of the rate-distortion curve. Finally, it formalizes pruning as a bilevel Stackelberg game, in which a generative flow network samples diverse near-optimal solutions. On three public benchmarks, AgentDojo, $\tau$-bench and ToolEmu, PRISM compresses the number of authorized tools per role by 78.3%, attains a task success rate of 78.2%, reaches a counterfactual necessity accuracy of 88.7%, and lowers the blast radius to 15.9%.

## Taxbit Assist: A grounded, role-aware AI agent on Amazon Bedrock AgentCore

DevFeed: [Taxbit Assist: A grounded, role-aware AI agent on Amazon Bedrock AgentCore](<https://devfeed.tech/articles/taxbit-assist-a-grounded-role-aware-ai-agent-on-amazon-bedrock-agentcore-121746.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/machine-learning/taxbit-assist-a-grounded-role-aware-ai-agent-on-amazon-bedrock-agentcore/>)

Author: Karan Nayak

Published: 2026-11-06T16:49:42Z

Content type: article

Language: en

Sources: [Artificial Intelligence](<https://devfeed.tech/sources/artificial-intelligence.md>)

Topics: [Amazon Bedrock AgentCore](<https://devfeed.tech/topics/amazon-bedrock-agentcore.md>), [Amazon Bedrock Knowledge Bases](<https://devfeed.tech/topics/amazon-bedrock-knowledge-bases.md>), [AI Agent](<https://devfeed.tech/topics/ai-agent.md>), [AI Chat](<https://devfeed.tech/topics/ai-chat.md>), [rbac](<https://devfeed.tech/topics/rbac.md>), [knowledge-engineering](<https://devfeed.tech/topics/knowledge-engineering.md>), [Amazon CloudWatch](<https://devfeed.tech/topics/amazon-cloudwatch.md>), [Amazon S3](<https://devfeed.tech/topics/amazon-s3.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [Documentation](<https://devfeed.tech/topics/documentation.md>), [Amazon EventBridge](<https://devfeed.tech/topics/amazon-eventbridge.md>), [AI for customer service automation](<https://devfeed.tech/topics/ai-for-customer-service-automation.md>)

Tags: [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [agent](<https://devfeed.tech/tags/agent.md>), [agentcore-runtime](<https://devfeed.tech/tags/agentcore-runtime.md>), [agents-sdk](<https://devfeed.tech/tags/agents-sdk.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agent](<https://devfeed.tech/tags/ai-agent.md>), [ai-assistant](<https://devfeed.tech/tags/ai-assistant.md>), [amazon-bedrock](<https://devfeed.tech/tags/amazon-bedrock.md>), [amazon-bedrock-agentcore](<https://devfeed.tech/tags/amazon-bedrock-agentcore.md>), [amazon-bedrock-guardrails](<https://devfeed.tech/tags/amazon-bedrock-guardrails.md>), [amazon-bedrock-knowledge-bases](<https://devfeed.tech/tags/amazon-bedrock-knowledge-bases.md>), [amazon-cloudwatch](<https://devfeed.tech/tags/amazon-cloudwatch.md>), [amazon-eventbridge](<https://devfeed.tech/tags/amazon-eventbridge.md>), [amazon-s3](<https://devfeed.tech/tags/amazon-s3.md>), [amazon-simple-storage-service-amazon-s3](<https://devfeed.tech/tags/amazon-simple-storage-service-amazon-s3.md>), [customer-solutions](<https://devfeed.tech/tags/customer-solutions.md>), [knowledge-base](<https://devfeed.tech/tags/knowledge-base.md>), [permission](<https://devfeed.tech/tags/permission.md>), [production](<https://devfeed.tech/tags/production.md>), [quality](<https://devfeed.tech/tags/quality.md>), [region](<https://devfeed.tech/tags/region.md>), [safety](<https://devfeed.tech/tags/safety.md>)

### AI overview

Taxbit built a cited, permission-aware assistant inside its dashboard using Strands Agents SDK on Amazon Bedrock AgentCore. It grounds answers in a curated knowledge base combining published help and API content, product documentation generated from source code, and approved corrections. Semantic chunking adds each document's title and scope to passages; retrieval over-fetches and reranks candidates, while code enforces which sources can be cited. The model checks feature and role access before suggesting workflows, but identity comes from the authenticated service and is bound to tools; AgentCore isolates sessions. Guardrails screen each incoming turn, masking formatted tax identifiers and blocking secrets. EU and US deployments use geography-aware inference. Production traces feed automated evaluations and expert review, with approved corrections incrementally ingested. Taxbit reports over 55% of users who ask a question return within 24 hours, and average model cost below 20 cents per conversation. The assistant currently uses product knowledge and cannot read customer tax data.

### Source excerpt

Taxbit built Taxbit Assist, a cited, permission-aware AI assistant embedded in its enterprise dashboard, on Amazon Bedrock AgentCore. This post shows how they grounded answers in a curated knowledge base, enforced role-aware and region-compliant safety, and continuously measured answer quality on live production traffic.

## 6 Best Platforms for LLM Access Control in Enterprise

DevFeed: [6 Best Platforms for LLM Access Control in Enterprise](<https://devfeed.tech/articles/6-best-platforms-for-llm-access-control-in-enterprise-120980.md>)

Original publisher: [Read original article](<https://www.lyzr.ai/blog/best-platforms-for-llm-access-control-in-enterprise/>)

Author: Lyzr Team

Published: 2026-11-06T11:01:57Z

Content type: comparison

Language: en

Sources: [Lyzr.ai](<https://devfeed.tech/sources/lyzr-ai.md>)

Topics: [Access Control](<https://devfeed.tech/topics/access-control.md>), [LLM security](<https://devfeed.tech/topics/llm-security.md>), [rbac](<https://devfeed.tech/topics/rbac.md>), [enterprise data protection](<https://devfeed.tech/topics/enterprise-data-protection.md>), [Large Language Model](<https://devfeed.tech/topics/llm.md>), [AWS IAM](<https://devfeed.tech/topics/aws-iam.md>), [databricks](<https://devfeed.tech/topics/databricks.md>), [okta](<https://devfeed.tech/topics/okta.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [access-control](<https://devfeed.tech/tags/access-control.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [best](<https://devfeed.tech/tags/best.md>), [enterprise](<https://devfeed.tech/tags/enterprise.md>), [llm](<https://devfeed.tech/tags/llm.md>), [platforms](<https://devfeed.tech/tags/platforms.md>), [snowflake](<https://devfeed.tech/tags/snowflake.md>)

### AI overview

Enterprise LLM access control must identify the caller, permitted model and region, data allowed for the call, and usage budget--and ensure every call passes through enforcement. The excerpt compares six platforms: Lyzr OpenController applies shared policies across providers, self-hosted models, and agents, but only to traffic routed through its gateways. Bedrock uses IAM, SCPs, and guardrails, with many models enabled by default; Microsoft Foundry uses Azure Policy to restrict deployments, not each request. Google's organization policy controls Model Garden actions but is not per-user and allows all models when unset. Databricks governs model APIs through Unity Catalog grants and rate limits, while Snowflake grants Cortex model access through application roles. These native controls are platform-specific. The excerpt recommends default-deny allowlists alongside role-based access and warns that calls bypassing the enforcement point, such as an agent using its own provider key, escape those controls. Snowflake's cited behavior change also illustrates that rules must be checked on every call path.

### Source excerpt

TL;DR This year, Snowflake published a behavior change worth reading. According to Snowflake's release notes for its 2026_02 behavior change bundle, Cortex functions such as...

## Article: Identity as an Architectural Concern: Enterprise IAM Beyond Authentication

DevFeed: [Article: Identity as an Architectural Concern: Enterprise IAM Beyond Authentication](<https://devfeed.tech/articles/article-identity-as-an-architectural-concern-enterprise-iam-beyond-authentication-120951.md>)

Original publisher: [Read original article](<https://www.infoq.com/articles/identity-as-architecture/>)

Author: Vaishnavi Khosla

Published: 2026-11-06T09:00:00Z

Content type: article

Language: en

Sources: [InfoQ](<https://devfeed.tech/sources/infoq.md>)

Topics: [identity and access management](<https://devfeed.tech/topics/identity-and-access-management.md>), [Access Control](<https://devfeed.tech/topics/access-control.md>), [rbac](<https://devfeed.tech/topics/rbac.md>), [HashiCorp Vault](<https://devfeed.tech/topics/hashicorp-vault.md>), [Secure token management](<https://devfeed.tech/topics/secure-token-management.md>), [Single sign-on (SSO)](<https://devfeed.tech/topics/sso.md>), [Publish-subscribe pattern](<https://devfeed.tech/topics/pubsub.md>)

Tags: [account](<https://devfeed.tech/tags/account.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [architecture-design](<https://devfeed.tech/tags/architecture-design.md>), [article](<https://devfeed.tech/tags/article.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [authorization](<https://devfeed.tech/tags/authorization.md>), [based](<https://devfeed.tech/tags/based.md>), [data](<https://devfeed.tech/tags/data.md>), [design](<https://devfeed.tech/tags/design.md>), [development](<https://devfeed.tech/tags/development.md>), [don-t](<https://devfeed.tech/tags/don-t.md>), [enterprise](<https://devfeed.tech/tags/enterprise.md>), [event](<https://devfeed.tech/tags/event.md>), [experience](<https://devfeed.tech/tags/experience.md>), [governance](<https://devfeed.tech/tags/governance.md>), [graph](<https://devfeed.tech/tags/graph.md>), [iam](<https://devfeed.tech/tags/iam.md>), [identity](<https://devfeed.tech/tags/identity.md>), [identity-as-architecture](<https://devfeed.tech/tags/identity-as-architecture.md>), [identity-management](<https://devfeed.tech/tags/identity-management.md>), [java](<https://devfeed.tech/tags/java.md>), [management](<https://devfeed.tech/tags/management.md>), [models](<https://devfeed.tech/tags/models.md>), [oauth](<https://devfeed.tech/tags/oauth.md>), [rbac](<https://devfeed.tech/tags/rbac.md>), [scope](<https://devfeed.tech/tags/scope.md>), [security](<https://devfeed.tech/tags/security.md>), [service](<https://devfeed.tech/tags/service.md>), [single-sign-on](<https://devfeed.tech/tags/single-sign-on.md>), [stream](<https://devfeed.tech/tags/stream.md>)

### AI overview

At enterprise scale, identity design shapes data models, service boundaries, ownership governance, and revocation behavior. The author describes modeling ownership and time-bounded access as relationships in Neo4j, queried through GraphQL; this made common ownership and validity questions direct, though it adds datastore and modeling costs, and the article says flat RBAC remains suitable for small, single-app setups. A unified workflow for attestation, credential rotation, and vaulting reduced reported revocation time from about three days to under one. Because the vault is owned by another team, the integration fails closed and reconciles its state before marking vaulting complete. Across services, scoped OAuth 2.0 token exchange carries identity context while a policy decision point makes authorization decisions. Kafka distributes entitlement changes, so revocation is eventually consistent: consumers invalidate cached decisions, and a maximum cache age bounds stale access if an event is lost, at the cost of more source-of-truth checks when that limit is shorter.

### Source excerpt

The way you design your identities will drive your data models, your service scope, and your revocation policies; enterprise identity management is thus an architectural problem, not an afterthought. Based on our experience in service account governance, this article touches upon graph vs. RBAC, integrating a vault you don't own, and bounding revocation latency for an event stream. By Vaishnavi Khosla

## CVE-2026-88800 - MDJM Event Management and Mobile Events Manager \<= 1.7.8.7 - Unauthenticated Arbitrary Role Deletion

DevFeed: [CVE-2026-88800 - MDJM Event Management and Mobile Events Manager \<= 1.7.8.7 - Unauthenticated Arbitrary Role Deletion](<https://devfeed.tech/articles/cve-2026-88800-mdjm-event-management-and-mobile-events-manager-1-7-8-7-unauthenticated-arbitrary-role-deletion-120890.md>)

Original publisher: [Read original article](<https://cvefeed.io/vuln/detail/CVE-2026-88800>)

Author: CVEFEED.io; wpscan.com

Published: 2026-11-06T08:17:38Z

Content type: article

Language: en

Sources: [Latest High/Critical Vulnerabilitiy Feed](<https://devfeed.tech/sources/latest-high-critical-vulnerabilitiy-feed.md>)

Topics: [WordPress](<https://devfeed.tech/topics/wordpress.md>), [rbac](<https://devfeed.tech/topics/rbac.md>)

Tags: [administrator](<https://devfeed.tech/tags/administrator.md>), [capabilities](<https://devfeed.tech/tags/capabilities.md>), [critical](<https://devfeed.tech/tags/critical.md>), [cve-2026-88800](<https://devfeed.tech/tags/cve-2026-88800.md>), [mobile-events-manager](<https://devfeed.tech/tags/mobile-events-manager.md>), [mobileeventsmanager](<https://devfeed.tech/tags/mobileeventsmanager.md>), [roles](<https://devfeed.tech/tags/roles.md>), [wordpress-plugins](<https://devfeed.tech/tags/wordpress-plugins.md>)

### AI overview

The MDJM Event Management and Mobile Events Manager WordPress plugins through version 1.7.8.7 reportedly process role deletion on every page load without a capability check or nonce. The user-assignment safeguard checks a different request value from the one used to select the role for deletion, allowing unauthenticated attackers to delete any role, including administrator. Deletion permanently removes the affected role's capabilities from every user assigned to it. The source rates the issue 9.1, Critical.

### Source excerpt

CVE ID :CVE-2026-88800 Published : Nov. 6, 2026, 8:17 a.m. | 1 hour, 30 minutes ago Description :The MDJM Event Management and Mobile Events Manager WordPress plugins through 1.7.8.7 act on a role deletion request on every page load with no capability check and no nonce, and the guard meant to protect roles that have users assigned reads a different part of the request from the one that selects what is deleted, allowing unauthenticated attackers to remove any WordPress role including administrator, which permanently strips every user of their capabilities. Severity: 9.1 | CRITICAL Visit the link for more details, such as CVSS details, affected products, timeline, and more...

## Introducing AWS account access manager: IAM role flexibility with centralized workforce access

DevFeed: [Introducing AWS account access manager: IAM role flexibility with centralized workforce access](<https://devfeed.tech/articles/introducing-aws-account-access-manager-iam-role-flexibility-with-centralized-workforce-access-121130.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/security/introducing-aws-account-access-manager-iam-role-flexibility-with-centralized-workforce-access/>)

Author: Moumita Saha

Published: 2026-11-05T19:21:56Z

Content type: release

Language: en

Sources: [AWS Security Blog](<https://devfeed.tech/sources/aws-security-blog.md>)

Topics: [AWS IAM](<https://devfeed.tech/topics/aws-iam.md>), [AWS IAM Identity Center](<https://devfeed.tech/topics/aws-iam-identity-center.md>), [identity and access management](<https://devfeed.tech/topics/identity-and-access-management.md>), [rbac](<https://devfeed.tech/topics/rbac.md>), [Amazon Web Services](<https://devfeed.tech/topics/aws.md>), [Single sign-on (SSO)](<https://devfeed.tech/topics/sso.md>), [okta](<https://devfeed.tech/topics/okta.md>), [AWS CloudTrail](<https://devfeed.tech/topics/aws-cloudtrail.md>), [Duo](<https://devfeed.tech/topics/duo.md>), [Entra ID](<https://devfeed.tech/topics/entra-id.md>)

Tags: [access-control](<https://devfeed.tech/tags/access-control.md>), [access-management](<https://devfeed.tech/tags/access-management.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-cli](<https://devfeed.tech/tags/aws-cli.md>), [aws-cloudformation](<https://devfeed.tech/tags/aws-cloudformation.md>), [aws-cloudtrail](<https://devfeed.tech/tags/aws-cloudtrail.md>), [aws-command-line-interface-aws-cli](<https://devfeed.tech/tags/aws-command-line-interface-aws-cli.md>), [aws-iam](<https://devfeed.tech/tags/aws-iam.md>), [aws-iam-identity-center](<https://devfeed.tech/tags/aws-iam-identity-center.md>), [aws-identity-and-access-management-iam](<https://devfeed.tech/tags/aws-identity-and-access-management-iam.md>), [aws-key-management-service](<https://devfeed.tech/tags/aws-key-management-service.md>), [aws-key-management-service-aws-kms](<https://devfeed.tech/tags/aws-key-management-service-aws-kms.md>), [aws-management-console](<https://devfeed.tech/tags/aws-management-console.md>), [aws-sdk](<https://devfeed.tech/tags/aws-sdk.md>), [aws-tools-for-powershell](<https://devfeed.tech/tags/aws-tools-for-powershell.md>), [best-practices](<https://devfeed.tech/tags/best-practices.md>), [beyondtrust](<https://devfeed.tech/tags/beyondtrust.md>), [iam](<https://devfeed.tech/tags/iam.md>), [iam-identity-center](<https://devfeed.tech/tags/iam-identity-center.md>), [intermediate-200](<https://devfeed.tech/tags/intermediate-200.md>), [security-blog](<https://devfeed.tech/tags/security-blog.md>), [security-identity-compliance](<https://devfeed.tech/tags/security-identity-compliance.md>), [technical-how-to](<https://devfeed.tech/tags/technical-how-to.md>), [workforce](<https://devfeed.tech/tags/workforce.md>)

### AI overview

Account access manager lets an organization assign existing IAM roles in individual AWS accounts to IAM Identity Center users and groups through a centralized federation point, while retaining role-specific trust policies, tags, and paths and adding user-level audit context. Setup requires an organization instance of IAM Identity Center, eligible IAM roles with a trust policy allowing the service, and management-account enablement in the Identity Center primary Region. Administrators create per-user or per-group entitlements; each role assignment is created individually, and the console cannot discover roles, so administrators must know their names. Users can access assigned roles in the portal or obtain CLI credentials with `aws login` (AWS CLI v2.36.0 or newer); IAM Identity Center commands such as `aws sso configure` do not work for these assignments. Role sessions use the underlying role's configured maximum duration, up to 12 hours. The text says the service is available at no additional cost in Commercial Regions except opt-in Regions, and excludes GovCloud (US), China, and other non-commercial Regions.

### Source excerpt

AWS Identity and Access Management (IAM) is introducing account access manager, a flexible new way to manage workforce access to your Amazon Web Services (AWS) accounts. This combines the IAM role flexibility your teams already rely on, delivered through the centralized federation of AWS IAM Identity Center, with user-level visibility built-in. Account access manager streamlines [...]

## RBAC for AI agents in Kubernetes

DevFeed: [RBAC for AI agents in Kubernetes](<https://devfeed.tech/articles/rbac-for-ai-agents-in-kubernetes-121571.md>)

Original publisher: [Read original article](<https://nirmata.com/2026/11/05/rbac-for-ai-agents-in-kubernetes/>)

Author: Ritesh Patel

Published: 2026-11-05T07:00:00Z

Content type: tutorial

Language: en

Sources: [Nirmata](<https://devfeed.tech/sources/nirmata.md>)

Topics: [rbac](<https://devfeed.tech/topics/rbac.md>), [Kyverno](<https://devfeed.tech/topics/kyverno.md>)

Tags: [account](<https://devfeed.tech/tags/account.md>), [admission](<https://devfeed.tech/tags/admission.md>), [agent](<https://devfeed.tech/tags/agent.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agent](<https://devfeed.tech/tags/ai-agent.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [ai-governance](<https://devfeed.tech/tags/ai-governance.md>), [api](<https://devfeed.tech/tags/api.md>), [audit](<https://devfeed.tech/tags/audit.md>), [authorization](<https://devfeed.tech/tags/authorization.md>), [bind](<https://devfeed.tech/tags/bind.md>), [credentials](<https://devfeed.tech/tags/credentials.md>), [delete](<https://devfeed.tech/tags/delete.md>), [development](<https://devfeed.tech/tags/development.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [limit](<https://devfeed.tech/tags/limit.md>), [pod](<https://devfeed.tech/tags/pod.md>), [rbac](<https://devfeed.tech/tags/rbac.md>), [rules](<https://devfeed.tech/tags/rules.md>), [security](<https://devfeed.tech/tags/security.md>), [service](<https://devfeed.tech/tags/service.md>)

### AI overview

Give each AI agent a named Kubernetes service account and grant only the required resources and verbs through a RoleBinding in the agent's namespace. Kubernetes RBAC is additive and has no deny rules; audit both direct bindings and group grants, since broader group permissions can exceed a narrow account binding. Pods that omit `serviceAccountName` use the namespace's `default` account, so a grant to `default` can affect every pod that falls back to it. Disable `automountServiceAccountToken` for agents that never call the API; API-using agents should use short-lived, rotating projected tokens rather than static Secret tokens. RBAC governs Kubernetes API access, while container permissions on the node require separate pod security controls. The excerpt also recommends starting Kyverno enforcement in audit mode before switching to deny.

### Source excerpt

Give each AI agent its own service account, bind it to a narrow Role, and point its pod at that account. RBAC has no deny rules, so grants are the limit.

## Per-workspace roles: Custom roles scoped to a resource type in WorkOS

DevFeed: [Per-workspace roles: Custom roles scoped to a resource type in WorkOS](<https://devfeed.tech/articles/per-workspace-roles-custom-roles-scoped-to-a-resource-type-in-workos-121082.md>)

Original publisher: [Read original article](<https://workos.com/blog/resource-scoped-custom-roles>)

Author: WorkOS

Published: 2026-11-05T00:00:00Z

Content type: article

Language: en

Sources: [WorkOS](<https://devfeed.tech/sources/workos-blog.md>)

Topics: [rbac](<https://devfeed.tech/topics/rbac.md>)

Tags: [custom](<https://devfeed.tech/tags/custom.md>), [organization](<https://devfeed.tech/tags/organization.md>), [resource](<https://devfeed.tech/tags/resource.md>), [roles](<https://devfeed.tech/tags/roles.md>), [type](<https://devfeed.tech/tags/type.md>), [workos](<https://devfeed.tech/tags/workos.md>)

### AI overview

Resource-scoped WorkOS roles let one organization member have different access on individual workspaces or projects, avoiding organization-wide roles for every access combination. Define resource types in the Dashboard, scope permissions and roles to the matching type, assign a role to a membership on a specific resource, and use authorization endpoints to check access; project permissions can inherit through a workspace. Environment roles suit permissions shared across customers, while custom roles belong to one organization. Resource types, role scopes, permission scopes, and slugs are immutable, so correcting a scope requires creating replacements, migrating assignments and application checks, then deleting old entries. The text also notes hierarchy and instance limits, role slug rules, and deletion conflicts while assignments or group mappings remain.

### Source excerpt

Organization roles give a member the same access everywhere. Scope a WorkOS role to a resource type and one person can edit one workspace and view another.

## Introducing identity and access management for Lambda Cloud

DevFeed: [Introducing identity and access management for Lambda Cloud](<https://devfeed.tech/articles/introducing-identity-and-access-management-for-lambda-cloud-118901.md>)

Original publisher: [Read original article](<https://lambda.com/blog/lambda-cloud-iam-rbac>)

Author: Lambda

Published: 2026-11-04T19:45:57Z

Content type: release

Language: en

Sources: [The Lambda deep learning blog](<https://devfeed.tech/sources/the-lambda-deep-learning-blog.md>)

Topics: [identity and access management](<https://devfeed.tech/topics/identity-and-access-management.md>), [rbac](<https://devfeed.tech/topics/rbac.md>), [Access Control](<https://devfeed.tech/topics/access-control.md>)

Tags: [access-control](<https://devfeed.tech/tags/access-control.md>), [access-management](<https://devfeed.tech/tags/access-management.md>), [account](<https://devfeed.tech/tags/account.md>), [admin](<https://devfeed.tech/tags/admin.md>), [api](<https://devfeed.tech/tags/api.md>), [api-key](<https://devfeed.tech/tags/api-key.md>), [api-keys](<https://devfeed.tech/tags/api-keys.md>), [audit](<https://devfeed.tech/tags/audit.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [console](<https://devfeed.tech/tags/console.md>), [gpu](<https://devfeed.tech/tags/gpu.md>), [gpu-cloud](<https://devfeed.tech/tags/gpu-cloud.md>), [groups](<https://devfeed.tech/tags/groups.md>), [iam](<https://devfeed.tech/tags/iam.md>), [identity](<https://devfeed.tech/tags/identity.md>), [identity-and-access-management](<https://devfeed.tech/tags/identity-and-access-management.md>), [lambda](<https://devfeed.tech/tags/lambda.md>), [lambda-cloud](<https://devfeed.tech/tags/lambda-cloud.md>), [product-updates](<https://devfeed.tech/tags/product-updates.md>), [rbac](<https://devfeed.tech/tags/rbac.md>), [role-based-access-control](<https://devfeed.tech/tags/role-based-access-control.md>), [roles](<https://devfeed.tech/tags/roles.md>), [security](<https://devfeed.tech/tags/security.md>), [service-identities](<https://devfeed.tech/tags/service-identities.md>)

### AI overview

Lambda Cloud IAM adds role-based access for users and software, with fine-grained roles at account or workspace scope. Resource actions require both workspace membership and a role that permits the action. Groups can contain users and service identities and pass assigned roles to their members; an effective access view shows direct and inherited roles by workspace. For automation, the article recommends giving scripts their own service identity, granting only needed roles, setting API key expiration, and rotating between its two keys; personal keys remain active until deleted. Only account admins and IAM admins can manage IAM. Existing Admin and Member access maps to Account Admin and Account Member, and current keys are unchanged. Audit logs are retained for six months; accounts can have up to 100 groups and 50 service identities. IAM is free.

### Source excerpt

Role-based access control for your GPU cloud: roles, groups, and service identities are now in the Lambda Cloud console.

## One customer needs a role nobody else has: organization-scoped custom roles

DevFeed: [One customer needs a role nobody else has: organization-scoped custom roles](<https://devfeed.tech/articles/one-customer-needs-a-role-nobody-else-has-organization-scoped-custom-roles-115970.md>)

Original publisher: [Read original article](<https://workos.com/blog/organization-scoped-custom-roles>)

Author: WorkOS

Published: 2026-11-03T14:42:18Z

Content type: tutorial

Language: en

Sources: [WorkOS](<https://devfeed.tech/sources/workos-blog.md>)

Topics: [rbac](<https://devfeed.tech/topics/rbac.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [access-control](<https://devfeed.tech/tags/access-control.md>), [admin](<https://devfeed.tech/tags/admin.md>), [api](<https://devfeed.tech/tags/api.md>), [app](<https://devfeed.tech/tags/app.md>), [application](<https://devfeed.tech/tags/application.md>), [authorization](<https://devfeed.tech/tags/authorization.md>), [b2b](<https://devfeed.tech/tags/b2b.md>), [billing](<https://devfeed.tech/tags/billing.md>), [control](<https://devfeed.tech/tags/control.md>), [custom](<https://devfeed.tech/tags/custom.md>), [customer](<https://devfeed.tech/tags/customer.md>), [customers](<https://devfeed.tech/tags/customers.md>), [dashboard](<https://devfeed.tech/tags/dashboard.md>), [environment](<https://devfeed.tech/tags/environment.md>), [needs](<https://devfeed.tech/tags/needs.md>), [one](<https://devfeed.tech/tags/one.md>), [organization](<https://devfeed.tech/tags/organization.md>), [rest](<https://devfeed.tech/tags/rest.md>), [roles](<https://devfeed.tech/tags/roles.md>)

### AI overview

Organization-scoped custom roles let one WorkOS organization have customer-specific permissions without adding role options for every tenant. Create them on an organization's Roles tab or with POST /authorization/organizations/:organizationId/roles; new roles start without permissions, which must be set separately. Use a deliberate slug if application code depends on it: slugs cannot be changed, and custom slugs are unique within the organization. Creating the first custom role also forks that organization's default role and priority order from the environment's current settings; later environment changes no longer update those settings, so review them on the organization's Roles tab. A custom role cannot be deleted while it has active assignments or identity provider group mappings. Custom and environment roles appear together in the organization's role list and work with existing assignment paths.

### Source excerpt

Environment roles apply to every organization. A custom role belongs to one, so you can give a customer the role they asked for without touching the rest.

## ZT-DAC: ML-Driven Dynamic Access Control Policy for Zero Trust in DER Networks

DevFeed: [ZT-DAC: ML-Driven Dynamic Access Control Policy for Zero Trust in DER Networks](<https://devfeed.tech/articles/zt-dac-ml-driven-dynamic-access-control-policy-for-zero-trust-in-der-networks-114066.md>)

Original publisher: [Read original article](<https://arxiv.org/abs/2611.02107>)

Author: Arun B. Chandrasekaran, Damilola Popoola, Souradeep Bhattacharya, Manimaran Govindarasu

Published: 2026-11-03T05:00:00Z

Content type: article

Language: en

Sources: [arXiv: Artificial Intelligence](<https://devfeed.tech/sources/arxiv-artificial-intelligence.md>), [arXiv: Cryptography and Security](<https://devfeed.tech/sources/arxiv-cryptography-and-security.md>)

Topics: [Access Control](<https://devfeed.tech/topics/access-control.md>), [Zero Trust](<https://devfeed.tech/topics/zero-trust.md>), [Dynamic authorization rules](<https://devfeed.tech/topics/dynamic-authorization-rules.md>), [Machine learning](<https://devfeed.tech/topics/machine-learning.md>), [rbac](<https://devfeed.tech/topics/rbac.md>), [Authorization](<https://devfeed.tech/topics/authorization.md>), [Security](<https://devfeed.tech/topics/security.md>), [Open Policy Agent](<https://devfeed.tech/topics/open-policy-agent.md>), [trust](<https://devfeed.tech/topics/trust.md>), [network security](<https://devfeed.tech/topics/network-security.md>)

Tags: [access-control](<https://devfeed.tech/tags/access-control.md>), [access-requests](<https://devfeed.tech/tags/access-requests.md>), [adaptive](<https://devfeed.tech/tags/adaptive.md>), [adversarial](<https://devfeed.tech/tags/adversarial.md>), [attack-surface](<https://devfeed.tech/tags/attack-surface.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [cs-ai](<https://devfeed.tech/tags/cs-ai.md>), [cs-cr](<https://devfeed.tech/tags/cs-cr.md>), [dataset](<https://devfeed.tech/tags/dataset.md>), [energy](<https://devfeed.tech/tags/energy.md>), [framework](<https://devfeed.tech/tags/framework.md>), [grid](<https://devfeed.tech/tags/grid.md>), [machine](<https://devfeed.tech/tags/machine.md>), [machine-learning](<https://devfeed.tech/tags/machine-learning.md>), [ml](<https://devfeed.tech/tags/ml.md>), [model](<https://devfeed.tech/tags/model.md>), [networks](<https://devfeed.tech/tags/networks.md>), [opa](<https://devfeed.tech/tags/opa.md>), [open-policy-agent](<https://devfeed.tech/tags/open-policy-agent.md>), [policy](<https://devfeed.tech/tags/policy.md>), [trust](<https://devfeed.tech/tags/trust.md>), [zero-trust](<https://devfeed.tech/tags/zero-trust.md>)

### AI overview

ZT-DAC combines an Open Policy Agent (OPA)-based RBAC decision layer with ML-based ABAC in a two-stage process intended to assess trust continuously for DER network access. The authors create a DER-specific access model and a dataset containing legitimate and adversarial requests. On that dataset, the OPA layer reports 91.92% accuracy and a 14.45% false positive rate; the ML trust-score predictor reports MAE 2.074 and R² 0.891; and the ABAC layer reports 93.27% accuracy and a 3.88% false positive rate. These are dataset results; the supplied abstract does not establish performance in deployed DER environments.

### Source excerpt

arXiv:2611.02107v1 Announce Type: new Abstract: The increasing penetration of Distributed Energy Resources (DERs) in the smart grid has significantly expanded the cyber-attack surface. Traditionally, DER networks rely on static role-based access control (RBAC) mechanisms that assume persistent trust after authentication. This limitation enables adversaries to maintain unauthorized privileges and move laterally across DER systems, disrupting grid operations. Although attribute-based access control (ABAC) enables fine-grained and context-aware access decisions, it does not fully eliminate implicit trust. Zero Trust (ZT) principles can be incorporated to enhance ABAC policies. This paper proposes a dynamic access control framework for implementing ZT in DER networks (ZT-DAC). The proposed solution employs a two-stage verification process and integrates an Open Policy Agent (OPA)-based RBAC with a machine learning (ML)-based ABAC to enforce continuous and adaptive trust score assessment. To support realistic DER operations, a DER-specific access control model is developed and used to generate a domain-informed dataset of access requests incorporating both legitimate and adversarial behaviors. Experimental results on the dataset show that the OPA-based decision layer achieves \(91.92\%\) accuracy, with a False Positive Rate of \(14.45\%\), while the ML model achieves a Mean Absolute Error of \(2.074\) and an \(R^2\) of \(0.891\) in trust-score prediction. The ABAC layer achieves \(93.27\%\) accuracy, with a FPR of \(3.88\%\), validating its practical feasibility within realistic DER environments.

## CVE-2026-61850 - Kargo: Privilege escalation via Project RBAC management in the Kargo API

DevFeed: [CVE-2026-61850 - Kargo: Privilege escalation via Project RBAC management in the Kargo API](<https://devfeed.tech/articles/cve-2026-61850-kargo-privilege-escalation-via-project-rbac-management-in-the-kargo-api-109383.md>)

Original publisher: [Read original article](<https://cvefeed.io/vuln/detail/CVE-2026-61850>)

Author: CVEFEED.io; github.com

Published: 2026-10-30T20:17:11Z

Content type: news

Language: en

Sources: [Latest High/Critical Vulnerabilitiy Feed](<https://devfeed.tech/sources/latest-high-critical-vulnerabilitiy-feed.md>)

Topics: [rbac](<https://devfeed.tech/topics/rbac.md>), [Authorization](<https://devfeed.tech/topics/authorization.md>), [identity and access management](<https://devfeed.tech/topics/identity-and-access-management.md>), [Credential theft](<https://devfeed.tech/topics/credential-theft.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [account](<https://devfeed.tech/tags/account.md>), [administrator](<https://devfeed.tech/tags/administrator.md>), [akuity](<https://devfeed.tech/tags/akuity.md>), [api](<https://devfeed.tech/tags/api.md>), [api-server](<https://devfeed.tech/tags/api-server.md>), [artifacts](<https://devfeed.tech/tags/artifacts.md>), [authorization](<https://devfeed.tech/tags/authorization.md>), [bind](<https://devfeed.tech/tags/bind.md>), [changes](<https://devfeed.tech/tags/changes.md>), [cluster](<https://devfeed.tech/tags/cluster.md>), [container-registry](<https://devfeed.tech/tags/container-registry.md>), [credentials](<https://devfeed.tech/tags/credentials.md>), [cross](<https://devfeed.tech/tags/cross.md>), [cve](<https://devfeed.tech/tags/cve.md>), [cve-2026-61850](<https://devfeed.tech/tags/cve-2026-61850.md>), [kargo](<https://devfeed.tech/tags/kargo.md>), [management](<https://devfeed.tech/tags/management.md>), [privilege-escalation](<https://devfeed.tech/tags/privilege-escalation.md>), [project](<https://devfeed.tech/tags/project.md>), [rbac](<https://devfeed.tech/tags/rbac.md>)

### AI overview

CVE-2026-61850 affects Kargo versions from 0.6.0 up to fixes 1.8.14, 1.9.9, and 1.10.8. In the project-scoped RBAC API, delegated permission to edit Roles can be abused to grant unheld permissions, or permission to edit a Role's ServiceAccount can bind an identity to a more powerful Role. The API uses broadly privileged server credentials and checks only the resource kind, not the permissions being granted. An attacker must control an account assigned an administrator-created custom role with relevant RBAC-management permissions; default non-administrator roles do not allow this. Escalation can expose Project Secrets and credentials or alter and delete Project resources, but remains confined to Projects where the attacker has that delegation and does not itself grant cluster-wide or cross-Project access. Stolen Git, container-registry, or Helm-registry credentials may extend impacts to those systems.

### Source excerpt

CVE ID :CVE-2026-61850 Published : Oct. 30, 2026, 8:17 p.m. | 1 hour, 37 minutes ago Description :Kargo manages and automates the promotion of software artifacts. From 0.6.0 until 1.8.14, 1.9.9, and 1.10.8, two authorization flaws in the `project-scoped RBAC API` let an authenticated user with delegated permission to manage a Project's `Roles` or `ServiceAccounts` confer permissions exceeding the user's own. A user authorized to edit `Roles` can create, replace, or add rules granting permissions not held by the user; a user authorized to edit a Role's ServiceAccount can bind an identity, including the user's own, to a more powerful Role. A Kargo Role comprises a `ServiceAccount, Role, and RoleBinding` in the Project namespace. Changes are written using the API server's broadly privileged credentials after only a coarse resource-kind edit check, rather than checking each permission being conferred. This permits escalation to Project-administrator access, disclosure of `Project Secrets` and credentials, and modification or deletion of Project resources. Stolen Git, container-registry, or Helm-registry credentials can extend confidentiality and integrity impacts to those external systems. Escalation remains limited to Projects where the attacker already has RBAC-management delegation and does not itself grant cluster-wide or cross-Project access. Default non-administrator roles do not permit these operations; exploitation requires an `administrator-created custom role` granting the relevant permissions and control of an account assigned that role. This issue is fixed in versions 1.8.14, 1.9.9, and 1.10.8. Severity: 9.3 | CRITICAL Visit the link for more details, such as CVSS details, affected products, timeline, and more...

[Next page](<https://devfeed.tech/topics/rbac.md?cursor=WyIyMDI2LTEwLTMwVDIwOjE3OjExKzAwOjAwIiwgIjFkOTljMDAyLTA1OGEtNDM2My1iZjcwLTcwMzNlOGNmZGNmZSJd>)