Commercial Mobile Device (CMD) Policy Security Technical Implementation Guide (STIG)

This STIG contains the policy, training, and operating procedure security controls for the use of CMDs in the DoD environment. The previous version of this STIG (V1R8) was called the Smartphone Policy STIG. Comments or proposed revisions to this document should be sent via e-mail to the following address: [email protected]

Details

Version / Release: V2R3

Published: 2013-03-12

Updated At: 2018-09-23 02:04:38

Compare/View Releases

Select any two versions of this STIG to compare the individual requirements

Select any old version/release of this STIG to view the previous requirements

Actions

Download

Filter


Findings
Severity Open Not Reviewed Not Applicable Not a Finding
Overall 0 0 0 0
Low 0 0 0 0
Medium 0 0 0 0
High 0 0 0 0
Drop CKL or SCAP (XCCDF) results here.

    Vuln Rule Version CCI Severity Title Description Status Finding Details Comments
    SV-30690r3_rule WIR-SPP-001 LOW Site physical security policy must include a statement outlining whether CMDs with digital cameras (still and video) are permitted or prohibited on or in this DoD facility. Mobile devices with cameras are easily used to photograph sensitive information and areas if not addressed. Sites must establish, document, and train on how to mitigate this threat. Information Assurance OfficerSecurity ManagerECWN-1
    SV-30692r4_rule WIR-SPP-003-01 MEDIUM A data spill (Classified Message Incident (CMI)) procedure or policy must be published for site CMDs. 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 da
    SV-30694r3_rule WIR-SPP-003-02 HIGH If a data spill (Classified Message Incident (CMI)) occurs on a wireless email device or system at a site, the site must follow required data spill procedures. If required procedures are not followed after a data spill, classified data could be exposed to unauthorized personnel.System AdministratorInformation Assurance OfficerVIIR-1, VIIR-2
    SV-30695r4_rule WIR-SPP-004 LOW Required procedures must be followed for the disposal of CMDs. If appropriate procedures are not followed prior to disposal of a CMD, an adversary may be able to obtain sensitive DoD information or learn aspects of the configuration of the device that might facilitate a subsequent attack.System AdministratorInformati
    SV-30697r3_rule WIR-SPP-005 HIGH Mobile operating system (OS) based CMDs and systems must not be used to send, receive, store, or process classified messages unless specifically approved by NSA for such purposes and NSA approved transmission and storage methods are used. DoDD 8100.2 states wireless devices will not be used for classified data unless approved for such use. Classified data could be exposed to unauthorized personnel.Information Assurance OfficerECWN-1
    SV-30698r4_rule WIR-SPP-006-01 LOW Mobile device users must complete training on required content before being provided mobile devices or allowed access to DoD networks with a mobile device. Users are the first line of security controls for CMD systems. They must be trained in using CMD security controls or the system could be vulnerable to attack.System AdministratorInformation Assurance OfficerPETN-1
    SV-30699r4_rule WIR-SPP-007-01 LOW The site Incident Response Plan or other procedure must include procedures to follow when a mobile operating system (OS) based mobile device is reported lost or stolen. Sensitive DoD data could be stored in memory on a DoD operated mobile operating system (OS) based CMD and the data could be compromised if required actions are not followed when a CMD is lost or stolen. Without procedures for lost or stolen mobile operati
    SV-30700r3_rule WIR-SPP-008-01 LOW The mobile device SA must perform a wipe command on all new or reissued CMDs and a STIG-compliant IT policy will be pushed to the device before issuing it to DoD personnel. Malware can be installed on the device at some point between shipping from the factory and delivery to DoD. The malware could result in the compromise of sensitive DoD information or result in the introduction of malware within the DoD network.System Adm
    SV-30701r3_rule WIR-SPP-008-02 LOW Mobile device software updates must only originate from approved DoD sources. Users must not accept Over-The-Air (OTA) wireless software updates from the wireless carrier or other non-DoD sources unless the updates have been tested and approved by the IAO. Unauthorized/unapproved software updates could include malware or cause a de
    SV-30702r3_rule WIR-SPP-009 MEDIUM CMD Instant Messaging (IM) client application must connect only to a DoD controlled IM server compliant with the Instant Messaging STIG. Non-DoD IM servers can be located anywhere in the world and may be under an adversary’s control. If a DoD CMD IM client connects to a non-DoD IM server, malware could be installed on the CMD from the server or sensitive DoD data on the CMD could be tran
    SV-30703r4_rule WIR-SPP-010 LOW The site wireless policy or wireless remote access policy must include information on required CMD Wi-Fi security controls. If the policy does not include information on Wi-Fi security controls, then it is more likely that the security controls will not be implemented properly. Wi-Fi is vulnerable to a number of security breaches without appropriate controls. These breaches
    SV-30705r4_rule WIR-SPP-011 LOW Mobile devices must be provisioned with DoD PKI digital certificates, so users can digitally sign and encrypt email notifications or other email messages required by DoD policy. DAA approval will be obtained prior to the use of software PKI certificates on mobile devices. S/MIME provides the user with the ability to digitally sign and encrypt email messages, to verify the digital signatures on received messages, and to decrypt messages received from others if those messages are encrypted. Digital signatures provide strong
    SV-30706r4_rule WIR-SPP-007-02 LOW Required actions must be followed at the site when a CMD has been lost or stolen. If procedures for lost or stolen CMDs are not followed, it is more likely that an adversary could obtain the device and use it to access DoD networks or otherwise compromise DoD IA.System AdministratorInformation Assurance OfficerECSC-1
    SV-30836r4_rule WIR-WRA-001 LOW Users must receive training on required topics before they are authorized to access a DoD network via a wireless remote access device. Improper use of wireless remote access to a DoD network can compromise both the wireless client and the network, as well as, expose DoD data to unauthorized people. Without adequate training remote access users are more likely to engage in behaviors that
    SV-30837r4_rule WIR-WRA-002 LOW The site must have a Wireless Remote Access Policy signed by the site DAA, Commander, Director, or other appropriate authority. Wireless clients, DoD data, and the DoD network could be compromised if operational policies for the use of wireless remote access are not documented by the site.System AdministratorInformation Assurance OfficerECWN-1
    SV-30838r3_rule WIR-WRA-003 LOW The site physical security policy must include a statement if CMDs with digital cameras (still and video) are permitted or prohibited on or in the DoD facility. Wireless client, networks, and data could be compromised if unapproved wireless remote access is used. In most cases, unapproved devices are not managed and configured as required by the appropriate STIG and the site’s overall network security controls
    SV-36045r4_rule WIR-SPP-006-02 LOW Mobile users must complete required training annually. Users are the first line of security controls for CMD systems. They must be trained in using CMD security controls or the system could be vulnerable to attack. If training is not renewed on an annual basis, users may not be informed of new security proced
    SV-43020r2_rule WIR-SPP-020 MEDIUM All non-core applications on the CMD must be approved by the DAA or the Command IT Configuration Control Board. Non-approved applications can contain malware. Approved applications should be reviewed and tested by the approving authority to ensure they do not contain malware, spyware, or have unexpected features (e.g., send private information to a web site, track
    SV-43023r2_rule WIR-SPP-021 HIGH A security risk analysis must be performed on a mobile application by the DAA or DAA authorized authority prior to the application being approved for use. Non-approved applications can contain malware. Approved applications should be reviewed and tested by the approving authority to ensure they do not contain malware, spyware, or have unexpected features (e.g., send private information to a web site, track