avinashmamidi / serverless-guardduty-findings-to-sns

A lambda function to push GuardDuty Findings to SNS Topic 🎓

Amazon GuardDuty Findings to SNS

Every GuardDuty finding is assigned a finding ID. For every finding with a unique finding ID, GuardDuty aggregates all subsequent occurrences of a particular finding that take place in six-hour intervals into a single event. GuardDuty then sends a notification about these subsequent occurrences based on this event. We can use this to push the notifications into SNS topic, and getting the security teams to investigate the findings.

This AWS Lambda function will help you to automatically push GuardDuty findings to an SNS topic which can be used by ITSM tools for their workflows.

Follow this article in Youtube

Pre-Requisities

We will need the following pre-requisites to successfully complete this activity,

• A SNS topic to which our lambda will publish the GuardDuty Findings. Help for setting up SNS Topic
  • <ARN-OF-YOUR-SNS-TOPIC> - We need this to update in the IAM Policy
  • An email address already subscribed to this topic
• IAM Role - i.e Lambda Service Role - with two permissions; Help for setting up IAM Role
  • AWSLambdaBasicExecutionRole - To allow Lambda to log events
  • InlinePolicy - To allow Lambda to publish to SNS topic

Step 0: IAM Policy

{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Sid": "VisualEditor0",
            "Effect": "Allow",
            "Action": "sns:Publish",
            "Resource": "<ARN-OF-YOUR-SNS-TOPIC>"
        }
    ]
}

Step 1 - Configure Lambda Function- Serverless Janitor

The python script is written(and tested) in Python 3.6. Remember to choose the same in AWS Lambda Functions.

Customisations

• Change the global variables at the top of the script to suit your needs.

  • globalVars['SNSTopicArn']] - Update the code with your <ARN-OF-YOUR-SNS-TOPIC>; you can also do that using Lambda Environment variables

• Copy the code from Serverless-GuardDuty-Findings-To-SNS in this repo to the lambda function

  • Consider increasing the lambda run time as needed, the default is 3 seconds.

• Save the lambda function

Step 2 - Configure Lambda Triggers

Goto the Cloudwatch Dashboard, We are going to use Event Rules

1. Choose Create a new Rule
2. For Event Source - Choose Event pattern
   1. For Service, Choose/Type GuardDuty
   2. For Event Type, Choose GuardDuty Finding
3. For Target, Choose Lambda Function
   1. From dropdown select your Lambda Function Name
4. In the bottom, Configure Details
5. Fill the Rule Name & Rule Description
   1. Make sure it is Enabled
6. Enable Trigger by Checking the box
7. Click Save

Now your lambda function should be triggered when ever there is a GuardDuty Findings

Step 3 - Testing the solution

Goto GuardDuty Dashboard. Here we can generate some sample findings from Settings Tab.

Or if you want more sophisticated testing, try out this If you dont have any, considering trying out my Serverless AMI Baker.

Summary

We have demonstrated how you can automatically push the findings to SNS Topic.