AWS connect documentation change
Summary
Updated service name from 'Amazon Connect' to 'Connect Customer' in security best practices documentation
Security assessment
Purely a branding change. The actual security guidance about permission management and inherited permissions remains unchanged with no new vulnerabilities addressed.
Diff
diff --git a/connect/latest/adminguide/security-profile-best-practices.md b/connect/latest/adminguide/security-profile-best-practices.md index a50293ab3..3d9711544 100644 --- a//connect/latest/adminguide/security-profile-best-practices.md +++ b//connect/latest/adminguide/security-profile-best-practices.md @@ -7 +7 @@ -# Best practices for Amazon Connect and Contact Control Panel (CCP) security profiles +# Best practices for Connect Customer and Contact Control Panel (CCP) security profiles @@ -17 +17 @@ People with these permissions pose a risk to your contact center because they ca -Doing these things would enable someone to lock out those who need to access Amazon Connect, and allow in others who can steal customer data and damage your business. +Doing these things would enable someone to lock out those who need to access Connect Customer, and allow in others who can steal customer data and damage your business. @@ -25 +25 @@ To reduce the risk, as a best practice we recommend limiting the number of peopl -Some security profiles included inherited permissions: when you assign dedicated permissions to one object, by default permissions are granted to sub-objects. For example, when you grant dedicated permission to edit users, you also grant them permission to list all security profiles for your Amazon Connect instance. This is because to edit users, the person has access to the drop-down list of security profiles. +Some security profiles included inherited permissions: when you assign dedicated permissions to one object, by default permissions are granted to sub-objects. For example, when you grant dedicated permission to edit users, you also grant them permission to list all security profiles for your Connect Customer instance. This is because to edit users, the person has access to the drop-down list of security profiles. @@ -29 +29 @@ Before assigning security profiles, review the list of inherited permissions. - * **Understand the implications of[access control tags](https://docs.aws.amazon.com/connect/latest/adminguide/tag-based-access-control.html) before applying them to a security profile.** Applying access control tags is an advanced configuration feature that is supported by Amazon Connect and that follows the AWS shared responsibility model. Ensure that you have read the documentation and understand the implications of applying granular permission configurations. For more information, review the [AWS shared responsibilities model](https://aws.amazon.com/compliance/shared-responsibility-model/). + * **Understand the implications of[access control tags](https://docs.aws.amazon.com/connect/latest/adminguide/tag-based-access-control.html) before applying them to a security profile.** Applying access control tags is an advanced configuration feature that is supported by Connect Customer and that follows the AWS shared responsibility model. Ensure that you have read the documentation and understand the implications of applying granular permission configurations. For more information, review the [AWS shared responsibilities model](https://aws.amazon.com/compliance/shared-responsibility-model/). @@ -52 +52 @@ Security profiles -Inherited permissions for Amazon Connect and Contact Control Panel (CCP) security profiles +Inherited permissions for Connect Customer and Contact Control Panel (CCP) security profiles