Join Now
Interested companies are encouraged to review the Benefits of Membership and apply today!
Join NowGlossary
Unfamiliar with a term used in this section? Check the TCG Glossary of TechnicalTerms for the definition.
View Glossary
Learn More
- Frequently Asked Questions - Trusted Mobility Solutions
Trusted Mobility Solutions - FAQs
Why did the Trusted Computing Group (TCG) form the Trusted Mobility Solutions (TMS) Work Group (WG)?
What problems does the TMS WG intend to address?
How will the TMS WG address these problems?
What is a “trusted mobility solution”?
The TMS WG defines a "trusted mobility solution" as one that addresses all of the following features and concepts:
- Mobile endpoints are managed computing resources.
- One or more mobile endpoint management functions are defined and operate as part of the solution.
- Mobile endpoints can connect to a network, preferably using TCG TNC network attachment integrity verification.
- Mobile endpoints can be physically moved by a person with ease, or in conjunction with the movement of a person (e.g., in an automobile).
- Mobile endpoint trustworthiness is enabled and/or supported by one or more capabilities that are conformant to TCG technical specifications (e.g., TPM or MTM).
- Mobile endpoint trusted boot, applications, databases, security policies, etc., can be reliably deployed in order to support a trusted execution environment (e.g., using a TCG Opal SED).
Laptops, tablets, and smartphones are the mobile endpoints that are the primary focus for the TMS WG. Other portable consumer devices (e.g., radios, cameras, music players, sensors, and analog devices) are out-of-scope in the TMS WG charter.
What types of deliverables will the TMS WG produce?
The TMS WG will define use cases and solution requirements for managing and provisioning trusted mobile, network-connected endpoints, and will document a unifying, integrated architectural framework that will enable the interoperable use of trusted computing standards. Although, the TMS WG will not develop new TCG technical standards, the work group will define implementation guidance, best practices, and also recommendations for updates to existing relevant TCG standards. Furthermore, new approaches to demonstrate the solution certification and compliance may also be developed.
What is the relationship between TMS WG and other TCG Work Groups, such as the Mobile Phone Work Group (MPWG)?
TCG Work Groups, such as the Mobile Phone Work Group (MPWG), define security-related use cases, requirements and technical specifications For MPWG, the focus is on securely booting mobile and embedded systems that provide TCG TPM-compliant features like remote attestation, key management, and authentication and secure storage for applications and OS services, as well as support for local and remote ownership to address corresponding security requirements.
Moreover, the purpose of the TMS WG is to synthesize requirements and technical specifications from multiple TCG technical WGs to provide an integrating framework for mobility solutions architectures.
The objectives of the TMS WG may also expose additional requirements for future TCG specifications or even for new TCG WGs in order to deploy a TMS solution. In these cases, the TMS WG will engage with the respective technical WGs to help refine the requirements.
Also, the trusted platform concepts developed by the TCG will require specific lifecycle management and integration into mobile solution architectures. The TMS WG will aim to assist other TCG work groups in demonstrating how the current and future specifications could contribute in enabling the trust models which make new mobile compute paradigms possible.
What existing TCG specifications are relevant to the efforts of the TMS WG?
Since the activities of the TMS WG are solutions-oriented, several TCG technical specifications may be applicable to our trusted mobile solutions architecture. The key examples include:
- MTM - Mobile Trusted Module (mobile and embedded subset of TPM)
- TPM - Trusted Platform Module (encryption and other keys, hardware security)
- TNC - Trusted Network Connect (integrity measurement and verification)
- IF-MAP - Metadata Access Point (interworking across security architectures)
- OPAL - Self-Encrypting Drive (secure OS and application data storage)
- TMI - Trusted Multi-Tenant Infrastructure (separation of consumer and business applications)
The TMS WG use cases should include a selection of these TCG technical specifications to show how the integration of these capabilities can be deployed, managed, and operated to meet the security objectives of particular reference implementations. Financial, telecommunications, and government TMS WG members and liaisons should propose and evaluate key TMS use cases.
Some people think that a TPM is hard to provision and manage for PCs. How is the mobile world different than PCs and how does the TMS WG aim to address this issue?
Certainly there are many issues that must be considered when provisioning and managing TPM or MTM-enabled devices, and the diversity of devices and interconnection technologies in the mobile world introduces even more complexity. This realization motivated the formation of the TMS WG to leverage the work of the other TCG WGs and other non-TCG standards groups that address the mobile world and explore the issues that enterprises face when provisioning and managing TCG technologies within mobility-enabled infrastructures. Using real-world use cases, the TMS WG will apply TCG standards within the mobile world and demonstrate how management challenges and technical risks can be handled in a cohesive and comprehensive manner. The TMS WG will work with other TCG WGs to resolve difficulties that are identified in the demonstration of these capabilities and propose recommendations for updates to TCG standards.
Are there any mobile devices that currently ship with a TPM or MTM?
To date, the MTM has been implemented primarily in company-internal and lab research projects. For example, Nokia Research Center has produced a GPL open source MTM add-on to the TPM emulator by Mario Strasser et al, and a reference implementation of the manufacturer profile of MTM (MRTM) for ARM TrustZone. Also, the Terminal Mode V1.0 standard recommends hardware-assisted MTM security for key storage and usage.
To ease both implementation and adoption, the newest MTM use cases introduce concepts where common interfaces for messaging - protocol data units (PDUs) and application programming interfaces (APIs) - are utilized, primarily between the OS and the trusted execution environment, but also between applications and the OS, to provide added value for service deployment.
How does the TMS WG collaborate with and complement the efforts of other forums or standards bodies involved in mobile security?
The primary focus of the TMS WG is to synthesize TCG-based technical specifications into an architectural framework, set of relevant use cases, demonstrated capabilities, and lessons learned. Other standards groups and forums also are working on secure mobility specifications, projects, and use cases such as the Global Platform, the Mobey Forum, the U.S. Government Mobile Applications Group and National Institute of Standards and Technology (NIST), and the German Federal Ministry of Education and Research through the ESUKOM project. The TMS WG plans to collaborate with these groups as their efforts relate to trusted computing and where TCG specifications can be applied.
What types of members participate in the TMS WG?
Current members of the TMS WG include a wide variety of participants: handset and other mobile platform providers, system integrators, chip manufacturers, network systems providers, hard drive manufacturers, system and application software vendors, and voices from academia, and government. This diversity of viewpoints and capabilities is essential to the development of robust solutions frameworks. The TMS WG cordially invites new or existing TCG members to participate in our development of trusted mobile solutions requirements and real-world demonstrations.
What kinds of expertise are needed for a member to contribute to the TMS WG?
The TMS WG welcomes members with all types and levels of expertise, who could contribute in exploring and resolving different issues associated with deploying the TCG technologies within the mobile devices ecosystem. A diversity of backgrounds will assist the TMS WG in ensuring that its recommendations have a widespread applicability within the mobile-device-equipped enterprises.
How can builders or users of trusted mobile solutions benefit from the work of the TMS WG?
The TMS WG will define specific recommendations for the use of TCG technologies in trusted mobile solutions. The builders of trusted mobile solutions can use these recommendations to ensure that their products meet the needs of diverse mobility communities. Users of trusted mobile solutions can use the recommendations that are specific to their needs to plan the purchase, deployment and management of appropriate and scalable trusted mobility solutions.
When do you expect builders or users of mobile solutions to benefit from the work of the TMS WG?
Mobile solutions providers or adopters can benefit immediately in improving their understanding of the application of TCG capabilities through participating in the ongoing work of TMS WG activities, such as the development of white papers, solution requirements, use cases, and the TMS architecture framework. In addition, the WG plans to deliver initial versions of these documents starting in the first and second quarters of 2012. The TMS WG deliverables should assist solutions providers and adopters to plan the development and deployment of trusted and scalable mobile solutions.
- 1-14