AWS securityhub documentation change
Summary
Removed details about request signing requirements using IAM credentials/AWS STS
Security assessment
Removal of authentication documentation could reduce clarity about security requirements, but there's no evidence this addresses a specific vulnerability. Change appears to be content reduction rather than security fix.
Diff
diff --git a/securityhub/latest/userguide/infrastructure-security.md b/securityhub/latest/userguide/infrastructure-security.md index b88434076..3abafafbb 100644 --- a//securityhub/latest/userguide/infrastructure-security.md +++ b//securityhub/latest/userguide/infrastructure-security.md @@ -18,2 +17,0 @@ You use AWS published API calls to access Security Hub through the network. Clie -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. -