AWS guardduty documentation change
Summary
Removed mention of specific AWS interfaces (Console/CLI/API) from default permissions explanation
Security assessment
The change simplifies the description of default permissions but doesn't address any specific vulnerability or security incident. It removes redundant technical details about access methods without altering security recommendations or policies.
Diff
diff --git a/guardduty/latest/ug/security_iam_id-based-policy-examples.md b/guardduty/latest/ug/security_iam_id-based-policy-examples.md index 301a85fba..ad0dbe786 100644 --- a//guardduty/latest/ug/security_iam_id-based-policy-examples.md +++ b//guardduty/latest/ug/security_iam_id-based-policy-examples.md @@ -9 +9 @@ Policy best practicesUsing the consolePermissions required to enable GuardDutyAl -By default, users and roles don't have permission to create or modify GuardDuty resources. They also can't perform tasks by using the AWS Management Console, AWS Command Line Interface (AWS CLI), or AWS API. To grant users permission to perform actions on the resources that they need, an IAM administrator can create IAM policies. The administrator can then add the IAM policies to roles, and users can assume the roles. +By default, users and roles don't have permission to create or modify GuardDuty resources. To grant users permission to perform actions on the resources that they need, an IAM administrator can create IAM policies.