Cisco Umbrella

Samurai [Local] CollectorSamurai [Cloud] CollectorSamurai [Cloud Native] Collector
Picture1.svg

This guide describes all steps required to configure Cisco Umbrella to send logs to an S3 bucket and allows Samurai to access (read-only) and ingest the logs.

mceclip0.png Cisco Umbrella integration requires a self managed AWS S3 bucket. For more information on Cisco Umbrella logging refer to the Cisco documentation Manage Your Logs.

mceclip0.png If you already have an AWS S3 bucket configured and have enabled Cisco Umbrella logging then jump straight to Configure an existing AWS S3 bucket to allow Samurai access

If you have not enabled Cisco Umbrella logging to an AWS S3 bucket then follow the steps below to complete the integration:

1) Ensure you have been provided the following parameters from NTT

  • IntegrationsID
  • Passkey

mceclip0.png These parameters will be made available to you during onboarding

2) Have an Amazon AWS Account

  • If you do not have an AWS Account you can refer directly to Cisco Umbrella documentation Enable Logging to your own S3 bucket. This document makes reference to Amazon’s S3 documentation.

3) Decide on an S3 Data Retention Period

  • Defined by you and your retention policy, this refers to automatic deletion of objects in the S3 bucket after X number of days. The default is 7 days, however you can override the value and select a maximum of 365 days.

4) From your browser

5) From your Cisco Umbrella console

Launch the integration stack and complete

Complete the following steps from your browser:

  1. Browse to:

We have simplified the integration through use of a CloudFormation Template that creates the following resources:

  • SNS Topic
  • S3 Bucket with SNS Notification of ObjectCreated Events
  • Secure Bucket Policy, Allowing Samurai RO access
  • SNS HTTPS Webhook Subscription to the Samurai Platform
  1. Click on Launch Stack 

  2. Sign in to your AWS Account with administrative permissions

  3. The Create Stack page will be shown: 

mceclip1.png

  1. Select your AWS region to deploy the stack:
mceclip0.png
  1. Click on Next

  2. The Specify stack details page will be shown:

Specifystackdetails_blank.png
  • Specify a unique Stack name (optional) we default to NTTSamuraiS3Stack 

  • Enter the following parameters previously provided to you by NTT:

    • Samurai Cloud IntegrationsId
    • Samurai Cloud Integrations Pass Key
  • Select Yes under Enabled Cisco Umbrella access to Cloud Integrations S3 Bucket via Bucket Policy

  • Leave The name of an existing Cisco Umbrella Bucket blank

  • Update the Samurai Cloud Integrations Bucket Data Retention period (as needed) 

mceclip0.png The default retention period is 7 days (we recommend 7 days but based on your retention policy you can override the value as necessary)

  1. Click Next

  2. The Configure stack options will be shown:

mceclip3.png
  1. Click Next

  2. You can now Review the steps worked through:

mceclip4.png

  1. Click Create Stack

  2. You will now be shown the stack Events:

mceclip0.png
  1. Select the Resources tab:

mceclip1.png

  1. Make note of the S3 bucket name as you will need this when configuring Cisco Umbrella. The S3 bucket name is the Physical ID of the S3 Bucket and is also a hyperlink.

  2. To verify the webhook has registered with Samurai, click on the hyperlink of the Physical ID of the SamuraiSNS Topic (Logical ID)

  3. The Topic details page will open, you should see Status as Confirmed (see example below):

f5fe6d22-711f-4e49-ba0a-cccf888c5028.jpg

From your Cisco Umbrella console

Follow the Enable Logging section (Steps 1-3) in the Cisco Umbrella documentation:

mceclip0.png Ensure you have the exact name of the AWS S3 bucket

Your integration is now complete. If you have any problems or questions please raise a ticket or reach out to your NTT point of contact.

Configure an existing AWS S3 bucket to allow Samurai access

If you already have Cisco Umbrella logging to a self managed AWS S3 bucket then follow the steps below:

1) Ensure you have been provided the following parameters from NTT

  • IntegrationsID
  • Passkey

mceclip0.png These parameters will be made available to you during onboarding

2) From your browser

Launch the integration stack and complete

Complete the following steps from your browser:

  1. Browse to:

We have simplified the integration through use of a CloudFormation Template that creates the following resources:

  • SNS Topic
  • SNS HTTPS Webhook Subscription to the Samurai Platform
  1. Click on Launch Stack 

  2. Sign in to your AWS Account with administrative permissions

  3. The Create Stack page will be shown: 

mceclip1.png
  1. Select your AWS region to deploy the stack:
mceclip0.png
  1. Click on Next

  2. The Specify stack details page will be shown:

Specifystackdetails.png
  • Specify a unique Stack name (optional) we default to NTTSamuraiS3Stack 

  • Enter the following parameters previously provided to you by NTT:

    • Samurai Cloud IntegrationsId
    • Samurai Cloud Integrations Pass Key
  • Select Yes under Enabled Cisco Umbrella access to Cloud Integrations S3 Bucket via Bucket Policy

  • Under The name of an existing Cisco Umbrella Bucket enter the name of your existing S3 Bucket (an example is depicted in the graphic)

  • Update the Samurai Cloud Integrations Bucket Data Retention period (as needed) 

mceclip0.png The default retention period is 7 days (we recommend 7 days but based on your retention policy you can override the value as necessary)

  1. Click Next

  2. The Configure stack options will be shown:

mceclip3.png
  1. Click Next

  2. You can now Review the steps worked through:

mceclip4.png

  1. Click Create Stack

  2. You will now be shown the stack Events

  3. You can view Resources created:

resources.png

  1. You must now Create Event Notifications. Browse to your existing S3 Bucket Properties
bucketproperties.png
  1. Click Create Event Notification

Createeventnotification.png

  1. The Create event notification window will be shown:
createevent.png

mceclip0.png Scroll down for Destination

MicrosoftTeams-image (3).png
  1. Complete the following fields with the following parameters: (leave all other fields as default)
Field NameParameter
Event namewhatever you want
Object creationAll object create events (enabled)
DestinationSNS Topic (selected)
Specify SNS topicSelect your method to specify the SNS topic
SNS TopicEnter or choose from your topics the relevant Samurai entry
  1. Click Save Changes

  2. You now need to add an S3 bucket policy. Browse to your existing S3 Bucket Properties

  3. Select Edit and add the following statements:

{   "Effect": "Allow",   "Principal": {      "AWS": "arn:aws:iam::600502389717:user/samurai-xdr-s3-reader-user"   },   "Action": [      "s3:GetObject",      "s3:ListBucket"   ],   "Resource": [   "arn:aws:s3:::samurai-12a98319b803",   "arn:aws:s3:::samurai-12a98319b803/*"   ]}
  1. Click Save changes

  2. To verify the webhook has registered with Samurai. Go to the Resources tab of the Samurai Stack and click on the hyperlink of the Physical ID of the SamuraiSNS Topic*(Logical ID)***

  3. The Topic details page will open, you should see Status as Confirmed (see example below):

f5fe6d22-711f-4e49-ba0a-cccf888c5028.jpg

  1. You now need to ensure the S3 Object Ownership of your existing S3 bucket to ensure Samurai is able to download the logs. Sign-in to the AWS Management Console and open the Amazon S3 console (if you have not already done so!) at https://console.aws.amazon.com/s3/

  2. In the Buckets list choose the name of the bucket that you want to apply an S3 Object Ownership setting to

  3. Choose the Permissions tab

  4. Under the Object Ownership, choose Edit

  5. Under Object Ownership ensure Bucket owner preferred is enabled (as depicted in the graphic below)

S3objectownership.jpg

  1. Click Save changes

  2. If you have ACLs disabled, your integration is now complete***.***

  3. If you have ACLs enabled you will need to edit the ACL

  4. In the Buckets list choose the name of the bucket that you want to set permission for

  5. Choose Permissions

  6. Under Access control list, choose Edit

s3ACL.png

  1. Under Access for other AWS account, click Add grantee

  2. Enter 5501afb2b26d7609fe4051b3d23916c6c185da004301607ebbb71883d12d4142 as the canonical ID

  3. Click List (under Objects) and Read (under Bucket ACL)

EditAcl2.png
  1. Click Save Changes

Your integration is now complete. If you have any problems or questions please raise a ticket or reach out to your NTT point of contact.

Our Integration guide was accurate at the time of writing but vendors change things frequently! If you find errors or anything is outdated, let us know by raising a request in the Samurai MDR application and we shall get it updated.