nodeProtect works by configuring the built-in Firewall in Windows. When the nodeProtect agent is installed on a system, it will “phone home” to the nodeProtect service and get the most current settings.
nodeProtect is authoritative of the configuration, meaning that all locally-configured firewall settings, both system default and manually configured Inbound and Outbound rules, will be replaced by the rules configured in nodeProtect. Make sure you have configured all necessary rules before applying the configuration.
The most common way to get started is detailed below:
1. Deploy nodeProtect Agent via you favorite software delivery system. The Agent is in MSI format with a fully featured silent syntax. All the settings needed for silent installation are available under Settings (cogwheel in the upper right corner)
2. Inventory the current configuration. This can come in handy for importing firewall rules and getting information about current configurations.
3. Use node groups if you have many systems that should have the same firewall configuration. Exemple: WebServerFarm1, CitrixFarm1, SQLServers etc.
4. Next up is create firewall rules. You can create them yourself, import rules from analysis jobs och use nodeProtect-provided templates.
5. IP scopes are the next elements to configure. This lists the remote addresses needed when configuring what subnet and IP adresses are allowed to communicate with the protected end node.
6. Policies are used to bind all the node and node groups with IP scopes and firewall rules.
7. When all is configured and you are happy with all the settings, you Apply the configurations to your end nodes.