AWS network-firewall documentation change
Summary
Simplified explanation of default Network Firewall permissions by removing explicit mentions of console/CLI/API access restrictions
Security assessment
The change removes specific examples of access methods (console/CLI/API) from the default permissions description but maintains the core security principle of least privilege. This appears to be a documentation simplification rather than addressing a specific vulnerability or security incident.
Diff
diff --git a/network-firewall/latest/developerguide/security_iam_id-based-policy-examples.md b/network-firewall/latest/developerguide/security_iam_id-based-policy-examples.md index 1666ae0cc..7238ca1b8 100644 --- a//network-firewall/latest/developerguide/security_iam_id-based-policy-examples.md +++ b//network-firewall/latest/developerguide/security_iam_id-based-policy-examples.md @@ -9 +9 @@ Policy best practicesUsing the consoleAllow users to view their own permissions -By default, users and roles don't have permission to create or modify Network Firewall 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 Network Firewall resources. To grant users permission to perform actions on the resources that they need, an IAM administrator can create IAM policies.