AWS cognito: Grammar and heading fixes in user pool security overview
Summary
Editorial corrections: 'option like' to 'options like', 'subject to a smaller degree to attacks' to 'less subject to attacks', heading 'User pools security features' to "User pools' security features", 'send' to 'sends', and 'Case sensitvity' to 'Case sensitivity'.
Security assessment
The diff only rephrases existing security guidance (public sign-up risk, MFA, case sensitivity) for clarity and grammar; no new security feature, control, or vulnerability remediation is documented.
Evidence
+An important decision that you must make when you configure your user pool is whether to permit public sign-up and sign-in. Some user pool options like confidential clients, administrative creation and confirmation of users, and user pools without a domain are less subject to attacks over the internet. However, a common use case is public clients that accept sign-up from anyone on the internet and send all operations directly to your user pool. In any configuration, but especially in the case of these public configurations, we recommend that you plan and deploy your user pool with security features in mind. Insufficient security can also affect your AWS bill when unwanted sources create new active users or attempt to exploit existing users.
Diff
diff --git a/cognito/latest/developerguide/managing-security.md b/cognito/latest/developerguide/managing-security.md index c28f13f..2075ac3 100644 --- a//cognito/latest/developerguide/managing-security.md +++ b//cognito/latest/developerguide/managing-security.md @@ -13 +13 @@ For account-level and service-wide security guidance—the shared responsibility -An important decision that you must make when you configure your user pool is whether to permit public sign-up and sign-in. Some user pool option like confidential clients, administrative creation and confirmation of users, and user pools without a domain, are subject to a smaller degree to attacks over the internet. However, a common use case is public clients that accept sign-up from anyone on the internet and send all operations directly to your user pool. In any configuration, but especially in the case of these public configurations, we recommend that you plan and deploy your user pool with security features in mind. Insufficient security can also affect your AWS bill when unwanted sources create new active users or attempt to exploit existing users. +An important decision that you must make when you configure your user pool is whether to permit public sign-up and sign-in. Some user pool options like confidential clients, administrative creation and confirmation of users, and user pools without a domain are less subject to attacks over the internet. However, a common use case is public clients that accept sign-up from anyone on the internet and send all operations directly to your user pool. In any configuration, but especially in the case of these public configurations, we recommend that you plan and deploy your user pool with security features in mind. Insufficient security can also affect your AWS bill when unwanted sources create new active users or attempt to exploit existing users. @@ -17 +17 @@ MFA and threat protection apply to [local users](./cognito-terms.html#terms-loca -###### User pools security features +###### User pools' security features @@ -22 +22 @@ MFA and threat protection apply to [local users](./cognito-terms.html#terms-loca -Request a code that your user pool send by email (with the Essentials or Plus feature plan) or SMS message, or from an authenticator app, to confirm user pool sign-in. +Request a code that your user pool sends by email (with the Essentials or Plus feature plan) or SMS message, or from an authenticator app, to confirm user pool sign-in. @@ -34 +34 @@ Inspect incoming traffic to your [user pool endpoints and authentication API](./ -**Case sensitvity** +**Case sensitivity**