@Decopi in my opinion Application Control is just where it belongs, part of firewall. It is the firewall job to manage connections.
I can imagine a scenario, where ZA says: "Let's build the most minimalist software, where almost everything behaves automatically".
In this scenario, App Control and Firewall Control really are not needed as part of the UI. As you perfectly explained here:
The firewall already applies a series of rules. It has few allow rules and the last one is called “Cleanup Rule” where all traffic not allowed goes and is blocked. The application control takes care of limiting the apps. Together, they ensure connection not desired by the user and not needed are not initiated.
And ZA and you are right!, this can be one scenario, it's totally valid and depends on ZA approach.
So, why I don't like it?
Because this approach will work only for a "safe - list"... made by ZA. And "safe - lists" are useful, and they help!, but in a zero-day-attack scenario, software never should trust "safe - lists".
Important to remind that I like the minimalist approach! I just never liked the "too minimalist ZA" approach. I don't feel comfortable with the:
a. Check a safe-list
b. "Allow all" (that it's on the safe-list)
In short: If ZA approach is based on "safe-list => Allow All"... then, the current App Control/Firewall Control is almost useless, because users can block only stuff under ZA "safe-list". This ZA approach is not adding security, it adds only a small degree of administrative control for safe-listed stuff.
Again, I grant you that ZA approach will work for Average Joe's, they're going to be happy with an automatic software, silent, no decisions need to be taken from Average Joe.
But personally, I don't like it, I don't feel comfortable (with the "a." above). And I believe that small improvements can make the current App Control + Firewall Control much more powerful. If ZA already took the effort to create a small UI for App Control + Firewall Control, then now another small step will make it very powerful.
What must be done from here:
-I believe firewall should automatically apply blocks to apps not classified as safe (the Check Point ThreatCloud network knows what’s safe and what’s not).
-Perhaps user prompt so user can decide
-Option to terminate apps, not just to block their connection (that’s in Harmony Endpoint).
Option to add apps in advance (as mentioned by Decopi).
Nevertheless, app control indeed is a positive improvement. Also, I hope before final release, engines will be updated to 86.80 as well and not 86.72.
Now you're talking! Hell, yeah!
ZA can keep current approach! I'm not talking about structural changes. I'm talking about "complements", small further steps, for example:
1. App and Firewall with separated UI controls. An unified alternative might be a Firewall Control, with the option of terminating processes.
2. As
@Trident said, ZA can keep current approach, but can offer a kind of "Advanced Options":
2.1 General options ("Block All", "Allow All", "Automatic", "Manual") for both, App Controls and the Firewall Controls.
2.2. The "Manual" option should allow users to block any connection + any process, not just known or safe Apps.
2.3 The "Manual" option is not quiet/silent, needs the
@Trident suggestion "user prompt => user can decide"
In short, if Average Joe wants a silent ZAESNG, he can choose the "automatic" option (based on ZA safe-list + few logical rules). This Joe will need to trust ZA, but he'll gain a silent peaceful software.
And if another user wants "Advanced Options", then he'll gain small control over any process (execution AND connection), but he'll need to deal with ZA pop-ups.