Page History
IDERA IDERA SQL Secure provides the following new features and fixed issues.
...
4.
...
4 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 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 form 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 reports 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 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. 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 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 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
SQL Secure 2.9 now can enumerate users within a group when the target server is in an environment when 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:
- SQL Secure 2.9 fixes an issue causing 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.
| Excerpt |
|---|
SQL Secure tells you who has access to what on your SQL Server databases. Learn more > > |
The Snapshot Comparison report settings now include a checkbox that allows the report to show the object comparison based on:Anchor SQLSECU-2907 SQLSECU-2907 - Current logic.
- Updated logic to ignore restored objects that are identical to the previous snapshot.
The Snapshot Comparison report now shows a more detailed view of the user level access changes that occurred between two different snapshots.Anchor SQLSECU-2190 SQLSECU-2190
4.4 Fixed issues
The Snapshot May Be Missing Data security check was incorrectly reported for SQL Server 2016 and SQL Server 2017. This is now fixed.Anchor SQLSECU-2799 SQLSECU-2799
...