Identity supply chains are under siege as trust cascades downstream

At a glance

What this is: This is Delinea’s April 2026 identity threat outlook, which shows attackers using compromised trusted identities to turn enterprise access paths into downstream attack routes.

Why it matters: It matters because IAM, PAM, and NHI programmes now have to govern inherited trust across tenants, partners, and automation instead of treating authentication as the finish line.

By the numbers:

• In March, 5,236 CVEs were disclosed across the industry, and 519 were identity-related.
• The article says 62 CVEs directly affected identity products.
• Tycoon 2FA accounted for 62% of all phishing attempts blocked by Microsoft by mid-2025.

Context

Identity supply chains describe the trust paths that connect administrators, third parties, service accounts, cloud roles, and automation across organisations. When one trusted identity is compromised, the access it carries can cascade into downstream systems that were never directly breached.

This month’s pattern is not about perimeter bypass. It is about trusted identities being used exactly as designed, which makes continuous governance more important than initial authentication. For IAM, PAM, and NHI teams, the question is who can inherit trust and for how long.

The article’s central finding is that identity control failures now propagate across organisational boundaries. That changes the governance problem from account security to trust-chain security, where access can remain valid long after the context that created it has changed.

Key questions

Q: What breaks when one trusted identity can unlock multiple downstream systems?

A: The control breaks at the trust boundary. If one administrative, partner, or machine identity can open several environments without fresh authorisation, a single compromise becomes a propagation path. The right question is not whether the login was valid, but whether downstream access should still be honoured after context, ownership, or purpose has changed.

Q: What problem does ownership attribution solve for service accounts and API keys?

A: It closes the gap between exposure detection and accountable remediation. Many organisations can find the secret, but not the human who introduced it, maintains it, or can safely replace it. Ownership attribution gives security teams a practical way to assign action without relying on informal knowledge that disappears during staff changes.

Q: How do teams know whether trust inheritance is under control?

A: Look for whether every high-value boundary requires explicit reauthorisation, not just initial login success. If an upstream identity can reach new systems, clients, or tenants without a fresh decision, trust inheritance is still driving the access model. Review evidence should show where trust ends, not only where authentication succeeded.

Q: Who should own third-party identity access across vendors and BPOs?

A: Ownership should sit with the business and identity governance function together, because inherited access crosses operational and contractual lines. If no team can name the current purpose, scope, and expiry of a partner credential, accountability has already fractured. That is when downstream trust becomes an enterprise risk rather than a vendor issue.

Technical breakdown

How downstream trust cascades through identity supply chains

Identity supply chains form when one identity assertion is accepted by another system as proof of legitimacy. In practice, that means an SSO session, cloud IAM role, API key, or service account can unlock a second environment without re-proving intent. The security failure is not only credential theft. It is the assumption that a trusted upstream identity still deserves downstream access after context has changed. Once that trust is inherited, attackers do not need to break every control plane. They only need one credential path that is accepted across organisational seams.

Practical implication: map where trust is inherited automatically and require explicit reauthorisation at each boundary.

Why non-human identities remain the quiet entry point

Service accounts, API keys, and automation tokens bypass user-centric controls by design. They do not prompt for MFA, they often lack a human owner at execution time, and they can persist across pipelines or vendors long after the original task is complete. That makes them ideal for quiet initial access and downstream movement. The risk is amplified when those identities are reused across environments or embedded in CI/CD and third-party workflows. In that pattern, one leaked token can become a reusable trust bridge rather than a single compromised account.

Practical implication: inventory NHI credentials by owner, scope, and expiry so reused trust paths can be removed.

Continuous authorization is the missing control plane

Authentication answers who got in. Continuous authorization answers whether that identity should still be allowed to act. Delinea’s examples show why that distinction matters: once an admin, partner account, or machine identity is inside, destructive action often looks legitimate until the outcome is visible. Modern identity governance therefore has to evaluate privilege at execution time, not just at login or provisioning. For high-impact operations, the relevant question is whether the authorised action still matches the current business context, not whether the session was initially valid.

Practical implication: place execution-time checks around high-impact actions instead of relying on one-time login approval.

Threat narrative

Attacker objective: The attacker’s objective is to convert one trusted identity into broad downstream access that can be used for disruption, theft, or lateral compromise.

1. Entry occurred through compromised trusted identities, including administrative credentials, SSO accounts, cloud IAM roles, and CI/CD service accounts.
2. Credential or session abuse enabled the attacker to authenticate legitimately and operate inside downstream environments without exploiting a perimeter vulnerability.
3. Escalation happened through inherited trust, where one valid identity opened access to additional systems, partners, or tenants that accepted the original assertion.
4. Impact followed when those downstream rights were used for device wiping, data theft, or further compromise of client environments.

Breaches seen in the wild

• reviewdog Action compromise 2025: A stolen maintainer token poisoned reviewdog/action-setup, leaking CI secrets including the tj-actions bot token used in the next attack.
• BeyondTrust breach 2024: A stolen BeyondTrust Remote Support API key let a China state-sponsored actor reset accounts and reach US Treasury workstations in 2024.

Read and download The State of NHI & AI Agent Breach Report 2026, covering 200+ breaches impacting Non-Human Identities including AI Agents.

NHI Mgmt Group analysis

Identity supply chains are now a governance problem, not just an authentication problem. The article shows that attackers often use valid credentials exactly as intended, which means the security failure sits in how trust is inherited across systems. That shifts the centre of gravity from login hardening to trust-path control. Practitioners should treat every downstream acceptance point as a governance boundary.

Continuous authorization is the decisive control when trust moves faster than review cycles. Access review processes assume privilege can be observed after it is granted, but inherited trust can cross multiple environments before any periodic review occurs. That makes execution-time authorization more relevant than certification cadence in high-impact paths. The implication is that teams must govern what an identity can do at the moment of action, not just what it was allowed to do at onboarding.

Third-party identity access is the identity supply chain’s weakest link when ownership is diffuse. The article’s examples show BPOs, vendors, and software pipelines acting as trust amplifiers rather than simple intermediaries. Once access is shared across organisations, accountability fragments and the blast radius expands beyond the original breach. The implication is that third-party identity must be governed as part of the same control plane as internal identities.

Multi-administrator approval for destructive operations belongs in the same category as access governance. The Stryker wipe shows that one authenticated administrator can create enterprise-wide impact when high-risk actions lack a second decision boundary. That is a failure of privilege design, not only incident response. Practitioners should treat approval separation for destructive operations as a core identity control, not an optional workflow.

Identity supply chain risk is the new form of trust debt. Reused credentials, cross-tenant access, and long-lived automation tokens accumulate hidden exposure until a breach reveals how many downstream systems were depending on one upstream trust decision. That debt is not visible in traditional authentication reporting. The implication is that identity governance has to measure inherited trust, not only active accounts.

From our research library:

• 92% of organisations expose NHIs to third parties, raising concerns about supply chain security, according to the Ultimate Guide to NHIs.
• Read next: NHI Lifecycle Management Guide

What this signals

Identity supply chain risk is a control-plane issue. The practical problem is not simply stolen credentials. It is that one trusted identity can be accepted by multiple downstream systems before governance catches up, which means inherited trust must be measured and constrained as part of access design.

Trust debt will keep growing wherever partner access, automation, and reuse intersect. The more an environment depends on cross-tenant access, embedded service credentials, and CI/CD tokens, the harder it becomes to prove that a privileged path is still necessary. That is why continuous review of downstream trust paths should become a standing programme activity.

The 92% of organisations that expose NHIs to third parties, according to the Ultimate Guide to NHIs, shows how widely this risk is distributed. When third-party credentials and trust relationships are already pervasive, the governance question becomes whether organisations can still tell which inherited access is truly authorised.

For practitioners

• Map downstream trust paths Document which administrators, partners, cloud roles, and service accounts can open access in other environments without reproof of intent. Prioritise shared SSO, federated, and vendor-managed paths first.
• Classify non-human identities by blast radius Group service accounts, API keys, and automation tokens by owner, expiry, and the systems they can reach so reused credentials can be removed from high-impact chains.
• Add execution-time checks for destructive actions Require a second governance decision for device wipes, policy changes, tenant-wide resets, and other irreversible operations instead of trusting the original session alone.
• Review third-party access as a living dependency Continuously validate which BPOs, vendors, and software pipelines still need access, because inherited trust often outlives the business relationship that created it.
• Remove reusable trust bridges from CI/CD and cloud paths Rotate or revoke credentials exposed in build systems, pipelines, and vendor integrations where one leaked token could unlock multiple downstream environments.

Key takeaways

• Attackers no longer need to break every control boundary when one trusted identity can open several downstream environments.
• The article’s examples show that administrative credentials, SSO accounts, cloud roles, and CI/CD service accounts can all become propagation points.
• The most effective response is to govern inherited trust, require execution-time checks for high-impact actions, and reduce reusable cross-environment access.

Key terms

• Identity supply chain: An identity supply chain is the network of trusted accounts, roles, tokens, and delegated permissions that connect one system to another. When one link is compromised, attackers can inherit access downstream and use legitimate trust relationships to spread impact across environments.
• Downstream Trust Path: A downstream trust path is the route from a trusted supplier or integration into the customer environment. It matters because attackers do not always need to breach the customer directly if they can abuse a legitimate trust relationship that already has access.
• Execution-Time Authorization: Execution-time authorization is the practice of checking access at the moment an action is taken, rather than granting broad standing access in advance. In agent systems, this limits what the model can do to the permissions currently held by the user and the specific action being requested.
• Trust debt: Accumulated security risk created when access assumptions are not revalidated quickly enough for the pace of modern automation. In identity programmes, trust debt appears when roles, secrets, or agent permissions persist longer than the environment that justified them.

Deepen your knowledge

NHI governance, agentic AI identity, and machine identity lifecycle are core topics in our NHI Foundation Level course, the industry's only accredited NHI security programme. If you are responsible for identity security strategy or NHI governance in your organisation, it is worth exploring.