AWSOverview
With server-side encryption, your Kinesis stream producers and consumers don't need to manage master keys or cryptographic operations. Your data is automatically encrypted as it enters and leaves the Kinesis Data Streams service, so your data at rest is encrypted.
Remediation guidance
AWS remediation
Console
- Open Kinesis Data Stream.
- Enable at-rest encryption with KMS.
AWS CLI
aws kinesis start-stream-encryption \
--stream-name <stream-name> \
--encryption-type KMS \
--key-id <kms-key-id-or-arn>
References
- https://docs.aws.amazon.com/streams/latest/dev/what-is-sse.html
- https://docs.aws.amazon.com/cli/latest/reference/kinesis/start-stream-encryption.html
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.
Kinesis Data Streams use encryption at rest
Connectors
AWS
Covered asset types
KinesisDataStream
Expected check: eq []
{kinesisDataStreams(where:{encryptionType:"NONE"}){...AssetFragment}}
