Versions Compared

Old Version 37

changes.mady.by.user Nicolas Rios

Saved on

compared with

New Version Current

changes.mady.by.user Rodrigo Rivero

Saved on

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.build includes many fixed issues, including the following updates.

Expand
title6.1 New features
  • Anchor
    SQLCM-6350
    SQLCM-6350
         SQL Compliance Manager 6.1 adds a new feature “Auditing the IP address of the source of an event” which allows SQL Compliance Manager to capture and record the IP address of the source of an event along with other relevant information. It is configurable in the Audited Activities tab.
  • Anchor
    SQLCM-6458
    SQLCM-6458
    SQL Compliance Manager 6.1 improved to detect all the manual changes made to the [Events] and [EventSQL] tables by an Integrity Check.
  • Anchor
    SQLCM-6608
    SQLCM-6608
    SQL 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.
Expand
title6.1 Fixed issues
  • Anchor
    SQLCM-6435
    SQLCM-6435
         When running reports in both the Windows Console and Reportings Services you can now select multiple instances in the <Server Instance> dropdown.
  • Anchor
    SQLCM-6495
    SQLCM-6495
         Report Results rows now can be configured to use more than 10K Event Records.
  • Anchor
    SQLCM-6486
    SQLCM-6486
         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 reports.
  • Anchor
    SQLCM-6438
    SQLCM-6438
         Resolved the issue where running the SQL Server Reporting Services listed all users in a long string in the report output when all users are selected.
  • Anchor
    SQLCM-6368
    SQLCM-6368
         Fixed an issue where an error occurred during the setup of the Collection Service account with a password longer than 32 characters during the installation.
  • Anchor
    SQLCM-6506
    SQLCM-6506
         Resolved the issue where auditing via extended events and making changes to the temp-tables caused to "Audit all user tables" when "DML\SELECT Filters" was configured.
  • Anchor
    SQLCM-6377
    SQLCM-6377
         Resolved an issue where the DataChanges table showed a number of eventId     ` s with a value of NULL.
  • Anchor
    SQLCM-6482
    SQLCM-6482
         Fixed 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 names.
  • Anchor
    SQLCM-6526
    SQLCM-6526
         Resolved the issue where SSMS native activities were picked up when using Extended Events as the collection method.
  • Anchor
    SQLCM-6440
    SQLCM-6440
         Resolved the issue where an error appeared when opening Excel export of "Regulatory Compliance Check" report in SSRS.
  • Anchor
    SQLCM-6441
    SQLCM-6441
         Fixed the issue where the Audit Events View didn't keep custom columns after the console was restarted.
  • Anchor
    SQLCM-6458
    SQLCM-6458
         Fixed an issue where making changes to the [EventSQL] table was not picked up by the Integrity Check.
  • Anchor
    SQLCM-6591
    SQLCM-6591
         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.
  • Anchor
    SQLCM-6267
    SQLCM-6267
         Resolved an issue where Trusted User registration was case-sensitive for an auto-registered new database while it was case-insensitive for manually registered databases.     
Expand
title6.0 New features
  • Anchor
    SQLCM-6350
    SQLCM-6350
         SQL Compliance Manager 6.0 extends the capabilities of the current SQL CM Agent to support remote auditing on SQL servers on EC2. Allowing users to add SQL Servers active on the share network location to write/read data and support DBaaS SQL Server Instances.  The Cloud Agent consists of the same behavior and functionality as the current SQL Agent, but the RDS agent is a separate agent deployed into the cloud with its own configuration auditing settings.
  • Anchor
    SQLCM-6489
    SQLCM-6489
    SQL Compliance Manager 6.0 adds support for Amazon RDS to audit servers, databases, Sensitive Data, and Activities while alerting and reporting on them. Users can select Amazon RDS as their Server Type when adding a new server in the Specify SQL Server configuration window. According to the selection, SQL CM asks to Specify Connection Credentials for the authentication, and once registered, users can begin auditing the database activity on that server.
  • Anchor
    SQLCM-6557
    SQLCM-6557
    SQL Compliance Manager 6.0 permits the creation of storage accounts to place its components within AWS. In Amazon RDS, users can audit Microsoft SQL Server databases using the built-in SQL Server auditing mechanism. For additional information on Support for SQL Server Audit, visit the SQL Server Audit User Guide.
  • Anchor
    SQLCM-6555
    SQLCM-6555
    Upon upgrading to SQL CM 6.0 or preparing a new installation, SQL Compliance Manager Event Collection Method Capture Default Setting changes to "SQL Server Audit Specifications". All audit logs for 'DML and Select Activities' are captured and filtered properly both for the existing CM architecture and the cloud support platform. 
Expand
title6.0 Fixed issues
  • Anchor
    SQLCM-6555
    SQLCM-6555
         Resolved the issue where users were mistakenly prompted for an agent upgrade. Now, if the Agent is on the latest version, the Upgrade Agent displays as a non-clickable out.
Expand
title5.9 New features

There are no new features in this release.

Expand
title5.9 Fixed issues
  • Anchor
    SQLCM-6385
    SQLCM-6385
         Exporting Audit Settings now successfully includes an export of the Server Level Trusted Users configured . 
  • Anchor
    SQLCM-6259
    SQLCM-6259
         Resolved the issue where the SQL Server Properties window displayed the version as Unknown for registered SQL Server 2019 instances. Now, the correct version is shown. 
  • Anchor
    SQLCM-6407
    SQLCM-6407
         Resolved the issue where auditing stopped working when a user-configured Sensitive Column auditing without first selecting the DML or SELECT option caused the SQLcompliance Agent to have problems creating the sp_SQLcompliance_AuditXE  stored procedure.
  • Anchor
    SQLCM-6277
    SQLCM-6277
         Resolved the issue where Events were not captured for sensitive columns when SELECT and DML are not enabled at database-level audited activities on fresh and upgraded setups.
  • Anchor
    SQLCM-6463
    SQLCM-6463
         The DML Activity (Before-After) report shows accurate results regardless of the collection method being set to Extended Events or SQL Tracing.
  • Anchor
    SQLCM-6460
    SQLCM-6460
         The DML\SELECT filters are now working correctly when auditing SQL Server 2019 and no longer prevent DML and SELECT activities from being audited accordingly.
  • Anchor
    SQLCM-6457
    SQLCM-6457
         The following error is no longer observed when attempting to run DML changes on a table configured for Before-After auditing in the software.     "The DELETE permission was denied on the object 'SQLcompliance_Changed_Data_Table'."
  • Anchor
    SQLCM-6379
    SQLCM-6379
         The retention period of the Activity Log is now configurable. It is set to a default of 60 days which can be modified in the SQLcomplianceCollectionService.exe.config file in the MAX_ACTIVITY_LOGS_AGE flag.
  • Anchor
    SQLCM-6376/6365
    SQLCM-6376/6365
         Console loading times are faster now at both console startup and when navigating to the Audit Events view of the audited server or database.
  • Anchor
    SQLCM-6370
    SQLCM-6370
         Event details on INSERT and DELETE events, audited not as INSERT INTO or DELETE FROM executions, are no longer missing the Target Object Name information, showing the name of the database object affected by the audited DML change.
  • Anchor
    SQLCM-6349
    SQLCM-6349
         Reports deployed to SQL Server Reporting Services now show corresponding logins in the Login dropdown filter when these are set to run against an archived database.
  • Anchor
    SQLCM-6223
    SQLCM-6223
    Reports no longer show a syntax error when executed either from the console application or SQL Server Reporting Services.
  • Anchor
    SQLCM-6149
    SQLCM-6149
    The permissions check for the SQL Server service account permissions on the Agent Trace Files folder no longer fails when the SQL Server is running under the NETWORK SERVICE service account.
  • Anchor
    SQLCM-6327/6193
    SQLCM-6327/6193
         Data types have been updated in the tables saving Before-After data to prevent the tables from filling up with event data too soon. This would have prevented new events from processing otherwise, as a result.
  • Anchor
    SQLCM-6367
    SQLCM-6367
         The console application logging is no longer showing a collation conflict error, as shown below:      "Cannot resolve the collation conflict between "SQL_Latin1_General_CP1_CI_AS" and "Latin1_General_CI_AS" in the equal to operation."
Expand
title5.8.1 New features

There are no new features in this release.

Expand
title5.8.1 Fixed issues
  • Anchor
    SQLCM-6134
    SQLCM-6134
    Resolved the issue where the audit configuration was not updated when new users were added to a Windows Domain group which were previously configured as Trusted Users. 
  • Anchor
    SQLCM-6219
    SQLCM-6219
    Resolved the issue where public where public roles were granted unnecessary permissions, such as ALTERas ALTER, EXECUTE, CONTROL, TAKE OWNERSHIP, and VIEW DEFINITION, on the audit stored procedures sp_SQLcompliance_Audit and sp_SQLCompliance_StartUp .
  • Anchor
    SQLCM-6230
    SQLCM-6230
    Resolved the issue where the Collection Server installer raised an error message requesting the removal of the newly restored SQLcompliance and SQLcomplianceProcessing databases. Currently, the migration of the Collection Server preserves the repository databases and displays the events on the console as expected.
  • Anchor
    SQLCM-6050
    SQLCM-6050
    Resolved the issue where users were unable to register instances that are unreachable or from an untrusted domain. Currently, users are able to can register unreachable instances or instances from untrusted domains. Please note that while unreachable instances can be registered for auditing, it is required for the Agent service to be deployed manually on these server instances.
Expand
title5.8.0 New features
  • Anchor
    SQLCM-6206
    SQLCM-6206
    The default settings for capturing DML and Select activities were changed to Extended Events on SQL Compliance Manager 5.8. This change provides a significant performance improvement for the collection service efficiency in event collection, as well as on the performance impact on monitored instances.
  • Anchor
    SQLCM-6207
    SQLCM-6207
    SQL Compliance Manager 5.8 introduces a new highly optimized index format where the application the application upgrades indexes in the background , from a none compression state to a page-level compression type. This operation is done as an Online operation for supported SQL Server editions. Currently, the SQL Compliance Manager repository does not utilize the optimized indexes format. Rebuilding the indexes into the new optimized format provides a significant performance enhancement to the Management Console when viewing audited events and provides a considerable database repository size reduction resulting in resulting in less space usage on disk. For more information see Indexes rebuild operation. 
  • Anchor
    SQLCM-6210
    SQLCM-6210
    SQL Compliance Manager 5.8 modified the Collection Server and Agent to allow a mode where trace files are transferred by the Agent to the Collection Server without compression. Transferring files from the Agent to the Collection Server without compression provides a significant performance enhancement both on the server side in event collection efficiency, and it reduces the performance impact on the monitored instances. In the Agent Properties window, users with Agents in version 5.8 have the option to decide whether to compress or not compress the file transfer from the Agent directory to the Collection directory.  For For more information, see Agent Properties - Trace Options tab. 

...

Expand
title5.7.1 Fixed issues

General issues

  • Anchor
    SQLCM-5989
    SQLCM-5989
    Resolved the issue where the SQL Compliance Manager did not recognize a GMSA account as a Trusted users user 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.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 the Server level and what is being audited at the Database level. With the implementation of Implementing 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 the Server level. Trusted Users designated at the 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.5.0 New features

Anchor
SQLCM-5042
SQLCM-5042
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 2015 and above) or Audit Logs (SQL Server 2017 or and 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.

Anchor
SQLCM-5044
SQLCM-5044
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.

Info

Anchor
SQLCM-5370
SQLCM-5370
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. 

Anchor
SQLCM-5043
SQLCM-5043
Supports SQL Server 2017

IDERA SQL Compliance Manager 5.5 now supports the 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. 

Anchor
SQLCM-5215
SQLCM-5215
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.  

Anchor
SQLCM-5044
SQLCM-5044
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. 

Anchor
SQLCM-5105
SQLCM-5105
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.

Anchor
SQLCM-4929
SQLCM-4929
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. 

Expand
title5.5.0 Fixed issues

Administration issues

  • Anchor
    SQLCM-3759
    SQLCM-3759
    Audit thresholds appear enabled in the ReportCard even after removing and/or archiving an instance.     
  • Anchor
    SQLCM-4972
    SQLCM-4972
    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. 
  • Anchor
    SQLCM-5016/5017
    SQLCM-5016/5017
    Resolved the issue preventing SQL Scripts files with Supplementary Characters to work on the Collation SQL Server.  
  • Anchor
    SQLCM-3741
    SQLCM-3741
    Resolved the issue causing unexpected behavior during the manual upgrade of the SQL Compliance Manager Agent on a remote machine.
  • Anchor
    SQLCM-4674
    SQLCM-4674
    Resolved an issue causing overwritten permissions on the Agent Trace folder after deploying the SQL Compliance Manager Agent. 

Auditing issues

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

Reporting issues

  • Anchor
    SQLCM-4898
    SQLCM-4898
    Email notifications for Event Alerts now display the date and time in the Collection Server time zone. 

  • Anchor
    SQLCM-4645
    SQLCM-4645
    SQL Compliance Manager alerts users about the limit of SQL Statements when exporting reports. 

  • Anchor
    SQLCM-4850/4741
    SQLCM-4850/4741
    Resolved an issue preventing users to view and report on audit data or see events. 

...

called SQL Column Searchhttps://www.idera. com/productssolutions/freetools/sql-column-search. Available from the IDERA SQL Compliance Manager Instance Details view, this feature allows you to search tables and columns on a targeted database to discover the location of sensitive data needing to be audited. For more information about using the Sensitive Column Search, see Sensitive Column Search window.

Offers SQL Compliance Manager Windows Console functionality in the Web Console

The following features, previously available only through the IDERA SQL Compliance Manager Windows Console now are available in the Web Console as well:

Includes updated regulatory guideline templates

IDERA SQL Compliance Manager includes a number of regulatory guideline templates for customer use. IDERA SQL Compliance Manager 5.4 includes updates for these templates. For more information about this feature, see Comply with specific regulations.

Expand
title5.4.0 New features
Warning

IDERA SQL Compliance Manager 5.4 depends on certain Microsoft components that did not ship with SQL Server versions prior to SQL Server 2012 SP1. If you are installing SQL Compliance Manager's Collection Service on a Repository running on SQL Server 2012 or below, you must install these components manually. For more information about this process, see Important installation steps for SQLCM 5.4.x and above.

Improves archiving through the availability of SQL Server Extended Events

IDERA SQL Compliance Manager 5.4 includes support for event handling with SQL Server Extended Events. This optional feature is available for use in auditing instead of using SQL Trace. Running Extended Events offers a performance improvement over the default SQL Trace audit event gathering system and is available for instances running SQL Server 2012 and later. For more information about using the Extended Events option, see Using SQL Server Extended Events.

Includes new Sensitive Column Search

Included in this release is integration with a free tool from IDERA called 

Newtablink
aliasurl

...

Expand
title5.0.0 New features

Fully supports the SQL Server AlwaysOn Availability Groups feature 

SQL Compliance Manager 5.0 now allows DBAs to monitor their availability groups, availability replicas, and availability databases through AlwaysOn Availability in SQL Server 2012 and newer. AlwaysOn automatically switches auditing from the primary to the secondary replica in the event of failure as well as failback to primary when it comes back online. This advantage prevents a loss of audit data trail in the event of failure.

Support for this feature also comes with:

  • An Availability Group Statistics report that allows you view the historical health of your availability groups, availability replicas, and availability databases.
  • An Availability Group Topology report that allows you to view the current topology of your availability groups configuration.
  • Monitoring of key metrics specific to the AlwaysOn Availability Groups feature.
  • Queue Size and Transfer Rates charts.

For additional information on SQL Compliance Manager and the AlwaysOn Availability Groups feature, see Enable automatic failover using AlwaysOn Availability Groups.

Offers a technology preview of a new web-based SQL Compliance Manager Dashboard

Along with the integration of the IDERA Dashboard, SQL Compliance Manager 5.0 includes a preview of a newly-designed web console that offers quick views of key audit trail activities on your SQL Servers from any web browser. Identify key compliance issues quickly and provide an easy access point to non-DBAs without giving them access to the entire Management Console.

Added integration with the IDERA Dashboard

SQL Compliance Manager 5.0 now integrates with the IDERA Dashboard, a common technology framework designed to support the IDERA product suite. Users are able to obtain an overview of the status of their SQL Servers and hosted databases all in a consolidated view and navigate to individual product dashboards for details. The IDERA Dashboard provides a central set of services for managing users, product registry, instance registry, aggregated alerts across IDERA applications, a central web server, and tags for grouping instances. For more information about the IDERA Dashboard, see Navigate the IDERA Dashboard web consoleWeb Console.

Moved to the Windows .NET 4.0 framework

SQL Compliance Manager 5.0 supports Microsoft Windows operating systems using .NET 4.0. Note that .NET 4.0 or later must be installed on the audited server. For more information about requirements, see Software requirements.

...