Versions Compared

Old Version 3

changes.mady.by.user Mirza Muzammil Baig

Saved on

compared with

New Version 4

changes.mady.by.user Mirza Muzammil Baig

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Info

This capability is available starting from Snare Enterprise Agents v5.8.0 and Snare Agent Manager (SAM) v2.0.0.

...

This functionality replaces previous pushing configuration method to Snare Agents via Snare Central component Agent Management Console (AMC). 

Info

Recommendation

Customers who use AMC to push configuration to the Agents, are encouraged to migrate to this new mechanism where Agent policies are defined in SAM, and Agents pull policy updates from SAM. 
This new mechanism is more secure and provides ability to manage Agents configuration without having web access enabled on every managed endpoint.
Please see <Migration Instructions (TO DO)> for details.

...

Snare Agent that has its policy managed by SAM will indicate this on the 'Agent Status pagePage', under Managed Configuration Status. All the settings that are managed by the Snare Agent Manager are read-only, marked Remote as shown following:

...

These remote configs are called Master Configuration that agent pulls from Snare Agent Manager (SAM). See the SAM documentation on how to create the master configuration.

Some agent configuration are strictly local and cannot be assigned from master configuration. These settings include Override Hostname, Select the specific Network Adapter, Client Name and upgrade path. These settings are always shown as LR.

...

Exporting Agent Configuration as JSON

...