Learn how to configure AppGuard first and then decide later what you want to do about the firewall. Don't try to learn and do everything all at one time.
@Lockdown , I know host-based firewall pretty well; my legacy configuration included TinyWall, and I have spent countless hours administering exceptions based on apps, ports and protocols.
I migrated from my legacy configuration containing TinyWall and assorted definition-based security apps to the following "OOTB Windows Firewall and locked-down AppGuard" implementation:
Meltcheesedec Security Configuration 2017.
@Umbra then stated that he thought OOTB Windows Firewall may not provide sufficient protection:
Appguard wont help against outbound connection. What if you install a FUD weaponized legit application that stealthily call home when it shoudn't? it will install on C , so Appguard won't block it, and then it will call home.
The situation you hope for is valid, if like me, you take time to deeply check every program you install.
Whereas in another thread you wrote:
The base protections on my test systems:
- AppGuard
- uBlock Origin
- Windows Defender
- Windows Firewall
- USB flash drive and DropBox for file backups
This uncomplicated set-up gives high protection. You can ask any long-time AppGuard user if the system ever got seriously infected while AppGuard protections were enabled.
Questions:
- in the "test systems" you referenced, do you configure Windows Firewall as Out of the Box/default?
- do you feel that "OOTB Windows Firewall and locked-down AppGuard" offers sufficient protection, or do you instead share the same concerns
@Umbra noted in the aforementioned quote?