Help shape the future of Box
Welcome to Box Pulse, our product feedback tool powered by UserVoice. Got an idea for how to improve Box? Share it with us and gather support or vote on other people's ideas. Your feedback is essential to informing roadmap decisions and shaping the future of our products. Thanks for joining our community!
See user guide here.
185 results found
-
BOX SHIELD - Block all applications from downloading content
The following feature is redundant:
Block all applications from downloading content - No integrated applications (except Microsoft Office for the web, Google Workspace, Apple iWork, and Adobe Acrobat Online) or published custom applications will be able to download content protected by the access policy.
I thought the purpose of Box Shield was to protect organizations from data breaches????
We have configured everything within our box account to prevent certain data from being download or printed. However, Box gives our users the option to open these confidential files in Adobe Acrobat which then allows them to download, print, and anything else…
2 votes -
Can we get another pop-up screen when Deleting a Shield Access policy to make sure that is the action the admin wants to take?
The 'Delete' and the 'Edit' button are right next to each other on the Shield Access Policy page. When clicking 'Delete' the policy automatically deletes. It is easy to accidentally click instead of 'Edit'. Can we get a second window that asks if that is the action the Admin/ Co-Admin wants to take on the policy?
2 votes -
Automatically classify content based off uploader
Automatically classify content based off uploader of document. Use case: anything a legal team member uploads should automatically be classified as confidential
2 votes -
Auto classification of files/folders based on metadata and comments
It would be helpful if Box's auto classification feature were able to trigger file classification (and thus, security controls) if metadata on a file/folder is sensitive in nature or if a file has comments/tasks/annotations that contain sensitive information.
2 votes -
Add a Birthdate / Birth date infotype to Automated Classification
Birthday is not an an InfoType in automated classification. Please add this field.
2 votes -
Add ability to allowlist unpublished apps in a Shield list or Access Policy
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.
2 votes -
File Security Classification, non-compliance label
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.
2 votes -
Be able to Block specific filetypes from being uploaded to Box
Allow for an organization-wide policy to block specific filetypes from being uploaded to Box, or at least prevent them from being uploaded/moved to specific folders with specific classifications.
1 vote -
Allow Shield Location Rule Restriction By Folder
Currently Shield's Location Restriction rule is applied to the entire EID by user/groups. It would be helpful to be able to set this up by specific folder(s) or folder structure.
Ex. Team A is not allowed to view specific content while in Location X, however Team B is able to. Currently the restriction would be set on the EID level and both teams would be under this restriction.
We could exclude group B or other groups from the rule however Group A would still be restricted from accessing other content within the EID.
1 vote -
Make MPIP and Shield Classification Labels Bidirectional
This make require partnership with Microsoft, but it would be ideal if the MPIP integration was bidirectional. For example, if a file in Box doesn't have an MPIP label, but a Shield classification label is applied, the document would have an MPIP label applied based on the mapping table
1 vote -
1 vote
-
Ability to map Box Groups to Information Barrier Segments
The current requirement for uniqueness in Information Barrier segments only allows Box Admins to add individual users to segments, not user groups. This process can increase the long-term maintenance.
Ideally, customers should be able to use attributes from Active Directory that are then synced to Box Groups. Ultimately, the Box Groups would be used to update Information Barrier segment membership automatically. If the group update breaks the requirement that a user can only belong to one segment, Box could produce an error message.
1 vote -
Applying folder exceptions/exclusions to Classification policies
Would like to apply folder exceptions/exclusions to Classification Policies. Currently, we can apply to a selected group of folders, but we have an organizational need to be able to apply a classification policy to all content and add a small selection of folders to exclude from that classification policy.
1 vote -
Additional info in Anomalous Download Shield e-mail notifications
It would be very helpful to see "Previous weekly download amount", "anomalous download amount" and the "delta" on Anomalous download e-mail notifications. We use these to identify notifications that require further investigation, but these are only available by clicking into the reports which make this kind of detection difficult to scale and manage.
1 vote -
File criteria exclusion list for Box Shield classification policies
When setting up classification policies, Omnicell, Inc., would like to be able to create a list of custom terms to exclude, in addition to the existing ability to designate file criteria that will trigger application of a classification label. This would reduce the number of documents that will incorrectly have a classification applied when auto-classification is enabled. For example, Omnicell has a lot of content with dummy PHI in their environment - this content is allowed to be stored in Box and should not be classified; however, they also want to protect actual PHI that may be stored in Box,…
1 vote -
Allow for exceptions on the Download and Print Restriction security control.
Allow for exceptions on the Download and Print Restriction security control.
We want to restrict users from downloading files that have been identified as having PII. However, we would like a mechanism to allow users that have a business reason to download files. Either through a 'User Justification' similar to the 'External Collaborators Restriction' security policy or an approval workflow.
1 vote -
Ability to scope Malicious Content Rules by User/Group/Shield Lists
Currently malicious content rules apply to all users. To test moving from an audit/detection-only stance to enforcement, it would be useful to be able to create multiple rules that are scoped to specific users/groups/Shield Lists.
This will allow us to keep most users in an audit/detection-only rule, while we test enforcement with a pilot group in another rule.1 vote -
Allow groups to be specified as 'notified to' in Box Shield Threat Detection Rules
Only user accounts can be specified for the 'Notification Destination' of the Threat Detection rules in Box Shield.
Since maintenance is required when the person in charge changes, it should be possible to specify a group.■In Japanese：
Box shieldに存在する検出ルールの「通知の送信先」は、ユーザーアカウントのみが指定できます。
担当者が変わったときメンテナンスが必要になるので、グループを指定できるようにしてください。1 vote -
Shield access policy to restrict shared link creation
Have the option to restrict shared link creation with Box Shield access policy
1 vote -
Secure admin only download of 'malicious' files for analysis
Admins should be able to download Box Shield tagged malware without marking the file safe for everyone. That way a security admin could download the file and scan it with their own security tools. That’s the only real way to diagnose if a file is malicious or just a false positive.
Asking us to mark it safe by chatting with the user is far from best practice
1 vote
- Don't see your idea?