Aembit

No entries match these filters. Clear filters

1. 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 MCPMCPModel 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.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
   • 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.
   • Automate session revocation in incident-response workflows via the Aembit Cloud API.
   • Sessions appear for MCP clients that connect through a Client-to-Gateway Access Policy using an OIDC ID Token Credential Provider with refresh tokenrefresh tokenA 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.

   4 details in Everything

2. changelog Oct 29, 2026 · issue 124

   Aembit adds AEMBIT_NETWORK_ACCESS_POLICY to control which MCPMCPModel 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 tokenaccess tokenA 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.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
   • 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.
   • 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.
   • 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.
   • 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.

   +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.
   • 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.
   • Read the MCP Identity Gateway version without an access tokenaccess tokenA 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.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

   6 more in Everything

3. Aembit Now Supports SPIFFE: X.509-SVID and JWT-SVID Without SPIRE (2026-10-27) Oct 27, 2026 · issue 123

   Aembit now issues SPIFFESPIFFEAn 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-SVIDX.509-SVIDAn 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-SVIDJWT-SVIDA 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.509X.509A 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 mTLSmTLSMutual 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.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
   • Issues SPIFFE JWTJWTAn 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).
   • Handles SPIFFE identity attestation, credential issuance, and policy evaluation directly from the Aembit control plane, requiring no SPIRE server, agent, or supporting infrastructure.

   3 details in Everything

4. docs update Oct 21, 2026 · issue 115

   Aembit: MCPMCPModel 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 tokenaccess tokenA 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 tokensrefresh tokensA 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.
5. changelog Oct 20, 2026 · issue 114

   Aembit adds MCPMCPModel 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).⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
   • 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.
   • 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.
   • 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.
   • 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.

   +5 more show less

   • Adds AWS Metadata Service, Azure Instance Metadata Service, GCP Identity Token, Kubernetes Service Account, and OIDCOIDCOpenID 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+).
   • 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.
   • Adds new integration guides for Azure Functions, Azure virtual machines, GitHub ActionsGitHub ActionsGitHub'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.
   • Adds per-MCP-serverMCP-serverA 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.
   • 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.
   • 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).⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
   • 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.
   • 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.
   • 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.
   • 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.

   +3 more show less

   • Adds AWS Metadata Service, Azure Instance Metadata Service, GCP Identity Token, Kubernetes Service Account, and OIDCOIDCOpenID 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+).
   • Adds new integration guides for Azure Functions, Azure virtual machines, GitHub ActionsGitHub ActionsGitHub'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.
   • Adds per-MCP-serverMCP-serverA 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.

   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 tokenaccess tokenA 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 tokensaccess tokensA 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.
6. Introducing MCP Tool Filtering: Fine-Grained, Least-Privilege Authorization for AI Agents (2026-10-15) Oct 15, 2026 · issue 110

   Aembit adds MCPMCPModel 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.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
   • 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.
   • 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.
   • 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.
   • 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.

   +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.
   • 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.

   7 details in Everything

7. Introducing MCP Tool Filtering: Fine-Grained, Least-Privilege Authorization for AI Agents (2026-10-15) Oct 15, 2026 · issue 016

   Aembit adds MCPMCPModel 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.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
   • 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.
   • 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.
   • 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.
   • 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.

   +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.
   • 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.

   7 details in Everything

8. docs update Oct 14, 2026 · issue 108

   Aembit adds MCPMCPModel 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 ServerMCP ServerA 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.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
   • Prompts to revoke active sessions when deleting an Identity Provider that has sessions tied to an OIDCOIDCOpenID 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.
   • 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.
   • 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.
   • Entering a ${...} expression in a Credential Provider field in the Tenant UI automatically switches the field to Dynamic mode.

   +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.
   • Enhanced security for sign-in to the Aembit Tenant UI, including single sign-onsingle sign-onSingle sign-on, using one identity provider to sign in to multiple applications. It reduces separate passwords and centralizes account and access management. support.
   • 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.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
   • Prompts to revoke active sessions when deleting an Identity Provider that has sessions tied to an OIDCOIDCOpenID 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.
   • 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.
   • Entering a ${...} expression in a Credential Provider field in the Tenant UI automatically switches the field to Dynamic mode.

   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.
9. docs update Oct 14, 2026 · issue 108
   • New integration Snyk integration for workload security posture
10. docs update Oct 9, 2026 · issue 098

    Agent Proxy now injects credentials for MCPMCPModel 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 platformAgent 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.
    • Updated integrationNew supported platformMCP 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.
    • 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.
    • 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.
    • 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.

    +1 more show less

    • Agent Proxy (1.34.5755+) retrieves and injects credentials for Access Policies whose Credential Provider uses Private Network Access.

    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.
11. 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 integrationUpdated integrationAssigns 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.
    • 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.
    • Provides a per-agent kill switch that revokes all access for a specific agent instantly across connected services without disrupting the employee.
    • Centralizes audit logging for every agent access decision, capturing which agent acted, on whose behalf, what it touched, and which policy permitted the request.

    4 details in Everything

12. 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 MCPMCPModel 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 IAMIAMIdentity 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.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
    • Supports Meta Muse Dynamic Client Registration against the Aembit authorization server — no manual app creation, client ID, or secret required.
    • 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.
    • 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.
    • Provides MCP Authorization Tracing to diagnose authorization flow issues during Muse-to-gateway setup.

    +1 more show less

    • Extends centralized access policy management to cover Meta Muse alongside Microsoft Copilot Studio, Claude, ChatGPT, Gemini, and custom LLMLLMA 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.
    • Adds Meta Muse as a supported client workload in Aembit's IAMIAMIdentity 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.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
    • Supports Meta Muse Dynamic Client Registration against the Aembit authorization server — no manual app creation, client ID, or secret required.
    • 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.
    • 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.
    • Provides MCP Authorization Tracing to diagnose authorization flow issues during Muse-to-gateway setup.

    1 more in Everything

13. changelog Sep 26, 2026 · issue 086

    Aembit: Adds ${saml.response.subject.nameId}, ${saml.response.issuer}, and ${saml.response.attributes['<name>']} expressions so OAuth 2.0OAuth 2.0An 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.0SAML 2.0A 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 SAMLSAMLA 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 mTLSmTLSMutual 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 CSRCSRA 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 TLSmutual TLSMutual 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.
    • Enables the MCPMCPModel 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 tokensaccess tokensA 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 provideridentity providerA 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.
    • 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.
    • Allows a Kubernetes Service Account Trust Provider to accept multiple OIDCOIDCOpenID 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.
    • 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 TLSmutual TLSMutual 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.
    • Enables the MCPMCPModel 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 tokensaccess tokensA 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 provideridentity providerA 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.
    • 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.

    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.
14. changelog Sep 25, 2026 · issue 085
    └──▷ USE IT
    Issue mTLSmTLSMutual 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 IAMIAMIdentity 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 STSAWS STSAWS 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 SAMLSAMLA 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.0OAuth 2.0An 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).
15. changelog Sep 24, 2026 · issue 084

    Aembit adds SAMLSAMLA 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-SVIDX.509-SVIDAn 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, MCPMCPModel 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 STSAWS STSAWS 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 ActionsGitHub ActionsGitHub'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 mTLSmTLSMutual 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 CSRCSRA 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.0OAuth 2.0An 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 IAMIAMIdentity 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 STSSTSAWS 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.
    • 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 JWTJWTAn 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.
    • 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.
    • 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.
    • Adds Agent Controller support for KerberosKerberosA 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 EC2EC2Amazon's cloud virtual-machine service, letting tools run on-demand servers without managing physical hardware. instances (version 1.34.3725).

    +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.
    • Populates user first and last names from OIDCOIDCOpenID 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-onsingle sign-onSingle sign-on, using one identity provider to sign in to multiple applications. It reduces separate passwords and centralizes account and access management..
    • 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.
    • 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.

    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).
16. docs update Sep 24, 2026 · issue 084

    Aembit: Aembit now reads given_name, family_name, and name OIDCOIDCOpenID 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-onsingle sign-onSingle 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.0OAuth 2.0An 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 SAMLSAMLA 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 MCPMCPModel 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.
17. announced seen Sep 23, 2026 · issue 083

    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 ProtocolModel Context ProtocolModel 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.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
    • 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.
    • 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.
    • Provides a common enforcement point for AI agent access to MCPMCPModel 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.
    • Adds an Enterprise-Managed Authorization Credential Provider that implements the Model Context ProtocolModel Context ProtocolModel 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.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
    • 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.

    2 more in Everything

18. docs update Sep 23, 2026 · issue 083

    Aembit adds SAMLSAMLA 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 OIDCOIDCOpenID 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, MCPMCPModel 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-SVIDX.509-SVIDAn 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.0OAuth 2.0An 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 TLSmutual TLSMutual 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.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
    • Adds three SAML 2.0SAML 2.0A 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 2OAuth 2An 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.
    • 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.
    • Adds the MCP Enterprise Managed Access Token Credential Provider in the Aembit Tenant UI, obtaining per-user MCP server access tokensaccess tokensA 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 provideridentity providerA 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.
    • 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 TLSmutual TLSMutual 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.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
    • Adds three SAML 2.0SAML 2.0A 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 2OAuth 2An 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.
    • Adds the MCP Enterprise Managed Access Token Credential Provider in the Aembit Tenant UI, obtaining per-user MCP server access tokensaccess tokensA 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 provideridentity providerA 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.

    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.
19. Kubernetes Service Account Trust Provider now supports multiple OIDC endpoints Sep 23, 2026 · release notes

    Kubernetes Service Account Trust Provider adds support for multiple OIDCOIDCOpenID 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.

    1 detail in Everything

20. Dynamic claims now support SAML assertions Sep 23, 2026 · release notes

    Dynamic claims in Aembit now support SAMLSAMLA 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 provideridentity providerA 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.
    • Adds ${saml.response.issuer} expression to dynamic claims to return the identity provider issuer from a SAML assertion.
    • Adds ${saml.response.attributes['<name>']} expression to dynamic claims to return specific attributes (e.g., groups) from a SAML assertion.

    3 details in Everything

21. Automatic user creation reads user names from more claims Sep 23, 2026 · release notes

    Aembit reads user first/last names from OIDCOIDCOpenID 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 SSOSSOSingle 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.
    • Enhanced: User name resolution logic in automatic SSO user creation now explicitly supports standard OpenID ConnectOpenID ConnectOpenID 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.

    2 details in Everything

22. 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 SaaSSaaSSoftware delivered over the internet and run on the provider's infrastructure, so the buyer pays a subscription instead of installing or operating anything locally. MCPMCPModel 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 SSOSSOSingle 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 tokenrefresh tokenA 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 exchangetoken exchangeAn 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.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
    • Aembit's Edge Controller brokers XAA between identity providersidentity providersA 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 IdPIdPA 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.
    • Automatically falls back to the standard OAuth Authorization Code flow for any upstream MCP server or identity provideridentity providerA 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.
    • Adds a new Enterprise-Managed Authorization (EMA) Credential Provider that captures a user's SSOSSOSingle 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 tokenrefresh tokenA 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 exchangetoken exchangeAn 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.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
    • Aembit's Edge Controller brokers XAA between identity providersidentity providersA 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 IdPIdPA 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.

    1 more in Everything

23. docs update Sep 17, 2026 · issue 077

    Aembit adds MCPMCPModel 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.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
    • 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.

    2 details in Everything

24. docs update Sep 17, 2026 · issue 077

    Aembit adds multi-provider AWS STSAWS STSAWS 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 ActionsGitHub ActionsGitHub'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., MCPMCPModel 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 STSSTSAWS 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 IAMIAMIdentity 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.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
    • The Edge API credentials endpoint now carries the AWS STS Credential Provider selector alongside selectors for multiple JWTJWTAn 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.
    • Edge SDKs for TypeScript and Python (minimum Edge SDK 1.34.0) accept the Credential Provider selector as connection metadata on the credential request.
    • 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.
    • MCP Tool Access Control entries accept exact tool names or case-sensitive glob patterns matched against the name the MCP server publishes.

    +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.
    • 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 STSSTSAWS 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 IAMIAMIdentity 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.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
    • 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.
    • MCP Tool Access Control entries accept exact tool names or case-sensitive glob patterns matched against the name the MCP server publishes.
    • 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.

    2 more in Everything

25. docs update Sep 17, 2026 · issue 077

    Aembit adds MCPMCPModel 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 ServerMCP ServerA 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.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

    1 detail in Everything

26. docs update Sep 17, 2026 · issue 077

    Aembit introduces MCPMCPModel 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.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

    1 detail in Everything

27. Agent Controller 1.34.3725 release Sep 17, 2026 · release notes

    Agent Controller restores KerberosKerberosA 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 EC2EC2Amazon'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.
    • On Windows, Agent Controller now installs intermediate CA certificates from its TLS certificate chain into the LocalMachine certificate store

    2 details in Everything

28. 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 mTLSmTLSMutual 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
    • Secrets Operator now writes certificates to kubernetes.io/tls Secret types (with tls.crt and tls.key fields) when using the X509Svid credential type
    • Enables automatic certificate renewal for X.509-SVIDX.509-SVIDAn 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

    3 details in Everything

29. Aembit Cloud configuration updates Sep 16, 2026 · release notes

    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.
    • Client Workload Redirect URI field now correctly handles pasted values without overwriting surrounding text and displays one validation message at a time.
    • Terraform can now read the state of a Trust Provider secret when that provider belongs to a custom Resource Set.
    • Authorization event date filters in Access Authorization Events now support a maximum timespan of 24 hours.

    4 details in Everything

30. GitHub Actions now selects among multiple AWS STS Credential Providers Sep 16, 2026 · release notes

    Aembit GitHub Action now selects among multiple AWS STSAWS STSAWS 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

    1 detail in Everything

31. 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 MCPMCPModel 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.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
    • 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.
    • 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.
    • Makes the integration configurable through the Aembit UI, API, or Terraform with no changes required to existing AIDR console configuration.

    4 details in Everything

32. MCP Identity Gateway 1.34.5794 release Sep 15, 2026 · release notes

    Adds MCPMCPModel 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
    • Tool Visibility and Tool Invocation controls now accept glob patterns for MCP tool names (case-sensitive matching against the server-published name)

    2 details in Everything

33. docs update Sep 11, 2026 · issue 071

    Aembit adds Content Security Providers for MCPMCPModel 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.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
    • 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.
    • 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.

    3 details in Everything

34. docs update Sep 11, 2026 · issue 071

    Aembit: Adds Content Security Providers to govern Model Context ProtocolModel Context ProtocolModel 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. (MCPMCPModel 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.

    1 detail in Everything

35. docs update Sep 11, 2026 · issue 071

    Aembit: Adds Content Security Providers to Access Policies, enabling evaluation and policy enforcement on MCPMCPModel 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.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

36. docs update Sep 11, 2026 · issue 071

    Aembit adds a CLI for terminal-based credential retrieval, an MCPMCPModel 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.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
    • 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.
    • Adds the Agent Controller edge component, which brokers registration between Agent Proxies and Aembit Cloud, available for Linux amd64 and Windows amd64.
    • 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.

    4 details in Everything

37. announced seen Sep 2, 2026 · issue 062

    Aembit integrates with CrowdStrike Falcon AIDR to enforce detection and response policies on MCPMCPModel 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.
    • 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.
    • Configurable policies on MCP interactions support allow, report, block, or transform actions based on identity context and risks identified by CrowdStrike AIDR.
    • Aembit supplies run-time identities for user-delegated and autonomous agents to CrowdStrike AIDR, enriching AIDR policy decisions with workload identityworkload identityAn 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.
    • CrowdStrike AIDR findings now link directly to corresponding Aembit access records, enabling investigators to pivot between platforms without manually reconciling separate logs.

    5 details in Everything

38. Aembit + CrowdStrike: More Judgment Behind Every AI Agent “Yes” (2026-09-01) Sep 1, 2026 · issue 061

    Aembit integrates CrowdStrike AIDR into MCPMCPModel 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.
    • Supports configurable fail-open or fail-closed behavior per access policy when CrowdStrike AIDR is unreachable, with every failure recorded as a workload event.
    • 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.
    • 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.
    • New integration is configurable through the Aembit UI, API, or Terraform; requires a CrowdStrike AIDR for Agents subscription.

    5 details in Everything

39. changelog Aug 31, 2026 · issue 060

    Aembit adds Edge SDK (TypeScript & Python), glibc amd64 CLI build, and authorizationChain field in Agent Proxy workload events.

    └──▷ TRY IT
    Apply gRPCgRPCAn 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.
    • 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.
    • Windows MSI installer now applies AEMBIT_TENANT_GRPC_PING_INTERVAL_SECS and AEMBIT_TENANT_GRPC_PING_TIMEOUT_SECS when passed as install-time properties.
    • Linux installer script now validates Agent Proxy arguments — including numeric environment variables such as AEMBIT_HTTP_IDLE_TIMEOUT_SECS — before installation proceeds.
    • 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.

    +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 OIDCOIDCOpenID 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.
    • Provides Edge SDK integration guides for four platforms: AWS EC2EC2Amazon's cloud virtual-machine service, letting tools run on-demand servers without managing physical hardware., AWS Lambda, GCP Cloud RunCloud RunGoogle'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.
    • 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.
    • 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.

    9 details in Everything

40. 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 gRPCgRPCAn 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.
    • Aembit-generated response events now report outcome.result, outcome.reason, and severity fields instead of clearing them.

    2 details in Everything

41. 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.
    • Supports workload attestation via seven Trust Providers: AWS Metadata Service, AWS Role, Azure Instance Metadata Service, GCP Identity Token, GitHub, GitLab, and OIDCOIDCOpenID 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.

    2 details in Everything

42. Google Cloud Identity-Aware Proxy (IAP) JWT Trust Provider now available Aug 19, 2026 · release notes

    Adds GCP IAP JWTJWTAn 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 GKEGKEGoogle Kubernetes Engine, Google's managed Kubernetes service, which lets cyber tools run containerized workloads without managing the underlying cluster infrastructure., Cloud RunCloud RunGoogle'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.
    • Enables match rules on token claims aud, iss, sub, and email, plus any additional claim via the custom_claim attribute.
    • Enables management of the GCP IAP JWT Trust Provider through the Aembit Terraform provider using aembit_trust_provider.

    3 details in Everything

43. MCP Identity Gateway 1.34.5733 release Aug 18, 2026 · release notes

    MCPMCPModel 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, JWKSJWKSA 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.
    • Updates the Gateway's metrics reference to document all 20 MCP-specific metrics with types, labels, and label values.

    2 details in Everything

44. 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 WIFWIFWorkload 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 OIDCOIDCOpenID 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 tokensaccess tokensA 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.
    • Extends Aembit's WIF credential provider ecosystem to now cover AWS STSAWS STSAWS 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.
    • 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 tokenaccess tokenA 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.

    3 details in Everything

45. Content Security now available Aug 7, 2026 · release notes

    Aembit adds Content Security policy component with CrowdStrike AIDR integration for MCPMCPModel 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.
    • 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.
    • Enriches Access Authorization Events with the Content Security component identifier and MCP Workload Events with the AIDR decision and CrowdStrike request ID for correlation.

    3 details in Everything

46. Aembit Adds Workload Identity Federation Support for the Claude API (2026-08-05) Aug 5, 2026 · issue 054

    Aembit extends its WIFWIFWorkload 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).
    • 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.
    • Aembit's EdgeController now transparently performs the federation token exchangetoken exchangeAn 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 tokenbearer tokenA 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.
    • Extends Aembit's existing Workload Identity Federation Credential Provider pattern (previously covering AWS STSAWS STSAWS 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 OIDCOIDCOpenID 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 IAMAWS IAMAWS 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 IDEntra IDMicrosoft'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 ActionsGitHub ActionsGitHub'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.
    • Aembit auto-generates a dedicated OIDC Issuer URL (serving /.well-known/openid-configuration and JWKSJWKSA 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.

    5 details in Everything

47. AWS Application Load Balancer JWT Trust Provider now available Aug 5, 2026 · release notes

    Adds an AWS ALBALBAWS 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. JWTJWTAn 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 OIDCOIDCOpenID 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.
    • Enables match rules on ALB token claims including aud, iss, sub, email, and multiple custom_claim entries for authorization decisions.
    • Supports managing the AWS ALB JWT Trust Provider through the Aembit Terraform Provider with aembit_trust_provider.

    3 details in Everything

48. MCP Identity Gateway 1.33.5547 release Jul 28, 2026 · release notes

    MCPMCPModel 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.

    1 detail in Everything

49. OpenAI WIF Credential Provider now available Jul 8, 2026 · release notes

    Aembit adds OpenAI WIFWIFWorkload 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.
    • Adds Verify button in the UI to confirm trust between Aembit and your OpenAI federation setup before assigning to an Access Policy.
    • Enables management of the OpenAI WIF Credential Provider through the Aembit Terraform Provider.

    3 details in Everything

50. Client ID Metadata Document (CIMD) identification now available Jun 30, 2026 · release notes

    Aembit now identifies MCPMCPModel 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 (CIMDCIMDA 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
    • Validates metadata from a public HTTPSHTTPSHTTP 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

    2 details in Everything

51. MCP Identity Gateway event correlation and platform fixes Jun 30, 2026 · release notes

    MCPMCPModel 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 identification generally available.

52. MCP Identity Gateway sessions can persist across restarts Jun 30, 2026 · release notes

    Self-hosted MCPMCPModel 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.
    • Adds AEMBIT_MCP_SESSION_IDLE_TTL_SECS configuration to control idle session timeout (defaults to 12 hours)

    2 details in Everything

53. MCP User-Based Access Token callback URL format Jun 26, 2026 · release notes

    New credential providers use a new callback URL format for MCPMCPModel 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 tokensaccess tokensA 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
    • New Credential Providers generate the updated callback URL upon save

    2 details in Everything

54. Resource Set deletion now available Jun 23, 2026 · release notes

    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
    • Introduces Terraform support for Resource Set lifecycle management via the aembit_resource_set resource type
    • Exposes the resource_set_id argument in Terraform to assign or filter entities by Resource Set

    3 details in Everything

55. Edge components release with Aembit CLI and Secrets Operator updates Jun 12, 2026 · release notes

    Aembit CLI gains AWS/K8s 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
    • The --deployment-model option now accepts vm, kubernetes, ecs_fargate, and lambda_container; the AWS Role Trust Provider requires it.
    • Expands Aembit Secrets Operator 1.32.322 credential retrieval to any type issued by an Access Policy, beyond previous HashiCorp Vault token limitation

    3 details in Everything

56. Claude API WIF Credential Provider now available Jun 12, 2026 · release notes

    Aembit adds a Claude WIFWIFWorkload 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.
    • Adds a Verify action to confirm trust between Aembit and the Claude federation rule before applying to an Access Policy
    • Adds Terraform provider support to manage the Claude WIF Credential Provider resource

    3 details in Everything

57. MCP Identity Gateway 1.32.5006 release Jun 4, 2026 · release notes

    MCPMCPModel 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.
    • Workload events now include an ordered authorization chain of context IDs to trace requests end-to-end across agent, gateway, and server sides.
    • Health endpoint returns HTTP 503 status when the Gateway is unhealthy, enabling accurate detection by orchestrators and load balancers.

    3 details in Everything

58. 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 STSAWS STSAWS 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).
    • Supports ApiKey, UsernamePassword, AwsStsFederation, and GoogleWorkloadIdentityFederation credential types, each producing specific Secret data keys.
    • Redacts AWS access key, secret access key, and session token values from debug logs in Secrets Operator.

    3 details in Everything

59. Edge components release with reliability and CLI enhancements Jun 4, 2026 · release notes

    Adds CLI X.509-SVIDX.509-SVIDAn 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 gRPCgRPCAn 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.509X.509A 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.
    • 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.
    • AGENT_TRUST_PATH again supports supplying a custom CA certificate for Agent Proxy connections to Aembit Cloud.
    • AEMBIT_HTTP_IDLE_TIMEOUT_SECS configures the HTTP idle timeout on Windows in the Agent Proxy.
    • Improved upstream proxy diagnostics now show the full error source chain in logs.

    5 details in Everything

60. 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-SVIDX.509-SVIDAn 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 SPIFFESPIFFEAn 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.509X.509A 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
    • X.509-SVID retrieval generates the CSRCSRA 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.

    2 details in Everything

61. End-to-end mTLS between Client and Server Workloads with SPIFFE X.509-SVID certi May 21, 2026 · release notes

    New end-to-end mTLSmTLSMutual 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 SPIFFESPIFFEAn 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-SVIDX.509-SVIDAn 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.509X.509A 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.
    • Adds mTLS Authentication method with the x509 Certificate scheme to Server Workloads for validating client certificates.
    • Enables Agent Proxy to establish outbound mTLS connections to Server Workloads using SPIFFE-compliant X.509-SVID certificates generated in memory.

    3 details in Everything

62. MCP Identity Gateway 1.31.4955 release May 19, 2026 · release notes

    MCPMCPModel 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.
    • Adds Prometheus metrics for MCP protocol-level errors and request failures.
    • Exposes application-scoped Prometheus metrics for MCP Identity Gateway observability.

    3 details in Everything

63. Expanded MCP and AI IAM event coverage May 19, 2026 · release notes

    Adds MCPMCPModel 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
    • Adds application.mcp.userId field to MCP Workload Events and corresponding User (MCP App Protocol only) filter in the Workload Events view
    • Changes Trust Provider attestation failure severity from Warning to Error
    • Improves access.credential event reason to identify which token expired and at which step
    • Adds live MCP Authorization Tracing view in the Reporting dashboard for real-time inbound authorization request diagnostics

    5 details in Everything

64. Aembit Secrets Operator CRDs graduate to v1 May 15, 2026 · release notes

    Aembit Secrets Operator 1.31.314 updates its CRDsCRDsA 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.

65. Aembit Secrets Operator now available May 12, 2026 · release notes

    Aembit Secrets Operator 1.31.298 adds Service Account and OIDCOIDCOpenID 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
    • Adds OIDC symmetric key authentication (HS256) for custom claims and non-Kubernetes identity scenarios
    • Enables proactive credential renewal where credentials refresh at 80% of their TTLTTLTime 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
    • Allows multi-namespace install by supporting the same Helm release name across multiple namespaces on the same cluster without resource name conflicts

    4 details in Everything

66. MCP Identity Gateway 1.31 release May 12, 2026 · release notes

    MCPMCPModel 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
    • Enables MCP clients to terminate sessions by sending an HTTP DELETE request to the /mcp endpoint

    2 details in Everything

67. Dynamic claims now support custom environment variables May 2, 2026 · release notes

    Aembit OIDCOIDCOpenID 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-SVIDJWT-SVIDA 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 JWTJWTAn 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
    • Always-available Kubernetes variables (K8S_POD_NAME, K8S_NAMESPACE, KUBERNETES_PROVIDER_ID) are now usable in dynamic claims regardless of the allowlist

    2 details in Everything

68. 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.
    • Oracle Database protocol support is now generally available, including mid-connection TLS and Prometheus metrics for credential injection events.
    • Agent Proxy and Aembit CLI add upstream HTTP proxy configuration with NO_PROXY support for gRPCgRPCAn 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/HTTPSHTTPSHTTP carried over an encrypted TLS connection. It protects traffic in transit and lets a browser verify the server's certificate. traffic.
    • Large file uploads to AWS S3 Log Streams are now supported via streaming AWS chunked signing, removing the previous upload size limit.

    4 details in Everything

69. 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.
    • Enables independent TLS configuration on client-to-proxy and proxy-to-database connections for Oracle Server Workloads.
    • Provides Prometheus metrics (aembit_agent_proxy_credential_injections_total with application_protocol="oracleDatabase") for monitoring Oracle credential injection events.

    3 details in Everything

70. 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.

71. 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

72. Refresh token support for MCP authorization flows Apr 7, 2026 · release notes

    MCPMCPModel 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 tokensrefresh tokensA 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 OIDCOIDCOpenID 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.
    • Adds Absolute Token Lifetime setting to control how long refresh tokens remain valid for exchanging for new access tokensaccess tokensA 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

    2 details in Everything

73. MCP Identity Gateway 1.30 release Apr 3, 2026 · release notes

    MCPMCPModel 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)
    • Includes tool annotations in MCP responses
    • Returns HTTP 405 for GET requests to the MCP endpoint
    • Adds additional metadata to Unauthorized (401) responses
    • Honors the AEMBIT_TRUSTED_ISSUER_DOMAINS environment variable for trusted issuer configuration

    +1 more show less

    • Provides a new metrics endpoint for Gateway operational metrics on a configurable port

    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.
74. MCP Authorization Server now supports unauthenticated flows Mar 31, 2026 · release notes

    Aembit MCPMCPModel 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 tokensaccess tokensA 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 provideridentity providerA 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

    1 detail in Everything

75. MCP Identity Gateway now supports MCP resources Mar 17, 2026 · release notes

    MCPMCPModel 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
    • resources/read endpoint retrieves a specific resource by URI from the appropriate MCP server

    2 details in Everything

76. 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.
    • 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.

    2 details in Everything

77. MCP Identity Gateway enters beta with MCP Server and component copying Feb 24, 2026 · release notes

    Aembit adds MCPMCPModel 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 ServerMCP ServerA 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
    • Adds MCP Server to enable AI agents and users to query Aembit event logs using structured commands via the Model Context ProtocolModel Context ProtocolModel 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.
    • Adds MCP User-Based Access Token Credential Provider type supporting OAuth 2.0OAuth 2.0An 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 PKCEPKCEProof 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
    • Adds component copying capability between Resource Sets, allowing replication of Access Policy components and entire Access Policies

    4 details in Everything

78. 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
    • process name and process username added as Client Workload Identifiers
    • Extended AWS S3 support to include all SigV4SigV4AWS'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

    3 details in Everything

79. 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, MCPMCPModel 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 identityworkload identityAn 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. federation
    • Introduces MCP Authorization Server (beta) securing Model Context ProtocolModel Context ProtocolModel 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.1OAuth 2.1A 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
    • Enables Private Network Access (PNA) for AWS Secrets Manager Credential Provider to retrieve secrets from private VPCsVPCsVirtual 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.
    • Adds an opt-in Access Policy Builder with card-based navigation and inline component creation; enable Use new access policy in user profile preferences.

    4 details in Everything

80. 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 STSAWS STSAWS 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.
    • Streaming signed payload uploads default to a 50 MiB limit, configurable with AEMBIT_AWS_MAX_BUFFERED_PAYLOAD_BYTES.
    • Access Policy now supports multiple AWS STS Credential Providers matched automatically using Access Key ID selectors.

    3 details in Everything

81. 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 OIDCOIDCOpenID 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. SSOSSOSingle 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.
    • Introduces the Azure Entra Federation Credential Provider integration to authenticate with Azure Entra using Workload Identity Federation and OIDC
    • Enables configuration of OIDC 1.0 Identity Providers for administrator Single Sign-On (SSO) authentication in the Aembit admin console

    3 details in Everything

82. SPIFFE JWT-SVID Credential Provider now available Aug 26, 2025 · release notes

    Aembit adds SPIFFESPIFFEAn 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-SVIDJWT-SVIDA 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.

83. 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 support for Edge components

    • Adds Private Network Access to the AWS Secrets Manager Credential Provider for Aembit CLI and Agent Proxy
    • Adds Official Red Hat OpenShift and ROSA support for Agent Proxy and Sidecar Init, including SecurityContextConstraint configurations
    • Adds custom annotation support on Kubernetes resources in the Helm chart

    3 details in Everything

84. GitLab CI/CD Component, OIDC dynamic claims, and CrowdStrike conditions now avai Aug 19, 2025 · release notes

    Aembit adds GitLab CI/CD Component, OIDCOIDCOpenID 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.
    • OIDC ID Token Credential Provider now supports dynamic claims to extract values from OIDC tokens for personalized credential data.
    • New Access Conditions for CrowdStrike: MAC Address and Local IP Address ensure Host MAC and Local IP match Agent Proxy retrieval.

    3 details in Everything

85. 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/IAMIAMIdentity 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.
    • Introduces the AWS IAMAWS IAMAWS 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.
    • Introduces the AWS Secrets Manager Credential Provider for direct secret retrieval from AWS Secrets Manager.
    • Adds support for Jenkins Pipelines as a compatible CI/CD target for Aembit-managed credentials.
    • Enables wildcard hostname support for Server Workloads in Agent Controller.

    +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.

    6 details in Everything

86. Discovery filtering and OIDC ID Token Trust Provider now available Jul 22, 2025 · release notes

    New Discovery filtering in UI and OIDCOIDCOpenID 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
    • Introduces the OIDC ID Token Trust Provider to validate incoming tokens against issuer, audience, and subject claims for workload authentication

    2 details in Everything

87. 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.
    • Expands Wiz Discovery integration to discover Client Workload resources including VMs, AWS Client Workload Identifies, and Azure Client Workload Identifies.
    • Expands Wiz Discovery integration to discover Server Workload resources including Azure Blob Storage and GCP BigQueryBigQueryA 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..

    3 details in Everything

88. 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.
    • Introduces a new Global Policy Compliance page under Reporting in the left nav menu for viewing Access Policies compliance status.

    2 details in Everything

89. 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.

90. 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
    • Improves compatibility with securityContext settings in Kubernetes pod specs
    • Enhances TLS certificate handling within the Agent Injector

    3 details in Everything

91. CrowdStrike SIEM Log Streams and Agent Proxy enhancements May 26, 2025 · release notes

    Adds CrowdStrike SIEMSIEMSecurity 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 (HECHECAn 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.)
    • Adds AEMBIT_CLIENT_WORKLOAD_PROCESS_IDENTIFICATION_ENABLED environment variable to Agent Proxy to enable Process Name Client Workload identification

    2 details in Everything

92. Global Policy Compliance, OIDC ID Token Credential Provider, and Splunk Log Stre May 6, 2025 · release notes

    New Global Policy Compliance engine, OIDCOIDCOpenID 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 HECSplunk HECAn 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
    • Introduces Global Policy Compliance for centralized security enforcement with Required, Recommended, and Optional tiers via color-coded status icons
    • Adds OIDC ID Token Credential Provider supporting RS256/ES256ES256An 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 STSAWS STSAWS 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 WIFWIFWorkload 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
    • Enables Log Stream for Splunk SIEMSIEMSecurity 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 (HECHECAn 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

    4 details in Everything

93. Workload Discovery now available Apr 25, 2025 · release notes

    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
    • Adds Aembit Edge Discovery as a native source for finding workloads
    • Adds Wiz integration as a supported source for workload discovery

    3 details in Everything

94. 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
    • Enables creation of GitLab Service Account integrations for GitLab.com plans

    2 details in Everything

95. 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

96. 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.

    1 detail in Everything

97. Windows Server now supported for Kerberos Trust Provider and Agent Controller Apr 3, 2025 · release notes

    Aembit adds Windows Server support for KerberosKerberosA 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 DirectoryActive DirectoryMicrosoft'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..
    • Agent Controller can be installed on Windows Server 2019 and Windows Server 2022 virtual machines.

    2 details in Everything

98. 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.
    • Updates Deploy Edge Components experience in the Aembit admin UI with deployment guides for Kubernetes, Ubuntu Linux, Red Hat Enterprise Linux, and Microsoft.
    • Introduces Credential Provider Integrations to automate credential lifecycle management, starting with GitLab Service Account integration.

    3 details in Everything

99. AWS SigV4 and SigV4a request signing now supported Mar 5, 2025 · release notes

    Aembit Credential Provider for AWS STSAWS STSAWS 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 SigV4SigV4AWS'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

100. 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.

101. Vault private network access and CrowdStrike on Windows now available Feb 20, 2025 · release notes

     Aembit adds Vault private network access and CrowdStrike Conditional AccessConditional AccessA 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
     • Adds AWS Role Trust Provider support on Agent Proxy for ECSECSElastic 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

     2 details in Everything

102. 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 SSOSSOSingle 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 IdPIdPA 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.
     • Enables Automatic User Creation triggered by SSO login requests.
     • Enhances the Identity Provider configuration page to map SAMLSAMLA 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.
     • Allows changing the leaf certificate lifetime when using the TLS Decrypt feature.

     4 details in Everything

103. RHEL with SELinux now supported for Edge components Dec 26, 2024 · release notes

     Aembit Edge Components now support RHELRHELRed 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 SELinuxSELinuxA 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.

104. 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.

105. 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

106. 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)

107. 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
     • Enhances Access Authorization Events to now capture and display VM hostname, IP address, and process name workload metadata

     2 details in Everything

108. 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.
     • Adds Terraform Provider support for GitLab Job Trust Provider types.

     2 details in Everything

109. 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
     • Exposes Prometheus-compatible metrics for Aembit Edge Components (Agent Proxy, Agent Controller, Agent Injector) on Kubernetes and VMs
     • Adds Admin Dashboard tiles for Client/Server Workloads, Credential Usage by Type, and Access Condition failures over the past 24 hours

     3 details in Everything

110. Improved access authorization events and audit logging Oct 1, 2024 · release notes

     Aembit improves access authorization events and audit logging visibility for better diagnosis.

111. 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.

112. Custom Resource Sets now supported for GitHub Actions and GitLab Jobs Sep 18, 2024 · release notes

     Aembit adds Custom Resource Sets support for GitHub ActionsGitHub ActionsGitHub'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

113. 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 ECSECSElastic 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. PKIPKIA 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.

114. 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.
     • Access Policies support multiple Credential Providers associated with a single policy.

     2 details in Everything

115. 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+

116. Aembit Edge Terraform module and ECS TLS support now available Jul 29, 2024 · release notes

     Aembit Edge adds an AWS ECSAWS ECSAmazon'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 ECSECSElastic 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
     • Enables TLS between Agent Proxy and Agent Controller in ECS deployments using Aembit-provided PKIPKIA 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.

     2 details in Everything

117. 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.

     1 detail in Everything

118. 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
     • Adds wildcard support for Trust Provider match rules to simplify identity pattern configuration

     2 details in Everything

119. OAuth 2.0 Authorization Code Credential Provider now available Jun 26, 2024 · release notes

     Aembit adds 3-legged OAuth 2.0OAuth 2.0An 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 BigQueryBigQueryA 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
     • Enables integration with Atlassian, GitLab, Slack, GCP BigQuery, Apigee, and PagerDuty using the new credential provider

     2 details in Everything

120. OAuth 2.0 Authorization Code Credential Provider enters beta Jun 10, 2024 · release notes

     Aembit beta releases OAuth 2.0OAuth 2.0An 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 SaaSSaaSSoftware delivered over the internet and run on the provider's infrastructure, so the buyer pays a subscription instead of installing or operating anything locally. auth

121. 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

122. 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.

     1 detail in Everything

123. Resource Sets now available May 30, 2024 · release notes

     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.
     • Allows assigning specific users to manage these grouped resources for segmented management responsibilities.

     2 details in Everything

124. 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.

     1 detail in Everything

125. AWS Lambda Container deployment now supported Apr 30, 2024 · release notes

     Aembit adds support for deploying Edge Components as AWS Lambda Containers.

126. GeoIP Access Conditions and Google Cloud Storage Log Streams now available Apr 23, 2024 · release notes

     Aembit adds GeoIPGeoIPA 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
     • Adds Log Stream destination type targeting Google Cloud Storage Buckets via the Administration tab

     2 details in Everything

127. 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.

128. 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

129. Kerberos Trust Provider now available for Active Directory Mar 12, 2024 · release notes

     Adds a KerberosKerberosA 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 DirectoryActive DirectoryMicrosoft'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..

130. TLS support between Agent Proxy and Agent Controller Mar 11, 2024 · release notes

     Aembit adds TLS support between Agent Proxy and Agent Controller

131. Aembit Terraform Provider now available Mar 9, 2024 · release notes

     Aembit now offers a Terraform provider for managing cloud resources via IaCIaCInfrastructure 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.
     • Support for managing resources manually or through CI/CD workflows using standard Terraform syntax.

     2 details in Everything

132. Access Authorization Events and Google Cloud Run Jobs support now available Jan 16, 2024 · release notes

     Adds Access Authorization Events observability and Google Cloud RunCloud RunGoogle'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
     • Supports Google Cloud Run Jobs as Client Workloads with Attestation-based identity

     2 details in Everything

133. 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.

     1 detail in Everything

134. 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

135. MFA support and Linux virtual machine Edge deployment now available Nov 14, 2023 · release notes

     Aembit adds MFAMFAMulti-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 authenticationmulti-factor authenticationMulti-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
     • Enables viewing which users have configured MFA within the Aembit Users view
     • Adds support for deploying Aembit Edge Components to non-Kubernetes Linux virtual machines

     3 details in Everything

136. Dynamic Claims now available for Credential Providers Oct 16, 2023 · release notes

     Adds Dynamic Claims for Credential Providers, initially supported only for Vault integration.