Sourced from public evidenceLast checked 16 October 2026 with AI-assisted research. Editor: Akshay Dubey.MethodologyCorrections log

Everything below comes from public sources. The company has not reviewed this profile. Data last verified: 16 October 2026. Status labels are defined in the methodology. About this record.

Publisher interest: HumanAudit Inc., which publishes this site, sells governance documentation and plans NHI governance packs, including an RFP kit that does not name, rank or recommend any vendor. It builds and sells no NHI scanner and no NHI discovery, monitoring or security tool.

At a glance

Scroll sideways to see all columns.

OwnershipGoogle (Google Cloud product)VerifiedSource: Google Cloud documentation: Workload Identity Federation (Official product documentation).
General availability9 April 2021VerifiedSource: Google Cloud documentation: IAM release notes (Official product documentation). Date from the IAM release notes.
Purpose (official)Replaces service account keys for on-premises and multicloud workloadsVerifiedSource: Google Cloud documentation: Workload Identity Federation (Official product documentation).
Supported sources (official)AWS, Azure, Active Directory, X.509 client certificates, deployment services such as GitHub and GitLab, and OIDC or SAML 2.0 providersVerifiedSource: Google Cloud documentation: Workload Identity Federation (Official product documentation).
Token (official)Short-lived access token from the Google Security Token ServiceVerifiedSource: Google Cloud documentation: Workload Identity Federation (Official product documentation).
Controls (official)Attribute mapping and attribute conditions on external tokens, written in Common Expression LanguageVerifiedSource: Google Cloud documentation: Workload Identity Federation (Official product documentation).
Access methods (official)Direct resource access, or service account impersonation requiring the Workload Identity User roleVerifiedSource: Google Cloud documentation: Workload Identity Federation (Official product documentation).
Google's risk statementService account keys are powerful credentials and can present a security risk if not managed correctlyVerifiedSource: Google Cloud documentation: Workload Identity Federation (Official product documentation).

Source audit: AI research assistants checked the facts in this profile line by line against public sources on 16 October 2026. Akshay Dubey, the editor, is accountable for publication. Each fact carries a label for the kind of evidence behind it. What could not be confirmed is listed under What we could not verify.

What changed recently

  • 22 Aug 2026: Agent Identity auth manager and Agent Identity APIs generally available
  • 22 Apr 2026: Agent Identity, a separate IAM feature, generally available
  • 7 Apr 2026: Custom organisation policy constraints available for Workload Identity Federation
  • 18 Mar 2026: Managed workload identities generally available

Categories and identity types

Scroll sideways to see all columns.

CategoriesWorkload identity federation, Keyless cloud access
Identity and credential types (as the company describes them)External workloads (AWS, Azure, on-premises), CI/CD pipelines, OIDC and SAML identities, X.509 certificate identities, Service accounts

Capability evidence is in the capability matrix below.

Funding history

No funding round is recorded for this entry. For acquired companies, public companies and products of larger companies, see ownership above.

Disclosed investors: Not applicableVerifiedSource: Google Cloud documentation: Workload Identity Federation (Official product documentation).

Google product; funding not applicable.

What Google documents

Google says applications outside Google Cloud have traditionally used service account keys, which are powerful credentials and a risk if mismanaged, and that Workload Identity Federation removes the need for them. Tokens from an external identity provider carry attributes; an attribute mapping derives Google token attributes from them and an attribute condition restricts which external identities are accepted. The result is a short-lived access token for Google Cloud APIs. Access is granted either directly to the federated principal or through an impersonated service account. With impersonation, the external identity must be granted the Workload Identity User role on the service account. Google also documents audit log entries for each token exchange once Data Access logs are enabled.

Why it matters for NHI governance

Google describes service account keys as a security risk if not managed correctly. Federation replaces them with short-lived tokens tied to an identity already governed elsewhere, such as a CI system or another cloud's role. For governance, the attribute conditions become the policy: they decide which pipelines, repositories or roles may act in Google Cloud, so they deserve change control and owner sign-off like any access rule.

Practical guidance for governance teams

  • Inventory existing service account keys and plan their replacement with federation.
  • Write attribute conditions narrowly (specific repositories, branches or roles).
  • Assign an owner to each workload identity pool and provider, and review them periodically.
  • Monitor for new service account keys being created after migration.

Strengths, on the evidence

  • Removes the need for service account keys for workloads outside Google Cloud, per Google's documentation.
  • Works across clouds, on-premises and CI/CD.
  • Policy expressed in reviewable attribute conditions.

Gaps and what we do not know

  • Agent-specific features are not part of Workload Identity Federation. Google documents them under a separate IAM feature, Agent Identity, generally available since 22 April 2026.
  • Ownership of pools and providers depends on customer process.
  • Token exchange audit logs depend on Data Access logging being enabled by the customer.

What it says about the market

Google documents federation as the way for external workloads to reach Google Cloud without service account keys. Organisations that still hold such keys outside Google Cloud are using the pattern that Google's documentation describes as a security risk if not managed correctly.

Common questions

What does Google Cloud Workload Identity Federation do for non-human identity?
The feature addresses one specific NHI problem: long-lived service account keys held outside Google Cloud. It replaces a stored secret with a token exchange based on an identity the workload already has. It is an access mechanism, not a discovery or governance product. (Our analysis of public documentation.)
Who owns Google Cloud Workload Identity Federation?
Google.
Does Google Cloud Workload Identity Federation cover AI agents?
Evidence status: Documented by vendor. Covered by a separate IAM feature, Agent Identity, which assigns SPIFFE-based identities to agents. Workload Identity Federation itself has no agent-specific function in the documentation reviewed.
Who are Google Cloud Workload Identity Federation's competitors?
In our analysis of product scope: Microsoft Entra (Workload ID / Agent ID), AWS IAM / Bedrock AgentCore Identity. See Competitors and alternatives.

Timeline

Scroll sideways to see all columns.

DateEventSource
22 Aug 2026Agent Identity auth manager and Agent Identity APIs generally availableGoogle Cloud documentation: IAM release notes
22 Apr 2026Agent Identity, a separate IAM feature, generally availableGoogle Cloud documentation: IAM release notes
7 Apr 2026Custom organisation policy constraints available for Workload Identity FederationGoogle Cloud documentation: IAM release notes
18 Mar 2026Managed workload identities generally availableGoogle Cloud documentation: IAM release notes
7 May 2025Federation with X.509 certificates generally availableGoogle Cloud documentation: IAM release notes
29 Apr 2022Support for any SAML 2.0 identity provider generally availableGoogle Cloud documentation: IAM release notes
9 Apr 2021Workload Identity Federation generally availableGoogle Cloud documentation: IAM release notes
8 Apr 2021Google Cloud blog introduces Workload Identity Federation for AWS, Azure and OIDC providersGoogle Cloud Blog: Keyless API authentication through workload identity federation

Leadership

No named leadership was recorded for this entry from the sources reviewed. For a product of a larger company, see the parent company.

Products

Workload Identity Federation

An IAM feature that lets workloads outside Google Cloud exchange a credential from their own identity provider for a short-lived Google access token. Administrators define workload identity pools and providers, map token attributes and set attribute conditions. Documented sources include AWS, Azure, Active Directory, X.509 client certificates, OIDC and SAML 2.0 providers. [source]

Federation for deployment pipelines

Documented configurations for CI/CD systems that issue OIDC tokens to jobs. Google's guide covers Azure DevOps, GitHub Actions, GitLab SaaS and HCP Terraform. Google advises attribute conditions for multi-tenant providers, because checking the issuer alone is not sufficient. [source]

Managed workload identities

A related IAM feature for workloads running on Google Cloud. It binds attested, SPIFFE-based identities to Compute Engine and Google Kubernetes Engine workloads and provisions X.509 credentials from Certificate Authority Service for mutual TLS. Identities are defined inside a workload identity pool. Release notes record general availability on 18 March 2026; the overview page still marks GKE support as Preview. [source]

Agent Identity

A separate IAM feature that gives each agent a SPIFFE-based identity. The overview lists Gemini Enterprise Agent Platform Runtime, Gemini Enterprise and Cloud Run as supported runtimes. Release notes record general availability on 22 April 2026. It is not part of Workload Identity Federation. [source]

Capability matrix

This matrix records what public evidence shows. It is not a score. Documented by vendor means the company's own documentation or product pages describe the capability; it is not independent verification and says nothing about depth. Not publicly verified means we did not find public documentation, which is different from saying the product lacks the capability.

6 documented by the vendor, 0 independently reported, 15 not publicly verified.

Scroll sideways to see all columns.

CapabilityEvidence statusWhat the evidence says
NHI discovery Not publicly verifiedPublic documentation reviewed for this profile did not establish this capability.
NHI inventory Not publicly verifiedPublic documentation reviewed for this profile did not establish this capability.
Ownership assignment Not publicly verifiedPublic documentation reviewed for this profile did not establish this capability.
Attribution to humans Not publicly verifiedPublic documentation reviewed for this profile did not establish this capability.
Access analysis Not publicly verifiedPublic documentation reviewed for this profile did not establish this capability.
Authorization policy Documented by vendorAttribute conditions in Common Expression Language accept or reject external credentials, and IAM roles are granted to federated principals. [source]
Least privilege Not publicly verifiedDocumentation supports narrow attribute conditions and resource-specific roles. We did not find documentation of right-sizing analysis within this feature.
Lifecycle management Not publicly verifiedPublic documentation reviewed for this profile did not establish this capability.
Credential rotation Not publicly verifiedThe feature is documented as a replacement for service account keys, using short-lived tokens. It is not described as a rotation tool.
Secrets management Not publicly verifiedPublic documentation reviewed for this profile did not establish this capability.
Certificate management Not publicly verifiedFederation accepts X.509 client certificates, and managed workload identities receive certificates from Certificate Authority Service. Certificate lifecycle management is not described as part of this feature.
Service accounts Documented by vendorExternal identities can impersonate a service account when granted the Workload Identity User role. [source]
API keys Not publicly verifiedPublic documentation reviewed for this profile did not establish this capability.
OAuth apps and tokens Not publicly verifiedPublic documentation reviewed for this profile did not establish this capability.
Workload identity Documented by vendorFederating external workload identities into Google Cloud is the documented purpose of the feature. [source]
Cloud identity Documented by vendorAWS and Azure identities are documented as federation sources. [source]
AI agents Documented by vendorCovered by a separate IAM feature, Agent Identity, which assigns SPIFFE-based identities to agents. Workload Identity Federation itself has no agent-specific function in the documentation reviewed. [source]
Agent governance Not publicly verifiedPublic documentation reviewed for this profile did not establish this capability.
Monitoring and detection Not publicly verifiedAudit logs are documented. We did not find detection or alerting described as part of this feature.
Remediation Not publicly verifiedPublic documentation reviewed for this profile did not establish this capability.
Audit evidence Documented by vendorIAM writes an audit log entry for each token exchange and each short-lived credential generation, once Data Access logs are enabled. [source]

Customers

No named customers were found in the public sources reviewed. That does not mean there are none.

Positioning: claim and analysis

What the company says: Google states that Workload Identity Federation lets on-premises and multicloud workloads access Google Cloud resources without service account keys, which it describes as powerful credentials that can present a security risk if not managed correctly. [source]

What NHI problem it addresses (our analysis): The feature addresses one specific NHI problem: long-lived service account keys held outside Google Cloud. It replaces a stored secret with a token exchange based on an identity the workload already has. It is an access mechanism, not a discovery or governance product.

Where the evidence is strongest (our analysis): The documentation is detailed and current, with pages updated in September and October 2026. Policy is expressed as attribute mappings and conditions that can be reviewed. Token exchanges can be traced to the external subject in audit logs. General availability dates back to April 2021.

What public information does not establish:

  • Public documentation reviewed for this profile did not establish discovery or inventory of non-human identities as part of this feature.
  • Public documentation reviewed for this profile did not establish owner assignment for workload identity pools or providers beyond standard IAM administration.
  • We did not find agent-specific functions in Workload Identity Federation. Google documents those under the separate Agent Identity feature.
  • Token exchange audit logs require Data Access logging to be enabled by the customer, according to the documentation.

Competitors and alternatives

These groupings are our analysis of overlapping product scope. They are not rankings, and order carries no meaning.

Scroll sideways to see all columns.

RelationshipCompany or approachWhy it overlaps
Direct competitorMicrosoft Entra (Workload ID / Agent ID)workload identity federation for Azure resources
Direct competitorAWS IAM / Bedrock AgentCore Identityrole assumption with external identity providers on AWS
AdjacentAembitworkload access management across clouds
AdjacentDefakto (formerly SPIRL)SPIFFE-based workload identity
AdjacentSPIFFE / SPIRE (CNCF)open standard and runtime for workload identity
Substitute approachService account keys held in a secrets managerthe long-lived credential pattern that federation is documented to replace

Recent news

  • 22 August 2026: Agent Identity auth manager and APIs reach general availability. Google's IAM release notes record general availability of the Agent Identity auth manager and the Agent Identity APIs. These belong to the separate Agent Identity feature, not Workload Identity Federation. [source]
  • 22 April 2026: Agent Identity reaches general availability. Google's IAM release notes record a separate feature giving each agent an attested identity. It sits alongside, not inside, Workload Identity Federation. [source]
  • 7 April 2026: Custom organisation policy constraints cover Workload Identity Federation. Release notes state that Organization Policy Service custom constraints are available for managed workload identity and Workload Identity Federation. [source]
  • 18 March 2026: Managed workload identities reach general availability. The SPIFFE-based identity feature for Google Cloud workloads moved from preview to general availability, per the release notes. [source]
  • 7 May 2025: Federation with X.509 certificates becomes generally available. Workloads can authenticate with X.509 client certificates. A Google Cloud blog of 1 May 2025 described this as keyless access for non-human identities. [source]

What we could not verify

  • Adoption figures for Workload Identity Federation are not publicly disclosed in the sources reviewed.
  • No named customer case study for this feature is cited, so no customers are listed.
  • The managed workload identities overview marks GKE support as Preview, while release notes record general availability on 18 March 2026 and for Compute Engine on 27 July 2026. Which scope each statement covers is not clear from the documentation.
  • The documentation gives a default one hour lifetime for service account tokens in the AWS and Azure guide. The lifetime of the federated token itself is not established here.

This list covers points where public sources were missing, unclear or could not be opened. It is not complete. If you can supply a public source, tell us.

Additional sources for the sections above

  1. Google Cloud documentation: Workload Identity Federation (Official product documentation, 2026-09-30)
  2. Google Cloud documentation: IAM release notes (Official product documentation, 2026)
  3. Google Cloud Blog: Keyless API authentication through workload identity federation (Official company announcement, 2021-04-08)
  4. Google Cloud documentation: Best practices for using Workload Identity Federation (Official product documentation, 2026-10-02)
  5. Google Cloud documentation: Example logs for Workload Identity Federation (Official product documentation, 2026-10-05)
  6. Google Cloud documentation: Configure Workload Identity Federation with deployment pipelines (Official product documentation, 2026-10-05)
  7. Google Cloud documentation: Configure Workload Identity Federation with AWS or Azure (Official product documentation, 2026-09-30)
  8. Google Cloud documentation: Managed workload identities overview (Official product documentation, 2026-09-30)
  9. Google Cloud documentation: Agent Identity overview (Official product documentation, 2026-10-06)
  10. Google Cloud Blog: What's new in IAM, Access Risk, and Cloud Governance (Official company announcement, 2025-05-01)

Other companies in this category

Google Cloud Workload Identity Federation is listed under Identity governance platforms with NHI coverage. The companies below share that category in our directory. This is a category listing, not a ranking, and inclusion does not mean the products are equivalent.

Scroll sideways to see all columns.

CompanyOwnershipFunding (as stated in its profile)AI agent coverage (as stated)
C1 (formerly ConductorOne)Workday agreed to acquire C1 (definitive agreement announced 13 October 2026); completion not confirmedMore than $100M (company statement, October 2025)Yes (agents as first-class identities with credentials, policies, lifecycle and ownership; AI Access Management, March 2026)
LumosIndependentNot publicly disclosed as a total. Announced rounds: over $30M (May 2022, reported) and $35M (May 2024)Yes (governs agents; Identity Agent Force automates governance; MCP Governance checks agent tool calls, September 2026)
OakIndependent$60M seedYes (core)
OktaPublic (Nasdaq: OKTA)Not in the profile summaryYes (Okta for AI Agents; Agent SSO generally available August 2026; Cross App Access; Permiso detection)
SailPointPublic (Nasdaq: SAIL); controlled by Thoma BravoNot in the profile summaryYes (Agentic Fabric; Agent Identity Security; SailPoint Entro)
SaviyntPrivateNot stated by the company. Announced financings sum to about $1.075B: $170M total capital as of September 2021 (including a $130M financing), $205M in January 2023 and $700M in December 2025Yes (AI Agent Identity Management product)
Amazon Bedrock AgentCore IdentityAmazon Web ServicesNot in the profile summaryYes (core)
Clarity SecurityIndependent, venture-backedNot publicly disclosedYes (discovery, ownership and permission mapping, vendor-stated)

Frameworks and guides that apply to this category

Full list: NHI company directory.

Sources

  1. Google Cloud documentation: Agent Identity overview (Official product documentation, 2026-10-06)
  2. Google Cloud documentation: Example logs for Workload Identity Federation (Official product documentation, 2026-10-05)
  3. Google Cloud Blog: Keyless API authentication through workload identity federation (Official company announcement, 2021-04-08)
  4. Google Cloud Blog: What's new in IAM, Access Risk, and Cloud Governance (Official company announcement, 2025-05-01)
  5. Google Cloud documentation: Best practices for using Workload Identity Federation (Official product documentation, 2026-10-02)
  6. Google Cloud documentation: Configure Workload Identity Federation with AWS or Azure (Official product documentation, 2026-09-30)
  7. Google Cloud documentation: Managed workload identities overview (Official product documentation, 2026-09-30)
  8. Google Cloud documentation: Configure Workload Identity Federation with deployment pipelines (Official product documentation, 2026-10-05)
  9. Google Cloud documentation: IAM release notes (Official product documentation, 2026)
  10. Google Cloud documentation: Workload Identity Federation (Official product documentation, 2026-09-30)

No company pays to appear on NHI Governance. Spot an error? Tell us; corrections are logged publicly.

About this record

Research summary. This profile is compiled from public sources by NHI Governance. Inclusion is not an endorsement, certification, security assessment or investment recommendation, and does not imply any partnership or affiliation with Google Cloud Workload Identity Federation. Names and trademarks belong to their owners. Statements marked as analysis are our opinion.

Research status
Researched from public sources; sources checked
Last verified
Next review due
2026-12-23
Editorial responsibility
Akshay Dubey (editor), HumanAudit Inc.
Company input
None recorded. Under our editorial policy, companies do not approve pages.

Something wrong or out of date? Report it. Companies have a right of reply.

Monthly change log

Know when the NHI landscape changes.

One email a month from this reference: new deals, standards status changes and corrections. No sponsored content. Unsubscribe from any email.

We first email you a link to confirm. Privacy policy.