There are a lot of chatter out there about managing mobile devices and when the technology is logical given the management of mobile ... and when MDM or MAM make sense in light of Mobile content management. In this alphabet soup of acronyms mobile, which is a mobile business that embraces start?
Overlooking our customer base and how are using enterprise mobility, in some ways pretty amazing, I 'm here to tell you it is not an "or / or. "More often than not, it is an" i want it all "or" MDM for these "and" those for MAM. " Let me tell you what I mean.
We have a client who is a great non-profit hospital. They have tens of thousands of employees, many who want mobile access to email, administrative systems and electronic medical records. The hospital needs to ensure that they not only provide secure access to these people, but they make sure that they are monitoring and reporting on all devices on the network to the HIPAA / HiTech . On the other hand, they have another crew of people to whom they are providing access: thousands of medical consultants. These doctors probably do not need a complete management on the device, and the hospital IT department does not want to be in the area of management of non-employees devices. So for them, the ability to deploy MDM and MAM employees while deploying only email secure and secure access a TRA (ie MMA) to consulting physicians is the best of all worlds. It is the right level of access and management to the role of the employee and the situation risk profile.
Similarly, we have a client who is a big high-tech company. They have activities all over the world, including most importantly the United States for its base of US employees, the organization wants to deploy full on MDM. They need to make asset management and want to know which devices and applications on the network. But they have employees in countries where laws on user privacy are quite expensive. While many MDM functionality, ie monitoring the location of the device or reports on installed applications, can be suppressed to the directors, the company wants to avoid even the smell of walking on employee privacy. So for them, what is needed is MDM for US employees, but only secure email for countries with laws on privacy of the user. For users, the company can not only protect corporate data, but to protect equipment from the company managing users. Everybody wins
One thing that is clear :. MDM seems fundamental that most businesses want to do. Although the big driver is the need to ensure and control applications (which, frankly, is where things get interesting for customers who want to mobilize their business) many organizations want device policy-based. As a baseline, they want to deploy a password and enforce basic security, such as encryption on the devices. They also want to simplify the mobile experience for their users to access WiFi provisioning and single issue certs so the devices can access corporate resources without having to enter their credentials every time. They also want to link the policies of the camera application and network access, such as prevention of jailbroken devices to get their applications, wiping a device of its corporate applications and data if the unit is out of some geo-scope (for example, a hospital or retail store), or to limit access to a chatty application if the power is off Wi-Fi so reduce costs.
Whether the need is the device or application management, almost all organizations need to make content available to users on a device. So secure content access and management is almost always a requirement, especially for organizations that are regulated or process business information or sensitive customer.
So if the main driver for deploying the management of enterprise mobility is a necessity for the device, app, or managing data, MDM is a core capability for many companies. Beyond that three-letter acronym you deploy depends on the situation. And what we are increasingly finding our intrepid mobile customer base, it is a combo.
0 Komentar