To function to their full potential both Snare Agent Manager (SAM) and Snare Enterprise Agents require allowances to transmit data through corporate firewalls. Below are the default ports and protocols used by these products. Please take time to consider the information here and adjust your network firewall configuration accordingly.

Snare Agent Manager

The Snare Agent Manager requires network connections for two important tasks:

1. Configuration via its web management interface
2. Communication and licensing of Snare Agents

If deploying the SAM for use for agents running on the Internet, then it is recommended to use the SAM in a DMZ and only expose the tcp port 6262 to the internet for client systems to connect to. Its considered general security practice to never expose the corporate LAN systems to the Internet directly. The web management port for the SAM should be under access restrictions due to providing admin access to the application. This concept is the same for when the SAM in Snare Central is used for providing agent license access to systems on the Internet, ie the Snare Central server for this should be a separate server running in the DMZ. 

The table below outlines the default ports used for each Snare products when communicating with SAM.

*Default ports

Agent Management Console (via Snare Server)

The Agent Management Console (AMC) requires network connections when crawling and configuring communication with Snare Enterprise Agents.

The table below outlines the default ports used for each Snare products when communicating with AMC.

*Default ports

Snare Enterprise Agents - Web Management Interface

All Snare Enterprise Agents provide a web management interface that enables easy configuration and maintenance of the software.

The table below outlines the default ports used by each Agent.

*Default ports

...