From Mobile Policy Security Requirements Guide
Part of SRG-MPOL-053
Associated with: CCI-001458
When a data spill occurs on a CMD, classified or sensitive data must be protected to prevent disclosure. After a data spill, the CMD must either be wiped using approved procedures, or destroyed if no procedures are available, so classified or sensitive data is not exposed. If a data spill procedure is not published, the site may not use approved procedures to remediate after a data spill occurs and classified data could be exposed.
Verify classified incident handling, response, and reporting procedures are documented in CMD procedures or security policies. If classified incident handling, response, and reporting procedures are not documented in site procedures or security policies, this is a finding. This requirement applies at both sites where CMDs are issued and managed and at sites where the CMD management server is located. At the CMD management server site, verify Incident Handling and Response procedures include actions to sanitize the CMD management server and email servers (e.g., Exchange, Oracle mail). At CMD sites, verify Incident Handling and Response procedures include actions for incident reporting and actions to safeguard classified CMD devices. The following actions will be followed for all CMD involved in a data spill: -BlackBerry CMDs: follow procedures in the DoD Data Spill Procedures Guide for BlackBerry CMDs located at http://iase.disa.mil/stigs/net_perimeter/wireless/CMD.html. -Windows Mobile, Android, and iOS CMDs: the CMD will be destroyed.
Create and publish an SOP for CMI on CMDs.
Lavender hyperlinks in small type off to the right (of CSS
class id
, if you view the page source) point to
globally unique URIs for each document and item. Copy the
link location and paste anywhere you need to talk
unambiguously about these things.
You can obtain data about documents and items in other
formats. Simply provide an HTTP header Accept:
text/turtle
or
Accept: application/rdf+xml
.
Powered by sagemincer