...
- When exporting a Policy, SQL Secure no longer checks all the checkboxes by default. It only keeps the enabled ones of the exported policy.
- The 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.
- When the sa login is renamed and disabled, SQL Secure reports a Warning level risk finding.
- SQL Secure no longer displays Orphaned Users check findings when database users are mapped to certificates.
- Now the Risk Assessment Report correctly reports the sa account status when it is disabled.
- The Risk Assessment Report correctly reports when the sa account does not exist on the server.
- Now SQL Secure Grooming Job runs correctly and as expected.
...
- SQL Secure enhanced the assessmentassessments' s loading time; they no longer take several minutes to display information.
- Snapshot collection on Availability Group Nodes no longer generates a file permissions warning message.
- Snapshot collection completes successfully for a log-shipped database.
- The The number of Stored Procedures in the Stored Procedures Encrypted details of the security check no longer differs from the number of Stored Procedures in SSMS.
- SQL Secure no longer displays timeout errors while generating the Database Roles Reports.
- Renaming and disabling sa login account no longer shows a "sa Account Not Disabled" security check.
- "Public Server Role only granted default Microsoft permissions" security check shows the correct information related to Server Roles.
- The Snapshot Comparison Report no longer displays server changes when no changes have been made.
- The User Permission Report works correctly with different collations sets.
- SQL Secure imports hidden instances using CSV files.
- The Snapshot collection process completes successfully for imported instances using CSV files.
- The Risk Assessment Report no longer reports the sa login account incorrectly.
- SQL Secure no longer has issues with bulk email notification settings.
- Renaming the sa login in a SQL Server instance no longer generates a false warning risk level in the 'sa account is not disabled' check.
- SQL Secure enhanced the SQL Job Permission security check.
...
null