: Begin Scanning a Microsoft Exchange App
Focus
Focus

Begin Scanning a Microsoft Exchange App

Table of Contents

Begin Scanning a Microsoft Exchange App

Use Data Security to scan and identify incidents found when scanning assets and email attachments in your Microsoft Exchange app.
To connect a Microsoft Exchange app to Data Security and begin scanning assets, you need to:
  • Ensure that you have a Microsoft Exchange or Office 365 account with Global Admin role.
  • Grant Exchange API access to Data Security.
  • Add the Exchange app to Data Security.
As of July 2020, the Exchange integration on Data Security is now updated to optimize the permissions required for cloud app features. To revoke unnecessary permissions that you granted previously and that Data Security no longer needs, reauthenticate the Exchange app.
Support for automated remediation capabilities varies by SaaS application.

Add Microsoft Exchange App

In order for Data Security to scan assets, you must consent to the following permissions during the course of adding the Exchange app:
API
PermissionDescription
Microsoft Graph API
Read all users' basic profiles
Retrieves basic user information such as display name, email address, and User-ID to display user information on People page.
Read all users' full profiles
Allows Data Security to make a user API call. Data Security uses this permission for both Graph API and Outlook Legacy REST API.
Additionally, allows Data Security to retrieve detailed user information (For example, user principle name (UPN), job title, office location, phone number, etc.), but Data Security discards all this information except for UPN, which Data Security needs to retrieve user mailbox settings.
Read all user mailbox settings
Retrieves each user's mailbox settings (For example, retention policy settings, email forward settings, public folder access settings, and delegate rules settings), and then determines if there is any security risk in those settings.
Read mail in all mailboxes
Retrieves and scan the user's email.
Read all hidden memberships
Not currently used, but Data Security plans to use this permission to detect memberships of hidden groups.
Read all groups
Not currently used, but Data Security plans to use this permission to scan group properties and detect the members in the group.
Read calendars in all mailboxes
Allows Data Security to access attachments in calendar events.
Use Exchange Web Services with full access to all mailboxes
Retrieves each user's mailbox settings (For example, inbox rules and eDiscovery search configuration), and then determines if there is any security risk in those settings. Data Security plans to use this permission to determine if the user owns any public folders.
Read directory data
Allows Data Security to retrieve and scan for a list of users and groups. Data Security uses this permission for both Azure Active Directory Legacy API and Graph API.
Read activity data for your organization
Allows Data Security to read and log activity data to display activity data on Activities page.
  1. (Recommended) Add your Exchange domain as an internal domain.
  2. Log in to Microsoft Exchange or Office 365 using an account with privileges that will enable communication between Data Security and the Microsoft Exchange app.
    Before you can establish communication between Data Security and the Exchange app, you must:
    • Go to http://portal.microsoftonline.com and log out of Exchange or Office 365.
    • Log in to Exchange or Office 365 using an account that has the Global Admin role before adding the Exchange app to Data Security.
  3. Add the Exchange app.
    1. Log in to SaaS Security.
    2. Add the Microsoft Exchange app. Go to Data SecurityApplicationsAdd ApplicationMicrosoft Exchange.
    3. Enter the login credentials for the account with Global Admin role privileges on the Microsoft online page to which Data Security redirects you.
    4. Review and Accept the changes that Data Security can perform on your assets in Microsoft Exchange.
      Data Security requires these permissions to scan your assets on Exchange app.
      After authentication, Data Security adds the new Exchange app to the list of Cloud Apps as Microsoft Exchange n, where n is the number of Exchange app instances that you have connected to Data Security. For example, if you added one Exchange app, the name displays as Exchange 1.
  4. Next step: Proceed to Customize Microsoft Exchange App.

Troubleshooting Onboarding for Microsoft Exchange App

To ensure that your app has onboarded correctly without any issues in authentication or permissions, Data Security performs validation checks between the onboarding and scanning process. You can start scanning only after a successful validation. For Microsoft Exchange, the following two validations happen:
  • App Authentication
  • Validating Permissions
After the validation is successful, Data Security displays sample assets and sample activities.
If you don't have any subscriptions, you will not see any User activities in the validation page. It might take up to 12 hours for the first content blobs to become available. For more information, see Office 365 Management Activity API reference.
If the App Authentication or Validating Permissions check fails, try the following:
  1. Ensure you have administrator permissions.
  2. Check if Palo Alto Networks application is listed in the list of Enterprise Applications. Following are the app names for specific regions:
    • USA: Aperture by Palo Alto Networks - Exchange
    • Japan: Palo Alto Networks NG-CASB - JP - Exchange
    • EU: Aperture by Palo Alto Networks - Exchange
    • India: Palo Alto Networks NG-CASB - India - Exchange
    • APAC: Aperture by Palo Alto Networks - Exchange
    • UK: Palo Alto Networks NG-CASB - UK - Exchange
    • Australia: Palo Alto Networks NG-CASB - AUS - Exchange
  3. If Palo Alto Networks application is not listed, check if the Audit Logs Activity displays as Consent to application, Target as <app from the list given above>, and Status as Success.
See the following table to understand the errors you are facing during validation.
Error Codes
Description
Errors in App Authentication
invalid_request
Request is invalid.
invalid_grant
Internal error encountered.
unauthorized_client
The installed app in the Marketplace was uninstalled manually from your cloud app.
invalid_client
Issue related to Marketplace instance.
temporarily_unavailable
Microsoft Exchange app issue on the server side. Please reinstall.
Errors in fetching sample assets and activities (warning messages only)
accessDenied
Access is denied for ${user}.
activityLimitReached
App's API limit reached. Try after sometime.
invalidRange
You don't have any thing to get for this entity.
invalidRequest
Request is invalid.
itemNotFound
No data associated with this entity.
notAllowed
Authentication failure while retrieving the entity.
notSupported
Getting entity with required information no longer supported.
serviceNotAvailable
Microsoft Exchange server is not responding.
quotaLimitReached
Quota for app request has been exhausted for now.
unauthenticated
Microsoft Exchange app issue from server side.
If the issue persists, contact SaaS Security Technical Support.

Customize Microsoft Exchange App

  1. (Optional) Give a descriptive name to this app instance.
    1. Select the Exchangen link on the Cloud Apps list.
    2. Enter a descriptive Name to differentiate this instance of Exchange from other instances you are managing.
    3. Click Done to save your changes.
  2. Next step: Proceed to Identify Risks.

Identify Risks

When you add a new cloud app and enable scanning, Data Security automatically scans the cloud app against the default data patterns and displays the match occurrences. You can take action now to improve your scan results and identify risks.
  1. Start scanning the new Exchange app for risks.
    All email attachments in Exchange are scanned based on defined policy rules. Email content is scanned based on defined policy rules only if the sender or receiver of the email is from an external domain. Scanning only starts on installation, and assets without risks are not stored.
  2. Monitor the scan results.
    During the discovery phase, Data Security scans files and matches them against enabled default policy rules.
    Verify that your default policy rules are effective. If the results don’t capture all risks or you see false positives, improve the results.
  3. (Optional) Modify match criteria for existing policy rules.
  4. (Optional) Add new policy rules.
    Consider the business use of your cloud app, then identify risks unique to your enterprise. As necessary, add new:
  5. (Optional) Configure or edit a data pattern.
    You can Configure Data Patterns to identify specific strings of text, characters, words, or patterns to make it possible to find all instances of text that match a data pattern you specify.