To fully integrate USM Anywhere with your Cisco Umbrella (formerly, OpenDNS) implementation, you should configure log collection so that USM Anywhere can retrieve and normalizeNormalization describes the translation of log file entries received from disparate types of monitored assets into the standardized framework of Event types and sub-types. raw log data from Cisco Umbrella. The combination of the Cisco Umbrella data source integration and configuration of the AlienApp for Cisco Umbrella provides a full scope of data and analysis within USM Anywhere.
Note: Cisco Umbrella provides log retention for the mid (Insights) and top (Platform) tier product packages only. If you are using the lowest tier package (Professional), you cannot collect log data from Cisco Umbrella. For more information about the Cisco Umbrella product packages, refer to the vendor website.
Important: By design, Cisco Umbrella only exports log data to an Amazon S3 bucket. Because of this limitation, log collection requires a USM Anywhere Sensor deployed in an AWS account. However, you can use another deployed Sensor type to configure an AlienApp for Cisco Umbrella API connection to support response actions.
For more information about deploying an additional USM Anywhere Sensor in an AWS environment, see Adding an Additional Sensor for Other AWS Accounts.
Amazon S3 Log Management
Before the USM Anywhere can collect the Umbrella log data, you must set up Amazon Simple Storage Service (S3) log management in your Cisco Umbrella deployment. This requires that you have a self-managed Amazon S3 bucket in an Amazon Web Service (AWS) account that is configured to accept uploads from the Umbrella Service. For detailed information about this configuration, refer to this article: https://support.umbrella.com/hc/en-us/articles/231248448-Cisco-Umbrella-Log-Management-in-Amazon-S3#self-bucket
Note: USM Anywhere currently does not support the Cisco-managed buckets in Amazon S3.
To verify Amazon S3 log management in Cisco Umbrella
- Log in to the Cisco Umbrella (OpenDNS) dashboard.
- Go to Settings > Log Management.
- Click Amazon S3.
- In the Bucket Name field, enter the exact Amazon S3 bucket name.
A confirmation message in the dashboard indicates that the bucket has been successfully verified.
After you verify that Cisco Umbrella is configured to send log data to an Amazon S3 bucket for an account where you have a deployed USM Anywhere Sensor, you can set up a log collection job for USM Anywhere to retrieve that data.
Note: If you want to deploy a sensor to facilitate Cisco Umbrella log collection, see AWS Sensor Deployment.
To schedule Cisco Umbrella log collection
- Go to Settings > Scheduler.
In the left navigation list, click Log Collection.
Note: You can use the Sensor filter at the top of the list to choose your
AWS sensorto easily review the current AWSlog jobs.
Click Create Log Collection Job.
Note: If you recently deployed a new USM Anywhere Sensor, it can take 10 to 20 minutes for USM Anywhere to discover the various log sources. After it discovers the logs, you must manually enable the
AWSlog collection jobs you want before the system collects the log data.
Enter the name and description for the job.
The description is optional, but it is a best practice to provide this information so that others can easily understand what it does.
- For the Action Type option, select Amazon Web Services.
- Select the USM Anywhere Sensor for the job to run on.
For the App Action option, select Monitor S3 bucket.
- In the Bucket Name field, enter the name of the Amazon S3 bucket that is configured in Cisco Umbrella log management.
- In the Path field, enter the path on the bucket where the logs reside (in this case, dnslogs/).
- For the Source Format option, select raw.
For the Plugin option, select Cisco Umbrella.
- In the Schedule section, specify when USM Anywhere runs the job.
You should start seeing new Cisco Umbrella events in USM Anywhere shortly after the initial raw log data collection and normalization.
First, select the increment as Hour, Day, Week, Month, or Year.
Next, set the interval options for the increment. The selected increment determines the available options.
For example, on a weekly increment you can select the days of the week to run the job.
Or, on a monthly increment you can specify a date or a day of the week that occurs within the month.
To finish, set the Start time. This is the time that the job starts at the specified interval. It uses the time zone configured for your USM Anywhere instance (default is UTC).