Versions Compared

Old Version 20

changes.mady.by.user Nicolas Rios

Saved on

compared with

New Version 21

changes.mady.by.user Unknown User (6092af18a56f2f006f392eb0)

Saved on

Key

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

...

Warning

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

...

.1 Fixed issues

Administration issues

  • Anchor
    SQLCM-

...

  • 4972
    SQLCM-

...

  • 4972
    IDERA SQL Compliance Manager 5.5

...

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.

...

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.

...

  • .1 process version 4.5 traces files. After upgrading the Collection Server to version 5.5.1, the agent must be upgraded to the same version. Once upgrades of both, the Agent and the Collection Server is complete, SQL Compliance Manager will process trace files. For more information, see Upgrade to this build.

  • Anchor
    SQLCM-5339/5021/5243/5013/5340/5343
    SQLCM-5339/5021/5243/5013/5340/5343
    Resolved an issue in which the SQL Compliance Manager Collection Server was not processing trace files, or processing them slowly, causing backlog files to get accumulated in the Collection Trace Directory in large transactional databases.

  • Anchor
    SQLCM-5306
    SQLCM-5306
    IDERA SQL Compliance Manager installation no longer fails if TLS 1.0 is disabled and if SQL Server 2012 Native Client is not available.

  • Anchor
    SQLCM-5275/4919/2512
    SQLCM-5275/4919/2512
    IDERA SQL Compliance Manager no longer shows the "Violation of PRIMARY KEY constraint" error nor terminates the statement when performing an archive of a highly transactional database. 

  • Anchor
    SQLCM-5264
    SQLCM-5264
    Integrity check runs for archived databases performed through stored procedures. 

  • Anchor
    SQLCM-5456
    SQLCM-5456
    IDERA SQL Compliance Manager installation no longer fails due to an error setting up permissions if the username used has special characters (e.g. ",", space characters, etc.).
  • Anchor
    SQLCM-4633
    SQLCM-4633
    IDERA SQL Compliance Manager supports user names longer than 20 characters as well as special characters for the user's password, such as £.

For more information about new features and fixed issues in versions 5.5.x, see Previous new features and fixed issues.

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. 

...

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. 

...

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.  

...

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. 

...

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.

...

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

...

Auditing issues

...

Reporting issues

...


Scroll pdf ignore

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

IDERA Website | Products | Buy | Support | Community | About Us | Resources | Legal

Scroll Pagebreak