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
Infographic: Mobile Security Run Amok
Newest First  |  Oldest First  |  Threaded View
<<   <   Page 2 / 2
PeteJW
100%
0%
PeteJW,
User Rank: Apprentice
2/4/2014 | 4:16:32 AM
Re: No Clue? The 45 percent
Part of the issue is also understanding that users too are sensitive to heavy handed IT policies and controls that potentially effect their own privacy. That's why businesses are supplementing standard devuce controls with app and contatent management - especially techniques to isolate and secure business and personal content -at rest and in-flight. If they don't do this effectively (across multiple devices and silos) without adding more burden on IT and a usability tax on the user, then the device will be left at home, become an office paperweight, or as research indicates compromise a business. Whatever the case everyone loses.
Li Tan
50%
50%
Li Tan,
User Rank: Apprentice
2/3/2014 | 8:13:53 PM
Re: No Clue? The 45 percent
BYOD brings significant benefits to business and improves the efficiency at least one fold. But the security threat is always a headache of IT department. Last month my company pushed the installation of new security software on our BYOD device so that the security is enhanced when accessing company network to download email. The installation process is rather tedious and time-consuming. Furthmore, I do doubt its effectiveness. The stringent policy is good for security but if you cannot enforce it easily, then it's really something of vain.
WKash
50%
50%
WKash,
User Rank: Apprentice
2/3/2014 | 4:44:13 PM
Re: No Clue? The 45 percent
It does seem that some of these respondents' companies are inviting trouble. For those trying to figure out what baseline to use to improve their BYOD policy, here's what the US CIO issued to agencies nearly 18 months ago:
A Toolkit to Support Federal Agencies Implementing Bring Your Own Device (BYOD) Programs

Contents http://www.whitehouse.gov/digitalgov/bring-your-own-device#key-considerations
Thomas Claburn
50%
50%
Thomas Claburn,
User Rank: Ninja
2/3/2014 | 4:28:01 PM
Re: No Clue? The 45 percent
Surely, there must be some MDM vendors out there that support the big three: Android, iOS, and Windows Phone.
Marilyn Cohodas
50%
50%
Marilyn Cohodas,
User Rank: Strategist
2/3/2014 | 3:19:37 PM
Re: No Clue? The 45 percent
I certainly understand that trying to stay on top of mobile security is like shooting a moving target. Yet it seems to me that it  is equally absurd to spend the time developing policies if you know you can't enforce them. 
Lorna Garey
50%
50%
Lorna Garey,
User Rank: Ninja
2/3/2014 | 3:16:15 PM
Re: No Clue? The 45 percent
Marilyn, In my discussions with practitioners, it's more common that you'd think. The usual justification is that HR requires employees to sign a form where they promise to observe some set of rules and policies. However, as we saw with Edward Snowden, those forms aren't worth the paper they're printed on if the employee decides to misuse mobility. There's also the problem of well-meaning but clueless users who use "0000" as a passcode or stick a post-it note to the back of their tablets with email and SaaS passwords.

Wny not put enforcement in place? Usual reasons are the business won't stand for it (or pay for it)and/or the MDM/MAM market is still too fragmented given that they support multiple platforms.
Marilyn Cohodas
50%
50%
Marilyn Cohodas,
User Rank: Strategist
2/3/2014 | 2:55:29 PM
No Clue? The 45 percent
Can it be true that nearly half of respondents allow all users on to the network if they agree to policies that no one enforces? How typical is that? 
<<   <   Page 2 / 2


7 Tips for Choosing Security Metrics That Matter
Ericka Chickowski, Contributing Writer,  10/19/2020
IoT Vulnerability Disclosure Platform Launched
Dark Reading Staff 10/19/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-9994
PUBLISHED: 2020-10-22
A path handling issue was addressed with improved validation. This issue is fixed in iOS 13.5 and iPadOS 13.5, macOS Catalina 10.15.5, tvOS 13.4.5, watchOS 6.2.5. A malicious application may be able to overwrite arbitrary files.
CVE-2020-9997
PUBLISHED: 2020-10-22
An information disclosure issue was addressed with improved state management. This issue is fixed in macOS Catalina 10.15.6, watchOS 6.2.8. A malicious application may disclose restricted memory.
CVE-2020-9927
PUBLISHED: 2020-10-22
A memory corruption issue was addressed with improved input validation. This issue is fixed in macOS Catalina 10.15.6. An application may be able to execute arbitrary code with kernel privileges.
CVE-2020-9928
PUBLISHED: 2020-10-22
Multiple memory corruption issues were addressed with improved memory handling. This issue is fixed in macOS Catalina 10.15.6. An application may be able to execute arbitrary code with kernel privileges.
CVE-2020-9929
PUBLISHED: 2020-10-22
A memory corruption issue was addressed with improved memory handling. This issue is fixed in macOS Catalina 10.15.6. A local user may be able to cause unexpected system termination or read kernel memory.