O365 and encrypted mail to other email systems
-
Has anyone here used MS's email encryption solution with O365?
The goal, send an encrypted email from me to someone else on a completely different server, requiring verification of ID on the other side (within reason).
Basically I'm asking if anyone has used the MS version of what Zix offers.
-
@Dashrender said in O365 and encrypted mail to other email systems:
Has anyone here used MS's email encryption solution with O365?
What solution? Exchange Online has opportunistic TLS enabled always.
-
@Dashrender said in O365 and encrypted mail to other email systems:
Has anyone here used MS's email encryption solution with O365?
These instructions tell you how to force TLS on a per domain basis.
-
I'm not talking about TLS email server to email server encryption, I'm talking about user to user encryption.
Like Zix.
-
Check this out
-
@Dashrender said in O365 and encrypted mail to other email systems:
I'm not talking about TLS email server to email server encryption, I'm talking about user to user encryption.
Like Zix.
But that's not even email. Anything like Zix can only work by not even being email. If you want something like that, you need Zix itself.
-
I realize this sits on top of Email - but it's the solution that's being called for. End users have no clue that it's not really email that makes it encrypted, nor do they care.
And while it is a pain in the ASS, Zix or MS's own encryption solution does provide a solution to those that don't use Zix or MS's solution directly.
So back to the OP - has anyone used MS's solution with O365?
-
Exchange Online is encrypted from the endpoint to the server. So when a user sends an email from inside your domain to another user inside your domain it is encrypted end-to-end.
-
@Dashrender said in O365 and encrypted mail to other email systems:
Check this out
Apparently we have it now, but we don't use it. Email is already secure to anyone who wants it to be secure, doing things like this don't really increase the security when it matters (either legally or as desired) since anyone how needs or cares would always get it encrypted and the legal responsibility ends at offering them the security at best. This type of stuff is really just marketing fluff for the non-IT types, IMHO. It adds effort and complications, raises cost and lowers the usability of email.
-
@coliver said in O365 and encrypted mail to other email systems:
Exchange Online is encrypted from the endpoint to the server. So when a user sends an email from inside your domain to another user inside your domain it is encrypted end-to-end.
Correct, I do understand this, but this is not my goal.
My goal is to, for example, send an email to you, at your email address (which isn't on my email server, or part of my domain) so that even your IT admin can't read it. Full end to end encryption.
Of course the huge failing is the initial setup of the credentials - because if the admin intercepts the original mail, he can setup the account at first time access and read at least that first message, but we'll ignore this problem for now.
-
@Dashrender said in O365 and encrypted mail to other email systems:
@coliver said in O365 and encrypted mail to other email systems:
Exchange Online is encrypted from the endpoint to the server. So when a user sends an email from inside your domain to another user inside your domain it is encrypted end-to-end.
Correct, I do understand this, but this is not my goal.
The goal isn't user-to-user encryption? I thought that was what you had stated a few posts earlier.
-
@coliver said in O365 and encrypted mail to other email systems:
Exchange Online is encrypted from the endpoint to the server. So when a user sends an email from inside your domain to another user inside your domain it is encrypted end-to-end.
More importantly, it is encrypted end to end with any normal user on the other side, as well. Basically all business and most consumer email domains are secured end to end today. So you'd have to find someone who has seriously opted out of the security to not have end to end, user to user security for email today and it would always be at the discretion of the other party. That's what's great about email today, for all intents and purposes, it is totally secure. The "email security" concerns of the past have been solved because of TLS and web interfaces.
-
@coliver said in O365 and encrypted mail to other email systems:
@Dashrender said in O365 and encrypted mail to other email systems:
@coliver said in O365 and encrypted mail to other email systems:
Exchange Online is encrypted from the endpoint to the server. So when a user sends an email from inside your domain to another user inside your domain it is encrypted end-to-end.
Correct, I do understand this, but this is not my goal.
The goal isn't user-to-user encryption? I thought that was what you had stated a few posts earlier.
I think that he stated incorrectly. That's what he has. What he actually wants is a non-transparently, individually encrypted payload that has to be decrypted manually by the end user. Like GPG.
-
@scottalanmiller said in O365 and encrypted mail to other email systems:
@coliver said in O365 and encrypted mail to other email systems:
@Dashrender said in O365 and encrypted mail to other email systems:
@coliver said in O365 and encrypted mail to other email systems:
Exchange Online is encrypted from the endpoint to the server. So when a user sends an email from inside your domain to another user inside your domain it is encrypted end-to-end.
Correct, I do understand this, but this is not my goal.
The goal isn't user-to-user encryption? I thought that was what you had stated a few posts earlier.
I think that he stated incorrectly. That's what he has. What he actually wants is a non-transparently, individually encrypted payload that has to be decrypted manually by the end user. Like GPG.
Ah, so the goal is to make email impossible to use so your users go to some other insecure method of communication.
-
Which is not actually email encryption, that's part of why these discussions go this way.
Email IS encrypted and incredibly secure. The issue here isn't based on security.
What Zix, Microsoft's solution or GPG do, actually, is encrypt a separate file that the already secure email delivery system delivers. It's payload encryption, but as the payload itself isn't actually email, the term email encryption makes this confusing. It's literally no different than using 7zip to encrypt want you want to send, just more convenient (barely.)
-
This compares to something like Barracuda Mail Encryption. It's shining point isn't really around mail in transit, but mail at rest at the destination. TLS is great until that email sits unencrypted in a recipients gmail box that 80 hackers and your kids have the password to. It's a legitimate concern as a business owner... you want it to be secure end to end.
That said, there is no requirement, HIPAA or PCI or otherwise, that places the burden of safety of that email in your hands. Once it's over the wire encrypted, it's no longer your problem. But I do understand it's value; we used Barracuda email encryption whenever we would (be forced to) send PHI to another doctor office.
-
@scottalanmiller said in O365 and encrypted mail to other email systems:
@coliver said in O365 and encrypted mail to other email systems:
@Dashrender said in O365 and encrypted mail to other email systems:
@coliver said in O365 and encrypted mail to other email systems:
Exchange Online is encrypted from the endpoint to the server. So when a user sends an email from inside your domain to another user inside your domain it is encrypted end-to-end.
Correct, I do understand this, but this is not my goal.
The goal isn't user-to-user encryption? I thought that was what you had stated a few posts earlier.
I think that he stated incorrectly. That's what he has. What he actually wants is a non-transparently, individually encrypted payload that has to be decrypted manually by the end user. Like GPG.
OK - this ^. Sadly the lawyer only consider this to be "secure email" Without this layer, sending an email is not considered secure, and fails audits.
Yes I understand all the other stated things, but they don't matter, sadly - only the audit matters.
-
I think that the sole benefit of a system like this is that you can secure the email so that your own and their own (sender and receiver) admins cannot view the mail. However, that shifts the entire burden of security management onto the receiver of the email. So it causes huge management issues because the users cannot turn to their IT departments to enable this for them and, if they do, it disables the only goal that the system can have because it reverts it to the same security as TLS before.
-
@Dashrender said in O365 and encrypted mail to other email systems:
@scottalanmiller said in O365 and encrypted mail to other email systems:
@coliver said in O365 and encrypted mail to other email systems:
@Dashrender said in O365 and encrypted mail to other email systems:
@coliver said in O365 and encrypted mail to other email systems:
Exchange Online is encrypted from the endpoint to the server. So when a user sends an email from inside your domain to another user inside your domain it is encrypted end-to-end.
Correct, I do understand this, but this is not my goal.
The goal isn't user-to-user encryption? I thought that was what you had stated a few posts earlier.
I think that he stated incorrectly. That's what he has. What he actually wants is a non-transparently, individually encrypted payload that has to be decrypted manually by the end user. Like GPG.
OK - this ^. Sadly the lawyer only consider this to be "secure email" Without this layer, sending an email is not considered secure, and fails audits.
Yes I understand all the other stated things, but they don't matter, sadly - only the audit matters.
That's fine, thanks for clarifying your goal. We have similar issues here.
-
@Dashrender said in O365 and encrypted mail to other email systems:
Yes I understand all the other stated things, but they don't matter, sadly - only the audit matters.
In that case your question should be worded around that specific context. The issue at hand is not security, email or encryption. It's tricking a lawyer who is unethically doing a job far over his head.
