Schema-Driven Redaction of sensitive fields in Kafka Events Using AsyncAPI

on YouTube ↗23m

" summary

Claims a schema-first system that uses AsyncAPI vendor extensions like x-acme-redact:true to mark sensitive fields and a parser that loads the spec into an in-memory map used by a custom Deserializer on Kafka consumers. Modifying the AsyncAPI file (not code) immediately changes runtime redaction, the demo shows redacted payloads returned to the consumer, and latency impact is minimal while governance and automatic evolution replace hardcoded field lists.

AI-written summary · about

" chapters (9)

1. 0:00Introduction
2. 1:52Sensitive data in logs
3. 3:19Manual redaction challenges
4. 5:31Schema-driven redaction with AsyncAPI
5. 7:14Custom deserializer
6. 9:25Live demo
7. 12:40Advantages of schema-driven
8. 13:42Key takeaways and IBM’s solution
9. 18:55Q&A

" related talks

• 07mDescribing Kafka security in AsyncAPIDale Lane · AsyncAPI Conference 2021
• 23mSharing the wealth, socialising Kafka event sources in an organisationS. Saeed, N. Townsend · AsyncAPI Conference 2021
• 38mStreaming with StructureKatherine Stanley · GOTOpia February 2021
• 26mKafka in the WildLaura Schornack, Maureen Penzenik · GOTOpia Chicago 2021
• 51mClient-Side Field-Level Encryption for Apache Kafka ConnectHans-Peter Grahsl · Voxxed Days Luxembourg 2022
• 32mBuilding a Real-time Ingestion Platform using Kafka and AerospikeMatteo Pelati · Aerospike Virtual Summit ’20
• 39mModern Event-driven Architecture: Adopting Data in MotionAlex Stuart · GOTO EDA Day 2022
• 23mSimplifying Kafka Governance for DevelopersMuralidhar Basani · Conf42 DevSecOps 2023