Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.iru.com/llms.txt

Use this file to discover all available pages before exploring further.

​
About Amazon GuardDuty

The Amazon GuardDuty connector collects detectors, findings, and member-account relationships for threat-detection evidence. GuardDuty must be enabled per Region - otherwise APIs legitimately return nothing. Authentication uses sts:AssumeRole into your role (typically in the administrator or delegated admin account).

​
How it works

Use AmazonGuardDutyReadOnlyAccess, or the guardduty: inline JSON below.
DetailValue
CategoryThreat detection
AuthenticationCross-account IAM role

​
Prerequisites

  • IAM rights to create roles where GuardDuty is centrally managed.
  • Detectors enabled in Regions you expect evidence from.

​
Connect AWS GuardDuty to Iru

​
Copy the trust policy from Iru

1

Open Sources

In Iru Compliance, on the left navigation bar, expand Compliance and select Sources.
Left navigation: Compliance expanded, Sources selected
2

Turn on AWS GuardDuty

Find AWS GuardDuty (use Category or Search by name or description). On that card, turn on the toggle. Leave the wizard tab open.
3

Copy the trust policy JSON

{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Effect": "Allow",
      "Principal": {
        "AWS": "arn:aws:iam::753695775620:role/IruConnect"
      },
      "Condition": {
        "StringEquals": {
          "sts:ExternalId": "YOUR_EXTERNAL_ID"
        }
      },
      "Action": "sts:AssumeRole"
    }
  ]
}

​
Create the IAM role in AWS

1

Start Create role

Open IAM → Roles → Create role.
2

Configure trusted entity

Choose AWS account → Another AWS account. Enter 753695775620 (or the ID Iru shows). Enable Require external ID and paste the external ID from Iru.
3

Attach GuardDuty read permissions

Attach AmazonGuardDutyReadOnlyAccess, or attach this inline policy:
{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Effect": "Allow",
      "Action": [
        "guardduty:Describe*",
        "guardduty:Get*",
        "guardduty:List*"
      ],
      "Resource": "*"
    }
  ]
}
4

Name the role and copy the ARN

Name the role, create it, and copy the Role ARN.

​
Submit the role ARN in Iru

1

Paste the IAM Role ARN

Paste the Role ARN into the connector where the wizard prompts for it.
2

Confirm the source is Active

Submit until AWS GuardDuty shows Active.

​
Troubleshooting

Check pop-up blocker settings for the Iru site and try again.
Enable GuardDuty detectors there first.
External ID mismatch.

​
Considerations

Detections can be cross-account: align role…

Detections can be cross-account - align role placement with your org’s delegated-admin pattern.

​
See also