Configuring iManage Threat Manager Connectors

This connector allows Stellar Cyber to ingest logs from iManage Threat Manager and add the records to the data lake. It integrates with the iManage Threat Manager API to collect alerts from Behavioral Analytics and Detect and Protect, retrieving alerts from legal document management systems.

Stellar Cyber connectors with the Collect function (collectors) may skip collecting some data when the ingestion volume is large, which potentially can lead to data loss. This can happen when the processing capacity of the collector is exceeded.

Connector Overview: iManage Threat Manager

Adding an iManage Threat Manager Connector

To add an iManage Threat Manager connector:

1. Obtain credentials
2. Add the connector in Stellar Cyber
3. Test the connector
4. Verify ingestion

Obtaining iManage Threat Manager Credentials

Before you configure the connector in Stellar Cyber, you must obtain the following iManage Threat Manager credentials:

• Base URL—The base URL for API access. The default is https://example.tm-cloudimanage.com/example-api-path

• API Token Auth Method—The API Token authentication method:

  • API Token

  • API Secret

• User Sign-In Auth Method—The User Sign-In authentication method:

  • Username

  • Password

Follow the guidance in the documents: Integrating iManage Threat Manager alerts into your SIEM application using the iManage Threat Manager API or iManage Threat Manager Administration Guide.

API Token Auth Method

You can generate an application token, consisting of a token and a secret pair, within the iManage Threat Manager admin console.

You need to be in the Integrations Manager role to create an application token.

1. Navigate to Configuration > Settings > System > New Token.

   

User Sign-In Auth Method

You can also use the iManage Threat Manager API with an access token obtained from explicit user credentials. This provides a similar level of access to what you have in the admin console.

Adding the Connector in Stellar Cyber

To add an iManage Threat Manager connector in Stellar Cyber:

1. Log in to Stellar Cyber.

2. Click System | INTEGRATIONS | Connectors. The Connector Overview appears.

   

3. Click Create and select Connector.

   

   The General tab of the Add Connector screen appears. The information on this tab cannot be changed after you add the connector.

4. Choose Data Loss Prevention from the Category dropdown.

5. Choose iManage Threat Manager from the Type dropdown

   

   The asterisk (*) indicates a required field.

6. For this connector, the supported Function is Collect, which is enabled already.

7. Enter a Name.

   Notes:

   • This field does not accept multibyte characters.
   • It is recommended that you follow a naming convention such as tenantname-connectortype.

8. Choose a Tenant Name. The Interflow records created by this connector include this tenant name.

9. Choose the device on which to run the connector.

   • Certain connectors can be run on either a Sensor or a Data Processor. The available devices are displayed in the Run On menu. If you want to associate your collector with a sensor, you must have configured that sensor prior to configuring the connector or you will not be able to select it during initial configuration. If you select Data Processor, you will need to associate the connector with a Data Analyzer profile as a separate step. That step is not required for a sensor, which is configured with only one possible profile.

   • If the device you're connecting to is on premises, we recommend you run on the local sensor. If you're connecting to a cloud service, we recommend you run on the DP.

10. (Optional) When the Function is Collect, you can apply Log Filters. For information, see Managing Log Filters.

11. Click Next. The Configuration tab appears.

    

    The asterisk (*) indicates a required field.

12. Enter the Base URL you noted above in Obtaining iManage Threat Manager Credentials.

13. For Auth Method API Token:

    1. Enter the API Token you noted above.

    2. Enter the API Secret you noted above.

14. For Auth Method User Sign-In:

    1. Enter the Username you noted above.

    2. Enter the Password you noted above.

       

15. (Optional) Click Disable SSL Certificate Verification if you want to disable SSL certificate verification. Only disable SSL certificates if you have a reason to, otherwise, it is not a good security practice.

16. Choose the Interval (min). This is how often the logs are collected.

17. Choose the Content Type you would like to collect. The logs for Behavioral Analytics Alerts and Detect and Protect Alerts are supported. See Query for Behavioral Analytics Alerts for information on Behavioral Analytics Alerts.

    Use the User Sign-In Auth Method to pull the Detect and Protect Alerts.

18. Click Next. The final confirmation tab appears.

    

19. Click Submit.

    To pull data, a connector must be added to a Data Analyzer profile if it is running on the Data Processor.

20. If you are adding rather than editing a connector with the Collect function enabled and you specified for it to run on a Data Processor, a dialog box now prompts you to add the connector to the default Data Analyzer profile. Click Cancel to leave it out of the default profile or click OK to add it to the default profile.

    • This prompt only occurs during the initial create connector process when Collect is enabled.

    • Certain connectors can be run on either a Sensor or a Data Processor, and some are best run on one versus the other. In any case, when the connector is run on a Data Processor, that connector must be included in a Data Analyzer profile. If you leave it out of the default profile, you must add it to another profile. You need the Administrator Root scope to add the connector to the Data Analyzer profile. If you do not have privileges to configure Data Analyzer profiles, a dialog displays recommending you ask your administrator to add it for you.

    • The first time you add a Collect connector to a profile, it pulls data immediately and then not again until the scheduled interval has elapsed. If the connector configuration dialog did not offer an option to set a specific interval, it is run every five minutes. Exceptions to this default interval are the Proofpoint on Demand (pulls data every 1 hour) and Azure Event Hub (continuously pulls data) connectors. The intervals for each connector are listed in the Connector Types & Functions topic.

    The Connector Overview appears.

The new connector is immediately active.

Query for Behavioral Analytics Alerts

For the Behavioral Analytics Alerts, the two different authentication methods use different API endpoints:

• API Token uses /getAlertList. This alert can only be queried using the access token from the API Token Auth Method.

• User Sign-In uses /getAddressableAlerts. This alert can only be queried using the access token from the User Sign-In Auth Method.

Detect and Protect Alerts can only be obtained with an access token from the User Sign-In Auth Method.

Testing the Connector

In addition to testing for connectivity, the Test button for the iManage Threat Manager connector tests that the Base URL and authentication are correct and data requests for the requested content types return successful responses.

When you add (or edit) a connector, we recommend that you run a test to validate the connectivity parameters you entered. (The test validates authentication and connectivity).

1. Click System | INTEGRATIONS | Connectors. The Connector Overview appears.

   

2. Locate the connector by name that you added, or modified, or that you want to test.

3. Click Test at the right side of that row. The test runs immediately.

   Note that you may run only one test at a time.

Verifying Ingestion

To verify ingestion:

1. Select Threat Hunting.

   The Interflow Search tab appears.

2. Change the Indices to Syslog.

   The table immediately updates to show ingested Interflow records.