![]() For a complete list of ports used in Deep Security, see Port numbers, URLs, and IP addresses. These are the default port numbers - yours may be different. (For more information, see Agent-manager communication.) This is required to listen for agent heartbeats. This is required for access to the Deep Security Manager web UI and API. Alternatively, you can Prevent Deep Security from automatically adding iptables rules and add them manually instead: By default, these rules are added when Deep Security Manager starts up and removed when the manager is stopped or uninstalled. If iptables is enabled on the computer where Deep Security Manager is being installed, there are two required iptables rules. ![]() If iptables is disabled, it stays disabled.) However, if the iptables service is running, Deep Security Agent and Deep Security Manager require certain iptables rules, as described below. ![]() (If iptables is enabled, it stays enabled after the agent installation. Deep Security Agent no longer disables iptables. With Deep Security 10.2 and higher (including Deep Security 11), the functionality around iptables has changed. However, the iptables service is used for more than just firewall (for example, Docker manages iptables rules as part of its normal operation), so disabling it sometimes had negative consequences. When Deep Security Agent 10.1 or earlier was installed on Linux, it disabled the iptables service to avoid firewall conflicts unless you added a configuration file that prevented that change.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |