TL;DR: AI-directed intrusion workflows can enumerate systems, harvest credentials, and move laterally at machine speed, which is why Keyfactor argues PKI and x.509 certificates are now foundational for infrastructure defence. Passwords and MFA still protect people at the login screen, but they do not govern internal machine-to-machine trust or autonomous attack behaviour.
At a glance
What this is: NHI Mgmt Group's analysis, drawing on Keyfactor's blog post: AI-directed intrusion workflows make PKI, certificates, and workload identities central to resisting machine-speed credential abuse.
Why it matters: It matters because IAM, PAM, and NHI teams need controls that govern internal service trust, not just human authentication at the edge.
Context
AI-driven intrusion workflows change the problem from human login abuse to internal trust abuse. Once an attacker can reason over exposed credentials at machine speed, the real question becomes which identities authenticate services, devices, and workloads inside the environment.
The article argues that passwords and MFA are the wrong control plane for that problem because they were built for people, not for continuous machine-to-machine authentication. That puts NHI governance, workload identity, and certificate lifecycle management at the centre of the defence model.
Key questions
Q: What fails when AI-driven attackers can reason over internal credentials at machine speed?
A: Review-based controls fail first because the attacker can discover and map access paths faster than human governance cycles can react. The practical weakness is not only stolen credentials, but the ability to test which ones unlock which internal services before defenders notice the lateral movement pattern.
Q: Why is MFA not a complete control for non-human identities?
A: MFA is built for interactive human authentication, while non-human identities usually authenticate with certificates, tokens, keys, or federated workload trust. Those mechanisms need lifecycle management, rotation, and scope control instead of a second human factor. Treating MFA as the answer for bots or service accounts leaves the real trust problem unresolved.
Q: What breaks if internal services still rely on shared secrets?
A: Shared secrets create a large reuse surface, so one exposed token can open multiple systems or paths. In practice that means credential theft becomes a privilege expansion problem, not just a login problem, and the attacker can pivot through trusted service relationships with very little friction.
Q: Should teams prioritise PKI over password hardening for infrastructure defence?
A: Yes, when the main risk is machine-to-machine trust rather than human login abuse. Password hardening helps at the edge, but PKI and workload-bound certificates govern the identity layer that AI-driven attackers actually exploit inside distributed infrastructure.
Technical breakdown
Why passwords and MFA fail against machine-speed attacks
Passwords and MFA are human-centric controls. A password is a shared secret, so it can be copied and reused once exposed. MFA adds a checkpoint for a person at login, but it does not govern the continuous authentication that happens between services, APIs, and workloads inside a distributed environment. When an adversary can enumerate systems and harvest internal credentials automatically, the login screen is no longer the main defensive boundary. The attack surface shifts to service accounts, bearer tokens, API keys, and certificates already trusted by internal systems.
Practical implication: move the primary control point from human login to service authentication and credential governance.
How PKI changes machine-to-machine trust
PKI replaces shared secrets with asymmetric cryptography. A private key stays inside a protected boundary, while the public key can be shared for verification. That changes authentication from secret comparison to cryptographic proof, which is much harder to steal and replay at scale. In infrastructure terms, certificates let services prove identity without exposing reusable passwords or static bearer tokens. That is why PKI is a stronger fit for internal trust than human-oriented authentication patterns when the actor is a workload, device, or automated system.
Practical implication: use certificates for service and device identity where reusable secrets create lateral movement risk.
Why mTLS and OAuth solve different problems
mTLS answers who a system is talking to, while OAuth answers what that system is allowed to do. Conflating them leaves a gap: a bearer token can still be stolen even when the authorization flow is sound. The article’s central point is that AI-directed operators exploited internal credentials and trust relationships, not just external login prompts. That means cryptographic identity for transport and workload trust must be paired with authorization scope control, rather than treated as interchangeable controls.
Practical implication: separate authentication from authorization and require cryptographic identity for machine communications.
Threat narrative
Attacker objective: The objective was to expand access across internal systems fast enough to support coordinated espionage and persistence before defenders could intervene.
- Entry began with AI-directed reconnaissance that identified accessible systems and harvested internal credentials from the environment.
- Escalation occurred when the attacker mapped which stolen credentials opened which services, then pivoted through internal trust relationships.
- Impact followed as lateral movement continued across more than two dozen organizations using machine-speed credential abuse and access chaining.
Breaches seen in the wild
- Sisense breach 2024: A credential in Sisense's GitLab reportedly opened S3 buckets of customer tokens, passwords and certificates; CISA urged a full reset.
- CISA Private-CISA GitHub leak 2026: A CISA contractor's public GitHub repo exposed AWS GovCloud admin keys, Artifactory credentials and plaintext passwords for six months.
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
PKI is becoming the minimum viable trust layer for machine identities: When internal systems authenticate each other through shared secrets, the attacker only has to find one reusable credential to open multiple paths. Certificates shift that burden because identity is verified cryptographically, not inferred from possession of a copied secret. For practitioners, the implication is that workload identity governance now sits on the same critical path as perimeter authentication.
The old assumption was that credentials are reviewed by people before they are abused. That assumption breaks when an AI-directed intruder can enumerate, test, and map access relationships continuously during the attack itself. The governance implication is not just faster response; it is that review-based models cannot be the primary control for ephemeral machine-speed abuse.
Workload-bound identity is now an architectural requirement, not a preference: The article shows that internal services, APIs, and devices are where autonomous or AI-assisted attackers gain leverage after the first foothold. That makes certificate lifecycle, revocation, and service authentication a core identity programme responsibility, not an infrastructure add-on. Practitioners should treat machine trust as a governed identity domain.
Identity blast radius is the new exposure metric: The real problem is not whether a password is strong enough for a person, but how far a compromised credential can travel inside the machine trust graph. AI-directed attackers exploit credential reuse, static tokens, and flat internal trust to expand reach rapidly. Identity teams need to measure how much privilege each secret can unlock across services and environments.
Passwords and MFA remain necessary for humans but insufficient for infrastructure defence: Human authentication controls stop at the boundary where machine identities begin to talk to each other. That split is now operationally important because attackers no longer need to impersonate a user to move laterally. The practitioner conclusion is to govern human IAM and NHI trust as separate, connected control planes.
From our research library:
- 67% of organisations still rely heavily on static credentials despite the risks they pose to agentic AI deployments, according to the 2026 Infrastructure Identity Survey.
- Read next: Agentic AI Security Guide
What this signals
Identity blast radius: The more systems a single workload secret can unlock, the more machine-speed attackers can amplify one foothold into a broad internal compromise. That changes identity work from credential issuance alone to access containment across service trust graphs.
Passwords and MFA remain necessary for humans, but they do not govern the internal trust relationships that AI-directed intrusions exploit. Security programmes that do not separate human authentication from workload authentication will keep leaving a blind spot inside the perimeter.
For practitioners
- Define a machine identity inventory Catalogue certificates, service accounts, API keys, bearer tokens, and other workload credentials by owner, environment, and expiry status.
- Move service-to-service calls to mTLS Require mutual TLS for internal service communication so that workloads authenticate with certificates instead of reusable shared secrets.
- Separate authentication from authorization Use PKI to prove identity and OAuth only to govern permissions, so a stolen token does not become a full trust bypass.
- Reduce internal credential blast radius Scope each service credential to the narrowest possible environment and revoke anything that can unlock multiple systems or tenants.
- Test revocation and rotation paths Validate that certificate replacement, token invalidation, and service offboarding actually remove access from internal dependencies before reuse can occur.
Key takeaways
- AI-directed intrusion workflows expose a structural gap between human login controls and the machine-to-machine trust used by infrastructure.
- The article shows that internal credential mapping and lateral movement can happen faster than review-based identity governance can respond.
- PKI, certificates, and workload identity reduce the reuse and replay risk that shared secrets and bearer tokens leave behind.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
OWASP Non-Human Identity Top 10 and MITRE ATT&CK address the attack and risk surface, while NIST SP 800-53 Rev 5 and NIST CSF 2.0 set the governance and control requirements practitioners need to meet.
| Framework | Control / Reference | Relevance |
|---|---|---|
| OWASP Non-Human Identity Top 10 | NHI-04 — Insecure Authentication | The article centres on insecure machine authentication and trust reuse. |
| NHI-07 — Long-Lived Secrets | Static credentials and bearer tokens are the attack surface described in the article. | |
| Recommendation — Apply NHI-04 to replace reusable machine secrets with cryptographic identity checks. Reduce long-lived machine secrets and enforce short-lived, certificate-backed credentials. | ||
| NIST SP 800-53 Rev 5 | IA-9 — Identification and Authentication (Non-Organizational Users) | Workloads, services, and devices authenticating to each other fall under IA-9. |
| Recommendation — Use IA-9 to govern service and workload authentication with certificates instead of shared secrets. | ||
| NIST CSF 2.0 | PR.AA-05 — Access Permissions, Entitlements and Authorizations | The article focuses on how internal identities gain access and move laterally. |
| Recommendation — Map workload access paths under PR.AA-05 and remove excess entitlements that expand blast radius. | ||
| MITRE ATT&CK | TA0006; TA0008 — Credential Access; Lateral Movement | The attack chain described credential harvesting and movement across internal systems. |
| Recommendation — Map the attack pattern to TA0006 and TA0008 to prioritise detection of credential theft and pivoting. | ||
Key terms
- Workload Identity: The identity assigned to a software workload, such as a containerised application, serverless function, or microservice, enabling it to authenticate to other services without storing static credentials.
- Mutual Tls: Mutual TLS is a transport security method where both client and server present certificates and authenticate each other. In implant frameworks, it helps prevent impersonation, supports encrypted sessions, and ties each deployment to its own trust material rather than shared credentials.
- Certificate Lifecycle Management: The governance of digital certificates from issuance through renewal and revocation, ensuring certificates are valid, monitored, and rotated before expiry. Expired certificates are a leading cause of outages and unplanned security gaps.
- Identity Blast Radius: The amount of damage a compromised identity can cause across systems, data, and infrastructure. In NHI environments, it is shaped by permissions, network reach, and administrative capability rather than by the credential alone. Reducing blast radius is a containment strategy that limits lateral movement and data exposure.
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 building or maturing an IAM programme, it is worth exploring.
Published by the NHIMG editorial team on June 25, 2026.
Updated on October 11, 2026.
NHI Mgmt Group, the independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org