Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision | ||
contentdiscovery [2020_03_12 11:48] – jim | contentdiscovery [2024_03_04 17:50] – steven | ||
---|---|---|---|
Line 1: | Line 1: | ||
# Content Discovery and DLP | # Content Discovery and DLP | ||
- | The File Fabric | + | A forthcoming add-on to Nasuni Access Anywhere will feature |
Data stored and uploaded is scanned for data stored in files, based on pre-selected templates, in real-time. | Data stored and uploaded is scanned for data stored in files, based on pre-selected templates, in real-time. | ||
Line 12: | Line 12: | ||
Content rules can also be used with [[automationrules]] that react to content discovery events by taking actions such as sending an email, moving a file etc. | Content rules can also be used with [[automationrules]] that react to content discovery events by taking actions such as sending an email, moving a file etc. | ||
- | |||
- | Applies to: | ||
- | |||
- | * Enterprise File Fabric Appliance [add-on] (since [[cloudappliance/ | ||
See also: | See also: | ||
Line 22: | Line 18: | ||
* [[automationrules]] | * [[automationrules]] | ||
- | This feature replaces [[piidiscovery]]. | ||
## Feature Summary | ## Feature Summary | ||
Line 28: | Line 23: | ||
### Detecting Content | ### Detecting Content | ||
- | Content Discovery works by looking for content of interest after files are indexed by the search engine. This happens when files are added or updated, and when storage providers are added or synchronised. | + | Content Discovery works by looking for content of interest after files are indexed by Content Search. This happens when files are added or updated, and when storage providers are added or synchronised |
Our example company operating within the GDPR might have a detector for UK NHS numbers and a detector for Spanish NIF numbers, among others. Our example sales organization company might have detectors for a specific set of SKUs | Our example company operating within the GDPR might have a detector for UK NHS numbers and a detector for Spanish NIF numbers, among others. Our example sales organization company might have detectors for a specific set of SKUs | ||
Line 56: | Line 51: | ||
### Metadata Indexing | ### Metadata Indexing | ||
- | The Enterprise File Fabric | + | Nasuni Access Anywhere |
The metadata index is a cache of the file name, size, timestamps and other information that provide fast file searches and directory listings. | The metadata index is a cache of the file name, size, timestamps and other information that provide fast file searches and directory listings. | ||
Line 75: | Line 70: | ||
### Classification and Tagging of Files | ### Classification and Tagging of Files | ||
- | When matching content is detected in a file, a category tag is added to the file metadata indicating the type of content that was detected. | + | When matching content is detected in a file, a category tag is added to the file metadata indicating the type of content that was detected. |
{{ : | {{ : | ||
Line 142: | Line 137: | ||
- | In the initial release of v1808 only files containing matching content for at least one of the content detectors in each of the selected categories will be candidates for inclusion in the search results. This behaviour may change in future versions. | + | |
When searching by content detectors, tick the detectors for the kinds of matching content for which you want to search: | When searching by content detectors, tick the detectors for the kinds of matching content for which you want to search: |