Bedrock custom models produced by model customization can be encrypted at rest with a customer-managed KMS key rather than resting under an AWS-owned key the organization cannot audit, rotate, or revoke.
Risk
A fine-tuned model is derived from the training data used to build it and can leak that data through inference.
Under an AWS-owned key, the organization has no key policy to restrict who may decrypt the artifacts, no customer-controlled rotation, no CloudTrail record of key usage, and no way to revoke access to the model by disabling a key.
prowler aws --checks bedrock_custom_model_encrypted_with_cmk
Recommendation
Choose a customer-managed KMS key when creating each model customization job so the resulting custom model rests under a key with an auditable policy and rotation. The key cannot be changed after the model is created, so re-run customization for existing models.
Remediation
- Open the AWS Console and go to Amazon Bedrock
- Select Custom models, then create a new customization job
- Under encryption, choose a customer-managed KMS key instead of the default
- Grant the customization service role kms:Decrypt, kms:GenerateDataKey and kms:DescribeKey on that key
- Re-run customization, because the key of an existing custom model cannot be changed in place
Source Code
Resource Type
Other
References
Related To
- bedrock_prompt_encrypted_with_cmk