Outbound firewall - app / service whitelisting

I'm considering trialling Connection Explorer but first I want to confirm that it can operate in the way I need. Can I tell it to block everything then prompt me as each Windows app or service attempts to access the Internet, giving me the option to allow or ignore (continue to block)?

Also, does it have any ability to identify in more detail what underlying component of Windows is making the request? Or does it just identify things as 'svchost' for example? 

373 views 4 replies
Reply #1 Top

Hello,
I have forwarded your problem/question to Stardock Support Team for their assistance. Please keep an eye on this thread for any updates. We appreciate your feedback and patience. Thank you.

Basj,
Stardock Community Assistant

Reply #2 Top

Right now, there is a not a full lockdown and then prompt on a request-by-request basis. Connection Explorer lets you see what is going on with basic blocking capabilities but it's not currently setup to be a full firewall management tool (yet).

And for now, it's going to say things like SVCHOST without the specific identity associated with it - the intent is to continue to push down into the connection stack to further help identify what is causing the outbound/inbound traffic but I had to put a line in the sand so that we could initially ship the product before adding more features.

So, the TLDR, more features coming after a couple bug fixes go out.

Reply #3 Top

Thanks Brad, it's good to know you have further plans, I will keep an eye on developments. I like the reassurance whitelisting offers. A while back I threw my arms up with Windows' shenanigans and went for firewall blocking and a forward web proxy with DNS block lists. This works ok for me with the exception of Windows Updates that require a proxy exclusion to make BITS and such work.

A client side app like Connection Explorer might offer much better insight into what Windows is up to and allow for simpler lock-down management for home users who aren't worrying about lots of clients on a corporate network.

Reply #4 Top

Quoting bdsams, reply 2

Connection Explorer lets you see what is going on with basic blocking capabilities but it's not currently setup to be a full firewall management tool (yet).

End of bdsams's quote

I really hope that Connection Explorer in the future, in addition to monitoring connections, it could also be a firewall, perhaps with support of wildcards patterns for executable's paths and also Allow / Block executable's domains, if needed.