AWS security-lake documentation change
Summary
Simplified explanation of default permissions by removing redundant details about AWS Management Console/CLI/API access restrictions
Security assessment
The change removes specific examples of access methods (Console/CLI/API) but maintains the core security principle of least privilege. This is a documentation clarification rather than addressing a vulnerability or adding security controls.
Diff
diff --git a/security-lake/latest/userguide/security_iam_id-based-policy-examples.md b/security-lake/latest/userguide/security_iam_id-based-policy-examples.md index 4a4c5ea46..fdbdf145e 100644 --- a//security-lake/latest/userguide/security_iam_id-based-policy-examples.md +++ b//security-lake/latest/userguide/security_iam_id-based-policy-examples.md @@ -9 +9 @@ Policy best practicesUsing the Security Lake consoleExample: Allow users to view -By default, users and roles don't have permission to create or modify Security Lake 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 Security Lake resources. To grant users permission to perform actions on the resources that they need, an IAM administrator can create IAM policies.