AWS deadline-cloud documentation change
Summary
Minor wording change from 'This includes' to 'This recommendation includes' for clarity
Security assessment
Change improves readability but doesn't address any specific security vulnerability or weakness. The content remains general security guidance without evidence of incident response.
Diff
diff --git a/deadline-cloud/latest/userguide/security-best-practices.md b/deadline-cloud/latest/userguide/security-best-practices.md index 4f96f9282..d0f46a7ea 100644 --- a//deadline-cloud/latest/userguide/security-best-practices.md +++ b//deadline-cloud/latest/userguide/security-best-practices.md @@ -34 +34 @@ For data protection purposes, we recommend that you protect AWS account credenti -We strongly recommend that you never put sensitive identifying information, such as your customers' account numbers, into free-form fields such as a **Name** field. This includes when you work with AWS Deadline Cloud or other AWS services using the console, API, AWS CLI, or AWS SDKs. Any data that you enter into Deadline Cloud or other services might get picked up for inclusion in diagnostic logs. When you provide a URL to an external server, don’t include credentials information in the URL to validate your request to that server. +We strongly recommend that you never put sensitive identifying information, such as your customers' account numbers, into free-form fields such as a **Name** field. This recommendation includes when you work with AWS Deadline Cloud or other AWS services using the console, API, AWS CLI, or AWS SDKs. Any data that you enter into Deadline Cloud or other services might get picked up for inclusion in diagnostic logs. When you provide a URL to an external server, don’t include credentials information in the URL to validate your request to that server.