Join our Newsletter — 33% off our NHI Course

Why does CircleCI show eBPF observability still miss credential reuse?

 

(@nhi-mgmt-group)
Member Moderator
Joined: 2 years ago
Posts: 20225
Topic starter  

TL;DR: eBPF observability can reveal workload activity, but it cannot stop a compromised process from reusing ambient credentials, tokens, or certificates, according to Riptides. Workload defenses still need enforcement at the point of connection to block lateral movement after a local compromise.

Editorial analysis by NHI Mgmt Group, based on content published by Riptides: “Why Deep Kernel Security Matters for Enterprises — When eBPF Falls Short”.

Key questions

Q: Why do ambient credentials increase lateral movement risk in workloads?

A: Because a valid token, password, or certificate can still be reused by an attacker who gains code execution inside the process.

Q: How can security teams tell if workload identity is actually being preserved?

A: Look for identity continuity across every hop, not just at launch.

Q: What breaks when eBPF is used for workload identity control?

A: eBPF breaks down when the job includes credential creation, certificate binding, or just-in-time delivery, because it is designed for safe inspection and lightweight enforcement rather than owning the identity lifecycle.

Practitioner guidance

  • Map ambient credential paths Inventory where workload secrets live in environment variables, config files, token stores, and certificate material so you know which processes can impersonate which services.
  • Separate observability from enforcement Keep eBPF-based tooling for telemetry and investigation, but assign a different control to actually permit or deny workload connections.
  • Bind trust to process identity Require the connection decision to follow the running process rather than the mere presence of a reusable secret on disk or in memory.

Bottom line: The article’s core warning is that observability alone cannot stop a compromised workload from using legitimate credentials to reach protected services.

Glossary terms: Ambient Credential Inheritance, Point-of-Connection Enforcement, Process Identity, Identity Blast Radius

Explore further

View Full Forum →  |  NHI Foundation Course →  |  Our Services →  |  Read the full analysis →


This topic was modified 4 days ago by NHI Mgmt Group

   
Quote
(@mr-nhi)
Member Moderator
Joined: 6 months ago
Posts: 20715
 

Visibility without enforcement is an identity governance gap, not a monitoring gap. Security teams often treat telemetry as if it were a control, but the article shows that seeing authenticated activity does not stop a workload from using a valid secret. The practical conclusion is that workload identity must be enforced where the connection happens, not inferred after the fact.

A few things that frame the scale:

  • Only 5.7% of organisations have full visibility into their service accounts, according to the Ultimate Guide to NHIs.

A question worth separating out:

Q: Should teams prioritise point-of-connection enforcement over more telemetry?

A: Yes, when the threat is credential reuse after workload compromise. More telemetry improves detection, but it does not stop a shell, script, or binary from using stolen trust. Enforcement matters most when your incident path depends on preventing lateral movement, not just observing it.

👉 Read our full editorial: Deep kernel security exposes the limits of eBPF observability



   
ReplyQuote
Share:

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.