AWS Security ChangesHomeSearch

AWS whitepapers documentation change

Service: whitepapers · 2025-05-10 · Documentation low

File: whitepapers/latest/aws-caf-security-perspective/application-security.md

Summary

Changed 'Amazon QuickSight' to 'QuickSight' in vulnerability monitoring documentation

Security assessment

Minor product name formatting change in existing security context, but does not introduce new security documentation or address vulnerabilities.

Diff

diff --git a/whitepapers/latest/aws-caf-security-perspective/application-security.md b/whitepapers/latest/aws-caf-security-perspective/application-security.md
index cdd5e127b..15bdc5606 100644
--- a//whitepapers/latest/aws-caf-security-perspective/application-security.md
+++ b//whitepapers/latest/aws-caf-security-perspective/application-security.md
@@ -65 +65 @@ Production applications begin to adopt [Zero Trust](https://docs.aws.amazon.com/
-As you collect output from various testing tools across your environment, you can make better use of the vulnerability trending data. You can adjust key performance indicators (KPIs) where needed, and make more data-driven decisions. Centralize output data from your various testing tools using [Amazon RDS](https://aws.amazon.com/rds/), and create dashboards with Amazon QuickSight. Create KPIs to monitor and drive secure coding behavior at the team, leadership, and individual level. The focus should be on _time-of-detection_ versus time-of-remediation, recurrence of vulnerabilities, security incident remediation timings, and preventable vulnerabilities that made it into production. 
+As you collect output from various testing tools across your environment, you can make better use of the vulnerability trending data. You can adjust key performance indicators (KPIs) where needed, and make more data-driven decisions. Centralize output data from your various testing tools using [Amazon RDS](https://aws.amazon.com/rds/), and create dashboards with QuickSight. Create KPIs to monitor and drive secure coding behavior at the team, leadership, and individual level. The focus should be on _time-of-detection_ versus time-of-remediation, recurrence of vulnerabilities, security incident remediation timings, and preventable vulnerabilities that made it into production.