AWS Security ChangesHomeSearch

AWS controlcatalog documentation change

Service: controlcatalog · 2025-05-25 · Documentation low

File: controlcatalog/latest/userguide/infrastructure-security.md

Summary

Updated product name references from 'AWS Control Catalog' to 'Control Catalog'

Security assessment

Branding/naming changes only. Security requirements (TLS versions, cipher suites, access keys) remain unchanged. Existing security documentation is maintained but not expanded.

Diff

diff --git a/controlcatalog/latest/userguide/infrastructure-security.md b/controlcatalog/latest/userguide/infrastructure-security.md
index 03869b31c..517964f3c 100644
--- a//controlcatalog/latest/userguide/infrastructure-security.md
+++ b//controlcatalog/latest/userguide/infrastructure-security.md
@@ -7 +7 @@ Configuration and vulnerability
-# Infrastructure Security in AWS Control Catalog
+# Infrastructure Security in Control Catalog
@@ -9 +9 @@ Configuration and vulnerability
-As a managed service, AWS Control Catalog is protected by the AWS global network security procedures that are described in the [Amazon Web Services: Overview of Security Processes](https://d0.awsstatic.com/whitepapers/Security/AWS_Security_Whitepaper.pdf) whitepaper.
+As a managed service, Control Catalog is protected by the AWS global network security procedures that are described in the [Amazon Web Services: Overview of Security Processes](https://d0.awsstatic.com/whitepapers/Security/AWS_Security_Whitepaper.pdf) whitepaper.
@@ -11 +11 @@ As a managed service, AWS Control Catalog is protected by the AWS global network
-You use AWS published API calls to access AWS Control Catalog through the network. Clients must support Transport Layer Security (TLS) 1.0 or later. We recommend TLS 1.2 or later. Clients must also support cipher suites with perfect forward secrecy (PFS) such as DHE (Ephemeral Diffie-Hellman) or ECDHE (Elliptic Curve Ephemeral Diffie-Hellman). Most modern systems such as Java 7 and later support these modes.
+You use AWS published API calls to access Control Catalog through the network. Clients must support Transport Layer Security (TLS) 1.0 or later. We recommend TLS 1.2 or later. Clients must also support cipher suites with perfect forward secrecy (PFS) such as DHE (Ephemeral Diffie-Hellman) or ECDHE (Elliptic Curve Ephemeral Diffie-Hellman). Most modern systems such as Java 7 and later support these modes.
@@ -15 +15 @@ Additionally, requests must be signed by using an access key ID and a secret acc
-## Configuration and vulnerability analysis in AWS Control Catalog
+## Configuration and vulnerability analysis in Control Catalog