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.

Comments
What Scares Me About Healthcare & Electric Power Security
Newest First  |  Oldest First  |  Threaded View
<<   <   Page 2 / 2
Thomas Claburn
50%
50%
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
50%
50%
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.
GonzSTL
50%
50%
GonzSTL,
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!!!"
RyanSepe
50%
50%
RyanSepe,
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
50%
50%
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?
RyanSepe
100%
0%
RyanSepe,
User Rank: Ninja
10/28/2014 | 12:41:37 PM
Validation
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


COVID-19: Latest Security News & Commentary
Dark Reading Staff 9/25/2020
Hacking Yourself: Marie Moe and Pacemaker Security
Gary McGraw Ph.D., Co-founder Berryville Institute of Machine Learning,  9/21/2020
Startup Aims to Map and Track All the IT and Security Things
Kelly Jackson Higgins, Executive Editor at Dark Reading,  9/22/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Special Report: Computing's New Normal
This special report examines how IT security organizations have adapted to the "new normal" of computing and what the long-term effects will be. Read it and get a unique set of perspectives on issues ranging from new threats & vulnerabilities as a result of remote working to how enterprise security strategy will be affected long term.
Flash Poll
How IT Security Organizations are Attacking the Cybersecurity Problem
How IT Security Organizations are Attacking the Cybersecurity Problem
The COVID-19 pandemic turned the world -- and enterprise computing -- on end. Here's a look at how cybersecurity teams are retrenching their defense strategies, rebuilding their teams, and selecting new technologies to stop the oncoming rise of online attacks.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-15208
PUBLISHED: 2020-09-25
In tensorflow-lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, when determining the common dimension size of two tensors, TFLite uses a `DCHECK` which is no-op outside of debug compilation modes. Since the function always returns the dimension of the first tensor, malicious attackers can ...
CVE-2020-15209
PUBLISHED: 2020-09-25
In tensorflow-lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, a crafted TFLite model can force a node to have as input a tensor backed by a `nullptr` buffer. This can be achieved by changing a buffer index in the flatbuffer serialization to convert a read-only tensor to a read-write one....
CVE-2020-15210
PUBLISHED: 2020-09-25
In tensorflow-lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, if a TFLite saved model uses the same tensor as both input and output of an operator, then, depending on the operator, we can observe a segmentation fault or just memory corruption. We have patched the issue in d58c96946b and ...
CVE-2020-15211
PUBLISHED: 2020-09-25
In TensorFlow Lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, saved models in the flatbuffer format use a double indexing scheme: a model has a set of subgraphs, each subgraph has a set of operators and each operator has a set of input/output tensors. The flatbuffer format uses indices f...
CVE-2020-15212
PUBLISHED: 2020-09-25
In TensorFlow Lite before versions 2.2.1 and 2.3.1, models using segment sum can trigger writes outside of bounds of heap allocated buffers by inserting negative elements in the segment ids tensor. Users having access to `segment_ids_data` can alter `output_index` and then write to outside of `outpu...