Kaspersky Security 11.x for Windows Server

About Firewall rules

June 10, 2022

ID 146690

The Firewall Management task controls filtration of incoming and outgoing network traffic using allowing rules forcibly applied to the Windows Firewall during task execution.

The first time the task is started Kaspersky Security for Windows Server reads and copies all the incoming network traffic rules specified in the Windows Firewall settings to the Firewall Management task settings. Then the application operates according to the following rules:

  • If a new rule is created in the Windows Firewall settings (manually or automatically during a new application installation), Kaspersky Security for Windows Server deletes the rule.
  • If an existing rule is deleted from the Windows Firewall settings, Kaspersky Security for Windows Server restores the rule when the task is restarted.
  • If the parameters of an existing rule are changed in the Windows Firewall settings, Kaspersky Security for Windows Server rolls back the changes.
  • If a new rule is created in the Firewall Management settings, Kaspersky Security for Windows Server forcibly applies the rule to Windows Firewall.
  • If an existing rule is deleted from the Firewall Management settings, Kaspersky Security for Windows Server forcibly deletes the rule from the Windows Firewall settings.

Kaspersky Security for Windows Server does not work with blocking rules or rules controlling outgoing network traffic. Upon start of the Firewall Management task, Kaspersky Security for Windows Server deletes all such rules from the Windows Firewall settings.

You can set, delete and edit filtration rules for incoming network traffic.

You cannot specify a new rule to control outgoing network traffic in the Firewall Management task settings. All Firewall rules specified in Kaspersky Security for Windows Server control only incoming network traffic.

You can manage different types of Firewall rules: for applications and for ports.

Application rules

This type of rule allows targeted network connections for specified applications. The triggering criterion for these rules is based on a path to an executable file.

You can manage application rules:

  • Add new rules.
  • Remove existing rules.
  • Enable or disable specified rules.
  • Edit the parameters of the specified rules: specify the rule name, path to the executable file, and the rule usage scope.

Port rules

This type of rule allows network connections for specified ports and protocols (TCP / UDP). The triggering criteria for these rules are based on the port number and protocol type.

You can manage port rules:

  • Add new rules.
  • Remove existing rules.
  • Enable or disable specified rules.
  • Edit the parameters of the specified rules: set the rule name, port number, protocol type, and scope for application of the rule.

Port rules involve a broader scope than application rules. By allowing connections based on port rules, you lower the security level of the protected device.

Did you find this article helpful?
What can we do better?
Thank you for your feedback! You're helping us improve.
Thank you for your feedback! You're helping us improve.