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

4.0 New features

• The SQL Secure Data Collector Job Keys allow you to manage snapshot collection jobs. Use this option to throttle the collector jobs so that they do not overload the SQL Server instance.
• SQL Secure supports TLS 1.2 to send email requests to SMTP.

4.0 Fixed issues

• SQL Secure enhanced the assessment'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 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.

3.4.1 Fixed issues

• The time to keep snapshots before letting them be groomed is no longer set by default to one day when importing files in CSV format.
• The User Permission report is no longer showing errors in the db_role information.
•  The User Permissions report shows all schema-level permissions data. The Object Type filter is no longer generating blank spaces after any object type name.
•  You can access registry key information and the SQL Server install folder with Local Administrador and Sysadmin permissions. The Snapshot collection is no longer displaying warning messages caused by permissions on the SQL Server instance.
• "Orphaned Users" security check is no longer identifying users without matching logins as orphan users.

• The All User Permissions report now allows you to expand or collapse results upon report execution. When the report has many permission results, displaying the results collapsed will allow the report to complete execution faster while permissions can be expanded and explored for each audited database.
• Generating the Database Roles report is no longer causing a "maximum recursion" error message.

• SQL Secure fixed the "Is the SQL Server sa account enabled" security check to have a passed status when the finding is "The sa account is not enabled".

3.4 New features

• SQL Secure adds a DISA-NIST STIG policy and security check templates for SQL Server 2016, with 11 security checks enabled by default.
• An additional policy field filtering option was implemented in the Assessment Comparison report.

3.4 Fixed issues

• The error message where "SQL Secure was unable to acquire a valid key" is no longer displayed while trying to take snapshots after decommissioning some servers.
• The SQL Mail or Database Mail Enabled security check now is working as expected.
• Addressed several areas causing poor performance and usability in the user permissions report with significant success.
• Streamlined workflow for the snapshot data collection operation.

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 the Operating system matches 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.2 includes the following New Security Templates:

• Center for Internet Security (CIS) for SQL Server 2008 R2, 2014, and 2016.
  

• Defense Information Systems Agency (DISA) & National Institute of Standards and Technology (NIST) for SQL Server 2012 and 2014.
  

• Sarbanes-Oxley Act, Section 404 (SOX 404).
  
• North American Electric Reliability Corporation (NERC).

Security Templates Updates

On this release IDERA SQL Secure updates the following Security templates:

• Center for Internet Security (CIS) in 2008 and 2012.

• Payment Card Industry Data Security Standard (PCI-DSS).

New Configuration Checks

IDERA SQL Secure 3.2 adds the following configuration checks:

• Hidden Instance Option is Set

• Auto Close Set for Contained Databases

• Max Number of Concurrent Sessions

• Backups Must Be in Compliance with RTO and RPO Requirements

• Shutdown SQL Server on Trace Failure

• Ad Hoc Distributed Queries Enabled

New Access Checks

IDERA SQL Secure 3.2 adds the following access checks:

• Asymmetric Key Size
• Database Master Key Encrypted by Service Master Key
• SQL Server Database Level Encryption
• Appropriate Cryptographic Modules Have Been Used to Encrypt Data
• Database Master Keys Encrypted by Password
• Symmetric Keys Not Encrypted with a Certificate
• Implement Cell Level Encryption
  

New Auditing Checks

IDERA SQL Secure 3.2 adds the following auditing checks:

• SQL Server Audit is Configured for Logins
• DISA Audit Configuration

• Implement Change Data Capture

New Login Checks

IDERA SQL Secure 3.2 adds the following login checks:

• SQL Logins Not Using Must Change

New Permissions Checks

IDERA SQL Secure 3.2 adds the following permissions checks:

• Limit propagation of access rights

• Direct access permissions

Supports SQL Server 2017

IDERA SQL Secure 3.2 now supports the repository and a monitored server of SQL Server 2017 on Windows.

3.2 Fixed issues

• This version of SQL Secure improves the execution time of the Snapshot Comparison Report, making it able to display large datasets.
• Time out error is no longer displayed on the User Permissions Report when the report was running for 80+ databases. In addition, users can export the report to CSV format.
• Users now are able to filter for specific databases in the Database Roles Report.
• Increased Excel Report Export capability to support reports with more than 65,000 rows of data.
  
• This release improves Risk Assessment performance, which now is able to process policy information.
• This release updates the console installation to use the existing repository.
• Users can configure STMP for SQL Secure mail server.
• Users can choose to monitor Always On Availability Group by registering the listener or individual nodes. Take into account there may be some gaps if you register using the listener.
• Under Security Report Card users are able to see Logins Information with Windows Accounts Details for the Suspect Logins Security Check.
• The Integration Services Running security check now is updated depending on the integration service status.
  
• The Details Reports for SQL Server 2000 show database roles and members, it was previously not available for this version.
• Updated SQL Secure version for the deployed report target folder for SSRS reports.
• Users need to restart the application to update the SQL Secure Repository Connection Status after adding a new license in the SQL Secure Manage License section.

• SQL Secure now supports international date time format.

• The Integration Services Login Account Not Acceptable Security Check is no longer showing incorrect data for azure databases.
  

3.1.200 New features

Allows reference to decommissioned server instance snapshots

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.

Includes new product versioning (x.x.x.x)

For internal tracking reasons, this release of IDERA SQL Secure includes an updated product versioning format from three to four parts. For example, the previous version of SQL Secure was version 3.1.0 (x.x.x) and this release is 3.1.200.x (x.x.x.x).

3.1.200 Fixed issues

• 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 Yes, the assessment is kept intact while the instance is deleted. If No, the server is removed from the assessment as well.
• The SQL Server SYSADMIN Accounts security check now reports an accurate status instead of always reporting OK 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 Database roles and members is enabled: "Error 515 encountered online 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 Unauthorized Account 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 account 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 Criteria 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 Database roles and members and the Server roles and members 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 Launch SQL Secure Console 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 Row-Level Security check is changed from, "... is configured for specific databases ..." to, "... is configured for specific tables ...".
• The descriptive text within the Dynamic Data Masking security check is changed from, "... is configured for specific databases ..." to, "... is configured for specific columns ...".

3.1 New features

Supports auditing of Azure SQL Database and SQL Server running in Azure virtual machines

IDERA SQL Secure 3.1 offers cloud-specific capabilities for Azure-hosted SQL Server databases, including:

• Azure SQL Database and SQL Server running on Azure Virtual Machines (VMs).
• Security audits on Azure SQL Database instances and Azure Active Directory.
• Connecting to fully-qualified domain names for Azure VMs and Azure SQL Database instances as registered servers.

Expands installation options

IDERA SQL Secure 3.1 includes expanded installation options to support hybrid cloud environments.

Expands Security Check coverage

This release expands Security Check coverage for data protection, encryption, and firewall rules for the SQL Server platform, including Always Encrypted and Transparent Data Encryption.

Moved to the Windows .NET 4.6 framework

IDERA SQL Secure 3.1 supports Microsoft Windows operating systems using .NET 4.6. For more information about requirements, see Product requirements.

3.1 Fixed issues

There are no fixed issues in this release.

3.0 New features

Added SQL Server file import

Users now can import a .csv file containing the SQL Servers they want to import for registration in IDERA SQL Secure. This is an important feature for environments having more than a few SQL Servers as it allows you to bulk import data into IDERA SQL Secure. For more information about this feature, see Import SQL Server instances.

Added tags for easier server management

IDERA SQL Secure now features server group tags to allow you to more easily manage your SQL Server instance snapshots. You can select tags when registering a SQL Server or simply add a tag to your existing instances. Tags allow you to select a specific group of SQL Servers rather than selecting servers one by one. For more information about server group tags, see Manage server group tags.

Added suspect SQL Server logins report

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 Security.

Expanded Risk Assessment reporting

IDERA SQL Secure 3.0 includes multiple additions and modifications to the existing Security Checks in the Risk Assessment report. These new checks include:

• Access
  • Files on Drive Using Not Using NTFS. Updated to support ReFS for SQL Server 2016.
  • Supported Operating Systems. Removed support for Microsoft Windows 2003 and added support for Windows 2012, Windows 2012 R2, and Windows 2016.
  • SQL Jobs and Agent. Updated to flag any case where a proxy account is not in use.
  • Encryption Methods. Updated to flag any case where unsupported encryption methods are in use. Note that beginning with SQL Server 2016, all algorithms other than AES_128, AES_192, and AES_256 are deprecated.
  • Certificate private keys were never exported. Verifies that Certificate private keys are exported.
• Configuration
  • Linked Server. Checks to see if there are linked servers, and then checks to see if the linked server is running as a member of the sysadmin group. Linked servers can lead to performance issues and running them using sysadmin privileges can leave a database vulnerable to corruption.
  • SQL Server Version. Checks to make sure a supported version of SQL Server is in use. Flags any case where an unsupported SQL Server version is in use.
  • Full-Text Search Service Running. Checks to make sure that this service is running on the selected instance.
  • Unauthorized Accounts Check. Updated to include checks for roles beyond sysadmin, including the Separation of Duties roles in SQL Server 2014 and the roles surrounding encryption for SQL Server 2016.
  • Other General Domain Accounts Check. Update to include checks for general domain accounts such as domain Users, Everyone, and Authenticated Users added to the selected instance.
• Surface
  • SQL Server Available for Browsing. Updated the name of this check to SQL Server Browser Running.

For more information about using reports within IDERA SQL Secure, see Report on SQL Server Security.

3.0 Fixed issues

The following issues are fixed in IDERA SQL Secure:

• Resolved an issue that occurred when trying to register a SQL Server instance, which is clustered and using AlwaysOn Availability Groups. The system tried to register the Cluster Server Name instead of the SQL Server Instance Name.
• Resolved an issue that caused SQL Server administrator accounts to show sysadmin accounts for other servers in the Server Security Report Card.
• IDERA SQL Secure no longer incorrectly pulls database role information from SQL Server 2000 databases.
• Users no longer receive false warning messages when running a snapshot.
• Resolved an issue that caused the system to display authorized accounts as unauthorized when a wildcard was included in the list of authorized accounts in Unauthorized Accounts Are Sysadmins.