recommended reading

Pentagon’s blueprint for mobile devices lacks security details

U.S. Navy

This story has been updated.

The Defense Department on Friday released a mobile device strategy that provides top-level policy guidance on the use of smartphones and tablets, but offers no specifics on how to secure them for use on Defense networks.

Defense Chief Information Officer Teresa Takai wrote in a cover letter that the strategy “takes advantage of existing technology, the ability to use or build custom apps, and a workforce increasingly comfortable with mobile devices.”

“This strategy is not simply about embracing the newest technology -- it is about keeping the DoD workforce relevant in an era when information and cyberspace play a critical role in mission success,” Takai wrote.

Commercial smartphones and tablets that run under the Apple, Google Android, BlackBerry, Windows Phone 7 and Symbian operating systems offer a more cost-effective solution than development of custom hardware, the strategy said. But it added, “most do not come equipped out of the box with the security controls, access protocols and necessary security features required by DoD.”

The department “must develop policy and standards to guide the secure, yet rapid adoption of commercial devices” and needs to streamline the approval process for their use, the document said, but did not provide any timeline. The standards and policies also will cover the use of personally owned hardware on Defense networks, it said.

The Pentagon plans to set up a central mobile device management service at the enterprise level to ensure the security of mobile hardware. This will include over-the-air distribution of data, application and configuration settings and registration of end-user devices. Defense “must establish a federated mobile device management service to optimize operation and maintenance,” and support “access control, encryption, malware detection” and security updates, the strategy said.

This approach follows that of the Veterans Affairs Department, which in October 2011 said it planned to use mobile device management to secure Apple hardware used on its network.

Additionally, Defense should beef up its network infrastructure to include broadband 4G LTE cellular service and short-range wireless systems, the policy paper said. The Pentagon also should participate in international wireless standards bodies to help shape those standards to its requirements.

The policy calls for a Defense mobile application development framework and certification process that will support “low-cost, often faster development and delivery of simple but useful function to the warfighter and/or support personnel,” the document said.

Threatwatch Alert

Credential-stealing malware / User accounts compromised / Software vulnerability

Android Malware Infects More than 1M Phones, Adds 13,000 Devices a Day

See threatwatch report


Close [ x ] More from Nextgov

Thank you for subscribing to newsletters from
We think these reports might interest you:

  • Featured Content from RSA Conference: Dissed by NIST

    Learn more about the latest draft of the U.S. National Institute of Standards and Technology guidance document on authentication and lifecycle management.

  • PIV- I And Multifactor Authentication: The Best Defense for Federal Government Contractors

    This white paper explores NIST SP 800-171 and why compliance is critical to federal government contractors, especially those that work with the Department of Defense, as well as how leveraging PIV-I credentialing with multifactor authentication can be used as a defense against cyberattacks

  • Toward A More Innovative Government

    This research study aims to understand how state and local leaders regard their agency’s innovation efforts and what they are doing to overcome the challenges they face in successfully implementing these efforts.

  • From Volume to Value: UK’s NHS Digital Provides U.S. Healthcare Agencies A Roadmap For Value-Based Payment Models

    The U.S. healthcare industry is rapidly moving away from traditional fee-for-service models and towards value-based purchasing that reimburses physicians for quality of care in place of frequency of care.

  • GBC Flash Poll: Is Your Agency Safe?

    Federal leaders weigh in on the state of information security

  • Data-Centric Security vs. Database-Level Security

    Database-level encryption had its origins in the 1990s and early 2000s in response to very basic risks which largely revolved around the theft of servers, backup tapes and other physical-layer assets. As noted in Verizon’s 2014, Data Breach Investigations Report (DBIR)1, threats today are far more advanced and dangerous.


When you download a report, your information may be shared with the underwriters of that document.