AWS wickr documentation change
Summary
Condensed explanation of attribute-based access control (ABAC) and removed contextual note about ABAC's benefits in rapidly growing environments.
Security assessment
The change streamlines documentation without altering security guidance. No evidence of addressing a security flaw or introducing security-specific content.
Diff
diff --git a/wickr/latest/adminguide-classic/security_iam_service-with-iam-tags.md b/wickr/latest/adminguide-classic/security_iam_service-with-iam-tags.md index 2c9086696..ee8ac7e5d 100644 --- a//wickr/latest/adminguide-classic/security_iam_service-with-iam-tags.md +++ b//wickr/latest/adminguide-classic/security_iam_service-with-iam-tags.md @@ -11,3 +11 @@ This guide documents the classic version of the AWS Wickr administration console -Attribute-based access control (ABAC) is an authorization strategy that defines permissions based on attributes. In AWS, these attributes are called _tags_. You can attach tags to IAM entities (users or roles) and to many AWS resources. Tagging entities and resources is the first step of ABAC. Then you design ABAC policies to allow operations when the principal's tag matches the tag on the resource that they are trying to access. - -ABAC is helpful in environments that are growing rapidly and helps with situations where policy management becomes cumbersome. +Attribute-based access control (ABAC) is an authorization strategy that defines permissions based on attributes called tags. You can attach tags to IAM entities and AWS resources, then design ABAC policies to allow operations when the principal's tag matches the tag on the resource.