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.

What Scares Me About Healthcare & Electric Power Security
Newest First  |  Oldest First  |  Threaded View
<<   <   Page 2 / 2
Thomas Claburn
Thomas Claburn,
User Rank: Ninja
10/28/2014 | 7:08:33 PM
Re: public safety
>now it's time for the public to be better informed on this.

If only the public cared. And for those who do, the healthcare market is so screwed up that it's unlikely consumers will be able to vote with their feet -- they'll have to wait until open enrollment periods to switch providers and then they're likely to face few real choices. And if you're electricity provider is lax in its security, you probably have nowhere else to go.
Kelly Jackson Higgins
Kelly Jackson Higgins,
User Rank: Strategist
10/28/2014 | 3:40:41 PM
public safety
What worries me is that the world outside of our security bubble won't truly take security seriously until there's a tangible attack that affects public safety, etc. The increasingly networked consumer space is bringing this issue to the fore--now it's time for the public to be better informed on this.
User Rank: Ninja
10/28/2014 | 3:34:30 PM
Re: Validation
Agree completely. During security reviews of potential vendors, I've asked for SAS 70 or SSAE 16 audit results if they have a current one, or a review of their security policies. Surprisingly, one potential vendor we looked into had none of those. Can you believe that? Not even security policies! So of course we expressed a lack of interest, and the next day, they miraculously came up with rudimentary security policies specific to our request. They indicated that they simply adopted the policies of one of their business partners who gave them permission to do so. One little problem – the policies reflected the name of their business partner, and not their own company. I couldn't believe how sloppy they were and naturally, my recommendation was "NO!!!"
User Rank: Ninja
10/28/2014 | 1:18:15 PM
Re: Validation
Vendors need to receive the same scrutiny that you would provide to your own enteprise. They are handling your data. If they store your data or are connected via VPN, your corporation is taking a risk which needs to be acknowledged. Their compromise and is your compromise. You need to ensure that they follow stringent standards that you hold your own enterprise, to safeguard the data. Cryptology methods need to safeguard data in transit and at rest. Firewalls and DMZ's positioned to secure different severities of data. Active scanning to determine that no outside malicious influence has already circumvented your perimeter. There are many others, but a good template is to follow best security practices for data handling.
Marilyn Cohodas
Marilyn Cohodas,
User Rank: Strategist
10/28/2014 | 12:54:20 PM
Re: Validation
Interesting, ryan. What are some of the "measures" you are asking vendors about?
User Rank: Ninja
10/28/2014 | 12:41:37 PM
Working for a healthcare enterprise I can vouch for many of these significant mismatches. Especailly "Too much vendor trust". However, at my organization we are starting to crack down on ensuring Business Associate Agreements are signed that mandate certain measures be performed by vendors that want to do business with us. This along with legal documentation need to be present ensure that vendors are providing due diligence for data security. Vendors are concerned mainly with functionality and due to this, security tends to fall by the wayside. I feel that if vendors are held to higher standards and industry starts cracking down on the stringence of their protocols that the security initiative will be represented much better.
<<   <   Page 2 / 2

I Smell a RAT! New Cybersecurity Threats for the Crypto Industry
David Trepp, Partner, IT Assurance with accounting and advisory firm BPM LLP,  7/9/2021
Attacks on Kaseya Servers Led to Ransomware in Less Than 2 Hours
Robert Lemos, Contributing Writer,  7/7/2021
It's in the Game (but It Shouldn't Be)
Tal Memran, Cybersecurity Expert, CYE,  7/9/2021
Register for Dark Reading Newsletters
White Papers
Current Issue
Black Hat USA 2022 Attendee Report
Black Hat attendees are not sleeping well. Between concerns about attacks against cloud services, ransomware, and the growing risks to the global supply chain, these security pros have a lot to be worried about. Read our 2022 report to hear what they're concerned about now.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
PUBLISHED: 2022-08-12
Improper input validation on the `contains` LoopBack filter may allow for arbitrary SQL injection. When the extended filter property `contains` is permitted to be interpreted by the Postgres connector, it is possible to inject arbitrary SQL which may affect the confidentiality and integrity of data ...
PUBLISHED: 2022-08-12
undici is an HTTP/1.1 client, written from scratch for Node.js.`undici` is vulnerable to SSRF (Server-side Request Forgery) when an application takes in **user input** into the `path/pathname` option of `undici.request`. If a user specifies a URL such as `` or `//` ```js con...
PUBLISHED: 2022-08-12
BookWyrm is a social network for tracking your reading, talking about books, writing reviews, and discovering what to read next. Some links in BookWyrm may be vulnerable to tabnabbing, a form of phishing that gives attackers an opportunity to redirect a user to a malicious site. The issue was patche...
PUBLISHED: 2022-08-12
This Rails gem adds two methods to the ActiveRecord::Base class that allow you to update many records on a single database hit, using a case sql statement for it. Before version 0.1.3 `update_by_case` gem used custom sql strings, and it was not sanitized, making it vulnerable to sql injection. Upgra...
PUBLISHED: 2022-08-12
Shield is an authentication and authorization framework for CodeIgniter 4. This vulnerability may allow [SameSite Attackers](https://canitakeyoursubdomain.name/) to bypass the [CodeIgniter4 CSRF protection](https://codeigniter4.github.io/userguide/libraries/security.html) mechanism with CodeIgniter ...