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.

Perimeter

12/24/2012
12:38 PM
Wendy Nather
Wendy Nather
Commentary
50%
50%

Monitoring A La Borg

What would a true infrastructure collective look like?

Imagine there’s no console. It’s easy if you try. No central server, no admin tty.

Imagine all the endpoints, living all the same …

I have this vision for the future of computing: where endpoints provide different views, perhaps based on their form factors, but they otherwise access the same data, so they’re interchangeable. Today, your mobile device is still Your Device. It’s customized the way you like it, with all of the settings and applications you prefer, and with Your Data on it.

Lending it out to someone else feels kind of icky, like lending your toothbrush. And losing it is a calamity, even if you have a backup somewhere, because once you buy a factory-new device, you have to spend time breaking it in again and putting everything back on it the way it was before.

I imagine a future where a family just has a pile of devices on the coffee table, and everyone grabs one as they need it. Or maybe there’s one in the kitchen, one in each bedroom, and a couple by the front door to grab on your way out. It wouldn’t matter which one you picked up; once you authenticated to it, the device would show you your last session and be able to access all your own data. Remember when families all shared one or two TVs and corded phones? Wasn’t that quaint?

The cloud promises this sort of interchangeability and dynamic provisioning, but only to a certain level. Vendors are working on providing roaming profiles for handheld tablets (for example, for health-care workers), but that’s for a limited set of software. Desktop virtualization is for, well, desktops. And the endpoint experience can still be completely different for the same functionality, depending on what you’re using: Why do I need an app on my mobile device just to consume the same website content that I can view in a browser on my laptop?

The final frontier is administration: We still use a hierarchy for most infrastructure. This has traditionally meant that we needed central servers with which to manage things, or something on the perimeter in a network choke point that controlled some aspect of all traffic. Well, we all know the P-word is going away; that means, in theory, that no one vantage point over the infrastructure is any better than another. It also means that an administrative console – that trusted entity which makes such a juicy target for attackers – can end up in a pretty arbitrary location.

I’ve been seeing the beginnings of peer-to-peer monitoring and administration, where you can query data that has been passed among all the components of a networked system, rather than waiting for a central entity to poll each one. This functionality is going to be vital as our use of cloud computing expands to the scale that is possible, and as we become more mobile in terms of how and where we make contact with our resources. What if you could query any given endpoint and ask, "Hey, how are we all doing today?"

For the record, I always thought it was cheating to have a Borg Queen: talk about your literal deus ex machina. It provided a central weakness that you could use to defeat what was otherwise a resilient, self-healing collective. If you can spin up one VM to replace another, then couldn’t you have VMs that knew everything that all the other ones did? Couldn’t you have VMs that watch one another for changes and alert on them?

We may not be at the point yet where all the components of a scalable infrastructure are interchangeable -- any more than our smartphones are interchangeable today. But making sure that they all have access to the same data, without having a single point of control and therefore a single point of failure, is a powerful start. Collective monitoring could be a way forward.

Wendy Nather is Research Director of the Enterprise Security Practice at the independent analyst firm 451 Research. You can find her on Twitter as @451wendy.

Wendy Nather is Research Director of the Enterprise Security Practice at independent analyst firm 451 Research. With over 30 years of IT experience, she has worked both in financial services and in the public sector, both in the US and in Europe. Wendy's coverage areas ... View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
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...