AWS GuardDuty Connector

Pre-requisites

  • AWS Access key
  • AWS Secret key
  • AWS Region
  • Detector ID
How to Derive the Prerequisites

  • Log in to the AWS Management Console
  • Go to the IAM Dashboard – In the search bar, type IAM and select the IAM service.




  • Go to the Policies section.
  • Click Create Policy.
  • Use the following JSON to define the required permissions for accessing the ListFindings and GetFindings methods:
{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Effect": "Allow",
            "Action": [
                "guardduty:ListFindings",
                "guardduty:GetFindings"
            ],
            "Resource": "*"
        }
    ]
}
  • Attach Policy to a User
    • Create a new IAM user.
    • Select Programmatic Access to generate an access key and secret key.
    • Attach the policy created.
  • Download the Access Key
    •  After the user is created, you’ll see the Access key ID and Secret access key. – Click Download .csv to save these credentials securely. 
    • Important : You won’t be able to view the Secret Access Key again, so ensure you download or copy it securely.
Configurations

Use the following fields to configure the AWS GuardDuty Connector in DNIF:

FieldDescription
Connector NameProvide a unique name for the connector.
AWS Access KeyAWS credentials used to authenticate API requests to AWS services.
AWS Secret KeyAWS credentials, paired with the access key to securely authorize requests.
AWS RegionThe AWS region (e.g., us-east-1) where your GuardDuty instance is deployed. 
Detector IDA unique ID associated with your GuardDuty detector.
  • Click Save after entering all the required details and click Test Connection, to test the configuration.
  • A Connection successful message will be displayed on screen along with the time stamp.