Begin Scanning a Salesforce App

To begin scanning a Salesforce app:
  1. Ensure that the Salesforce administrator account you plan to use with the Aperture service has sufficient privileges.
    To configure the required permissions within Salesforce:
    1. Under Setup, select Manage UsersUsers.
    2. Select the administrative user account you plan to use to connect the Aperture service to Salesforce and then click System Permissions.
    3. Under System, enable the following permissions:
      • API Enabled
      • Manage Chatter Messages (required only if you use Chatter)
      • Modify All Data
      • View All Data
    4. Under Users, enable the following permissions:
      • View All Users
      • Manage Users (required only if you have not enabled User Sharing)
  2. Add the Salesforce app.
    1. From the Aperture Dashboard, Add a Cloud App.
    2. Select Salesforce.
    3. Choose the type of Salesforce application to add:
      • Connect to Salesforce Account—Adds your Salesforce production account to the Aperture service.
      • Connect to Salesforce Sandbox—Adds a Salesforce Sandbox account to the Aperture service. Sandboxes are special Salesforce accounts. They are maintained separately from your product account and useful for development, testing, and training.
    4. Log in to Salesforce.
      Upon successful authentication using an account with the appropriate privileges, the new Salesforce app is added to the list of Cloud Apps as Salesforce n, where n is the number of Salesforce app instances you have connected to the Aperture service. For example, if this is the second Salesforce app you have added to the Aperture service, the name displays as Salesforce 2.
  3. Give a descriptive name to this app instance.
    1. Select the Salesforce n link on the Cloud Apps list.
    2. (Optional) Enter a descriptive Name to differentiate this instance of Salesforce from other instances you are securing.
    3. Click Done to save your changes.
  4. (Optional) Tune the maximum number of API calls allowed from the Aperture service to Salesforce.
    By default, the Aperture service can send a maximum of 10,000 API calls to Salesforce.
  5. Define global scan settings.
  6. Add policy rules.
    When you add a new cloud app, the Aperture service automatically scans the app against the default data patterns and displays the match occurrences. As a best practice, consider the business use of your app to determine whether you want to Add a New Policy Rule for Content to look for risks unique to the new app.
  7. (Optional) Configure or edit a data pattern.
    When you add a new cloud app, the Aperture service automatically scans the app against the default data patterns and displays the match occurrences. 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.
  8. Start scanning the new app for risks.
    1. Select SettingsCloud Apps & Scan Settings.
    2. In the Cloud Apps row that corresponds to the new Salesforce app you just added, select ActionsStart Scanning.
      The status changes to Scanning. The Aperture service starts scanning all assets in the associated Salesforce app and begins identifying incidents. Depending on the number of Salesforce users and assets, it may take some time for the Aperture service to complete the process of discovering all assets and users. However, as soon as you begin to see this information populating in the Aperture web interface, you can begin to Assess Incidents.
  9. Monitor the results of the scan.
    As the Aperture service starts scanning files and matching them against enabled policy rules, Monitor Scan Results on the Dashboard to verify that your policy rules are effective.
    Monitoring the progress of the scan during the discovery phase allows you to Fine-Tune Policy to modify the match criteria and ensure better results.

Related Documentation