Friday, October 11, 2013

READ: BYOD legal problem

CITATION: Jones, J. (2012). Beginner's Guide to BYOD (Bring Your Own Device). BYOD, from http://blogs.technet.com/b/security/archive/2012/07/18/beginner-s-guide-to-byod-bring-your-own-device.aspx
Let's say you need to pull some corporate data off an employee's personal iPad. Under the newly and hastily crafted bring-your-own-device policy, or BYOD, the employee is required to hand over the iPad to the IT computer forensics team.
The team finds child pornography on the iPad in areas unrelated to the job.
Did the team have permission to conduct e-discovery on personal data? Is the team obligated to call law enforcement? Would the finding be admissible in court? Was the employee's privacy rights violated? Was the BYOD policy thorough enough to cover such scenarios?
Welcome to the foggy world of BYOD, where the blending of personal and work lives on a single device open up a host of problems. CIOs often fret about security and management, but BYOD can land a company in murky legal water, too.
"It's a slippery slope," says Ben Tomhave, principal consultant at governance, risk and compliance vendor LockPath. While he isn't a lawyer, Tomhave is co-vice chairman and incoming co-chairman of the American Bar Association's SciTech Information Security Committee and regularly blogs about risk management issues.
If CIOs think they can get off this slippery slope by blocking BYOD at the front door, think again.
Juniper Networks just released results of a survey of more than 4,000 mobile-device users and IT professionals. This IT-gets-burned stat stood out: Many employees circumvent their employers official mobile-device policies, with 41 percent of all respondents who use their personal devices for work doing so without permission from the company, the report states.
"The IT departments that I talk to on a regular basis don't think [the risk] is that high," says Dan Hoffman, chief mobile security evangelist at Juniper Networks. "They think they have a lot more control and insight than they really do."
Rogue BYOD behavior puts a company at even further legal risk because there aren't any formal policies to fall back on when things go south—which will happen.
Child porn on an iPad is an extreme case (at least, let's hope it is), but a more likely scenario is that IT conducts a search on a BYOD iPad and stumbles upon signs that an employee has been working on a project that potentially undermines or competes with the organization.
If the employee was doing this on his own time—that is, not company time—can the company fire the employee based solely on this potentially ill-gotten evidence?
Here's a follow-on scenario adding even more intrigue: Let's say the employee is terminated and the company remote wipes his iPad, which deletes personal data. Is the company culpable? "You've got to make sure policies and legal agreements clearly articulate the expectation," Tomhave says.


This legal white-hot knife cuts both ways; employees need personal protections, too.
Companies (and IT departments) can be just as sneaky when it comes to BYOD. Abuses of access run rampant in the tech industry, headlined by Hewlett-Packard surreptitiously obtaining phone records of board members and press in order to ferret out leakers in 2006.
Today, companies will pressure employees to give up Facebook passwords for hiring and firing purposes. What does this mean for BYOD? Most employees have a Facebook app on their personal smartphones and tablets, whereby the app automatically logs them in with their usernames and passwords. When those devices are in the hands of IT, all of a person's Facebook account is accessible.
Tomhave advises employees to lawyer up before signing the BYOD agreement. He envisions a cottage industry of legal advice that helps employees build a privacy protection shield. "You'll want to sign a policy that clearly delineates what the business is allowed to do and not allowed to do," including conditions for seizing and searching the BYOD device in the first place, he says.
Another alternative is to go back to the days of carrying around multiple devices: a personal smartphone and a business smartphone, even if that business phone falls under BYOD. That way, you don't run the risk with crossover.
It's clear that companies and employees need good legal agreements in place for participating in a BYOD program. Unfortunately, such agreements are scarce.
"I don't think a complete risk analysis has been done on any of this stuff," Tomhave says. "A lot of organizations are playing catch-up."

Tuesday, August 13, 2013

Two great things today...Gartner article and Jack's suggestions

After weeks of trying, finally David Robinson at Mason got me the Gartner article I wanted.  This was amazing!  For weeks I was denied this article.  Finally last week I called Gartner again and they suggested an office at Mason that "has access".  Contacted them and after much transferring, I was handed via email to David.  He managed to get it and send it to me via email!  It is 43 pages, full of great ideas and research.  I will be starting on more literature review starting with that after coming back from Germany.

The next thing was meeting with Jack tonight and his wife Julie was there too.  He went over my PowerPoint and made a good many suggestions and changes.  He recommended Carnegie Mellon SEI Systems Engineering Process and Mitre's CVE (cve.mitre.org) database.  Also NIST 800-37 RMF (Risk Matrix Framework) and DISA STIG (iase.disa.mil --> STIG --> Network --> Wireless --> Smartphone and Tablet).  I am going to check these sites and tools.

Tuesday, July 16, 2013

Topic rephrase ideas


Hypothesis 1 and topic: BYOD framework can be constructed for an enterprise that reduces its risks to a level on par with corporate owned managed devices through a balanced (optimized) combination of technology and policy management: A Systems Engineering Risk Analysis Problem

Hypothesis 2: BYOD framework can be constructed for an enterprise that increases its productivity as a whole beyond that of an existing framework for corporate owned managed devices

Sunday, July 14, 2013

Change of direction in the topic so it is more SE like


So if an organization encourages BYOD, it will have increased productivity and also increased risks due to the security issues with BYOD.  I conjecture that the risks can be reduced to an acceptable level on par with corporate owned managed devices such as Blackberries.  The cost of reducing the risks is more than offset by the productivity gain.  In other words a BYOD system can be modeled and potentially constructed that increases productivity of an organization as a whole while reducing its own risks using a balanced (optimized) combination of technology and policy management.

READ: Mobile Device Management Systems

CITATION:
Rouse, M. (2013). Mobile Device Management Systems  Retrieved July 14, 2013, from http://searchmobilecomputing.techtarget.com/definition/mobile-device-management

URL:
http://searchmobilecomputing.techtarget.com/definition/mobile-device-management

Good definitions of MDMs.


Mobile device management (MDM) is the administrative area dealing with deploying, securing, monitoring, integrating and managing mobile devices, such as smartphones,tablets and laptops, in the workplace. The intent of MDM is to optimize the functionality and security of mobile devices within the enterprise, while simultaneously protecting the corporate network.
Mobile device management software allows distribution of applications, data and configuration settings and patches for such devices. Ideally, MDM software allows administrators to oversee mobile devices as easily as desktop computers and provides optimal performance for users. MDM tools should include application management, file synchronization and sharing, data security tools, and support for either a corporate-owned or personally owned device.
The ideal mobile device management tool:
  • Is compatible with all common handheld device operating platforms and applications.
  • Can function through multiple service providers.
  • Can be implemented directly over the air, targeting specific devices as necessary.
  • Can deploy next-generation hardware, operating platforms and applications quickly.
  • Can add or remove devices from the system as necessary to ensure optimum networkefficiency and security.

Saturday, July 13, 2013

Adviser Meeting and Topic Mod

Met today with the advisers and as expected they killed my ideas once more.  They were nicer about it this time though.  I taped the session this time.  Based on what I understood them say, they are focused on two areas:
  • How am I going to prove my hypothesis?
  • My data needs to be either original (I got it first hand) or else be academically sound, that is published or I must have access to the source
So these are the two areas I will focus on for the next 8 weeks.  Our next meeting in September 7.  I also located several places on the web for getting data.  I will be calling them on Monday to see about getting data.  Emailed Dr. Ron Ross to talk to him about the first point.  I am leaning towards modifying my topic further to make it simpler:

Current:
Mobile Device Management (MDM) Systems within an organization's Bring Your Own Device (BYOD) environment: A Systems Engineering Optimization of Technology and Policy Management

Modified to:
Mobile Device Management (MDM) Systems within an Organization's Bring Your Own Device (BYOD) environment
A Systems Engineering Optimization of Technology and Policy Management with an Acceptable Level of Risk: Case Study in the Financial Sector

It's kind of long and I like to shorten it some.  I have to work on it some more.  The idea here is that given a situation, in this case a Financial Company for example, how to implement MDM to allow BYOD to be productive and mitigate the risks to a level acceptable to the organization.  The question remains: how can I prove it?  I was thinking doing risk analysis of what the organization's risk level of BYOD (a number or collection of numbers) would be before the combination of MDM and Policy Management and the risk, and what would the risk level of BYOD would be after implementation or at least the projected risk level after modeling.  It's a lot of work but perhaps I am onto something.

Friday, July 5, 2013

Submitted PowerPoint for Saturday meeting

Completed and submitted the PowerPoint for the Saturday 13 of July meeting.  I wonder how badly they will butcher it after all my hard work and effort.

Thursday, June 20, 2013

Dr. Ron Ross at ISSA about 800-53 Rev 4

I went to the ISSA meeting today and the guest speaker was Dr. Ron Ross.  Liz was there too.  He was quite awesome.  I tried to write down as much as I could and as much as made sense.  He did have a PowerPoint which I will write him and ask for.

Here are some points:

80% of Android devices have a malware on it
95% of Android devices have been tampered with

Quote from Einstein:
Everything should be made as simple as possible - but not any simpler.

Dumbing down...IT is way to complex and crowded; it needs to be simplified.

Strength of mechanism - Build it right.

NASA uses the Integrated Project Team which means all stake holders are available and no project moves forward until all stake holders are satisfied.

How to break down barriers:
-As an example when American car manufacturers wanted to compete with the Japanese, they built rooms and put people on it to do quality control.  It didn't work and made matters worse.  We must face the issues and answer hard questions, and solve using simple and elegant methods.

Strength of IT Infrastructure:

-Simplify
  • Reduce and manage the complexity of IT infrastructure
  • Use Enterprise Architecture to streamline the IT infrastructure
  • Standardize, optimize, consolidate IT assets
-Specialize
  • Use guidance in SP 800-53 Rev 4 to customize security plans to support specific mission functions
-Integrate
  • Enterprise Architecture
  • System Engineering
  • System Development Life Cycle
  • Acquisition
He also mentioned the 800-160 which I will look into.

Friday, June 14, 2013

Topic mod

The ineffectiveness of MDM security systems on BYOD within organizations
A requirements and risk analyses of BYOD and a systems engineering approach to balancing technology and policy management

The effect of Mobile Device Management (MDM) Systems in an organization's Bring Your Own Device (BYOD) environment
A requirements analysis or MDM and a risk analysis of BYOD
Optimization and balancing of mobile security technology and security policy management

Phone call with Jeff Rowell referred by Dennis Perry

Using a gov laptop and comp laptop
As policies changed
He could use comp laptop and access gov resources
Policies changed and couldn't do that any more
No thumb drives allowed but you can email stuff
once locked out of gov computer while on travel; when remote help desk can't just get into your computer; a week without a computer
Gov uses the common access card; needed two cards for a while and a finger print reader

If not an issued gov device, it is not allowed in classified environments; same with the company
Structure of the building would not permit cellular signal (not a policy but a circumstance)
Now-a-days a lot of iPads and iPhones are allowed in the company if you are high enough
If not using a company device, cannot download file attachments; limited ability
BYOD is not entirely welcome; when allowed, they must use a VPN
Policy was BYOD to company network but they can have it with them as long as they are not in a classified environment

Wednesday, June 12, 2013

IEEE Northern Virginia Chapter meeting

Went to the IEEE meeting today for the first time.  It was held at Olive Garden.  Great bunch of people and four gave me their contact info and asked that I call them.  I will.  They will have me participate in conferences as a volunteer and that will help me next year with my paper hopefully.  The chair was Mithun.  President was Mark Apter.  Also got the secretary Rhonda Farrell.  I will contact them all.

Tuesday, June 11, 2013

Meeting with Dr. Sarkani and Dr. Mazzuchi / READ: Mobile Security Gaps Abound

I met with Drs. Sarkani and Mazzuchi today and expressed my progress and nervousness about my topic, what the advisors are saying, and the deadlines.  Dr. Sarkani told me I need to focus more on reading literature (10 he said) and forget the practical side of stuff.  He said they are interested in theory.  Dr. Mazzuchi took me to the computers and show me to search Gelman using two databases: Web of Science and Compendex.  He used the phrases "Mobile Security", "Risk Analysis", and "Policy Management" as titles and topics.  He pointed out how I can click the little number that takes me to how many people have referenced that particular article.  Interestingly he printed two out for me which he considered good and the second one I happened to glance at the last paragraph.  It reads:

"There's no doubt BYOD is off and running, yet security and management are not
keeping pace.  That gap creates a serious exposure for enterprises and one that CIOs
should be looking to get their arms around.  Unfortunately, the lack of a widely 
published mobile security failure has lulled executives into thinking that the
situation is well in hand.  Nothing could be further from the truth"

Basically the premise for my topic.  I told him I like to show him the last paragraph of the article he just printed as I had just glanced at it.  He read it and laughed.  Shortly there after as I was saying goodbye he laughed again and said "That was great you finding that paragraph!"  Let's hope it is a silver lining.

CITATION
Finneran, M. (2012). Mobile Security Gaps Abound. Informationweek, 26-29.


This article was the only one Dr. Mazzuchi could find; the other one he found was in Chinese.  Great article ad among other things it highlights my topic so clearly as mentioned above.  Here are some important points:

  • Number 1 and 2 concerns regarding mobile security are loss of device containing sensitive data and infected personal devices connecting to corporate network
  • Most user do not differentiate between Wi-Fi and 3G/4G access and carriers like it that way
  • Today mobile security is user security is data security; maintaining two or three policies is a recipe for confusion and noncompliance
    • The more unified the policy the easier to enforce
  • Having users agree to follow policies is translated into "trust the user to do the right thing"
  • Only 14% of mobile security survey respondents mandate hardware level encryption
  •  If access from home Wi-Fi or public ones allowed, it must be through VPN
  • A large smartphone security concern is risky user behavior
    • To include malware on phones and users forwarding corporate data to cloud-based storage
  • From a policy perspective, an MDM system is what gives your rules teeth
  • Work with carriers and see what they can do for you
  • Four undeterred capabilities
    • Prevent installation of unknown apps
    • Recognize unauthorized software
    • Whitelist and blacklist applications
    • Restrict or block app stores

Saturday, June 1, 2013

DoD Link

Jack sent me the link below:

http://iase.disa.mil/stigs/net_perimeter/wireless/smartphone.html

It is the DoD Network / Perimeter / Wireless - Wireless (Smartphone/Tablet) Mobile Security Guides.  It covers iOS, Android, Blackberry, and Windows Mobile.  Interestingly, it only mentions Android 2.2 with no mention of the later versions.  Also, based on my quick review, it mentions that certain phones will not be allowed without being registered with their MDM.  I have to read up on it a little but sounds like a gold mine.

One last note, there are memos available from the Chief Information Assurance Executive.  They mention that the DoD is converting from the DoD 8500 Information Assurance controls to the NIST 800-53, precisely the publication Dr. Ron Ross has worked on and referred me to!  I will be attending his talk on June 20th regarding this publication.

By: Nima Zahadat

Friday, May 31, 2013

READ: Mobile Device Managamanet (MDM) Policies (Best Practice Guide)

CITATION
FiberLink. (2012). Mobile Device Management (MDM) Policies (Best Practice Guide). In MaaS360 (Ed.), (pp. 1-14): Fiberlink.

Interesting paper, more of an informational and a sales pamphlet.  IT is good though as it clearly highlights what they consider mobile security issues all of which interesting they have solutions for.

Some interesting pieces:
  • Best practices listed
    • Know your industry's regualtions
    • Require passcodes
    • Enforce encryption
    • Restrict device features as necessary
    • Keep a watchful eye on apps
    • Use TouchDown (their product which only works on Android) for setting up email
    • Distribute settings over the air
    • Warn first, then remediate policy violations
    • Test your policies
    • Monitor your devices
  • Sales pitch: MaaS will watch over your devices both BYOD and company issued
  • Setup as policies as to treat all users the same way (not practical in real world but makes for easier software development)
  • Setup passcode expiration
  • Sales pitch: with a few clicks you can make your passcode policy a reality
  • Apple supports native encryption; Android does not necessarily and may need additional software
  • Their recommendations: prevent any devices that cannot be encrypted from connecting to your corporate resources
    • While it is a reasonable recommendation, they don't mention how to do this and further, how to block someone from doing this if they are coming in over the telephone network and not Wi-Fi
  • Looking at some of their screenshots, one says: "Supported only on iOS 5 and higher"
    • What if someone has iOS 4?  Can they bypass the security? 
  • Some of their customers require the same apps so employees can collaborate together
  • For remediating policy violations, they recommend that it be automated without IT having to learn of the problem and then take action
    • This may be fine for small violations but not practical for very secure environments
  • Create test scenarios with groups of test users prior to deployment
By: Nima Zahadat

READ: Android Remains Main Target For Mobile Malware Writers Despite iOS Having More Vulnerabilities Says Symantec

CITATION
Lomas, N. (2013). Android Remains Main Target For Mobile Malware Writers Depsite iOS Having More Vulnerabilities, Says Symantec (pp. 1-4): TechCrunch.
 

Interesting article and as Jack said, Apple's iOS is more secure by default.  The article mentions the different approaches of iOS verses Android as different ecosystem approaches: Apple's walled garden versus Android's open playground.

Symantec found 103 new threats targeting Android versus just one for iOS in 2012.  This seems to be caused by Android allowing downloads from third party app locations which iOS does not allow unless the phone is jail broken.  Symantec does point out that rogue software has made it to the Google store in the past as legitimate however.

The Android threats are most common in Eastern Europe and China which utilize the Android platform much more than Apple's iOS.

Another issue is the variety of Android vendors.  While Android is in version 4.x, the vast majority (90% according to Symantec) utilize older versions which are less secure.

...while the [mobile] threat is still small (compared to desktops and LANs), it is now more than doubling year-on-year.


McAfee reported 36,699 pieces of mobile malware, 95% of which cropped up in 2012.  Symantex explains the huge difference as McAfee reporting all the variants of a threat as opposed to just the new threats.

Still another mobile security software provider NQ Mobile reported more than 65,000 distinct forms of mobile malware such as app repackaging, malicious URLs, and SMS phishing.

Security companies of course have a vested interest in hyping malware threats, since they are in the business of selling security, so it's worth taking the highest figures with a big pinch of salt.

By: Nima Zahadat

Wednesday, May 29, 2013

Meeting with Jack

Met with Jack last night and it was very positive.  He told me there are a lot of MDM solutions out there but not a single one is complete.  He reaffirmed Dr. Ron Ross' statement that there must be a balance between technology and policy.  He has a solid grasp on mobile security and systems engineering concepts.  Here are some of what I wrote down:

  • Jack believes it is better for organizations to issue devices rather than BYOD
  • Mentioned MDMs use the sandbox approach; drawbacks include
    • Interface is propriety and people hate it
    • Sandbox can be attacked
    • Battery usage is excessive; mentioned in a test, their sandbox drained the battery in 2 hours
  • MDMs are a collaboration between Apple, Google, Microsoft, and Blackberry
    • These are the proprietary standards for mobile security
    • Mentioned 37 items that form an MDM
    • None of the vendors support all 37 items
  • Jack mentioned he believe NIST or IEEE or some high level government organization needs to propose the standard for these vendors to adhere to
  • MDM provides security but in and of itself is not secure
    • This was very cool to know
    • He showed me his iPhone 5 which has MDM installed and under settings it can easily be removed
    • He mentioned that the data stays however
  • Jack mentioned a company that installs a legal root-kit that bypasses all the software and controls everything from below
    • Problem is, especially in BYOD, the privacy issues and would someone want a root-kit on their own device
  • Some BYOD challenges
    • What if you do not want to register your device?
    • Even if registration is done, there needs to be a separate MDM profile for each OS version for each carrier.  So each updates to iOS would need a different MDM profile and of course separate ones for AT&T, Verizon, and Sprint!  The permutations is crazy
  • GPS technology is available to disable hardware (such as camera) based on what location you are at
  • Again, no vendor supports all the MDM requirements
A successful plan require technology, culture, MDM, policy, and management  commitment

iOS is built on a far more superior architecture than Android
  • Apple does not allow apps to talk to each other
  • Android does and causes a havoc
  • Compare the early days of Windows to Mac; that's Android verus iOS
Systems Engineering
  • Security is a derived functionality requirement of the Systems Engineering process
  • To start, we need
    • Define needs
    • Define requirements
      • Functional requirements
      • Technology requirements
      •  Security requirements
    • Define the architecture
    • Define the specifications
    • Define the design
    • Define the implementation
  • Security is in effect a subsystem of Systems Engineering
BYOD
  • Define mobility needs
  • Define the context you are operating in
  • Determine the specs
  • Design
 Cost consideration:
  • Would you spend millions to secure 30 devices?
Security policy consideration:
  • With security in place, there has to be Trust but Verify
  • Can we trust and verify or no because if it is not, the security or its policy are not worth it
  • At what point do you rely on technology?
  • At what point do you rely on policy?
  • What are the privacy and legal consideration?
 IT Systems
  • IT is built from many systems
    • LAN
    • WAN
    • Web
    • DNS
    • Mail
    • Application
    • Storage
    • Databases
    • Hardware
    • Software
  • Security is another part of an IT system that permeates everything
By: Nima Zahadat

Sunday, May 26, 2013

READ: The 5 Hot Tips to Secure Your BYOD Workplace

CITATION
Voice, F. N. (2012). The 5 Hot Tips to Secure Your BYOD Workplace  Retrieved May 25, 2013, from http://www.forbes.com/sites/netapp/2012/08/28/the-5-most-common-tips-to-secure-your-bring-your-own-device-workplace/
 

URL
http://www.forbes.com/sites/netapp/2012/08/28/the-5-most-common-tips-to-secure-your-bring-your-own-device-workplace/

Good article but nothing new.  It does mention that Kraft, Whirlpool and some divisions of IBM have established BYOD guidelines.  It also suggests 5 items for security:

  1. Devices must be password protected
  2. Corporate information must never be stored locally
  3. Data must be encapsulated and backed up, frequently
  4. Applications may only be downloaded from sites that have been deemed trustworthy by the IT organization
  5. Mobile devices must support the ability to be remotely wiped of all data in the event they are lost or stolen.
 I like number 2 because I thought of it a few days ago before reading this article.  So I am doing well.  I am forming some definite ideas on how to implement BYOD and at the same time have a system that secures it.

By: Nima Zahadat

READ: Pros and Cons of Bring Your Own Device

CITATION
Dodd, C. (2013). Pros and Cons of Bring Your Own Device  Retrieved May 25, 2013, 2013, from http://turbinehq.com/2013/bring-your-own-device/ 

URL
http://turbinehq.com/2013/bring-your-own-device/

Overall a good article though it presented nothing new other than some statistics.  Based on the article
  •  Two thirds of small businesses and three quarter of larger organizations support a BYOD initiative
  • Those employers refusing BYOD will find that employees will bring and use their devices regardless
Directly from the article:

Pros

  • People have a vested interest in understanding how to use their own devices. Employees will naturally be more savvy and self-supporting, meaning a reduction in the need for IT support.
  • With the flexibility of the where and when of work that BYOD offers, many suggest it can provide a significant increase in productivity. A Huffington Post article highlights that in one quarter, Intel saw 640,000 emails sent via mobile phones, equating to an extra 51 minutes of productivity per day.
  • Being able to use personal devices to work on professional tasks is a big step forward in integrating people’s working and personal lives: having that flexibility can greatly improve employee satisfaction and retention.

Cons

  • The biggest, loudest concern sounded from all quarters is security. 
  • Following behind is the difficult switch in mindset for managers as they lose control and oversight over their employees. If people can work anytime, anywhere on a device that a manager has no right to access, they have to find new ways to measure productivity.

Solutions: security

  • Mobile device management allows companies to effectively create specific apps for their employee’s devices that they can control and encrypt as necessary. It can also allow companies access to wipe devices that have been stolen or lost. Some cloud applications work entirely virtually, meaning employees can access and edit data without it ever actually being downloaded onto their personal device.
  • CYOD is a new trend emerging amongst enterprises, meaning choose your own device. The device remains company owned and controlled but employees have a say in which device they use and some of it’s configuration.
  • This Forbes article lists five helpful tips to secure your BYOD workplace.

Solutions: people

  • Find a balance between freedom and control. Whilst you may need to monitor some employee behaviour on their personal devices, think carefully about the contents and transparency of your BYOD policy.
  • Learn to measure productivity by output rather than hours at the desk. In a cross over with remote working, embracing a BYOD culture means embracing a new style of management and collaboration. Trust your employees.
  • Pay attention to how your staff is using their devices. The emphasis of BYOD should be the ‘your’ rather than ‘device’. The momentum behind the trend is that people are finding new, efficient and innovative ways of working, so you should pay attention to how and why they are using their devices. For example, if your staff are using Evernote to collate and share information, don’t rush to ban the app, but instead consider paying for Evernote Pro to encrypt the data and support your staff’s efforts to make their jobs and lives easier.
 By: Nima Zahadat

READ: Mobile Device Management Key Components, V1.0

CITATION
Alliance, C. S. (2012). Mobile Device Management Key Components, V1.0 (pp. 1-11): CSA.

This is a great paper and divides MDM into various parts marking them as Must Haves or Optional.  Interestingly I found the Optionals to be more relevant to BYOD.  Here are some excerpts:

  • MDM is a critical component of the device life cycle
  • Well defined policy provides management direction and support for IT and information security and is the foundation for a solid MDM framework implementation
  • As part of risk management organizations should perform risk assessment periodically
  • Configuration management involves automated configuration of device settings
  • Software distribution includes updates for apps and OS, fixes, backups and restores
  • An enterprise app store is recommended
  • An active content library is recommended
  • Finance department is responsible for monitoring and controlling mobility costs
  • Privacy cannot be bargained away
  • Selective wipes and remote wipes are must haves
  • While most companies have a security policy in place, those policies need to be reviewed and possibly updated to account for the many components of mobile technology
  • Everything has to start with the basic understanding of the triangle, People, Process, and Technology


By: Nima Zahadat




Saturday, May 25, 2013

READ: International Data Privacy Legislation Review: A Guide for BYOD Policies

CITATION
Absalom, R. (2012). International Data Privacy Legislation Review: A Guide for BYOD Policies.


Long article that focused on various countries (localities) and the BYOD trend in general with some helpful tips.  The focus is on privacy laws and the report offers guidance concerning privacy laws in 8 major geographic markets along with suggested mobility policy to help ensure compliance.  Here are some useful pieces:

  • Enterprise mobility strategy must account for parameters set by local data privacy laws
  • Legal advice should be sought when implementing a policy that may require monitoring an employee's mobile device
  • Requiring employees to sign up to a mobile policy is the best way of ensuring both data security and legal compliance according to the author
  •  There are differences in data privacy laws in different countries but two themes are fairly consistent
    • Individuals must give full consent to their device being monitored
    • Organizations accessing sensitive personal data must provide for encryption, secure channel, and strong PIN
  • BYOD as many do not like to carry two devices
  • Employees find ways to get around limitations and use their own devices
  • In 2011, 80% of vertical markets reported employees using personal devices at work
  • Most organizations are unlikely to have the required tools and expertise to manage and secure corporate data across all these disparate operating systems, applications, and devices

Allowing BYOD leaves an organization in danger of breaching employee's private data and potentially open the door for a lawsuit.  On the other hand, allowing employees to have organizational data such as customer information on their phones may cause a lawsuit for the organization from the customer.  So organizations are stuck between a rock and a hard place.

Typical MDM features:
  • Providing encryption if not supported natively
  • Remote lock and wipe
  • PIN policy enforcement
  • Over-the-air (OTA) device recognition and enrollment
  • Device location and activity tracking
While these solutions may answer some of the technical problems, installing such software on personal devices can create further issues related to employee privacy laws.

Recommended corporate mobility policy framework:

8 different countries and their laws as they pertain to BYOD are examined.  The one country that does not have a single comprehensive piece of data protection legislation is the US!  In case of litigation, it is irrelevant in the US if the device is corporate or private; privacy does not apply.  Further, certain vertical-specific legislation does have impact on BYOD.   For instance, the provisions of Health Insurance Portability and Accountability Act (HIPPA) do not allow patient data to be stored on personally owned devices.

A case study of Unisys is described (pp. 19-20) and hailed as a good model.  Also, it is stated that International firms that are implementing a BYOD policy are seeing the benefits to recruitment.

Multinational businesses that are rolling out BYOD policies understand that it cannot be done on a corporate-wide basis but must be managed according to the privacy regulations in each country in which it operates.

This means technology alone is not enough.  Policy alone is not enough.  And even technology and policy are not enough.  The local laws must be incorporated into the overall technology/policy/regulation umbrella for BYOD. 

Recommended Reading: The BYOD Gap: Trends, Strategy, and the State of Mobile Device Management, October 2011

By: Nima Zahadat 

Friday, May 24, 2013

READ: These are the top 5 BYOD issues facing the healthcare industry

CITATION
 Crowell, C. (2013). These are the top 5 BYOD issues facing the healthcare industry  Retrieved May 24, 2013, from http://venturebeat.com/2013/04/26/top-5-byod-issues-facing-healthcare-industry/

URL
http://venturebeat.com/2013/04/26/top-5-byod-issues-facing-healthcare-industry/

Good article by the CEO of Enterasys, a security company.  He indicates 4 out of 5 doctors bring their own devices to work.  He indicates that while security and privacy are huge issues, there are others such as the heavy burden placed on the IT infrastructure of the healthcare organization.  He suggests that the IT support of the organization must be able to handle these 5 challenges:

  1. Upgrade the infrastructure if necessary to meet the demand of all BYOD devices, those of doctors, nurses, staff, and patients.  Federal standards call for institutions to deploy a single network to handle the needs of the medical devices as well as provide a standard of interoperability for securing all data on the clinical wireless LAN.
  2.  Have a strategy for lost devices as BYOD is not owned by the organization yet it may include patient data.  There must be a balance in strategy that takes into account the need to be noninvasive, yet law abiding. When dealing with patient information, anything that contains data covered by HIPAA needs to be secured, and those devices need to be able to be wiped clean.
  3. Providing a solution for the mixing of personal and professional data as well as use of the BYOD.  The idea that personal devices may compromise professional behavior, and the concern that procedures may not be clear around professional vs. personal use on personal devices. BYOD in this environment requires a shift in culture that revolves around transparency. 
  4. Ruggadize devices (provide subsidy) and put in place policies for proper sanitation of devices.
  5. Application deployment across many different devices with different operating systems and even differences between the versions of the operating systems is a huge challenge.  There are more than 20,000 mHealth apps out there and trying to manage and monitor their deployments requires a comprehensive planning and policy.  IT and the mobile workforce must have the same goal in mind — patient safety and protection. From there, they can put clear policies in place.
The author further says that BYOD isn’t a passing fad. It’s here to stay, and organizations need to establish strategies and best practices to handle this ever-changing landscape.

By: Nima Zahadat

Thursday, May 23, 2013

READ: Study Predicts BYOD Boom By 2016

CITATION
Ballenstedt, B. (2013). Study Predicts BYOD Boom by 2016  Retrieved May 23, 2013, from http://www.nextgov.com/cio-briefing/wired-workplace/2013/05/study-predicts-byod-boom-2016/62990/
URL
http://www.nextgov.com/cio-briefing/wired-workplace/2013/05/study-predicts-byod-boom-2016/62990/

A study done by Gartner predicts by 2016 38% of organizations will stop providing mobile devices to their employees and instead allow employees to use their own.  This number jumps to 50% by 2017.

One major question is if organizations should continue to subsidize their employees devices and service costs.  Gartner suggests keeping it simple and letting the employee pay for the device with part of the service cost be subsidized.

Gartner also found that BYOD is happening in government and organizations of all sizes.

By: Nima Zahadat


READ: Surprising Stats About Mobile Security

CITATION
Enterprise, M. (2013). Surprising Stats About Mobile Security  Retrieved May 23, 2013, from http://mobileenterprise.edgl.com/news/Surprising-Stats-About-Mobile-Security84688

URL
http://mobileenterprise.edgl.com/news/Surprising-Stats-About-Mobile-Security84688

This article was full of statistics.  Some interesting quotes:

51% of organizations surveyed had a BYOD program that allows employees to use their own devices

55% allow downloading of apps at the employee's discretion

"Mobile asset management hasn't reached maturity yet and many organizations need to implement best practice strategies" says Barbara Rembiesa CEO of IAITAM.

By: Nima Zahadat

READ: If iOS is Less Secure, Why Does Android Get Attacked?

CITATION
Roberts, P. (2013). If iOS is Less Secure, Why Does Android Get Attacked? All Things Security  Retrieved May 23, 2013, from http://www.veracode.com/blog/2013/04/if-ios-is-less-secure-why-does-android-get-attacked/

URL
http://www.veracode.com/blog/2013/04/if-ios-is-less-secure-why-does-android-get-attacked/

Very cool article and fun to read.  Comment at the end pretty good too.  It says that according to Symantec, in 2012, out of 108 malicious programs for mobile devices, 103 were for Android and 1 for iOS.  In contrast, iOS had 387 of the documented vulnerabilities out of 415 total.  The issue seems to be that since Google licensed its OS to vendors, the vendors are not updating their customers devices for fear of problems and calls to the help desk.  The current version of Android is 4.1 - 4.2 while 44% of the Android users are running versions 2.3.3 - 2.3.7 from two years ago with lots of vulnerabilities.

In 2012, according to Symantec, there was a 58% increase in mobile malware.  59% of all malwares were discovered in 2012.

The commentator indicates "It's the system stupid" saying the Apple offers far superior system as far as patching and ease of use is concerned and thus can keep its OS up-to-date without reliance on the carriers.  I tend to agree.

By: Nima Zahadat

Wednesday, May 22, 2013

READ: Towards a User-Friendly Security-Enhancing BYOD Solution

CITATION
Gessner, D., Girao, J., Karame, G., & Li, W. (2013). Towards a User-Friendly Security-Enhancing BYOD Solution. NEC TECHNICAL JOURNAL, 7(3), 113.


Good article on BYOD.  The authors propose containerization of enterprise apps as a way not to modify the underlying OS and also allow the use to run their own private apps.  It is an interesting solution though they fail to provide an actual solution.  Looking into the references Citrix and VMware are mentioned so I imagine virtualization is what they mean by containerization.  While great, virtualization still relies on the underlying OS to get everything done.  For instance, a key logger installed will capture the key strokes even from the container.  It is a good solution but still lacks total integrity.

As Rick Tracy told me, we want a game changer like iPhone change the whole concept of telephones, smartphones, and communication, we want a solution that just leaves the rest in the dust as irrelevant.

By: Nima Zahadat

READ: The Device Divide

CITATION
Hayes, J. (2012). The device divide. Engineering & Technology, 7(9), 76-78.

Good article as it pointed out the usual benefits of BYOD and the usual security concerns.  It does point out Sophos Mobile Control as a MDM.  I checked it out and the MDM supports iOS, Android, Windows Mobile, and Blackberry but it is limited of course.  I will have to review it and perhaps interview Sophos.

Some interesting pieces:
  • Security implications [of BYOD] alone cause IT staff to wake up in cold sweat
  • Pro arguments are persuasive but somewhat unproven
 Some statistics:
  • 75% of company bosses feel allowing BYOD positions their firms as "flexible and attractive"
  • 60% believe money can be saved through BYOD
  • 67% or organizations surveyed reported their senior management either didn't know where all the company data resides or are not sure
  • 74% stated they do not have a process for tracking which files have been placed on third party cloud and devices
  • 44% indicate BYOD is a pressing challenge
Other thoughts:
  •  BYOD is partly about decentralization and freeing up choice but still has to be managed under a policy-based regime
  • BYOD can create as many challenges for an enterprise as it claims to resolve
  • Sophos and Avaya offer some MDM solutions
    • Sophos Mobile Control
    • Avaya Identity Engine
  • VoIP may be going away soon as most messaging is done via text and email
    • A 10 word text message gets more across than a rambling voice mail which may be skipped 
By: Nima Zahadat 

Tuesday, May 21, 2013

READ: Security Requirements of a Mobile Device Management System

CITATION
Rhee, K., Won, D., Jang, S.-W., Chae, S., & Park, S. (2013). Threat modeling of a mobile device management system for secure smart work. Electronic Commerce Research, 1-14.

Good paper, though quite high level.  The authors acknowledge that "...no criteria have been established as of yet to evaluate whether such Mobile Device Management systems correctly provide the basic security functions needed by enterprises and whether such functions have been securely developed".  The paper is from April 2012 so quite recent even by technology measure.  Some good points:
  • MDMs should manage not only the data stored on BYOD but also the hardware such as USB ports and cameras
  • MDMs sould be flexible to employees, developers, and administrators

A MDM should follow five steps it is suggested:
  1.  Enrollment/Configuration
  2. Distribution
  3. Authentication
  4. Instructions
  5. Control/Report
A good list of Threats and Security Objectives is included.  Also a table of Security Functional Requirements is provided.  Lots of references at the end which I will look into.

By: Nima Zahadat 

READ: Mobile Device Management Software: The Answer to BYOD?

CITATION
Goedert, J. (2013). Mobile device management software: the answer to BYOD? Health data management, 21(2), 32, 34, 36 passim.

Great article that mentions how MDM in recent times (2011-2013) has been trying to address the security and privacy issues related to BYOD in the health care industry.  It mentions the fantastic benefits but also the risks involved and one additional issue, the cost of implementation as well as the ongoing cost of maintenance and upgrades.

Some notable pieces of the article:

  • [With physicians] devices quickly become a status symbol
  • Health care industry is far more open that other industries with more "free agents"
    • Doctors can work at multiple hospitals using their own devices
    • Of course they also have their own data on those devices along patients/hospitals data
  • It has not been clear to hospitals how they can control their data access and security on these devices
  • Physicians typically want certain functionality so they will download what they want or else pay a developer to make it and then they start using it
    • These developers are not necessarily security experts
    • This means security is often not built into the apps
    • This of course is critical to health care providers
    • Many times after the transaction, the developer disappears along with the source code
 MDM
  •  MDM started with some basic tools
    • Enforcing passwords
    • Enforcing encryption
    • Remote wipe
  • Talk to five mobile security experts as what is MDM and you will get five different answers!!!
A well rounded MDM definition perhaps (see below)?

Mobile Device Management configures the device and apps, protects the data,
separates professional and personal data, and at the end of a session removes the professional data

  •  MDM [strives to be] the way of allowing BYOD on the corporate network in a secure and reliable manner (whatever reliable means)

According to the article mobile market as we know it is young and did not come into play until the second half of 2010.  The only MDMs out there were for Blackberries and RiM might be going out of business or be sold.  Doctors, nurses, and staff prefer their iPhones and Androids and more recently iPads.
  • Hospitals have been learning it is not possible to deny BYOD
  • Once the device is on the network, there is no way to know what is running on the device short of some MDM solution
MDM systems enable a consistent, policy-driven and enterprise configuration of mobile devices.  The software enables many features:
  • Email restriction of photos, notes and videos
  • Passwords can remotely be reset
  • Devices can remotely be locked
  • Devices can be tracked via GPS
  • Certain apps (such as network scanners) can be blacklisted
  • Devices can be remotely wiped
  • Cameras can be disabled
Lessons learned:
  •  Pilot program started with 50 and grew to 300 in less than 4 months
  •  Kids love iPads and it helps them not think about needles
  • Every part of a hospital needs to be represented for beta testings
  • Devices that do not say "Hi" within 24 hours are wiped remotely (or locked)
  • Benefits of mobile computing have been significant workflow improvement for physicians and nurses
  • Some health insurers are finding it necessary to develop mobile device management policies
  • There is not a static version of MDM software; upgrades are frequent
  • Supporting mobile devices is a bigger challenge that previously thought
  • Most IT support is Windows trained and need quick learning to become familiar with mobile devices, their apps, MDM, and security challenges
  • Setup costs and cost of licenses is a high and can be a sticker shock when a $140 license per device is required
By: Nima Zahadat 

Monday, May 20, 2013

Possible mod to the topic

Effects of BYOD on an enterprise's [health care's] security systems: Optimizing the requirements of security, privacy, technology, and cost

Effects of BYOD on an enterprise's [health care's] security systems: Optimizing the requirements of security, privacy, and technology as a function of cost

Problem: BYOD is popular and unstoppable.  It has many benefits to an enterprise [health care] such as increased productivity, reduced costs, and reduced procurement.  There are, however, security and privacy concerns regarding BYOD.

Hypothesis: BYOD should be embraced. Through the proper combination and optimization of security technologies and security policies, a proper system life cycle for BYOD can be implemented successfully at the enterprise [health care].

Solution:

Validation:

By: Nima Zahadat 

READ: BYOD (Bring Your Own Device)

CITATION
Brooks, C. (2012). BYOD (Bring your own device).

This was a presentation by Chartered Institute for IT.  Interesting facts:

By 2016
  • 4/5 people will have a smartphone
  • 4/5 people will have a tablet device
  • 60% of smartphones will be employee owned
  • 70% of tablets will be employee owned
  • Devices will be more popular than laptops
  • More iPhones are sold every day than are babies born
  • 35 million apps are downloaded each day (2012)
  • Senior executives prefer to use their iPhone rather than a Blackberry at work
  • IT departments sued to drive technology, however this is now in reverse
Benefits of BYOD: Many listed but here are some highlights
  • Less training as users are self-taught
  • Citrix now creating BYOD platforms
  • BYOD makes the most of cloud technology
  • Less reliance on IT staff
  • Enables work from anywhere at any time
Risks of BYOD: Some highlights
  • BYOD have led IT departments to adopt less restrictive policies
  • Hard to enforce "Acceptable user policy" for a user's own device
  • Devices left un-managed can potentially result in significant data breaches
  • Users want financial incentive
BYOD Case Studies: Some highlights
  • IBM supporting 200,000 BYOD in 2012 and growing
  • Citrix gives each new employee 2,000 pounds in UK to purchase BYOD when they join
  • Ford allows email from any BYOD device
  •  Cheaper to enable BYOD infrastructure than to purchase notebooks/textbooks
By: Nima Zahadat