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.1 New features

There are no new features in this release.

Expand
title5.7.1 Fixed issues

General issues

  • Anchor
    SQLCM-5989
    SQLCM-5989
    Resolved the issue where SQL Compliance Manager did not recognize a GMSA account as a Trusted users when adding the account as part of a group.
  • Anchor
    SQLCM-6058
    SQLCM-6058
    Resolved the issue which caused the cluster setup installation to perform a fresh installation instead of asking users to upgrade the agent service .
  • Anchor
    SQLCM-6128
    SQLCM-6128
    Resolved the issue where SQL Compliance Manager could not establish a connection with the AG databases on the Secondary nodes where no read access is allowed. SQL Compliance Manager successfully populates the list of AG databases to be configured for auditing on the Secondary nodes.
  • Anchor
    SQLCM-6027
    SQLCM-6027
    Resolved the issue where configuring Sensitive Column auditing caused the SQLcompliance Agent to have problems creating the sp_SQLcompliance_Audit  stored procedure.
  • Anchor
    SQLCM-6057
    SQLCM-6057
    Resolved the issue with the Daily Audit Activity Statistics Report which displayed an error message due to a missing component. The Daily Audit Activity Statistics Report runs successfully.
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. 

...