...
| Info | ||
|---|---|---|
| ||
This user guide describes how to use the Agent Management Console also referred to AMC within the Snare Central Server product. This guide targets the console that was launched in v7.0.x of the Snare Central Server. If you are using an earlier, or later, version of the server, please refer to the User Guide for that version instead as there may be significant changes between versions. It is designed to be a starting point for users who already have a working Snare Central Server v7.0.x installation, and are familiar with the basic navigation concepts. For help installing the server, please refer to the Snare Central Server v7.0 Installation Guide. Likewise, if you are running an older version (v6, v5 or v4), then please update your Snare Central Server version first. This guide also assumes that you have at least one working Snare Agent within your environment. Please refer to the associated Agent user guides if you need any help installing your Agents. Please also refer to the Compatibility Chart to ensure that the Agents you are using are compatible with the console. |
| Note |
|---|
Starting from Snare Central v8.6.0 AMC is superseded by Snare Agent Manager (SAM) that introduces a new configuration management capability for Snare Agents v5.8.0 and newer. It is recommended to manage Snare Agents v5.8.0 or newer in Snare Agent Manager (SAM), as AMC will be deprecated in the future. For Migration instructions, please refer to SAM User Guide > Appendix A - AMC to SAM Migration Guide for Remote Agents Configuration Management |
What is the Agent Management Console (AMC)?
...
- The Agent Management Console currently only manages Agent Configurations for compatible Enterprise Agents.
- It does not provide the ability to install and/or upgrade the Agent software. Upgrades of the agents can be performed by the Snare Agent Manager (SAM) from version 1.2 onwardsonward.
- It will only work on Agents that have the Remote Management function enabled, without this, the Console cannot communicate with the Agent.
- All communication is initiated by the Server, so firewall rules must be in place to allow the Server to connect to each Agent.
- The Console cannot monitor/wait for an Agent to come online - if it is not online when the check/sync is triggered, it will be considered uncontactable.
...
Agent | Version(s) | Config Pull | Config Push |
Enterprise - Snare Agent for Windows | v4.1.x, v5.x | 
|
|
Enterprise - Snare Agent for Windows | v4.0.2.x |
| 
|
Enterprise - Snare Agent for Windows | v4.0.0.0, v4.0.1.x |
|
|
| Enterprise - Snare Epilog | v5.x.x |
|
|
Enterprise - Snare for MSSQL | v5.x.x |
|
|
Enterprise - Snare Agent for Linux | v5.x.x |
|
|
Enterprise - Snare Agent for Solaris | v5.x.x |
|
|
| Enterprise - Mac OSX Agent | v5.x.x |
|  |
Enterprise - Snare Agent for Linux | v1, v2.1, v3, v4 |
|
|
Enterprise - Snare Agent for Solaris | v3.x, v4.x |
|
|
| Enterprise - Mac OSX Agent | v1.x |
|
|
Open Source - Snare Agent/Epilog | any |
|
|
Notes:
- Compatibility table refers to Snare Central Server v7.x.x only.
- "Config Pull" means Agent Configuration can be retrieved from the Agent by the Server.
- "Config Push" means Agent Configuration can be updated by the Server on the Agent.
...