Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.


11:15 PM

Choosing Email Security Services? Watch Your Step

New Dark Reading Tech Center report offers advice on what to look for -- and what to avoid -- in third-party services

[Excerpted from "You've Got (Secure) Mail: Using Service Providers To Boost Protection," a new report published today in Dark Reading's Security Services Tech Center.]

When it comes to choosing email security services, there are some basic elements to look for -- and some basic elements to avoid. Let's take a look at each.

First, virtually all of these services run at least one (and usually more than one) traditional signature-based antivirus product. Of course, that's a bit of a misnomer -- no modern AV product operates solely on signatures. Even though traditional AV systems are no longer in vogue and are ultimately playing a losing game, they still do a lot of heavy lifting, providing protection from malicious attachments.

Second, every vendor has some form of IP reputation technology. IP reputation is a mature security measure, though new twists have sprung up around it. Blacklists for bad-acting mail servers have been around for more than a decade, though IP reputation with smarter updates and larger pools of monitored traffic raise the stakes beyond just a simple "Has this host sent spam in the last X hours?" check.

Finally, ever since spam has been a problem, spam-blocking software has been steadily learning how to identify it. Drawing from machine-learning, Bayesian inference, and fuzzy fingerprinting, a wide variety of related algorithms are churning through the massive amount of e-mail sent daily to try and predict what's bad before spam hits your network.

While it's hard to exactly compare the many different methods in use, one thing is certain -- those with the biggest databases have head starts. The better data you feed your engine, the more likely it is to correctly sort the spam from the ham.

Tread carefully if a vendor tries to sell you on e-mail whitelisting techniques. While positive security models do provide stronger defenses and are a much more promising long-term solution to malware than desktop antivirus, they simply do not apply to e-mail.

Think about it: E-mail works for the business because we receive messages from new, different people all the time. While whitelisted applications on a desktop are easily hashed and validated as legitimate, it's impossible to perfectly validate an incoming e-mail as being from the person it claims to be from. Therefore, it will be impossible to implement positive-security models in e-mail. Show any vendor selling that particular brand of snake oil the door.

Encrypting e-mail can mean different things to different vendors, and it's important to know what's being offered. First, forced TLS (transport layer security) encryption is, technically, encryption for e-mail. That said, it encrypts only one mail-server-to-mail-server connection.

The receiving mail server may be simply turning around and sending e-mail elsewhere on an unencrypted link. This feature will be attractive to companies interested in only a perfunctory level of compliance with e-mail encryption requirements. State privacy laws may be a motivator here. After all, once a message leaves your mail server, the thinking goes, it's not your fault if the receiving mail server mishandles the e-mail, right?

Well, only if you don't care about security best practices and defense in depth.

The proper solution -- and one that is increasingly becoming an popular add-on service from many vendors -- is to automatically encrypt the message content or attachment using a standard encryption engine, and rely on some other out-of-band method for transmitting key information.

While this can have a significant impact on usability, it does guarantee that e-mail leaving your organization won't be easily sniffed somewhere along the way.

Be aware, though, that pricing will vary from vendor to vendor. Most offer encryption as an add-on, but comparing plans may be difficult as the price-per seat for the feature may be rolled into a flat rate, or it may be licensed on a per-recipient or per-sender basis.

To download the full report, which includes analysis of secure e-mail services functionality and a discussion of the key differentiators between service offerings, click here.

Have a comment on this story? Please click "Discuss" below. If you'd like to contact Dark Reading's editors directly, send us a message.

Comment  | 
Print  | 
More Insights
Newest First  |  Oldest First  |  Threaded View
I 'Hacked' My Accounts Using My Mobile Number: Here's What I Learned
Nicole Sette, Director in the Cyber Risk practice of Kroll, a division of Duff & Phelps,  11/19/2019
DevSecOps: The Answer to the Cloud Security Skills Gap
Lamont Orange, Chief Information Security Officer at Netskope,  11/15/2019
Attackers' Costs Increasing as Businesses Focus on Security
Robert Lemos, Contributing Writer,  11/15/2019
Register for Dark Reading Newsletters
White Papers
Cartoon Contest
Current Issue
Navigating the Deluge of Security Data
In this Tech Digest, Dark Reading shares the experiences of some top security practitioners as they navigate volumes of security data. We examine some examples of how enterprises can cull this data to find the clues they need.
Flash Poll
Rethinking Enterprise Data Defense
Rethinking Enterprise Data Defense
Frustrated with recurring intrusions and breaches, cybersecurity professionals are questioning some of the industrys conventional wisdom. Heres a look at what theyre thinking about.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
PUBLISHED: 2019-11-22
A cross-site request forgery (CSRF) vulnerability in the Activity module 6.x-1.x for Drupal.
PUBLISHED: 2019-11-21
An issue was discovered in Symfony before 4.2.12 and 4.3.x before 4.3.8. The VarExport component incorrectly escapes strings, allowing some specially crafted ones to escalate to execution of arbitrary PHP code. This is related to symfony/var-exporter.
PUBLISHED: 2019-11-21
An issue was discovered in Symfony 2.8.0 through 2.8.50, 3.4.0 through 3.4.34, 4.2.0 through 4.2.11, and 4.3.0 through 4.3.7. The UriSigner was subject to timing attacks. This is related to symfony/http-kernel.
PUBLISHED: 2019-11-21
An issue was discovered in Symfony 2.8.0 through 2.8.50, 3.4.0 through 3.4.34, 4.2.0 through 4.2.11, and 4.3.0 through 4.3.7. If an application passes unvalidated user input as the file for which MIME type validation should occur, then arbitrary arguments are passed to the underlying file command. T...
PUBLISHED: 2019-11-21
An issue was discovered in Symfony 3.4.0 through 3.4.34, 4.2.0 through 4.2.11, and 4.3.0 through 4.3.7. Serializing certain cache adapter interfaces could result in remote code injection. This is related to symfony/cache.