Notifications
Clear all
Topic starter
17/08/2026 4:40 pm
TL;DR: Modern infrastructure now depends on NHIs that still authenticate with static credentials, excessive permissions, and weak oversight, according to Teleport, creating exposure across CI/CD, IaC, multi-cloud federation, and MCP-driven automation. The core problem is that access models built for human-paced review do not hold up when machines, runners, and AI-triggered actions execute at runtime.
NHIMG editorial — based on content published by Teleport: Your Infrastructure Has a Non-Human Trust Problem
By the numbers:
- 97% of NHIs carry excessive privileges, increasing unauthorised access and broadening the attack surface.
Questions worth separating out
Q: How should security teams eliminate static secrets from CI/CD pipelines?
A: Security teams should move from stored credentials to runtime-issued access wherever possible.
Q: Why do non-human identities increase cloud IAM risk so quickly?
A: Non-human identities increase cloud IAM risk because they multiply faster than human accounts and often carry persistent access with weak ownership.
Q: What breaks when AI agents rely on shared service accounts or API keys?
A: Shared credentials hide which actor actually performed the action, make revocation coarse, and blur accountability across humans and machines.
Practitioner guidance
- Eliminate durable secrets from automation paths Replace hardcoded tokens, shared SSH keys, and injected environment credentials with short-lived workload identities bound to a specific job or session.
- Split cloud roles by workflow and environment Assign separate least-privilege roles for each repository, deployment target, and environment so a single pipeline credential cannot cross boundaries.
- Bind MCP actions to auditable identities Require every tool call from an AI-enabled workflow to carry a scoped identity, role claim, and immutable log trail that links the action to the session.
What's in the full article
Teleport's full post covers the operational detail this analysis intentionally leaves for the source:
- Step-by-step examples for issuing short-lived certificates to CI/CD runners and bots in real workflows.
- Implementation detail for GitHub OIDC, AWS role assumption, and SPIFFE-based workload identity patterns.
- MCP-specific examples showing how scoped identity and audit logging are applied to model-driven actions.
- Concrete deployment patterns for multi-cloud federation with central trust and expiration handling.
👉 Read Teleport's analysis of non-human trust across CI/CD, IaC, and MCP →
Non-human trust in infrastructure: are your controls keeping up?
Explore further
View Full Forum → | NHI Foundation Course → | Our Services →
17/08/2026 4:45 pm
Static credential trust is the real infrastructure governance failure. The article describes a world where bots, runners, and agents still authenticate through long-lived secrets and broad service accounts. That is not a tooling detail. It is a governance failure because the identity layer is being asked to prove trust after the fact, when the access path already exists. The practitioner implication is that non-human access must be treated as a lifecycle problem, not a secrets-only problem.
A few things that frame the scale:
- 97% of NHIs carry excessive privileges, increasing unauthorised access and broadening the attack surface, according to Ultimate Guide to NHIs.
- Only 20% have formal processes for offboarding and revoking API keys, and even fewer have procedures for rotating them.
A question worth separating out:
Q: Who is accountable when an MCP agent accesses the wrong resource?
A: Accountability sits with the teams that defined consent, token handling, and policy review for the MCP deployment. If token passthrough, weak audience checks, or incomplete client approval allowed the request, that is a governance failure, not an agent anomaly. Frameworks such as NIST CSF and Zero Trust architecture expect explicit access validation.
👉 Read our full editorial: Your infrastructure has a non-human trust problem
