No unprotected flows are visible in the Visibility & Planning dashboard.
Flow collection appears to be functioning, but the UI shows zero unprotected flows.
SSP
The issue occurs when a default ANY–ANY–DENY rule is configured in the environment.
Because this rule denies all traffic by default, no traffic is allowed to traverse or reach the analysis engine. As a result, no unprotected flows are detected or recorded in the UI.
In other words, the system is functioning as designed—traffic that is dropped by the default deny rule will not appear as an unprotected flow.
The system is functioning as expected.
To view unprotected flows and plan microsegmentation policies for new workloads, follow the steps below:
TESTGROUP, within the Applications section.
The default ANY–ANY–DENY rule should remain in place as a best practice for enforcing least privilege.
Only create specific allow rules for legitimate application traffic that needs to be analyzed or permitted.
If unprotected flows are still not visible after creating allow rules, ensure:
The workloads are actively generating traffic.
The relevant sensors and collectors are operational.