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.

Database Security
Authentication
Mobile
Privacy
Compliance
Careers and People
Identity & Access Management
Security Monitoring
Advanced Threats
Insider Threats
Vulnerability Management
Comments
Internet Of Things: 3 Holiday Gifts That Will Keep CISOs Up At Night
Newest First  |  Oldest First  |  Threaded View
ChrisRouland
ChrisRouland,
 User Rank: Strategist
12/12/2014 | 9:16:20 AM
Re: How do we detect these devices?

Marilyn,

The MDM market is well established to help secure personal devices connected to corporate infrastructure, however host agents such as MDM's don't run on the majority of the IOT.   Broad spectrum intrusion detection, vulnerability assessment and localization will be key to managing risk around devices that are unable to run a host based security agent.

Marilyn Cohodas
Marilyn Cohodas,
 User Rank: Strategist
12/11/2014 | 4:28:21 PM
Re: How do we detect these devices?
Thanks, Chris. What do you think will be the biggest challenges with IoT in the enterprise compared to BYOD?
ChrisRouland
ChrisRouland,
 User Rank: Strategist
12/11/2014 | 10:55:04 AM
Re: How do we detect these devices?
There are certainly some short-term solutions, such as an IoT policy that segregates devices from the corporate network. Long term, however, enterprises will be responsible for implementing policies that ensure the security of their airspace, while not infringing on the personal privacy of employees, contractors, and the thousands of others who come in and out of their corporate environments each day. New technology needs to come to market to provide vulnerability assessment, intrusion detection and localization across the wide spectrum of protocols of the IoT.   With the tremendous growth of IoT, brings opportunity for innovation in security in the space.
gwilson001
gwilson001,
 User Rank: Strategist
12/10/2014 | 6:09:40 PM
Re: How do we detect these devices?
I don't think any one has policies around things like the fitness bands etc.  Policies are essential but getting people to follow them where these devices are concerned would be difficult.  You would have to update the policy everytime a new device came out that was not covered under another product category.  I can see this being a mess to manage.  Enforcement would be diufficult as well since these devices are often very small and could be tossed in a purse or backpack/gym bag and brought into the office.  Since WiFi scanners won't monitor for these devices how will we detect them? 
ODA155
ODA155,
 User Rank: Ninja
12/10/2014 | 4:15:15 PM
Re: How do we detect these devices?
@gwilson001,... I could be wrong, but I think actually "detecting" these devices is the easy part. The difficult thing for some companies would be trying to manage them or just ignoring them altogether. Personally, I'm of the mind to block ANY USB or Bluetooth device that isn't woned by the company and already registered on the network or mated with a specific computer\system. If it doesn't have a valid business need then it shouldn't be on the network regardless of who wants to use it... sometime you just have to say no.
Marilyn Cohodas
Marilyn Cohodas,
 User Rank: Strategist
12/10/2014 | 3:19:45 PM
Re: How do we detect these devices?
That/s the  million-dollar question with IoT security, @gwilson001. For an enterprise, the first step would be to create policies surrounding them. But given the popularity (& success) of BYOD policies, I'm not overly optimistic.
gwilson001
gwilson001,
 User Rank: Strategist
12/10/2014 | 2:06:39 PM
How do we detect these devices?
Interesting but not surprising article.  It outline the threat but offers no solutions.  How do we detect or otherwise manage these devices so that we can at least be aware of them before they can do damage?


Edge-DRsplash-10-edge-articles
I Smell a RAT! New Cybersecurity Threats for the Crypto Industry
David Trepp, Partner, IT Assurance with accounting and advisory firm BPM LLP,  7/9/2021
News
Attacks on Kaseya Servers Led to Ransomware in Less Than 2 Hours
Robert Lemos, Contributing Writer,  7/7/2021
Commentary
It's in the Game (but It Shouldn't Be)
Tal Memran, Cybersecurity Expert, CYE,  7/9/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Developing and Testing an Effective Breach Response Plan
Whether or not a data breach is a disaster for the organization depends on the security team's response and that is based on how the team developed a breach response plan beforehand and if it was thoroughly tested. Inside this report, experts share how to: -understand the technical environment, -determine what types of incidents would trigger the plan, -know which stakeholders need to be notified and how to do so, -develop steps to contain the breach, collect evidence, and initiate recovery.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2022-41717
PUBLISHED: 2022-12-08
An attacker can cause excessive memory growth in a Go server accepting HTTP/2 requests. HTTP/2 server connections contain a cache of HTTP header keys sent by the client. While the total number of entries in this cache is capped, an attacker sending very large keys can cause the server to allocate ap...
CVE-2022-44938
PUBLISHED: 2022-12-08
Weak reset token generation in SeedDMS v6.0.20 and v5.1.7 allows attackers to execute a full account takeover via a brute force attack.
CVE-2022-4366
PUBLISHED: 2022-12-08
Exposure of Sensitive System Information to an Unauthorized Control Sphere in GitHub repository lirantal/daloradius prior to master branch.
CVE-2022-46826
PUBLISHED: 2022-12-08
In JetBrains IntelliJ IDEA before 2022.3 the built-in web server allowed an arbitrary file to be read by exploiting a path traversal vulnerability.
CVE-2022-46827
PUBLISHED: 2022-12-08
In JetBrains IntelliJ IDEA before 2022.3 an XXE attack leading to SSRF via requests to custom plugin repositories was possible.