Authdnticated encryption is important, the secure key to be stored in software vault. Every encrypted content to be supported by a digital signature. If symmetric encryption is used, hmac to be created to support encrypted content.
This is awesome. Thanks. Do you have something on intro to message brokers and how setup, integrate and publish them? I know there are many videos out there but nothing comes close to your quality of explanation and reasoning.
No I don't have anything about any specific types of brokers. I've tried to be, for the most part, pretty abstract and only showing a tool/tech for illustration purposes. I will think about it though, so thanks for the feedback.
So in the end the message broker should handle the security part ,I mean dealing with common encryption key that both parts producer and consumer shall own? Thank you!
This also helps with event sourcing too, we use a solution where we have a unique key that is used in the messages metadata. Therefore once someone wants deleting we're able to remove that key instead of modifying events. Obviously the stream readers cater for the ability to understand it is deleted and act accordingly.
Authdnticated encryption is important, the secure key to be stored in software vault.
Every encrypted content to be supported by a digital signature.
If symmetric encryption is used, hmac to be created to support encrypted content.
This is awesome. Thanks. Do you have something on intro to message brokers and how setup, integrate and publish them? I know there are many videos out there but nothing comes close to your quality of explanation and reasoning.
No I don't have anything about any specific types of brokers. I've tried to be, for the most part, pretty abstract and only showing a tool/tech for illustration purposes. I will think about it though, so thanks for the feedback.
How does PCI compliance affect this?
So in the end the message broker should handle the security part ,I mean dealing with common encryption key that both parts producer and consumer shall own? Thank you!
Those are options by either at rest or in transit.
how would you do a GDPR compliant event sourced app?
Check out: www.eventstore.com/blog/protecting-sensitive-data-in-event-sourced-systems-with-crypto-shredding-1
Didn't know the message broker can do those heavy lifting job. Great explanation. Thanks a lot.
Yes, I should of also mentioned Azure Service Bus supports encryption at rest as well.
Hi, what's the name of the payment gateway you using in this video?
I'm not really referencing anything in particular.
This also helps with event sourcing too, we use a solution where we have a unique key that is used in the messages metadata. Therefore once someone wants deleting we're able to remove that key instead of modifying events. Obviously the stream readers cater for the ability to understand it is deleted and act accordingly.
Crypto shredding, right?