Professional Placement Resources LLC MDMs Risk Management Report

This report focuses on MDMs (Mobile Device Management) risk management for businesses, specifically referencing Professional Placement Resources LLC. It addresses the challenges of managing mobile devices in corporate networks and the associated security risks. The report emphasizes the importance of implementing reliable security solutions to protect sensitive data and maintain control over mobile devices. It explores various risk management approaches, including server-based rules-based action frameworks, passcode enforcement, and monitoring of device inventories and data usage. The rationale behind these strategies is to safeguard business confidentiality by preventing data leakages and ensuring secure access to company resources. The report also highlights the need to address threats such as data modification, malware, and unauthorized access. The report references key concepts such as Over-the-Air (OTA) and Wi-Fi communication, which are integral to MDM systems. This report provides a comprehensive overview of MDMs risk management, offering valuable insights for businesses seeking to secure their mobile devices.

Running Head: MDMs 1
Professional Placement Resources LLC Company and MDMs
Student’s Name
Institutional Affiliation.

MDMs 2
Introduction
The recent trends in the cooprate network are different from the traditional one in that, it
provides mobile phones to employees who can access companies’ resources remotely (Malik,
Singh, & Bopalli 2015). This mobility of users from an IT point of view is a challenge despite it
being favorable to the organization. Small and middle size business organizations like
Professional Placement Resources LLC Company, should be aware of how to manage risks that
come with the MDM technology (Harris & Patten, 2014).
Risk Management
The first approach to consider is providing reliable security solution. The strategy left, is
simplifying the control and configuration of the mobile devices in order to counter to the rapidly
changing mobile platforms which are threats to the organizational security and management
goals (Malik, Singh, & Bopalli, 2015).
Using a server-based rules-based action framework is a risk management against the
variety of devices to include mobile devices (Malik, Singh, & Bopalli, 2015). The status
information is monitored and changes are responded to automatically. Here, appropriate rules are
evaluated to determine which one is triggered. The administration pre-selects the rules which are
then automatically instigated. These rules are endorsed to work in various platforms to simplify
the administration process (Malik, Singh, & Bopalli, 2015).
When there is a determination that mobile devices with applications that share files, the
administration counters that by creating a rule that pops on the user’s mobile phone as a warning
(Malik, Singh, & Bopalli, 2015). The rule can send an email to the management team. Having
device front ends make information concerning installation of file-sharing applications reach the
admin.

MDMs 3
The administration may also enforce the passcode rule to all users. This will enhance the
security of the mobile devices. To do so the admin initiates an enforcement of a passcode
compliance template that enforces and configures the password (Jansen & Scarfone, 2008).
As a risk management, the company may include a template for enforcing control and
management that verifies that authenticity of the mobile OS and whether it is in its best working
condition (Liu et al., 2011). The company may also enforce a rule that restricts the user from
accessing the device’s services once the Simcards are changed. Rules concerning monitoring of
inventories and data charges like for example when the user has moved out of the country- Geo-
fencing rules. On data usage, the user will be notified when almost reaching to data limits.
Moreover, when devices become noncompliant emails are automatically sent to the admins
(Malik, Singh, & Bopalli 2015).
Rationale
The need to counter the risks posed by the use of mobile devices is to protect the
confidentiality of the business by preventing leakages. This is done by adopting the MDM
system technology that manages both data stored in the devices as well as hardware (Chen,
Franklin & Regenscheid, 2012). The MDM’s wireless communication technology such as Over-
the-Air (OTA) and Wi-Fi (Rhee, Jeon & Won, 2012). When employees within the organization
use different devices and operating systems it is not easy for the organization to monitor how the
users access the computing resources in the organization network. Worse still, mobile users
always want to customize the phones to be used for both businesses and for pleasure. Mobile
phones like Apple devices use different operating systems which make it difficult for IT
managers to provide retreat against the variety of devices (Malik, Singh, & Bopalli 2015). The
MDM system identifies the risk –threats and deduces the security requirements. Threats come in

MDMs 4
many forms like leakage, modification of the system, bypassing the security functions, changing
data, infecting the MDM system with malware and many others (Rhee, Jeon & Won, 2012).

MDMs 5
References
Chen, L., Franklin, J., & Regenscheid, A. (2012). Guidelines on hardware-rooted security in
mobile devices (Draft). NIST Special Publication, 800(164), 10-11.
Harris, M., & P. Patten, K. (2014). Mobile device security considerations for small-and medium-
sized enterprise business mobility. Information Management & Computer Security, 22(1),
97-114.
Jansen, W., & Scarfone, K. (2008). Guidelines on cell phone and PDA security. NIST Special
publication, 800, 124.
Liu, F., Tong, J., Mao, J., Bohn, R., Messina, J., Badger, L., & Leaf, D. (2011). NIST cloud
computing reference architecture. NIST
Malik, J., Singh, R., & Bopalli, R. (2015). U.S. Patent No. 9,071,518. Washington, DC: U.S.
Patent and Trademark Office.
Rhee, K., Jeon, W., & Won, D. (2012). Security requirements of a mobile device management
system. International Journal of Security and Its Applications, 6(2), 353-358.