What would you like to add or change?
I'd like the Network Activity page to support filtering by the scope/source of the applied rule, for example:
Default Network Action @ GlobalOutgoing Rule @ Global- ...
Incoming Rule @ Global- App-specific rules
- Other rule scopes
The most valuable filter, in my opinion, would be Default Network Action.
Why do you and others need this?
Users who configure Default Network Action = Block often use the Network Activity page to gradually build an allowlist by explicitly allowing only the required connections or block specificy domain or IP in the Global or App Settings.
Currently, once the activity log contains entries generated by different rule types, it becomes difficult to identify which connections were blocked solely because of the default policy.
Adding a filter for Default Network Action would provide a dedicated view containing only those events. This would make it much easier to periodically review blocked connections, explicitly allow or deny them, and progressively reduce the number of events that depend on the default rule.
This feature would significantly improve the usability of the Network Activity page for users adopting a default-deny security model, making rule management cleaner and more efficient.
What would you like to add or change?
I'd like the Network Activity page to support filtering by the scope/source of the applied rule, for example:
Default Network Action @ GlobalOutgoing Rule @ GlobalIncoming Rule @ GlobalThe most valuable filter, in my opinion, would be Default Network Action.
Why do you and others need this?
Users who configure Default Network Action = Block often use the Network Activity page to gradually build an allowlist by explicitly allowing only the required connections or block specificy domain or IP in the Global or App Settings.
Currently, once the activity log contains entries generated by different rule types, it becomes difficult to identify which connections were blocked solely because of the default policy.
Adding a filter for Default Network Action would provide a dedicated view containing only those events. This would make it much easier to periodically review blocked connections, explicitly allow or deny them, and progressively reduce the number of events that depend on the default rule.
This feature would significantly improve the usability of the Network Activity page for users adopting a default-deny security model, making rule management cleaner and more efficient.