AWS network-firewall documentation change
Summary
Removed details about requiring API requests to be signed with IAM access keys or AWS STS temporary credentials
Security assessment
The removed lines described standard AWS security practices for API authentication. Their removal does not indicate a vulnerability fix, but rather simplifies documentation. However, deleting references to credential requirements could reduce emphasis on security best practices without concrete evidence of a security incident.
Diff
diff --git a/network-firewall/latest/developerguide/infrastructure-security.md b/network-firewall/latest/developerguide/infrastructure-security.md index 8832d3874..1b7b1ac7a 100644 --- a//network-firewall/latest/developerguide/infrastructure-security.md +++ b//network-firewall/latest/developerguide/infrastructure-security.md @@ -18,2 +17,0 @@ You use AWS published API calls to access Network Firewall through the network. -Additionally, requests must be signed by using an access key ID and a secret access key that is associated with an IAM principal. Or you can use the [AWS Security Token Service](https://docs.aws.amazon.com/STS/latest/APIReference/welcome.html) (AWS STS) to generate temporary security credentials to sign requests. -