Email security and encryption are essential for reliable email sending. There are two major security protocols used for email delivery: SSL and TLS.
There are three encryption requirement options available to use with Start TLS:
- No TLS
- Opportunistic TLS
- Enforced TLS:
The Dynamics 365 Customer Insights - Journeys sending infrastructure uses the most flexible and reliable option, opportunistic TLS.
Customers send sensitive personal data (information about membership in a trade union) and they are not allowed to send without Forced TLS as a minimum.
Could you please enable Enforced TLS?
Comments
I'm refering to this topic in the documentation of Customer Insight - Journey Email security encryption.Currenty the Dynamics 365 Customer Insights - Journeys sending infrastructure uses the opportunistic TLS. But my current client a customer in Germany is struggeling with this way of sending emails. Their standard way of email transfer is the "enforced TSL". That's part of their enterprise policy. Right now we can't meet the requirement to send emails from CI-J with enforced TSL because their is no way to switch from one to the other option. And the client is quite unhappy with that.As their are many very conservative customers in Germany with a high sensitivity for data security and data protection I'm asking to enhance the email channel in CI-J with an option to switch to "enforced TSL" and sending out emails this way. Even if this implicates a higher rate of email which aren't send to the receiver, it provides more trust in the platform at all.
Category: Email
I would very much support this attitude, as it offers real security hereand does not put the user of this function in need of explanation to a supervisor as to what has been done to secure it, since personal data can only be transmitted in encrypted form. GDPR Art 5processed in a manner that ensures appropriate security of the personal data, including protection against unauthorised or unlawful processing and against accidental loss, destruction or damage, using appropriate technical or organisational measures (‘integrity and confidentiality’).GDPR Art. 32 is also importent
Category: Email
Please also check out: https://experience.dynamics.com/ideas/idea/?ideaid=0b459ffd-08e2-ef11-b541-7c1e52c70aaa
Category: Email