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
In The Cyber Realm, Lets Be Knights Not Blacksmiths
Newest First  |  Oldest First  |  Threaded View
Jeff.schilling
50%
50%
Jeff.schilling,
User Rank: Author
7/6/2015 | 5:50:22 PM
Re: Kights with weak swords
Gary,

Thank you for your response to the article.  Great points all around.  Flawed Software is the crux of the issue.  I tell people everyday that threat actors are not doing much different from when I ran the DOD Security Ops centers from 2007-2012.  Their operational processes have gotten much more organized and their ability to leverage Zero day exploits much quicker.  

I am hopeful we will get it right when we move to IOT, which really a cloud-based, data centric model vice a network centric model we live in for the most part today.

Jeff   
Blog Voyage
100%
0%
Blog Voyage,
User Rank: Strategist
7/3/2015 | 9:06:21 AM
Re: Kights with weak swords
Very nice analysis.
GaryS166
100%
0%
GaryS166,
User Rank: Apprentice
7/2/2015 | 3:47:33 PM
Kights with weak swords
I suggest that the issue is more than not being knights (a good and important point).  Rather the idea of having swords 2-feet shorter starts to highlight the pragmatic reality.  Attackers have a large attack surface to attack, a surface that to the defender is much like an iceberg - the part we see (known vulnerabilities) is only a small part of the overall.  And we face adversaries conducting 'undersea' operations.  Moreover, the 4 IOT actions could be quite effective if (BIG IF) they are implemented such that they are correct, always invoked when needed, not bypassed, and not tampered with.  Yet if we could do that for these IOT actions, we could do it for non-IOT means as well.  And the reasons we are not would apply to the IOT actions as well.

A first principle is that a problem due to flawed software cannot be corrected by adding more flawed software.  The trustworthiness of SW is NOT determined by what it does, but by how it came to be.  And the software for the 4-IOT actions will be implemented with SW of the same low assurance as the SW it is trying to protect; unless doing differently is an explicit part of the actions to be performed.

My suggestion is - sure, absolutely pursue ideas such as your 4-IOT actions.  Yet more importantly and as mandatory for mission/business success FIRST:

a. See the reality of large low assurance IT for what it is - highly susceptible to attack and a situation that cannot, on first principles, be meaningfully changed by the addition of more low-assurance SW;

b. Use the IT we have according to what it is, not what we wish it was, making 'wise use' decisions as to what and how much to automate and having alternative mission/business processes for contingency operations;

c. Measure our cybersecurity capability against the adversary, not against our previous capability (to avoid measuring degrees of ineffectiveness and start measuring how effective we really are); and

d. Make changes to the above as the reality of the IT we use changes in a meaningful manner.

Gary Stoneburner, Senior Professional Staff, Johns Hopkins University/Applied Physics Laboratory and major contributor to NIST information security guidance (Expressing personnal judgement and not an position of my employer)


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