README.md: use a dedicated zero-trust diagram, stop reusing the doc's
Was reusing netbird-zero-trust-mesh-topology.svg (the doc's detailed peer-topology diagram) in the README too - breaks this repo's own established convention of the README getting its own dedicated asset even when covering related material (see readme-trust-boundaries- blast-radius.svg vs architecture-overview-trust-depth.svg). New diagram is a simple perimeter-vs-zero-trust conceptual contrast, matching the README section's generalized framing rather than NetBird's specific implementation topology.
This commit is contained in:
2 files changed
+5
-1
No files matched your search
@@ -54,7 +54,7 @@ Zero trust is where enterprise security has been heading for years now — NIST
|
||||
|
||||
This fleet doesn't just talk about that model — the four trust boundaries above are one expression of it, and remote/roaming access is a second, separate one, since "how do you reach the fleet from outside it" is a genuinely different problem from "how do services inside it talk to each other." That second problem is solved with a self-hosted zero-trust mesh (**NetBird**, WireGuard-based): every host and every device gets its own cryptographic identity, access is granted per-identity through explicit policy, and the mesh's own built-in allow-everything default is disabled — nothing crosses it unless a rule says so.
|
||||
|
||||

|
||||

|
||||
|
||||
Full breakdown — the mesh-vs-VPN reasoning, the complete policy model (groups, scoped keys, peer approval, posture checks), the real bring-up story, and live evidence straight from the running system: [docs/netbird-zero-trust.md](docs/netbird-zero-trust.md).
|
||||
|
||||
|
||||
Reference in new issue
Block a user