This rule ensures that inline policies do not allow blocked actions on KMS keys.
Rule | Ensure inline policies attached to IAM users, roles, and groups should not allow blocked actions on KMS keys |
Framework | GxP 21 CFR Part 11 |
Severity | ✔ Medium |
Rule Description
This rule ensures that the inline policies attached to IAM users, roles, and groups do not allow blocked actions on KMS (Key Management Service) keys in compliance with GxP (Good Practice) and 21 CFR (Code of Federal Regulations) Part 11 regulations for data integrity and security.
Policy Verification Steps
Troubleshooting Steps
In case any inline policies are found that allow blocked actions on KMS keys, follow these troubleshooting steps:
Neccessary Codes
In case you need to update or modify an inline policy, here is an example of how to deny the "kms:Encrypt" action for a specific KMS key:
{ "Version": "2012-10-17", "Statement": [ { "Effect": "Deny", "Action": "kms:Encrypt", "Resource": "arn:aws:kms:region:account-id:key/key-id" } ] }
Replace "region" with the appropriate AWS region, "account-id" with your AWS account ID, and "key-id" with the ID of the KMS key you want to deny the "kms:Encrypt" action for.
Remediation Steps
To remediate the policy and align it with the rule, follow these step-by-step guide:
Identify the IAM user, role, or group whose policy needs to be remediated.
Determine whether modifying the existing inline policy or creating a new one is more appropriate for your use case.
Understand the specific actions that should be allowed or denied for the KMS keys involved.
Access the AWS Management Console or use the AWS Command Line Interface (CLI) for further actions.
If modifying an existing policy:
If creating a new policy:
By following these remediation steps, you can ensure that the inline policies attached to IAM users, roles, and groups do not allow blocked actions on KMS keys, thereby complying with GxP 21 CFR Part 11 regulations.