AWS inspector documentation change
Summary
Simplified explanation of default permissions by removing redundant interface examples (console/CLI/API)
Security assessment
The change removes explicit examples of access methods (console/CLI/API) but maintains the same security context about default permissions requiring IAM policies. No evidence of addressing a specific vulnerability or security incident.
Diff
diff --git a/inspector/latest/user/security_iam_id-based-policy-examples.md b/inspector/latest/user/security_iam_id-based-policy-examples.md index b4c395460..99846ba5b 100644 --- a//inspector/latest/user/security_iam_id-based-policy-examples.md +++ b//inspector/latest/user/security_iam_id-based-policy-examples.md @@ -9 +9 @@ Policy best practicesUsing the consoleAllow users to view their own permissionsA -By default, users and roles don't have permission to create or modify Amazon Inspector 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 Amazon Inspector resources. To grant users permission to perform actions on the resources that they need, an IAM administrator can create IAM policies.