5 ms·
Seems odd that someone wouldn't have understood that even 10-15 years ago. Outsourced means being exposed to risk from your supplier -- by the company itself,
by rdl 13y ago
Seems odd that someone wouldn't have understood that even 10-15 years ago. Outsourced means being exposed to risk from your supplier -- by the company itself, by its employees, or by governments. Gmail has somewhat better technical security to protect from outside non-state hackers than your average self-hosted exchange server, and from insiders (the IT guy, like Snowden, may not have the same goals as the organization...), but that may or may not make up for the ease of serving a third-party communications service provider.
I still prefer well-run self-hosted mail unless:
* You have a <6 month retention policy (i.e. so ECPA's weaker protections are a non issue) (which can be specified in Google Apps for Your Domain)
* You don't have the technical competence to run your own mail server (which gets complicated in a larger organization due to HR risk), or don't have the business competence to hire a contractor to run it in-house in such a way that their staff don't become a huge risk.
There's a third way which would be a lot better for everyone, but it's not technically feasible yet -- a way to outsource some aspects of the server without giving up control.
- ricardobeat 13y agoIt would be great to have a service that could manage your mailserver configuration, tracking reputation & avoiding spam, while not having any access at all to the data itself.
- yen223 13y agoIs there any way to tell if a particular email is spam, without knowing the content or the sender of said email?
- olalonde 13y agoMaybe homomorphic encryption[0] could help here? Here's what comes up after a quick Google: http://www.eweek.com/c/a/Security/IBM-Uncovers-Encryption-Scheme-That-Could-Improve-Cloud-Security-Spam-Filtering-135413/ http://www.eweek.com/c/a/Security/IBM-Uncovers-Encryption-Sc... [0] http://en.wikipedia.org/wiki/Homomorphic_encryption http://en.wikipedia.org/wiki/Homomorphic_encryption
- ChuckMcM 13y agoIf all your actual email is encrypted then by definition spam is the unencrypted stuff. A long time ago in a different galaxy I built a PGP MTA (based on sendmail at the time) which only forwarded mail that was encrypted, and as expected it was spam free, all though these days spammers just might go to the trouble of sending it encrypted if they thought it would get through.
- csense 13y agoI'm guessing that people who only accept encrypted mail are such a small minority, you're probably safe from most spammers if you do this. People who target your company and employees specifically, maybe not. But even this could be made more difficult for spammers by only allowing access to your public key directory from trusted IP ranges. It's also a great idea from the standpoint of giving an encryption policy teeth. I'm thinking of a company where the official line is "We encrypt all our email," but then some IT screwup results in having half the company sending each other cleartext email for several quarters before anybody notices. If your mailservers reject unencrypted mail, the above scenario can't happen, because presumably people will notice when everyone's mail starts getting discarded, and it'll be fixed very quickly.
- rdl 13y agoEven just setting START TLS REQUIRED might solve your spam problem, as long as only a tiny minority of people did it. That would have the added benefit of protecting you from Yahoo Mail users, the FBI, and such. At this point, I'd consider NOT using START TLS for your MTA to be nearly as irresponsible as not using ssh instead of telnet/rsh, or not using secure passwords. It correctly pushes all the pain onto the sysadmin (and a very tiny amount of pain), rather than end users.
- bigiain 13y agoDo you know if a successful response to a START TLS command endured end-to-end TLS secured mail transport? I kinda doubt it - if for some reason your outgoing mail server connects to one of my secondary/relaying MX servers, I don't think there's any way for you to ensure that server bothers trying to set up a TLS session when it relays my mail(which I guess is mostly my problem/fault) - and similarly, if your ISP requires you to send mail via their SMTP servers (blocking port 25 isn't uncommon here) - I don't think you've got any say in whether or not that server requires TLS? (I know - I really should go and look this up myself…)
- clicks 13y agoIt could be a crowd-sourced effort -- e-mails that are spam you mark as spam and upload to some repo that is maintained by someone (a la Adblock). You keep your filters updated, and run your e-mail against the filters file.
- ricardobeat 13y agoThat's how current spam filters work, every mail server reports back to some central directories which keep tab on IPs, common subjects, keywords and other characteristics used to calculate spam scores. The trick is doing that without giving out access to message content to third-parties. http://en.wikipedia.org/wiki/The_Spamhaus_Project http://en.wikipedia.org/wiki/The_Spamhaus_Project
- rdl 13y agoYou can free ride -- receive the spam directory but not contribute. As long as your mail is representative of the overall mail corpus, that works out fine.
- eru 13y agoThat would be trivially defeated by sending everyone a slightly different spam email. (And if your encryption doesn't produce totally different files for slight changes in plaintext, it doesn't deserve that name.)
- ricardobeat 13y agoI think you're replying to the wrong comment tree. Spammers already do this today, by including your name and other data in the message, and varying the wording, but that is not enough to fool the spam blockers, and there are diminishing rewards as your addresses/IPs begin to get marked as source of spam regardless of the content.
- eru 13y agoNo, it was the right one. I was thinking about the grand-grand-fathers suggestion in relation to encryption.
- rdl 13y agoNo need to go that far. The provider just pushes code to a server the user controls. The code is trusted to just do mail server with no backdoor for the service provider to get data. That code executes in an environment trusted by the data owner, so the code is allowed to see the data and process based on it. I'm kind of tempted to do this, since we largely do this kind of thing for VPN already. Doing it with trusted execution lets the code execute on hardware owned by the service provider, but that is technically difficult and hard to prove. Just letting you run code on your own virtual machine host is a lot easier (could be a third party virtualization provider if that is what you want, but I'd at least go for colo of my own server, if not on premise.)
- clicks 13y ago> I'm kind of tempted to do this, since we largely do this kind off thing for VPN already. Take advantage of the zeitgeist rdl. You can look forward to at least one customer if you decide to go ahead with this. (me). :)
- betterunix 13y agoYes, but it is still very much in the research stages, not quite ready for real-world deployment: https://en.wikipedia.org/wiki/Fully_homomorphic_encryption https://en.wikipedia.org/wiki/Fully_homomorphic_encryption https://en.wikipedia.org/wiki/Secure_multi-party_computation https://en.wikipedia.org/wiki/Secure_multi-party_computation There is a huge amount of interest among cryptography researchers and from DARPA and the NSF.
- rdl 13y agoYeah, that wouldn't be too hard to set up. You could run arbitrary services that way -- the key would be keeping configurations totally locked down, so all config edits happen through some kind of defined interface, to let the service provider do full testing. But I don't think individual mailboxes would be very likely to cause changed in testing before deploying upgrades. You could just use the "virtual appliance" model and do virtual machine level upgrades, with data on a separate partition -- less of a hassle than testing a bunch of upgrades from smaller patches (the paranoia about breaking it is that the service provider doesn't have root, so a failed upgrade could be bad). I'd probably want encrypted backups held with the provider too, for most non sophisticated users.
- damian2000 13y agoI think he understood the risks, but basically took it as fact that the US was beholden to decent privacy laws restricting access to private (and encrypted) communications like email. One of the main arguments for using Google apps in the past is the technical level of Google's security, and protection from being hacked. But the NSA/prism leaks have raised a new question in peoples minds, in favour of keeping things in-house or at least in your own country.
- mpyne 13y agoThat's just it though, we've heard of stuff like ECHELON (which involved no warrants whatsoever) since years before this discussion would have taken place. ECPA dates to 1986! FISA dates to 1978! The insidiously loose interpretation on 4th Amendment controls for third-party communications dates back for centuries. A lot of this was just a quick Google search away, and would have been just as relevant the very year GMail was introduced. Likewise there's no theoretical reason to trust internal Google policy controls over U.S. government legal and policy controls. Even if what the author thought had been true about U.S. law actually was true, he'd still have been setting his customer up for the possibility of having their confidential data leaked (maliciously or not) or hacked into (e.g. by the always-vulnerable password reset function). That's not just a nitpick either. There have been a couple of services at work I would have liked to setup on something like Digital Ocean, Basecamp Breeze, etc. that I can't because of PII concerns. So while I'm sorry that the author made wrong assumptions I don't know what to tell him other than IANAL isn't just a five-letter acronym, and "due diligence" doesn't simply mean "hire a contractor to think about this for me".
- rdl 13y agoFISA and ECPA made things more secure than they were previously, which is the crazy part.
- dfc 13y agoFor those interested in google apps retention: http://support.google.com/a/bin/answer.py?hl=en&answer=151128 http://support.google.com/a/bin/answer.py?hl=en&answer=15112... Spoiler Alert: Apps for Business/Education only