Configuring Cisco Umbrella Connectors

Connectors allow Stellar Cyber to collect data from external sources and add it to the data lake.

Connector Overview: Cisco Umbrella

               Let us know if you find the above overview useful.

Adding a Cisco Umbrella Connector

To add a Cisco Umbrella connector:

1. Configure Cisco Umbrella log management
2. Add the connector in Stellar Cyber
3. Test the connector
4. Verify ingestion

Configuring Cisco Umbrella Log Management

To configure Cisco Umbrella log management:

Use our example as a guideline, as you might be using a different software version.

1. Log in to your Cisco Umbrella dashboard at https://umbrella.cisco.com .

2. Click Admin. The Admin menu expands.

   

3. Click Log Management. The Log Management page appears.
4. In the Amazon S3 section, configure your S3 storage:

   1. If your company has an Amazon S3 bucket, enter the Amazon S3 bucket name and click Verify.

      

   2. To use Cisco-managed Amazon S3 storage, select a region and retention duration.

      

5. Click Save. A confirmation dialog appears.

6. Click Continue. Your storage is activated, and an activation screen appears. Copy the Access Key and Secret Key to a safe location.

   

7. Click Got it!. The Continue button becomes active.

8. Click Continue. The Amazon S3 section now displays your S3 storage.

   

9. Copy the Data Path and add a forward slash (/) to the end of the value.

Adding the Connector in Stellar Cyber

With the data path and keys ready, you can add a Cisco Umbrella connector in Stellar Cyber:

1. Log in to Stellar Cyber.

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

   

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

   

4. Choose Web Security from the Category drop-down.

5. Choose Cisco Umbrella from the Type drop-down.

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

7. Enter a Name.

   This field does not accept multibyte characters.

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 create Log Filters. For information, see Managing Log Filters.

11. Click Next. The Configuration tab appears.

    

12. Enter the Data Path you copied earlier. Make sure there is a forward slash (/) at the end of the value.

13. Enter the Access Key you copied earlier.

14. Enter the Secret Key you copied earlier.

15. Enter the Interval (min). This is how often the logs are collected. By default, the interval is 10 minutes.

16. Choose the Content Type you would like to collect. The logs for Cloud Firewall Logs, DNS Logs, IP Logs, and Proxy Logs are supported.

17. Click Next. The final confirmation tab appears.

    

18. Click Submit.

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

19. 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.

Testing the Connector

When you add (or edit) a connector, we recommend that you run a test to validate the connectivity parameters you entered. (The test validates only the authentication / connectivity; it does not validate data flow).

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

   

2. Locate the connector 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.

Display sample messages...

Success !

Failure with summary of issue: Show More example detail:

 

Verifying Ingestion

To verify ingestion:

1. Click Investigate | Threat Hunting. The Interflow Search tab appears.
2. Change the Indices to Syslog. The table immediately updates to show ingested Interflow records.