Add policy for AWS KMS Key Confused Deputy Protection #1449
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Background
This policy ensures that AWS KMS Key policies with service principals include conditions to prevent cross-service confused deputy issues. Without these conditions (such as aws:SourceArn, aws:SourceAccount, aws:SourceOrgID, or aws:SourceOrgPaths), attackers may exploit the policy to misuse KMS keys by impersonating trusted services.
https://docs.aws.amazon.com/IAM/latest/UserGuide/confused-deputy.html
Changes
Added a new policy: AWS.KMS.ConfusedDeputyProtection to verify that AWS KMS Key policies containing service principals include at least one of the required conditions to prevent cross-service abuse.
Testing
KMS Key Policy Without Required Conditions:
KMS Key Policy With Required Conditions:
KMS Key Policy Without Service Principal: