Amazon GuardDuty and AWS Organizations - AWS Organizations

Amazon GuardDuty and AWS Organizations

Amazon GuardDuty is a continuous security monitoring service that analyzes and processes a variety data sources, using threat intelligence feeds and machine learning to identify unexpected and potentially unauthorized and malicious activity within your AWS environment. This can include issues like escalations of privileges, uses of exposed credentials, or communication with malicious IP addresses, URLs, or domains.

You can help simplify management of GuardDuty by using Organizations to manage GuardDuty across all of the accounts in your organization.

For more information, see Managing GuardDuty accounts with AWS Organizations in the Amazon GuardDuty User Guide

Use the following information to help you integrate Amazon GuardDuty with AWS Organizations.

Service-linked roles created when you enable integration

The following service-linked role is automatically created in your organization's accounts when you enable trusted access. These roles allow GuardDuty to perform supported operations within the accounts in your organization.

You can delete or modify these roles only if you disable trusted access between GuardDuty and Organizations, or if you remove the member account from the organization.

  • AWSServiceRoleForAmazonGuardDuty

Service principals used by the service-linked roles

The service-linked roles in the previous section can be assumed only by the service principals authorized by the trust relationships defined for the role. The service-linked roles used by GuardDuty grant access to the following service principals:

  • guardduty.amazonaws.com

Enabling trusted access with GuardDuty

For information about the permissions needed to enable trusted access, see Permissions required to enable trusted access.

You can enable trusted access using only the Amazon GuardDuty console or tools.

You can enable trusted access using the Amazon GuardDuty console.

Amazon GuardDuty requires trusted access to AWS Organizations before you can designate a member account to be the GuardDuty administrator for your organization. If you configure a delegated administrator using the AWS Management Console, then GuardDuty automatically enables trusted access for you. However, if you want to configure a delegated administrator account using the AWS CLI or one of the AWS SDKs, then you must explicitly call the EnableAWSServiceAccess operation and provide the service principal as a parameter. Then you can call EnableOrganizationAdminAccount to delegate the GuardDuty administrator account.

Disabling trusted access with GuardDuty

For information about the permissions needed to disable trusted access, see Permissions required to disable trusted access.

You can disable trusted access using only the Organizations console or tools.

You can disable trusted access by using either the AWS Organizations console, by running an Organizations AWS CLI command, or by calling an Organizations API operation in one of the AWS SDKs.

New console

To disable trusted service access using the Organizations console

  1. Sign in to the AWS Organizations console. You must sign in as an IAM user, assume an IAM role, or sign in as the root user (not recommended) in the organization’s management account.

  2. On the Services page, find the row for Amazon GuardDuty and then choose the service’s name.

  3. Choose Enable trusted access.

  4. In the confirmation dialog box, enter disable in the box, and then choose Disable trusted access.

  5. If you are the administrator of only AWS Organizations, tell the administrator of Amazon GuardDuty that they can now disable that service using its console or tools from working with AWS Organizations.

Old console
Important

We redesigned the AWS Organizations console to make it easier to use. Starting on April 28th, 2021 the old console will no longer be available. We recommend that you switch to the new console and use the procedures in the New console tab instead.

To disable trusted service access using the Organizations console

  1. Sign in to the AWS Organizations console. You must sign in as an IAM user, assume an IAM role, or sign in as the root user (not recommended) in the organization’s management account.

  2. On the Settings tab under Trusted access for AWS services, find the row for Amazon GuardDuty and then choose Disable access.

  3. In the dialog box, choose Disable access for service-name.

  4. If you are the administrator of only AWS Organizations, tell the administrator of Amazon GuardDuty that they can now disable that service using its console or tools from working with AWS Organizations.

AWS CLI, AWS API

To disable trusted service access using the Organizations CLI/SDK

You can use the following AWS CLI commands or API operations to disable trusted service access:

Enabling a delegated administrator account for GuardDuty

When you designate a member account as a delegated administrator for the organization, users and roles from that account can perform administrative actions for GuardDuty that otherwise can be performed only by users or roles in the organization's management account. This helps you to separate management of the organization from management of GuardDuty.

Minimum permissions

For information about the permissions required to designate a member account as a delegated administrator, see Permissions required to designate a delegated administrator in the Amazon GuardDuty User Guide

To designate a member account as a delegated administrator for GuardDuty

See Designate a delegated administrator and add member accounts (console) and Designate a delegated administrator and add member accounts (API)