Cloud

10/31/2017
03:09 PM
Connect Directly
Twitter
LinkedIn
Google+
RSS
E-Mail
0%
100%

Office 365 Missed 34,000 Phishing Emails Last Month

Nearly 10% of emails delivered to Office 365 inboxes were spam, phishing messages, and known or zero-day malware.

Microsoft Office 365 missed 9.3% emails containing spam, phishing, and malware from the beginning of September through early October, report Cyren researchers, who analyzed 10.7 million messages.

The threat intelligence firm gauges clients' email security with its Email Security Gap Analysis tool. Inbound emails are processed by its email security system, and all messages that go on to users' inboxes are BCC'd to Cyren's system for automated analysis.

"It's a standard engagement we have with clients," says Pete Starr, Cyren's director of field engineering. "But occasionally we get some interesting nuggets of information." Researchers were curious about how Office 365 was performing, which led to evaluating its security.

During the month of September, Cyren analyzed 10.7 million emails forwarded by Office 365 to user mailboxes for companies tested during that time frame. Of the messages evaluated, 9.75 million (90.7%) were found to be clean. This included 4.6 million newsletter emails, which made up nearly half of legitimate email traffic.

Nearly one million (9.3% of) messages were spam or malicious emails missed by Office 365, says Cyren, noting that the standard Office365 email service has Exchange Online Protection (EOP) to protect against malware and spam. The "false negatives" should not have made it to inboxes.

Researchers found 957,039 emails, or 8.93% of all email traffic, turned out to be spam. Usually, these messages are filtered out through content scanning or pattern detection applied to elements of the email message or its distribution pattern.

Spam aside, 34,077 emails delivered to Office 365 users were phishing messages. Of these, 18,052 were financial phishing emails requesting banking details or account access, 5,424 were password phishing emails, and 10,601 were general phishing emails.

"The biggest shock was just how much was coming through," says Starr. "Yes, the majority of it is spam, but quite a lot is something you don't want."

He refers to the malware attachments found on 3,900 emails delivered to users. While a tiny percentage (0.04%) of all emails delivered, it's also the most dangerous. Of those malware emails, 1,438 were zero-day attachments with no previously known malware signatures. However, malware attached to 2,462 emails was known and should have been detected.

"What really surprised me was the two-and-a-half thousand samples of known malware," Starr says. "Stuff caught by basic, signature-based detection. You expect that kind of stuff to be filtered out."

Is the customer at fault, or is Microsoft? Starr puts some blame on both parties. "Your average Office 365 customer is less well-configured; they perhaps don’t have the best policies on average," he explains.

However, he continues, Microsoft's solution is particularly reliant on reputation-based filtering, meaning the extent of their knowledge is only as good as their database. Today, with the rise of distributed attacks involving malware, phishing, spam, and botnets, many machines involved are fresh IPs. There's a good chance they won't exist inside an IP reputation database, he says.

"Being able to track new IPs is very, very difficult," says Starr. "You find out about them when it's too late."

For businesses hoping to improve their email security, he advises being more sensible about whitelists, noting that many organizations are too broad when adding domain names to their whitelists and letting potentially harmful messages in.

Another mistake is not appreciating how much valid email exists in other languages, like Chinese or Russian. "People either completely block, or completely allow them," he adds, suggesting users take full advantage of email features to set more specific filters.

Related Content:

Join Dark Reading LIVE for two days of practical cyber defense discussions. Learn from the industry’s most knowledgeable IT security experts. Check out the INsecurity agenda here.

Kelly Sheridan is the Staff Editor at Dark Reading, where she focuses on cybersecurity news and analysis. She is a business technology journalist who previously reported for InformationWeek, where she covered Microsoft, and Insurance & Technology, where she covered financial ... View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
marklas1
100%
0%
marklas1,
User Rank: Apprentice
11/2/2017 | 3:08:11 PM
Re: Very low on usable and/or verifiable details
My first thought was regarding ATP and whether or not it was being used.  No email system offers anything beyond some basic features.  You will need to add an additional service to actually get ahead of the problem.
cdansbee
50%
50%
cdansbee,
User Rank: Apprentice
11/2/2017 | 11:33:21 AM
Re: Very low on usable and/or verifiable details
Agree completely! This article fails to produce any actual findings from any sources other than Microsoft's competition. Unfortunately, people will read the headline and jump to the conclusion that EOL is not a good option, which seems to be what the author is after. 

It seems Dark Reading may be chasing headlines on this one.
dmstork
100%
0%
dmstork,
User Rank: Strategist
11/1/2017 | 9:18:32 AM
Very low on usable and/or verifiable details
Unfortunatly the research paper is very low on details, which exact settings where used in Office 365 (default settings tend to change for new tenants) and whether or not Office 365 Advanced Threat Protection was added. Also, the exact setup is a little bit questionable as there are multiple layers of scanning (even down to mailbox level) that scanning takes place (also after the mail landed in the mailbox).

But looking at their website, it becomes clear that Exchange Online Protection is actually a direct competitor of theirs. That is a clear conflict of interest and IMHO should've been mentioned in this article otherwise this is just an elaborate ad...
What We Talk About When We Talk About Risk
Jack Jones, Chairman, FAIR Institute,  7/11/2018
Ticketmaster Breach Part of Massive Payment Card Hacking Campaign
Jai Vijayan, Freelance writer,  7/10/2018
7 Ways to Keep DNS Safe
Curtis Franklin Jr., Senior Editor at Dark Reading,  7/10/2018
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: Locked device, Ha! I knew there was another way in.
Current Issue
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2017-15137
PUBLISHED: 2018-07-16
The OpenShift image import whitelist failed to enforce restrictions correctly when running commands such as "oc tag", for example. This could allow a user with access to OpenShift to run images from registries that should not be allowed.
CVE-2017-17541
PUBLISHED: 2018-07-16
A Cross-site Scripting (XSS) vulnerability in Fortinet FortiManager 6.0.0, 5.6.4 and below versions, FortiAnalyzer 6.0.0, 5.6.4 and below versions allows inject Javascript code and HTML tags through the CN value of CA and CRL certificates via the import CA and CRL certificates feature.
CVE-2018-1046
PUBLISHED: 2018-07-16
pdns before version 4.1.2 is vulnerable to a buffer overflow in dnsreplay. In the dnsreplay tool provided with PowerDNS Authoritative, replaying a specially crafted PCAP file can trigger a stack-based buffer overflow, leading to a crash and potentially arbitrary code execution. This buffer overflow ...
CVE-2018-10840
PUBLISHED: 2018-07-16
Linux kernel is vulnerable to a heap-based buffer overflow in the fs/ext4/xattr.c:ext4_xattr_set_entry() function. An attacker could exploit this by operating on a mounted crafted ext4 image.
CVE-2018-10857
PUBLISHED: 2018-07-16
git-annex is vulnerable to a private data exposure and exfiltration attack. It could expose the content of files located outside the git-annex repository, or content from a private web server on localhost or the LAN.