The exposure level describes how an asset is being shared. Although every SaaS application has its own settings for controlling how and with whom users may share assets, the Aperture service provides a mechanism for setting and enforcing acceptable exposure levels consistently across all of your managed SaaS applications. In the Aperture service, each policy rule—both the default rules as well as any custom rules you define—allows you to set a level of exposure identifying an asset as being at risk (except for Sensitive Documents rules, which are designed to match only documents with particular characteristics).
The exposure level is just one of the match criteria in a policy rule and, therefore, determining the minimum level of exposure posing a threat depending on the other match criteria and what threat the policy rule is designed to protect against. For example, the WildFire policy rule scans all of your assets for files containing malware. In this case, any file containing malware poses a threat no matter how the asset is being shared so the rule must match all exposure levels. However, if you add a Sensitive Credential policy rule to protect an engineering GitHub repository (used for sharing code throughout the company), any external sharing poses a risk so you should configure the rule to match on Public and External exposures.
The Aperture service scans assets for the following exposure levels:
An asset is considered Public if it contains either of the following:
The owner invited one or more users outside of your organization to collaborate on the asset.
The owner created a company-wide URL giving anyone in the company direct access to the asset.
Includes assets the owner has not shared. Also includes assets the owner has shared, but only with users within the company. These users have an email address in the enterprise domain name.
Shared via Custom URL
The owner created a custom link, vanity URL, or password-protected link for direct access to the asset and then shared this asset (directly or indirectly) using the link.
This option is for Box assets only; it is hidden if you are not using Aperture to secure Box applications.
New Features Introduced in August 2016
New Features Introduced in August 2016 The following table provide a snapshot of new features introduced for Aperture™ in August 2016. Refer to the Aperture ...
Add a New Asset Policy Rule
Add a New Asset Policy Rule To add a new policy rule for scanning assets stored on your SaaS applications: Select Policy Asset Rules Add ...
Change Sharing SaaS applications make it easy for users to collaborate and share information in the cloud. However, tracking and controlling the different types of ...
View Asset Details
View Asset Details As the Aperture service scans your managed cloud apps and discovers content, you can view the details on Explore Assets . This ...
New Features Introduced in September 2017
New Features Introduced in September 2017 The following table provides a snapshot of new features introduced for Aperture™ in September 2017. Refer to the Aperture ...
New Features Introduced in October 2017
New Features Introduced in October 2017 The following table provides a snapshot of new features introduced for Aperture™ in October 2017. Refer to the Aperture ...
Use Faceted Search to Filter Assets
Use Faceted Search to Filter Assets In addition to the highlights from the Dashboard, the Aperture service provides visibility into all assets in your managed ...
Match Criteria by Rule Type
Match Criteria by Rule Type When you Add a New Policy Rule for Content or you Modify a Policy Rule , you define the match ...
Aperture Predefined Content Data Patterns
Aperture Predefined Content Data Patterns The predefined data patterns provided by Aperture enable you to discover sensitive content and how that content is being shared ...