Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

This build of IDERA SQL Secure includes many fixed issues, including the following previous updates.

3.4.1 Fixed issues

  • Anchor
    SQLSECU-2759
    SQLSECU-2759
    The time to keep snapshots before letting them be groomed is no longer set by default to one day when importing files in CSV format.
  • Anchor
    SQLSECU-2758
    SQLSECU-2758
    The User Permission report is no longer showing errors in the db_role information.
  • Anchor
    SQLSECU-2757
    SQLSECU-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.
  • Anchor
    SQLSECU-2744
    SQLSECU-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.
  • Anchor
    SQLSECU-2735
    SQLSECU-2735
    "Orphaned users" security check is no longer identifying users without matching logins as orphan users.
  • Anchor
    SQLSECU-2678
    SQLSECU-2678
    The 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.
  • Anchor
    SQLSECU-2676
    SQLSECU-2676
    Generating the Database Roles report is no longer causing a "maximum recursion" error message.
  • Anchor
    SQLSECU-2608
    SQLSECU-2608
    SQL 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".

3.4 New features

  • Anchor
    SQLSECU-2687
    SQLSECU-2687
    SQL Secure adds a DISA-NIST STIG policy and security check templates for SQL Server 2016, with 11 security checks enabled by default.
  • Anchor
    SQLSECU-2557
    SQLSECU-2557
    An additional policy field filtering option was implemented in the Assessment Comparison report.

3.4 Fixed issues

  • Anchor
    SQLSECU-2679
    SQLSECU-2679
    The 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.
  • Anchor
    SQLSECU-2688
    SQLSECU-2688
    The SQL Mail or Database Mail Enabled security check now is working as expected.
  • Anchor
    SQLSECU-2689
    SQLSECU-2689
    Addressed several areas causing poor performance and usability in the user permissions report with significant success.
  • Anchor
    SQLSECU-2711
    SQLSECU-2711
    Streamlined workflow for the snapshot data collection operation.

3.3.2 New features

  • Anchor
    SQLSECU-2702
    SQLSECU-2702
    Anchor
    SQLSECU-2703
    SQLSECU-2703
    Anchor
    SQLSECU-2645
    SQLSECU-2645
    Anchor
    SQLSECU-2685
    SQLSECU-2685
    Anchor
    SQLSECU-2677
    SQLSECU-2677
    SQL Secure now supports Windows Server 2019 and SQL Server 2019.
    • Install, upgrade, uninstall SQL Secure using SQL Server 2019 based repository.
    • Monitor SQL Server 2019 based instances where SQL Secure repository uses SQL Server 2019 or previous versions.
    • Monitor SQL Server 2019 and previous versions from environments where SQL Secure repository uses SQL Server 2019.
    • Register SQL Server 2019 on Azure VM and Azure SQL Database, generates all available reports.
    • Register SQL Server 2019 on Amazon EC2 and Amazon RDS for SQL Server, generates all available reports.
  • Anchor
    SQLSECU-2686
    SQLSECU-2686
    SQL Secure adds policy templates: CIS for SQL Server 2017 and SQL Server 2019.

...