From cd55c3d0cf1660daca26ecc7ac615d256fb36a97 Mon Sep 17 00:00:00 2001
From: Jack Carter <128555021+SunsetDrifter@users.noreply.github.com>
Date: Tue, 21 Jul 2026 16:13:37 +0200
Subject: [PATCH] docs: remove incorrect posture-check troubleshooting bullet
 in Zero Trust guide (#870)

The "Policy exists but connection is still blocked" entry told readers to look
for "blocked due to posture" or "no matching policy" entries in Traffic Events.
Those entries do not exist: a failed posture check or group mismatch is resolved
on the management server and never produces a Traffic Event. Drop the bullet;
the remaining checks (policy and posture checks under Access Control, group
membership under Peers) are the accurate guidance.
---
 src/pages/use-cases/security/implement-zero-trust.mdx | 1 -
 1 file changed, 1 deletion(-)

diff --git a/src/pages/use-cases/security/implement-zero-trust.mdx b/src/pages/use-cases/security/implement-zero-trust.mdx
index 99e5a133..c7784612 100644
--- a/src/pages/use-cases/security/implement-zero-trust.mdx
+++ b/src/pages/use-cases/security/implement-zero-trust.mdx
@@ -808,7 +808,6 @@ What to do:
 
 - Check the policy and its posture checks in **Access Control → Policies**.
 - Confirm the peer's group membership in the dashboard under **Peers**.
-- Look at Traffic Events for explicit "blocked due to posture" or "no matching policy" entries.
 
 Useful commands on the peer: