Securing your messaging networks: What needs protecting and how?
summary
Covers concrete controls: broker authentication options (username/password, Kerberos, OIDC/OAuth2 tokens, mutual TLS), TLS for transport plus the operational pain of certificate lifecycle and need for automated certificate management, choices for at-rest protection (disk encryption versus application or end-to-end encryption like HashiCorp services), HA and auditing as part of security, and standards gaps around cross-protocol message encryption — one in six breaches use AI and MQ uses PKCS7 for message payloads and encrypts payload not properties.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 1:50Why securing data matters
- 4:59Focus areas in messaging security
- 8:09Broker authentication & authorization
- 9:12TLS for communication lines
- 10:36Data at rest security
- 13:21High availability as security
- 14:49Zero trust for messaging
- 17:38Auditing and monitoring
- 18:23Security agility
- 21:20Balancing security & usability
- 22:44Conclusion
related talks
47mSecure messaging - how to protect yourself & your company
44mBeyond End to End Encryption
49mSecure System Integrations
56mDeep dive into data streaming security
37mSecurity Holes in the Integration and Management of Messaging Protocols on Commercial IoT Clouds
57mHow Do I Secure My Micro-Services?
30mSecuring the Connected World - Detangling Encryption and Decryption
38mTop 10 Security Best Practices to secure your Microservices