IDERA SQL Compliance Manager build includes many fixed issues, including the following updates.
Expand |
---|
|
- SQL Compliance Manager 6.2 improved to determine if an Alert Rule has been configured as 'Email Notification' or 'Email Summary Notification', users no longer are required to edit the alert rule. The rule description has been enhanced to make it convenient to distinguish between the two without the need for alert rule modifications.
- SQL Compliance Manager 6.2 upgraded to provide a CLI command line for registering a server, grooming, archiving, and verifying audit data integrity - version 6.2 is now augmented with CLI for enabling and disabling auditing servers.
- SQL Compliance Manager 6.2 improved and added the number of rows at the end of the reports to ease access to the information contained in each report.
- SQL Compliance Manager 6.2 enhanced security by deploying a strong Advanced Encryption Standard (AES) algorithm to meet the latest high standards of our large enterprise customers. The Advanced Encryption Standard (AES) is an algorithm that uses the same key to encrypt and decrypt protected data. Instead of a single round of encryption, data is put through several rounds of substitution, transposition, and mixing to make it harder to compromise.
|
Expand |
---|
|
- DDL, DML, and DROP events are correctly shown in the "Audit Events" tab after performing the DDL action on the "Sensitive Column" when using the "via Audit Logs" collection method.
- Audit events for "insert" are accurately being recorded for Sensitive columns with "select and DML activity" enabled.
- Resolved the issue where Trace events were not being correctly captured for "delete from <table>" audit events when sensitive columns with "select and DML activity" were configured.
- Fixed an issue where the number of Logout events captured was significantly more than the number of Login events.
- Resolved the issue where a warning message was displayed in the Event Viewer after execution of the trace file out to the collection Server for processing.
- Fixed an issue where the "Delete" DML events were shown twice after executing a single "Delete" query on the "Sensitive Columns" table when "Trace" or "Audit Logs" collection methods were used.
- Resolved the issue where the events table integrity check did not detect changes done on hash columns.
- The “SQL Statement” content is correctly displayed in the “Event Properties” after executing the DDL query if the “via SQL server Audit specification” is used.
- Resolved the issue where the "+" icon was missing for the DDL column-sensitive event in the "Audit Events" tab.
- Addressed an issue where the layout was broken for reports downloaded in PDF and TIF formats.
- Resolved an issue where Events were not captured as expected with Extended Events and SELECT auditing was enabled.
- Fixed the issue where the Bin file was not getting updated for the Privileged User set up through a domain group at the server level.
- Resolved an issue where "Unknown Publisher" was displayed in the "User Account Control" when installing SQLCM.
- Addressed an issue where an error message would come up when trying to import audit settings.
|
Expand |
---|
|
- SQL Compliance Manager 6.1 adds a new feature “Auditing the IP address of the source of an event” which allows SQL Compliance Manager to capture and record the IP address of the source of an event along with other relevant information. It is configurable in the Audited Activities tab.
- SQL Compliance Manager 6.1 improved to detect all the manual changes made to the [Events] and [EventSQL] tables by an Integrity Check.
- SQL Compliance Manager 6.1 adds support for Windows 11 and Windows Server 2022 for installation and features. For more information on the operating system support, visit the Software Requirements page.
|
Expand |
---|
|
- When running reports in both the Windows Console and Reportings Services you can now select multiple instances in the <Server Instance> dropdown.
- Report Results rows now can be configured to use more than 10K Event Records.
- Added a Horizontal Line in the Reports allowing users to adjust the space that the filters or the report use at any given time. Also added a horizontal scrollbar allowing the user to navigate through the reports.
- Resolved the issue where running the SQL Server Reporting Services listed all users in a long string in the report output when all users are selected.
- Fixed an issue where an error occurred during the setup of the Collection Service account with a password longer than 32 characters during the installation.
- Resolved the issue where auditing via extended events and making changes to the temp-tables caused to "Audit all user tables" when "DML\SELECT Filters" was configured.
- Resolved an issue where the DataChanges table showed a number of eventId ` s with a value of NULL.
- Fixed an issue where the error prompted "An item with the same key has already been added" prompted while loading configuration for the SERVER and occurred when having two databases with the same id but different names.
- Resolved the issue where SSMS native activities were picked up when using Extended Events as the collection method.
- Resolved the issue where an error appeared when opening Excel export of "Regulatory Compliance Check" report in SSRS.
- Fixed the issue where the Audit Events View didn't keep custom columns after the console was restarted.
- Fixed an issue where making changes to the [EventSQL] table was not picked up by the Integrity Check.
- Resolved an issue where the Login Filter was recording the same login multiple times.
- Excel report export no longer rounds up event timestamps.
- Resolved an issue where Trusted User registration was case-sensitive for an auto-registered new database while it was case-insensitive for manually registered databases.
-
|
Expand |
---|
|
- SQL Compliance Manager 6.0 extends the capabilities of the current SQL CM Agent to support remote auditing on SQL servers on EC2. Allowing users to add SQL Servers active on the share network location to write/read data and support DBaaS SQL Server Instances. The Cloud Agent consists of the same behavior and functionality as the current SQL Agent, but the RDS agent is a separate agent deployed into the cloud with its own configuration auditing settings.
- SQL Compliance Manager 6.0 adds support for Amazon RDS to audit servers, databases, Sensitive Data, and Activities while alerting and reporting on them. Users can select Amazon RDS as their Server Type when adding a new server in the Specify SQL Server configuration window. According to the selection, SQL CM asks to Specify Connection Credentials for the authentication, and once registered, users can begin auditing the database activity on that server.
- SQL Compliance Manager 6.0 permits the creation of storage accounts to place its components within AWS. In Amazon RDS, users can audit Microsoft SQL Server databases using the built-in SQL Server auditing mechanism. For additional information on Support for SQL Server Audit, visit the SQL Server Audit User Guide.
- Upon upgrading to SQL CM 6.0 or preparing a new installation, SQL Compliance Manager Event Collection Method Capture Default Setting changes to "SQL Server Audit Specifications". All audit logs for 'DML and Select Activities' are captured and filtered properly both for the existing CM architecture and the cloud support platform.
|
...