When agents are decommissioned, the agents are still reported as non-contactable in the Agent Management Console (AMC). The reason for this is that the Snare Server keeps the old meta data associated with the old connection. These agents will roll off the Snare Server after 3 months. To remove the agent manually, you must remove […]Read More
Snare. The world standard for effectively gathering and filtering IT-event data for critical security monitoring, analysis, auditing and archiving.
The Snare Agent Management Console (AMC) is a subset of the Snare Server. The AMC allows configuration of large numbers of agents. The common issues around AMC are: Firewall ports not allowing inbound connections to 6161 or 6161 or 6163 for SQL Needing to set master agent server with the configuration you want to push to […]Read More
There is no technical user maximum you may have in the Agent Management Console. There is a logical maximum of 16 million i.e. A 10.x.x.x range. However there are some performance based maximums. It is best to limit an objective to 5-10 class C network ranges as it's too time consuming to scan large networks when there are […]Read More
The Agent Management Console (AMC) is a tool introduced within version 6.1 of the Snare Server that enables remote management of Snare Agents through the Snare Server interface. The AMC allows for multiple configuration sets (objectives) so it is easy to manage different sets of Snare Enterprise Agents through the same interface. There is no […]Read More
The current version of the Agent Management Console (AMC) can not perform agent updates, only configuration updates. Though we do provide the option to use an MSI packaged agent that you can use with your other software deployment tools ie Microsoft SCCM or GPO.Read More