Page History

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

...

4.

...

3 New features

• Anchor
  SQLSECU-

  2759

  2754 SQLSECU-

  2759

  2754

  SQL Secure allows you to schedule snapshots at the policy level, which lets you apply them to multiple instancesThe time to keep snapshots before letting them be groomed is no longer set by default to one day when importing files in CSV format.

• Anchor
  SQLSECU-

  2758

  2638 SQLSECU-

  2758The User Permission report is no longer showing errors in the db_role information

  2638

  SQL Secure allows you to add system-supplied or user-specified certificates to the whitelist for the Certificate private key were never exported security check
  

  Note
  The whitelist is already populated with the Microsoft certificates marked with NO-PRIVATE-KEY .

• Anchor
  SQLSECU-

  2757

  2091 SQLSECU-

  2757

  2091

   The User Permissions report shows all schema level permissions data. The Object Type filter is no longer generating blank spaces after any object type nameSuspect SQL Logins report now includes 'Enforce Password Policy" and 'Enforce Password Expiration' information.

• Anchor
  SQLSECU-

  2744

  2842 SQLSECU-

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

  2842

  The Database Roles report now has an Only active employees filter that allows selecting Active, Disabled, or All AD accounts.

4.3 Fixed issues

• Anchor
  SQLSECU-

  2735

  2816 SQLSECU-

  2735"Orphaned users" security check is no longer identifying users without matching logins as orphan users

  2816

  The Suspect SQL Logins report correctly lists SQL accounts avoiding Windows NT accounts.

• Anchor
  SQLSECU-

  2678

  2871 SQLSECU-

  2678The 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.

  2871

  SQL Secure improved Snapshots performance for large databases.

• Anchor
  SQLSECU-

  2676

  2874 SQLSECU-

  2676Generating the Database Roles report is no longer causing a "maximum recursion" error message

  2874

  Fixed an issue when performing a snapshot comparison containing certificate changes.

• Anchor
  SQLSECU-

  2608

  2869 SQLSECU-

  2608

  2869

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

...

• now shows the correct values for CLR SAFE_ACCESS and CLR Enabled security checks.

• Anchor
  SQLSECU-

  2687

  2806 SQLSECU-

  2687

  2806

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

...

• now contains the CIS for SQL Server 2022 benchmark. All other CIS benchmarks have been updated to their most recent available benchmark version.

4.2 New features

• Anchor
  SQLSECU-2679215 SQLSECU-2679215

  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.now allows you to take a snapshot of all registered servers in a policy. Snapshots can also be scheduled at the policy level

• Anchor
  SQLSECU-26882655 SQLSECU-26882655

  The SQL Mail or Database Mail Enabled security check now is working as expectedServer Roles report now shows members from Windows groups.

• Anchor
  SQLSECU-26891242 SQLSECU-2689

  Addressed several areas causing poor performance and usability in the user permissions report with significant success. AnchorSQLSECU-2711SQLSECU-2711 Streamlined workflow for the snapshot data collection operation.

...

• 1242

  The Database Roles report now displays the creation date of the database.

4.2 Fixed issues

• Anchor
  SQLSECU-27022833 SQLSECU-2702
  Anchor
  2833

  SQL Secure successfully monitors a set of databases after taking a snapshot, avoiding the "Some databases were unavailable for auditing" warning.
• SQLSECU-2685

  SQLSECU-2703	SQLSECU-2703
  Anchor
  SQLSECU-26452831 SQLSECU-2645
  Anchor
  SQLSECU-2685
  2831

  SQL Secure now correctly labels log-shipped databases in standby/read-only recovery as "Databases Files" when running a snapshot.

• Anchor
  SQLSECU-26772811 SQLSECU-2677

  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

2811

Collation settings no longer cause a conflict between the audited server and what it is expecting to match.

• Anchor
  SQLSECU-2820 SQLSECU-2820

  "Backups compliance with RTO and RPO requirements" security check includes non-system databases that never had a backup, excluding system databases.

• Anchor
  SQLSECU-2823 SQLSECU-2823

  Latest SQL Secure version no longer supports SQL Server 2000 and SQL Server 2005, a workaround is to install Secure on a SQL instance with a different collation.

• Anchor
  SQLSECU-2764 SQLSECU-2764

  Database Roles report now shows results in Alphabetical order.

• Anchor
  SQLSECU-2821 SQLSECU-2821

  The Database Roles report now allows a filter on active and inactive AD accounts.

• Anchor
  SQLSECU-26862798 SQLSECU-26862798

  SQL Secure adds policy templates: CIS for SQL Server 2017 and SQL Server 2019.

...

• correctly reports "SQL Server Database Level Encryption" security check for Azure SQL Databases.

4.1 New features

• Anchor
  SQLSECU-25442639 SQLSECU-2544

  The CIS for SQL Server 2016 policy lists all the corresponding security checks. AnchorSQLSECU-2486SQLSECU-2486

  2639

  The Configuration Security Checks  now allows you to configure your Backups compliance more freely with the Backups compliance with RTO and RPO requirements check . Now, you can set up the backup frequency and select the databases to backup.

4.1 Fixed issues

• Anchor
  SQLSECU-2664 SQLSECU-2664

  When exporting a Policy, SQL Secure no longer checks all the checkboxes by default. It only keeps the enabled ones of the exported policySnapshot comparison report doesn't show server role change.

• Anchor
  SQLSECU-7232760 SQLSECU-7232760

  Exporting the User Permission Report is working as expected.

...

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

• Anchor
  SQLSECU-

  2649

  2772 SQLSECU-

  2649The Operating System Security Check no longer generates risks when the Operating system matches the details

  2772

  When the sa login is renamed and disabled, SQL Secure reports a Warning level risk finding.

• Anchor
  SQLSECU-

  2648

  2782 SQLSECU-

  2648Unauthorized Account Security Check is no longer displaying inconsistent results and details

  2782

  SQL Secure no longer displays Orphaned Users check findings when database users are mapped to certificates.

• Anchor
  SQLSECU-

  2622

  2771 SQLSECU-

  2622

  2771

  Now the Risk Assessment Report correctly reports the sa account status when it is disabled.

• Anchor
  SQLSECU-

  2656

  2773 SQLSECU-

  2656SQL Secure improved its performance significantly decreasing report generation times

  2773

  The Risk Assessment Report correctly reports when the sa account does not exist on the server.

• Anchor
  SQLSECU-

  2486

  2801 SQLSECU-

  2486

  2801

  Now SQL Secure Grooming Job runs correctly and as expected.

4.0 New features

• Anchor
  SQLSECU-20662783 SQLSECU-2066

  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.

• 2783

  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.

• Anchor
  SQLSECU-2763 SQLSECU-2763

  SQL Secure supports TLS 1.2 to send email requests to SMTP.

4.0

...

Fixed issues

• Anchor
  SQLSECU-

  2309

  2704 SQLSECU-

  2309

  2704

  SQL Secure is no longer having issues with expired Licensesenhanced the assessment's loading time; they no longer take several minutes to display information.

• Anchor
  SQLSECU-22692778 SQLSECU-2269

  SQL Secure Grooming Job is no longer failing while classifying errors from warnings

  2778

  Snapshot collection on Availability Group Nodes no longer generates a file permissions warning message.
  

• Anchor
  SQLSECU-22442779 SQLSECU-2244

  The Unauthorized Account Check security check is not returning findings on SQL Server 2008 R2, it works with SQL Server 2016 and above

  2779

  Snapshot collection completes successfully for a log-shipped database.

• Anchor
  SQLSECU-22232716 SQLSECU-2223

  The explanation notes functionality is working for all security checks

  2716

   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.

• Anchor
  SQLSECU-21512777 SQLSECU-2151

  The uninstallation process completes removing all SQL Secure files. AnchorSQLSECU-2089SQLSECU-2089SQL Secure reports show Snapshot missing data when all Sequence Objects are included in the filter

  2777

  SQL Secure no longer displays timeout errors while generating the Database Roles Reports.

• Anchor
  SQLSECU-20832781 SQLSECU-2083

  The Snapshot Data Collection process for Windows Server 2016 is no longer showing incorrect warnings

  2781

  Renaming and disabling sa login account no longer shows a "sa Account Not Disabled" security check.

• Anchor
  SQLSECU-20742780 SQLSECU-2074

  TracerX-Viewer.application no longer requires to upgrade the .NET version.

  2780

  "Public Server Role only granted default Microsoft permissions" security check shows the correct information related to Server Roles

• Anchor
  SQLSECU-20642589 SQLSECU-2064

  SQL Secure includes the option to add new servers to Server Group Tags

  2589

  The Snapshot Comparison Report no longer displays server changes when no changes have been made.

• Anchor
  SQLSECU-20372774 SQLSECU-20372774

  The Risk Assessment Report includes the Show Risk Only optionUser Permission Report works correctly with different collations sets.

• Anchor
  SQLSECU-2122762 SQLSECU-212

  HIPAA policy now includes msdb database as default in the criteria

  2762

  SQL Secure imports hidden instances using CSV files.

• Anchor
  SQLSECU-20862788 SQLSECU-2086

  SQL Secure installer includes the Visual C++ 2015 Redistributable.

3.2 New features

• 2788

  Anchor
  SQLSECU-

...

• 2766 SQLSECU-

...

IDERA SQL Secure 3.2 includes the following New Security Templates:

• 2766

  The Snapshot collection process completes successfully for imported instances using CSV files.

• Anchor
  SQLSECU-2771 SQLSECU-2771

  Anchor
  SQLSECU-2766 SQLSECU-2766

  The Risk Assessment Report no longer reports the sa login account incorrectly

• 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).

• Anchor
  SQLSECU-

...

• 2793 SQLSECU-

...

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

• 2793

  SQL Secure no longer has issues with bulk email notification settings.

• Anchor
  SQLSECU-2772 SQLSECU-2772

  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

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

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

• Anchor
  SQLSECU-

...

• 2774 SQLSECU-

...

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

...

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
  

...

IDERA SQL Secure 3.2 adds the following auditing checks:

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

• Implement Change Data Capture

...

IDERA SQL Secure 3.2 adds the following login checks:

• SQL Logins Not Using Must Change

...

IDERA SQL Secure 3.2 adds the following permissions checks:

• Limit propagation of access rights

• Direct access permissions

...

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

3.2 Fixed issues

...

3.1.200 New features

...

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.

...

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.

...

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

...

• 2774

  SQL Secure enhanced the SQL Job Permission security check.

3.4.1 Fixed issues

• Anchor
  SQLSECU-2759 SQLSECU-2759

  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.

• Anchor
  SQLSECU-2758 SQLSECU-2758

  The User Permission report is no longer showing errors in the db_role information.

• Anchor
  SQLSECU-2757 SQLSECU-2757

   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.

• Anchor
  SQLSECU-2744 SQLSECU-2744

   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.

• Anchor
  SQLSECU-2735 SQLSECU-2735

  "Orphaned Users" security check is no longer identifying users without matching logins as orphan users.

• Anchor
  SQLSECU-2678 SQLSECU-2678

  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.

• Anchor
  SQLSECU-2676 SQLSECU-2676

  Generating the Database Roles report is no longer causing a "maximum recursion" error message.

• Anchor
  SQLSECU-2608 SQLSECU-2608

  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

• Anchor
  SQLSECU-2687 SQLSECU-2687

  SQL Secure adds a DISA-NIST STIG policy and security check templates for SQL Server 2016, with 11 security checks enabled by default.

• Anchor
  SQLSECU-2557 SQLSECU-2557

  An additional policy field filtering option was implemented in the Assessment Comparison report.

3.4 Fixed issues

• Anchor
  SQLSECU-2679 SQLSECU-2679

  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.

• Anchor
  SQLSECU-2688 SQLSECU-2688

  The SQL Mail or Database Mail Enabled security check now is working as expected.

• Anchor
  SQLSECU-2689 SQLSECU-2689

  Addressed several areas causing poor performance and usability in the user permissions report with significant success.

• Anchor
  SQLSECU-2711 SQLSECU-2711

  Streamlined workflow for the snapshot data collection operation.

3.3.2 New features

• Anchor
  SQLSECU-2702 SQLSECU-2702

  Anchor
  SQLSECU-2703 SQLSECU-2703

  Anchor
  SQLSECU-2645 SQLSECU-2645

  Anchor
  SQLSECU-2685 SQLSECU-2685

  Anchor
  SQLSECU-2677 SQLSECU-2677

  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.

• Anchor
  SQLSECU-2686 SQLSECU-2686

  SQL Secure adds policy templates: CIS for SQL Server 2017 and SQL Server 2019.

3.3.2 Fixed issues

• Anchor
  SQLSECU-2544 SQLSECU-2544

  The CIS for SQL Server 2016 policy lists all the corresponding security checks.

• Anchor
  SQLSECU-2486 SQLSECU-2486

  Snapshot comparison report doesn't show server role change.

• Anchor
  SQLSECU-723 SQLSECU-723

  Exporting the User Permission Report is working as expected.

3.3.1 Fixed issues

• Anchor
  SQLSECU-2649 SQLSECU-2649

  The Operating System Security Check no longer generates risks when the Operating system matches the details.

• Anchor
  SQLSECU-2648 SQLSECU-2648

  Unauthorized Account Security Check is no longer displaying inconsistent results and details.

• Anchor
  SQLSECU-2622 SQLSECU-2622

  Anchor
  SQLSECU-2656 SQLSECU-2656

  SQL Secure improved its performance significantly decreasing report generation times.

• Anchor
  SQLSECU-2486 SQLSECU-2486

  Anchor
  SQLSECU-2066 SQLSECU-2066

  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

• Anchor
  SQLSECU-2309 SQLSECU-2309

  SQL Secure is no longer having issues with expired Licenses.

• Anchor
  SQLSECU-2269 SQLSECU-2269

  SQL Secure Grooming Job is no longer failing while classifying errors from warnings.

• Anchor
  SQLSECU-2244 SQLSECU-2244

  The Unauthorized Account Check security check is not returning findings on SQL Server 2008 R2, it works with SQL Server 2016 and above.

• Anchor
  SQLSECU-2223 SQLSECU-2223

  The explanation notes functionality is working for all security checks.

• Anchor
  SQLSECU-2151 SQLSECU-2151

  The uninstallation process completes removing all SQL Secure files.

• Anchor
  SQLSECU-2089 SQLSECU-2089

  SQL Secure reports show Snapshot missing data when all Sequence Objects are included in the filter.

• Anchor
  SQLSECU-2083 SQLSECU-2083

  The Snapshot Data Collection process for Windows Server 2016 is no longer showing incorrect warnings.

• Anchor
  SQLSECU-2074 SQLSECU-2074

  TracerX-Viewer.application no longer requires to upgrade the .NET version.

• Anchor
  SQLSECU-2064 SQLSECU-2064

  SQL Secure includes the option to add new servers to Server Group Tags.

• Anchor
  SQLSECU-2037 SQLSECU-2037

  The Risk Assessment Report includes the Show Risk Only option.

• Anchor
  SQLSECU-212 SQLSECU-212

  HIPAA policy now includes msdb database as default in the criteria.

• Anchor
  SQLSECU-2086 SQLSECU-2086

  SQL Secure installer includes the Visual C++ 2015 Redistributable.

3.2 New features

Anchor
SQLSECU-Req SQLSECU-Req

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

Anchor
SQLSECU-Req SQLSECU-Req

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

Anchor
SQLSECU-Req SQLSECU-Req

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

Anchor
SQLSECU-Req SQLSECU-Req

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
  

Anchor
SQLSECU-Req SQLSECU-Req

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

Anchor
SQLSECU-Req SQLSECU-Req

New Login Checks

IDERA SQL Secure 3.2 adds the following login checks:

• SQL Logins Not Using Must Change

Anchor
SQLSECU-Req SQLSECU-Req

New Permissions Checks

IDERA SQL Secure 3.2 adds the following permissions checks:

• Limit propagation of access rights

• Direct access permissions

Anchor
SQLSECU-Req SQLSECU-Req

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

• Anchor
  SQLSECU-720 SQLSECU-720

  This version of SQL Secure improves the execution time of the Snapshot Comparison Report, making it able to display large datasets.

• Anchor
  SQLSECU-745 SQLSECU-745

  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.

• Anchor
  SQLSECU-1503 SQLSECU-1503

  Users now are able to filter for specific databases in the Database Roles Report.

• Anchor
  SQLSECU-1177 SQLSECU-1177

  Increased Excel Report Export capability to support reports with more than 65,000 rows of data.
  

• Anchor
  SQLSECU-750 SQLSECU-750

  This release improves Risk Assessment performance, which now is able to process policy information.

• Anchor
  SQLSECU-1216 SQLSECU-1216

  This release updates the console installation to use the existing repository.

• Anchor
  SQLSECU-1329 SQLSECU-1329

  Users can configure STMP for SQL Secure mail server.

• Anchor
  SQLSECU-1501 SQLSECU-1501

  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.

• Anchor
  SQLSECU-1522 SQLSECU-1522

  Under Security Report Card users are able to see Logins Information with Windows Accounts Details for the Suspect Logins Security Check.

• Anchor
  SQLSECU-2055 SQLSECU-2055

  The Integration Services Running security check now is updated depending on the integration service status.
  

• Anchor
  SQLSECU-2053 SQLSECU-2053

  The Details Reports for SQL Server 2000 show database roles and members, it was previously not available for this version.

• Anchor
  SQLSECU-1542 SQLSECU-1542

  Updated SQL Secure version for the deployed report target folder for SSRS reports.

• Anchor
  SQLSECU-1765 SQLSECU-1765

  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.

• Anchor
  SQLSECU-2022 SQLSECU-2022

  SQL Secure now supports international date time format.

• Anchor
  SQLSECU-2056 SQLSECU-2056

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

  Anchor
  SQLSECU-2056 SQLSECU-2056

...

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:

...

2.9 New features

Improved Name Matches selection of rule filter properties

IDERA SQL Secure 2.9 simplifies the process for selecting a named variable when setting filter properties. Click Any in the Name Matches column of the Filter Properties dialog box, and IDERA SQL Secure displays a dialog box that allows you to see a list of available elements and a list of selected elements, and easily move the databases, tables, views, or functions between the two lists.

The list is populated based on the row where you click Any, i.e. if you click to select items from the Tables where row, the list displays only tables. To select more than one element at a time, press and hold the Shift key to click the first and last element in a series or press Ctrl and then click each element, not in a series. Click Add to move elements from the Available list to the Selected list. Click Remove to move elements from the Selected list to the Available list. Search functionality also is available in this dialog box. Note that you can use wildcards when entering a search string. For more information about using Filter Properties, see Edit filter settings.

Enhanced reporting

Expanded some reports to show users within groups

The User Permissions, All User Permissions, and Database Roles report now provide an option to view access at the user level within a group. The new Level field in the report filter allows you to select Member to display access results at the group (member) level or select User to display access results that show individual user account names within the group as well as whether the account is enabled. For more information about using reports within IDERA SQL Secure, see Report on SQL Server Security.

Additional enhancements to the All User Permissions report

While the All User Permissions report now includes user-level information, it also includes updates that allow you to run the report for one or more specific databases. The All User Permissions report displays user permissions at the object level. IDERA SQL Secure 2.9 includes a new Database field and corresponding All Databases check box that allows you to enter specific databases to include in the report, or check the box to include all databases within the selected SQL Server.

Clear the All Databases check box to enable the selection of one or more databases in the displayed list. To select more than one database at a time, press and hold the Shift key to click the first and last databases in a series or press Ctrl and then click each database, not in a series. For more information about using reports within IDERA SQL Secure, see Report on SQL Server Security.

Supports SQL Server 2016

IDERA SQL Secure 2.9 and later support SQL Server 2016 for the repository and audited instances. For more information about supported platforms, see Product requirements.

Enumerates group members in a one-way trust

IDERA SQL Secure 2.9 now can enumerate users within a group when the target server is in an environment when IDERA SQL Secure is across domains configured as a one-way trust.

Updates Guest User Enabled Access functionality

The Guest User Enabled Access check now includes msdb, master, and tempdb in the Approved user access list for all default templates.

2.9 Fixed issues

The following issues are fixed in IDERA SQL Secure:

• IDERA SQL Secure 2.9 fixes an issue causing IDERA SQL Secure to incorrectly report some servers as failing the Login Audit Level security check.
• An issue that triggered an email notification after data collection that stated that suspect windows were encountered no longer occurs.

2.8 New features

• IDERA SQL Secure now supports SQL Server 2014
• IDERA SQL Secure now supports Always On Availability Groups
• IDERA SQL Secure now allows you to install the SQL Secure Repository on a failover cluster. The installer provides an option to select the Cluster installation and specify a cluster node.
• Policy Templates have been updated to use the latest versions of SQL Server and OS:

• • Updated to policy templates:
    
    • CIS v 2.0 for SQL Server 2005 (from version 1.2)
    • PCI-DSS v 3.0 Guidelines for SQL Server (from version 2.0)
    • HIPAA Guidelines for SQL Server - updated security checks as needed e.g. Operating System Version
  • Added templates for:
    • CIS v1.1.0 for SQL Server 2008
    • CIS v1.0.0 for SQL Server 2012
    • MS Best Practices Analyzer for 2008
    • MS Best Practices Analyzer for 2012
• This version had updated to a granular process for Exporting and Importing policies, so that authorized SQL Logins can be excluded from exporting, and when imported the active settings for those checks remain unmodified.
• The process for registering new SQL Server instances with IDERA SQL Secure now allows defining folders for file system permissions checks.
• IDERA SQL Secure now supports Sequence Objects for SQL Server 2012.
• IDERA SQL Secure supports users in contained databases for SQL Server 2012 and 2014.
• IDERA SQL Secure now provides the following new Security Checks:
  • Security Check for SQL Server Integration Services (SSIS) to verify if any public or other unauthorized principals have been granted permission to use SSIS stored procedures.
  • Security Check added to level 1 and level 2 policy templates that show risk on systems where permissions have been granted to the public role on objects outside the sys schema in user databases.
  • Security Check: Unacceptable Database Ownership detects if a database is found with an unacceptable owner
  • The Risk Assessment Report has been updated with new nine security checks.

2.8 Fixed issues

Phase-out IDERA SQL Secure Itanium support

IDERA is beginning to phase out all Itanium support in IDERA SQL Secure 2.6 and all subsequent 2.x versions. While 2.8 will continue to operate with Itanium and support is available, IDERA SQL Secure 3.0 will not support the Itanium processor architecture. For more information, see the product requirements.

SQL Secure Repository requires SQL Server 2005 or later

When upgrading, migrating, or deploying the SQL Secure Repository for the first time, ensure you select an instance running SQL Server 2005 or later for your target location. SQL Secure no longer supports SQL Server 2000 platform for the SQL Secure Repository.

If you are upgrading from SQL Secure version 2.0 or earlier, you will need to migrate the Repository to a SQL Server 2005 or later instance. For more information, see IDERA Solution 00002617 ("How do I migrate SQL Secure from one server to another?").

Microsoft Reporting Services 2000 is no longer supported

If you are upgrading reports from Microsoft Reporting Services 2000, then upgrade to Microsoft Reporting Services 2005 before installing the new reports in SQL Secure 2.8 to ensure the upgrade is successful.

New credentials may be necessary when upgrading

SQL Secure no longer uses the default credentials of your SQL Server Agent to collect Operating System and SQL Server security information. If in a previously installed version, SQL Secure was configured to use the default SQL Agent credentials to collect security information, a window will open when you first open SQL Secure 2.8, prompting you for new credentials.

Blank password not accepted when registering a SQL Server instance

When registering a new SQL Server instance, blank passwords are not accepted for SQL logins due to the extreme security risk this poses.

SQL Secure can now audit the same cluster node on which it is installed

The SQL Secure now allows you to audit security data from SQL Server instances hosted on the same cluster node that hosts the SQL Secure Collector.

Support for contained database authentication security

SQL Secure now displays information and report on the security settings of database principals used for contained database authentication and connections. Contained databases are a new security feature available in SQL Server 2012.

SQL Secure now collects security data for AlwaysOn Availability Groups

...

...