Not all locations with sensitive content pose a risk as some of them may be intended to have such content. For example, a Human Resources folder is likely to contain Social Security Numbers of company employees as it is the most relevant location for such content. You can tell Egnyte Protect in advance to permit sensitive content in such locations.
For every Egnyte Connect source, you can specify the folder hierarchies that are permitted to contain certain types of sensitive content.
1) Go to the Content Sources settings page for the Egnyte Connect source and then to the section titled “PERMITTED SENSITIVE CONTENT LOCATIONS”.
2) Click on the button in the section to start permitting sensitive content. You’ll be directed to a pane summarizing the permitted folders in the source. Every active classification policy (both built-in and custom policies) will have a row in this pane, with a summary of folders permitted to contain content matching that policy.
3) Click on a policy’s row to open a dialog for permitting content matching that specific policy. For example, clicking on the GLBA policy’s button will open a dialog to permit GLBA content in the source.
4) Every folder in the dialog has a checkbox next to it, which indicates the permissions for the folder itself to contain sensitive content. For example, the checkbox next to the Accounting folder in the above dialog is checked, implying that the Accounting folder is permitted to directly contain files matching the GLBA policy.
5) Every folder also contains an icon next to it that indicates whether the folder and its sub-folder have mixed permissions for containing sensitive content. For example, while the Monthly Stats folder and its sub-folders are permitted to contain GLBA content, its parent Finance folder is not permitted to directly contain any GLBA content. Therefore the Finance folder and its sub-folders contain mixed permissions for GLBA content. On the other hand, the Human Resources folder and all its sub-folders are not permitted to contain any GLBA content.
5) A folder and all its sub-folders can easily be permitted to contain sensitive content in this dialog.
For example, if you would like to permit the entire Finance folder tree to contain GLBA content, simply toggle the checkbox next to the Finance folder. The folder and every one of its sub-folders will be automatically permitted to contain GLBA content. Even if any Finance sub-folder, like the Payroll folder, was previously not permitted to contain GLBA content, its settings will be overridden by your latest change for the Finance folder.
6) Save your changes in the modal to update the permissions for sensitive content.
7) Your permission changes will be reflected immediately in the Sensitive Content tab. For example, if the Payroll folder had a row in the Sensitive Content tab when you click on its row now, you can see in the Details pane that PCI-DSS has been permitted in that sub-folder.
7) You can also unpermit sensitive content in just a folder from the Sensitive Content tab and see the change reflected in this dialog. In the above example, if you unpermit the Payroll folder to contain GLBA content from the Sensitive Content tab, the dialog for the GLBA policy will immediately reflect your selection.
8) You can click on "Manage permitted locations" to go back to the Settings pane summarizing the permitted folders in the source.