AWS controltower documentation change
Summary
Updated framework link and metadata documentation for compliance controls
Security assessment
Documents updates to compliance framework mappings that could impact security posture evaluation, but does not resolve active vulnerabilities.
Diff
diff --git a/controltower/latest/userguide/2025-all.md b/controltower/latest/userguide/2025-all.md index 2249d57e9..53e117a24 100644 --- a//controltower/latest/userguide/2025-all.md +++ b//controltower/latest/userguide/2025-all.md @@ -38 +38 @@ Since January 2025, AWS Control Tower has released the following updates: -With this release, AWS Control Tower expands to include support for 10 industry frameworks. For a list of frameworks, see [Frameworks supported](https://docs.aws.amazon.com/controltower/latest/controls/frameworks.html). +With this release, AWS Control Tower expands to include support for 10 industry frameworks. For a list of frameworks, see [Frameworks supported](https://docs.aws.amazon.com/controltower/latest/controlreference/frameworks-supported.html). @@ -42 +42 @@ For example, you can get started by navigating to the Control Catalog page in th -The metadata definitions associated with contols are changing, to better support these additional industry framewoks. The changes to metadata can affect the way you evaluate controls for enablement. For example, the values for NIST, PCI, and CIS metadata may have changed. We recommend that you r _eview the mappings_ for your enabled controls, on the **Control details** page in the console. +The metadata definitions associated with controls are changing, to better support these additional industry framewoks. The changes to metadata can affect the way you evaluate controls for enablement. For example, the values for NIST, PCI, and CIS metadata may have changed. We recommend that you r _eview the mappings_ for your enabled controls, on the **Control details** page in the console.