Bulk Ignoring Issues
You can now select more than one issue in the Issues tab, allowing you to ignore multiple issues in a single action. You can multi-select using the checkboxes which appear on hover, or by using the familiar CTRL-click (or ⌘-click) and SHIFT-click interactions.
In the future, you will be able to fix issues in bulk as well.
Filter Facet Counts
You now see the number of issues that match each filter value (aka facet) shown in the Issues tab. These counts will update to reflect the number of issues that match the current filters applied. You can use these counts as guidance when drilling down into issues from this view.
Sensitive Content Match Viewer
Details about sensitive content matches within a file can now be reviewed by choosing View Matches in the folder details dialog. Each match is highlighted, along with the text surrounding the match to provide more context. You can easily switch between different versions of the file in this viewer, allowing you to identify at what point in time sensitive content was introduced to the file.
Custom Content Classification Policies
In addition to the built-in Regulatory Compliance policies, you can now create your own custom content classification policies. When creating a custom policy, you can select which pattern sets, such as Personally Identifiable Information (PII), that you want to look for in your files. Any matching files will be marked with the tag you specify for the policy.
Sensitive Content Filter
Issues can now be filtered based on whether they impact files containing sensitive information. Within the Issues tab, you can choose to show only issues that relate to files with PII, for instance. In combination with the severity filter, this allows you to focus on key issues first.
Individual Permission Rule
If you follow best practice and assign permissions within your repositories strictly to groups rather than to individual users, you can use the new Individual Permission rule to spot any places where this practice is violated. If enabled, any item with permissions assigned to individual users will be flagged.
Note that this rule is disabled by default because it would generate spurious results if you assign individual permissions as a common practice. You can enable it from the detail view for a given content source.