MEDIUM

Ensure Kinesis Data Firehose has backup to S3 enabled

Firehose should backup source records to S3 even when primary destination is Redshift, Elasticsearch, or Splunk.

Security Impact

Without backup, delivery failures to primary destination result in permanent data loss.

How to Remediate

Enable S3 backup for all source records in Firehose configuration. Use separate encrypted bucket for backups.

Affected Resources

AWS::KinesisFirehose::DeliveryStreamAWS::S3::Bucket

Compliance Frameworks

Data ProtectionBusiness Continuity

How TigerGate Helps

TigerGate continuously monitors your AWS environment to detect and alert on this misconfiguration. Here's what our platform does for this specific check:

  • Continuous Scanning

    Automatically scans all Amazon Kinesis resources across your AWS accounts every hour

  • Instant Alerts

    Get notified via Slack, email, or webhooks when this misconfiguration is detected

  • One-Click Remediation

    Fix this issue directly from the TigerGate dashboard with our guided remediation

  • Compliance Evidence

    Automatically collect audit evidence for Data Protection, Business Continuity compliance

  • Drift Detection

    Get alerted if this configuration drifts back to an insecure state after remediation

Check Details

Check ID
aws-kinesis-10
Service
Amazon Kinesis
Category
Data Protection
Severity
MEDIUM

Automate This Check

TigerGate automatically scans your AWS environment for this and 575+ other security checks.

Start Free Trial

Related Amazon Kinesis Checks

View all checks
aws-kinesis-1high

Ensure Kinesis Data Streams have encryption at rest enabled

aws-kinesis-2high

Ensure Kinesis Data Streams enforce encryption in transit

aws-kinesis-3low

Ensure Kinesis Data Streams have enhanced monitoring enabled

aws-kinesis-4high

Ensure Kinesis Data Firehose delivery streams encrypt data at rest

aws-kinesis-5medium

Ensure Kinesis Data Firehose has error logging enabled