V5.0.1

Enhancement

• To improve the error reporting when SnareMSSQL cannot access trace file directory, now an error message is shown below each objective when SnareMSSQL cannot access trace file directory or if it cannot create trace file in the configured location.
• Key IDs on the Agent /license pages is now styled to show alpha characters in black and numeric characters in a red tone. This is to make it easier for those that have problems seeing the different shades of grey.
• Licenses may now list a KeyID of 0 (zero).
• As there can be multiple instances of SnareMSSQL agents that may be running on a cluster machine so sometimes it is confusing in SAM network scan results when these multiple instances of SnareMSSQL agents are reported from the same machine. With SAM v1.0.1, additional meta information is added for SnareMSSQL agents. Now in SAM network scan results, when a SnareMSSQL agent is expanded it shows two new fields i.e. DB Cluster (only for SnareMSSQL cluster installations) and DB Instance.

Security Updates

• Maintenance update for OpenSSL to patch to OpenSSL-1.0.2j.

Bug Fixes

• In previous versions, SnareMSSQL service(s) can be started for all cluster SQL server instances of an MS SQL cluster node. This version fixes this issue and SnareMSSQL service is started only for SQL server instances that are currently active on a cluster node.
• There was an issue with SnareMSSQL installer, causing the SnareMSSQL service to be 'automatic' instead of 'manual' if SnareMSSQL is installed on cluster machines. This issue is fixed in this release and now SnareMSSQL service type is set to 'manual' during fresh installation. This release also fixes the issue in existing installation and updates the service type to 'manual' even when SnareMSSQL installer is run using 'Keep Settings' option.
• The Statistics page will no longer reset when the agent syncs with the SAM without any settings change. It will correctly display 24 hours worth of data in the graph.
• The AccessKeySet registry setting will no longer contain a valid hash if not set during the install.
• Fixed the handling of the conversion of logging levels in Group Policy when upgrading from v4 to v5.
• There was an issue that if a Snare agent and SAM are running on the same machine then Snare agent can be licensed even without configuring the SAM details in them. This issue is fixed in this release and now the SAM details should be included in the Snare agent to get it licensed from SAM.
• Host validation updated for Restrict IP when comma separated list of hosts is used
• Fix a bug where the SAM and Certificate Section of an inf file were not imported correctly by the installer
• There was an issue the way agent handles the missing registry keys due to a corrupt configuration or a user manually removing registry keys. Due to this issue, if an agent cannot open a registry key then it just ignores it; causing snare get an error. This issue is fixed in this release. Now if snare cannot open a registry key then it creates the key with default values so that registry values can be written in newly created key. Snare logs an error if it cannot create the registry key if there is a permission problem.