Access to Vulnerability ProtectionDeep Security Manager Web console browser interface.
Access to Deep Security Manager by an ESXi server to request the Deep Security Filter Driver during the preparation of an ESXi server for Anti-Malware protection.
Requests for Security Updates by the Deep Security Virtual Appliance.
Protocol: TCP
Initiated By:
Web Browser
ESXi server
Deep Security Virtual Appliance
Connected To: Vulnerability ProtectionDeep Security Manager
Proxy: No
Configuration: This port is configured during the Vulnerability ProtectionDeep Security Manager installation process.
Port: 4120 (default)
Use: Agent/Appliance-initiated communication with the Manager. The Agent/Appliance sends Events to the Manager, and the Manager sends Configuration Updates.
Protocol: TCP
Initiated By: Agent/Appliance
Connected To: Vulnerability ProtectionDeep Security Manager
Proxy: No
Configuration: This port is configured during the Vulnerability ProtectionDeep Security Manager installation process.
Notes: The vCenter provides three URLs on the ESXi to the Vulnerability ProtectionDeep Security Manager to upload the three vmdk's that make up the Virtual Appliance. Vulnerability ProtectionDeep Security Manager establishes an HTTPS connection and POSTS the vmdk's to the ESXi.
Local Software Distribution Web Server
Port: 80 or 443
Use: Agents can be configured to request their Software Updates from these web servers instead of Deep Security Relays