Page History
This build of IDERA SQL Compliance Manager build includes many fixed issues, including the following updates.
Expand |
---|
...
|
...
|
...
|
...
Supports Windows Server 2012 cluster deployment
This version of SQL Compliance Manager allows you to install in a Windows Server 2012 clustered environment. For more information about this feature, see Deploy SQL Compliance Manager in a Windows Server 2012 clustered environment.
Audit the local SQL Server instance running the Collection Server on a cluster
SQL Compliance Manager allows you to audit a virtual SQL Server instance including the local instance on a cluster running the Collection Server. For more information about auditing a virtual SQL Server instance, see Audit a virtual SQL Server instance.
Schedule automatic archives
SQL Compliance Manager now allows you to schedule automatic archiving. You can select from daily, weekly, or monthly options. This feature is disabled by default. You can enable this feature and manage these settings in the Archive Preferences window.
Specify archive database drive
When setting up archiving, you can specify the drive where you want SQL Compliance Manager to store the archive database. You can manage this location in the Archive Preferences window.
Receive alerts through SNMP
Users now can select to receive alerts as SNMP Trap messages to a specified destination network management console. For more information about creating a new event rule to includes SNMP Traps, see New Event Alert Rule wizard - Alert Actions tab.
Before-After data values display NULL when there is no value
After collecting data, if there is no before or after data available, SQL Compliance Manager displays "NULL" in the Before Value and After Value columns of the Event Properties window. For more information about Before-After data, see Audited Database Properties window - Before-After Data tab.
Supports PCI DSS v3
SQL Compliance Manager now supports Payment Card Industry Data Security Standard (PCI DSS) v3.0.
Improved table compression
The data type is changed in a number of highly-utilized tables from NTEXT to VARCHAR in an attempt to improve data compression.
Improved installation process
The SQL Compliance Manager installer now checks the permissions on the trace directory and the IDERA folders to ensure that the service account is appropriately added with full control permissions for processing.
Improved database usage regarding failed inserts
SQL Compliance Manager includes new code that allows it to reuse event IDs in the event of a failed data insert.
4.5 Fixed issues
- SQL Compliance Manager includes new code regarding the threading library, making sure that all files in the trace directory are successfully processed. This fixes an issue that caused large trace file backlogs in the Collection Server.
- The Administrative Activities Audit Option no longer re-enables automatically after disabled.
- Users no longer receive an error when processing the trace file due to a limited column size in the table associated with Before-After Data.
- Users upgrading from SQL Compliance Manager 3.7 to 4.3 no longer receive numerous file parsing errors.
- This release fixes an issue causing incorrect dates to appear if you have SELECT and Sensitive Columns enabled in the Audited Database Properties window. Previously, if the Database SELECT operations check box on the Audited Activities tab, and the Sensitive Columns tab includes All Columns of the dbo.Customers table, the dates in the summary for the associated SQL Server instance were incorrect.
- An issue that prevented new SQL Compliance Manager Agent files from processing after adding a second node to a clustered repository no longer occurs.
- All failed integrity checks now includes specific events in the Details area of the Integrity Check Results window.
- Users no longer experience missing registry keys after re-adding monitored SQL Server instances.
- Adding an audited database to a monitored SQL Server instance no longer returns the server settings to default.
- Providing read-only access to the SQLcompliance database no longer requires that the GUEST account be enabled.
4.3 New features
SQL Compliance Manager 4.3 now offers a Collection Server-only install
SQL Compliance Manager 4.3 now allows you to install the Collection Server and Repository only to support installing SQL Compliance Manager on a cluster.
4.3 Fixed issues
There are no fixed issues in this release.
4.2 New features
New Family Educational Rights and Privacy Act (FERPA) guideline
Apply the new FERPA regulatory guideline to ensure your audited databases meet the requirements of this legislation. You can apply this guideline through the CLI or through the Import Audit Settings feature in the Console.
FERPA was introduced in 1974. This federal law mandates the confidentiality and protection of student information in any educational institution that receives funding from the Federal Government from kindergarten through the university level. FERPA generally prevents an education agency or institution from sharing student records or personally identifiable information in those records with individuals who are not authorized to view that information. In some cases authorized individuals need to be monitored to deter insider theft and unauthorized dissemination of information.
New Sarbanes Oxley (SOX) guideline
Apply the new SOX regulatory guideline to immediately enforce the right auditing settings for sensitive financial data. Collect a detailed audit trail of all access to that data and then deliver reports that prove your compliance to auditors. You can apply this guideline through the CLI or through the Import Audit Settings feature in the Console.
SOX, also known as the Corporate and Auditing Accountability and Responsibility Act, was first introduced in 2002. This legislation was put in place as a response to the corporate and accounting scandals which cost investors billions of dollars. From an information technology standpoint, security professionals and database administrators must collectively implement policies and processes that audit permissions on, and access to, financial data as well data changes such as before and after values.
New CLI actions register instances and apply audit settings
Use the new command line interface (CLI) actions to quickly and easily register large numbers of SQL Server instances and immediately apply audit settings to the hosted databases. You can choose to apply the default audit settings, custom audit settings you have exported from another audited instance, or a regulation guideline.
4.2 Fixed issues
- When the T-SQL query associated with an event cannot be parsed, SQL Compliance Manager now captures the SQL statement and indicates that it could not be parsed. This issue was mostly likely to occur when auditing sensitive column access.
- The Details tab of the Event Properties window now displays the SQL statement that is issued to SQL Server before SQL Server performs its query parameterization. This code represents the initial T-SQL query executed by the user.
4.0 New features
Offers HIPAA compliance guideline support
Collect data that helps you align with nine Health Insurance Portability Accountability Act (HIPAA) citations and one HITECH requirement via an out-of-the-box, customizable template.
Includes PCI compliance templates
Use the new, customizable auditing templates to help you comply with eight Payment Card Industry Data Security Standards (PCI DSS) requirement guidelines.
Provides Regulation Guideline reporting
The Regulation Guidelines report includes details for all of the guidelines applied to the databases on the selected SQL Server instance.
Features a new SQL Compliance Manager Configuration Wizard for ease of use
The new SQL Compliance Manager Configuration Wizard allows you to use a single wizard to register SQL Server instances, deploy the SQLcompliance Agent, add databases for audit, configure your audit settings for selected regulatory guidelines, and more.
4.0 Fixed issues
- SQL Compliance Manager now properly processes Grant statements.
- An issue causing SQL Compliance Manager to record Create and Drop Index events as Alter User Table events no longer occurs.
- SQL Compliance Manager now loads custom reports on the Archived Events page without requiring the user to select a filter.
- SQL Compliance Manager now honors the DML/SELECT filters if you enable both Select auditing and Sensitive Column Auditing.
- SQL Compliance Manager now properly applies event filters for instances using non-standard ports.
3.7 New features
SQL Server 2012 compatible with experimental support
SQL Compliance Manager 3.7 is SQL Server 2012 RTM compatible. This version of SQL Compliance Manager is not certified against newer builds of SQL Server and should not be used with these builds in a production environment. IDERA provides experimental support while you use your installation in a testing environment to ensure the features you rely on most are working as, or better than, expected.
3.7 Fixed issues
There are no fixed issues in this release.
3.6 New features
New sensitive column alerting
You can now receive alert notifications when someone accesses a sensitive column in your audited databases.
Improved integrity check user interface
The Integrity Check Results window now indicates when before-after data associated with DML
events and sensitive column access data associated with SELECT
events have been modified or deleted.
3.6 Fixed issues
The following reports now include the option to view related data from all audited SQL Server instances in your environment:
- Database Schema Change History
- Object Activity
- User Login History
3.5 New features
Sensitive column auditing
Track who has "selected" data from any number of columns in your audited tables and proactively identify malicious intent.
Transaction status auditing
Audit the status of any transaction that executes DML activity on your audited database. This audit data enhancement includes rollbacks and save points, allowing you to recognize suspicious activity.
3.5 Fixed issues
The Management Console now correctly imports alert rules exported from version 3.3 or earlier.
3.3 Fixed issues
- SQL Compliance Manager now supports auditing SQL Server instances located in environments that require FIPS compliance.
- The Collection Server now no longer performs duplicate processing of events collected in high-traffic environments. When this issue occurred, SQL Compliance Manager would write error and warning messages to the application event log, stating that it was either unable to read a trace file due to insufficient privileges or unable to delete the trace file due to a SQL Server lock.
- You can now successfully audit before-after data for DML events that occur on SQL Server databases hosted by a Windows Server Cluster.
- The DML/SELECT Filters tab of the Audited Database Properties window now allows you to successfully enable before-after auditing for DML events on specific database tables.
3.2 Hotfix 1 Fixed issues
- The SQLcompliance Agent now correctly handles a fail over that occurs on an active-active Windows cluster.
- When storing DML events collected for Before-After auditing, event processing now correctly stores each event only one time for statements that insert more than 1000 rows.
3.2 Fixed issues
- The SQLcompliance Agent now refreshes its list of DBID (database identifier) properties at each heartbeat. This fix ensures that SQL Compliance Manager can continue collecting audit data for a database after its ID number changes. For example, database ID numbers can change when a database is dropped, backed up, re-attached, or restored.
- The groom job now correctly deletes all events older than the specified age.
- The groom job now correctly identifies the SQL Server version, ensuring it grooms before and after data generated by DML events in SQL Server 2005 or later only. The ability to collect before and after data is not supported on SQL Server 2000 instances.
- Event Filters now support blank, empty, or null values when specifying application and host names.
3.1 Hotfix 1 Fixed issues
- When attempting to audit DML activity on specific databases, the SQLcompliance Agent would sometimes fail to collect the DML events according to your audit settings. With this hotfix, the SQLcompliance Agent correctly audits the specified databases for DML activity.
- After enabling the ability to audit Before-After data on database tables, SQL Compliance Manager would require accounts to have administrator privileges to the tables created by SQL Compliance Manager in order to modify data in the audited table, potentially preventing third-party applications and other accounts from writing to these tables. This hotfix allows SQL Server logins to read and write to the audited tables per the assigned privileges.
- When attempting to groom audit data from a SQL Compliance Manager Repository hosted on a SQL Server 2000 instance, the grooming process would fail, returning the error “incorrect syntax near the keyword 'TOP'”. With this hotfix, you can successfully groom the Repository.
- When you attempt to update the archive database indexes using the command-line interface or the Management Console, the update process would fail. With this hotfix, you can successfully update all archive databases to the new Repository schema.
- The Management Console did not correctly format statistics with large values, resulting in an incorrect Processed Events statistic on the Explore Activity views. This hotfix resolves these formatting issues.
Excerpt |
---|
SQL Compliance Manager audits all activity on your server. Learn more > > |
|
Expand | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Expand | ||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||
|
Expand | ||||||
---|---|---|---|---|---|---|
| ||||||
|
Expand | ||
---|---|---|
| ||
There are no new features in this release. |
Expand | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Expand | ||
---|---|---|
| ||
There are no new features in this release. |
Expand | ||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||
|
Expand | ||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||
|
Expand | ||
---|---|---|
| ||
There are no new features in this release. |
Expand | ||
---|---|---|
| ||
There are no new features in this release. |
Expand | ||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||
General issues
|
Expand | ||
---|---|---|
| ||
GeneralSupports SQL Server 2019IDERA SQL Compliance Manager 5.7 now supports the installation of the Database Repository for the 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 2019The 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. ReportsNew ReportsSQL 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 usersSQL Compliance Manager version 5.7 introduces the ability to restrict user access to certain SQL CM reports. As an administrator, you can grant users permission 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 improvementsSQL Compliance Manager version 5.7 brings updates and improvements to reports by making reports more consistent and adding new filter 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 | ||||||
---|---|---|---|---|---|---|
| ||||||
General issues
|
Expand | ||
---|---|---|
| ||
GeneralSensitive Column SearchSQL 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 | ||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||
Installation and Configuration issues
|
Expand | ||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||
GeneralCapture Logout EventsCurrently, 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 SettingsSQL 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 AutomaticallySQL 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 ClarificationsCompliance 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. 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.
Server-Level Trusted UsersSQL 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 AuditingSQL 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 UpdatesSQL 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.
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 GuidelinesGDPR RegulationSQL 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. ReportsConfiguration Check ReportSQL 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 ReportSQL 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 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Installation and Configuration issues
|
Expand | ||
---|---|---|
| ||
There are no new features in this release |
Expand | ||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||||||||
Administration issues
|
Expand | ||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||||||||||||||||
Anchor |
|
Anchor | ||||
---|---|---|---|---|
|
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 | ||||||
---|---|---|---|---|---|---|
|
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
SQLCM-5043 | |
SQLCM-5043 |
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
SQLCM-5215 | |
SQLCM-5215 |
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
SQLCM-5044 | |
SQLCM-5044 |
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
SQLCM-5105 | |
SQLCM-5105 |
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 | ||||
---|---|---|---|---|
|
IDERA SQL Compliance Manager 5.5 allows users to install and/or upgrade in a non-default drive path.
Expand | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Administration issues
Auditing issues
Reporting issues
|
Expand | ||
---|---|---|
| ||
Supports TLS 1.2 with SQL CM 5.4.2IDERA SQL Compliance Manager 5.4.2 includes support for Transport Layer Security (TLS) version 1.2. The TLS protocol provides encryption, authentication, and data privacy and integrity when transferring information over a network, including VPN, VOIP, and instant messaging. |
Expand | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Administration issues
Auditing issues
Archiving issues
Reporting issues
|
Expand | ||
---|---|---|
| ||
Improves archiving through the availability of SQL Server Extended EventsIDERA 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 SearchIncluded in this release is integration with a free tool from IDERA called 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 ConsoleThe 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 templatesIDERA 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 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Installation and upgrade issues
|
Expand | ||
---|---|---|
| ||
Supports SQL Server 2016 IDERA SQL Compliance Manager 5.3.1 and later support audited and collection servers using Microsoft SQL Server 2016. For more information about supported platforms, see Software requirements. |
Expand | ||
---|---|---|
| ||
There are no fixed issues in this release. |
Expand | ||
---|---|---|
| ||
Expanded the SQL Compliance Manager Web console to provide a richer set of capabilities onlineIDERA SQL Compliance Manager 5.3 continues to build on the work developed by prior versions to bring a richer set of capabilities to the web console. New web capabilities include:
Integration with IDERA Dashboard 2.2IDERA Dashboard integration began with SQL Compliance Manager 5.0, which centralizes the common administration, tasks, and views across all IDERA SQL products. This release of SQL Compliance Manager expands this integration by supporting IDERA Dashboard 2.2, which includes the following widgets specific to SQL Compliance Manager:
For more information about using SQL Compliance Manager widgets within the IDERA Dashboard, see Overview tab. Limited Support for SQL Server 2016IDERA supports installation of SQL Compliance Manager 5.3 on Microsoft SQL Server 2016 with limited technical support. Full technical support is available a short period after SQL Server 2016 is generally available. |
Expand | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
General
Installation
Licensing
Services
Auditing
|
Expand | ||
---|---|---|
| ||
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:
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 DashboardAlong 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 DashboardSQL 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 Console. Moved to the Windows .NET 4.0 frameworkSQL 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. |
Expand | ||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Scroll Pagebreak |
---|
...