As a Snare Enterprise agent user I desire the ability to read and transmit via syslog Event Trace Log (ETL) files. One example in which this feature would be valuable is the reading and transmission of Microsoft DNS Server Analytic Logs.

We are currently moving our office environment to the local server based environment to and Office 365 environment. We would like to be able to collect Office 365 into our SIEM and make auditing easier. Office 365 seems to be the software for many moving forward, especially in the current circumstances of COVID-19 and working remotely.

I would like to see a "counter" for the Flat File monitoring by the SAM agent. I understand that the Snare agent is able to resend the logs by resetting the counter inside the target computer's registry. Can we have this for the Flat File Monitoring as well?

Besides plan TLS and TLS Auth, allow TLS Mutual Authentication (where both the agent and destination have certificates and must verify each other).

The customer must currently select the Certificate to be used.

most common TLS clients (web browsers) don't check CRLs (cert revocation lists) or do soft failure. It would be nice to do the same in SNARE, so that CRL fetch outage doesnt cause logging outage

SNMP enabled for query on the Snare Server to monitor health of our Snare server.

Snare logs when installed on Linux do not send syslog + FIM events in a format that a SIEM like QRadar, Arcsight, AlienVault, Splunk natively understand. This is because the Snare agent re-writes the log. We want to be able to send those logs in their native format or a custom format we choose.This way, we can send Linux logs in their native format and send FIM logs that look different so the SIEM can handle them differently. This is currently why we don't use or recommend Snare for Linux FIM monitoring.

The Snare Agent Manager has only a single login available for use. This causes a problem in providing the login to users that you don’t wish to have administrative access to the SAM.

Need to show how much data is being reflected in executive reports. The current Snare Central Reflector page only shows a rolling 24 hour volume.

Allow the user to add multiple networks to the SAM at once, either by importing a list of networks or pasting in a list of networks.

Right now if you want to clear out old agents (usually Legacy agents) you have to delete them individually. When you have over 1000 of them it is unworkable. Provide option to "select all" or select all from a filter and do bulk delete on them.

The customer would like to have the same method that we use to restrict access to the WebUI for the Agents added to the SAM.

Have the WebUI's timeout changed or have an option to adjust the timeout time

Allow the Snare Central Server to enable FIPS compliance mode. This will restrict all encryption methods to only use they approved encryption algorithms.

Pattern Map Details in reports do not allow selection of columns. Certain fields such as DETAILS and STRING are large and take up a large amount of screen estate.

Although the Tabular details allows inclusion or exclusion of fields the Pattern Map’s details does not allow that customization and shows fields that are not desired.

Snare Central does not currently have an option to save logs in an uncompressed format.

We currently provide Snare Central Server as an ISO file. We don’t have a deployable version of Snare Central Server to be deployed in Amazon Web Services (AWS). Not have a deployable Snare Central Server in Amazon Web can affect future business for Threat Intelligence upsells for customers who are wanting a full deployment of Snare Central Servers in the cloud.

We only provide an ISO file for Snare Server. We don’t have an OVA for AWS. Having a standard deployable OVA Snare Central Server in AWS will be necessary for ALL customers running Snare Central Server in the cloud.