4.4 Operations and Maintenance
All changes in this version
Title
Operations and Maintenance
Control
Operational processes that are particularly helpful for maintaining mobile device security, and thus should be performed regularly, include the following:
Checking for upgrades and patches to the mobile device solution components (including mobile device infrastructure components, mobile device operating systems, and mobile device applications), and acquiring, testing, and deploying the updates 12
12 Some mobile devices do not offer OS upgrades; even though a newer OS version might be generally available, it cannot be installed on a particular mobile device, often due to hardware limitations. This can significantly negatively impact the Ensuring that each mobile device infrastructure component (mobile device management servers, authentication servers, etc.) has its clock synced to a common time source so that its timestamps will match those generated by other systems
Reconfiguring access control features as needed based on factors such as policy changes, technology changes, audit findings, and new security needs
Detecting and documenting anomalies within the mobile device infrastructure through continuous monitoring, including unauthorized configuration changes to mobile devices. Such anomalies might indicate malicious activity or deviations from policy and procedures. Anomalies should be reported to other systems’ administrators as appropriate.
Keeping an active inventory of each mobile device, its user(s), and its applications
Providing training and awareness activities for mobile device users on threats and recommended security practices
Revoking access to or deleting an application that has already been installed but has subsequently been assessed as too risky to use
Scrubbing sensitive data from mobile devices before reissuing them to other users (see Section 4.5 for more information on data scrubbing)
Organizations should also periodically perform assessments to confirm that the organization’s mobile device policies, processes, and procedures are being followed properly. Assessment activities may be passive, such as reviewing logs, or active, such as performing vulnerability scans and penetration testing. More information on technical assessments is available from NIST SP 800-115, Technical Guide to Information Security Testing and Assessment [SP800-115].