Page History

IDERA strives to ensure our products provide quality solutions for your SQL Server needs. If you need further assistance with any issue, please contact Support (www.idera.com/support).

3.

...

4 Known issues

...

• Anchor
  SQLSECU-2663 SQLSECU-2663

  Exporting reports to PDF may generate blank spaces in within the document. 

• Anchor
  SQLSECU-2664 SQLSECU-2664

  The export policy process may change the number of security checks enabled for each policy.

• Anchor
  SQLSECU-2666 SQLSECU-2666

  Importing policies may display the following error: "This security check requires at least one criterion".

• Anchor
  SQLSECU-2676 SQLSECU-2676

  Circular dependency in database user groups causes a "maximum recursion" error message while generating the Database Roles report. AnchorSQLSECU-2679SQLSECU-2679SQL Secure counts up decommissioned servers as licensed servers, which may affect auditing of the registered servers if licenses are insufficient. Consider removing the decommissioned servers as a workaround to this issue. AnchorSQLSECU-2688SQLSECU-2688The "SQL Mail Or Database Mail Enabled" security check is validated only against SQL Server 2005 and lower. AnchorSQLSECU-2622SQLSECU-2622 AnchorSQLSECU-2689SQLSECU-2689 AnchorSQLSECU-2678SQLSECU-2678The User Permissions report for specific databases may generate a timeout error. Consider increasing the SQL Command Timeout to prevent timeout errors.

• Anchor
  SQLSECU-2708 SQLSECU-2708

  SQL Secure displays an error message when a user with Audit Data User permissions launches the console. To fix this error message, consider granting explicit "Select" permissions to the user on the SQLSecure repository database as shown in the image below.

...

• Anchor
  SQLSECU-2707 SQLSECU-2707

  Anchor
  SQLSECU-2661 SQLSECU-2661

  When launching the application with the "Run as Administrator" option, the UAC (User Account Control) prompt shows "Unknown" for the Publisher information.

3.3.1 Known issues

General

• Anchor
  SQLSECU-26222735 SQLSECU-2622

  The User Permission Report for specific databases may generate a timeout error. Increase the SQL Command Timeout from default to fix the problem. AnchorSQLSECU-2544SQLSECU-2544The CIS for SQL Server 2016 policy is not listing the 3.10 (Ensure Windows local groups are not SQL Logins) and the 3.11 (Ensure the public role in the msdb databases is not granted access to SQL Agent proxies) security checks.

  2735

  A user without login is identified as an orphan user. As a workaround, when these users are discovered and manually validated as such, they should be added into the exclusion filter of the Orphaned Users security check AnchorSQLSECU-2486SQLSECU-2486The Snapshot Comparison Report is not showing server role changes. AnchorSQLSECU-723SQLSECU-723The User Permission Report is missing some information when exporting in Excel files.

...