Threat Intelligence

6/14/2017
09:00 PM
Connect Directly
Twitter
LinkedIn
Google+
RSS
E-Mail
50%
50%

Hospital Email Security in Critical Condition as DMARC Adoption Lags

Healthcare providers put patient data at risk by failing to protect their email domains with DMARC adoption.

Healthcare providers are slow to adopt Domain-based Message Authentication, Reporting and Conformance (DMARC) protocol, and it's dangerously compromising their email security, according to new research by the Global Cyber Alliance (GCA).

The GCA scanned nearly 100 hospitals, half for-profit and half public, to evaluate the extent of DMARC adoption. Nearly all (99%) of the largest public and private hospitals have failed to secure their email domains from threat actors.

DMARC protects against phishing attacks by verifying whether an email is truly from the domain it claims to be from. It's designed to help businesses stop spammers from using an email domain to trick customers, partners, and employees into sharing data. DMARC discloses attempts to spam, phish, or spearphish a business brand or name.

"This is particularly critical for hospitals and healthcare companies," says GCA president and CEO Philip Reitinger, of DMARC. "Your health data is actually much more valuable to someone who wants to spoof your identity than your credit data or username."

Attackers target healthcare organizations by using phishing emails with malicious attachments to target medical data stored on hospital networks. These records contain personally identifiable information like home addresses, Social Security numbers, etc.

"Most intrusions still start with email," says Reitinger. "It's still the weapon of choice for bad guys to get things they shouldn't get."

Black Hat USA returns to the fabulous Mandalay Bay in Las Vegas, Nevada, July 22-27, 2017. Click for information on the conference schedule and to register.

Verizon's 2017 Data Breach Investigations Report (DBIR) found 15% of data breaches in the last year involved healthcare businesses. Two-thirds of malware installed on healthcare networks arrived via email attachment, sent by hackers looking for personal data.

Researchers found only one of the hospitals using DMARC has deployed to a level that prevents spam from arriving in users' inboxes. Twenty-two of the 48 largest private hospitals, and six of the 50 largest public hospitals, have deployed DMARC "in a limited capacity," says Reitinger.

There are multiple levels of DMARC adoption. "Limited capacity" indicates deployment at the monitor level, which tells organizations someone is trying to spoof their customers with a fake domain name but does not block spam delivery. This is a sign hospitals want to know whether they have correctly deployed DMARC, he explains. It means they are headed in the right direction.

Reitinger cites several reasons for slow DMARC adoption. "Part of the problem is awareness, part of it is incentive," he says, noting that some people aren't aware of DMARC at all.

Incentive is a powerful motivator for CEOs and CFOs worried about customer trust. CISOs and CIOs can deploy DMARC and prevent customers from getting phished, but they aren't the executives interacting with consumers. The CEO relies on emails going through and therefore has more incentive to ensure DMARC is deployed effectively.

"Email is still the main way businesses communicate online and you want to make sure you do it right," says Reitinger. Many organizations are worried they will make mistakes and prevent emails from going through.

"DMARC, at least for small and medium-sized businesses, is not that complicated to deploy," he explains. "It's more complicated, and takes more effort, for bigger entities. It depends on how complicated the infrastructure you use to send mail is."

Healthcare isn't the only industry lagging in DMARC adoption, he continues. Most businesses are still in monitoring mode. Reitinger's statements echo findings from the Federal Trade Commission, which conducted research on 500 businesses to evaluate usage of DMARC, Sender Policy Framework (SPF), and DomainKeys Identified Mail (DKIM).

The FTC discovered most (86%) of organizations use SPF to verify IP addresses and DKIM for digital signatures. Only one-third use DMARC, and less than 10% are using the strongest available setting, which tells recipients to reject unauthenticated messages.

Related Content:

Kelly Sheridan is Associate Editor at Dark Reading. She started her career in business tech journalism at Insurance & Technology and most recently reported for InformationWeek, where she covered Microsoft and business IT. Sheridan earned her BA at Villanova University. View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Threaded  |  Newest First  |  Oldest First
5 Reasons the Cybersecurity Labor Shortfall Won't End Soon
Steve Morgan, Founder & CEO, Cybersecurity Ventures,  12/11/2017
Oracle Product Rollout Underscores Need for Trust in the Cloud
Kelly Sheridan, Associate Editor, Dark Reading,  12/11/2017
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: Gee, these virtual reality goggles work great!!! 
Current Issue
The Year in Security: 2017
A look at the biggest news stories (so far) of 2017 that shaped the cybersecurity landscape -- from Russian hacking, ransomware's coming-out party, and voting machine vulnerabilities to the massive data breach of credit-monitoring firm Equifax.
Flash Poll
[Strategic Security Report] How Enterprises Are Attacking the IT Security Problem
[Strategic Security Report] How Enterprises Are Attacking the IT Security Problem
Enterprises are spending more of their IT budgets on cybersecurity technology. How do your organization's security plans and strategies compare to what others are doing? Here's an in-depth look.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2017-0290
Published: 2017-05-09
NScript in mpengine in Microsoft Malware Protection Engine with Engine Version before 1.1.13704.0, as used in Windows Defender and other products, allows remote attackers to execute arbitrary code or cause a denial of service (type confusion and application crash) via crafted JavaScript code within ...

CVE-2016-10369
Published: 2017-05-08
unixsocket.c in lxterminal through 0.3.0 insecurely uses /tmp for a socket file, allowing a local user to cause a denial of service (preventing terminal launch), or possibly have other impact (bypassing terminal access control).

CVE-2016-8202
Published: 2017-05-08
A privilege escalation vulnerability in Brocade Fibre Channel SAN products running Brocade Fabric OS (FOS) releases earlier than v7.4.1d and v8.0.1b could allow an authenticated attacker to elevate the privileges of user accounts accessing the system via command line interface. With affected version...

CVE-2016-8209
Published: 2017-05-08
Improper checks for unusual or exceptional conditions in Brocade NetIron 05.8.00 and later releases up to and including 06.1.00, when the Management Module is continuously scanned on port 22, may allow attackers to cause a denial of service (crash and reload) of the management module.

CVE-2017-0890
Published: 2017-05-08
Nextcloud Server before 11.0.3 is vulnerable to an inadequate escaping leading to a XSS vulnerability in the search module. To be exploitable a user has to write or paste malicious content into the search dialogue.