AWSOverview
Overview
In order to prevent data breaches, it is advised to encrypt SageMaker Notebook instances using a KMS Key.
Remediation guidance
- Go to the SageMaker dashboard
- Create a new instance
- In the
Permissions and encryptionsection, select Customer managed key from the Encryption key drop down and enter the desired KMS Key ARN - Complete the rest of the configuration
- Copy the data from the existing notebook instance to the new one
- Once the data is copied, you can remove the old notebook instance
Service-wide remediation
Recommended when many resources are affected: fix the platform baseline first so new resources inherit the secure setting, then remediate the existing flagged resources in batches.
AWS
Use AWS Organizations guardrails, AWS Config rules or conformance packs where they fit, approved account baselines, and IaC modules so new resources inherit the secure setting.
Operational rollout
- Fix the baseline first at the account, subscription, project, cluster, or tenant scope that owns this control.
- Remediate the currently affected resources in batches, starting with internet-exposed and production assets.
- Re-scan and track approved exceptions with an owner and expiry date.
Query logic
These are the stored checks tied to this control.
Get unencrypted SageMaker notebooks
Connectors
AWS
Covered asset types
SageMakerNoteBook
Expected check: eq []
{
sageMakerNoteBooks(
where: {
kmsKey: null
}
) {...AssetFragment}
}
