Page tree

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

This build of IDERA SQL Compliance Manager includes many fixed issues, including the following updates.


Expand
title5.7.0 New features

General

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.

Expand
title5.7.0 Fixed issues

General issues

  • 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. 
Expand
title5.6.1 New features

General

Sensitive Column Search

SQL Compliance Manager version 5.6.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 

Expand
title5.6.1 Fixed issues

Installation and Configuration issues

  • Anchor
    SQLCM-5846
    SQLCM-5846
    Resolved the issue where the Stored Procedure did not get disabled for the secondary node, which caused an accumulation of trace files on the secondary node.
  • Anchor
    SQLCM-5539
    SQLCM-5539
    Resolved the issue which caused DML/SELECT filter settings to import incorrectly.
  • Anchor
    SQLCM-5514
    SQLCM-5514
    Resolved the issue where an error message appeared in the SQL Server Logs about an invalid call to stored procedure master.dbo.sp_SQLcompliance_AuditXE .
Expand
title5.6.0 New features

General

Capture Logout Events

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.  

Anchor
SQLCM-5503
SQLCM-5503
Log File

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.

Anchor
SQLCM-566
SQLCM-566
Non-sysadmin

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.  

Anchor
SQLCM-566
SQLCM-566
Increase the number of threads processed

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.

Expand
title5.6.0 Fixed issues

Installation and Configuration issues

  • Anchor
    SQLCM-5526
    SQLCM-5526
    SQL Compliance Manager version 5.6 resolved the issue where the Compliance Manager Windows Console rebooted after installing or upgrading the SQL Server 2012 Native client version. 
  • 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 view.
  • Anchor
    SQLCM-5100
    SQLCM-5100
    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-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 Servers.
  • Anchor
    SQLCM-5239
    SQLCM-5239
    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-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 User.

...

Expand
title5.3.0 Fixed issues

General

  • Anchor
    DE19332, SQLCM-2522
    DE19332, SQLCM-2522
    Resolved an issue that did not properly update group permissions after modification and honored group settings over the individual user account in some situations.
  • Anchor
    DE43232, SQLCM-2352
    DE43232, SQLCM-2352
    Improved Permissions Check functionality to prevent false or inconsistent results.

Installation

  • Anchor
    US16650, SQLCM-540
    US16650, SQLCM-540
    Renamed the SQL Compliance Processing database from SQLCompliance.Processing to SQLComplianceProcessing.
  • Anchor
    DE43945, SQLCM-2333
    DE43945, SQLCM-2333
    Corrected an issue preventing the ... button from properly working in the Add SQL Compliance Manager Agent Service window on Windows 2012/2012 R2 installations.

Licensing

  • Anchor
    DE46199, SQLCM-2165
    DE46199, SQLCM-2165
    Resolved an issue causing users with AlwaysOn Availability Groups to receive a message that the maximum number of servers is reached while they actually had less than that limit.

Services

  • Anchor
    DE44606, DE44676, DE41432, SQLCM-2313, SQLCM-2448, SQLCM-2345, SQLCM-2322
    DE44606, DE44676, DE41432, SQLCM-2313, SQLCM-2448, SQLCM-2345, SQLCM-2322
    Improved the Collection Service performance to be able to process a substantially large number of trace files.

Auditing

  • Anchor
    DE43812, SQLCM-2344
    DE43812, SQLCM-2344
    SQL Compliance Manager now can log events that are accessed through a view.
  • Anchor
    DE44527, SQLCM-2316
    DE44527, SQLCM-2316
    Sensitive column traces no longer include events from databases not configured for sensitive column auditing.
  • Anchor
    DE44679, SQLCM-2312
    DE44679, SQLCM-2312
    Resolved an issue that prevented SQL Compliance Manager from discovering and auditing new users added to the list of Trusted Users / Privileged Users within a domain group without manually updating the audit settings.
  • Anchor
    DE46329, SQLCM-2162
    DE46329, SQLCM-2162
    Exported audit settings now include database level privileged users.

...

Scroll PDF Exporter Ignore
Newtabfooter
aliasIDERA
urlhttp://www.idera.com
 | 
Newtabfooter
aliasProducts
urlhttps://www.idera.com/productssolutions/sqlserver
 
Newtabfooter
aliasPurchase
urlhttps://www.idera.com/buynow/onlinestore
 | 
Newtabfooter
aliasSupport
urlhttps://idera.secure.force.com/
 | 
Newtabfooter
aliasCommunity
urlhttp://community.idera.com
 
|
 
Newtabfooter
aliasResources
urlhttp://www.idera.com/resourcecentral
 | 
Newtabfooter
aliasAbout Us
urlhttp://www.idera.com/about/aboutus
 
Newtabfooter
aliasLegal
urlhttps://www.idera.com/legal/termsofuse

Scroll Pagebreak