AWS GuardDuty is a threat detection service that continuously monitors your AWS accounts and workloads for malicious activity and delivers detailed security findings for visibility and remediation.
Last updated
Was this helpful?
Go to Alert sources -> Alert sources and click on Create new alert source
Search for AWS GuardDuty in the search field, click on the AWS GuardDuty tile and click on Next.
Give your alert source a name, optionally assign teams, and click Next.
Select an escalation policy by creating a new one or assigning an existing one.
Select your Alert grouping preference and click Continue setup. You may click Do not group alerts for now and change it later.
The next page shows additional settings, such as customer alert templates or notification priority. Click on Finish setup for now.
On the final page, an API key and / or webhook URL will be generated that you will need later in this guide.
Use the search bar and select Simple Notification Service (SNS). Select Topics and click Create Topic in the SNS Dashboard.
Input a Topic name, Display name, and Create topic. After the topic has been created, Select Subscriptions in the left-hand menu and click Create Subscription.
Select HTTPS Protocol and put the URL that was received from the ilert side into the Endpoint field, keep the Enable raw message delivery checkbox unchecked, and Create Subscription.
The subscription would be confirmed automatically on the ilert side, but make sure the Subscription ID is not in PendingConfirmation state.
Search and select the Amazon GuardDuty console in the Service Search. Search for GuardDuty click Enable GuardDuty if this is the first time enabling Amazon GuardDuty.
If the GuardDuty is enabled, CloudWatch Event Rules can be configured to send alerts to ilert. Navigate to the CloudWatch console.
To create a rule, select Rules under Events and then click Create Rules. Select GuardDuty as the Service Name and then choose GuardDuty Finding as the Event Type.
Click Add a target and select SNS topic, select Your Topic Name that has been created earlier and then click Configure Details.
Assign a Name like ilert-incidents and click Create Rule.
In order to test this, go back to the Amazon GuardDuty console and generate sample findings to create an event in ilert.
Select Settings, then select Generate Sample Findings, and then click Findings in the left navigation bar.
The sample findings should have been generated, and it will create the event in the ilert automatically.
