AWS wellarchitected documentation change
Summary
Changed wording from 'complete freedom' to 'ability' when describing customer control over security architecture design
Security assessment
The change appears to be a terminology clarification rather than addressing a specific security vulnerability. While discussing security architecture capabilities, there is no evidence of patching vulnerabilities or responding to security incidents. The modification adjusts emphasis but maintains the same security guidance.
Diff
diff --git a/wellarchitected/latest/maori-data-lens/md_sec-2-how-do-you-design-workload-security-for-long-term-safety.md b/wellarchitected/latest/maori-data-lens/md_sec-2-how-do-you-design-workload-security-for-long-term-safety.md index cc6513446..82bc22b73 100644 --- a//wellarchitected/latest/maori-data-lens/md_sec-2-how-do-you-design-workload-security-for-long-term-safety.md +++ b//wellarchitected/latest/maori-data-lens/md_sec-2-how-do-you-design-workload-security-for-long-term-safety.md @@ -11 +11 @@ Ransomware is a good example to consider. If you have one copy of your data and - * **MD_SEC02-BP01: Understand data protection options available through your provider to protect data at the level of control your customer wants.** Customers control how they configure their environments and secure their content, including whether they encrypt their content (at rest and in transit), and what other security features and tools they use and how they use them. AWS does not change customer configuration settings, as these settings are determined and controlled by the customer. AWS customers have the complete freedom to design their security architecture to meet their compliance needs. AWS provides the customer autonomy to decide when and how security measures are implemented in the cloud, in accordance with each customer's business needs. When choosing which option is best, you should understand the risks you are trying to mitigate, take into account both the benefits and costs of each solution, and choose a solution that meets your requirements. Choose a cloud provider that offers contractual restrictions on their access to your data and operational restrictions. AWS, for example, is one of those cloud providers who offers both. + * **MD_SEC02-BP01: Understand data protection options available through your provider to protect data at the level of control your customer wants.** Customers control how they configure their environments and secure their content, including whether they encrypt their content (at rest and in transit), and what other security features and tools they use and how they use them. AWS does not change customer configuration settings, as these settings are determined and controlled by the customer. AWS customers have the ability to design their security architecture to meet their compliance needs. AWS provides the customer autonomy to decide when and how security measures are implemented in the cloud, in accordance with each customer's business needs. When choosing which option is best, you should understand the risks you are trying to mitigate, take into account both the benefits and costs of each solution, and choose a solution that meets your requirements. Choose a cloud provider that offers contractual restrictions on their access to your data and operational restrictions. AWS, for example, is one of those cloud providers who offers both.