We want to get the activity reports for specific classification(just like specifying the folder).

We need to audit user activities for confidential files every quarter. Current activity reports can only specify the user, date, folder and action, not classification.

Need the ability to generate a Shield alert when someone copies or moves content from one EID repository to another EID; to include any movement of content via the api.box.com utilizing cURL or other CLI.

When running automated classification, files containing passwords will not be checked for PII information. This means they are potentially at risk of getting shared externally. There should be options to classify them if they are password protected or it should have the option of alerting.

Birthday is not an an InfoType in automated classification. Please add this field.

We want "Smart Access: Download restriction" to control the download/printing capability of G-Suite apps. We want the integration just like office online which restrict download/print on office online apps.

For security perspective, we want to minimize the risk of data breach, so we are planning to store the confidential files on box and restrict the content to be downloaded to the devices. However currently if user opened the files on G-Suite, the files can be downloaded or printed.

Currently, the only apps that can be exempt from an Access Policy are published apps or custom JWT apps that have been approved in the Admin Console. There is a gap for unpublished OAuth apps that may need to be allowlisted from a policy.

In Box Shield Smart Access, if moved from Folder A, which is assigned the [In-House] classification, to Folder B, which is assigned the [Public] classification, Folder A's classification will be inherited.

However, the classification of [In-house] in folder A is not inherited when the copy operation is performed, the [Public] classification assigned to folder B is assigned.
Since the classification is not inherited by the copy operation, this function can be useful to prevent information leakage by implementing this function.

The input fields are not the easiest way to find a value to add to a Shield List. Naming convention is different across systems, so it would be helpful to know the values that are available to be added.

I would like to see the ability to add Shield Classifications per client - with the appropriate access policy (restricting to client email domain) we could avoid any possibility to overshare when inviting the wrong clients into a folder or sharing a shared link - There is a maximum number of classifications of 25 so could this be extended to facilitate this use case/control.

Threat detection at the classification level. Specifically, we would like the ability to monitor suspicious location and/or suspicious download for a particular dataset rather than the entire content population of our account.

To apply or change a classification, select "Owners/co-owners and editors" in the classification settings, and then click Users with editorial privileges or higher can apply and change the classifications.
However, by implementing a feature that allows configuration of permissions to apply and change each classification created, the Security can be enhanced.

As a user in an industry which must be PCI compliant,
I want content flagged by Shield as containing PCI content to not be included in the full-text search index,
So that our Box environment can be PCI compliant without having to disable full text search for the entire environment.

When viewing a folder, it is currently not possible to know if there are files within the folder structure that have a differing classification label from the one at the root level. This "non-compliance" could potentially be problematic, or even a signal that someone has inadvertently changed a classification. It would be nice to have some kind of visual indicator that the top-level classification label is not 100% cascaded throughout the folder/file structure below it in the waterfall.

Currently, the trial mode classification and settings will disappear at the end of the trial period.
If we have a Shield contract, we would like to take over its classification and settings.

By eliminating the need to set them up again in the production environment, we can make a smooth transition.

Isolate the EDIT SHIELD CONFIGURATION co-admin permission to 2 different permissions:

1. View-only detection rules, access policies, lists


2. View, Edit, and Create Detection rules, access policies, and lists.

When viewing the contents of a folder, it would be beneficial to the user experience to see which items are classified and how without needing to select the item or attempt to preview it.

To support ethical walls, it would be advantageous to be able to create lists of email addresses for different teams within the same company so that collaboration and shared link access can be restricted. Example for private side, public side employees within an investment bank content could be classified for each with access controls in place to prevent sharing and collaboration.

We would like to have the ability to search by classification.