1

We are a small MSP who currently use S1 through a reseller. We haven’t been using the Network Control\Firewall feature but are interested in implementing it as an alternative to Windows Defender Firewall. Obviously the firewall starts as completely empty with no policies.

We understand how to create rules, tags, order rules, etc. But we were hoping to get guidance on what actual rules we should or shouldn’t create - things like ‘on Windows systems, you need these allow rules if you want windows updates to continue working’ or ideally a basic template that will allow critical network reliant OS functions to work, that we can then build upon. We did ask our reseller for support on this and all they could do is link us to the knowledge base on how to create rules, which we’ve already read and doesn’t answer the actual question.

I realize that the majority of the rule creation is dependent on what we are going to be using it for. For example, if we have customers running a machine shop, we’ll need to add rules so they run their CATIA license server on a protected system, and so on. We’re not looking for hand holding over that. Just some basic guidance, because right now our guy piloting this is considering just duplicating the pre-defined rules in Windows Firewall with a block all rule at the end.

1 Spice up