Page History
...
| Warning |
|---|
IDERA, Inc. customers have the sole responsibility to ensure their compliance with the laws and standards affecting their business. IDERA, Inc. does not represent that its products or services ensures 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. |
5.6.1 New Features
General
Capture Logout Events
Sensitive Column Search
Currently SQL Compliance Manager captures Logins and Failed Logins, with SQL CM version 5.6 users have the ability to capture Logouts as a separate tracking option for their registered servers and for their configured Server Level Privileged Users.
Default Audit Configuration Settings
SQL Compliance Manager provides users with the capability to set up a single Server default setting and a single Database default setting. Allowing users to set up newly added Servers and Databases with their exact desired settings. Users also have the ability to apply those default settings to already registered Servers and Databases. By default, SQL CM provides users with the Idera Default Settings, which are a set of basic settings to help users start auditing from the moment a Server is registered. For more information about this feature, see Default Audit Settings
Add Databases Automatically
SQL Compliance Manager version 5.6 provides users with the ability to enable their Server Instances to automatically add any new database that is created on an audited server. For more information about this feature, see Registered SQL Server Properties - Advanced tab.
Configurations Clarifications
Compliance Manager version 5.6 improved the configurations setting to help users have a clear understanding of what is being audited at Server level and what is being audited at Database level. With the implementation of a new logic that shows items checked and unavailable for deselection at the Database level since those items are already selected at the Server level.
| Info |
|---|
Please note that it is possible that with the setting inheritance you may collect more data, to avoid doing so, please review your settings to ensure that all items all collected as you expect. |
Server Level Trusted Users
SQL Compliance Manager version 5.6 allows users to configure Trusted Users at Server level. Trusted Users designated at Server level will apply across all databases in the selected server, giving users a greater control over who is monitored at what level. For more information, see Trusted Users at Server level.
Sensitive Columns Auditing
SQL Compliance Manager version 5.6 updated the Sensitive Column functionality in order to alert users if PII data is selected or altered. To know if such data has been accessed, users can choose to collect information for Select Only, Selects and DML or for All Activity.
Web Console Updates
SQL Compliance Manager version 5.6 removed all the configuration settings from the Web Console, to help users have a greater control over who can change audit data while still allowing granted users to view the information being audited. Centralizing the setting configurations to the Desktop Console only, makes the Web Console a place where Auditors and Executives can easily use Reports and Alerts to see the information that they need to see.
...
SQL Compliance Manager version 5.6 includes a new Log file that keeps track of the product ́s versions and upgrades. The new Log file, found in the SQL CM installation folder, help users track the timelines for upgrade versions.
...
SQL Compliance Manager version 5.6 provides users with the ability to register a non-sysadmin role with permission to run the Compliance Manager Agent and permission to access the trace files.
...
.1 introduces the Sensitive Column Search functionality, allowing you to search all of the tables and columns on a targeted database to discover the sensitive data location that needs to be audited. For more information, see Sensitive Column Search window.
5.6.1
SQL Compliance Manager version 5.6 added the option to adjust the number of threads that can be used to process trace files at a time.
Regulatory Guidelines
GDPR Regulation
SQL Compliance Manager version 5.6 added the General Data Protection Regulation (GDPR) guideline to the selectable list of regulatory guidelines, providing users with the option to select GDPR guideline and comply with their auditing needs. For more information about this feature, see Comply with Specific Regulations.
Reports
Configuration Check Report
SQL Compliance Manager version 5.6 implemented the Configuration Check Report, which allows users to compare the settings configured on the registered servers and databases with the previously defined default settings. This report allows users to quickly identify where settings may vary from what is defined as the default settings as well as to identify the differences in the configurations across your registered servers and databases. For more information about this feature, see Available Reports.
Regulation Compliance Check Report
SQL Compliance Manager version 5.6 implemented the Regulation Compliance Check Report, which allows users to review the configurations set for all registered servers and databases and determine if settings comply with the selected Regulatory Guideline. This report compares the server and database configured settings to the predefined settings for any IDERA supported Regulation Guideline. For more information about this feature, see Available Reports.
...
Fixed Issues
Installation and Configuration issues
SQL Compliance Manager version 5.6 resolvedAnchor SQLCM-55265846 SQLCM-5526
Resolved the issue where the Compliance Manager Windows Console rebooted after installing or upgrading the SQL Server 2012 Native client version.5846 Anchor SQLCM-3040 SQLCM-3040 Resolved an issue where SQL Compliance Manager recorded Create/Drop index events as “Alter User Table” events.Anchor SQLCM-5421 SQLCM-5421 SQL Compliance Manager version 5.6 implemented updates in the Sensitive Column functionality which resolved the issue where Sensitive Column events were not displayed if accessed from a viewStored Procedure did not get disabled for the secondary node, which caused an accumulation of trace files on the secondary node.
Resolved an issue where SQL Compliance Manager was not capturing BAD auditing information when two objects with the same name exist in the same schema.Anchor SQLCM-51005539 SQLCM-51005539 Anchor SQLCM-5317 SQLCM-5317 SQL Compliance Manager version 5.6 resolved the issue where SQL Statements for DDL activities was not getting captured.Anchor SQLCM-3773 SQLCM-3773 SQL Compliance Manager version 5.6 resolved the issue which did not allow users to remove a database from the Administration pane.Anchor SQLCM-4963/4974 SQLCM-4963/4974 Resolved an issue where users were able to register active audited databases to archived SQL Serversissue which caused DML/SELECT filter settings to import incorrectly.
Resolved an issue where the Capture SQL statements for DDL activities and Security Changes option could not be selected unless the Database Definition (DDL) option was saved first.Anchor SQLCM-52395514 SQLCM-52395514 Anchor SQLCM-5104 SQLCM-5104 Resolved the issue where no events got captured for traces performed by non-privileged users.Anchor SQLCM-5281 SQLCM-5281 Resolved the issue where using encrypted credentials to deploy SQL Compliance Manager performing a silent installation returned an authentication error message .Anchor SQLCM-5229 SQLCM-5229 Resolved the issue where SQL Compliance Manager was not able to process alerts when a Group of users is set as a Privileged Userappeared in the SQL Server Logs about an invalid call to stored procedure master.dbo.sp_SQLcompliance_AuditXE .
For more information about new features and fixed issues in versions 5.5.x, see Previous new features and fixed issues.
...