IDERA SQL Compliance Manager build includes many fixed issues, including the following updates.
| Expand |
|---|
|
- 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.
- 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.
- 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.
- 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 |
|---|
|
- 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 |
|---|
|
There are no new features in this release. |
...