Topic starter
17/08/2026 4:40 pm
TL;DR: Teleport says modern infrastructure now depends on non-human identities that still rely on static credentials, excessive permissions and minimal oversight across CI/CD, IaC, multi-cloud federation and MCP-driven automation. Human-paced trust models do not survive machine-paced execution, so governance must shift to short-lived identity and job-scoped authorization.
Editorial analysis by NHI Mgmt Group, based on content published by Teleport: “Your Infrastructure Has a Non-Human Trust Problem”.
Key questions
Q: What breaks when CI/CD pipelines rely on static secrets?
A: Static secrets create a reusable attack path into production infrastructure.
Q: Why do broad machine permissions increase infrastructure risk?
A: Broad permissions increase risk because automation rarely needs permanent, cross-environment authority to finish one task.
Q: How do teams know if machine identity governance is actually working?
A: Look for evidence that each service account has a current owner, a narrow purpose, a short credential lifetime, and a clear retirement path.
Practitioner guidance
- Replace standing secrets with short-lived workload identity Issue time-bound credentials for CI/CD runners, bots and deployment jobs so each workflow gets only the access needed for that execution window.
- Bind IaC roles to deployment context Scope cloud permissions by repository, environment and job so infrastructure-as-code runs cannot reuse broad service accounts across unrelated targets.
- Separate AI-triggered actions from shared API keys Require MCP-connected agents to obtain per-action identity and explicit operation scopes instead of using one reusable key for many tool calls.
Bottom line: Modern infrastructure increasingly depends on machine identities that are trusted for too long and too broadly across deployment paths.
What's in the full article
Teleport's full article covers the operational detail this post intentionally leaves for the source:
- Step-by-step examples for securing GitHub Actions, Jenkins and GitLab runners with short-lived credentials
- Terraform and cloud role-assumption patterns for repository-scoped deployment identities
- The MCP access model used to scope AI actions, log prompt-triggered operations and eliminate shared API keys
- A worked example of multi-cloud workload identity using SPIFFE-style certificates and central trust policies
👉 Read Teleport's analysis of non-human trust problems in infrastructure →
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
17/08/2026 4:45 pm
Non-human trust debt is now a governance problem, not a tooling problem: Modern infrastructure accumulates trust debt when machine identities are granted more reach than their task requires and then left in place. The article shows that the same pattern repeats in CI/CD, IaC, federation and MCP because the underlying governance model still assumes slower, more reviewable access. Practitioners should read this as a signal that NHI governance has become a first-class control plane.
A few things that frame the scale:
- 96% of organisations store secrets outside of secrets managers in vulnerable locations including code, config files, and CI/CD tools, according to the Ultimate Guide to NHIs.
- 24,008 unique secrets were exposed in MCP configuration files in 2025 alone, the protocol's first year of widespread adoption, according to the State of Secrets Sprawl 2026.
A question worth separating out:
Q: What is the difference between static credentials and workload identity?
A: Static credentials are reusable secrets stored somewhere on disk or in a manager, while workload identity uses runtime-issued assertions or certificates that expire quickly and are tied to a specific service or task. For NHI governance, workload identity is preferable because it limits reuse, reduces persistence, and narrows the blast radius of theft.
👉 Read our full editorial: Your infrastructure has a non-human trust problem