No entries match these filters. Clear filters
Aembit adds embedded user authorization for MCP MCP Model Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. servers and new Prometheus metrics for credential injection and workload event batching︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ USE IT
Cap workload event batch size on a self-hosted MCP Identity Gateway to reduce per-flush payload size in high-traffic environments.
.env
copy
AEMBIT_EVENT_MAX_SEND_BATCH=100
Authorize a person into a specific MCP server by naming it in the mcp_server_url parameter of a standard OAuth authorization code flow with PKCE PKCE Proof Key for Code Exchange, an OAuth safeguard that binds an authorization code to the client that requested it. An intercepted code cannot be redeemed without the client's matching verifier. — Aembit shows no login page, Identity Provider picker, or consent screen of its own.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet New aembit_mcp_gateway_upstream_mcp_server_credential_injections_total Prometheus metric counts requests to MCP servers by whether MCP Identity Gateway added the credential the Access Policy configures. Not checked yet New aembit_mcp_gateway_upstream_mcp_server_http_requests_total Prometheus metric now reports outcome="auth_error" when an MCP server returns an HTTP authentication error. Not checked yet New aembit_event_batch_size Prometheus histogram records how many workload events each batch carried for every batch that reached Aembit Cloud. Not checked yet A saved OIDC OIDC OpenID Connect, a sign-in protocol built on OAuth 2.0. An application uses identity information from a trusted provider instead of maintaining a separate password for each user. 1.0 Identity Provider now displays the Aembit Client ID that your application sends to Aembit as client_id. Not checked yet
Authorize a person into a specific MCP server by naming it in the mcp_server_url parameter of a standard OAuth authorization code flow with PKCE PKCE Proof Key for Code Exchange, an OAuth safeguard that binds an authorization code to the client that requested it. An intercepted code cannot be redeemed without the client's matching verifier. — Aembit shows no login page, Identity Provider picker, or consent screen of its own.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet New aembit_mcp_gateway_upstream_mcp_server_credential_injections_total Prometheus metric counts requests to MCP servers by whether MCP Identity Gateway added the credential the Access Policy configures. Not checked yet New aembit_event_batch_size Prometheus histogram records how many workload events each batch carried for every batch that reached Aembit Cloud. Not checked yet
2 more in Everything
Aembit adds an Enforce SSO SSO Single sign-on, using one identity provider to sign in to multiple applications. It reduces separate passwords and centralizes account and access management. setting to Client Workload identification that requires users to authenticate through a configured identity provider identity provider A service that authenticates users and supplies identity information to other applications. It is the sign-in authority behind many single sign-on systems. during the OAuth flow︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ HOW TO FIND IT
Enforce that all Client Workload OAuth flows go through a specific SSO identity provider, preventing unauthenticated or direct access.
📍 In the Aembit console, go to Access Policies › Client Workloads › [your workload] › Identification › Redirect URI, enable Enforce SSO , then select at least one active SSO identity provider from the multi-select dropdown and save.
Aembit adds an Enforce SSO option to MCP MCP Model Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. Authorization Configuration, letting you require or skip identity-provider authentication during the OAuth flow︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ HOW TO FIND IT
Disable SSO SSO Single sign-on, using one identity provider to sign in to multiple applications. It reduces separate passwords and centralizes account and access management. enforcement for a Client Workload to allow the OAuth flow to complete without user authentication — useful for fully automated, non-human workloads.
📍 In the Aembit console, open the Client Workload, go to MCP Authorization Configuration, and set Enforce SSO to Off .
Restrict which identity providers identity providers A service that authenticates users and supplies identity information to other applications. It is the sign-in authority behind many single sign-on systems. users can choose on the MCP authentication page for a specific Client Workload.
📍 In the Aembit console, open the Client Workload, go to MCP Authorization Configuration, set Enforce SSO to On , then deselect any identity providers you do not want shown on the MCP authentication page.
Control whether users must authenticate through an SSO identity provider identity provider A service that authenticates users and supplies identity information to other applications. It is the sign-in authority behind many single sign-on systems. during the OAuth flow by setting the Enforce SSO option in MCP Authorization Configuration to On (default) or Off .︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet
1 detail in Everything
Aembit adds MCP MCP Model Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. Identity Gateway user identification by OIDC OIDC OpenID Connect, a sign-in protocol built on OAuth 2.0. An application uses identity information from a trusted provider instead of maintaining a separate password for each user. Identity Provider group︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Aembit adds Microsoft Copilot Studio agent support to MCP MCP Model Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. Identity Gateway, routing per-user credentials through OAuth 2.0 OAuth 2.0 An open authorization framework (IETF RFC 6749) that lets a service grant limited API access to a third party without sharing credentials, giving cyber tools a standard way to authenticate against external platforms. over Streamable HTTP Streamable HTTP An MCP transport protocol that lets a client send JSON-RPC requests over HTTP POST while the server streams responses back using Server-Sent Events, replacing the older stdio and SSE transports for remote tool communication. transport︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ HOW TO FIND IT
Connect a Copilot Studio agent to MCP Identity Gateway when the target MCP server (such as Microsoft Graph Microsoft Graph Microsoft's unified REST API for accessing data and services across Microsoft 365, Azure AD, and related cloud products, giving cyber tools a single authenticated endpoint to query users, emails, files, and sign-in logs. ) does not support OAuth discovery and requires manual OAuth configuration.
📍 In Copilot Studio, create a tool with your MCP Identity Gateway endpoint (ending in /mcp) as the Server URL, then when prompted for OAuth values enter the callback URL manually: https://<tenant-id>.id.<stack>.aembit.io/mcp-auth/userauth/<cp-id>/callback
Connect Microsoft Copilot Studio agents to MCP Identity Gateway using Streamable HTTP transport, with MCP Identity Gateway validating OAuth 2 OAuth 2 An open authorization framework (RFC 6749) that lets a service grant limited access to a user's resources on another service without exposing credentials, giving cyber tools a standard way to authenticate against third-party APIs. .0 access tokens access tokens A credential that authorizes a client to use a service or API. It usually has limited permissions and a lifetime; anyone holding it may be able to use those permissions. and proxying requests to downstream MCP servers using Aembit-managed credentials.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet Configure the OAuth callback URL in the form https://<tenant-id>.id.<stack>.aembit.io/mcp-auth/userauth/<cp-id>/callback when connecting Copilot Studio to servers (such as Microsoft Graph via the Microsoft MCP Server MCP Server A process that exposes tools, resources, and prompts over Anthropic's Model Context Protocol, letting an AI agent call external APIs or local services through a standardised interface. for Enterprise) that do not support OAuth discovery and require manual OAuth value entry. Not checked yet Manage Copilot Studio's 70-tool limit per agent by assigning fewer Access Policies per agent, using per-tool toggles, splitting integrations across child agents with their own tool budgets, or keeping MCP tool names to 64 characters or fewer including the Server Workload prefix MCP Identity Gateway adds. Not checked yet
3 details in Everything
Aembit adds MCP MCP Model Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. Identity Gateway, a stateless data-plane proxy that enforces Access Policies on every AI-agent-to-MCP-server MCP-server A process that exposes tools, resources, and prompts over Anthropic's Model Context Protocol, letting an AI agent call external APIs or local services through a standardised interface. request︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Aembit adds MCP Identity Gateway as a managed SaaS SaaS Software delivered over the internet and billed by subscription, hosted and operated by the vendor so the buyer skips installation and infrastructure management. proxy reachable at https://<tenant-id>.mcpgateway.aembit.io, placing per-request policy evaluation and credential injection between AI agents and MCP servers.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet Self-host MCP Identity Gateway inside your own environment so all runtime state stays within a single Aembit Tenant. Not checked yet MCP Identity Gateway now proxies MCP resource discovery and retrieval through the same request flow as tools, requiring no separate Access Policies for resources. Not checked yet Content Security in MCP Identity Gateway enforces four boundaries: token validation against the configured Trust Provider, TLS termination and re-initiation toward MCP servers, in-memory-only credential handling, and per-request evaluation against Aembit Access Policies. Not checked yet MCP Identity Gateway scopes credentials per connection — the AI agent holds a token valid only against the gateway, while the gateway holds a separate token valid against the MCP server and never exposes it to the agent. Not checked yet
+1 more
show less
Left-side policies control which MCP clients can connect to MCP Identity Gateway (one per MCP client and gateway combination), and right-side policies control where the gateway routes traffic and how it authenticates to each MCP server (one per MCP server). Not checked yet
6 details in Everything
Aembit adds Aembit Desktop for Windows 11 and an MCP Server MCP Server A process that exposes tools, resources, and prompts over Anthropic's Model Context Protocol, letting an AI agent call external APIs or local services through a standardised interface. for AI-assistant-driven tenant management︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Aembit Desktop now gives Windows 11 users access to HTTP and HTTPS HTTPS HTTP carried over an encrypted TLS connection. It protects traffic in transit and lets a browser verify the server's certificate. services without static credentials, covering setup, install, sign-in, settings delivery, AWS CLI use, and troubleshooting.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet Aembit adds an MCP Server that exposes Aembit Tenant configuration to MCP clients so practitioners can query and manage Aembit from an AI assistant. Not checked yet
2 details in Everything
Aembit adds blended identity for AI agents, combining user identity with workload identity workload identity An identity assigned to software, such as a service or container, rather than a person. It lets the workload authenticate and receive permissions without sharing a user's credentials. in a single access policy decision︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Aembit now supports blended identity in access policies, combining user identity (from your IdP IdP A service that authenticates users and supplies identity information to other applications. It is the sign-in authority behind many single sign-on systems. ) with AI agent workload identity so a single policy can ask: is this user, using this AI agent, authorized to reach this resource right now?︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet Access policies can now express per-agent-per-user rules, such as allowing a user to reach Confluence through Claude Desktop but denying access through an untrusted third-party AI agent. Not checked yet MCP MCP Model Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. Identity Gateway now stores OAuth tokens per user rather than per AI agent, so revoking one user's access does not affect other users sharing the same gateway. Not checked yet Blended identity spans two access policies: a Credential Provider embeds the user's identity into the access token access token A credential that authorizes a client to use a service or API. It usually has limited permissions and a lifetime; anyone holding it may be able to use those permissions. using dynamic claim injection, and MCP Identity Gateway uses its workload identity plus the embedded user context to obtain downstream credentials. Not checked yet
4 details in Everything
Aembit adds user access via Identity Providers for Aembit Desktop, plus OIDC OIDC OpenID Connect, a sign-in protocol built on OAuth 2.0. An application uses identity information from a trusted provider instead of maintaining a separate password for each user. group lookup for Access Policies︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ HOW TO FIND IT
Let Windows 11 users sign in to Aembit Desktop through an existing SSO SSO Single sign-on, using one identity provider to sign in to multiple applications. It reduces separate passwords and centralizes account and access management. Identity Provider without static credentials.
📍 In the Aembit console, go to Administration › Identity Providers › <your IdP> › Users tab, then toggle Enable User Access and save. The Users tab appears only after Aembit support enables Aembit Desktop for your tenant.
Enable user access for Aembit Desktop on a per-Identity Provider basis using Enable User Access on the Identity Provider's Users tab, letting Windows 11 users sign in through an existing SSO provider without holding static credentials.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet Turn on group lookup on an OIDC Identity Provider to let Access Policies match users by the groups they belong to in that provider, enabling MCP MCP Model Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. server restrictions by IdP IdP A service that authenticates users and supplies identity information to other applications. It is the sign-in authority behind many single sign-on systems. group. Not checked yet Aembit now supports automatic user creation tied to Identity Providers at sign-in. Not checked yet
3 details in Everything
Aembit adds MCP MCP Model Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. Identity Gateway reports for MCP traffic, with live authorization request views and exception tracking︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ HOW TO FIND IT
Review failed or blocked MCP requests at a glance — go to the Reporting dashboard and open MCP Access Exceptions to see every request that returned an error or exception code, grouped by user, client, server, method, target, and exception type.
📍 In the Aembit Tenant, go to Reporting › MCP reports › MCP Access Exceptions to view all MCP requests with an error or exception code, grouped by user, MCP client, MCP server, method, target, and exception.
Aembit now surfaces MCP Access Activities reports, listing MCP requests with no error or exception code grouped by user, MCP client, MCP server, method, and target, via the Reporting dashboard.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet Aembit now surfaces MCP Access Exceptions reports, listing MCP requests that carry an error or exception code grouped by user, MCP client, MCP server, method, target, and exception, via the Reporting dashboard. Not checked yet Aembit adds a live authorization request view at the MCP Identity Gateway that surfaces the redirect URI, resource, matched Client Workload, and Access Policy outcome for each inbound request before the standard event-pipeline delay. Not checked yet
3 details in Everything
Aembit adds MCP MCP Model Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. Identity Gateway, a managed proxy that brokers identity and access policies between AI agents and MCP servers︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ TRY IT
Verify your tenant's MCP Identity Gateway endpoint is live and TLS is terminating correctly before configuring any client workloads.
copy
$ curl -v https://<tenant-id>.mcpgateway.aembit.io/
Walk through the two required Access Policies and optional Content Security provider in the Aembit console to fully wire up an AI agent to an MCP server.
📍 1. In the Aembit console, go to Access Policies and create the Client-to-Gateway policy: set the Client Workload to the MCP client, set the Server Workload hostname to <tenant-id>.mcpgateway.aembit.io, and attach a Credential Provider that issues tokens whose audience matches MCP Identity Gateway.
2. Create the Gateway-to-Server policy: set the Client Workload to MCP Identity Gateway (https://<tenant-id>.aembit.io), set the Server Workload to the upstream MCP server, and configure OAuth with the Authorization URL and Token URL from the MCP server vendor.
3. Optionally, open the Access Conditions card in the right panel on either policy and add time-based or GeoIP-based conditions.
4. Optionally, attach a Content Security provider to the Gateway-to-Server policy to inspect each MCP tool message.
Aembit now operates MCP Identity Gateway as a managed service, giving each tenant a dedicated endpoint at https://<tenant-id>.mcpgateway.aembit.io to proxy AI-agent traffic to MCP servers.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet Configure two Access Policies — one governing which MCP clients and users can connect to MCP Identity Gateway, and one governing how MCP Identity Gateway connects to upstream MCP servers. Not checked yet MCP Identity Gateway now supports time-based and GeoIP GeoIP A database that maps IP addresses to geographic locations; tools use it to attribute traffic or alerts to countries, cities, or ASNs without querying external services. -based Access Conditions for MCP traffic, configurable per Access Policy. Not checked yet Attach a Content Security provider to an Access Policy to have MCP Identity Gateway inspect each MCP tool message matched by that policy. Not checked yet MCP Identity Gateway automatically discovers which MCP servers are available when it connects to the Aembit control plane, without requiring changes to MCP Identity Gateway itself. Not checked yet
5 details in Everything
Aembit: Aembit-managed deployment hosts MCP MCP Model Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. Identity Gateway at https://<tenant-id>.mcpgateway.aembit.io, handling TLS, cert renewal, and runtime ops.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Self-hosted deployment lets you run MCP Identity Gateway as a service on a Linux host you provision and maintain, configured via environment variables Aembit sets during provisioning. Not checked yet MCP Identity Gateway proxies traffic between AI agents and MCP servers — routing tool invocations and resource access — without requiring either side to upgrade to a new protocol revision. Not checked yet MCP Identity Gateway validates a signed JWT JWT An open standard (RFC 7519) for encoding claims as a signed, optionally encrypted JSON object passed between parties. Cyber tools use it to verify identity and permissions without querying a central session store. (JSON Web Token) on every MCP request using Aembit's signing keys (JWKS JWKS A JSON Web Key Set, a published collection of cryptographic keys. Applications use it to find the public key needed to verify a token's signature. ), extracting AI agent and user identity before allowing the request. Not checked yet MCP Identity Gateway obtains and caches credentials for downstream MCP servers per-request for 60 seconds and never persists them to disk, so AI agents never hold direct credentials for enterprise systems. Not checked yet A single MCP Identity Gateway instance routes traffic to multiple MCP servers while sharing centralized Aembit policies, replacing scattered per-agent configurations. Not checked yet
+2 more
show less
MCP Identity Gateway produces structured logs capturing AI agent identity, user identity, target MCP server, and policy decisions for auditability. Not checked yet MCP Identity Gateway denies all requests by default (fail-closed) unless a policy explicitly allows them. Not checked yet
7 details in Everything
Aembit adds Desktop proxy for Windows 11, MCP MCP Model Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. user-group matching, and two new MCP reporting dashboard views︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ TRY IT
Run an AWS CLI command from a developer workstation without any stored AWS access keys — Aembit Desktop injects the credential from the matching Access Policy.
copy
$ adt beta tool aws s3 ls s3://my-bucket
Restrict an MCP server to users who belong to the engineering team or any group starting with finance- in your OIDC OIDC OpenID Connect, a sign-in protocol built on OAuth 2.0. An application uses identity information from a trusted provider instead of maintaining a separate password for each user. Identity Provider.
📍 In the Aembit console, open the Client Workload, add a User Group identifier, select the OIDC 1.0 Identity Provider, and enter engineering or finance-* as the group value. Then go to the Identity Provider's Settings and enable User Groups & MCP Policy Access , setting the group claim name and cache time.
Review failed or blocked MCP requests in one place to triage access policy issues or client misconfigurations.
📍 In the Aembit console, go to Reporting › MCP Access Exceptions. Open any row to see the exception category and code, the Access Policy decisions applied, and the per-server outcome for that request.
Run AWS CLI commands without storing AWS access keys on the machine using adt beta tool aws, which pulls credentials from an Access Policy at request time.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet Aembit Desktop now delivers managed Desktop settings as JSON files to override per-user configuration on Windows 11 machines, and adds a local proxy for Windows 11 x64 Public beta that injects service credentials into HTTP and HTTPS HTTPS HTTP carried over an encrypted TLS connection. It protects traffic in transit and lets a browser verify the server's certificate. requests per-policy, with no credentials stored on the machine. Not checked yet A single Client Workload can now carry both a Redirect URI and a CIMD CIMD A text-based Short Message Service protocol from Nokia for exchanging SMS messages between applications and SMS centers, used to build tools that send, receive, or test carrier messaging flows. Client ID identifier for MCP client identification, and SSO SSO Single sign-on, using one identity provider to sign in to multiple applications. It reduces separate passwords and centralizes account and access management. enforcement can be enabled for CIMD Client ID Client Workloads with the Enforce SSO toggle, limiting the MCP sign-in page to only the Identity Providers assigned to that workload. Not checked yet MCP Authorization Server now accepts an application_type of native or web via Dynamic Client Registration, allowing native clients to register custom-scheme redirect URIs such as vscode://. Not checked yet MCP Server MCP Server A process that exposes tools, resources, and prompts over Anthropic's Model Context Protocol, letting an AI agent call external APIs or local services through a standardised interface. Workload URL Path values can now end in a trailing slash, such as /mcp/. Not checked yet
Run AWS CLI commands without storing AWS access keys on the machine using adt beta tool aws, which pulls credentials from an Access Policy at request time.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet Aembit Desktop now delivers managed Desktop settings as JSON files to override per-user configuration on Windows 11 machines, and adds a local proxy for Windows 11 x64 Public beta that injects service credentials into HTTP and HTTPS HTTPS HTTP carried over an encrypted TLS connection. It protects traffic in transit and lets a browser verify the server's certificate. requests per-policy, with no credentials stored on the machine. Not checked yet
3 more in Everything
Aembit adds MCP MCP Model Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. Identity Gateway, a managed proxy that injects credentials into MCP server requests so AI agents hold no downstream secrets︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ HOW TO FIND IT
Route an AI agent through MCP Identity Gateway instead of directly to an MCP server, so the agent authenticates through Aembit and holds no downstream credentials.
📍 In your Aembit Tenant, go to MCP Identity Gateway › Access Policies and create a Gateway-to-Server policy targeting the MCP server you want to front. Point your AI agent at the MCP Identity Gateway endpoint in place of the direct MCP server URL.
Aembit now offers MCP Identity Gateway, a managed data-plane proxy that sits between AI agents and MCP servers, injecting credentials per request so agents never hold downstream secrets.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet MCP Identity Gateway now supports per-user credential isolation, where many users share the same AI agent but each user's requests use their own downstream credentials scoped to their identity. Not checked yet MCP Identity Gateway now provides centralized routing so a single endpoint reaches multiple MCP servers, letting you add or remove servers through policy instead of reconfiguring every AI agent. Not checked yet
3 details in Everything
Aembit: Aembit now supports blended identity access control for AI agents, evaluating user and agent workload identity workload identity An identity assigned to software, such as a service or container, rather than a person. It lets the workload authenticate and receive permissions without sharing a user's credentials. in one Access Policy.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Aembit adds MCP MCP Model Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. Identity Gateway, a centralized proxy that provides per-user credential isolation and zero credential exposure when AI agents access MCP servers, with the AI agent registering at runtime and completing the OAuth flow without pre-shared client secrets. Not checked yet Aembit logs every AI agent MCP request with both verified user identity and AI agent workload identity, capturing authentication events (which user, which AI agent, time, location) and workload events (resources accessed, operations performed, credentials issued) for compliance audit trails. Not checked yet
2 details in Everything
Aembit: Aembit Desktop public beta for Windows 11 x64: sign in once via OIDC OIDC OpenID Connect, a sign-in protocol built on OAuth 2.0. An application uses identity information from a trusted provider instead of maintaining a separate password for each user. or SAML SAML A standard for passing signed identity assertions between a sign-in provider and an application. It lets a user sign in through their organization's identity provider. , reach enterprise services through a local proxy, no stored credentials.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ TRY IT
Run an AWS CLI command from a developer workstation without storing AWS access keys — the credential comes from the Access Policy at request time.
copy
$ adt beta tool aws s3 ls s3://my-bucket
Restrict an MCP MCP Model Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. server to members of a specific engineering group defined in an OIDC Identity Provider, using wildcard patterns for teams like all finance sub-groups.
📍 In the Client Workload editor, add a User Group identifier, select your OIDC 1.0 Identity Provider, and enter engineering or finance-* as the group pattern. Enable User Groups & MCP Policy Access on the Identity Provider's settings to set the group claim and cache time.
Enforce SSO SSO Single sign-on, using one identity provider to sign in to multiple applications. It reduces separate passwords and centralizes account and access management. for an MCP client identified only by CIMD CIMD A text-based Short Message Service protocol from Nokia for exchanging SMS messages between applications and SMS centers, used to build tools that send, receive, or test carrier messaging flows. Client ID, so only users from approved Identity Providers can reach the MCP server.
📍 In the Client Workload editor, set the identifier to a CIMD Client ID, toggle on Enforce SSO , and select one or more Identity Providers. Save requires at least one Identity Provider selected.
Administrators can deliver managed settings as JSON files that override user-set preferences on each machine. Not checked yet
1 detail in Everything
Aembit adds a Desktop application for accessing HTTP and HTTPS HTTPS HTTP carried over an encrypted TLS connection. It protects traffic in transit and lets a browser verify the server's certificate. Server Workloads︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Aembit Now Secures Google Antigravity Agents (2026-11-09)
Nov 9, 2026
·
issue 135
Aembit adds Google Antigravity support via the MCP MCP Model Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. Identity Gateway, brokering short-lived credentials using a blended agent-and-user identity model with full audit logging.
New integration Point mcp_config.json at the Aembit MCP Identity Gateway to enforce real-time policy evaluation for Google Antigravity (agy) agents before any credential is issued. Not checked yet Aembit's blended identity model evaluates both the agent's identity and the human user's IdP IdP A service that authenticates users and supplies identity information to other applications. It is the sign-in authority behind many single sign-on systems. identity together, replacing long-lived Google ADC sessions and bearer tokens bearer tokens A credential that grants access to whoever presents it, without a separate proof of possession. Protecting the token matters because a stolen copy can be used by someone else. stored in mcp_config.json or cached at ~/.gemini/antigravity/mcp_oauth_tokens.json with short-lived, scoped credentials. Not checked yet Every credential issuance and access event is logged against both the agent identity and the human identity behind it, making 'which agent touched production, and on whose behalf' a query rather than an investigation. Not checked yet
3 details in Everything
Aembit Now Secures OpenAI Dots Personal Agents (2026-11-04)
Nov 4, 2026
·
issue 131
Aembit adds OpenAI Dots support to its MCP MCP Model Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. Identity Gateway, giving personal AI agents just-in-time credentials and tool-level access control︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ HOW TO FIND IT
Extend existing ChatGPT gateway coverage to also control OpenAI Dots, limiting what tools the agent can call on a connected MCP server.
📍 In the Aembit console, go to the MCP Identity Gateway connector already configured for ChatGPT, extend the access policy to include the Dots agent identity, and add an MCP Tool Access Control rule specifying which tool names or patterns are permitted for tools/call — Dots will then share the same gateway connection with no additional connector needed.
Aembit now secures OpenAI Dots personal agents through the MCP Identity Gateway, using the same single connector already used for ChatGPT — no new product to deploy.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet MCP Tool Access Control filters which tools a Dot can discover via tools/list and checks each tools/call before it reaches the MCP server, with enforcement failing closed. Not checked yet The MCP Authorization Server evaluates policy on blended identity — the agent, the employee it acts for, group membership, and runtime security posture — before issuing credentials. Not checked yet Issues short-lived, scoped credentials at runtime for each MCP server request so agents never hold static long-lived credentials for connected services such as GitHub, Microsoft 365, and Salesforce. Not checked yet Security teams can revoke a specific Dot's access through Aembit without affecting the employee's own accounts, acting as an independent kill switch for agent access. Not checked yet
+1 more
show less
Applies the same policy framework across Dots, ChatGPT, Claude, Copilot Studio, and Meta Muse from a single centralized policy control plane. Not checked yet
Aembit now secures OpenAI Dots personal agents through the MCP Identity Gateway, using the same single connector already used for ChatGPT — no new product to deploy.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet MCP Tool Access Control filters which tools a Dot can discover via tools/list and checks each tools/call before it reaches the MCP server, with enforcement failing closed. Not checked yet
4 more in Everything
Introducing the AI Agent Kill Switch: Instant Single-User Revocation (2026-10-29)
Oct 29, 2026
·
issue 125
Aembit adds an AI agent kill switch to revoke a single user's MCP MCP Model Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. client session without affecting other agents or users︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ HOW TO FIND IT
Immediately cut off a single user's compromised Claude Code session without locking them out of other agents or breaking the tool for teammates.
📍 In your Aembit tenant:
1. Go to Administration › Identity Providers and open the provider your users sign in through.
2. Open the Sessions tab.
3. Filter by user email and MCP client to find the target session.
4. Select Revoke session and confirm.
Bulk-revoke all sessions tied to a retired MCP client during incident response, without touching any other user or agent.
📍 In your Aembit tenant:
1. Go to Administration › Identity Providers, open the relevant provider, and open the Sessions tab.
2. Filter by the retired MCP client name.
3. Select Revoke filtered and confirm.
Revoke a specific MCP user session by navigating to Administration > Identity Providers > Sessions tab and selecting Revoke session , scoped to one user and one MCP client without affecting other sessions.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet Filter and bulk-revoke sessions in the Sessions view by user email, MCP client, or both using Revoke filtered , covering all sessions for one user or all sessions for one MCP client. Not checked yet Automate session revocation in incident-response workflows via the Aembit Cloud API. Not checked yet Sessions appear for MCP clients that connect through a Client-to-Gateway Access Policy using an OIDC ID Token Credential Provider with refresh token refresh token A credential used to obtain a new access token without signing in again. It is sent to the authorization service rather than used directly to call the protected API. support enabled; admins need Read/Write permission on Identity Providers to revoke. Not checked yet
4 details in Everything
Aembit adds AEMBIT_NETWORK_ACCESS_POLICY to control which MCP MCP Model Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. servers a self-hosted MCP Identity Gateway can reach, and exposes gateway version in protected resource metada︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Read the MCP Identity Gateway version without an access token access token A credential that authorizes a client to use a service or API. It usually has limited permissions and a lifetime; anyone holding it may be able to use those permissions. via the aembit_gateway_version field now present in the protected resource metadata document.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet Agent Controller now bypasses an HTTP proxy when calling the AWS instance metadata service for AWS Metadata Service Trust Provider attestation, matching its existing Azure behavior. Not checked yet Agent Controller authentication errors now name the Agent Controller ID that failed, prompting you to confirm it is valid and active in your Aembit Tenant. Not checked yet MCP Identity Gateway now applies a new credential on the user's very next request after an MCP User-Based Access Token Credential Provider authorization, instead of returning errors until the cached credential expired. Not checked yet MCP clients now receive MCP server errors directly when MCP Tool Access Control is filtering a tool list and the upstream MCP server returns an error. Not checked yet
+2 more
show less
MCP Identity Gateway now sends tool-argument request headers to MCP clients on earlier specification revisions when connecting to MCP servers on the 2026-07-28 MCP specification. Not checked yet Workload events now record credential injection as failed when MCP Identity Gateway cannot add a credential to a request as a header or query parameter. Not checked yet
Read the MCP Identity Gateway version without an access token access token A credential that authorizes a client to use a service or API. It usually has limited permissions and a lifetime; anyone holding it may be able to use those permissions. via the aembit_gateway_version field now present in the protected resource metadata document.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet
6 more in Everything
Aembit Now Supports SPIFFE: X.509-SVID and JWT-SVID Without SPIRE (2026-10-27)
Oct 27, 2026
·
issue 123
Aembit now issues SPIFFE SPIFFE An open standard, maintained by the CNCF, for assigning cryptographic identities to workloads in dynamic infrastructure so services can authenticate each other without passwords or static credentials. X.509-SVID X.509-SVID An X.509 certificate formatted to carry a SPIFFE Verifiable Identity Document, binding a cryptographic identity to a workload so cyber tools can authenticate services without passwords or static secrets. certificates and JWT-SVID JWT-SVID A SPIFFE Verifiable Identity Document encoded as a JSON Web Token, used to prove workload identity across trust boundaries where X.509 certificates are impractical, such as HTTP headers. tokens directly from its control plane, eliminating the need for SPIRE.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Issues SPIFFE-compliant X.509 X.509 A standard defining the format of public-key certificates, maintained by the ITU-T, used by cyber tools to authenticate identities and establish encrypted connections over TLS and similar protocols. -SVID certificates for end-to-end mTLS mTLS Mutual TLS, an encrypted connection where both client and server present certificates to prove their identity. It helps services verify who they are communicating with. between workloads via Agent Proxy, CLI, or Aembit Secrets Operator (Kubernetes), with certificates auto-rotating at 80% of their lifetime (15-minute default, configurable) and private keys never persisted to disk.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet Issues SPIFFE JWT JWT An open standard (RFC 7519) for encoding claims as a signed, optionally encrypted JSON object passed between parties. Cyber tools use it to verify identity and permissions without querying a central session store. -SVID tokens for bearer-token authentication behind service meshes such as Istio and Envoy, automatically handling standard claims (sub, iss, aud, exp, iat, jti) and supporting custom claims built from literal values or dynamic workload attributes (Kubernetes namespace, AWS account ID, environment). Not checked yet Handles SPIFFE identity attestation, credential issuance, and policy evaluation directly from the Aembit control plane, requiring no SPIRE server, agent, or supporting infrastructure. Not checked yet
3 details in Everything
Aembit: MCP MCP Model Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. Identity Gateway now emits per-server request events for tools/list and resources/list fan-out, returns descriptive upstream connection errors, and raises
└──▷ TRY IT
Install the new Python Edge SDK in a workload that needs to attest with Kubernetes Service Account or other cloud Trust Providers.
copy
$ pip install aembit-edge-sdk
Tune how often MCP Identity Gateway polls for Server Workload assignment and MCP Tool Access Control rule changes in long-lived client sessions.
yaml
copy
subscriptions_workload_refresh_interval: 60
└──▷ BREAKING ON UPGRADE
! MCP Identity Gateway replaces the status field in MCP server connection error responses with upstreamHttpStatus — update any client code that reads status.! MCP Identity Gateway now accepts an access token access token A credential that authorizes a client to use a service or API. It usually has limited permissions and a lifetime; anyone holding it may be able to use those permissions. for only 3 seconds after expiry (down from 60 seconds) — ensure MCP clients refresh tokens refresh tokens A credential used to obtain a new access token without signing in again. It is sent to the authorization service rather than used directly to call the protected API. before expiry.! Fan-out tools/list and resources/list requests now emit one workload event per MCP server — review retention and alerting thresholds for the increased event volume.
Aembit adds MCP MCP Model Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. session management, change-notification relay, tool-output validation, named-header credentials, and parity across Edge SDKs.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ TRY IT
Install the new Aembit Python Edge SDK on a Python 3.10+ workload to unlock all nine Trust Providers.
copy
$ pip install aembit-edge-sdk
Revoke all active MCP sessions for a compromised user without deleting the Identity Provider.
📍 In the Aembit Tenant UI, go to Identity Providers › <your IdP> › Sessions, filter by the user, then select Revoke all sessions for this user .
Adds access.registration event type to Access Authorization Events, recording each Dynamic Client Registration (DCR) request an MCP client sends — successful registrations log client ID, client name, redirect URIs, grant types, and response types at severity Info ; failed registrations log at severity Error with a reason and the failing attribute (and its supplied value when present).︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet Adds subscriptions_workload_refresh_interval timeout setting (default: 30 seconds) to MCP Identity Gateway, controlling how often it checks for assignment and rule changes, and extends it to relay subscriptions/listen change notifications to MCP clients using the 2026-07-28 MCP specification revision, including notifications triggered by Server Workload assignment or MCP Tool Access Control rule changes and on reconnection. Not checked yet Adds tool-output validation to MCP Identity Gateway: when a tool publishes an output schema, completed results are checked against it and the MCP client receives an error in place of any result that does not match. Not checked yet Adds Header authentication scheme support to MCP Identity Gateway, sending credentials to MCP servers in a named header so MCP servers that accept an API key via a custom header now receive it correctly. Not checked yet Adds Sessions tab to each Identity Provider in the Aembit Tenant UI, listing active MCP user sessions with the ability to filter, revoke individual sessions, or revoke all sessions for a user or MCP client at once. Not checked yet
+5 more
show less
Adds AWS Metadata Service, Azure Instance Metadata Service, GCP Identity Token, Kubernetes Service Account, and OIDC OIDC OpenID Connect, a sign-in protocol built on OAuth 2.0. An application uses identity information from a trusted provider instead of maintaining a separate password for each user. ID Token Trust Provider support to the Python Edge SDK (pip install aembit-edge-sdk, requires Python 3.10+). Not checked yet Adds GitLab, Kubernetes Service Account, and Terraform Cloud Trust Provider support to the TypeScript Edge SDK, bringing both SDKs to parity across the same nine Trust Providers. Not checked yet Adds new integration guides for Azure Functions, Azure virtual machines, GitHub Actions GitHub Actions GitHub's built-in CI/CD system that runs automated workflows triggered by repository events, letting cyber tools automate testing, building, and releasing without managing separate pipeline infrastructure. , GitLab CI/CD, Kubernetes, and Terraform Cloud, each covering both TypeScript and Python, and adds an Edge SDK logging reference documenting events the SDKs log, how to route them to a logger, and which hosts the SDKs contact. Not checked yet Adds per-MCP-server MCP-server A process that exposes tools, resources, and prompts over Anthropic's Model Context Protocol, letting an AI agent call external APIs or local services through a standardised interface. workload events for tools/list and resources/list fan-out requests in MCP Identity Gateway, including events for servers that fail or are skipped because they do not support the method, naming the Server Workload and recording the server's host and HTTP status when known. Not checked yet Extends MCP Server Workloads to support any authentication method available to HTTP Server Workloads, including API Key, HTTP Authentication with the Basic scheme, and Static HTTP Headers. Not checked yet
Adds access.registration event type to Access Authorization Events, recording each Dynamic Client Registration (DCR) request an MCP client sends — successful registrations log client ID, client name, redirect URIs, grant types, and response types at severity Info ; failed registrations log at severity Error with a reason and the failing attribute (and its supplied value when present).︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet Adds subscriptions_workload_refresh_interval timeout setting (default: 30 seconds) to MCP Identity Gateway, controlling how often it checks for assignment and rule changes, and extends it to relay subscriptions/listen change notifications to MCP clients using the 2026-07-28 MCP specification revision, including notifications triggered by Server Workload assignment or MCP Tool Access Control rule changes and on reconnection. Not checked yet Adds tool-output validation to MCP Identity Gateway: when a tool publishes an output schema, completed results are checked against it and the MCP client receives an error in place of any result that does not match. Not checked yet Adds Header authentication scheme support to MCP Identity Gateway, sending credentials to MCP servers in a named header so MCP servers that accept an API key via a custom header now receive it correctly. Not checked yet Adds Sessions tab to each Identity Provider in the Aembit Tenant UI, listing active MCP user sessions with the ability to filter, revoke individual sessions, or revoke all sessions for a user or MCP client at once. Not checked yet
+3 more
show less
Adds AWS Metadata Service, Azure Instance Metadata Service, GCP Identity Token, Kubernetes Service Account, and OIDC OIDC OpenID Connect, a sign-in protocol built on OAuth 2.0. An application uses identity information from a trusted provider instead of maintaining a separate password for each user. ID Token Trust Provider support to the Python Edge SDK (pip install aembit-edge-sdk, requires Python 3.10+). Not checked yet Adds new integration guides for Azure Functions, Azure virtual machines, GitHub Actions GitHub Actions GitHub's built-in CI/CD system that runs automated workflows triggered by repository events, letting cyber tools automate testing, building, and releasing without managing separate pipeline infrastructure. , GitLab CI/CD, Kubernetes, and Terraform Cloud, each covering both TypeScript and Python, and adds an Edge SDK logging reference documenting events the SDKs log, how to route them to a logger, and which hosts the SDKs contact. Not checked yet Adds per-MCP-server MCP-server A process that exposes tools, resources, and prompts over Anthropic's Model Context Protocol, letting an AI agent call external APIs or local services through a standardised interface. workload events for tools/list and resources/list fan-out requests in MCP Identity Gateway, including events for servers that fail or are skipped because they do not support the method, naming the Server Workload and recording the server's host and HTTP status when known. Not checked yet
2 more in Everything
└──▷ BREAKING ON UPGRADE
! The status field in MCP client error data (sent when MCP Identity Gateway cannot connect to an MCP server) is replaced by upstreamHttpStatus — update any client code that reads status.! MCP Identity Gateway now accepts an access token access token A credential that authorizes a client to use a service or API. It usually has limited permissions and a lifetime; anyone holding it may be able to use those permissions. for up to 3 seconds after expiry, down from 60 seconds — MCP clients must refresh access tokens access tokens A credential that authorizes a client to use a service or API. It usually has limited permissions and a lifetime; anyone holding it may be able to use those permissions. before they expire.
Introducing MCP Tool Filtering: Fine-Grained, Least-Privilege Authorization for AI Agents (2026-10-15)
Oct 15, 2026
·
issue 110
Aembit adds MCP MCP Model Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. Tool Access Control — per-tool allow/block policies with glob patterns and fail-closed audit logging for AI agents.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ HOW TO FIND IT
Lock a read-only customer-support agent to only list_ tools on a GitHub MCP server, blocking all write and delete tools by glob pattern.
📍 In the Aembit console, open your access policy for the customer-support agent, enable MCP Tool Access Control, set mode to Allow , and add the rule:
Tool pattern: list_*
Leave all other tools unmatched — they are denied automatically. Save the policy; no MCP client or server changes are needed.
Adds application.mcp.contentSecurity.toolFilter audit event that records which rule matched and why for every filtered tools/list response or blocked tools/call request.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet Introduces MCP Tool Access Control in the Aembit MCP Identity Gateway, enabling per-tool allow/block rules inside an access policy — controlling both tools/list discovery visibility and tools/call invocation independently. Not checked yet Supports exact tool names and glob patterns (e.g., get_user*, admin_*, list_*, delete_*) in tool-filtering policies so new tools inherit rules automatically without manual allow-list updates. Not checked yet Enforces tool-filtering rules in Allow mode (deny unmatched by default) or Block mode (permit unmatched by default), selectable per policy to match least-privilege or low-maintenance postures. Not checked yet Scopes tool-access rules by blended identity — user identity, group membership, and workload/agent identity — so different principals sharing the same MCP server receive different tool sets. Not checked yet
+2 more
show less
Evaluates tool-filtering policy before deeper inspection layers (e.g., CrowdStrike AIDR), resolving coarse-grained discovery and invocation decisions first in the enforcement chain. Not checked yet Fails closed by default: a missing or malformed tool-filtering policy causes the gateway to return an empty tools/list and block tools/call, never failing open. Not checked yet
7 details in Everything
Introducing MCP Tool Filtering: Fine-Grained, Least-Privilege Authorization for AI Agents (2026-10-15)
Oct 15, 2026
·
issue 016
Aembit adds MCP MCP Model Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. Tool Access Control — per-tool allow/block policies with glob patterns and fail-closed audit logging for AI agents.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ HOW TO FIND IT
Lock a read-only customer-support agent to only list_ tools on a GitHub MCP server, blocking all write and delete tools by glob pattern.
📍 In the Aembit console, open your access policy for the customer-support agent, enable MCP Tool Access Control, set mode to Allow , and add the rule:
Tool pattern: list_*
Leave all other tools unmatched — they are denied automatically. Save the policy; no MCP client or server changes are needed.
Adds application.mcp.contentSecurity.toolFilter audit event that records which rule matched and why for every filtered tools/list response or blocked tools/call request.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet Introduces MCP Tool Access Control in the Aembit MCP Identity Gateway, enabling per-tool allow/block rules inside an access policy — controlling both tools/list discovery visibility and tools/call invocation independently. Not checked yet Supports exact tool names and glob patterns (e.g., get_user*, admin_*, list_*, delete_*) in tool-filtering policies so new tools inherit rules automatically without manual allow-list updates. Not checked yet Enforces tool-filtering rules in Allow mode (deny unmatched by default) or Block mode (permit unmatched by default), selectable per policy to match least-privilege or low-maintenance postures. Not checked yet Scopes tool-access rules by blended identity — user identity, group membership, and workload/agent identity — so different principals sharing the same MCP server receive different tool sets. Not checked yet
+2 more
show less
Evaluates tool-filtering policy before deeper inspection layers (e.g., CrowdStrike AIDR), resolving coarse-grained discovery and invocation decisions first in the enforcement chain. Not checked yet Fails closed by default: a missing or malformed tool-filtering policy causes the gateway to return an empty tools/list and block tools/call, never failing open. Not checked yet
7 details in Everything
Aembit adds MCP MCP Model Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. user session management, expanded MCP auth methods, and inline Dynamic/Literal value validation for Credential Providers.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ HOW TO FIND IT
Revoke all active MCP user sessions for a compromised user via the Identity Provider Sessions tab.
📍 In the Aembit Tenant UI, go to Identity Providers › [select provider] › Sessions tab. Filter by the target user, then select Revoke all sessions for this user to immediately invalidate all their active MCP sessions.
Assign API Key authentication to an MCP Server MCP Server A process that exposes tools, resources, and prompts over Anthropic's Model Context Protocol, letting an AI agent call external APIs or local services through a standardised interface. Workload instead of the default Bearer scheme.
📍 In the Aembit Tenant UI, go to Server Workloads › [select MCP workload] › Authentication. Change the method from the default HTTP Authentication / Bearer to API Key , configure the key field, and save.
Adds a Sessions tab to each Identity Provider in the Aembit Tenant UI, listing active MCP user sessions with the ability to filter, revoke individual sessions, or revoke all sessions for a user or MCP client at once.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet Prompts to revoke active sessions when deleting an Identity Provider that has sessions tied to an OIDC OIDC OpenID Connect, a sign-in protocol built on OAuth 2.0. An application uses identity information from a trusted provider instead of maintaining a separate password for each user. ID Token Credential Provider with Enable Refresh Token Support turned on. Not checked yet MCP Server Workloads now support all authentication methods available to HTTP Server Workloads, including API Key, HTTP Authentication with the Basic scheme, and Static HTTP Headers. Not checked yet Credential Provider fields that take a Literal or Dynamic value now validate the value against its type — Aembit rejects saves (including via the API or Terraform) when a Literal value contains a ${...} expression or a Dynamic value contains no valid ${...} expression. Not checked yet Entering a ${...} expression in a Credential Provider field in the Tenant UI automatically switches the field to Dynamic mode. Not checked yet
+2 more
show less
The Select Existing tab in the Access Policy builder now searches and pages through all accessible entities, removing the previous 100-entry cap on Client Workloads, Server Workloads, Trust Providers, Credential Providers, and Access Conditions. Not checked yet Enhanced security for sign-in to the Aembit Tenant UI, including single sign-on single sign-on Single sign-on, using one identity provider to sign in to multiple applications. It reduces separate passwords and centralizes account and access management. support. Not checked yet
Adds a Sessions tab to each Identity Provider in the Aembit Tenant UI, listing active MCP user sessions with the ability to filter, revoke individual sessions, or revoke all sessions for a user or MCP client at once.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet Prompts to revoke active sessions when deleting an Identity Provider that has sessions tied to an OIDC OIDC OpenID Connect, a sign-in protocol built on OAuth 2.0. An application uses identity information from a trusted provider instead of maintaining a separate password for each user. ID Token Credential Provider with Enable Refresh Token Support turned on. Not checked yet Credential Provider fields that take a Literal or Dynamic value now validate the value against its type — Aembit rejects saves (including via the API or Terraform) when a Literal value contains a ${...} expression or a Dynamic value contains no valid ${...} expression. Not checked yet Entering a ${...} expression in a Credential Provider field in the Tenant UI automatically switches the field to Dynamic mode. Not checked yet
3 more in Everything
└──▷ BREAKING ON UPGRADE
! Aembit now rejects saves of Credential Provider configurations (including via the API or Terraform) where a Literal value contains a ${...} expression or a Dynamic value contains no valid ${...} expression — existing configurations with this mismatch will fail on next save.
Agent Proxy now injects credentials for MCP MCP Model Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. traffic; MCP Identity Gateway gains prompt/resource aggregation, conflict detection, and revised timeout and metric semantics.
New supported platform Agent Proxy (1.34.6014) injects credentials for Server Workloads whose application protocol is MCP, handling the traffic as HTTP — earlier versions passed MCP traffic through without credential injection. Not checked yet Updated integration New supported platform MCP Identity Gateway lists prompts and resources from every assigned MCP server, routes task requests to the originating MCP server, and prefixes prompt and resource names with the Server Workload they came from. Not checked yet MCP Identity Gateway detects conflicting tool and prompt name prefixes when two Server Workloads assigned to the same MCP client produce the same name, omits both from the client's lists, and logs the conflict. Not checked yet Extends AEMBIT_MCP_GATEWAY_TIMEOUT with seven additional timeout names that tune prompts/list fanout, the fan-out cap, upstream calls, upstream session caching, and Multi Round-Trip Request backoff. Not checked yet aembit_mcp_gateway_mcp_request_duration_seconds now measures only time MCP Identity Gateway spends processing a request, excluding time spent waiting on MCP servers. Not checked yet
+1 more
show less
Agent Proxy (1.34.5755+) retrieves and injects credentials for Access Policies whose Credential Provider uses Private Network Access. Not checked yet
6 details in Everything
└──▷ BREAKING ON UPGRADE
! In MCP Identity Gateway, aembit_mcp_gateway_mcp_request_duration_seconds now excludes time spent waiting on MCP servers — expect lower values; review and update any alerts or dashboards built on this metric.! The timeout names initialize, notifications_initialized, proactive_tools_list, reinit_initialize, reinit_notifications_initialized, and reinit_tools_list in AEMBIT_MCP_GATEWAY_TIMEOUT no longer take effect; replace them with upstream_call_timeout or the matching list timeout.
Personal AI Agents Are Here, and Aembit Customers Can Secure Them Today (2026-10-05)
Oct 5, 2026
·
issue 096
Aembit now gives personal AI agents distinct agentic identities, just-in-time scoped credentials, a per-agent kill switch, and centralized audit logging at no extra cost.
New integration Updated integration Assigns each personal AI agent its own distinct agentic identity — separate from the sponsoring employee's login — so credentials can be issued, scoped, and revoked independently. Not checked yet Issues just-in-time, short-lived, scoped credentials to personal AI agents at the moment of each access request, eliminating standing credentials that can leak or be reused. Not checked yet Provides a per-agent kill switch that revokes all access for a specific agent instantly across connected services without disrupting the employee. Not checked yet Centralizes audit logging for every agent access decision, capturing which agent acted, on whose behalf, what it touched, and which policy permitted the request. Not checked yet
4 details in Everything
Aembit Launches Identity and Access Security Controls for Meta Muse (2026-10-05)
Oct 5, 2026
·
issue 095
Aembit adds Meta Muse support, brokering short-lived credentials through its MCP MCP Model Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. Identity Gateway and MCP Authorization Server.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ USE IT
Configure the Muse skill file so the agent can list and invoke tools through the Aembit MCP Identity Gateway using short-lived credentials.
~/workspace/skills/aembit-mcp-gateway/bin/mcp.py
copy
CREDENTIAL_NAME = "custom.aembit-mcp-gateway"
MCP_URL = "https://<tenant>.mcpgateway.aembit.io/mcp"
ALLOWED_HOSTS = ["<tenant>.mcpgateway.aembit.io", "<tenant>.id.useast2.aembit.io"]
Verify the Muse-to-gateway connection and confirm tool availability by calling tools/list after the OAuth flow completes.
📍 In the Muse chat window, type: 'connect my Aembit MCP gateway'. After Dynamic Client Registration and the OAuth flow complete, Muse will invoke tools/list against https://<tenant>.mcpgateway.aembit.io/mcp and return the available tools (e.g. 49 tools for GitHub).
Adds Meta Muse as a supported client workload in Aembit's IAM IAM Identity and Access Management — a framework of policies and services for controlling who can authenticate to systems and what resources they are authorized to use, letting cyber tools enforce least-privilege and audit access. for Agentic AI Platform, routing Muse's enterprise resource requests through the MCP Identity Gateway and MCP Authorization Server for policy-evaluated, short-lived credential issuance.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet Supports Meta Muse Dynamic Client Registration against the Aembit authorization server — no manual app creation, client ID, or secret required. Not checked yet Enables Muse to connect to the MCP Identity Gateway by requesting the gateway URL as an OAuth scope, matching the gateway's protected-resource metadata advertisement. Not checked yet Generates a reusable Muse skill file (e.g. ~/workspace/skills/aembit-mcp-gateway/bin/mcp.py) using CREDENTIAL_NAME, MCP_URL, and ALLOWED_HOSTS constants, enabling persistent tools/list and tools/call invocations through the gateway. Not checked yet Provides MCP Authorization Tracing to diagnose authorization flow issues during Muse-to-gateway setup. Not checked yet
+1 more
show less
Extends centralized access policy management to cover Meta Muse alongside Microsoft Copilot Studio, Claude, ChatGPT, Gemini, and custom LLM LLM A large language model, a neural network trained on large amounts of text to recognize patterns and generate language. Applications use it for tasks such as answering, summarizing and writing code. -based agents under a single policy model. Not checked yet
Adds Meta Muse as a supported client workload in Aembit's IAM IAM Identity and Access Management — a framework of policies and services for controlling who can authenticate to systems and what resources they are authorized to use, letting cyber tools enforce least-privilege and audit access. for Agentic AI Platform, routing Muse's enterprise resource requests through the MCP Identity Gateway and MCP Authorization Server for policy-evaluated, short-lived credential issuance.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet Supports Meta Muse Dynamic Client Registration against the Aembit authorization server — no manual app creation, client ID, or secret required. Not checked yet Enables Muse to connect to the MCP Identity Gateway by requesting the gateway URL as an OAuth scope, matching the gateway's protected-resource metadata advertisement. Not checked yet Generates a reusable Muse skill file (e.g. ~/workspace/skills/aembit-mcp-gateway/bin/mcp.py) using CREDENTIAL_NAME, MCP_URL, and ALLOWED_HOSTS constants, enabling persistent tools/list and tools/call invocations through the gateway. Not checked yet Provides MCP Authorization Tracing to diagnose authorization flow issues during Muse-to-gateway setup. Not checked yet
1 more in Everything
Aembit: Adds ${saml.response.subject.nameId}, ${saml.response.issuer}, and ${saml.response.attributes['<name>']} expressions so OAuth 2.0 OAuth 2.0 An open authorization framework (IETF RFC 6749) that lets a service grant limited API access to a third party without sharing credentials, giving cyber tools a standard way to authenticate against external platforms. Authorization Code Credential Provider dynamic claims can read values from a SAML 2.0 SAML 2.0 A standard for passing signed identity assertions between a sign-in provider and an application. It lets a user sign in through their organization's identity provider. response, binding each issued credential to the individual SAML SAML A standard for passing signed identity assertions between a sign-in provider and an application. It lets a user sign in through their organization's identity provider. user's identity.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ USE IT
Issue mTLS mTLS Mutual TLS, an encrypted connection where both client and server present certificates to prove their identity. It helps services verify who they are communicating with. certificates to a Kubernetes workload without the private key ever leaving the cluster — set credentialType: X509Svid on a refresh schedule and Secrets Operator handles CSR CSR A Certificate Signing Request is a block of encoded data submitted to a certificate authority, containing a public key and identity details, so the CA can issue a signed TLS certificate without ever seeing the private key. submission and auto-renewal.
yaml
copy
credentialType: X509Svid
Bind a SAML user's group membership into a dynamically issued credential so each user gets a credential scoped to their own identity.
text
copy
${saml.response.attributes['groups']}
Adds credentialType: X509Svid to AembitSecretRefreshSchedule so Aembit Secrets Operator generates a private key in-cluster, obtains a signed certificate from Aembit, and writes both to a kubernetes.io/tls Secret (tls.crt and tls.key) for mutual TLS mutual TLS Mutual TLS, an encrypted connection where both client and server present certificates to prove their identity. It helps services verify who they are communicating with. ; the private key never leaves the cluster and certificates renew automatically. Not checked yet Enables the MCP MCP Model Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. Enterprise Managed Access Token Credential Provider in the Aembit Tenant UI, obtaining per-user MCP server access tokens access tokens A credential that authorizes a client to use a service or API. It usually has limited permissions and a lifetime; anyone holding it may be able to use those permissions. through a corporate identity provider identity provider A service that authenticates users and supplies identity information to other applications. It is the sign-in authority behind many single sign-on systems. so users reach MCP servers behind the MCP Identity Gateway without a per-user consent prompt. Not checked yet Records MCP tool filtering decisions — which control decided the outcome, which rules matched, which tools were removed, and the return count — under application.mcp.contentSecurity in MCP workload authorization events. Not checked yet Allows a Kubernetes Service Account Trust Provider to accept multiple OIDC OIDC OpenID Connect, a sign-in protocol built on OAuth 2.0. An application uses identity information from a trusted provider instead of maintaining a separate password for each user. endpoints (one per cluster issuer URL, added via Add an Endpoint ), enabling attestation of a single Client Workload running active-active across two or more clusters. Not checked yet
Adds credentialType: X509Svid to AembitSecretRefreshSchedule so Aembit Secrets Operator generates a private key in-cluster, obtains a signed certificate from Aembit, and writes both to a kubernetes.io/tls Secret (tls.crt and tls.key) for mutual TLS mutual TLS Mutual TLS, an encrypted connection where both client and server present certificates to prove their identity. It helps services verify who they are communicating with. ; the private key never leaves the cluster and certificates renew automatically. Not checked yet Enables the MCP MCP Model Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. Enterprise Managed Access Token Credential Provider in the Aembit Tenant UI, obtaining per-user MCP server access tokens access tokens A credential that authorizes a client to use a service or API. It usually has limited permissions and a lifetime; anyone holding it may be able to use those permissions. through a corporate identity provider identity provider A service that authenticates users and supplies identity information to other applications. It is the sign-in authority behind many single sign-on systems. so users reach MCP servers behind the MCP Identity Gateway without a per-user consent prompt. Not checked yet Records MCP tool filtering decisions — which control decided the outcome, which rules matched, which tools were removed, and the return count — under application.mcp.contentSecurity in MCP workload authorization events. Not checked yet
1 more in Everything
└──▷ BREAKING ON UPGRADE
! Switching an AembitSecretRefreshSchedule to or from credentialType: X509Svid deletes and recreates the target Kubernetes Secret, because X509Svid writes a kubernetes.io/tls Secret while every other credential type writes a generic Secret.
└──▷ USE IT
Issue mTLS mTLS Mutual TLS, an encrypted connection where both client and server present certificates to prove their identity. It helps services verify who they are communicating with. certificates to a Kubernetes workload without the private key ever leaving the cluster — Secrets Operator handles generation, signing, and renewal automatically.
yaml
copy
credentialType: X509Svid
Let a GitHub-hosted Actions runner pick a specific IAM IAM Identity and Access Management — a framework of policies and services for controlling who can authenticate to systems and what resources they are authorized to use, letting cyber tools enforce least-privilege and audit access. role when an Access Policy holds multiple AWS STS AWS STS AWS Security Token Service, an Amazon Web service that issues short-lived credentials for IAM roles, letting tools authenticate to AWS APIs without storing long-term secrets. Federation Credential Providers.
.github/workflows/deploy.yml
copy
- uses: aembit/aembit-github-action@v1.3.0
with:
aws-access-key-id: AKIA_PROD_DEPLOY
Bind a SAML SAML A standard for passing signed identity assertions between a sign-in provider and an application. It lets a user sign in through their organization's identity provider. user's identity into an OAuth 2.0 OAuth 2.0 An open authorization framework (IETF RFC 6749) that lets a service grant limited API access to a third party without sharing credentials, giving cyber tools a standard way to authenticate against external platforms. credential by reading their NameID and a group attribute directly from the SAML assertion.
📍 In the Aembit Tenant UI, open the OAuth 2.0 Authorization Code Credential Provider form, add a dynamic claim, and set its value to ${saml.response.subject.nameId} or ${saml.response.attributes['groups']}.
└──▷ BREAKING ON UPGRADE
! Switching an AembitSecretRefreshSchedule to or from credentialType: X509Svid deletes and recreates the target Kubernetes Secret (X509Svid writes a kubernetes.io/tls Secret; all other credential types write a generic Secret).
Aembit adds SAML SAML A standard for passing signed identity assertions between a sign-in provider and an application. It lets a user sign in through their organization's identity provider. -bound dynamic claims, X.509-SVID X.509-SVID An X.509 certificate formatted to carry a SPIFFE Verifiable Identity Document, binding a cryptographic identity to a workload so cyber tools can authenticate services without passwords or static secrets. delivery, multi-cluster Kubernetes attestation, MCP MCP Model Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. Tool Access Control, and AWS STS AWS STS AWS Security Token Service, an Amazon Web service that issues short-lived credentials for IAM roles, letting tools authenticate to AWS APIs without storing long-term secrets. provider selection in GitHub Actions GitHub Actions GitHub's built-in CI/CD system that runs automated workflows triggered by repository events, letting cyber tools automate testing, building, and releasing without managing separate pipeline infrastructure. .︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ USE IT
Issue mTLS mTLS Mutual TLS, an encrypted connection where both client and server present certificates to prove their identity. It helps services verify who they are communicating with. certificates to a workload without the private key ever leaving the cluster — Secrets Operator handles CSR CSR A Certificate Signing Request is a block of encoded data submitted to a certificate authority, containing a public key and identity details, so the CA can issue a signed TLS certificate without ever seeing the private key. generation and automatic renewal.
yaml
copy
credentialType: X509Svid
Bind a credential to the authenticated SAML user's identity in an OAuth 2.0 OAuth 2.0 An open authorization framework (IETF RFC 6749) that lets a service grant limited API access to a third party without sharing credentials, giving cyber tools a standard way to authenticate against external platforms. Authorization Code Credential Provider, so each user gets a token scoped to their own account.
yaml
copy
${saml.response.subject.nameId}
Let a GitHub-hosted Actions runner assume a specific IAM IAM Identity and Access Management — a framework of policies and services for controlling who can authenticate to systems and what resources they are authorized to use, letting cyber tools enforce least-privilege and audit access. role from an Access Policy that holds multiple AWS STS STS AWS Security Token Service, an Amazon Web Services API that issues short-lived credentials for IAM roles, letting cyber tools authenticate to AWS without storing long-term secrets. Federation Credential Providers, identified by Access Key ID selector.
copy
$ - uses: aembit/aembit-github-action@v1
with:
aws-access-key-id: AKIA<SELECTOR_FOR_TARGET_ROLE>
Adds aws-access-key-id input to the Aembit GitHub Action (minimum version 1.3.0) so a workflow on a GitHub-hosted runner can select among multiple AWS STS Federation Credential Providers in a single Access Policy by Access Key ID selector. Not checked yet Extends the Edge API credentials endpoint and Edge SDKs for TypeScript and Python (minimum Edge SDK 1.34.0) to pass an AWS STS Credential Provider selector as connection metadata alongside existing JWT JWT An open standard (RFC 7519) for encoding claims as a signed, optionally encrypted JSON object passed between parties. Cyber tools use it to verify identity and permissions without querying a central session store. Credential Provider selectors. Not checked yet Adds MCP Tool Access Control enforcement to the MCP Identity Gateway (version 1.34.5794): Tool Visibility controls which MCP tools an AI agent discovers, Tool Invocation controls which it can call, and both accept exact tool names or case-sensitive glob patterns. Not checked yet Adds application.mcp.contentSecurity fields to MCP workload authorization events, recording which control decided a tool's fate, which rules matched, which tools a listing removed, and how many it returned. Not checked yet Adds Agent Controller support for Kerberos Kerberos A network authentication protocol that uses tickets issued by a trusted service. Users and services can prove their identities without sending a password to each application. Trust Provider attestation requests from Agent Proxy when running on AWS EC2 EC2 Amazon's cloud virtual-machine service, letting tools run on-demand servers without managing physical hardware. instances (version 1.34.3725). Not checked yet
+2 more
show less
Adds Windows certificate chain validation to Agent Controller: intermediate CA certificates from its TLS certificate chain are now installed into the LocalMachine certificate store so Windows TLS clients can validate the full chain. Not checked yet Populates user first and last names from OIDC OIDC OpenID Connect, a sign-in protocol built on OAuth 2.0. An application uses identity information from a trusted provider instead of maintaining a separate password for each user. profile claims (given_name, family_name, falling back to name) when Aembit creates a user through single sign-on single sign-on Single sign-on, using one identity provider to sign in to multiple applications. It reduces separate passwords and centralizes account and access management. . Not checked yet
Adds MCP Tool Access Control enforcement to the MCP Identity Gateway (version 1.34.5794): Tool Visibility controls which MCP tools an AI agent discovers, Tool Invocation controls which it can call, and both accept exact tool names or case-sensitive glob patterns. Not checked yet Adds application.mcp.contentSecurity fields to MCP workload authorization events, recording which control decided a tool's fate, which rules matched, which tools a listing removed, and how many it returned. Not checked yet
5 more in Everything
└──▷ BREAKING ON UPGRADE
! Switching an AembitSecretRefreshSchedule to or from credentialType: X509Svid deletes and recreates the target Kubernetes Secret (X509Svid writes a kubernetes.io/tls Secret; all other types write a generic Secret).
Aembit: Aembit now reads given_name, family_name, and name OIDC OIDC OpenID Connect, a sign-in protocol built on OAuth 2.0. An application uses identity information from a trusted provider instead of maintaining a separate password for each user. profile claims when provisioning users through single sign-on single sign-on Single sign-on, using one identity provider to sign in to multiple applications. It reduces separate passwords and centralizes account and access management. , populating first and last names automatically.
└──▷ USE IT
Deliver a mutual-TLS certificate to a workload in-cluster — Secrets Operator keeps the private key local and auto-renews before expiry.
yaml
copy
credentialType: X509Svid
Bind an OAuth 2.0 OAuth 2.0 An open authorization framework (IETF RFC 6749) that lets a service grant limited API access to a third party without sharing credentials, giving cyber tools a standard way to authenticate against external platforms. credential to the calling SAML SAML A standard for passing signed identity assertions between a sign-in provider and an application. It lets a user sign in through their organization's identity provider. user's identity so each token is scoped to that user — useful when users authenticate through the MCP MCP Model Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. Identity Gateway.
text
copy
${saml.response.subject.nameId}
└──▷ BREAKING ON UPGRADE
! Switching an AembitSecretRefreshSchedule to or from credentialType: X509Svid deletes and recreates the target Kubernetes Secret, because X509Svid writes a kubernetes.io/tls Secret while every other credential type writes a generic Secret.
Aembit adds Okta Cross App Access support via a new Enterprise-Managed Authorization Credential Provider for AI agent identity.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Adds an Enterprise-Managed Authorization Credential Provider that implements the Model Context Protocol Model Context Protocol Model Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. Working Group's Enterprise-Managed Authorization extension, enabling Okta Cross App Access (XAA) for AI agents without per-service consent steps.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet Extends policy-based access enforcement and auditability to Okta XAA-driven agent connections, letting security teams centrally control which agents act on whose behalf and under what policy. Not checked yet Supports XAA alongside existing OAuth authorization capabilities, allowing organizations to adopt Cross App Access incrementally as ecosystem support expands rather than requiring an all-or-nothing migration. Not checked yet Provides a common enforcement point for AI agent access to MCP MCP Model Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. servers, tools, and enterprise resources across both XAA and OAuth environments. Not checked yet
Adds an Enterprise-Managed Authorization Credential Provider that implements the Model Context Protocol Model Context Protocol Model Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. Working Group's Enterprise-Managed Authorization extension, enabling Okta Cross App Access (XAA) for AI agents without per-service consent steps.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet Supports XAA alongside existing OAuth authorization capabilities, allowing organizations to adopt Cross App Access incrementally as ecosystem support expands rather than requiring an all-or-nothing migration. Not checked yet
2 more in Everything
Aembit adds SAML SAML A standard for passing signed identity assertions between a sign-in provider and an application. It lets a user sign in through their organization's identity provider. dynamic claims, multi-cluster OIDC OIDC OpenID Connect, a sign-in protocol built on OAuth 2.0. An application uses identity information from a trusted provider instead of maintaining a separate password for each user. trust, MCP MCP Model Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. Enterprise tokens, and X.509-SVID X.509-SVID An X.509 certificate formatted to carry a SPIFFE Verifiable Identity Document, binding a cryptographic identity to a workload so cyber tools can authenticate services without passwords or static secrets. delivery via Secrets Operator︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ USE IT
Deliver a mutual-TLS certificate to a Kubernetes workload without the private key ever leaving the cluster.
yaml
copy
credentialType: X509Svid
Bind an issued OAuth 2.0 OAuth 2.0 An open authorization framework (IETF RFC 6749) that lets a service grant limited API access to a third party without sharing credentials, giving cyber tools a standard way to authenticate against external platforms. credential to the authenticated SAML user's group membership, so different users get scoped tokens.
text
copy
${saml.response.attributes['groups']}
Adds credentialType: X509Svid to AembitSecretRefreshSchedule so Secrets Operator generates a private key inside the cluster, obtains a signed certificate from Aembit, and writes both to a kubernetes.io/tls Secret (fields tls.crt and tls.key) for mutual TLS mutual TLS Mutual TLS, an encrypted connection where both client and server present certificates to prove their identity. It helps services verify who they are communicating with. — private key never leaves the cluster, and the certificate is renewed automatically before expiry.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet Adds three SAML 2.0 SAML 2.0 A standard for passing signed identity assertions between a sign-in provider and an application. It lets a user sign in through their organization's identity provider. dynamic-claim expressions — ${saml.response.subject.nameId}, ${saml.response.issuer}, and ${saml.response.attributes['<name>']} — to the OAuth 2 OAuth 2 An open authorization framework (RFC 6749) that lets a service grant limited access to a user's resources on another service without exposing credentials, giving cyber tools a standard way to authenticate against third-party APIs. .0 Authorization Code Credential Provider, binding issued credentials to the individual SAML user's identity. Not checked yet Adds support for multiple OIDC Endpoints in a single Kubernetes Service Account Trust Provider, enabling attestation of a client workload running active-active across two or more clusters, each with its own signing key. Not checked yet Adds the MCP Enterprise Managed Access Token Credential Provider in the Aembit Tenant UI, obtaining per-user MCP server access tokens access tokens A credential that authorizes a client to use a service or API. It usually has limited permissions and a lifetime; anyone holding it may be able to use those permissions. through a corporate identity provider identity provider A service that authenticates users and supplies identity information to other applications. It is the sign-in authority behind many single sign-on systems. so users reach MCP servers behind the MCP Identity Gateway without a per-user consent prompt. Not checked yet
Adds credentialType: X509Svid to AembitSecretRefreshSchedule so Secrets Operator generates a private key inside the cluster, obtains a signed certificate from Aembit, and writes both to a kubernetes.io/tls Secret (fields tls.crt and tls.key) for mutual TLS mutual TLS Mutual TLS, an encrypted connection where both client and server present certificates to prove their identity. It helps services verify who they are communicating with. — private key never leaves the cluster, and the certificate is renewed automatically before expiry.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet Adds three SAML 2.0 SAML 2.0 A standard for passing signed identity assertions between a sign-in provider and an application. It lets a user sign in through their organization's identity provider. dynamic-claim expressions — ${saml.response.subject.nameId}, ${saml.response.issuer}, and ${saml.response.attributes['<name>']} — to the OAuth 2 OAuth 2 An open authorization framework (RFC 6749) that lets a service grant limited access to a user's resources on another service without exposing credentials, giving cyber tools a standard way to authenticate against third-party APIs. .0 Authorization Code Credential Provider, binding issued credentials to the individual SAML user's identity. Not checked yet Adds the MCP Enterprise Managed Access Token Credential Provider in the Aembit Tenant UI, obtaining per-user MCP server access tokens access tokens A credential that authorizes a client to use a service or API. It usually has limited permissions and a lifetime; anyone holding it may be able to use those permissions. through a corporate identity provider identity provider A service that authenticates users and supplies identity information to other applications. It is the sign-in authority behind many single sign-on systems. so users reach MCP servers behind the MCP Identity Gateway without a per-user consent prompt. Not checked yet
1 more in Everything
└──▷ BREAKING ON UPGRADE
! Switching an AembitSecretRefreshSchedule to or from credentialType: X509Svid deletes and recreates the target Kubernetes Secret (type changes between kubernetes.io/tls and generic), which will break workloads that reference the existing Secret during the transition.
Kubernetes Service Account Trust Provider now supports multiple OIDC endpoints
Sep 23, 2026
· release notes
Kubernetes Service Account Trust Provider adds support for multiple OIDC OIDC OpenID Connect, a sign-in protocol built on OAuth 2.0. An application uses identity information from a trusted provider instead of maintaining a separate password for each user. endpoints to validate tokens across active-active clusters.
Adds the ability to configure multiple OIDC Endpoint values in a single Trust Provider via the Add an Endpoint action, allowing validation of service account tokens signed by different cluster issuers. Not checked yet
1 detail in Everything
Dynamic claims now support SAML assertions
Sep 23, 2026
· release notes
Dynamic claims in Aembit now support SAML SAML A standard for passing signed identity assertions between a sign-in provider and an application. It lets a user sign in through their organization's identity provider. assertions via new expressions
└──▷ TRY IT
Bind an issued credential to the user's unique identity found in the SAML NameID field.
copy
$ ${saml.response.subject.nameId}
Read the identity provider identity provider A service that authenticates users and supplies identity information to other applications. It is the sign-in authority behind many single sign-on systems. that issued the SAML assertion.
copy
$ ${saml.response.issuer}
Adds ${saml.response.subject.nameId} expression to dynamic claims to return the Subject NameID from a SAML response. Not checked yet Adds ${saml.response.issuer} expression to dynamic claims to return the identity provider issuer from a SAML assertion. Not checked yet Adds ${saml.response.attributes['<name>']} expression to dynamic claims to return specific attributes (e.g., groups) from a SAML assertion. Not checked yet
3 details in Everything
Automatic user creation reads user names from more claims
Sep 23, 2026
· release notes
Aembit reads user first/last names from OIDC OIDC OpenID Connect, a sign-in protocol built on OAuth 2.0. An application uses identity information from a trusted provider instead of maintaining a separate password for each user. given_name and family_name claims during SSO SSO Single sign-on, using one identity provider to sign in to multiple applications. It reduces separate passwords and centralizes account and access management. auto-creation
New: given_name and family_name are now read as the primary source for user first and last names during automatic SSO user creation, with fallback to the name claim if either is missing. Not checked yet Enhanced: User name resolution logic in automatic SSO user creation now explicitly supports standard OpenID Connect OpenID Connect OpenID Connect, a sign-in protocol built on OAuth 2.0. An application uses identity information from a trusted provider instead of maintaining a separate password for each user. (OIDC) profile claims. Not checked yet
2 details in Everything
How Aembit Makes Cross App Access Usable Before the Rest of the Stack Catches Up (2026-09-22)
Sep 22, 2026
·
issue 083
Aembit launches Enterprise-Managed Authorization Credential Provider to broker XAA/EMA for AI agents against SaaS SaaS Software delivered over the internet and billed by subscription, hosted and operated by the vendor so the buyer skips installation and infrastructure management. MCP MCP Model Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. servers︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Adds a new Enterprise-Managed Authorization (EMA) Credential Provider that captures a user's SSO SSO Single sign-on, using one identity provider to sign in to multiple applications. It reduces separate passwords and centralizes account and access management. ID token and refresh token refresh token A credential used to obtain a new access token without signing in again. It is sent to the authorization service rather than used directly to call the protected API. (requiring the offline_access scope) at login, refreshes them in the background, and performs a dual token exchange token exchange An OAuth 2.0 protocol extension (RFC 8693) that lets a service trade one token for another with different scopes, audience, or type, enabling delegation and impersonation across service boundaries without re-authenticating the user. at request time so AI agents can access downstream MCP servers without per-app OAuth consent screens.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet Aembit's Edge Controller brokers XAA between identity providers identity providers A service that authenticates users and supplies identity information to other applications. It is the sign-in authority behind many single sign-on systems. and upstream MCP servers that don't yet support XAA natively — generating and signing assertions using the tenant's own keys when the IdP IdP A service that authenticates users and supplies identity information to other applications. It is the sign-in authority behind many single sign-on systems. cannot perform the exchange directly. Not checked yet Automatically falls back to the standard OAuth Authorization Code flow for any upstream MCP server or identity provider identity provider A service that authenticates users and supplies identity information to other applications. It is the sign-in authority behind many single sign-on systems. that doesn't support XAA, requiring no separate configuration. Not checked yet
Adds a new Enterprise-Managed Authorization (EMA) Credential Provider that captures a user's SSO SSO Single sign-on, using one identity provider to sign in to multiple applications. It reduces separate passwords and centralizes account and access management. ID token and refresh token refresh token A credential used to obtain a new access token without signing in again. It is sent to the authorization service rather than used directly to call the protected API. (requiring the offline_access scope) at login, refreshes them in the background, and performs a dual token exchange token exchange An OAuth 2.0 protocol extension (RFC 8693) that lets a service trade one token for another with different scopes, audience, or type, enabling delegation and impersonation across service boundaries without re-authenticating the user. at request time so AI agents can access downstream MCP servers without per-app OAuth consent screens.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet Aembit's Edge Controller brokers XAA between identity providers identity providers A service that authenticates users and supplies identity information to other applications. It is the sign-in authority behind many single sign-on systems. and upstream MCP servers that don't yet support XAA natively — generating and signing assertions using the tenant's own keys when the IdP IdP A service that authenticates users and supplies identity information to other applications. It is the sign-in authority behind many single sign-on systems. cannot perform the exchange directly. Not checked yet
1 more in Everything
Aembit adds MCP MCP Model Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. Tool Access Control and CrowdStrike AIDR integration for governing AI agent tool access︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Adds MCP Tool Access Control Content Security Provider with independent Tool Visibility (controls which MCP tools an agent can discover in a listing) and Tool Invocation (controls which MCP tools an agent can call) controls, configurable per Access Policy via glob-syntax tool name rules.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet Adds CrowdStrike AIDR as a Content Security Provider that inspects MCP tool calls and tool listings on both the request and response paths before forwarding to the MCP server or AI agent, applied via Access Policy. Not checked yet
2 details in Everything
Aembit adds multi-provider AWS STS AWS STS AWS Security Token Service, an Amazon Web service that issues short-lived credentials for IAM roles, letting tools authenticate to AWS APIs without storing long-term secrets. selection in GitHub Actions GitHub Actions GitHub's built-in CI/CD system that runs automated workflows triggered by repository events, letting cyber tools automate testing, building, and releasing without managing separate pipeline infrastructure. , MCP MCP Model Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. Tool Access Control enforcement, and glob-pattern tool filtering.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Adds aws-access-key-id input to the Aembit GitHub Action (minimum version 1.3.0) to name the Access Key ID selector of a specific AWS STS STS AWS Security Token Service, an Amazon Web Services API that issues short-lived credentials for IAM roles, letting cyber tools authenticate to AWS without storing long-term secrets. Federation Credential Provider within an Access Policy, letting GitHub-hosted runners reach any IAM IAM Identity and Access Management — a framework of policies and services for controlling who can authenticate to systems and what resources they are authorized to use, letting cyber tools enforce least-privilege and audit access. role without a self-hosted runner.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet The Edge API credentials endpoint now carries the AWS STS Credential Provider selector alongside selectors for multiple JWT JWT An open standard (RFC 7519) for encoding claims as a signed, optionally encrypted JSON object passed between parties. Cyber tools use it to verify identity and permissions without querying a central session store. Credential Providers, enabling direct programmatic selection. Not checked yet Edge SDKs for TypeScript and Python (minimum Edge SDK 1.34.0) accept the Credential Provider selector as connection metadata on the credential request. Not checked yet The MCP Identity Gateway (version 1.34.5794) now enforces MCP Tool Access Control, a Content Security Provider added to an Access Policy, controlling which MCP tools an AI agent can discover and invoke. Not checked yet MCP Tool Access Control entries accept exact tool names or case-sensitive glob patterns matched against the name the MCP server publishes. Not checked yet
+1 more
show less
Tool filtering decisions are recorded in application.mcp.contentSecurity fields on MCP workload events, capturing which control decided an MCP tool's fate, which rules matched, which tools a listing removed, and how many were returned. Not checked yet
Adds aws-access-key-id input to the Aembit GitHub Action (minimum version 1.3.0) to name the Access Key ID selector of a specific AWS STS STS AWS Security Token Service, an Amazon Web Services API that issues short-lived credentials for IAM roles, letting cyber tools authenticate to AWS without storing long-term secrets. Federation Credential Provider within an Access Policy, letting GitHub-hosted runners reach any IAM IAM Identity and Access Management — a framework of policies and services for controlling who can authenticate to systems and what resources they are authorized to use, letting cyber tools enforce least-privilege and audit access. role without a self-hosted runner.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet The MCP Identity Gateway (version 1.34.5794) now enforces MCP Tool Access Control, a Content Security Provider added to an Access Policy, controlling which MCP tools an AI agent can discover and invoke. Not checked yet MCP Tool Access Control entries accept exact tool names or case-sensitive glob patterns matched against the name the MCP server publishes. Not checked yet Tool filtering decisions are recorded in application.mcp.contentSecurity fields on MCP workload events, capturing which control decided an MCP tool's fate, which rules matched, which tools a listing removed, and how many were returned. Not checked yet
2 more in Everything
Aembit adds MCP MCP Model Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. Identity Gateway, MCP Authorization Server, Blended Identity, and an MCP Server MCP Server A process that exposes tools, resources, and prompts over Anthropic's Model Context Protocol, letting an AI agent call external APIs or local services through a standardised interface. for AI assistant-driven tenant management.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Adds the Aembit MCP Server, which exposes tenant configuration to MCP clients so practitioners can query and manage Aembit from an AI assistant, with a published Prompt Library and MCP Server Reference.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet
1 detail in Everything
Aembit introduces MCP MCP Model Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. Identity Gateway for managing AI agent identities.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Introduces MCP Identity Gateway, enabling identity management for AI agents whether user-driven (such as Claude Desktop) or autonomous services.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet
1 detail in Everything
Agent Controller restores Kerberos Kerberos A network authentication protocol that uses tickets issued by a trusted service. Users and services can prove their identities without sending a password to each application. attestation on EC2 EC2 Amazon's cloud virtual-machine service, letting tools run on-demand servers without managing physical hardware. , installs intermediate TLS certificates on Windows, and fixes service logon account handling.
Restores Kerberos Trust Provider attestation for Agent Controller on AWS EC2, fixing the HTTP 500 responses in version 1.32.3541. Not checked yet On Windows, Agent Controller now installs intermediate CA certificates from its TLS certificate chain into the LocalMachine certificate store Not checked yet
2 details in Everything
Aembit Secrets Operator now delivers X.509-SVID certificates
Sep 17, 2026
· release notes
Aembit Secrets Operator 1.34.358 adds X509Svid credential type for mTLS mTLS Mutual TLS, an encrypted connection where both client and server present certificates to prove their identity. It helps services verify who they are communicating with. via kubernetes.io/tls Secrets
Adds X509Svid as a new value for credentialType in AembitSecretRefreshSchedule to generate private keys and signed certificates inside the cluster Not checked yet Secrets Operator now writes certificates to kubernetes.io/tls Secret types (with tls.crt and tls.key fields) when using the X509Svid credential type Not checked yet Enables automatic certificate renewal for X.509-SVID X.509-SVID An X.509 certificate formatted to carry a SPIFFE Verifiable Identity Document, binding a cryptographic identity to a workload so cyber tools can authenticate services without passwords or static secrets. identities by refreshing secrets before expiration Not checked yet
3 details in Everything
Aembit Cloud enhances Content Security, Client Workload URI handling, Terraform integration for Trust Providers, and Authorization event filters.
Allow /Block switching in Content Security tool lists no longer clears your configuration; Remove Tools now requires a separate confirmation step to clear the list. Not checked yet Client Workload Redirect URI field now correctly handles pasted values without overwriting surrounding text and displays one validation message at a time. Not checked yet Terraform can now read the state of a Trust Provider secret when that provider belongs to a custom Resource Set . Not checked yet Authorization event date filters in Access Authorization Events now support a maximum timespan of 24 hours. Not checked yet
4 details in Everything
GitHub Actions now selects among multiple AWS STS Credential Providers
Sep 16, 2026
· release notes
Aembit GitHub Action now selects among multiple AWS STS AWS STS AWS Security Token Service, an Amazon Web service that issues short-lived credentials for IAM roles, letting tools authenticate to AWS APIs without storing long-term secrets. Credential Providers via a new input.
The aws-access-key-id input names the Access Key ID selector of the Credential Provider you want in the Aembit GitHub Action Not checked yet
1 detail in Everything
CrowdStrike AIDR Tells You What’s Risky. Aembit Tells You Who Gets Access. (2026-09-15)
Sep 15, 2026
·
issue 076
Aembit adds CrowdStrike AIDR as a Content Security capability attached to Access Policies, covering MCP MCP Model Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. tool listings, inputs, and outputs.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ HOW TO FIND IT
Attach CrowdStrike AIDR content inspection to a specific MCP Access Policy so that tool listings, inputs, and outputs are evaluated before the agent's request is allowed through.
📍 In the Aembit UI, open the target Access Policy, navigate to the Content Security section, select CrowdStrike AIDR as the provider, and enable the checkpoints (tool listings, tool inputs, tool outputs) you want evaluated. Save the policy — AIDR verdicts (allow/block/transform) will now be enforced inline for every MCP connection governed by that policy.
Adds Content Security as a new capability type on Aembit Access Policy objects, enabling administrators to attach a CrowdStrike AIDR content-security configuration to the same enforcement path that governs MCP access.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet Covers three MCP inspection checkpoints per policy — tool listings, tool inputs, and tool outputs — with AIDR returning an allow, block, or transform verdict that Aembit enforces inline. Not checked yet Correlates every CrowdStrike AIDR finding with Aembit's identity and policy context (agent, target MCP server, applicable policy, Content Security decision) in a single workload event. Not checked yet Makes the integration configurable through the Aembit UI, API, or Terraform with no changes required to existing AIDR console configuration. Not checked yet
4 details in Everything
MCP Identity Gateway 1.34.5794 release
Sep 15, 2026
· release notes
Adds MCP MCP Model Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. Tool Access Control enforcement with glob pattern support and detailed workload event logging under application.mcp.contentSecurity.
application.mcp.contentSecurity events now record which Tool Visibility or Invocation control decided an MCP tool’s fate, including matched rules and listing counts Not checked yet Tool Visibility and Tool Invocation controls now accept glob patterns for MCP tool names (case-sensitive matching against the server-published name) Not checked yet
2 details in Everything
Aembit adds Content Security Providers for MCP MCP Model Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. traffic, with CrowdStrike AIDR as the first supported provider.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Adds application.mcp.contentSecurity field to MCP workload events, recording each Content Security Provider decision per message.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet Adds Content Security Provider support to Access Policies, inserting an inspection step on tools/list and tools/call MCP methods before forwarding to MCP servers. Not checked yet Integrates CrowdStrike AIDR as the first Content Security Provider, enabling verdict-enforced inspection of MCP tool discovery and invocation traffic through the MCP Identity Gateway. Not checked yet
3 details in Everything
Aembit: Adds Content Security Providers to govern Model Context Protocol Model Context Protocol Model Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. (MCP MCP Model Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. ) tool traffic flowing through Aembit's MCP Identity Gateway, attached to an Access Policy via its optional Content Security component.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Integrates CrowdStrike AI Detection and Response (AIDR) as a Content Security Provider to inspect MCP tool messages in real time and return verdicts that Aembit enforces before messages continue. Not checked yet
1 detail in Everything
Aembit: Adds Content Security Providers to Access Policies, enabling evaluation and policy enforcement on MCP MCP Model Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. tool messages proxied through the MCP Identity Gateway before they continue.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Aembit adds a CLI for terminal-based credential retrieval, an MCP MCP Model Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. Identity Gateway for AI agent/MCP server policy enforcement, and updated edge components.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Introduces the Aembit CLI, a command-line tool for fetching credentials to access Server Workloads directly from a terminal, available for Linux amd64 (musl and glibc), Linux arm64, and Windows amd64.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet Introduces the MCP Identity Gateway, a data-plane gateway between AI agents and MCP servers that enforces Access Policies on every connection, available for Linux amd64 and Linux arm64. Not checked yet Adds the Agent Controller edge component, which brokers registration between Agent Proxies and Aembit Cloud, available for Linux amd64 and Windows amd64. Not checked yet Adds the Agent Proxy edge component, which intercepts Client Workload traffic and injects credentials to enforce Access Policies, available for Linux amd64 and Windows amd64. Not checked yet
4 details in Everything
Aembit integrates with CrowdStrike Falcon AIDR to enforce detection and response policies on MCP MCP Model Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. transactions via the Aembit MCP Identity Gateway.
New integration with CrowdStrike Falcon AI Detection and Response (AIDR) enables inspection of MCP tool listings, inputs, and outputs for AI agent traffic governed by Aembit. Not checked yet Aembit MCP Identity Gateway allows centrally pre-configured CrowdStrike AIDR policies to be applied across all MCP clients without per-client configuration or custom agent-side inspection logic. Not checked yet Configurable policies on MCP interactions support allow, report, block, or transform actions based on identity context and risks identified by CrowdStrike AIDR. Not checked yet Aembit supplies run-time identities for user-delegated and autonomous agents to CrowdStrike AIDR, enriching AIDR policy decisions with workload identity workload identity An identity assigned to software, such as a service or container, rather than a person. It lets the workload authenticate and receive permissions without sharing a user's credentials. context. Not checked yet CrowdStrike AIDR findings now link directly to corresponding Aembit access records, enabling investigators to pivot between platforms without manually reconciling separate logs. Not checked yet
5 details in Everything
Aembit + CrowdStrike: More Judgment Behind Every AI Agent “Yes” (2026-09-01)
Sep 1, 2026
·
issue 061
Aembit integrates CrowdStrike AIDR into MCP MCP Model Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. access policies to inspect tool listings, inputs, and outputs for AI agents.
└──▷ HOW TO FIND IT
Attach a CrowdStrike AIDR content security configuration to a sensitive MCP access policy via the Aembit UI so that tool listings, inputs, and outputs are inspected before reaching your AI agent.
📍 In the Aembit console, open the target Access Policy › Content Security › attach a CrowdStrike AIDR content security configuration › set fail behavior to fail-closed › Save.
Adds a CrowdStrike AIDR content security configuration attachment to Aembit access policies, enabling MCP traffic inspection (tool listings, tool inputs, tool outputs) from the same control plane that handles identity and credential issuance. Not checked yet Supports configurable fail-open or fail-closed behavior per access policy when CrowdStrike AIDR is unreachable, with every failure recorded as a workload event. Not checked yet Inspection is opt-in per access policy — only the policies you explicitly configure with a CrowdStrike AIDR content security configuration trigger MCP content checks; all others continue to work unchanged. Not checked yet Based on AIDR's decision, Aembit allows, blocks, or forwards a transformed version of MCP content (e.g., sensitive data redacted or defanged), with the outcome logged as a workload event tied to the agent identity, target MCP server, and access policy. Not checked yet New integration is configurable through the Aembit UI, API, or Terraform; requires a CrowdStrike AIDR for Agents subscription. Not checked yet
5 details in Everything
Aembit adds Edge SDK (TypeScript & Python), glibc amd64 CLI build, and authorizationChain field in Agent Proxy workload events.
└──▷ TRY IT
Apply gRPC gRPC An open-source remote procedure call framework from Google that uses HTTP/2 and Protocol Buffers to let services call each other's functions across a network, giving tools low-latency, strongly typed inter-process communication. keep-alive settings at install time on Windows so the CLI maintains its tenant connection over idle periods.
copy
$ msiexec /i AembitCLI.msi AEMBIT_TENANT_GRPC_PING_INTERVAL_SECS=30 AEMBIT_TENANT_GRPC_PING_TIMEOUT_SECS=10
Adds authorizationChain field to Agent Proxy workload events — an ordered list of context IDs for the authorization events behind a request, enabling full trace-back to the directive and credential retrievals. Not checked yet Adds severity, outcome.result, and outcome.reason fields to response events when Aembit answers in place of the Server Workload, so the outcome is no longer cleared between request and response. Not checked yet Windows MSI installer now applies AEMBIT_TENANT_GRPC_PING_INTERVAL_SECS and AEMBIT_TENANT_GRPC_PING_TIMEOUT_SECS when passed as install-time properties. Not checked yet Linux installer script now validates Agent Proxy arguments — including numeric environment variables such as AEMBIT_HTTP_IDLE_TIMEOUT_SECS — before installation proceeds. Not checked yet Introduces the Aembit Edge SDK (TypeScript and Python): in-process libraries that handle workload attestation, token lifecycle, and credential retrieval with no proxy required, suited for serverless functions, ephemeral CI containers, and restricted runtimes. Not checked yet
+4 more
show less
Edge SDK supports seven Trust Providers: AWS Metadata Service, AWS Role, Azure Instance Metadata Service, GCP Identity Token, GitHub, GitLab, and OIDC OIDC OpenID Connect, a sign-in protocol built on OAuth 2.0. An application uses identity information from a trusted provider instead of maintaining a separate password for each user. ID Token. Not checked yet Provides Edge SDK integration guides for four platforms: AWS EC2 EC2 Amazon's cloud virtual-machine service, letting tools run on-demand servers without managing physical hardware. , AWS Lambda, GCP Cloud Run Cloud Run Google's managed container runtime that executes stateless workloads on demand, scaling to zero when idle, so tools can deploy without managing servers or paying for idle capacity. , and Vercel OIDC. Not checked yet Adds aembit_agent_cli_linux_amd64_glibc_<version>.tar.gz as a second Linux amd64 archive in Aembit CLI 1.34.5772, dynamically linking against glibc 2.28 or newer, for organizations whose policy requires glibc or to work around DNS resolution issues caused by musl's stricter handling of resolver responses. Not checked yet Consolidates API Guide, CLI Guide, and Edge SDK documentation into a single Developer Guide under /dev-guide/, with a side-by-side credential-path comparison of Agent Proxy, Edge SDK, Aembit CLI, and Edge API. Not checked yet
9 details in Everything
Edge components release with Agent Proxy fixes and expanded workload events
Aug 27, 2026
· release notes
Agent Proxy workload events now include authorizationChain and outcome fields; Windows installer supports gRPC gRPC An open-source remote procedure call framework from Google that uses HTTP/2 and Protocol Buffers to let services call each other's functions across a network, giving tools low-latency, strongly typed inter-process communication. keep-alive properties.
authorizationChain field added to Agent Proxy workload events for tracing authorization context IDs. Not checked yet Aembit-generated response events now report outcome.result, outcome.reason, and severity fields instead of clearing them. Not checked yet
2 details in Everything
Aembit Edge SDKs for TypeScript and Python now available
Aug 27, 2026
· release notes
Aembit Edge SDKs for TypeScript and Python now available for direct credential retrieval
Adds TypeScript and Python Edge SDK libraries for direct credential retrieval without hand-written HTTP requests or token lifecycle management. Not checked yet Supports workload attestation via seven Trust Providers: AWS Metadata Service, AWS Role, Azure Instance Metadata Service, GCP Identity Token, GitHub, GitLab, and OIDC OIDC OpenID Connect, a sign-in protocol built on OAuth 2.0. An application uses identity information from a trusted provider instead of maintaining a separate password for each user. ID Token. Not checked yet
2 details in Everything
Google Cloud Identity-Aware Proxy (IAP) JWT Trust Provider now available
Aug 19, 2026
· release notes
Adds GCP IAP JWT JWT An open standard (RFC 7519) for encoding claims as a signed, optionally encrypted JSON object passed between parties. Cyber tools use it to verify identity and permissions without querying a central session store. Trust Provider with Terraform support for validating IAP-signed tokens
Introduces the GCP IAP JWT Trust Provider type to validate signed x-goog-iap-jwt-assertion tokens from Google Cloud IAP on GKE GKE Google Kubernetes Engine, Google's managed Kubernetes service, which lets cyber tools run containerized workloads without managing the underlying cluster infrastructure. , Cloud Run Cloud Run Google's managed container runtime that executes stateless workloads on demand, scaling to zero when idle, so tools can deploy without managing servers or paying for idle capacity. , or App Engine. Not checked yet Enables match rules on token claims aud, iss, sub, and email, plus any additional claim via the custom_claim attribute. Not checked yet Enables management of the GCP IAP JWT Trust Provider through the Aembit Terraform provider using aembit_trust_provider. Not checked yet
3 details in Everything
MCP Identity Gateway 1.34.5733 release
Aug 18, 2026
· release notes
MCP MCP Model Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. Identity Gateway 1.34.5733 adds nine Prometheus metrics for fanout and auth visibility
Exposes nine new Prometheus metrics tracking upstream fanout behavior, authentication failures, JWKS JWKS A JSON Web Key Set, a published collection of cryptographic keys. Applications use it to find the public key needed to verify a token's signature. refreshes, session cleanup, and readiness probe stability. Not checked yet Updates the Gateway's metrics reference to document all 20 MCP-specific metrics with types, labels, and label values. Not checked yet
2 details in Everything
OpenAI Workload Identity Federation: Aembit Brings Secretless Access to the OpenAI API (2026-08-17)
Aug 17, 2026
·
issue 054
Aembit Cloud v1.33 adds an OpenAI WIF WIF Workload Identity Federation is a Google Cloud mechanism that lets external workloads authenticate to Google APIs using short-lived tokens from a trusted identity provider, eliminating the need to manage long-lived service account keys. credential provider for secretless, keyless ChatGPT API access via federated OIDC OIDC OpenID Connect, a sign-in protocol built on OAuth 2.0. An application uses identity information from a trusted provider instead of maintaining a separate password for each user. tokens.
Adds the OpenAI WIF credential provider in Aembit Cloud v1.33, enabling workloads to authenticate to the OpenAI ChatGPT API with short-lived, scoped access tokens access tokens A credential that authorizes a client to use a service or API. It usually has limited permissions and a lifetime; anyone holding it may be able to use those permissions. instead of static sk-proj-... API keys. Not checked yet Extends Aembit's WIF credential provider ecosystem to now cover AWS STS AWS STS AWS Security Token Service, an Amazon Web service that issues short-lived credentials for IAM roles, letting tools authenticate to AWS APIs without storing long-term secrets. , Azure Entra, GCP, Anthropic Claude, and OpenAI ChatGPT under a single secretless access policy model. Not checked yet The EdgeController intercepts outbound OpenAI API requests at runtime, exchanges an Aembit-issued federation token at OpenAI's token endpoint, and injects the resulting short-lived access token access token A credential that authorizes a client to use a service or API. It usually has limited permissions and a lifetime; anyone holding it may be able to use those permissions. — requiring no application code changes, SDK modifications, or credential management logic. Not checked yet
3 details in Everything
Aembit adds Content Security policy component with CrowdStrike AIDR integration for MCP MCP Model Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. traffic inspection
Adds the Content Security Access Policy component, an optional step positioned between Access Conditions and Credential Providers that inspects MCP Identity Gateway traffic and enforces inspection verdicts. Not checked yet Integrates CrowdStrike AI Detection and Response (AIDR) as a Content Security provider to inspect tool listings, inputs, and outputs for allow/block/transform decisions on MCP traffic. Requires an active CrowdStrike AIDR for Agents subscription. Not checked yet Enriches Access Authorization Events with the Content Security component identifier and MCP Workload Events with the AIDR decision and CrowdStrike request ID for correlation. Not checked yet
3 details in Everything
Aembit Adds Workload Identity Federation Support for the Claude API (2026-08-05)
Aug 5, 2026
·
issue 054
Aembit extends its WIF WIF Workload Identity Federation is a Google Cloud mechanism that lets external workloads authenticate to Google APIs using short-lived tokens from a trusted identity provider, eliminating the need to manage long-lived service account keys. Credential Provider ecosystem to the Claude API, replacing static sk-ant-… keys with short-lived, automatically exchanged tokens.
└──▷ USE IT
Provision a Claude WIF Credential Provider in Terraform so workloads get short-lived Claude tokens instead of static sk-ant-… keys.
hcl
copy
resource "aembit_credential_provider" "claude_wif" {
name = "claude-wif-prod"
claude_wif = {
federation_rule_id = "fdrl_xxxxxxxxxxxxxxxx"
organization_id = "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx"
service_account_id = "svac_xxxxxxxxxxxxxxxx"
workspace_id = "wrkspc_xxxxxxxxxxxxxxxx"
scope = "workspace:developer"
lifetime = 3600
}
}
Verify that a newly configured Claude WIF Credential Provider can successfully exchange tokens with Claude's OAuth endpoint before attaching it to a policy.
📍 # In the Aembit Admin Portal:
# 1. Go to Credential Providers
# 2. Select the Claude WIF Credential Provider you created
# 3. Click Verify
# A green Verified Successfully banner confirms Aembit can reach
# POST /v1/oauth/token and exchange tokens on behalf of workloads.
Adds a new Claude Workload Identity Federation Credential Type option in the Aembit Credential Provider UI, with required fields federation_rule_id, organization_id, and service_account_id, and optional fields audience, scope (defaults to workspace:developer), workspace_id, and lifetime (defaults to 3600 seconds, range 300–43200). Not checked yet Adds a claude_wif block to the Aembit Terraform Provider, with required arguments federation_rule_id, organization_id, and service_account_id, and optional arguments audience, scope, workspace_id, and lifetime. Not checked yet Aembit's EdgeController now transparently performs the federation token exchange token exchange An OAuth 2.0 protocol extension (RFC 8693) that lets a service trade one token for another with different scopes, audience, or type, enabling delegation and impersonation across service boundaries without re-authenticating the user. against Claude's POST /v1/oauth/token OAuth endpoint and injects the resulting short-lived bearer token bearer token A credential that grants access to whoever presents it, without a separate proof of possession. Protecting the token matters because a stolen copy can be used by someone else. into outbound requests — no application code changes required. Not checked yet Extends Aembit's existing Workload Identity Federation Credential Provider pattern (previously covering AWS STS AWS STS AWS Security Token Service, an Amazon Web service that issues short-lived credentials for IAM roles, letting tools authenticate to AWS APIs without storing long-term secrets. , Azure Entra, and GCP) to include Anthropic's Claude API, allowing any OIDC OIDC OpenID Connect, a sign-in protocol built on OAuth 2.0. An application uses identity information from a trusted provider instead of maintaining a separate password for each user. -compliant identity source (AWS IAM AWS IAM AWS Identity and Access Management is Amazon's service for controlling who and what can call AWS APIs, by attaching policies that allow or deny actions on resources. Cyber tools use it to scope credentials to least privilege. , Google Cloud, Microsoft Entra ID Entra ID Microsoft's cloud-based identity and access management service, formerly Azure Active Directory, used by cyber tools to authenticate users and enforce access policies in Microsoft 365 and Azure environments. , GitHub Actions GitHub Actions GitHub's built-in CI/CD system that runs automated workflows triggered by repository events, letting cyber tools automate testing, building, and releasing without managing separate pipeline infrastructure. , Kubernetes service accounts, SPIFFE, Okta) to authenticate to Claude under the same Access Policy model. Not checked yet Aembit auto-generates a dedicated OIDC Issuer URL (serving /.well-known/openid-configuration and JWKS JWKS A JSON Web Key Set, a published collection of cryptographic keys. Applications use it to find the public key needed to verify a token's signature. ) that Claude Console uses for OIDC discovery when registering Aembit as a federation issuer. Not checked yet
5 details in Everything
AWS Application Load Balancer JWT Trust Provider now available
Aug 5, 2026
· release notes
Adds an AWS ALB ALB AWS Application Load Balancer, a managed Layer 7 load balancer from Amazon that routes HTTP/HTTPS traffic by host, path, or header, giving tools flexible ingress control without managing their own proxy. JWT JWT An open standard (RFC 7519) for encoding claims as a signed, optionally encrypted JSON object passed between parties. Cyber tools use it to verify identity and permissions without querying a central session store. Trust Provider for x-amzn-oidc-data tokens, with Terraform management support.
Adds the AWS Application Load Balancer JWT Trust Provider type to validate signed x-amzn-oidc-data tokens forwarded by an ALB authenticating with OIDC OIDC OpenID Connect, a sign-in protocol built on OAuth 2.0. An application uses identity information from a trusted provider instead of maintaining a separate password for each user. , automatically resolving and caching regional public keys. Works with Aembit Edge; Agent Controller support is not yet available. Not checked yet Enables match rules on ALB token claims including aud, iss, sub, email, and multiple custom_claim entries for authorization decisions. Not checked yet Supports managing the AWS ALB JWT Trust Provider through the Aembit Terraform Provider with aembit_trust_provider. Not checked yet
3 details in Everything
MCP Identity Gateway 1.33.5547 release
Jul 28, 2026
· release notes
MCP MCP Model Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. Identity Gateway 1.33.5547 improves upstream reconnection reliability and documentation.
Upstream reconnection now refreshes available tools and reports clear errors if the connection fails. Not checked yet
1 detail in Everything
OpenAI WIF Credential Provider now available
Jul 8, 2026
· release notes
Aembit adds OpenAI WIF WIF Workload Identity Federation is a Google Cloud mechanism that lets external workloads authenticate to Google APIs using short-lived tokens from a trusted identity provider, eliminating the need to manage long-lived service account keys. Credential Provider for short-lived token auth
Adds OpenAI WIF Credential Provider type to configure Identity Provider ID, service account, and optional audience for OpenAI federation. Not checked yet Adds Verify button in the UI to confirm trust between Aembit and your OpenAI federation setup before assigning to an Access Policy. Not checked yet Enables management of the OpenAI WIF Credential Provider through the Aembit Terraform Provider. Not checked yet
3 details in Everything
Client ID Metadata Document (CIMD) identification now available
Jun 30, 2026
· release notes
Aembit now identifies MCP MCP Model Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. clients via Client ID Metadata Document Client ID Metadata Document An OAuth 2.0 mechanism letting a client publish its own metadata (redirect URIs, grant types, contacts) at a well-known URL so authorization servers can fetch and verify it without manual registration. (CIMD CIMD A text-based Short Message Service protocol from Nokia for exchanging SMS messages between applications and SMS centers, used to build tools that send, receive, or test carrier messaging flows. )
Enables CIMD-based identification for MCP client workloads Not checked yet Validates metadata from a public HTTPS HTTPS HTTP carried over an encrypted TLS connection. It protects traffic in transit and lets a browser verify the server's certificate. JSON document at the client_id URL Not checked yet
2 details in Everything
MCP Identity Gateway event correlation and platform fixes
Jun 30, 2026
· release notes
MCP MCP Model Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. Identity Gateway 1.32.5098 adds workload event correlation and makes Client ID Metadata Document Client ID Metadata Document An OAuth 2.0 mechanism letting a client publish its own metadata (redirect URIs, grant types, contacts) at a well-known URL so authorization servers can fetch and verify it without manual registration. identification generally available.
MCP Identity Gateway sessions can persist across restarts
Jun 30, 2026
· release notes
Self-hosted MCP MCP Model Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. Identity Gateway supports optional session persistence in Valkey and a configurable idle timeout.
Adds AEMBIT_VALKEY_URL to enable Valkey session persistence for a self-hosted MCP Identity Gateway; leaving it unset keeps the in-memory default. Not checked yet Adds AEMBIT_MCP_SESSION_IDLE_TTL_SECS configuration to control idle session timeout (defaults to 12 hours) Not checked yet
2 details in Everything
MCP User-Based Access Token callback URL format
Jun 26, 2026
· release notes
New credential providers use a new callback URL format for MCP MCP Model Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. user-based access tokens access tokens A credential that authorizes a client to use a service or API. It usually has limited permissions and a lifetime; anyone holding it may be able to use those permissions. .
Existing Credential Providers retain their original URL format and require no re-registration Not checked yet New Credential Providers generate the updated callback URL upon save Not checked yet
2 details in Everything
Aembit now supports cascading deletion of Resource Sets via UI and Terraform.
Adds the ability to delete a custom Resource Set and all its contained entities (Access Policies, Workloads, Trust Providers, etc.) in a single cascading operation through the console Not checked yet Introduces Terraform support for Resource Set lifecycle management via the aembit_resource_set resource type Not checked yet Exposes the resource_set_id argument in Terraform to assign or filter entities by Resource Set Not checked yet
3 details in Everything
Edge components release with Aembit CLI and Secrets Operator updates
Jun 12, 2026
· release notes
Aembit CLI gains AWS/K8s K8s Shorthand for Kubernetes, the open-source container orchestration system originally from Google; cyber tools use it to deploy, scale, and manage containerized workloads across clusters. Trust Provider attestation and deployment model flags; Secrets Operator expands credential types.
Adds aembit credentials get support for AWS Metadata Service, AWS Role, and Kubernetes Service Account Trust Providers with automatic local attestation Not checked yet The --deployment-model option now accepts vm, kubernetes, ecs_fargate, and lambda_container; the AWS Role Trust Provider requires it. Not checked yet Expands Aembit Secrets Operator 1.32.322 credential retrieval to any type issued by an Access Policy, beyond previous HashiCorp Vault token limitation Not checked yet
3 details in Everything
Claude API WIF Credential Provider now available
Jun 12, 2026
· release notes
Aembit adds a Claude WIF WIF Workload Identity Federation is a Google Cloud mechanism that lets external workloads authenticate to Google APIs using short-lived tokens from a trusted identity provider, eliminating the need to manage long-lived service account keys. Credential Provider with Terraform support and built-in verification
Adds the Claude WIF Credential Provider type to exchange assertions for short-lived Claude API tokens through Workload Identity Federation. Not checked yet Adds a Verify action to confirm trust between Aembit and the Claude federation rule before applying to an Access Policy Not checked yet Adds Terraform provider support to manage the Claude WIF Credential Provider resource Not checked yet
3 details in Everything
MCP Identity Gateway 1.32.5006 release
Jun 4, 2026
· release notes
MCP MCP Model Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. Identity Gateway adds MCP ping support, authorization chain in workload events, and accurate health endpoint status
Adds MCP ping method support for client connection-health checks per the MCP specification. Not checked yet Workload events now include an ordered authorization chain of context IDs to trace requests end-to-end across agent, gateway, and server sides. Not checked yet Health endpoint returns HTTP 503 status when the Gateway is unhealthy, enabling accurate detection by orchestrators and load balancers. Not checked yet
3 details in Everything
Aembit Secrets Operator now supports more credential types
Jun 4, 2026
· release notes
Aembit Secrets Operator 1.32.322 adds credentialType field for OAuth, API keys, AWS STS AWS STS AWS Security Token Service, an Amazon Web service that issues short-lived credentials for IAM roles, letting tools authenticate to AWS APIs without storing long-term secrets. , and Workload Identity federation
Adds credentialType field to AembitSecretRefreshSchedule resource to select the Credential Provider type (default: OAuthToken). Not checked yet Supports ApiKey, UsernamePassword, AwsStsFederation, and GoogleWorkloadIdentityFederation credential types, each producing specific Secret data keys. Not checked yet Redacts AWS access key, secret access key, and session token values from debug logs in Secrets Operator. Not checked yet
3 details in Everything
Edge components release with reliability and CLI enhancements
Jun 4, 2026
· release notes
Adds CLI X.509-SVID X.509-SVID An X.509 certificate formatted to carry a SPIFFE Verifiable Identity Document, binding a cryptographic identity to a workload so cyber tools can authenticate services without passwords or static secrets. retrieval, configurable gRPC gRPC An open-source remote procedure call framework from Google that uses HTTP/2 and Protocol Buffers to let services call each other's functions across a network, giving tools low-latency, strongly typed inter-process communication. keep-alives and Windows HTTP idle timeout, and restores custom CA configuration.
aembit credentials get --client-tls-private-key retrieves X.509 X.509 A standard defining the format of public-key certificates, maintained by the ITU-T, used by cyber tools to authenticate identities and establish encrypted connections over TLS and similar protocols. -SVID certificates using a local PEM private key without sending the key to the server. Not checked yet AEMBIT_TENANT_GRPC_PING_INTERVAL_SECS and AEMBIT_TENANT_GRPC_PING_TIMEOUT_SECS environment variables configure gRPC keep-alives for Agent Proxy reconnects. Keep-alives are off by default. Not checked yet AGENT_TRUST_PATH again supports supplying a custom CA certificate for Agent Proxy connections to Aembit Cloud. Not checked yet AEMBIT_HTTP_IDLE_TIMEOUT_SECS configures the HTTP idle timeout on Windows in the Agent Proxy. Not checked yet Improved upstream proxy diagnostics now show the full error source chain in logs. Not checked yet
5 details in Everything
Aembit CLI now retrieves X.509-SVID certificates
Jun 3, 2026
· release notes
Aembit CLI aembit credentials get now accepts --client-tls-private-key to retrieve X.509-SVID X.509-SVID An X.509 certificate formatted to carry a SPIFFE Verifiable Identity Document, binding a cryptographic identity to a workload so cyber tools can authenticate services without passwords or static secrets. certificates.
aembit credentials get command gains --client-tls-private-key flag for retrieving SPIFFE SPIFFE An open standard, maintained by the CNCF, for assigning cryptographic identities to workloads in dynamic infrastructure so services can authenticate each other without passwords or static credentials. -compliant X.509 X.509 A standard defining the format of public-key certificates, maintained by the ITU-T, used by cyber tools to authenticate identities and establish encrypted connections over TLS and similar protocols. -SVID certificates Not checked yet X.509-SVID retrieval generates the CSR CSR A Certificate Signing Request is a block of encoded data submitted to a certificate authority, containing a public key and identity details, so the CA can issue a signed TLS certificate without ever seeing the private key. locally and returns the signed certificate chain in CLIENT_CERT_CHAIN. Not checked yet
2 details in Everything
End-to-end mTLS between Client and Server Workloads with SPIFFE X.509-SVID certi
May 21, 2026
· release notes
New end-to-end mTLS mTLS Mutual TLS, an encrypted connection where both client and server present certificates to prove their identity. It helps services verify who they are communicating with. between Client and Server Workloads using SPIFFE SPIFFE An open standard, maintained by the CNCF, for assigning cryptographic identities to workloads in dynamic infrastructure so services can authenticate each other without passwords or static credentials. X.509-SVID X.509-SVID An X.509 certificate formatted to carry a SPIFFE Verifiable Identity Document, binding a cryptographic identity to a workload so cyber tools can authenticate services without passwords or static secrets. certificates
Adds X.509-SVID Credential Provider type that issues SPIFFE-compliant X.509 X.509 A standard defining the format of public-key certificates, maintained by the ITU-T, used by cyber tools to authenticate identities and establish encrypted connections over TLS and similar protocols. certificates with URI SANs and configurable lifetime. Not checked yet Adds mTLS Authentication method with the x509 Certificate scheme to Server Workloads for validating client certificates. Not checked yet Enables Agent Proxy to establish outbound mTLS connections to Server Workloads using SPIFFE-compliant X.509-SVID certificates generated in memory. Not checked yet
3 details in Everything
MCP Identity Gateway 1.31.4955 release
May 19, 2026
· release notes
MCP MCP Model Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. sessions can now be explicitly deleted via API; MCP protocol and app-level Prometheus metrics added.
Adds session deletion capability to enable clients to explicitly end MCP Identity Gateway sessions when finished. Not checked yet Adds Prometheus metrics for MCP protocol-level errors and request failures. Not checked yet Exposes application-scoped Prometheus metrics for MCP Identity Gateway observability. Not checked yet
3 details in Everything
Expanded MCP and AI IAM event coverage
May 19, 2026
· release notes
Adds MCP MCP Model Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. discovery events, user identity fields, clearer failure reporting, and live authorization tracing.
Adds access.discovery event type to list Client and Server Workloads considered during access evaluation Not checked yet Adds application.mcp.userId field to MCP Workload Events and corresponding User (MCP App Protocol only) filter in the Workload Events view Not checked yet Changes Trust Provider attestation failure severity from Warning to Error Not checked yet Improves access.credential event reason to identify which token expired and at which step Not checked yet Adds live MCP Authorization Tracing view in the Reporting dashboard for real-time inbound authorization request diagnostics Not checked yet
5 details in Everything
Aembit Secrets Operator CRDs graduate to v1
May 15, 2026
· release notes
Aembit Secrets Operator 1.31.314 updates its CRDs CRDs A Kubernetes extension that adds a new object type to the cluster, so a tool's configuration is stored, validated and versioned by Kubernetes itself rather than in a file beside it. to v1 API.
Aembit Secrets Operator now available
May 12, 2026
· release notes
Aembit Secrets Operator 1.31.298 adds Service Account and OIDC OIDC OpenID Connect, a sign-in protocol built on OAuth 2.0. An application uses identity information from a trusted provider instead of maintaining a separate password for each user. auth, proactive renewal, and multi-namespace Helm installs.
Adds Kubernetes Service Account authentication using the operator’s in-cluster ServiceAccount token validated against the cluster’s OIDC endpoint Not checked yet Adds OIDC symmetric key authentication (HS256) for custom claims and non-Kubernetes identity scenarios Not checked yet Enables proactive credential renewal where credentials refresh at 80% of their TTL TTL Time to live, a limit on how long data remains valid or how far a packet can travel. Caches use a time limit; IP packets use a hop limit. , or sooner when you configure a shorter refreshInterval Not checked yet Allows multi-namespace install by supporting the same Helm release name across multiple namespaces on the same cluster without resource name conflicts Not checked yet
4 details in Everything
MCP MCP Model Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. Identity Gateway 1.31 adds userId to workload events and client-initiated session termination via DELETE /mcp
Adds userId field to mcp.request and mcp.response workload events for authenticated clients, enabling user attribution in audit reports Not checked yet Enables MCP clients to terminate sessions by sending an HTTP DELETE request to the /mcp endpoint Not checked yet
2 details in Everything
Dynamic claims now support custom environment variables
May 2, 2026
· release notes
Aembit OIDC OIDC OpenID Connect, a sign-in protocol built on OAuth 2.0. An application uses identity information from a trusted provider instead of maintaining a separate password for each user. and JWT-SVID JWT-SVID A SPIFFE Verifiable Identity Document encoded as a JSON Web Token, used to prove workload identity across trust boundaries where X.509 certificates are impractical, such as HTTP headers. dynamic claims now read custom env vars via AEMBIT_ENV_VAR_ALLOWLIST.
Adds AEMBIT_ENV_VAR_ALLOWLIST environment variable to Agent Proxy and Aembit CLI to explicitly allowlist which custom environment variables may be captured for OIDC and JWT JWT An open standard (RFC 7519) for encoding claims as a signed, optionally encrypted JSON object passed between parties. Cyber tools use it to verify identity and permissions without querying a central session store. -SVID dynamic claims Not checked yet Always-available Kubernetes variables (K8S_POD_NAME, K8S_NAMESPACE, KUBERNETES_PROVIDER_ID) are now usable in dynamic claims regardless of the allowlist Not checked yet
2 details in Everything
Edge components release with Oracle GA and HTTP proxy support
May 2, 2026
· release notes
Oracle GA, HTTP proxy, dynamic env-var claims, and streaming S3 uploads in Aembit edge components
AEMBIT_ENV_VAR_ALLOWLIST environment variable enables Agent Proxy and Aembit CLI to gather dynamic claims from environment variables. Not checked yet Oracle Database protocol support is now generally available, including mid-connection TLS and Prometheus metrics for credential injection events. Not checked yet Agent Proxy and Aembit CLI add upstream HTTP proxy configuration with NO_PROXY support for gRPC gRPC An open-source remote procedure call framework from Google that uses HTTP/2 and Protocol Buffers to let services call each other's functions across a network, giving tools low-latency, strongly typed inter-process communication. and Server-Workload-bound HTTP/HTTPS HTTPS HTTP carried over an encrypted TLS connection. It protects traffic in transit and lets a browser verify the server's certificate. traffic. Not checked yet Large file uploads to AWS S3 Log Streams are now supported via streaming AWS chunked signing, removing the previous upload size limit. Not checked yet
4 details in Everything
Oracle Database now generally available
May 2, 2026
· release notes
Aembit adds general availability for Oracle Database support with TLS and enhanced monitoring.
Adds production-ready Oracle Database protocol support (19c and 21c) to eliminate static database passwords via credential injection. Not checked yet Enables independent TLS configuration on client-to-proxy and proxy-to-database connections for Oracle Server Workloads. Not checked yet Provides Prometheus metrics (aembit_agent_proxy_credential_injections_total with application_protocol="oracleDatabase") for monitoring Oracle credential injection events. Not checked yet
3 details in Everything
Agent Proxy now honors HTTP proxy environment variables
Apr 17, 2026
· release notes
Agent Proxy now honors HTTP_PROXY, HTTPS_PROXY, and NO_PROXY environment variables for outbound traffic routing.
Agent Controller now honors HTTP proxy environment variables
Apr 15, 2026
· release notes
Agent Controller now respects HTTP_PROXY, HTTPS_PROXY, and NO_PROXY env vars for outbound traffic routing
Refresh token support for MCP authorization flows
Apr 7, 2026
· release notes
MCP MCP Model Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. Authorization Server flows gain optional single-use refresh tokens refresh tokens A credential used to obtain a new access token without signing in again. It is sent to the authorization service rather than used directly to call the protected API. and configurable absolute token lifetime.
Adds Enable Refresh Token Support to OIDC OIDC OpenID Connect, a sign-in protocol built on OAuth 2.0. An application uses identity information from a trusted provider instead of maintaining a separate password for each user. ID Token and Aembit Access Token Credential Providers exclusively for MCP Authorization Server flows. Not checked yet Adds Absolute Token Lifetime setting to control how long refresh tokens remain valid for exchanging for new access tokens access tokens A credential that authorizes a client to use a service or API. It usually has limited permissions and a lifetime; anyone holding it may be able to use those permissions. after initial issuance Not checked yet
2 details in Everything
MCP MCP Model Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. Identity Gateway 1.30 adds pre-proxy auth, tool annotations, and a metrics endpoint.
Authenticates requests before proxying them to upstream MCP servers (new default behavior) Not checked yet Includes tool annotations in MCP responses Not checked yet Returns HTTP 405 for GET requests to the MCP endpoint Not checked yet Adds additional metadata to Unauthorized (401) responses Not checked yet Honors the AEMBIT_TRUSTED_ISSUER_DOMAINS environment variable for trusted issuer configuration Not checked yet
+1 more
show less
Provides a new metrics endpoint for Gateway operational metrics on a configurable port Not checked yet
6 details in Everything
└──▷ BREAKING ON UPGRADE
! The Gateway now authenticates requests before proxying them to upstream MCP servers as its new default behavior.! GET requests to the MCP endpoint now return HTTP 405.
MCP Authorization Server now supports unauthenticated flows
Mar 31, 2026
· release notes
Aembit MCP MCP Model Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. Authorization Server adds unauthenticated OAuth flows via Enforce SSO toggle
Allows MCP Authorization Server to issue access tokens access tokens A credential that authorizes a client to use a service or API. It usually has limited permissions and a lifetime; anyone holding it may be able to use those permissions. without identity provider identity provider A service that authenticates users and supplies identity information to other applications. It is the sign-in authority behind many single sign-on systems. redirection when Enforce SSO is off Not checked yet
1 detail in Everything
MCP Identity Gateway now supports MCP resources
Mar 17, 2026
· release notes
MCP MCP Model Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. Identity Gateway v1.29.4419 adds MCP resource support for identity-aware proxying
resources/list endpoint discovers available resources across all assigned MCP servers Not checked yet resources/read endpoint retrieves a specific resource by URI from the appropriate MCP server Not checked yet
2 details in Everything
Oracle Database support enters beta with new process-based identifiers
Feb 26, 2026
· release notes
Aembit adds Oracle Database support in Limited Beta and process-based Client Workload identifiers for Linux VM deployments.
Adds Oracle Database application protocol support (Limited Beta) to Agent Proxy, enabling transparent credential injection for client workloads connecting via the TNS wire protocol. Not checked yet Adds Process Command Line and Process Path Client Workload identifiers for Linux VM deployments, with wildcard matching for command lines and exact executable-path matching. Not checked yet
2 details in Everything
MCP Identity Gateway enters beta with MCP Server and component copying
Feb 24, 2026
· release notes
Aembit adds MCP MCP Model Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. Identity Gateway beta, MCP Server MCP Server A process that exposes tools, resources, and prompts over Anthropic's Model Context Protocol, letting an AI agent call external APIs or local services through a standardised interface. for log querying, per-user OAuth Credential Provider, and component copying.
Adds MCP Identity Gateway Beta for proxying MCP traffic with identity-aware policy enforcement and fail-closed behavior Not checked yet Adds MCP Server to enable AI agents and users to query Aembit event logs using structured commands via the Model Context Protocol Model Context Protocol Model Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. Not checked yet Adds MCP User-Based Access Token Credential Provider type supporting OAuth 2.0 OAuth 2.0 An open authorization framework (IETF RFC 6749) that lets a service grant limited API access to a third party without sharing credentials, giving cyber tools a standard way to authenticate against external platforms. Authorization Code flow with PKCE PKCE Proof Key for Code Exchange, an OAuth safeguard that binds an authorization code to the client that requested it. An intercepted code cannot be redeemed without the client's matching verifier. support for per-user credential scoping Not checked yet Adds component copying capability between Resource Sets, allowing replication of Access Policy components and entire Access Policies Not checked yet
4 details in Everything
Edge components release with S3 streaming and Secrets Manager improvements
Jan 16, 2026
· release notes
Agent Proxy 1.28 adds S3 chunked upload signing and Secrets Manager PNA for username/password
private network access support for HTTP Basic Auth Credential Providers using AWS Secrets Manager Not checked yet process name and process username added as Client Workload Identifiers Not checked yet Extended AWS S3 support to include all SigV4SigV4 AWS's request-signing protocol that authenticates HTTP calls by hashing the request body, headers, and credentials into a signature; cyber tools use it to talk to AWS APIs without embedding long-lived secrets. headers, enabling required signing type specification Not checked yet
3 details in Everything
GitHub Action, MCP Authorization Server beta, and Access Policy Builder now avai
Jan 13, 2026
· release notes
New GitHub Action for CI/CD credential injection, MCP MCP Model Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. Authorization Server beta, PNA support, and Access Policy Builder UI.
Adds official GitHub Action to inject credentials into CI/CD workflows using workload identity federation workload identity federation A mechanism that lets a workload running in one cloud or platform prove its identity to another service using a trusted token exchange, eliminating the need to store long-lived credentials or secrets. Not checked yet Introduces MCP Authorization Server Beta securing Model Context Protocol Model Context Protocol Model Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. workloads with OAuth 2.1 OAuth 2.1 A consolidated draft of the OAuth authorization framework that merges OAuth 2.0 with its most important security BCP updates, dropping unsafe flows so tools can delegate user access without handling credentials directly. authorization code flow Not checked yet Enables Private Network Access (PNA) for AWS Secrets Manager Credential Provider to retrieve secrets from private VPCs VPCs Virtual Private Clouds — isolated, software-defined network environments inside a public cloud provider such as AWS, Azure, or GCP — give cyber tools a controlled network boundary with configurable routing, subnets, and access rules. Not checked yet Adds an opt-in Access Policy Builder with card-based navigation and inline component creation; enable Use new access policy in user profile preferences. Not checked yet
4 details in Everything
Edge components release with AWS S3 uploads and multiple AWS STS support
Dec 4, 2025
· release notes
Aembit adds S3 upload support and multiple AWS STS AWS STS AWS Security Token Service, an Amazon Web service that issues short-lived credentials for IAM roles, letting tools authenticate to AWS APIs without storing long-term secrets. providers in a single Access Policy
Agent Proxy now supports transparent AWS S3 file uploads with automatic detection of signing methods via the x-amz-content-sha256 header. Not checked yet Streaming signed payload uploads default to a 50 MiB limit, configurable with AEMBIT_AWS_MAX_BUFFERED_PAYLOAD_BYTES. Not checked yet Access Policy now supports multiple AWS STS Credential Providers matched automatically using Access Key ID selectors. Not checked yet
3 details in Everything
Azure Key Vault Credential Provider and OIDC SSO now available
Oct 21, 2025
· release notes
Aembit adds Azure Key Vault private network access, Azure Entra Federation credential provider, and OIDC OIDC OpenID Connect, a sign-in protocol built on OAuth 2.0. An application uses identity information from a trusted provider instead of maintaining a separate password for each user. SSO SSO Single sign-on, using one identity provider to sign in to multiple applications. It reduces separate passwords and centralizes account and access management. for admin console.
Adds support for Azure Key Vault private network endpoints through the Azure Key Vault Credential Provider. Not checked yet Introduces the Azure Entra Federation Credential Provider integration to authenticate with Azure Entra using Workload Identity Federation and OIDC Not checked yet Enables configuration of OIDC 1.0 Identity Providers for administrator Single Sign-On (SSO) authentication in the Aembit admin console Not checked yet
3 details in Everything
SPIFFE JWT-SVID Credential Provider now available
Aug 26, 2025
· release notes
Aembit adds SPIFFE SPIFFE An open standard, maintained by the CNCF, for assigning cryptographic identities to workloads in dynamic infrastructure so services can authenticate each other without passwords or static credentials. JWT-SVID JWT-SVID A SPIFFE Verifiable Identity Document encoded as a JSON Web Token, used to prove workload identity across trust boundaries where X.509 certificates are impractical, such as HTTP headers. Credential Provider for workload authentication.
Edge components release with OpenShift support and AWS Secrets Manager private n
Aug 22, 2025
· release notes
Adds AWS Secrets Manager private network access and OpenShift OpenShift Red Hat's Kubernetes distribution that adds developer workflows, built-in CI/CD, and stricter security defaults on top of upstream Kubernetes, giving cyber tools a managed container platform with enterprise auth and RBAC already wired in. support for Edge components
Adds Private Network Access to the AWS Secrets Manager Credential Provider for Aembit CLI and Agent Proxy Not checked yet Adds Official Red Hat OpenShift and ROSA support for Agent Proxy and Sidecar Init, including SecurityContextConstraint configurations Not checked yet Adds custom annotation support on Kubernetes resources in the Helm chart Not checked yet
3 details in Everything
GitLab CI/CD Component, OIDC dynamic claims, and CrowdStrike conditions now avai
Aug 19, 2025
· release notes
Aembit adds GitLab CI/CD Component, OIDC OIDC OpenID Connect, a sign-in protocol built on OAuth 2.0. An application uses identity information from a trusted provider instead of maintaining a separate password for each user. dynamic claims for credential data, and CrowdStrike MAC/IP access conditions
Aembit Edge GitLab CI/CD Component available in the GitLab CI/CD Catalog to simplify pipeline integration. Not checked yet OIDC ID Token Credential Provider now supports dynamic claims to extract values from OIDC tokens for personalized credential data. Not checked yet New Access Conditions for CrowdStrike: MAC Address and Local IP Address ensure Host MAC and Local IP match Agent Proxy retrieval. Not checked yet
3 details in Everything
Aembit CLI, AWS Secrets Manager, and Jenkins Pipelines now available
Jul 29, 2025
· release notes
New Aembit CLI for CI/CD injection, AWS Secrets Manager/IAM IAM Identity and Access Management — a framework of policies and services for controlling who can authenticate to systems and what resources they are authorized to use, letting cyber tools enforce least-privilege and audit access. providers, Jenkins support, and Agent Controller TLS port hardening
Releases the Aembit CLI , a command-line interface that allows you to inject credentials into your CI/CD pipelines. Not checked yet Introduces the AWS IAM AWS IAM AWS Identity and Access Management is Amazon's service for controlling who and what can call AWS APIs, by attaching policies that allow or deny actions on resources. Cyber tools use it to scope credentials to least privilege. Role Credential Provider Integration, used with the Secrets Manager Credential Provider to retrieve AWS Secrets Manager secrets. Not checked yet Introduces the AWS Secrets Manager Credential Provider for direct secret retrieval from AWS Secrets Manager. Not checked yet Adds support for Jenkins Pipelines as a compatible CI/CD target for Aembit-managed credentials. Not checked yet Enables wildcard hostname support for Server Workloads in Agent Controller. Not checked yet
+1 more
show less
Agent Controller automatically closes insecure HTTP ports when TLS is enabled and opens port 443 (5443 on VMs) plus secure Prometheus port 9091. Not checked yet
6 details in Everything
Discovery filtering and OIDC ID Token Trust Provider now available
Jul 22, 2025
· release notes
New Discovery filtering in UI and OIDC OIDC OpenID Connect, a sign-in protocol built on OAuth 2.0. An application uses identity information from a trusted provider instead of maintaining a separate password for each user. ID Token Trust Provider for workload auth
Adds advanced filtering options to the Discovered tab for Client and Server Workloads in the UI Not checked yet Introduces the OIDC ID Token Trust Provider to validate incoming tokens against issuer, audience, and subject claims for workload authentication Not checked yet
2 details in Everything
Aembit Edge API now available with expanded Wiz Discovery
Jun 17, 2025
· release notes
Aembit Edge API for dynamic credential retrieval and expanded Wiz Discovery for Client/Server Workloads
Adds Aembit Edge API endpoint to retrieve credentials on-demand for CI/CD pipelines and serverless functions without deploying additional infrastructure. Not checked yet Expands Wiz Discovery integration to discover Client Workload resources including VMs, AWS Client Workload Identifies, and Azure Client Workload Identifies. Not checked yet Expands Wiz Discovery integration to discover Server Workload resources including Azure Blob Storage Azure Blob Storage Microsoft's object-storage service for unstructured data in Azure, offering scalable, cheap storage for files of any size; cyber tools use it to store logs, artifacts, or large datasets without managing infrastructure. and GCP BigQuery BigQuery A serverless, cloud-hosted analytical database from Google that runs SQL queries across massive datasets without managing infrastructure, giving cyber tools scalable storage and fast querying over large volumes of log or event data. . Not checked yet
3 details in Everything
Workload Discovery filtering and Global Policy Compliance reporting now availabl
Jun 3, 2025
· release notes
Workload Discovery filtering and Global Policy Compliance reporting now available
Adds comprehensive filtering to Workload Discovery pages allowing search by Client Workload Identifiers, Workload Discovery Source, Port, and Protocol. Not checked yet Introduces a new Global Policy Compliance page under Reporting in the left nav menu for viewing Access Policies compliance status. Not checked yet
2 details in Everything
Kerberos and PKI security enhancements for Agent Proxy
Jun 2, 2025
· release notes
Adds AEMBIT_HTTP_PORT_DISABLED to disable Agent Controller’s HTTP port.
Improved Agent Injector pod security and TLS handling
May 30, 2025
· release notes
New AEMBIT_LOG_LEVEL env var and improved pod security/TLS for Agent Injector
Adds AEMBIT_LOG_LEVEL environment variable to control Agent Injector logging verbosity Not checked yet Improves compatibility with securityContext settings in Kubernetes pod specs Not checked yet Enhances TLS certificate handling within the Agent Injector Not checked yet
3 details in Everything
CrowdStrike SIEM Log Streams and Agent Proxy enhancements
May 26, 2025
· release notes
Adds CrowdStrike SIEM SIEM Security information and event management, collecting logs from many systems and correlating events to find suspicious activity. Analysts use it to investigate alerts and incidents. Log Streams and an Agent Proxy environment variable for process-based Client Workload identification.
Adds Log Streams for CrowdStrike Next-Gen SIEM to stream Access Authorization Events, Audit Logs, and Workload Events via HTTP Event Collector HTTP Event Collector A Splunk token-based API endpoint that accepts JSON-formatted log and event data over HTTPS, letting cyber tools ship telemetry directly to Splunk without a forwarder agent. (HEC HEC An HTTP API endpoint provided by Splunk that lets applications stream JSON-formatted events directly into a Splunk index without a forwarder agent, reducing pipeline complexity for log-shipping tools. ) Not checked yet Adds AEMBIT_CLIENT_WORKLOAD_PROCESS_IDENTIFICATION_ENABLED environment variable to Agent Proxy to enable Process Name Client Workload identification Not checked yet
2 details in Everything
Global Policy Compliance, OIDC ID Token Credential Provider, and Splunk Log Stre
May 6, 2025
· release notes
New Global Policy Compliance engine, OIDC OIDC OpenID Connect, a sign-in protocol built on OAuth 2.0. An application uses identity information from a trusted provider instead of maintaining a separate password for each user. ID Token Credential Provider, and Splunk HEC Splunk HEC An HTTP endpoint built into Splunk that accepts JSON-formatted log and event data pushed directly from applications or agents over HTTPS, letting cyber tools ship telemetry to Splunk without requiring a forwarder agent on the sending host. log integration.
Adds Lambda Layer support for zip-based AWS Lambda Functions Not checked yet Introduces Global Policy Compliance for centralized security enforcement with Required, Recommended, and Optional tiers via color-coded status icons Not checked yet Adds OIDC ID Token Credential Provider supporting RS256/ES256 ES256 An ECDSA digital signature algorithm using a P-256 elliptic curve and SHA-256 hash, defined in RFC 7518. Cyber tools use it to sign and verify JWTs with smaller keys than RSA while keeping strong integrity guarantees. signing and integration with AWS STS AWS STS AWS Security Token Service, an Amazon Web service that issues short-lived credentials for IAM roles, letting tools authenticate to AWS APIs without storing long-term secrets. , GCP WIF WIF Workload Identity Federation is a Google Cloud mechanism that lets external workloads authenticate to Google APIs using short-lived tokens from a trusted identity provider, eliminating the need to manage long-lived service account keys. , Azure WIF, and HashiCorp Vault Not checked yet Enables Log Stream for Splunk SIEM SIEM Security information and event management, collecting logs from many systems and correlating events to find suspicious activity. Analysts use it to investigate alerts and incidents. using HTTP Event Collector HTTP Event Collector A Splunk token-based API endpoint that accepts JSON-formatted log and event data over HTTPS, letting cyber tools ship telemetry directly to Splunk without a forwarder agent. (HEC HEC An HTTP API endpoint provided by Splunk that lets applications stream JSON-formatted events directly into a Splunk index without a forwarder agent, reducing pipeline complexity for log-shipping tools. ) protocol Not checked yet
4 details in Everything
Aembit adds Workload Discovery feature to automatically identify workloads via Aembit Edge Discovery and Wiz integration.
Adds Discovery feature to automatically identify workloads across infrastructure for improved visibility, scalability, and access control Not checked yet Adds Aembit Edge Discovery as a native source for finding workloads Not checked yet Adds Wiz integration as a supported source for workload discovery Not checked yet
3 details in Everything
GitLab.com support and service account naming for Managed GitLab Account Credent
Apr 22, 2025
· release notes
Aembit adds service account naming and GitLab.com support for Managed GitLab Credential Providers.
Adds the ability to specify a custom name for the service account created by Aembit in GitLab for Managed GitLab Account Credential Providers Not checked yet Enables creation of GitLab Service Account integrations for GitLab.com plans Not checked yet
2 details in Everything
Pod startup delay and security enhancements for Agent Proxy
Apr 21, 2025
· release notes
Adds AEMBIT_PASS_THROUGH_TRAFFIC_BEFORE_REGISTRATION env var to delay Client Workload pod startup in Agent Proxy
Allowed TLS Hostname now configurable for Agent Controller
Apr 15, 2025
· release notes
Agent Controllers now support configuring the domain name for Managed TLS certificates via a new tenant field.
Allows specifying the exact domain name for Aembit Managed TLS certificates to enhance connection security. Not checked yet
1 detail in Everything
Windows Server now supported for Kerberos Trust Provider and Agent Controller
Apr 3, 2025
· release notes
Aembit adds Windows Server support for Kerberos Kerberos A network authentication protocol that uses tickets issued by a trusted service. Users and services can prove their identities without sending a password to each application. Trust Provider and Agent Controller
The Kerberos Trust Provider now attests Client Workloads on Windows Server VMs joined to Active Directory Active Directory Microsoft's directory service for Windows networks that centralises authentication and authorisation; cyber tools target or integrate with it because it controls identity and access across most enterprise environments. . Not checked yet Agent Controller can be installed on Windows Server 2019 and Windows Server 2022 virtual machines. Not checked yet
2 details in Everything
Standalone CAs and Credential Provider Integrations now available
Mar 25, 2025
· release notes
Aembit adds Standalone CAs for granular TLS control and Credential Provider Integrations like GitLab.
Adds Standalone CAs feature to create dedicated Certificate Authorities independent of Tenant-level certificates for isolated trust boundaries. Not checked yet Updates Deploy Edge Components experience in the Aembit admin UI with deployment guides for Kubernetes, Ubuntu Linux, Red Hat Enterprise Linux, and Microsoft. Not checked yet Introduces Credential Provider Integrations to automate credential lifecycle management, starting with GitLab Service Account integration. Not checked yet
3 details in Everything
AWS SigV4 and SigV4a request signing now supported
Mar 5, 2025
· release notes
Aembit Credential Provider for AWS STS AWS STS AWS Security Token Service, an Amazon Web service that issues short-lived credentials for IAM roles, letting tools authenticate to AWS APIs without storing long-term secrets. now supports SigV4 SigV4 AWS's request-signing protocol that authenticates HTTP calls by hashing the request body, headers, and credentials into a signature; cyber tools use it to talk to AWS APIs without embedding long-lived secrets. and SigV4a request signing
Agent Controller now serves the full CA certificate chain
Feb 27, 2025
· release notes
Agent Controller now serves the full CA certificate chain instead of just the leaf cert.
Vault private network access and CrowdStrike on Windows now available
Feb 20, 2025
· release notes
Aembit adds Vault private network access and CrowdStrike Conditional Access Conditional Access A policy enforcement framework, most commonly Microsoft's in Entra ID, that grants or blocks resource access based on signals like user identity, device state, and location — letting cyber tools trigger step-up auth or deny risky sessions. for Windows.
Adds support for accessing HashiCorp Vault Credential Providers on private networks via the colocated Agent Proxy Not checked yet Adds AWS Role Trust Provider support on Agent Proxy for ECS ECS Elastic Common Schema, an open specification maintained by Elastic that defines a standard field naming convention for log and event data, letting cyber tools share and correlate records without per-source field mapping. Fargate deployments Not checked yet
2 details in Everything
Azure Entra Workload Identity Federation and automatic user creation now availab
Feb 11, 2025
· release notes
Aembit adds Azure Entra Workload Identity Federation support, auto user creation via SSO SSO Single sign-on, using one identity provider to sign in to multiple applications. It reduces separate passwords and centralizes account and access management. , and configurable TLS leaf cert lifetime
Adds Azure Entra Workload Identity Federation as a Credential Provider, with Aembit acting as a third-party federated IdP IdP A service that authenticates users and supplies identity information to other applications. It is the sign-in authority behind many single sign-on systems. to obtain credentials for Azure Entra resources. Not checked yet Enables Automatic User Creation triggered by SSO login requests. Not checked yet Enhances the Identity Provider configuration page to map SAML SAML A standard for passing signed identity assertions between a sign-in provider and an application. It lets a user sign in through their organization's identity provider. attributes from external IdPs to Aembit Tenant roles during automatic user creation. Not checked yet Allows changing the leaf certificate lifetime when using the TLS Decrypt feature. Not checked yet
4 details in Everything
RHEL with SELinux now supported for Edge components
Dec 26, 2024
· release notes
Aembit Edge Components now support RHEL RHEL Red Hat Enterprise Linux, a commercially supported Linux distribution maintained by Red Hat, chosen by cyber tools for its long support lifecycle, certified hardware compatibility, and enterprise deployment prevalence. 8 and 9 with SELinux SELinux A mandatory access control system built into the Linux kernel, maintained by the NSA and Red Hat, that enforces fine-grained policies restricting what processes can access, even if they run as root.
Earlier Client Workload identification in AWS Lambda Extension
Nov 22, 2024
· release notes
Aembit AWS Lambda Extension now identifies client workloads earlier in the container lifecycle.
Network traffic tracing now available for Agent Proxy debugging
Oct 28, 2024
· release notes
New environment variable enables network traffic tracing for Agent Proxy debugging
Multiple match rules of the same type now supported in Terraform Provider
Oct 25, 2024
· release notes
Aembit Terraform Provider now supports multiple match rules of the same type (OR-based combinations)
Explicit steering and enhanced access authorization events now available
Oct 23, 2024
· release notes
Aembit adds explicit traffic steering and enhanced access audit metadata (VM hostname, IP, process)
Adds Explicit Steering to configure Client Workloads to direct only specific types of traffic to the Agent Proxy Not checked yet Enhances Access Authorization Events to now capture and display VM hostname, IP address, and process name workload metadata Not checked yet
2 details in Everything
GitLab Jobs now supported in the Aembit Terraform Provider
Oct 18, 2024
· release notes
Aembit Terraform Provider adds support for GitLab Jobs and trust providers
Adds Terraform Provider support for GitLab Job Client Identifiers to manage GitLab Client Workloads. Not checked yet Adds Terraform Provider support for GitLab Job Trust Provider types. Not checked yet
2 details in Everything
Multi-Credential Provider Terraform support and Prometheus metrics now available
Oct 8, 2024
· release notes
Aembit adds Terraform support for multi-credential access policies and Prometheus metrics export for Edge components
Adds Terraform resource support to manage Access Policies with multiple Credential Providers Not checked yet Exposes Prometheus-compatible metrics for Aembit Edge Components (Agent Proxy, Agent Controller, Agent Injector) on Kubernetes and VMs Not checked yet Adds Admin Dashboard tiles for Client/Server Workloads, Credential Usage by Type, and Access Condition failures over the past 24 hours Not checked yet
3 details in Everything
Improved access authorization events and audit logging
Oct 1, 2024
· release notes
Aembit improves access authorization events and audit logging visibility for better diagnosis.
Real-time Agent Controller health monitoring now available
Sep 30, 2024
· release notes
Aembit enables real-time visibility into Agent Controller health within the Tenant and updates core Edge component versions for performance.
Custom Resource Sets now supported for GitHub Actions and GitLab Jobs
Sep 18, 2024
· release notes
Aembit adds Custom Resource Sets support for GitHub Actions GitHub Actions GitHub's built-in CI/CD system that runs automated workflows triggered by repository events, letting cyber tools automate testing, building, and releasing without managing separate pipeline infrastructure. and GitLab Jobs CI/CD pipelines
Aembit PKI Agent Controller TLS now available for Kubernetes and virtual machine
Sep 17, 2024
· release notes
Aembit updates its Edge Components (Helm Chart, Terraform ECS ECS Elastic Common Schema, an open specification maintained by Elastic that defines a standard field naming convention for log and event data, letting cyber tools share and correlate records without per-source field mapping. Module, VM Artifacts, AWS Lambda Extension) to newer versions for performance. PKI PKI A framework of policies, roles, and cryptographic standards for issuing and managing digital certificates that bind public keys to identities, letting tools verify authenticity and encrypt communications without pre-shared secrets. -based TLS is now available for Kubernetes and VM deployments.
Updated Admin Dashboard and multiple Credential Providers per Access Policy
Aug 27, 2024
· release notes
Adds Admin Dashboard metrics and support for multiple Credential Providers per Access Policy.
Admin Dashboard now displays Client Workloads (Managed), Server Workloads (Managed), Credentials Usage By Type, and Workloads Connections (Managed) for the last 24 hours. Not checked yet Access Policies support multiple Credential Providers associated with a single policy. Not checked yet
2 details in Everything
Agent Proxy now injected as a native Kubernetes sidecar
Aug 9, 2024
· release notes
Aembit Agent Proxy now injects as a native Kubernetes sidecar for Kubernetes 1.29+
Aembit Edge Terraform module and ECS TLS support now available
Jul 29, 2024
· release notes
Aembit Edge adds an AWS ECS AWS ECS Amazon's managed container orchestration service that runs Docker containers on clusters of EC2 instances or Fargate, letting tools offload scheduling, scaling, and infrastructure management to AWS. Terraform module and TLS support between Agent Proxy and Controller.
Adds Aembit Edge Terraform Module for deploying components to AWS ECS ECS Elastic Common Schema, an open specification maintained by Elastic that defines a standard field naming convention for log and event data, letting cyber tools share and correlate records without per-source field mapping. via the Terraform Registry Not checked yet Enables TLS between Agent Proxy and Agent Controller in ECS deployments using Aembit-provided PKI PKI A framework of policies, roles, and cryptographic standards for issuing and managing digital certificates that bind public keys to identities, letting tools verify authenticity and encrypt communications without pre-shared secrets. ; customer-provided PKI is not supported for ECS. Not checked yet
2 details in Everything
Dynamic steering to specific hostnames now available
Jul 3, 2024
· release notes
Aembit adds dynamic steering capability to restrict Agent Proxy traffic to specific hostnames
Enables dynamic steering to proxy only egress traffic destined for user-specified hostnames via the Agent Proxy. Not checked yet
1 detail in Everything
Expanded Client Workload identification and Trust Provider match rules
Jun 26, 2024
· release notes
Aembit adds or condition matches and wildcard support for Client Workload identification and Trust Provider rules.
Adds multiple or condition matches for Client Workload identification to allow matching workloads against any of several criteria Not checked yet Adds wildcard support for Trust Provider match rules to simplify identity pattern configuration Not checked yet
2 details in Everything
OAuth 2.0 Authorization Code Credential Provider now available
Jun 26, 2024
· release notes
Aembit adds 3-legged OAuth 2.0 OAuth 2.0 An open authorization framework (IETF RFC 6749) that lets a service grant limited API access to a third party without sharing credentials, giving cyber tools a standard way to authenticate against external platforms. Authorization Code Credential Provider for Atlassian, GitLab, Slack, GCP BigQuery BigQuery A serverless, cloud-hosted analytical database from Google that runs SQL queries across massive datasets without managing infrastructure, giving cyber tools scalable storage and fast querying over large volumes of log or event data. , Apigee, and PagerDuty.
Adds support for 3-legged OAuth (3LO) workflows via the new OAuth 2.0 Authorization Code Credential Provider Not checked yet Enables integration with Atlassian, GitLab, Slack, GCP BigQuery, Apigee, and PagerDuty using the new credential provider Not checked yet
2 details in Everything
OAuth 2.0 Authorization Code Credential Provider enters beta
Jun 10, 2024
· release notes
Aembit beta releases OAuth 2.0 OAuth 2.0 An open authorization framework (IETF RFC 6749) that lets a service grant limited API access to a third party without sharing credentials, giving cyber tools a standard way to authenticate against external platforms. Authorization Code Credential Provider for short-lived SaaS SaaS Software delivered over the internet and billed by subscription, hosted and operated by the vendor so the buyer skips installation and infrastructure management. auth
Non-root Aembit containers and configurable Agent Proxy file descriptor limits
Jun 5, 2024
· release notes
Non-root Aembit containers and configurable Agent Proxy file descriptor limits via AEMBIT_FD_LIMIT
AWS Role Trust Provider now available
Jun 4, 2024
· release notes
Aembit adds AWS Role-Based Trust Provider as an option for managing resource trust.
Supports AWS Role-Based Trust Providers as a selectable option in Aembit environments. Not checked yet
1 detail in Everything
Aembit introduces Resource Sets to group and manage specific entities like Credential and Identity Providers
Enables grouping of entities and resources (e.g., Credential Providers, Trust Providers, Identity Providers) into single collections called Resource Sets. Not checked yet Allows assigning specific users to manage these grouped resources for segmented management responsibilities. Not checked yet
2 details in Everything
Graceful Agent Proxy shutdown for sidecars
May 15, 2024
· release notes
Aembit adds graceful shutdown capability for Agent Proxy sidecars, allowing them to remain running after the main container exits.
Adds support for gracefully terminating the main job while keeping the Agent Proxy sidecar active. Not checked yet
1 detail in Everything
AWS Lambda Container deployment now supported
Apr 30, 2024
· release notes
Aembit adds support for deploying Edge Components as AWS Lambda Containers.
GeoIP Access Conditions and Google Cloud Storage Log Streams now available
Apr 23, 2024
· release notes
Aembit adds GeoIP GeoIP A database that maps IP addresses to geographic locations; tools use it to attribute traffic or alerts to countries, cities, or ASNs without querying external services. access conditions and Google Cloud Storage log stream destinations.
Adds Access Condition support for Geographic IP (GeoIP) restrictions to designate countries/regions with access to Server Workloads Not checked yet Adds Log Stream destination type targeting Google Cloud Storage Buckets via the Administration tab Not checked yet
2 details in Everything
Red Hat 8.9 now supported for virtual machine deployments
Apr 8, 2024
· release notes
Aembit Edge Components now support virtual machine deployments to Red Hat 8.9.
GitLab CI/CD Jobs now supported as Client Workloads
Apr 4, 2024
· release notes
Aembit adds support for GitLab CI/CD Jobs as Client Workloads
Kerberos Trust Provider now available for Active Directory
Mar 12, 2024
· release notes
Adds a Kerberos Kerberos A network authentication protocol that uses tickets issued by a trusted service. Users and services can prove their identities without sending a password to each application. Trust Provider for attesting Client Workloads in on-premise virtual machines joined to Active Directory Active Directory Microsoft's directory service for Windows networks that centralises authentication and authorisation; cyber tools target or integrate with it because it controls identity and access across most enterprise environments. .
TLS support between Agent Proxy and Agent Controller
Mar 11, 2024
· release notes
Aembit adds TLS support between Agent Proxy and Agent Controller
Aembit Terraform Provider now available
Mar 9, 2024
· release notes
Aembit now offers a Terraform provider for managing cloud resources via IaC IaC Infrastructure as Code: the practice of defining and provisioning compute infrastructure through machine-readable config files rather than manual processes, giving cyber tools repeatable, version-controlled environment setup. .
Release of the Aembit Terraform Provider to the Hashicorp Terraform Registry enables Infrastructure as Code management for Aembit Cloud resources. Not checked yet Support for managing resources manually or through CI/CD workflows using standard Terraform syntax. Not checked yet
2 details in Everything
Access Authorization Events and Google Cloud Run Jobs support now available
Jan 16, 2024
· release notes
Adds Access Authorization Events observability and Google Cloud Run Cloud Run Google's managed container runtime that executes stateless workloads on demand, scaling to zero when idle, so tools can deploy without managing servers or paying for idle capacity. Jobs client workload support
Enables Access Authorization Events to observe credential requests Not checked yet Supports Google Cloud Run Jobs as Client Workloads with Attestation-based identity Not checked yet
2 details in Everything
Agent Controller high availability now supported
Jan 4, 2024
· release notes
Aembit Agent Controller now supports high availability configurations for continuous access management.
Enables high-availability Agent Controller installations for Agent Proxy registration and credential acquisition. Not checked yet
1 detail in Everything
CrowdStrike Falcon Sensor integration for virtual machine verification
Dec 7, 2023
· release notes
Aembit adds CrowdStrike Falcon Sensor integration to verify VM security for Client Workloads
MFA support and Linux virtual machine Edge deployment now available
Nov 14, 2023
· release notes
Aembit adds MFA MFA Multi-factor authentication, requiring proof from different categories, such as a password and a hardware key, to sign in. It reduces reliance on a password alone. support and Linux VM Edge component deployment
Adds multi-factor authentication multi-factor authentication Multi-factor authentication, requiring proof from different categories, such as a password and a hardware key, to sign in. It reduces reliance on a password alone. (MFA) support allowing users to configure compatible authentication apps via QR code Not checked yet Enables viewing which users have configured MFA within the Aembit Users view Not checked yet Adds support for deploying Aembit Edge Components to non-Kubernetes Linux virtual machines Not checked yet
3 details in Everything
Dynamic Claims now available for Credential Providers
Oct 16, 2023
· release notes
Adds Dynamic Claims for Credential Providers, initially supported only for Vault integration.