- Jul 5, 2017
- 109
I just came across a mention about TinyWall and I looked up their website. I'm curious about how it actually works in practice. They say that
I agree about "security fatigue", but I'm not so sure about the practicality of "the user will only notice that a program has been denied internet access when he can't use it any more".
I use Windows Firewall Control and I get notifications about new outbound access attempts and I act accordingly. Some of them refer to utilities or maintenance software installed by my PC vendor. The same applies to some requests by Microsoft. I normally allow these. How would TinyWall respond to outbound access requests by such programs?The no-popup approach
The problem
Most firewalls are based on the same interaction principles. Basically, whenever an application is trying to access the internet, display a popup asking the user what to do. This is not only annoying for the user, but is also less than secure. On an average computer, a lot of applications are trying to access the internet. Displaying a popup for each app makes it very probable that unneeded applications will gain access to the network, as it increases the likelyhood of the user granting unnecessary rights to many applications. This phenomenon could be characterized as "security fatigue", and at its extreme, the user does not verify any more what he gives internet access, but just blindly allows programs that ask for it.
The solution
TinyWall takes a different approach. It does not display popups that urge users to whitelist apps. In fact, it will not notify you of any blocked action at all in real-time. Instead of showing popups, TinyWall makes it easy to whitelist or unblock applications by different means. For example, you can just initiate whitelisting by a hotkey, then click on a window that you want to allow. Or, you can select an application from the list of running processes. Of course, the traditional way of selecting an executable also works. This approach avoids popups, but still keeps the firewall very easy to use. Most importantly, with the no-popup approach, the user will only notice that a program has been denied internet access when he can't use it any more. Consequently, users will only unblock applications that they actually need and none more, which is optimal from a security standpoint.
I agree about "security fatigue", but I'm not so sure about the practicality of "the user will only notice that a program has been denied internet access when he can't use it any more".