AWS elasticloadbalancing high security documentation change
Summary
Removed all documentation related to RFC 9151 (CNSA 1.0) security policies including policy descriptions, configuration details, cipher tables, and compliance guidance
Security assessment
The removal of RFC 9151 policy documentation indicates deprecation of security controls designed for compliance with US National Security Agency standards. This impacts customers requiring CNSA 1.0 compliance and eliminates guidance for secure cryptographic configurations meeting government standards.
Diff
diff --git a/elasticloadbalancing/latest/application/describe-ssl-policies.md b/elasticloadbalancing/latest/application/describe-ssl-policies.md index 2d45cd297..c1c433f7e 100644 --- a//elasticloadbalancing/latest/application/describe-ssl-policies.md +++ b//elasticloadbalancing/latest/application/describe-ssl-policies.md @@ -7 +7 @@ -Example describe-ssl-policies commandsTLS security policiesFIPS security policiesRFC 9151 (CNSA 1.0) security policiesFS supported policies +Example describe-ssl-policies commandsTLS security policiesFIPS security policiesFS supported policies @@ -27,2 +26,0 @@ Elastic Load Balancing uses a Secure Socket Layer (SSL) negotiation configuratio - * Security policies with RFC 9151 in their names help you comply with RFC 9151, which defines TLS requirements for the Commercial National Security Algorithm (CNSA) 1.0 suite as specified by the US National Security Agency (NSA). To help with transition, they are available in two categories: strict policies that enforce full RFC 9151 requirements, and interop policies (containing "INTEROP" in their name) that support both RFC 9151-compliant and non-RFC 9151 ciphers to facilitate gradual transition. AWS recommends starting with `ELBSecurityPolicy-TLS13-1-2-RFC9151-INTEROP4-FIPS-2023-07` to minimize disruption, then gradually moving to stricter policies as clients support RFC 9151. You can use the `tls_protocol`, `tls_cipher`, and `tls_keyexchange` fields in ALB connection logs to monitor client connections. For more information about RFC 9151, see [RFC 9151](https://datatracker.ietf.org/doc/html/rfc9151) on the IETF website. - @@ -48,2 +45,0 @@ Elastic Load Balancing uses a Secure Socket Layer (SSL) negotiation configuratio - * **RFC 9151 policy (including any interop policy)** \- Backend connections use `ELBSecurityPolicy-TLS13-1-2-RFC9151-INTEROP4-FIPS-2023-07` - @@ -83,8 +78,0 @@ Elastic Load Balancing uses a Secure Socket Layer (SSL) negotiation configuratio - * [RFC 9151 (CNSA 1.0) security policies](./describe-ssl-policies.html#rfc9151-security-policies) - - * [Protocols by policy](./describe-ssl-policies.html#rfc9151-protocols) - - * [Ciphers by policy](./describe-ssl-policies.html#rfc9151-policy-ciphers) - - * [Policies by cipher](./describe-ssl-policies.html#rfc9151-cipher-policies) - @@ -1194,293 +1181,0 @@ Cipher name | Security policies | Cipher suite -## RFC 9151 (CNSA 1.0) security policies - -Application Load Balancer supports security policies that help you comply with RFC 9151, which defines TLS requirements for the Commercial National Security Algorithm (CNSA) 1.0 suite as specified by the US National Security Agency (NSA). RFC 9151 specifies how to use the CNSA suite with TLS 1.2 and TLS 1.3 protocols, defining the cryptographic requirements for secure communications that meet government security standards. To learn more about RFC 9151, see [RFC 9151](https://datatracker.ietf.org/doc/html/rfc9151). - -RFC 9151 policies are available in two categories: - - * **Strict policies** – Enforce strict RFC 9151 cipher and signature scheme requirements. Use these when all your clients can support RFC 9151. - - * **Interop policies** – Support both RFC 9151-compliant and non-RFC 9151 ciphers and signature schemes to facilitate a gradual transition to RFC 9151 compliance. Use these when you are uncertain whether all clients can support RFC 9151, or you want to avoid disrupting clients during the transition. All interop policies contain "INTEROP" in their policy name. - - - - -AWS recommends starting with the interop policy `ELBSecurityPolicy-TLS13-1-2-RFC9151-INTEROP4-FIPS-2023-07`, which supports clients that can negotiate classical TLS 1.3, TLS 1.2, or strict RFC 9151 algorithms, minimizing disruption. You can gradually move to stricter policies as your clients can negotiate strict RFC 9151. You can leverage the `tls_protocol`, `tls_cipher`, and `tls_keyexchange` fields in ALB connection logs to monitor how clients are connecting. - -###### Important - -When you select an RFC 9151 security policy for your listener, the load balancer uses `ELBSecurityPolicy-TLS13-1-2-RFC9151-INTEROP4-FIPS-2023-07` for backend connections to targets and other services. However, the load balancer cannot guarantee or enforce RFC 9151 compliance on egress connections, including connections to targets, or customer-configured external services (such as third-party identity providers or authentication endpoints). - -It is your responsibility to ensure the following: - - * Your targets and any external services you configure can support the protocols and ciphers in the backend connection policy. - - * For strict RFC 9151 compliance between the load balancer and your targets, your targets must have RFC 9151-compliant certificates and ciphers implemented. - - * If your backend targets only support TLS 1.0 or TLS 1.1, connections will fail. You must update the protocols and ciphers on your targets to align with the ciphers supported by the `ELBSecurityPolicy-TLS13-1-2-RFC9151-INTEROP4-FIPS-2023-07` policy. - - - - -###### Contents - - * Protocols by policy - - * Ciphers by policy - - * Policies by cipher - - - - -### Protocols by policy - -The following table describes the protocols that each RFC 9151 security policy supports. - -Security policies | TLS 1.3 | TLS 1.2 | TLS 1.1 | TLS 1.0 ----|---|---|---|--- -ELBSecurityPolicy-TLS13-1-3-RFC9151-FIPS-2023-07 | Yes | No | No | No -ELBSecurityPolicy-TLS13-1-2-RFC9151-FIPS-2023-07 | Yes | Yes | No | No -ELBSecurityPolicy-TLS13-1-2-Ext0-RFC9151-FIPS-2023-07 | Yes | Yes | No | No -ELBSecurityPolicy-TLS13-1-2-RFC9151-INTEROP1-FIPS-2023-07 | Yes | Yes | No | No -ELBSecurityPolicy-TLS13-1-2-RFC9151-INTEROP2-FIPS-2023-07 | Yes | Yes | No | No -ELBSecurityPolicy-TLS13-1-2-RFC9151-INTEROP3-FIPS-2023-07 | Yes | Yes | No | No -ELBSecurityPolicy-TLS13-1-2-RFC9151-INTEROP4-FIPS-2023-07 | Yes | Yes | No | No - -### Ciphers by policy - -The following table describes the ciphers that each RFC 9151 security policy supports. - -Security policy | Ciphers ----|--- -ELBSecurityPolicy-TLS13-1-3-RFC9151-FIPS-2023-07 | - - * TLS_AES_256_GCM_SHA384 - - -ELBSecurityPolicy-TLS13-1-2-RFC9151-FIPS-2023-07 | - - * TLS_AES_256_GCM_SHA384 - * ECDHE-ECDSA-AES256-GCM-SHA384 - * ECDHE-RSA-AES256-GCM-SHA384 - - -ELBSecurityPolicy-TLS13-1-2-Ext0-RFC9151-FIPS-2023-07 | - - * TLS_AES_256_GCM_SHA384 - * ECDHE-ECDSA-AES256-GCM-SHA384 - * ECDHE-RSA-AES256-GCM-SHA384 - * AES256-GCM-SHA384 - - -ELBSecurityPolicy-TLS13-1-2-RFC9151-INTEROP1-FIPS-2023-07 | - - * TLS_AES_256_GCM_SHA384 - * TLS_AES_128_GCM_SHA256 - * ECDHE-ECDSA-AES256-GCM-SHA384 - * ECDHE-RSA-AES256-GCM-SHA384 - * ECDHE-ECDSA-AES128-GCM-SHA256 - * ECDHE-RSA-AES128-GCM-SHA256 - - -ELBSecurityPolicy-TLS13-1-2-RFC9151-INTEROP2-FIPS-2023-07 | - - * TLS_AES_256_GCM_SHA384 - * TLS_AES_128_GCM_SHA256 - * ECDHE-ECDSA-AES256-GCM-SHA384 - * ECDHE-RSA-AES256-GCM-SHA384 - * ECDHE-ECDSA-AES128-GCM-SHA256 - * ECDHE-RSA-AES128-GCM-SHA256 - * ECDHE-ECDSA-AES256-SHA384 - * ECDHE-RSA-AES256-SHA384 - * ECDHE-ECDSA-AES128-SHA256 - * ECDHE-RSA-AES128-SHA256 - - -ELBSecurityPolicy-TLS13-1-2-RFC9151-INTEROP3-FIPS-2023-07 | - - * TLS_AES_256_GCM_SHA384 - * TLS_AES_128_GCM_SHA256 - * ECDHE-ECDSA-AES256-GCM-SHA384 - * ECDHE-RSA-AES256-GCM-SHA384 - * ECDHE-ECDSA-AES256-SHA384 - * ECDHE-RSA-AES256-SHA384 - * ECDHE-ECDSA-AES256-SHA - * ECDHE-RSA-AES256-SHA - * ECDHE-ECDSA-AES128-GCM-SHA256 - * ECDHE-RSA-AES128-GCM-SHA256 - * ECDHE-ECDSA-AES128-SHA256 - * ECDHE-RSA-AES128-SHA256 - * ECDHE-ECDSA-AES128-SHA - * ECDHE-RSA-AES128-SHA - - -ELBSecurityPolicy-TLS13-1-2-RFC9151-INTEROP4-FIPS-2023-07 | - - * TLS_AES_256_GCM_SHA384 - * TLS_AES_128_GCM_SHA256 - * ECDHE-ECDSA-AES256-GCM-SHA384 - * ECDHE-RSA-AES256-GCM-SHA384 - * ECDHE-ECDSA-AES256-SHA384 - * ECDHE-RSA-AES256-SHA384 - * ECDHE-ECDSA-AES256-SHA - * ECDHE-RSA-AES256-SHA - * ECDHE-ECDSA-AES128-GCM-SHA256 - * ECDHE-RSA-AES128-GCM-SHA256 - * ECDHE-ECDSA-AES128-SHA256 - * ECDHE-RSA-AES128-SHA256 - * ECDHE-ECDSA-AES128-SHA - * ECDHE-RSA-AES128-SHA - * AES256-GCM-SHA384 - * AES256-SHA256 - * AES256-SHA - * AES128-GCM-SHA256 - * AES128-SHA256 - * AES128-SHA - - - -### Policies by cipher - -The following table describes the RFC 9151 security policies that support each cipher. - -Cipher name | Security policies | Cipher suite ----|---|--- -**OpenSSL** – TLS_AES_256_GCM_SHA384 **IANA** – TLS_AES_256_GCM_SHA384 | - - * ELBSecurityPolicy-TLS13-1-3-RFC9151-FIPS-2023-07 - * ELBSecurityPolicy-TLS13-1-2-RFC9151-FIPS-2023-07 - * ELBSecurityPolicy-TLS13-1-2-Ext0-RFC9151-FIPS-2023-07 - * ELBSecurityPolicy-TLS13-1-2-RFC9151-INTEROP1-FIPS-2023-07 - * ELBSecurityPolicy-TLS13-1-2-RFC9151-INTEROP2-FIPS-2023-07 - * ELBSecurityPolicy-TLS13-1-2-RFC9151-INTEROP3-FIPS-2023-07 - * ELBSecurityPolicy-TLS13-1-2-RFC9151-INTEROP4-FIPS-2023-07 - -| 1302 -**OpenSSL** – TLS_AES_128_GCM_SHA256 **IANA** – TLS_AES_128_GCM_SHA256 | - - * ELBSecurityPolicy-TLS13-1-2-RFC9151-INTEROP1-FIPS-2023-07 - * ELBSecurityPolicy-TLS13-1-2-RFC9151-INTEROP2-FIPS-2023-07 - * ELBSecurityPolicy-TLS13-1-2-RFC9151-INTEROP3-FIPS-2023-07 - * ELBSecurityPolicy-TLS13-1-2-RFC9151-INTEROP4-FIPS-2023-07 - -| 1301 -**OpenSSL** – ECDHE-ECDSA-AES256-GCM-SHA384 **IANA** – TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 | - - * ELBSecurityPolicy-TLS13-1-2-RFC9151-FIPS-2023-07 - * ELBSecurityPolicy-TLS13-1-2-Ext0-RFC9151-FIPS-2023-07