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
CISPA Bill: 5 Main Privacy Worries
Newest First  |  Oldest First  |  Threaded View
Andrew Hornback
50%
50%
Andrew Hornback,
User Rank: Apprentice
4/20/2012 | 2:37:52 AM
re: CISPA Bill: 5 Main Privacy Worries
On point 1 - every organization that I've been involved with has made it very clear that any information accessed or input on their systems is their property. Data that travels across their circuits (which were procured under the guise of empowering employees to do work) also becomes their property - whether they choose to examine it or not. Having built a sniffer system in the past for a previous employer, it is not only possible for them to examine that data, but also look at it in near real time. When you are using an employer's computing facilities to do personal tasks (e-mail, Facebook, eBay, etc.) you may be in violation of the terms of usage agreement that you may have signed prior to being granted access on the network. Point blank - don't use company resources for personal tasks.

On point 2 - who makes the determination as to what information should be passed along as being threat-related and who redacts that information to protect the civil liberties of the users? Then, who watches these watchers? Could turn into a downward logical spiral.

On point 3 - this really isn't a new item. Anyone, anywhere, at any time, can share any information they want with the National Security Agency. It's when the NSA or any of the other alphabet-soup organizations come looking for your information that the "rules of engagement" change.

On point 4 - it sounds to me like we either need to a) elect officials who actually know the difference between cybersecurity threats and fried green tomatoes or b) have the lobbyist groups draft the legislation and put it before a group of legislators that still don't know the difference between cybersecurity threats and fried green tomatoes. Passing legislation on things that you know little to nothing about is a recipe for disaster.

On point 5 - see point 4 and look for the fried green tomatoes. Passing legislation on things that you know little to nothing about is a recipe for disaster. I'm quite convinced that no piece of legislation in this arena is going to satisfy all parties and stakeholders. It's generally accepted that something needs to be done, but how it gets done is a point of contention that brings out the best in some people, even Anonymous, apparently.

Andrew Hornback
InformationWeek Contributor
Bprince
50%
50%
Bprince,
User Rank: Ninja
4/18/2012 | 3:56:57 PM
re: CISPA Bill: 5 Main Privacy Worries
@readers - numbers 2 and 3 touch on the issue of information sharing, which some in the critical infrastructure companies and intelligence community say there isn't enough of, while critics here say it could be dangerous. How should the balance be struck here between the need to share information and the need to protect civil liberties?
Brian Prince, InformationWeek/Dark Reading Comment Moderator


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...