AWS waf documentation change
Summary
Removed mention of specific interfaces (AWS Management Console, AWS CLI, AWS API) where default permissions prevent tasks, simplifying the explanation of default IAM permissions for Firewall Manager resources.
Security assessment
The change removes redundant details about default access restrictions but does not address a specific security vulnerability or weakness. It maintains existing security guidance about IAM policies being required for access, but does not introduce new security controls or documentation.
Diff
diff --git a/waf/latest/developerguide/fms-security_iam_id-based-policy-examples.md b/waf/latest/developerguide/fms-security_iam_id-based-policy-examples.md index 91d0c9e7b..322caecc2 100644 --- a//waf/latest/developerguide/fms-security_iam_id-based-policy-examples.md +++ b//waf/latest/developerguide/fms-security_iam_id-based-policy-examples.md @@ -13 +13 @@ You can now use the updated experience to access AWS WAF functionality anywhere -By default, users and roles don't have permission to create or modify Firewall Manager 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 Firewall Manager resources. To grant users permission to perform actions on the resources that they need, an IAM administrator can create IAM policies.