AWS cognito low security documentation change
Summary
Changed security masking value from 'HIDDEN_FOR_SECURITY_REASONS' to 'HIDDEN_DUE_TO_SECURITY_REASONS'
Security assessment
Explicitly clarifies security masking rationale in logs. The change reinforces security auditing practices by providing more descriptive obfuscation for sensitive fields, reducing potential misinterpretation of masked data.
Diff
diff --git a/cognito/latest/developerguide/logging-using-cloudtrail.md b/cognito/latest/developerguide/logging-using-cloudtrail.md index 4ebdaabc6..bf0ff266f 100644 --- a//cognito/latest/developerguide/logging-using-cloudtrail.md +++ b//cognito/latest/developerguide/logging-using-cloudtrail.md @@ -58 +58 @@ For more information, see the [CloudTrail userIdentity element](https://docs.aws -Because user pools and identity pools process user data, Amazon Cognito obscures some private fields in your CloudTrail events with the value `HIDDEN_FOR_SECURITY_REASONS`. For examples of fields that Amazon Cognito doesn't populate to events, see [Example Amazon Cognito events](./understanding-amazon-cognito-entries.html). Amazon Cognito only obscures some fields that commonly contain user information, like passwords and tokens. Amazon Cognito doesn't perform any automatic detection or masking of personally-identifying information that you populate to non-private fields in your API requests. +Because user pools and identity pools process user data, Amazon Cognito obscures some private fields in your CloudTrail events with the value `HIDDEN_DUE_TO_SECURITY_REASONS`. For examples of fields that Amazon Cognito doesn't populate to events, see [Example Amazon Cognito events](./understanding-amazon-cognito-entries.html). Amazon Cognito only obscures some fields that commonly contain user information, like passwords and tokens. Amazon Cognito doesn't perform any automatic detection or masking of personally-identifying information that you populate to non-private fields in your API requests.