Troubleshoot Automatic Policy Discovery Results
If automatic policy discovery results are not what you expect, check the following:
Extend the selected time range to include more data
Extend the time window to include more data and to capture events that happen infrequently. For example, if an application generates a complex quarterly report using data drawn from several provider applications, be sure to include a time range that includes that traffic.
Avoid data gathered before certain changes
If the scope definition has changed, or data gathered before a certain time has become invalid for some other reason, be sure your time range does NOT include data before that point.
Exclude misleading traffic flows
Exclusion filters may need to be configured or modified.
There are multiple places exclusion filters can be configured, and multiple places they can be enabled or disabled. Check each location:
-
Check the exclusion filters configured for the workspace.
-
Check the default exclusion filters configured at the bottom of the Default Policy Discovery Config page.
-
Check which exclusion filters are enabled in the Advanced Configurations section in the workspace's settings for automatic policy discovery.
-
Check which exclusion filters are enabled in Advanced Configurations section on the Default Policy Discovery Config page.
-
If you are using Default Exclusion Filters, make sure you have clicked Save on the Default Policy Discovery Config page to make those configurations available to individual workspaces.
For details, see Policy Discovery Flow Filters and subtopics.