...
- SQL Secure only recognizes the first license key added. If the first license key gets expired the product will ask for a new valid license key, even if the product has another valid license keys registered. You can remove the old license key by deleting it and this way it will recognize the valid license key. You can contact your IDERA Account Team for an updated license.
- The uninstall process may not completely remove the SQL Secure folder in the Program files but user can manually remove it after uninstall process completes.
- The Snapshot Data Collection process for Windows Server 2016 is showing some incorrect warnings.
- SQl Secure is not able to add new servers to Server Group Tags.
- The Show Risk Only option in the Risk Assessment Report does not make any difference in the report list.
| Anchor |
|---|
SQLSECU-2065 | SQLSECU-2065 | The Register SQL Server error message regarding supported versions needs updating to include SQL Server 2017.
Security Checks
- The Unauthorized Account Check Security Check is not listing the proper permissions for SQL Server 2008 and reports this message "Unauthorized member found: 'public' (VIEW ANY COLUMN ENCRYPTION KEY DEFINITION, VIEW ANY COLUMN MASTER KEY DEFINITION)"
- SQL Server Installation Directories on system Drive Security check is failing in Azure Virtual Machines.
- Some older security template requires a user input for the security checks but SQL Secure is allowing user to save these polices without inputting criteria. It can result in a risk finding in the report. When this happens the user can always go back in and edit the policy to update the criteria.
- Not all SSRS reports are able to export to CSV format. The workaround is to export to Excel and open the report in Excel and re-save as csv format.
...
null