...
| Warning |
|---|
IDERA, Inc. customers are solely responsible for ensuring compliance with the laws and standards affecting their business. IDERA, Inc. does not represent that its products or services 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
...
Quality Enhancements
...
...
The new feature “Auditing the IP address of the source of an event” allows SQL Compliance Manager to capture and record the IP address of the source of an event along with other relevant information. This feature provides an additional layer of security and compliance, giving organizations more visibility into who is accessing their data and from where. It is configurable in the Audited Activities tab.
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.1 improved to detect all the manual changes made to the [Events] and [EventSQL] tables by an Integrity Check.
...
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.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.
...
.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
-
| Anchor |
|---|
| SQLCM-64356748 |
|---|
| SQLCM-64356748 |
|---|
|
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 methodWhen 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 RecordsAudit events for "insert" are accurately being recorded for Sensitive columns with "select and DML activity" enabled.
- 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 reportsResolved 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.
-
| Anchor |
|---|
| SQLCM-64386403 |
|---|
| SQLCM-64386403 |
|---|
|
Resolved the Fixed an issue where running the SQL Server Reporting Services listed all users in a long string in the report output when all users are selectedthe number of Logout events captured was significantly more than the number of Login events.
-
| Anchor |
|---|
| SQLCM-63686539 |
|---|
| SQLCM-63686539 |
|---|
|
Fixed an Resolved the issue where an error occurred during the setup of the Collection Service account with a password longer than 32 characters during the installationa warning message was displayed in the Event Viewer after execution of the trace file out to the collection Server for processing.
| Anchor |
|---|
| SQLCM-65066773 |
|---|
| SQLCM-65066773 |
|---|
|
Resolved the Fixed an issue where auditing via extended events and making changes to the temp-tables caused to "Audit all user tables" when "DML\SELECT Filters" was configuredthe "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.
- 63776377Resolved an the issue where the DataChanges table showed a number of eventId ` s with a value of NULLevents table integrity check did not detect changes done on hash columns.
- 64826482Fixed 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 namesThe “SQL Statement” content is correctly displayed in the “Event Properties” after executing the DDL query if the “via SQL server Audit specification” is used.
-
| Anchor |
|---|
| SQLCM-65266749 |
|---|
| SQLCM-65266749 |
|---|
|
Resolved the issue where SSMS native activities were picked up when using Extended Events as the collection methodthe "+" icon was missing for the DDL column-sensitive event in the "Audit Events" tab.
| Anchor |
|---|
| SQLCM-64406721 |
|---|
| SQLCM-64406721 |
|---|
|
Resolved the issue where an error appeared when opening Excel export of "Regulatory Compliance Check" report in SSRSAddressed an issue where the layout was broken for reports downloaded in PDF and TIF formats.
-
| Anchor |
|---|
| SQLCM-64416697 |
|---|
| SQLCM-64416697 |
|---|
|
Fixed the Resolved an issue where the Audit Events View didn't keep custom columns after the console was restartedEvents were not captured as expected with Extended Events and SELECT auditing was enabled. -
| Anchor |
|---|
| SQLCM-64586671 |
|---|
| SQLCM-64586671 |
|---|
|
Fixed an the issue where making changes to the [EventSQL] table was not picked up by the Integrity Checkthe Bin file was not getting updated for the Privileged User set up through a domain group at the server level. -
| Anchor |
|---|
| SQLCM-65916629 |
|---|
| SQLCM-65916629 |
|---|
|
Resolved an issue where the Login Filter was recording the same login multiple times.| Anchor |
|---|
SQLCM-6359 | SQLCM-6359 | Excel report export no longer rounds up event timestamps"Unknown Publisher" was displayed in the "User Account Control" when installing SQLCM.
- 62676267Resolved Addressed an issue where Trusted User registration was case-sensitive for an auto-registered new database while it was case-insensitive for manually registered databasesan error message would come up when trying to import audit settings.
For more information about new features and fixed issues in version 6.01, see Previous new features and fixed issues.
...