Deep Dive into Data Streaming Security
summary
Concrete failure stories, precise mitigations, and measurable outcomes guide the decision: deployments use Apache Kafka, Apache Flink, Apache Iceberg; misconfigurations leak data (a public broker incident exposes Gamooga's public Kafka broker leaking 17GB, another case reveals years of delivery records); attacks exploit CVEs like CVE-2019-12399 and unauthenticated UIs; recommended fixes are specific — TLS, disk vs field vs end‑to‑end encryption, ACLs per client, network segmentation, quotas, patch cadence and auditing — and the talk gives numbers and concrete checklist items.
AI-written summary · about
chapters (13)
- 0:00Data streaming security intro
- 2:11Security bloopers awards
- 7:33Stream defenders checklist
- 9:02Payment use case Kafka Flink Iceberg
- 13:44Encryption techniques
- 21:53Access control in streaming
- 25:48Network segmentation
- 27:34Data exfiltration risks
- 30:51DDoS threats in pipelines
- 32:15AI risks and prompt injection
- 36:08Situational awareness
- 40:06Summary and certification
- 40:49Q&A
related talks
56mDeep dive into data streaming security
40mKeeping data private in real-time pipelines
43mAttacking (and Defending) Apache Kafka
33mUnderstanding the Threats and Attacks on Data Science Applications and Models
30mThe Secure Metamorphosis: Streaming Logs with Kafka and TLS
16mAnalysing Real time Activity Streams for Security
45mData Privacy for SaaS Kafka or Pulsar Offerings
46mApplication security from start to finish