spk-logo-tm-2023
0%
1-888-310-4540 (main) / 1-888-707-6150 (support) info@spkaa.com
Select Page

Bringing Your Own Android and Developing a BYOD Policy

windchill features best plm software
Written by SPK Blog Post
Published on September 11, 2014

The concept of letting employees bring their own phones and devices to work has become more and more common. Employees want to use their personal devices in the workplace without having to carry around a second device for personal use. While this helps with cost cutting and end-user happiness, it can lead to some security issues.

End users of personal Android phones can customize and modify the OS to get around some company policies set in place. One set of policies in particular deals with the Exchange device. Most companies require a pin or pass code as well as the ability to remotely wipe a device before allowing work email to be retrieved on the phone. While these can be useful security features, easy-to-access apps allow users to ignore both settings, getting emails on an Android device that will leave everything in the open if stolen.

Thankfully, the pain of this is getting easier with Android L. The new OS set to release later this year is introducing multiple profiles, a feature custom ROMs already have. This should allow users to have a separate, pin-locked work profile to access work email while their personal account is unlocked and readily available. The ease of switching between the two may lead to fewer users using third party work-arounds that block functionality.

Android is a great OS that can have locked down custom operating systems created for enterprise solutions, but unless that device is provided by the company a user has full control of their own phone. As a result, a bring your own device policy with Android devices that isn’t policed will be a security risk.

Next Steps:

Kaveh Nasouti
Systems Integration Engineer

Latest White Papers

10 AI Use Cases: Accelerating Automotive Embedded Development

10 AI Use Cases: Accelerating Automotive Embedded Development

Software-defined and electric vehicles are only increasing as automotive technology advances. As these features grow, automakers must adapt. Manufacturing a car is not the same as it was years ago. This eBook explores how AI can be used in the automotive development...

Related Resources

Why Aerospace Programs Miss Deadlines Part 2

Why Aerospace Programs Miss Deadlines Part 2

Key Takeaways A connected digital thread helps prevent schedule delays: Linking CAD, simulation, PLM, ALM, and DevOps gives aerospace teams better visibility into dependencies, changes, and risks across the lifecycle. Earlier validation reduces costly rework: Creo and...

5 Ways to Reduce Engineering Cycle Time Without Adding Headcount

5 Ways to Reduce Engineering Cycle Time Without Adding Headcount

Key takeaways Faster engineering does not always require more headcount: Disconnected systems, manual handoffs, rework, and poor visibility often create more delays than a lack of engineering capacity. A digital thread can eliminate major sources of wasted time:...

Why Late-Stage Changes Are Killing Your Time to Market

Why Late-Stage Changes Are Killing Your Time to Market

Key Takeaways Late-stage changes get expensive fast: The farther a problem travels through design, testing, and manufacturing, the more time, cost, and rework it creates. Disconnected systems and weak traceability are major causes: When requirements, design, software,...