Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 23 Next »

V5.2.1

Bug Fixes

  • Fixed issue where the Syslog Priority field in the Destination Configuration was not taking effect when set to Dynamic.

V5.2.0

Security Updates

  • Update for OpenSSL to patch to OpenSSL-1.0.2p.
  • Removed non-secure ciphers usage, according to the OWASP broad compatibility list.

Bug Fixes

  • Fixed intermittent locking issue when stopping the MSSQL service from the Service Control Manager.
  • Fixed the memory management issue to prevent high memory usage on busy SQL server machines.
  • This change affects the warning messages that are display when protocol for destination is set to TCP or TLS for web UI port 6161 as it can slow down the agent receiving log messages, which will be ignored on the web interface. In high volume environments the agent may appear to hang as a result. As it is not a recommended configuration this will now show as a warning if the agent is configured in this way. In general sending logs to the localhost is only used for testing and only used when its UDP protocol so the logs are discarded. Any real destination should use a real hostname or IP address and not localhost. This change does not affect any other functionality.

V5.1.2

Bug Fixes

  • Removed CacheSizeSet setting from installer script.

  • Added missing registry values in installer script.

V5.1.1

Security Updates

  • Maintenance update for OpenSSL to patch to OpenSSL-1.0.2o.
  • Added support for TLS 1.1 and TLS 1.2 for SQL Server connections. It's worth to mention that at least Microsoft® ODBC Driver 11 for SQL Server® must have been installed to support TLS 1.1 and TLS 1.2 connection. The recommended is Microsoft® ODBC Driver 13.1 for SQL Server®.
  • Resolved issues with the agents using TLS syslog to connect to servers with TLS 1.1 and 1.2 not negotiating correctly.  The agent will now correctly negotiate up to TLS 1.2.

Bug Fixes

  • There was an issue with the 'Use Host IP' installer option. Due to this issue if this option was selected during installation then it is ignored. Consequently, all the events are associated with hostname instead of Host IP. This issue is fixed in this release and now this installer option works correctly. Please note that if this option is selected during installation then the first available static IP of the machine is selected as host IP. If there is not a static IP then any first available IP is used as that host IP for syslog messages.
  • Fixed an issue where UTC was being appended to local time when displaying events in the latest events page.
  • This change affects warning message for license support expiry. This change updated the warning that can appear in the top right corner of the agent web UI where the message "No further events will be logged to the specified destination."  will no longer be displayed if license support expires.
  • Updated the agent to use the time the event was generated on the Latest Events Web UI page. Previously it was reporting the sent date/time.
  • This change modifies the licensing status on the Agent page if a license is expired or support is expired when there are multiple licenses. The best license with active support is selected for setting in the agent Web UI.

V5.1.0

Enhancements

  • New command line switch /license is introduced for the agent setup configuration file (.INF). This switch can point to the license file to be used during installation. This license file selected through /license switch has the higher priority than the license options selected though installer UI.  For example /license="20180206-SnareAgent-Evaluation-AZP-CYT.sl"
  • Previously, when option 'Host IP As Source' was selected then first IP address of machine was used as source address with reported events. Now user is shown all the IP address of the machine through a drop-down list. User can select the specific IP address to be used to report the source IP of the events.
  • Any file destination now shows the real file name along with any date appended to file name for rotation, for example C:\file_events_YYYYMMDD.txt.
  • User Interface (UI) update that affects the IP Address allowed to remote control SNARE field on the Access Configuration page. This data entry field is disabled if Restrict remote control of SNARE agent to certain hosts  check box is not selected. Host IP Address or hostname details can only be entered if the checkbox has been selected.
  • Updated usability on the Destination Configuration page, with a Hostname Options section.
  • Trace level logging now displays the bytes and events sent per second (EPS) for each configured destination after 5 secs.  This will aid in correlating and debugging the EPS rates when sending logs.

Security Updates

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

Bug Fixes

  • In previous releases of SnareMSSQL when 'Use HostIP' option was selected, SnareMSSQL use to select the IP address of the physical machine on which it is running. This was same for cluster mode too. Though, in cluster mode it should select the IP address of the virtual server on which SQL Server is installed. This issue is fixed in this release and now when 'Use HostIP' option is selected, SnareMSSQL selects the IP address of the virtual server on which cluster instance of SQL server is installed.
  • There was a bug that can cause the installation of the SnareMSSQL on a clustered environment to fail when the SQL server instance name detected was MSSQLSERVER. This issue is fixed in this release and now SnareMSSQL installer properly handles the default SQL server instance name.
  • Issue with agent running on SQL server cluster machine and Use Host IP options is selected. Due to this issue SnareMSSQL fails to determine the correct IP address of SQL cluster in some cases. This issue is fixed and now SnareMSSQL properly computes the IP address of SQL server cluster systems. 
  • There was an issue in previous release of SnareMSSQL where installation for some local instances of SQL server can be omitted in a hybrid installation environment i.e. where cluster instances and standalone instances of SQL server are installed on the same machine. This issue is fixed and now SnareMSSQL installer properly handles the installation of local and cluster instances of SQL server on the same machine.
  • There was an issue in previous release the way SnareMSSQL used to determine the hostname of the generated SQL event. Due to this issue, the hostname of the SQL event may be determined as the machine hostname on which SnareMSSQL agent is running. This issue is fixed and now SnareMSSQL property determines the machine hostname as per user preferences.
  • Fix for failed installations occurred on busy machines. The installer now properly checks the status of service operations and retries appropriately when needed.
  • There was minor issue in existing release of SQL agent when installed on SQL server cluster installations. Due to this issue the web GUI ports were not sequentially allocated to the different instances of the Snare SQL agent on the same cluster node. In this release the agent correctly allocates the web ports sequentially. To use this sequential installation, the existing installation of the agent should be removed (uninstalled) or the agent installer should be rerun with the reinstall option.
  • There was an issue in the installer not working correctly in the previous release of SnareMSSQL agent if the local SQL Server instances were in a failed state in a cluster environment. This problem was specifically prevalent in mixed installation scenarios where local and cluster instances of SQL Server are installed on a same cluster node.
  • There was an issue the way SnareMSSQL was handling the username for Latest Events page. Due to this issue, username was shown on Latest Events page for some events. This issue is fixed in this release and now SnareMSSQL properly handles the username for Latest Events page. Also not that if a username is not reported by the SQL Server trace function then it will still not be shown and the username column will show '-'.
  • Previous release with the agent where it cannot detect the 32-bit instances of SQL server installed on 64-bit machine. Due to this issue SnareMSSQL was unable to create objectives for such 32-bit SQL server instances on 64-bit machine. This is fixed and now SnareMSSQL is able to detect 32-bit instances of SQL Server on 64-bit machines and also able to generate trace logs from such instances.
  • Fixed an issue with the CEF message format having missing/incorrect information as well as possible special characters causing the message to not display correctly in ArcSight.
  • The agent installer is capable of listing any license files it finds in the same directory as the agent executable.  This change updates the agent installer to include a "None" option, to not install any license file if present.
  • Fixed a bug where the Snare Agent would not import the SyslogPriority and SyslogFacility values from an .INF (agent setup configuration file). Consequently CacheSizeEventLog was not used due to this bug.
  • Objective matching in Snare support wildcards. In existing release of Snare in some situations this wildcard matching can cause stack overflow crash. This issue is fixed in this release and stack overflow possibility is removed during wildcard matching.

  • In previous release there was a bug in the user match using wildcard match. Due to this issue expected user names can be filtered in or out. This is fixed and now wildcard filter for user match works correctly. Now the wildcard pattern for user matching should be included within () i.e. (*sa*) and user filter on specific user should be included by mentioning it's name i.e sa. For example include user pattern {sysadmin:^sa},(!dummy*),*tom*,micky is that include all SQL server sysadmin users, do not include users starting with dummy,and include user name having tom in it and user micky.

  • Some agent settings are machine specific i.e. Clientname, HostIP and HostGUID. There was an issue in the export settings command -x that was causing these machine specific settings to be exported into the .inf file and then can subsequently be loaded with /loadinf option during install. This issue is fixed in this release and now machine specific values are not exported into .inf file and even if .inf file is manually edited; these values are ignored during loadinf option.

  • Fix issue with heartbeat license messages spamming the logs with a license heatbeat every 60 minutes (if heartbeats are disabled) or every heartbeat period. Also fixed an issue with SAM issued licenses being immediately marked as expiring in 30 days and thus warning the customer that it was about to expire.
  • Heartbeats events are added for the Information level to provide more information regarding the working of agent. These new heartbeats are sent when any setting is changed from GUI and when the agent service status is changed.
  • This change modifies Agent behavior to not log any heartbeat if there is no SAM configured to connect.  If there is a SAM configured, then to log a heartbeat if the connection is lost for every 2 hours.
  • There was an issue with the internal restart of the agent. Due to this issue agent might keep holding a token handle during internal restart. This issue is fixed in this release and now agent properly releases all the token handles.
  • Fixed an issue whereby the Snare Server (via AMC) could not retrieve the master configuration from a SnareMSSQL Agent using digest authentication.

Other

Version 5.1 is the final version to support operating system Windows XP for 32-bit and 64-bit.

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.


  • No labels