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 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
'Hidden Tunnels' Help Hackers Launch Financial Services Attacks
Kelly Sheridan, Staff Editor, Dark Reading,  6/20/2018
Tesla Employee Steals, Sabotages Company Data
Jai Vijayan, Freelance writer,  6/19/2018
Inside a SamSam Ransomware Attack
Ajit Sancheti, CEO and Co-Founder, Preempt,  6/20/2018
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2017-2668
PUBLISHED: 2018-06-22
389-ds-base before versions 1.3.5.17 and 1.3.6.10 is vulnerable to an invalid pointer dereference in the way LDAP bind requests are handled. A remote unauthenticated attacker could use this flaw to make ns-slapd crash via a specially crafted LDAP bind request, resulting in denial of service.
CVE-2017-7466
PUBLISHED: 2018-06-22
Ansible before version 2.3 has an input validation vulnerability in the handling of data sent from client systems. An attacker with control over a client system being managed by Ansible, and the ability to send facts back to the Ansible server, could use this flaw to execute arbitrary code on the An...
CVE-2018-12648
PUBLISHED: 2018-06-22
The WEBP::GetLE32 function in XMPFiles/source/FormatSupport/WEBP_Support.hpp in Exempi 2.4.5 has a NULL pointer dereference.
CVE-2018-12641
PUBLISHED: 2018-06-22
An issue was discovered in arm_pt in cplus-dem.c in GNU libiberty, as distributed in GNU Binutils 2.30. Stack Exhaustion occurs in the C++ demangling functions provided by libiberty, and there are recursive stack frames: demangle_arm_hp_template, demangle_class_name, demangle_fund_type, do_type, do_...
CVE-2018-12642
PUBLISHED: 2018-06-22
Froxlor through 0.9.39.5 has Incorrect Access Control for tickets not owned by the current user.