Endpoint

5/16/2018
07:00 PM
50%
50%

7 Tools for Stronger IoT Security, Visibility

If you don't know what's on your IoT network, you don't know what to protect -- or protect from. These tools provide visibility into your network so you can be safe with (and from) what you see.
Previous
1 of 8
Next

(Image: Geralt)

(Image: Geralt)

It's hard to protect what you don't know you have. Put another way, it's those "unknown unknowns" that tend to get you. And the number of unknown unknowns is increasing because of the rapid rise in enterprise IoT devices and the incredibly disruptive rise of the "shadow IoT" that parallels the shadow IT seen in the traditional IT space. That's why one of the words most commonly heard at security conferences is "visibility," and why getting a handle on what's actually attached to the network is a critical step in any security plan.

It's also why there are so many new tools for getting that critical visibility, all looking at the computing environment from different vantage points.

Visibility for security means knowing all of the devices attached to the network, all the software running on those devices, which cloud services they might be using, and more. Traditional instruments of network visibility - like the tap or span port - might not be enough for IoT. While these are valuable tools when use as part of non-destructive traffic flow analysis, they're layer 1 devices that don't, in and of themselves, provide the kind of network or IoT visibility that comes through the systems included here. They may provide access to the network, but they don't provide analysis.

The good news is, the visibility-increasing IoT security-enabling tools listed here can help your IT team in more ways than one. The same tools that provide visibility for security can often provide visibility for management and operational analytics or other applications through APIs; or, improved visibility might be a critical piece of a larger IT solution.

Here are seven options for your security team to consider:

 

 

Curtis Franklin Jr. is Senior Editor at Dark Reading. In this role he focuses on product and technology coverage for the publication. In addition he works on audio and video programming for Dark Reading and contributes to activities at Interop ITX, Black Hat, INsecurity, and ... View Full Bio

Previous
1 of 8
Next
Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
What We Talk About When We Talk About Risk
Jack Jones, Chairman, FAIR Institute,  7/11/2018
Major International Airport System Access Sold for $10 on Dark Web
Kelly Sheridan, Staff Editor, Dark Reading,  7/11/2018
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: This comment is waiting for review by our moderators.
Current Issue
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2018-14373
PUBLISHED: 2018-07-17
An issue was discovered in LibTIFF 4.0.9. In TIFFFindField in tif_dirinfo.c, the structure tif is being dereferenced without first checking that the structure is not empty and has the requested fields (tif_foundfield). In the call sequences following from the affected library functions (TIFFVGetFiel...
CVE-2018-14374
PUBLISHED: 2018-07-17
An issue was discovered in LibTIFF 4.0.9. A buffer overflow can occur via an empty fmt argument to unixErrorHandler in tif_unix.c, and it can be exploited (at a minimum) via the following high-level library API functions: TIFFClientOpen, TIFFFdOpen, TIFFRawStripSize, TIFFCheckTile, TIFFComputeStrip,...
CVE-2018-14375
PUBLISHED: 2018-07-17
An issue was discovered in LibTIFF 4.0.9. A buffer overflow vulnerability can occur via an invalid or empty tif argument to TIFFRGBAImageOK in tif_getimage.c, and it can be exploited (at a minimum) via the following high-level library API functions: TIFFReadRGBAImage, TIFFRGBAImageOK, and TIFFRGBAIm...
CVE-2018-14378
PUBLISHED: 2018-07-17
An issue was discovered in LibTIFF 4.0.9. A buffer overflow can occur via an invalid or empty tif argument to TIFFWriteBufferSetup in tif_write.c, and it can be exploited (at a minimum) via the following high-level library API function: TIFFWriteTile.
CVE-2018-14363
PUBLISHED: 2018-07-17
An issue was discovered in NeoMutt before 2018-07-16. newsrc.c does not properly restrict '/' characters that may have unsafe interaction with cache pathnames.