Versions Compared

Old Version 2

changes.mady.by.user Nadja Pollard

Saved on

compared with

New Version 3

changes.mady.by.user Nadja Pollard

Saved on

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.

2.7 New features

New policy templates for PCI and HIPAA

The SQL Secure policy templates now address security standards for the Payment Card Industry (PCI) and the Health Insurance Portability and Accountability Act (HIPAA), allowing you to immediately begin accessing your SQL Server environment against these regulations.

New weak password detection

SQL Secure now detects and analyses the password health of SQL logins on your audited SQL Server instances, reporting when passwords are blank or weak.

New security checks

SQL Secure now provides these additional security checks to help you further harden the security of your SQL Server instances:

  • Weak Passwords
  • Public Role Has Permissions on Database User Objects
  • Integration Services Roles Have Dangerous Security Principals
  • Integration Services Permissions Not Acceptable
  • These security checks are enabled in the IDERA Level 3 policy template.

New FIPS support

SQL Secure now supports auditing and assessing the security of SQL Server instances located in environments that require FIPS compliance.

New SQL Server 2012 support

SQL Secure now offers full support of SQL Server 2012 RTM.

2.7 Fixed issues

  • When changing server connection credentials, SQL Secure now identifies other audited SQL Server instances that use the same account and then lets you change their connection credentials as well.
  • SQL Secure now correctly processes local account information for SQL Server instances operating in clustered environments.
  • Snapshots that have been marked as baselines are no longer deleted from the SQL Secure Repository database during grooming.
  • The SQL Secure Collector now correctly gets file permissions for service executable files when the file name is specified in upper case.
  • The SQL Secure Collector now correctly gets permissions data for system databases that are not located on the local drive of the target SQL Server instance.
  • SQL Secure now successfully displays the Server Security Report Card and generates the Risk Assessment report when the audited SQL Server instance and the instance hosting the SQL Secure Repository have been assigned different collations.
  • When scheduling monthly snapshots, SQL Secure now correctly applies the "3rd," "4th," and "Last" options for specific days of the month.

...