Amazon managed policies for Amazon GuardDuty
To add permissions to users, groups, and roles, it is easier to use Amazon managed policies than to write policies yourself. It takes time and expertise to create IAM customer managed policies that provide your team with only the permissions they need. To get started quickly, you can use our Amazon managed policies. These policies cover common use cases and are available in your Amazon Web Services account. For more information about Amazon managed policies, see Amazon managed policies in the IAM User Guide.
Amazon services maintain and update Amazon managed policies. You can't change the permissions in Amazon managed policies. Services occasionally add additional permissions to an Amazon managed policy to support new features. This type of update affects all identities (users, groups, and roles) where the policy is attached. Services are most likely to update an Amazon managed policy when a new feature is launched or when new operations become available. Services do not remove permissions from an Amazon managed policy, so policy updates won't break your existing permissions.
Additionally, Amazon supports managed policies for job functions that span multiple services. For example, the ReadOnlyAccess Amazon managed policy provides read-only access to all Amazon services and resources. When a service launches a new feature, Amazon adds read-only permissions for new operations and resources. For a list and descriptions of job function policies, see Amazon managed policies for job functions in the IAM User Guide.
Amazon managed policy: AmazonGuardDutyFullAccess
You can attach the AmazonGuardDutyFullAccess
policy to your IAM
identities.
This policy grants administrative permissions that allow a user full access to all GuardDuty actions.
Permissions details
This policy includes the following permissions.
-
GuardDuty
– Allows users full access to all GuardDuty actions. -
IAM
– Allows users to create the GuardDuty service-linked role. This allows a GuardDuty administrator to enable GuardDuty for member accounts. -
Organizations
– Allows users to designate a delegated administrator and manage members for a GuardDuty organization.
The permission to perform an iam:GetRole
action on
AWSServiceRoleForAmazonGuardDutyMalwareProtection
establishes if the
service-linked role (SLR) for Malware Protection exists in an account.
{ "Version": "2012-10-17", "Statement": [ { "Effect": "Allow", "Action": "guardduty:*", "Resource": "*" }, { "Effect": "Allow", "Action": "iam:CreateServiceLinkedRole", "Resource": "*", "Condition": { "StringLike": { "iam:AWSServiceName": [ "guardduty.amazonaws.com", "malware-protection.guardduty.amazonaws.com" ] } } }, { "Effect": "Allow", "Action": [ "organizations:EnableAWSServiceAccess", "organizations:RegisterDelegatedAdministrator", "organizations:ListDelegatedAdministrators", "organizations:ListAWSServiceAccessForOrganization", "organizations:DescribeOrganizationalUnit", "organizations:DescribeAccount", "organizations:DescribeOrganization" ], "Resource": "*" }, { "Effect": "Allow", "Action": "iam:GetRole", "Resource": "arn:aws-cn:iam::*:role/*AWSServiceRoleForAmazonGuardDutyMalwareProtection" } ] }
Amazon managed policy: AmazonGuardDutyReadOnlyAccess
You can attach the AmazonGuardDutyReadOnlyAccess
policy to your IAM
identities.
This policy grants read-only permissions that allow a user to view GuardDuty findings and details of your GuardDuty organization.
Permissions details
This policy includes the following permissions.
-
GuardDuty
– Allows users to view GuardDuty findings and perform API operations that start withGet
,List
, orDescribe
. -
Organizations
– Allows users to retrieve information about your GuardDuty organization configuration, including details of the delegated administrator account.
{ "Version": "2012-10-17", "Statement": [ { "Effect": "Allow", "Action": [ "guardduty:Describe*", "guardduty:Get*", "guardduty:List*" ], "Resource": "*" }, { "Effect": "Allow", "Action": [ "organizations:ListDelegatedAdministrators", "organizations:ListAWSServiceAccessForOrganization", "organizations:DescribeOrganizationalUnit", "organizations:DescribeAccount", "organizations:DescribeOrganization" ], "Resource": "*" } ] }
Amazon managed policy: AmazonGuardDutyServiceRolePolicy
You can't attach AmazonGuardDutyServiceRolePolicy
to your IAM entities.
This Amazon managed policy is attached to a service-linked role that allows GuardDuty to
perform actions on your behalf. For more information, see Service-linked role permissions for GuardDuty.
GuardDuty updates to Amazon managed policies
View details about updates to Amazon managed policies for GuardDuty since this service began tracking these changes. For automatic alerts about changes to this page, subscribe to the RSS feed on the GuardDuty Document history page.
Change | Description | Date |
---|---|---|
AmazonGuardDutyServiceRolePolicy – Update to an existing policy |
GuardDuty has added new permissions to allow GuardDuty to create Service-linked role for Malware Protection. This will help GuardDuty streamline the process of enabling Malware Protection. GuardDuty can now perform the following IAM action:
|
Feb 21, 2023 |
AmazonGuardDutyFullAccess – Update to an existing policy |
GuardDuty updated ARN for |
Jul 26, 2022 |
AmazonGuardDutyFullAccess – Update to an existing policy |
GuardDuty added a new GuardDuty can now perform the |
Jul 26, 2022 |
AmazonGuardDutyServiceRolePolicy – Update to an existing policy |
GuardDuty added new permissions to allow GuardDuty to use Amazon EC2 networking actions to improve findings. GuardDuty can now perform the following EC2 actions to gain information about how your EC2 instances are communicating. This information is used to improve finding accuracy.
|
Aug 3, 2021 |
GuardDuty started tracking changes |
GuardDuty started tracking changes for its Amazon managed policies. |
Aug 3, 2021 |