Ensure Kinesis Data Streams enforce encryption in transit
Producers and consumers should use TLS when sending/receiving data from Kinesis streams to prevent interception.
Security Impact
Unencrypted connections allow network eavesdropping on streaming data.
How to Remediate
Configure producers and consumers to use HTTPS endpoints. Enforce TLS 1.2 minimum via IAM policies if needed.
Affected Resources
Compliance Frameworks
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 PCI-DSS, HIPAA, SOC 2 compliance
- Drift Detection
Get alerted if this configuration drifts back to an insecure state after remediation
Check Details
- Check ID
- aws-kinesis-2
- Service
- Amazon Kinesis
- Category
- Encryption
- Severity
- HIGH
Automate This Check
TigerGate automatically scans your AWS environment for this and 575+ other security checks.
Start Free TrialRelated Amazon Kinesis Checks
View all checksEnsure Kinesis Data Streams have encryption at rest enabled
Ensure Kinesis Data Streams have enhanced monitoring enabled
Ensure Kinesis Data Firehose delivery streams encrypt data at rest
Ensure Kinesis Data Firehose has error logging enabled
Ensure Kinesis Data Analytics applications use VPC configuration