View Source

IDERA SQL Compliance Manager provides the following new features and fixed issues.

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

Includes updated and new regulation guidelines

IDERA SQL Compliance Manager 5.5 includes updates on PCI DSS and HIPAA regulation guidelines templates. It also includes new sets of regulation guidelines, allowing users to perform data audits according the corresponding security rules.

The new regulation guidelines are the following:

Defense Information Security Agency (DISA STIG)
North American Electric Reliability Corporation (NERC)
Center for Internet Security (CIS)
Sarbanes-Oxley Act (SOX)
Family Educational Rights and Privacy Act (FERPA)

For more information about this feature, see Comply with specific Regulations.

Auditing available via SQL Server Audit Logs

IDERA SQL Compliance Manager 5.5 includes the ability to track your alerts via SQL Server Audit Logs for Agents running on SQL Server 2017 or above. Users can now decide if they want to track events via Trace Files, Extended Events (SQL Server 2012 and above) or Audit Logs (SQL Server 2017 or above). This new feature is supported in both the Web console and the Windows Management Console.

For more information about this feature, see Using SQL Server Audit Logs.

Includes a Row Count feature

IDERA SQL Compliance Manager 5.5 includes the row count feature which captures and reports on the frequency that users access Event types and SQL Statements, alerting database administrators about suspicious behavior.

As part of the row count functionality in SQL Compliance Manager 5.5 and above, we are now capturing Statement Completed instead of Statement Start. In some cases, if a SQL statement is run but not executed (e.g. SET SHOWPLAN_XML), SQL Compliance Manager may pick up those events.

For more information about this feature, see Control data access - Row count.

Enable SQL Extended Events Auditing from the Windows Management Console

SQL Extended Events auditing can now be enabled from both the Web Console and the Windows Management Console.

For more information about this feature, see Using SQL Server Extended Events.

Supports SQL Server 2017

IDERA SQL Compliance Manager 5.5 now supports installation of the Database Repository for Collection Server, deployment of the SQL Compliance Manager Agent, and auditing events for SQL Server 2017.

For more information, see Software requirements.

Supports Windows Server 2016

The user can install IDERA SQL Compliance Manager 5.5 and deploy the SQL Compliance Manager Agent in Windows Server 2016.

For more information, see Software requirements.

Allows users to create Sensitive Column data sets

IDERA SQL Compliance Manager 5.5 allows users to create Sensitive Column data sets that can be monitored as a group of sensitive information. Users can also add Sensitive Column data sets to any regulation guideline applied in servers or databases.

For more information, see Sensitive Column window.

BAD Alerts

IDERA SQL Compliance Manager 5.5 allows users to add Host Name, Login, and Before-After data values to the alert message templates.

Agent Deployment method

IDERA SQL Compliance Manager 5.5 allows users to see the agent deployment method in the Registered SQL Servers window of the Administration view.

Allows users to install or upgrade on a non default drive

IDERA SQL Compliance Manager 5.5 allows users to install and/or upgrade in a non default drive path.

5.5 Fixed issues

Administration issues

Audit thresholds appear enabled in the ReportCard even after removing and/or archiving an instance.
SQL Compliance Manager 5.5 no longer fails to reach the Collection service on the active node after a successful failover in a clustered environment.
Resolved the issue preventing SQL Scripts files with Supplementary Characters to work on the Collation SQL Server.
Resolved the issue causing unexpected behavior during the manual upgrade of the SQL Compliance Manager Agent on a remote machine.
Resolved an issue causing overwritten permissions on the Agent Trace folder after deploying the SQL Compliance Manager Agent.

Auditing issues

SQL Compliance Manager Agent no longer recreates stored procedures every second.
Resolved an issue in which SQL Compliance Manager was not showing Before-After data when enabling capture DML events using Extended Events.
Resolved an issue causing DDL Events to display twice for the same event.
Resolved an issue in which SQL Compliance Manager was not saving changes made in privileged users when applying regulation guidelines.
Resolved the issue preventing the user to capture SQL Statements for DDL and Security changes.
Resolved the issue preventing the capture of Before-After Data when using Extended Events auditing to capture DML events.

Reporting issues

Email notifications for Event Alerts now display the date and time in the Collection Server time zone.
SQL Compliance Manager alerts users about the limit of SQL Statements when exporting reports.
Resolved an issue preventing users to view and report on audit data or see events.

SQL Compliance Manager audits all activity on your server. Learn more > >