This build of IDERA SQL Secure includes many fixed issues, including the following previous updates.
3.3.2 New features
- 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.
- SQL Secure adds policy templates: CIS for SQL Server 2017 and SQL Server 2019.
3.3.2 Fixed issues
- The CIS for SQL Server 2016 policy lists all the corresponding security checks.
- Snapshot comparison report doesn't show server role change.
- Exporting the User Permission Report is working as expected.
3.3.1 Fixed issues
- The Operating System Security Check no longer generates risks when Operating system matches with the details.
- Unauthorized Account Security Check is no longer displaying inconsistent results and details.
- SQL Secure improved its performance significantly decreasing report generation times.
- Snapshot Comparison Report displays the correct Server Role when a difference is generated between snapshots.
3.3 New features
- Adds audit support for Amazon RDS and Amazon EC2.
- Supports installing SQL Secure on Azure VM and Amazon EC2.
- Adds new security checks to support GDPR and provide a GDPR policy template.
- Updates Idera Level 1 - 3 policy templates.
- Enhances the Import/Export Policy.
- Provides an option to make bulk changes to email notification settings.
- Allows users to archive snapshots for decommissioned servers.
3.3 Fixed issues
- SQL Secure is no longer having issues with expired Licenses.
- SQL Secure Grooming Job is no longer failing while classifying errors from warnings.
- The Unauthorized Account Check security check is not returning findings on SQL Server 2008 R2, it works with SQL Server 2016 and above.
- The explanation notes functionality is working for all security checks.
- The uninstallation process completes removing all SQL Secure files.
- SQL Secure reports show Snapshot missing data when all Sequence Objects are included in the filter.
- The Snapshot Data Collection process for Windows Server 2016 is no longer showing incorrect warnings.
- TracerX-Viewer.application no longer requires to upgrade the .NET version.
- SQL Secure includes the option to add new servers to Server Group Tags.
- The Risk Assessment Report includes the Show Risk Only option.
- HIPAA policy now includes msdb database as default in the criteria.
- SQL Secure installer includes the Visual C++ 2015 Redistributable.
3.2 New features
New Security Templates
...
IDERA SQL Secure 3.1.200 now allows you to reference snapshots of decommissioned instances. Previously, IDERA SQL Secure removed permissions data for a server when it is removed from auditing. The only way to save the permissions and snapshot information for that instance was to back up the repository before decommissioning.
Supports TLS 1.2
IDERA SQL Secure 3.1.200 includes support for Transport Layer Security (TLS) version 1.2. The TLS protocol provides encryption, authentication, and data privacy and integrity when transferring information over a network, including VPN, VOIP, and instant messaging.
...
- This release fixes an issue causing the SQL Secure Risk Assessment Comparison Report to show changes between snapshots when no changes actually occurred.
- Users now can remove a server instance without first removing it from an assessment or draft. If any assessment data exists, the user is asked whether they want to remove the server from all active assessments as well. If If Yes, the assessment is kept intact while the instance is deleted. If If No, the server is removed from the assessment as well.
- The The SQL Server SYSADMIN Accounts security security check now reports an accurate status instead of always reporting reporting OK and and not displaying any accounts. This metric did and continues to report correctly in a snapshot.
- Resolved an issue that caused the following error while processing a security check when when Database roles and members is is enabled: "Error 515 encountered on line xxxx: Cannot insert the value NULL into column 'usertype', table '@DatabaseRoleUsers'; column does not allow nulls. INSERT fails."
- This release fixes an error regarding SQL Server 2014 and SQL Server 2016 accounts in the the Unauthorized Account security security check. Previously, the Unauthorized Account security check for SQL Server 2014 initially reported, "No issues found." Then, when a SQL Server 2016 server was added, it listed the unauthorized accounts in the result. However, when going back to the SQL Server 2014 server, it displayed the same unauthorized accounts results that the SQL Server 2016 server revealed.
- Resolved an issue causing the error message,"Cannot insert duplicate key in object 'dbo.<servername>'. The duplicate key value is (1281, 327). The statement has been terminated." when attempting to create a snapshot.
- Changed the Unauthorized Account Check wording from, "Specify the unauthorized accounts," to "Specify the authorized accounts," in the description for the the Criteria entry entry on the Policy Properties page and on the edit Values for Security Check window.
- When a user registers a virtual server that is part of a failover cluster, the name now correctly resolves to the cluster name.
- Resolved an issue with the the Database roles and members and the and the Server roles and members security security checks that caused metrics to provide details from other instances/databases.
- The GUI on the final screen of the SQL Secure Setup Wizard was updated to resolve the cut-off content of the descriptive text.
- The The Launch SQL Secure Console is is now enabled after a new installation or upgrade.
- The uninstallation wizard is updated to no longer show an incorrect final window.
- The copyright year is now correct throughout the product.
- The descriptive text within the the Row-Level Security check check is changed from, "... is configured for specific specific databases ..." to, "... is configured for specific specific tables ...".
- The descriptive text within the the Dynamic Data Masking security security check is changed from, "... is configured for specific specific databases ..." to, "... is configured for specific specific columns ...".
3.1 New features
Supports auditing of Azure SQL Database and SQL Server running in Azure virtual machines
...
The new Suspect SQL Logins report displays all of the suspect SQL Server Accounts that do not have any assigned permissions, i.e. databases, objects, or server files. For more information about reporting, see Report on SQL Server SQL Server Security.
Expanded Risk Assessment reporting
...
For more information about using reports within IDERA SQL Secure, see Report on SQL Server SQL Server Security.
3.0 Fixed issues
The following issues are fixed in IDERA SQL Secure:
...