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
A Building Code For Internet of Things Security, Privacy
Newest First  |  Oldest First  |  Threaded View
dhaivid3
50%
50%
dhaivid3,
User Rank: Apprentice
3/17/2015 | 11:20:45 AM
Re: lame > Who's got a better name for the IoT?
Ooh, the acronyms are going to keep coming out of the woodwork. The papers "The Things in the Internet of Things" and "Things in the Internet of Things: Towards a Definition" are some of the recent attempts to get to the core of the keyword 'Things' in the IoT phrase, and that is just ONE part of the phrase.
Marilyn Cohodas
50%
50%
Marilyn Cohodas,
User Rank: Strategist
3/10/2015 | 8:55:21 AM
Re: lame > Who's got a better name for the IoT?
I always thought "Internet of Things" was just an abbreviated 'Internet of Everything." But you are right, 1eustace, another buzz word willl no doubt enter our vocabulary and be just as annoying. The good news is that some of the most overused cliches have practically disappeared. Remember the Information Highway? #cringe
1eustace
50%
50%
1eustace,
User Rank: Strategist
3/9/2015 | 3:28:57 PM
Re: lame > Who's got a better name for the IoT?
Don't worry, it's potential replacement "Internet of Everything" or IoE is already taking roots and soon you will read about IoT as much as you read about M2M today.  Point is it is a concept (connectivity and its evolution) with appellation to feed the latest buzz.  I'll bet it's replacement will be no less annoying.  
prospecttoreza
50%
50%
prospecttoreza,
User Rank: Strategist
3/6/2015 | 9:42:42 AM
How come connected medical devices are 'fast emerging'?
They've been around for years and years. Besides, were is 'the building code' ??? I thought there will be at least a passing reference to the actual standard or best practices. Very disappointing.
Marilyn Cohodas
50%
50%
Marilyn Cohodas,
User Rank: Strategist
3/5/2015 | 10:20:07 AM
Re: lame > Who's got a better name for the IoT?
Agree that the term is gattinga tad overused, but it is a pretty good description of the next (or current) big thing in technology. Anyone have a better idea?
n0md3plum
50%
50%
n0md3plum,
User Rank: Apprentice
3/4/2015 | 7:36:10 PM
lame
I hate that term "Internet of things".


Why Vulnerable Code Is Shipped Knowingly
Chris Eng, Chief Research Officer, Veracode,  11/30/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
2021 Top Enterprise IT Trends
We've identified the key trends that are poised to impact the IT landscape in 2021. Find out why they're important and how they will affect you today!
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-27348
PUBLISHED: 2020-12-04
In some conditions, a snap package built by snapcraft includes the current directory in LD_LIBRARY_PATH, allowing a malicious snap to gain code execution within the context of another snap if both plug the home interface or similar. This issue affects snapcraft versions prior to 4.4.4, prior to 2.43...
CVE-2020-16123
PUBLISHED: 2020-12-04
An Ubuntu-specific patch in PulseAudio created a race condition where the snap policy module would fail to identify a client connection from a snap as coming from a snap if SCM_CREDENTIALS were missing, allowing the snap to connect to PulseAudio without proper confinement. This could be exploited by...
CVE-2018-21270
PUBLISHED: 2020-12-03
Versions less than 0.0.6 of the Node.js stringstream module are vulnerable to an out-of-bounds read because of allocation of uninitialized buffers when a number is passed in the input stream (when using Node.js 4.x).
CVE-2020-26248
PUBLISHED: 2020-12-03
In the PrestaShop module "productcomments" before version 4.2.1, an attacker can use a Blind SQL injection to retrieve data or stop the MySQL service. The problem is fixed in 4.2.1 of the module.
CVE-2020-29529
PUBLISHED: 2020-12-03
HashiCorp go-slug before 0.5.0 does not address attempts at directory traversal involving ../ and symlinks.