...
Warning |
---|
IDERA, Inc. customers have the sole responsibility to ensure their are solely responsible for ensuring compliance with the laws and standards affecting their business. IDERA, Inc. does not represent that its products or services ensures ensure that customer is in compliance with any law. It is the responsibility of the customer to obtain legal, accounting, or audit counsel as to the necessary business practices and actions to comply with such laws. |
...
6.
...
2 New Features
...
Supports SQL Server 2019
IDERA SQL Compliance Manager 5.7 now supports installation of the Database Repository for Collection Server, deployment of the SQL Compliance Manager Agent, and auditing events for SQL Server 2019. For more information, see Software requirements.
Supports Windows Server 2019
The user can install IDERA SQL Compliance Manager 5.7 and deploy the SQL Compliance Manager Agent in Windows Server 2019. For more information, see Software requirements.
Reports
New Reports
SQL Compliance Manager version 5.7 includes the Server Activity Report which allows users to view the SQL Server activity at the enterprise and at the individual instance levels. With this report, users can quickly check activity in each event category audited, and view statistics of the SQL Server activity. For more information, see Server Activity Report Card.
SQL Compliance Manager version 5.7 includes the Privileged/Trusted Users Report for users to list the trusted and privileged user roles set per a specific Server or Database. Users can run this report on Privileged and Trusted users to know what these were set to during a snapshot in time. For more information, see Privileged and Trusted Users Report.
SQL Compliance Manager version 5.7 includes the Sensitive Column/BAD Users Report which lists Sensitive Columns and Before-After data audit settings applied to the servers and databases in your environment. Users can run this report on Sensitive Columns and BAD auditing to know what these were set to during a snapshot in time. For more information, see Sensitive Columns and BAD Report.
Limit Report Access to specific users
SQL Compliance Manager version 5.7 introduces the ability to restrict user access to certain SQL CM reports. As an administrator you can grant users permissions to specific reports. This way you can tightly control permissions settings for report access for every user in your environment. For more information, see Login properties - Report Access.
Report Filter improvements
SQL Compliance Manager version 5.7 brings updates and improvements to reports by making reports more consistent and adding new filters options, such as the ability to filter reports based on a specific schema, event type, login, or multiple logins at a time. Users can also use the time range filters to report on the exact high activity time-frames or to filter out low activity time-frames.
5.7 Fixed Issues
Quality Enhancements
Enhanced User Experience with Email and Summary NotificationsSQL 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.
Command Line Interface (CLI) EnhancementSQL 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.
ReportsSQL 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.
Security Enhancements
EncryptionSQL 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.
6.2 Fixed Issues
- 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.
Anchor |
---|
SQLCM-5505 | SQLCM-5505 | The Object Activity Report no longer renders all data on a single page, and when run, the report displays the collected data correctly.
For more information about new features and fixed issues in versions 5.version 6.x1, see see Previous new features and fixed issues.
...