Page History

IDERA IDERA SQL Secure provides the following new features and fixed issues.

...

4.4

...

New features

• Anchor
  SQLSECU-

  2759

  2907 SQLSECU-

  2759The time to keep snapshots before letting them be groomed is no longer set by default to one day when importing files in CSV format. AnchorSQLSECU-2758SQLSECU-2758The User Permission report is no longer showing errors in the db_role information. AnchorSQLSECU-2757SQLSECU-2757 The User Permissions report shows all schema level permissions data. The Object Type filter is no longer generating blank spaces after any object type name. AnchorSQLSECU-2744SQLSECU-2744 You can access registry key information and the SQL Server install folder with Local Administrador and Sysadmin permissions. The Snapshot collection is no longer displaying warning messages caused by permissions on the SQL Server instance. AnchorSQLSECU-2735SQLSECU-2735"Orphaned users" security check is no longer identifying users without matching logins as orphan users. AnchorSQLSECU-2678SQLSECU-2678The All User Permissions report now allows you to expand or collapse results upon report execution. When the report has many permission results, displaying the results collapsed will allow the report to complete execution faster while permissions can be expanded and explored for each audited database

  2907

  The Snapshot Comparison report settings now include a checkbox that allows the report to show the object comparison based on:
  • Current logic.
  • Updated logic to ignore restored objects that are identical to the previous snapshot.

• Anchor
  SQLSECU-

  2676

  2190 SQLSECU-

  2676Generating the Database Roles report is no longer causing a "maximum recursion" error message. AnchorSQLSECU-2608SQLSECU-2608SQL Secure fixed the "Is the SQL Server sa account enabled" security check to have a passed status when the finding is "The sa account is not enabled".

...

• 2190

  The Snapshot Comparison report now shows a more detailed view of the user level access changes that occurred between two different snapshots.

4.4 Fixed issues

• Anchor
  SQLSECU-

  2687

  2799 SQLSECU-

  2687SQL Secure adds a DISA-NIST STIG policy and security check templates

  2799

  The Snapshot May Be Missing Data security check was incorrectly reported for SQL Server 2016
  , with 11 security checks enabled by default. AnchorSQLSECU-2557SQLSECU-2557 An additional policy field filtering option was implemented in the Assessment Comparison report.

3.4 Fixed issues

• AnchorSQLSECU-2679SQLSECU-2679The error message where "SQL Secure was unable to acquire a valid key" is no longer displayed while trying to take snapshots after decommissioning some servers. AnchorSQLSECU-2688SQLSECU-2688The SQL Mail or Database Mail Enabled security check now is working as expected. AnchorSQLSECU-2689SQLSECU-2689 Addressed several areas causing poor performance and usability in the user permissions report with significant success. AnchorSQLSECU-2711SQLSECU-2711Streamlined workflow for the snapshot data collection operation

  and SQL Server 2017. This is now fixed.

...