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.

Attacks/Breaches

9/5/2008
05:55 AM
Connect Directly
Google+
Twitter
RSS
E-Mail
50%
50%

Health Care Provider Plugs Potential Data Leak Points

Meridian Health Hospitals's data leak prevention system helped its users protect personal information

Meridian Health Hospitals needed a way for its users to access personal and Web-based email systems at work without risking any data leaks.

The New Jersey-based health care organization -- which operates four hospitals, oversees long-term care facilities, provides home health care services, supplies health care equipment, operates a trauma center, and runs a teaching hospital -- wanted to offer its 10,000 employees in various locations the flexibility to better balance their work and home responsibilities. But the open-door networking policy had its challenges when it came to HIPAA and an industry that puts a premium on safeguarding patient information.

Meridian officials had traditionally educated employees of the risks of this setup, and had placed the necessary security protection in its primary IT systems. But there still was the danger of confidential or sensitive data seeping out the door. “We realized that if we had a data leak, it would probably come from a personal account rather than a corporate one,” says Catherine Gorman-Klug, corporate director of privacy and data security for Meridian Health.

So about two years ago, the health care provider selected a content monitoring package that would examine information flowing out of the organization and identify instances where confidential information was being breached. At the time, the market for these products was in a nascent stage, so Meridian only evaluated a few products, including those from Tablus and Vontu. It went with Tablus, which offered a lexicon specifically for the health care industry. In addition, the software’s ability to monitor Web-based email and its ease of use were key selling points.

Meridian was able to justify the $50,000 purchase by weighing its features versus a potential security breach. “The state of New Jersey has passed a very stringent and punitive ID theft protection act,” Gorman-Klug says.

The deployment of the data leakage product took a few weeks -- and had a few hiccups. Fine-tuning typically is required with these content-monitoring systems so they capture only the appropriate items and don’t generate a lot of false positives. “Initially, we turned on all of filters, so lots of messages were flagged,” Gorman-Klug says. “In retrospect, we should have gone with the high-risk items and then gradually turned on others if they were needed.”

And with the new security tool, Meridian discovered that confidential information indeed was moving around in an insecure manner. “Users were very careful with patient and employer data, but they often sent out their own information from their personal email systems without encrypting it,” Gorman-Klug says. As a result, about 30 percent of the outgoing traffic included questionable material. So Meridian made sure users were made aware of the risks and took the proper steps to prevent these types of leaks.

Meanwhile, content monitoring has evolved quickly. RSA purchased Tablus late last year and renamed the product family, to the RSA Data Loss Prevention (DLP) Suite. “So far, we have not seen any changes in customer service,” Gorman-Klug says.

In fact, the health care provider found other uses for the product, such as scanning all the data stored on users’ laptops connected to its network. The RSA tool ensures that users encrypt all of their information -- both on the laptop and on any attached devices, such as portable storage drives.

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.

  • Vontu Inc.
  • RSA Security Inc. (Nasdaq: EMC)

    Kelly Jackson Higgins is the Executive Editor of Dark Reading. She is an award-winning veteran technology and business journalist with more than two decades of experience in reporting and editing for various publications, including Network Computing, Secure Enterprise ... View Full Bio
     

    Recommended Reading:

    Comment  | 
    Print  | 
    More Insights
  • Comments
    Newest First  |  Oldest First  |  Threaded View
    COVID-19: Latest Security News & Commentary
    Dark Reading Staff 5/28/2020
    Stay-at-Home Orders Coincide With Massive DNS Surge
    Robert Lemos, Contributing Writer,  5/27/2020
    Register for Dark Reading Newsletters
    White Papers
    Video
    Cartoon Contest
    Write a Caption, Win a Starbucks Card! Click Here
    Latest Comment: Can you smell me now?
    Current Issue
    How Cybersecurity Incident Response Programs Work (and Why Some Don't)
    This Tech Digest takes a look at the vital role cybersecurity incident response (IR) plays in managing cyber-risk within organizations. Download the Tech Digest today to find out how well-planned IR programs can detect intrusions, contain breaches, and help an organization restore normal operations.
    Flash Poll
    Twitter Feed
    Dark Reading - Bug Report
    Bug Report
    Enterprise Vulnerabilities
    From DHS/US-CERT's National Vulnerability Database
    CVE-2020-11844
    PUBLISHED: 2020-05-29
    There is an Incorrect Authorization vulnerability in Micro Focus Service Management Automation (SMA) product affecting version 2018.05 to 2020.02. The vulnerability could be exploited to provide unauthorized access to the Container Deployment Foundation.
    CVE-2020-6937
    PUBLISHED: 2020-05-29
    A Denial of Service vulnerability in MuleSoft Mule CE/EE 3.8.x, 3.9.x, and 4.x released before April 7, 2020, could allow remote attackers to submit data which can lead to resource exhaustion.
    CVE-2020-7648
    PUBLISHED: 2020-05-29
    All versions of snyk-broker before 4.72.2 are vulnerable to Arbitrary File Read. It allows arbitrary file reads for users who have access to Snyk's internal network by appending the URL with a fragment identifier and a whitelisted path e.g. `#package.json`
    CVE-2020-7650
    PUBLISHED: 2020-05-29
    All versions of snyk-broker after 4.72.0 including and before 4.73.1 are vulnerable to Arbitrary File Read. It allows arbitrary file reads to users with access to Snyk's internal network of any files ending in the following extensions: yaml, yml or json.
    CVE-2020-7654
    PUBLISHED: 2020-05-29
    All versions of snyk-broker before 4.73.1 are vulnerable to Information Exposure. It logs private keys if logging level is set to DEBUG.