Granular Control of Appware/Application Behavior
not pursuing
T
Trent Bartley
Currently, the default behavior is to allow AppAware traffic.
However, if a user blocks a category like "Webmail & Chat" and wants to allow only specific applications within that category, they must manually add the associated domains to their Allow list.
This can be a bit cumbersome, an alternate option or consideration is below.
The introduction of three possible statuses for AppAware applications:
Unmanaged (default): Blocking is determined based on existing category/block list configurations.
Allowed: Explicitly allows traffic to the domains associated with the application, regardless of category blocking.
Blocked: Explicitly blocks the domains associated with the application, even if the broader category is allowed.
Minetta Gould
not pursuing
Clever suggestion! We’re sticking with the current AppAware model for now, so this isn’t something we’ll be building in the near term.
Still, it’s always helpful to see where the workflow feels clunky — keep the ideas coming!