AWS prescriptive-guidance documentation change
Summary
Removed glossary links for 'proactive controls', 'security controls', and 'immutable' terms while keeping the definitions
Security assessment
The change only removes glossary reference links without altering security content. Proactive controls and security controls concepts remain described identically.
Diff
diff --git a/prescriptive-guidance/latest/enterprise-blueprint-factory/architecture-components.md b/prescriptive-guidance/latest/enterprise-blueprint-factory/architecture-components.md index fca7f7589..b1830f041 100644 --- a//prescriptive-guidance/latest/enterprise-blueprint-factory/architecture-components.md +++ b//prescriptive-guidance/latest/enterprise-blueprint-factory/architecture-components.md @@ -148 +148 @@ The release pipeline automates the release of blueprints as Service Catalog prod -The release pipeline includes [proactive controls](./apg-gloss.html#glossary-proactive-control) that automate security and compliance checks for your blueprints. _Proactive controls_ are designed to prevent the creation of noncompliant resources. These controls can reduce the number of security events handled by other types of [security controls](./apg-gloss.html#glossary-security-control), such as responsive and detective controls. Because proactive controls make sure that deployed resources are compliant before they are deployed, there is no detection event that requires response or remediation. +The release pipeline includes proactive controls that automate security and compliance checks for your blueprints. _Proactive controls_ are designed to prevent the creation of noncompliant resources. These controls can reduce the number of security events handled by other types of security controls, such as responsive and detective controls. Because proactive controls make sure that deployed resources are compliant before they are deployed, there is no detection event that requires response or remediation. @@ -168 +168 @@ The following are the stages of the release pipeline: - 4. **Version check** – The release pipeline performs version control based on the version strategy that is defined in the product config file. If the product version is defined as [immutable](./apg-gloss.html#glossary-immutable-infrastructure), Service Catalog inactivates the previous product version. + 4. **Version check** – The release pipeline performs version control based on the version strategy that is defined in the product config file. If the product version is defined as immutable, Service Catalog inactivates the previous product version.