V5.0.2

Enhancement

• Changes were made to validation of 'Access Configuration', SAM IP field. Previously hostname validation was limited to accept numeric values. Changed to accept fully qualified domain names. As a result, fields depending on ip/hostname validation will accept wider range of inputs that include FQDNs in addition to IPs.
• Alters references for Evaluation Licenses to Temporary Licenses.
• Added text on the License page in the UI to aid users using SAM or standalone licensing.

Security Updates

• This modifies the SHA version for certificate in Windows and Unix agents. Enable higher level of security by using SHA2 support for newer version of Windows and Linux agents.
• Snare Agent web UI functionality has been modified to avoid cross-site scripting attack.

Bug Fixes

• Notification and warning on Snare agents has been changed to to allow syslog_5424 format on port 514. As a result of this change, notification and warning will no longer appear for valid syslog format's when using port 514.
• Fix a potential for memory corruption of event data being sent via TCP, TLS or UDP when under very heavy loads.
• There was an issue in previous release of the snare agent where it was not properly handling the objectives during upgrade to latest release. Due to this issue, objectives may not be available after upgrade. This issue is fixed in this release and now snare properly handles the objectives during upgrade and all objectives are available after upgrade.
• Snare agent warning and notification messages has been changed to issue warning for selecting non-TAB delimiter for SNARE format(Snare Server destination). As a result of this change, new warning's will be issued when non-TAB delimited for SNARE format (for Snare Server destination) is selected.
• There was a debug logging issue in previous release of SnareMSSQL agent. Due to this issue, SnareMSSQL was not able to properly show the log messages on console if run from console. The fix ensures SnareMSSQL logs all the messages to console window as per input parameter -d when run from console. (e.g. snaremssql -c -d SAM:trace > mysnare.log 2>&1 )
• There was an issue with the uninstaller of the SnareMSSQL agent. Due to this issue uninstaller was not properly cleaning the registry of the SnareMSSQL agent. This issue is fixed in this release and now uninstaller properly cleans the registry during uninstall.
• There was in issue the way SnareMSSQL was saving/updating the objective. Due to this issue, an objective would not save correctly when 'Including SELECT' check box was checked on objective page. This issue is fixed in this release and now SnareMSSQL properly save the value of 'Including SELECT' checkbox.
• There was an installing issue in previous release of SnareMSSQL where installation was made using .inf file on machines that are part of Windows Cluster or machines running with Windows Server 2016. Due to these installation issues, SnareMSSQL installation might fail or objectives might fail to load from .inf file. These issues are fixed in this release. Now SnareMSSQL handles cluster installation as well as properly supports Windows Server 2016.
• There was an issue in previous release of SnareMSSQL where setting 'Use plain text objective data' under General Configuration was not working. Due to this issue objectives were not stored in plain text even when this option is checked. This issue is fixed in this release and now SnareMSSQL properly honors the setting 'Use plain text objective data' .
• Updated the validation of event types in objectives. An objective cannot be saved if at least one event type is not selected. This is to ensure that only a valid objective is saved.

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 the trace file directory or if it cannot create the 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.