AWS network-firewall documentation change
Summary
Updated link text from 'AWS managed rule groups' to 'Managed rule groups' for consistency
Security assessment
Minor editorial change to section reference wording, no security implications or feature changes.
Diff
diff --git a/network-firewall/latest/developerguide/tls-inspection-considerations.md b/network-firewall/latest/developerguide/tls-inspection-considerations.md index e3e703f64..64226e576 100644 --- a//network-firewall/latest/developerguide/tls-inspection-considerations.md +++ b//network-firewall/latest/developerguide/tls-inspection-considerations.md @@ -31 +31 @@ TLS inspection is available for the request and the response for HTTPS traffic a -You can use AWS managed rules with TLS inspection. However, due to the TLS decryption, TLS keywords don't initiate inspection within the stateful engine. You can benefit from non-TLS rules within managed rule groups and find increased visibility of those rules because the decrypted traffic is visible to the inspection engine. You can also create custom rules based on inner protocols, which are available for inspection. For example, you can match with an HTTP header within the decrypted HTTPS stream. For more information about using managed rules with Network Firewall, see [AWS managed rule groups in AWS Network Firewall](./nwfw-managed-rule-groups.html). +You can use AWS managed rules with TLS inspection. However, due to the TLS decryption, TLS keywords don't initiate inspection within the stateful engine. You can benefit from non-TLS rules within managed rule groups and find increased visibility of those rules because the decrypted traffic is visible to the inspection engine. You can also create custom rules based on inner protocols, which are available for inspection. For example, you can match with an HTTP header within the decrypted HTTPS stream. For more information about using managed rules with Network Firewall, see [Managed rule groups in AWS Network Firewall](./nwfw-managed-rule-groups.html).