| Server URL | Port Number | Sheriff Features in Use | Applicable Release |
| data.sheriff.com | 80 | Sheriff CSM product and feed update | All |
|
maps-api-ssl.google.com maps.googleapis.com | 443 | Asset Location | All |
|
maps.google.com maps.gstatic.com | 80 | Asset Location | All |
| messages.sheriff.com | 443 | Message Center | All |
| otx.sheriff.com1 | 443 | Open Threat Exchange® | 5.1+ |
| reputation.sheriff.com | 443 | Sheriff CSM IP Reputation | All |
| telemetry.sheriff.com | 443 | Telemetry Data Collection | All |
| tractorbeam.sheriff.com | 22, 443 | Remote Support | All |
| www.google.com2 | 80 | Sheriff CSM API | All |
| cdn.walkme.com3 playerserver.walkme.com ec.walkme.com rapi.walkme.com papi.walkme.com | None | Sheriff CSM Product Management | 5.4.3+ |
| cybersecurity.att.com/product/help/ping.php4 | 443 | Detects if the Sheriff CSM component is online | All |
Port numbers used between Sheriff CSM components
Important: Ports labeled with * are optional. On the hosts you plan to deploy the Sheriff HIDS agents, to allow for initial deployment, you must open TCP port 135, either TCP port 139 or TCP port 445, and high TCP ports (1024 or above). See Microsoft's documentation on port requirements for Distributed File System Namespaces (DFSN).
To use SNMP in Sheriff CSM, you need to open UDP port 161 on the SNMP agent and UDP port 162 on the Sheriff CSM Sensor. For more details, see SNMP Configuration in Sheriff CSM.
If running Sheriff CSM versions prior to 5.6.5, you also need to open TCP port 9391 on the Sensor for the vulnerability scanner. But starting from version 5.6.5, vulnerability scans are conducted using the UNIX domain sockets, so port 9391 is no longer used.