AWS neptune-analytics high security documentation change
Summary
Updated TLS requirements, removing support for TLS 1.0 and requiring TLS 1.2 or later
Security assessment
The change strengthens security requirements by removing support for older, less secure TLS versions, which is a security-related update
Diff
diff --git a/neptune-analytics/latest/userguide/infrastructure-security.md index c11a1f36f..5fd2ecaeb 100644 --- a/neptune-analytics/latest/userguide/infrastructure-security.md +++ b/neptune-analytics/latest/userguide/infrastructure-security.md @@ -9 +9 @@ As a managed service, Neptune Analytics is protected by the AWS global network s -You use AWS published API calls to access Neptune Analytics 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 Neptune Analytics through the network. Clients must support Transport Layer Security (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.