Risk
10/23/2008
12:27 AM
George V. Hulme
George V. Hulme
Commentary
50%
50%

New FTC Rules Governing Health Providers Go Into Effect Nov. 1

Are you ready? In about a week, new so-called "Red Flag Rules" from the FTC go into effect, aimed at curbing medical identity theft.

Are you ready? In about a week, new so-called "Red Flag Rules" from the FTC go into effect, aimed at curbing medical identity theft.It's a good thing, too. It seems new headlines surrounding medical identity theft surface all of the time. Just last week, a Californian pleaded guilty to federal charges for defrauding Medicare. The man allegedly used patients' Medicare identification numbers without their knowledge. His sentencing is scheduled for sometime this January, and he faces 12 years for billing the Medicare system for about $1,640,000.

Sometimes it's not outright fraud, sometimes it's just negligence on the part of hospitals themselves for failing to properly protect patient data. Consider this recent story about patients at Mary Washington Hospital, who learned it was possible for anyone to look at the private medical information of about 803 maternity patients on the hospital's online registration system. A hospital spokesperson called the incident an "anomaly." Ten years of reporting on these types of breaches tells me its a high probability of neglecting to properly secure or patch the system. While there was no medical identity theft in this specific case (that we know of), such carelessness can and will certainly lead to more incidents.

Now, the U.S. Department of Health & Human Services (HHS) is showing more interest the role health care providers can play in combating medical identity theft in the face of new Federal Trade Commission rules that go into place Nov. 1.

According to this press release, many hospitals aren't even aware of the rules:

In October, both the HHS Office for Civil Rights (OCR) and the Office of the National Coordination for Health Information Technology (ONC) signaled that stronger actions to address the issues of identity theft and particularly medical identity theft are coming.

On Oct. 10, OCR said it was examining the FTC's identity theft regulations, as questions have been raised over whether violations of the so-called "Red Flag" rules could also constitute violations of the HIPAA privacy or security rules. There also have been no decisions on whether OCR or CMS would refer cases to the FTC when they receive complaints in their HIPAA enforcement systems.

Many health care organizations are not aware that they will come under FTC authority as a result of identity theft rules that were once thought to only apply to financial institutions and other lenders.

The Red Flag rules require any organization -- including nonprofits and government agencies not traditionally subject to FTC jurisdiction -- that does not require payment at the time it provides service to establish and maintain a program to spot and address possible ID theft.

In recent weeks, the FTC said the rules also applied to health care entities.

This is good news, even if these red flag rules from the FTC do overlap with HIPAA. Why? Because too few hospitals have been fined or sanctioned for failing to properly safeguard patient data -- like Mary Washington Hospital -- by adequately putting into place the precautions necessary to make sure someone's health privacy isn't violated by an avoidable "anomaly."

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Register for Dark Reading Newsletters
Dark Reading Live EVENTS
INsecurity - For the Defenders of Enterprise Security
A Dark Reading Conference
While red team conferences focus primarily on new vulnerabilities and security researchers, INsecurity puts security execution, protection, and operations center stage. The primary speakers will be CISOs and leaders in security defense; the blue team will be the focus.
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: No, you were supposed to display UNICODE characters!
Current Issue
Security Vulnerabilities: The Next Wave
Just when you thought it was safe, researchers have unveiled a new round of IT security flaws. Is your enterprise ready?
Flash Poll
[Strategic Security Report] Assessing Cybersecurity Risk
[Strategic Security Report] Assessing Cybersecurity Risk
As cyber attackers become more sophisticated and enterprise defenses become more complex, many enterprises are faced with a complicated question: what is the risk of an IT security breach? This report delivers insight on how today's enterprises evaluate the risks they face. This report also offers a look at security professionals' concerns about a wide variety of threats, including cloud security, mobile security, and the Internet of Things.
Slideshows
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.