Amazon GuardDuty + PagerDuty Benefits

• The Amazon GuardDuty integration allows you to automate response workflows for security issues that could affect your AWS infrastructure.
• PagerDuty ensures that the right people are notified about things like unauthorized behavior, and you can use PagerDuty’s alert grouping to reduce noise by grouping similar alerts into a single issue.

Requirements

To Configure the Integration:

• In PagerDuty: Managers, Admins, Global Admins and Account Owners can configure the integration.
• In AWS: Users who set up and manage AWS Config must have full-access permissions. Please read Amazon’s documentation Granting Permissions for AWS Config Administration for more information about managing permissions in AWS.

How it Works

• This is a one-way integration. GuardDuty rules send finding events to PagerDuty, and those events generate incidents.

Version

This guide details configuration of the Amazon GuardDuty V1 integration.

Integration Walkthrough

In PagerDuty

There are two ways to integrate Amazon GuardDuty with PagerDuty:

• Integrate With Event Orchestration: Integrating with Event Orchestration may be beneficial if you want to build nested rules based on the payload coming from AWS.
• Integrate With a PagerDuty Service: Integrating with a PagerDuty service directly can be beneficial if you don’t need to route alerts from AWS to different responders based on the event payload. You can still use service-level Event Orchestration to perform actions such as suppressing.

Integrate With Event Orchestration

Integrate With a PagerDuty Service

In the AWS Management Console

1. In the Services search bar, search and select Simple Notification Service. In the SNS dashboard left menu, select Topics and click Create Topic on the right. This topic will be used to route alerts to PagerDuty from AWS.
2. Select the Standard Topic Type.
3. Next, perform the following:
   • Name: Enter a name for your topic. You may want to name your topic after your PagerDuty service’s name.
   • Display name (optional): Enter an optional display name.
   • Click Create topic.
4. Now that your topic has been created, select Subscriptions in the left menu and click Create Subscription.
5. Perform the following:
   • Topic ARN: Select the Topic ARN of the topic you just created.
   • Protocol: Select HTTPS.
   • Endpoint: Paste your Integration URL (generated in steps above).
   • Perform the following based on your preference:
     • If you are integrating with Global Orchestrations: We recommend that the Enable raw message delivery checkbox is checked.
     • If you are not integrating Global Orchestrations: Ensure that the Enable raw message delivery checkbox is unchecked.
   • Click Create Subscription.
6. Your subscription should be automatically confirmed. Refresh the page to make sure the Status is Confirmed and not PendingConfirmation.
7. • If you have not enabled GuardDuty, please follow Amazon’s documentation.
   • If you have already enabled GuardDuty, proceed to step 8.
8. Once you have enabled GuardDuty, you can begin building EventBridge Rules to send alerts to PagerDuty. Search and select EventBridge from the Services search bar.
9. Select Rules from the left menu, then click Create Rule. One or more rules can be created to send specific events to PagerDuty when a GuardDuty finding is opened.
10. On the next screen, perform the following:
    • Name: Enter a name that can be easily identified.
    • Description (optional): Enter a description of the rule, pattern and target(s).
    • Event Bus: Select default.
    • Enable the rule on the selected event bus: Toggle to the on position.
    • Rule with an event pattern: This will automatically be preselected.
    • Click Next to continue.
11. On the next page, perform the following:
    • Event source: Select AWS events or EventBridge partner events.
    • Sample event (optional): If you would like to view sample events, you may do so in this section.
    • Event Source: Select AWS services.
    • AWS Service: Select GuardDuty.
    • Event type: Select GuardDuty Finding.
    • Click Next to continue.
12. On the next page, perform the following:
    • Target types: Select AWS service.
    • Select a target: Search and select SNS topic.
    • Topic: Search and select the topic created in previous steps.
    • Configure other additional settings to your preference.
    • Click Next to continue.
13. On the next page, optionally add tags to your preference. Click Next to continue.
14. On the final page, review your settings and click Create Rule. If you would like to create more rules, repeat steps 9-14.

The integration is now complete. To ensure the configuration was successful, navigate back to the Amazon GuardDuty console, select Settings in the left menu, scroll down and click Generate Sample Findings, then select Findings in the left menu. You will see the sample findings that have been generated, and in PagerDuty you will see the correlated sample alert.