Begin Scanning a Jive App

To connect a Jive app to SaaS Security API and begin scanning assets:
  1. Add the Jive app.
    1. From the
      , click
      Add a Cloud App
      , and select
    2. Click
      Connect to Jive Account
      You must be a Jive community administrator to add a Jive app to SaaS Security API.
    3. Add the
      Jive URL
      for your instance.
    4. Add the
      Client ID
      Client Secret
      copied from the Jive Add-On management settings page and click
    5. Click
      to grant SaaS Security API access to your Jive account.
      After authentication, the new Jive app is added to the list of Cloud Apps as Jive n, where n is the number of Jive app instances you have connected to SaaS Security API. For example, if this is the second Jive app you have added, the name displays as Jive 2.
  2. (Optional)
    Give a descriptive name to this app instance.
    1. Select the Jive n link on the Cloud Apps list and enter a descriptive
      to differentiate this instance from other instances, and click
  3. Add policy rules.
    When you add a new cloud app, SaaS Security API automatically begins scanning the assets for possible policy violations. As a best practice, consider the business use and any associated risks and evaluate whether you want to Add a New Asset Rule to look for incidents unique to Jive.
  4. (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.
  5. Start scanning Jive for possible policy violations and data exposure.
    1. Select
      Cloud Apps & Scan Settings
    2. In the Cloud Apps row that corresponds to the Jive app you just added, select
      Start Scanning
      SaaS Security API scans the following assets in the associated Jive app — Discussions, Uploaded Files, Documents, Blog Posts, Events, and Ideas. Other asset types are not scanned. Depending on the number of Jive users and assets, it may take some time for SaaS Security API to complete the scan. As soon as you begin to see information populate the
      , you can begin to Assess Incidents on SaaS Security API.
  6. Monitor the results of the scan.
    As SaaS Security API scans files and matches them against enabled policy rules, you can 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.

Recommended For You