Page History

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

4.

...

2 New features

• Anchor
  SQLSECU-2639215 SQLSECU-2639

  The Configuration Security Checks

  215

  SQL Secure now  now allows you to configure your Backups compliance more freely with the Backups compliance with RTO and RPO requirements check. Now, you can set up the backup frequency and select the databases to backup.

...

• take a snapshot of your registered servers at once.

• Anchor
  SQLSECU-2655 SQLSECU-2655

  The Server Roles report now shows members from Windows groups.

• Anchor
  SQLSECU-1242 SQLSECU-1242

  The Database Roles report now displays the creation date of the database.

4.2 Fixed issues

• Anchor
  SQLSECU-26642833 SQLSECU-26642833

  When exporting a Policy, SQL Secure no longer checks all the checkboxes by default. It only keeps the enabled ones of the exported policySQL Secure successfully monitors a set of databases after taking a snapshot, avoiding the "Some databases were unavailable for auditing" warning.

• Anchor
  SQLSECU-27602831 SQLSECU-27602831

  SQL Secure now correctly labels log-shipped databases in standby/read-only recovery as "Databases Files" when running a snapshotThe results of the snapshot show the 'Weak Passwords' security check identifying the new SQL Login a user created with the password set to one of the passwords from the list of Default Weak Passwords, and flags that as a finding.

• Anchor
  SQLSECU-

  2772

  2811 SQLSECU-2811

  Collation settings no longer cause a conflict between the audited server and what it is expecting to match.

• Anchor
  SQLSECU-2820 SQLSECU-2820

  "Backups compliance with RTO and RPO requirements" security check includes non-system databases that never had a backup, excluding system databases2772 When the sa login is renamed and disabled, SQL Secure reports a Warning level risk finding.

• Anchor
  SQLSECU-

  2782

  2823 SQLSECU-

  2782

  2823

  SQL Secure no longer displays Orphaned Users check findings when database users are mapped to certificates Now you can Install SQL Secure on a SQL Instance with a different collation, allowing you to work with not supported SQL Server Versions.

• Anchor
  SQLSECU-

  2771

  2764 SQLSECU-2764

  Database Roles report now shows results in alphabetical order2771 Now the Risk Assessment Report correctly reports the sa account status when it is disabled.

• Anchor
  SQLSECU-

  2773

  2821 SQLSECU-

  2773

  2821

  The Risk Assessment Report correctly reports when the sa account does not exist on the serverDatabase Roles report now displays the expected results of the selected databases.

• Anchor
  SQLSECU-

  2801

  2798 SQLSECU-

  2801

  2798

  Now SQL Secure Grooming Job runs correctly and as expectedcorrectly reports the "SQL Server Database Level Encryption" security check for Azure SQL Databases.