Page History

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

...

These security checks are enabled in the Idera IDERA Level 3 policy template.

New FIPS support

...

• • SQL Secure now correctly detects whether the SQL Server Agent is running on SQL Server instance hosting the Repository. This issue occurred when the SQL Server instance was configured to use a double-byte character set, such as the Turkish language.
  • SQL Secure correctly excludes stored procedures listed in the Startup Stored Procedures security check criteria.
  • SQL Secure now correctly collects audit data when you configure your snapshot filters to retrieve security information about System Only or User Only object types.
  • SQL Secure now includes improved file data collection. Previously, when attempting to run a snapshot, SQL Secure had returned snapshot warnings and logged the following error: "Method failed with unexpected error code 53."
  • SQL Secure now correctly handles data collection from instances located in an Active-Active cluster running Windows Server 2008.
  • The Database File Permissions Not Acceptable security check now includes the system resource database files for SQL Server 2005 or later. On SQL Server 2005 instances, if these database files are not located in the same folder as the Master database, then SQL Secure may not be able to find the files and thus the security check may not return a correct finding.
  • The Audited SQL Server Properties window now correctly applies your policy membership changes.
  • SQL Secure now stores the Collector logs in the Idera IDERA installation directory by default.