Accenture MDR Quick Start Guide for Cisco Umbrella - Cloud Delivered Enterprise Security

This quick start guide will help Accenture MDR customers configure Cisco Umbrella Cloud Delivered Enterprise Security to send logs to the Log Collection Platform (LCP).

 

The document includes the following topics:

Supported Versions

A list of supported versions is available in the Accenture MDR Supported Products List document (Accenture_MDR_Supported_Products_List.xlsx) which can be found in Accenture MDR Portal.

Port Requirements

Table1-1: Port requirements for LCP communication.

Source

Destination

Port

Description

LCP

Cisco Umbrella

443(HTTPS)

Default port

Configuring Cisco Umbrella

There are two ways to configure the log management in Cisco Umbrella. 

  1. A Cisco-managed bucket, where Cisco Umbrella owns the bucket, and set the configuration automatically.

  2. A Self-managed bucket, where you own the bucket in Amazon and set up the configuration.

Once you have configure the bucket, follow the below ways to setup and verify the created S3 bucket..

i) Set up your Amazon S3 bucket.

ii) Verify your Amazon S3 bucket.

I. Configure Cisco Managed Amazon S3 bucket.

  1. On the Umbrella dashboard, navigate to Admin > Log Management.

2. Select Use a Cisco-managed Amazon S3 bucket.

3. From the Select a Region drop-down list, choose a region.

Regional endpoints are important to minimize latency when downloading logs to your servers. From the drop-down list, you can pick a region that is closest to you. In the future, if you wish to change your region you will need to delete your current settings and start over. 

4. From the Select a Retention Duration drop-down list, choose the time period.

The retention duration is simply 7, 14, or 30 days. Beyond the selected time period, all data will be purged and cannot be retrieved. We recommend a smaller time period if your ingestion cycle is regular. The retention duration can be changed at a later time.

5. Click Save and you will be asked to confirm your region and duration. 

6. Click Continue and  you will get an activation notification.

7. You will then get your access and secret keys. You must accept them by clicking Got it!, because this the only time you will get to see either of the keys. The access and secret keys are required in order to access your data path and download logs.

The summary screen displays the configuration and your bucket name. You can turn logging off/on at your convenience. However, logs will be purged based on your retention duration, whether or not you are continuing to log new data.

 Note: For more information on device configuration for log collection, refer: https://support.umbrella.com/hc/en-us/articles/231248448-Cisco-Umbrella-Log-Management-in-Amazon-S3

 

II. Set up a self-managed Amazon bucket in S3.

    Prerequisites:

    In order to archive DNS,Proxy logs, you must meet the following requirements:

  • Full administrative access to the Cisco Umbrella dashboard.

  • Login to the Amazon AWS service (http://aws.amazon.com/console/). If you do not have an account, Amazon provides free signup for S3. They require a credit card in case your usage exceeds the free plan usage.

  • User with s3 bucket read only access.

  • A bucket configured in Amazon S3 to be used for storing logs. Instructions for configuring and setting up the Amazon S3 bucket are given below.If IAM users want to fetch S3 bucket logs then, you have to generate the access keys using below steps:

To Create, Modify, or Delete a user's access keys

  1. Sign in to the AWS Management Console and open the IAM console at https://console.aws.amazon.com/iam/.

  2. Choose Users in the navigation pane.

  3. Choose the name of the desired user, and then choose the Security Credentials tab.

  4. If needed, expand the Access Keys section and do any of the following:

a) To create an access key, choose Create Access Key. Then choose Download Credentials to save the access key ID and secret access key to a CSV file on your computer.

b) Store the file in a secure location.

c) You will not have access to the secret access key again after this dialog box closes.

d) After you have downloaded the CSV file, choose Close.

To set up your Amazon S3 bucket:

  1. Login to the AWS console, and from the list of options, select S3 - Scalable Storage in the Cloud. (It is seen at the upper left corner, under Storage & Content Delivery.)

2. Next, to create a bucket click Create Bucket, if you do not have one.

 

3. In the Bucket Name text box, type the bucket name. 

The bucket name must be universally unique, not just to your AWS or Umbrella, but to all of Amazon AWS. Use something personal, such as my-organization-name-log-bucket. Use lowercase alphabets for the bucket name and it should not contain spaces or periods and must comply with DNS naming conventions. 

 Note: For more information on name restrictions, see: http://docs.aws.amazon.com/AmazonS3/latest/dev/BucketRestrictions.html

For more information on bucket creation, including naming, see: https://docs.aws.amazon.com/AmazonS3/latest/UG/CreatingaBucket.html

  4. From the Region drop-down list, select a region that works best for your location and click Create. 

5. Next, to configure the bucket to accept uploads from the Umbrella service (in S3, this is referred to as a bucket policy), click the newly created bucket to open it.

6. Then, at the upper right-hand corner, select Properties.

7. From the Properties drop-down list, select and expand Permissions. From the Permissions drop-down list, click Add bucket policy.

8. A modal window opens. Upload the preconfigured bucket policy provided in this article.

9. Copy and paste the JSON string below which contains the bucket policy to a text editor or simply paste it in the window. Substitute your bucket name where bucket name is specified below.

 Note: The bucket name must be exact or the service will not accept the bucket policy and you will receive the error message "Policy has invalid resource - arn:aws:s3:::bucketname/*".

 

{

"Version": "2008-10-17",

"Statement": [

{

"Sid": "",

"Effect": "Allow",

"Principal": {

"AWS": "arn:aws:iam::568526795995:user/logs"

},

"Action": "s3:PutObject",

"Resource": "arn:aws:s3:::bucketname/*"

},

{

"Sid": "",

"Effect": "Deny",

"Principal": {

"AWS": "arn:aws:iam::568526795995:user/logs"

},

"Action": "s3:GetObject",

"Resource": "arn:aws:s3:::bucketname/*"

},

{

"Sid": "",

"Effect": "Allow",

"Principal":

{ "AWS": "arn:aws:iam::568526795995:user/logs" }

,

"Action": "s3:GetBucketLocation",

"Resource": "arn:aws:s3:::bucketname"

},

{

"Sid": "",

"Effect": "Allow",

"Principal": {

"AWS": "arn:aws:iam::568526795995:user/logs"

},

"Action": "s3:ListBucket",

"Resource": "arn:aws:s3:::bucketname"

}

]

}

10. Click Save to confirm this change.

​Verify your Amazon S3 bucket.

Step 1:

  1. Go to the Umbrella dashboard and navigate to Admin > Log Management. 

  2. To expand the window, click Amazon S3.

  3. In the Bucket Name field, type or paste the exact bucket name you created in S3 and click Verify. 

  4. You should receive a confirmation message in your dashboard indicating that the bucket was successfully verified. If you receive an error indicating that your bucket could not be verified, re-check the syntax of the bucket name and review the configuration. If problems persist, please open a case with our support department. 

Step 2:

  1. As a precaution to ensure the correct bucket was specified, Umbrella will ask you to enter a unique activation token. The activation token can be obtained by revisiting your S3 bucket. As part of the verification process, a file named README_FROM_UMBRELLA.txt was uploaded from Umbrella to your Amazon S3 bucket and should appear there.  

  2. Double-click the readme file to download it and then open it in a text editor. Within the file, there will be a unique token tying your S3 bucket to your Umbrella dashboard.  

 Note: You may need to refresh your S3 bucket in the browser in order to see the readme file after it has been uploaded.

  3. Return to the Umbrella dashboard, and in the Token Number field, paste the token and click Save. At this point, the configuration is complete. 

 

LCP Configuration Parameters

Table 1-2: The Cisco Umbrella event collector (API -3839) properties to be configured by MDR are shown in the table.

Property

Custom

Description

Endpoint

http://s3.us-east-1.amazonaws.com/

Endpoint URL mentioned in the Pre-Installation Questionnaire (PIQ). AWS Region server name where you have created the bucket.https://docs.aws.amazon.com/general/latest/gr/rande.html#s3_region

BucketName

Value 1: umbrella-managed-2404292-6917979fd4efb1297a5c4e6764961489

Value 2: cisco-managed-us-west-1/1234567_ae5e32dc29f7b94d22d8f08fc9a3fcba6a3a1234

Data path which is defined in s3 configuration.

 

Note: copy the path after "s3://"

AccessKey

AKIAILGNLDA7PTJLKSQ

Based on the Account ID. IAM user must be part of an appropriate role that has required permissions to access/read from AWS S3.

SecretKey

PHEZgsYLvectp2Moa8Ygq1UW2N5abVwTMM0T3x==

Based on the Account ID.

 

Legal Notice

Copyright © 2021 Accenture. All rights reserved.

Accenture, the Accenture Logo, and DeepSight Intelligence are trademarks or registered trademarks of Accenture in the U.S. and other countries. Other names may be trademarks of their respective owners.

The product described in this document is distributed under licenses restricting its use, copying, distribution, and decompilation/reverse engineering. No part of this document may be reproduced in any form by any means without prior written authorization of Accenture and its licensors, if any.

THE DOCUMENTATION IS PROVIDED "AS IS" AND ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT, ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TO BE LEGALLY INVALID. ACCENTURE SHALL NOT BE LIABLE FOR INCIDENTAL OR CONSEQUENTIAL DAMAGES IN CONNECTION WITH THE FURNISHING, PERFORMANCE, OR USE OF THIS DOCUMENTATION. THE INFORMATION CONTAINED IN THIS DOCUMENTATION IS SUBJECT TO CHANGE WITHOUT NOTICE.

The Licensed Software and Documentation are deemed to be commercial computer software as defined in FAR 12.212 and subject to restricted rights as defined in FAR Section 52.227-19 "Commercial Computer Software - Restricted Rights" and DFARS 227.7202, et seq. "Commercial Computer Software and Commercial Computer Software Documentation," as applicable, and any successor regulations, whether delivered by Accenture as on premises or hosted services. Any use, modification, reproduction release, performance, display or disclosure of the Licensed Software and Documentation by the U.S. Government shall be solely in accordance with the terms of this Agreement.