Mobile

6/27/2018
10:06 PM
50%
50%

10 Tips for More Secure Mobile Devices

Mobile devices can be more secure than traditional desktop machines - but only if the proper policies and practices are in place and in use.
Previous
1 of 11
Next

(Image: oneinchpunch)

(Image: oneinchpunch)

Computing and mobile computing are, to an ever-growing degree, the same thing. According to research by StoneTemple, at the beginning of 2018, 63% of Web traffic comes from mobile devices; they expect the number to pass 2/3 of all traffic by the end of the year.

Most users, and most security professionals, seem to think that mobile platforms are inherently more secure than traditional desktop and laptop computers. In many circumstances that's correct, but that assumption can lead to behaviors that carry significant risks.

Fortunately, there are steps a security team can take secure mobile devices: Some of these are actions that the security team should take, while others are actions that should be taught to users. Many of these steps fall squarely in the "it just makes common sense" category of things. That doesn't mean that security pros and users alike don't need a reminder to check for each of these to be on their list of positive behaviors — and on the list of results to be enforced by policy on all devices.

There are many behaviors that can contribute to mobile device security or risk. We'd be interested in hearing about the behaviors that you see as important — but that didn't make our list. Use the comment section to let us know what we missed.

 

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 11
Next
Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
HPERPER
50%
50%
HPERPER,
User Rank: Apprentice
7/3/2018 | 3:04:27 PM
Mobile Device Security NIST NCCoE
The NIST National Cybersecurity Center of Excellence has publihsed guidance and best practices to secure mobile devicse.   Chek it our at nccoe[dot]nist[dot]gov
Joe Stanganelli
50%
50%
Joe Stanganelli,
User Rank: Ninja
6/27/2018 | 11:06:04 PM
OS updates
I have a bone to pick about OS updates. Vital for good security? Sure. But it's a self-created issue because the vendor then begins to treat the old OS as good as abandonware.

Which wouldn't be so bad except that so many OS updates are more feature driven than security driven such that, in my experience, they tend to be progressively worse.

Which then causes people to want to update less -- which leads to bad security.

Mobile OS teams: Want to improve security on your products? Fire all the elitist, desperate-to-win-an-award UX/UI jerks.
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.