← 返回列表

Zero Trust: From Perimeter to Kernel — How Riptides Pushes the Boundary

单站 Riptides Labs Blog 入库 2026-11-18T06:00:31

In the evolving threat landscape, “zero trust” is hardly a new phrase — but it is more important than ever. As attackers become more sophisticated, identity-based, lateral movement, and subtle persistence-based threats are no longer edge cases; they’re part of the assumed baseline. This post will walk through the general principles of zero trust (drawing on sources like John Kindervag’s original model, Google’s BeyondCorp/BeyondProd, Cloudflare’s implementation), then introduce how Riptides takes zero trust further, from the perimeter, to the node, to the kernel and why that matters for modern infrastructure security.

TL;DR: We achieve this kernel-level zero trust using strong attestation, SPIFFE for strong workload identity and kTLS for secure, identity-bound communication.

The General Principles of Zero Trust

Let’s begin with what zero trust means in practice, drawing from the original “never trust, always verify” model and how major players have implemented it.

Origins: Kindervag & the “Perimeter is Dead”

Key Concepts (as distilled over time)

Established guidance from Kindervag, NIST, and Google shows that robust zero trust architectures typically include:

  1. Strong Identity & Authentication
    Every user, every device, every service must prove who they are. Credentials, device posture, attestation, identity signals: these are continuously evaluated.
  2. Least Privilege Access / Principle of Minimal Privilege
    Access granted only to what is needed, for as long as it is needed. Permissions are narrowly scoped, ephemeral where possible.
  3. Micro-Segmentation
    Even within the data center or network, break up the environment so that lateral movement is constrained. Each boundary (service-to-service, process to process) is guarded.
  4. Continuous Verification / Context Awareness
    Trust decisions are not static. They consider context: device health, recent behavior, time, location, the system’s state.
  5. Monitoring, Auditing, Feedback, and Automation
    You need visibility into what is going on (flows, anomalies), to enforce policy, and to adjust dynamically.
  6. No Implicit or Perimeter Trust
    Simply being “inside” a network doesn’t confer trust. All traffic (east-west, north-south), all processes, all workloads must be verified.

Perspectives: Google BeyondCorp / BeyondProd & Cloudflare

Google’s BeyondCorp & BeyondProd

Cloudflare’s Zero Trust & “Access”

The Riptides Narrative: Zero Trust at the Kernel

The Riptides Narrative: Zero Trust at the Kernel

From Perimeter → Node → Kernel

Many zero trust implementations focus on either:

At Riptides, we believe zero trust should start even deeper: at the kernel.

So: for Riptides, it’s not enough that “access came from a trusted host” — the code itself, its provenance, its execution context, its behavior must be verified, attested, and assigned identity. That identity becomes the basis for further trust decisions.

Getting Trust Once Identity is Established

Once a workload/process has passed attestation and obtained a SPIFFE identity (an SVID), that becomes the key to building more complex trust relationships:

To dive deeper into how we handle workload identity federation and on-demand credential injection, take a look at these posts:

Why Starting in the Kernel Matters

Interested in how our Linux kernel journey unfolded and what we learned along the way?

How Riptides Realizes This in Practice

Putting It All Together: The Riptides Zero Trust Stack (Kernel-First)

Layer What It Covers Trust / Identity / Controls
Kernel / Process Attestation Code origin, integrity, execution environment SPIFFE IDs issued only after attestation; no userspace code is trusted by default
Inter-process / Service Communication Workload → workload, on same host or across hosts mTLS with SPIFFE IDs, policy enforcement per identity
Node / Host The host’s posture, environment, security properties Host attestation, secure boot, minimal trusted host invariants
Data Center / Cloud Networking, segmentation, environment boundaries Trust federated via identity, policies enforce cross-workload access
Multi-Cloud / Hybrid / Cross-Partner Heterogeneous environments, partners, external workloads Identity federation, on-demand credentials, consistent identity model across boundaries

Conclusion

Zero trust isn’t a product you buy; it’s a mindset, a set of architectural commitments. From Kindervag’s early formulation through Google’s BeyondCorp/BeyondProd, Cloudflare’s identity-based enforcement, we’ve seen how zero trust can dramatically reduce risk, but also how most implementations still assume some level of implicit trust and/or static credentials.

At Riptides, we push the boundary further: kernel first: trust nothing in userspace without attestation; only then issue identity; only then allow communication, based on fine-grained policy; extending trust across clouds via federation and credential injection. This gives us: stronger guarantees, smaller blast radius, and more defensible, resilient infrastructure. If you’re building systems today, especially cloud-native, distributed, hybrid or multi-cloud, it’s no longer sufficient to trust by node or network zone. The kernel is where the implicit trust still lingers — remove it, and you’re in a much stronger security posture.

How exposed are your workloads?

Run the NHI Security Audit Checklist, 8 questions to map your credential exposure, attribution gaps, and lateral movement surface across your own environment. Takes about 15 minutes.

Run the Checklist

Follow us on LinkedIn and X for more updates.

原文链接:https://riptides.io/blog/zero-trust-from-perimeter-to-kernel---how-riptides-pushes-the-boundary