Page History

...

5.5.1 Fixed issues

...

6.3 New Features

Security Enhancements

Anchor
SQLCM-

...

6760 SQLCM-

...

6760

Essential Security Permissions for SQLCM to Function

SQL Compliance Manager 6.3 release delivers security permissions based on the least privilege principle (as opposed to permissions based on standard user roles such as sysadmin) to further enhance the data security per user within the product.

6.3 Fixed Issues 

• Anchor
  SQLCM-6883 SQLCM-6883

  Fixed an issue where DDL events were not being captured for server-level privilege users configured through a domain group 5.5.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. AnchorSQLCM-5339/5021/5243/5013/5340/5343SQLCM-5339/5021/5243/5013/5340/5343Resolved 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

  6364 SQLCM-

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

  6364

  Resolved the issue where the Regulatory Compliance Check report was showing "No" at server-level for PCI DSS guideline. 
  

• Anchor
  SQLCM-

  5275/4919/2512

  6860 SQLCM-

  5275/4919/2512IDERA 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. 

  6860

  Fixed an issue where the IP Address Auditing checkbox was unchecked after importing an exported audit setting file.
  

• Anchor
  SQLCM-

  5264

  6855 SQLCM-

  5264Integrity check runs for archived databases performed through stored procedures. 

  6855

  Addressed an issue with Audit Events not appearing on SQLCM console when CM repo was hosted on a Case Sensitive SQL instance.
  

• Anchor
  SQLCM-

  5456

  6816 SQLCM-

  5456IDERA 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.). AnchorSQLCM-4633SQLCM-4633IDERA SQL Compliance Manager supports user names longer than 20 characters as well as special characters for the user's password, such as £

  6816

  Solved the issue of multiple alerts being logged for a single event.
  • The number of Data and Event alerts is consistent with the number of audit events generated.
  • The email alerts have been improved with the appropriate event description.

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