Ensure that your Kinesis Firehose delivery stream data records are encrypted at destination (i.e. Amazon S3) in order to meet regulatory requirements and protect your Firehose data at rest. The Firehose data records can be encrypted in the destination bucket using an AWS-managed CMK or a KMS Customer Master Key (CMK).
This rule can help you with the following compliance standards:
- PCI
- HIPAA
- GDPR
- APRA
- MAS
- NIST4
For further details on compliance standards supported by TrendAI Vision One™ Cloud Risk Management, see here.
This rule can help you work with the AWS Well-Architected Framework.
Organizations that must follow strict compliance and data security requirements often require that their data be encrypted at all times, including at rest or in transit within the AWS cloud. The encryption of Firehose data records delivered to Amazon S3 can help you meet these security requirements by providing an extra layer of protection for your data-at-rest.
Audit
To determine if your Firehose delivery stream data records are encrypted at destination, perform the following actions:
Remediation / Resolution
To ensure that your Firehose delivery stream data records are encrypted at destination (i.e. Amazon S3), perform the following actions:
References
- AWS Documentation
- Amazon Kinesis Data Firehose
- AWS KMS concepts
- Backup and Advanced Settings
- Protecting Data Using Server-Side Encryption with KMS keys Stored in AWS Key Management Service (SSE-KMS)
- AWS Command Line Interface (CLI) Documentation
- firehose
- list-delivery-streams
- describe-delivery-stream
- update-destination