Versions Compared

Old Version 41

changes.mady.by.user Rodrigo Rivero

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.

...

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. 

...