This build of IDERA SQL Secure includes many fixed issues, including the following previous updates.
4.3 New features
- SQL Secure allows you to schedule snapshots at the policy level, which lets you apply them to multiple instances.
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 . |
- The Suspect SQL Logins report now includes 'Enforce Password Policy" and 'Enforce Password Expiration' information.
- The Database Roles report now has an Only active employees filter that allows selecting Active, Disabled, or All AD accounts.
4.3 Fixed issues
The Suspect SQL Logins report correctly lists SQL accounts avoiding Windows NT accounts.
SQL Secure improved Snapshots performance for large databases.
Fixed an issue when performing a snapshot comparison containing certificate changes.
SQL Secure now shows the correct values for CLR SAFE_ACCESS and CLR Enabled security checks.
SQL Secure 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
- SQL Secure now allows you to take a snapshot of all registered servers in a policy. Snapshots can also be scheduled at the policy level
- The Server Roles report now shows members from Windows groups.
- The Database Roles report now displays the creation date of the database.
4.2 Fixed issues
- SQL Secure successfully monitors a set of databases after taking a snapshot, avoiding the "Some databases were unavailable for auditing" warning.
- SQL Secure now correctly labels log-shipped databases in standby/read-only recovery as "Databases Files" when running a snapshot.
- Collation settings no longer cause a conflict between the audited server and what it is expecting to match.
- "Backups compliance with RTO and RPO requirements" security check includes non-system databases that never had a backup, excluding system databases.
- 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.
- Database Roles report now shows results in Alphabetical order.
- The Database Roles report now allows a filter on active and inactive AD accounts.
- SQL Secure correctly reports "SQL Server Database Level Encryption" security check for Azure SQL Databases.
4.1 New features
- The Configuration Security Checks now allow 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.
...
- When exporting a Policy, SQL Secure no longer checks all the checkboxes by default. It only keeps the enabled ones of the exported policy.
- 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.
- When the sa login is renamed and disabled, SQL Secure reports a Warning level risk finding.
- SQL Secure no longer displays Orphaned Users check findings when database users are mapped to certificates.
- Now the Risk Assessment Report correctly reports the sa account status when it is disabled.
- The Risk Assessment Report correctly reports when the sa account does not exist on the server.
- Now SQL Secure Grooming Job runs correctly and as expected.
...
- SQL Secure enhanced the assessmentsassessment'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 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.
...
- 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.
Scroll pdf ignore |
---|
Excerpt |
---|
Newtabfooter |
---|
alias | IDERA |
---|
url | http://www.idera.com |
---|
| | Newtabfooter |
---|
alias | Products |
---|
url | https://www.idera.com/productssolutions/sqlserver |
---|
| | Newtabfooter |
---|
alias | Purchase |
---|
url | https://www.idera.com/buynow/onlinestore |
---|
| | Newtabfooter |
---|
alias | Support |
---|
url | https://idera.secure.force.com/ |
---|
| | Newtabfooter |
---|
alias | Community |
---|
url | http://community.idera.com |
---|
| | Newtabfooter |
---|
alias | Resources |
---|
url | http://www.idera.com/resourcecentral |
---|
| | Newtabfooter |
---|
alias | About Us |
---|
url | http://www.idera.com/about/aboutus |
---|
| | Newtabfooter |
---|
alias | Legal |
---|
url | https://www.idera.com/legal/termsofuse |
---|
|
|
|
...