DOCSLIB.ORG

Netflix Security Requirements for Android Platforms Version 1.0 December 6, 2010

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Netflix Security Requirements for Android Platforms Version 1.0 December 6, 2010 Netflix Security Requirements for Android Platforms Version 1.0 December 6, 2010 Netflix Confidential Overall Security Philosophy • Netflix and Partners are working together to create a market for connected platforms and services • For long-term success, this requires a healthy and secure ecosystem – Based on best practices – Transparency between content, service, and platform partners – Proactive cooperation, rapid response • Our mutual success depends on it – Breaches hurt everyone Netflix Confidential Typical Studio Requirements • Platforms must meet agreed-upon robustness specifications (Netflix Robustness Rules, DRM providers’ robustness rules) • Platform partners must submit sample products and security documentation to Netflix for certification. – Netflix must review documentation and assess compliance with robustness specifications • If a platform is breached, Netflix or partner may be required to revoke individual or class of platforms. • In case of extended breach or platform non-compliance, studio has option to suspend availability of content to the Netflix service. – Such action would adversely affect all platforms and all Netflix subscribers. Netflix Confidential Android vs. Studio Requirements • Most Android platforms have been “rooted” – yields full control of system – history suggests this problem will not go away • Once rooting occurs, Linux security model is insufficient to protect content -related assets • Without modification, these platforms do not allow Netflix to meet contractual obligations to studios • We are aggressively working with partners to address this vulnerability Netflix Confidential High-Level Platform Security Concerns • Content Protection – DRM keys – Content keys – AV content • Application Security – Application keys – Access to Netflix APIs & functionality – Non-modifiability – Non-migrateability Netflix Confidential Content Protection: DRM Keys • Group key – typically provisioned in manufacturing – one key for entire class of devices (e.g. model) – signs self-generated device certificates (it’s a CA key) – this is a very -high -value asset • Device key/certificate – typically self-generated by device, signed by group key – used in DRM license transactions – provides access to content keys – this is a high-value asset Netflix Confidential Content Protection: AV Content • Content key – used to decrypt content packets – because encrypted content is hosted by CDNs, these have a long lifetime – with content key and matching URL, can download and decrypt premium content title – this is a high -value asset • Content – decrypted, compressed content has moderately high value • can easily export regardless of local processing/encoding power – uncompressed content has lower value than compressed content • harder to export (depending on system) • system may not have high-speed encoding capability • if a 90-minute movie takes 6 hours to rip not so interesting to attacker • if platform supports high-speed encoding, more of an issue Netflix Confidential Content Protection Overview DRM License DRM keys at risk Most important protection (or) decrypt license best attacks here! Encrypted (Compressed) Video Content key at risk Most important protection (or) decrypt content best attacks here! Compressed Decrypted Video Fast, high quality Very important protection (or) ripping decode really great attack here! Uncompressed Decrypted Video Slow, good quality Some protection (or) render ripping minor attack here! Video Frames Netflix Confidential Application Security: High-Level Objectives • Protect Netflix application keys – Not as valuable as DRM keys, but must be protected to a suitable level • Protect access to Netflix APIs and functionality – Only authorized code/scripts allowed to access Netflix specific APIs • Protect application against modification (runtime or static) – Attackers must not be able to arbitrarily modify Netflix binaries for own use • Non-migrateability – Application can’t be moved to less-restrictive generic x86, in VM, etc. Netflix Confidential Meeting Application/Content Security Objectives • Content and application security are a function of execution environment security/trust • Abstractly, we require assets and selected application elements to reside in a “Trusted Execution Environment” (TEE) • May not be practical to protect some elements in TEE (e.g. application APIs) • TEE can be realized in various ways, with relative trust level varying depending on implementation details Netflix Confidential Defining a TEE • Provides the hardware/software controls required to meet robustness requirements • Required Properties – Meets minimum required robustness levels in face of attack • protects DRM keys • protects content keys • protects content • protects Netflix keys/credentials – Facilitates revocation/renewal in case of breach • provides unique and robust platform identification • binds application to platform Netflix Confidential TEE: Abstract Overview Netflix Confidential Numerous Ways to Implement TEE • Closed platform – typical CE streaming device • secure boot, secure update, strictly controlled firmware – no console, no native binary installation – generally requires professional tools, skills to subvert • Semi-closed platform w/multiple cores (hardware TEE) – sensitive operations run on “security” core • same security properties of closed platform • security core controls – OTP/keys – internal SRAM – sometimes can isolate/protect decrypted content – “application” core runs untrusted code Netflix Confidential Hardware TEE Example Netflix Confidential Numerous Ways to Implement TEE (2) • Semi-closed platform w/TrustZone – secure/non-secure world abstraction supported by hardware – processor can switch into protected “secure world” mode – sensitive operations run in “secure world” mode • same security properties of closed platform • secure world controls – OTP/keys – internal SRAM – sometimes can isolate/protect decrypted content – “normal world” runs untrusted code Netflix Confidential TrustZone TEE example *copied from “TrustZone: Integrated Hardware and Software Security”, Information Quarterly, Volume 3, Number 4, 2004 Netflix Confidential Numerous ways to Implement TEE (3) • Virtualization – with secure boot, robust hypervisor, and MMU/MPU, functionally equivalent to HW TEE, TrustZone – hypervisor + MMU/MPU enforces isolation of sensitive operations/keys – may meet robustness rules for SD/HD if compressed decrypted buffers are protected Netflix Confidential Numerous Ways to Implement TEE (4) • Software TEE – Challenge is in providing effective isolation between trusted and untrusted elements – Tools that can help: • rigorous obfuscation techniques • white -box cryptography • anti-debugging techniques • runtime tampering/integrity checks • policy/containment framework (e.g. SELinux, grsecurity) – Software TEE can always be defeated by an attacker with enough time/motivation, but may be sufficient for protecting most content Netflix Confidential TEE and Android • Properly implemented TEE provides foundation for meeting Netflix security requirements with Android-based platform • Whether a particular implementation is sufficient comes down to platform design questions: – Can TEE isolate secure store from Android? • implies exclusive TEE access to OTP/keys – Can DRM operations be isolated in TEE? • cryptographic operations relating to license acquisition, content key management/use must run in secure environment – Can all Netflix cryptographic operations be isolated in TEE? • NCCP encryption/decryption run in secure environment – Assuming Android is rooted, how much of playback pipeline can be protected? Netflix Confidential TEE and Android, cont. • Even with robust TEE, some assets may be difficult to protect • How do we adapt Netflix robustness requirements to this reality? • Studios have generally traded increased risk for reduced content quality (HD SD) – we think this can be used to accommodate some design choices/constraints Netflix Confidential Netflix Robustness Requirements for SD/HD • Minimum requirements for SD – TEE protects DRM credentials, content keys, Netflix keys – protect decrypted, compressed content • if not in TEE, requires kernel-enforced memory isolation • partner acknowledges and accepts risk of platform revocation • Minimum requirements for HD – meet all SD requirements – provisioned with device-unique credentials (e.g. Kpe/Kph) – TEE protects decrypted, compressed content – protect uncompressed content • if not in TEE, requires kernel-enforced memory isolation • partner acknowledges and accepts risk of platform revocation Netflix Confidential Approval Process for Android Platforms • Choose TEE architecture based on platform characteristics (hardware, software, or hybrid) • Based on quality target (SD vs. HD), determine best way to implement – secure store – DRM operations – Netflix protocol cryptography operations – playback pipeline protection • Netflix evaluates specification against robustness requirements, works with partner to close any gaps Netflix Confidential.
Load more

Recommended publications
  • Structuring the Smartphone Industry: Is the Mobile Internet OS Platform the Key?
    A Service of Leibniz-Informationszentrum econstor Wirtschaft Leibniz Information Centre Make Your Publications Visible. zbw for Economics Kenney, Martin; Pon, Bryan Working Paper Structuring the smartphone industry: Is the mobile internet OS platform the key? ETLA Discussion Papers, No. 1238 Provided in Cooperation with: The Research Institute of the Finnish Economy (ETLA), Helsinki Suggested Citation: Kenney, Martin; Pon, Bryan (2011) : Structuring the smartphone industry: Is the mobile internet OS platform the key?, ETLA Discussion Papers, No. 1238, The Research Institute of the Finnish Economy (ETLA), Helsinki This Version is available at: http://hdl.handle.net/10419/44498 Standard-Nutzungsbedingungen: Terms of use: Die Dokumente auf EconStor dürfen zu eigenen wissenschaftlichen Documents in EconStor may be saved and copied for your Zwecken und zum Privatgebrauch gespeichert und kopiert werden. personal and scholarly purposes. Sie dürfen die Dokumente nicht für öffentliche oder kommerzielle You are not to copy documents for public or commercial Zwecke vervielfältigen, öffentlich ausstellen, öffentlich zugänglich purposes, to exhibit the documents publicly, to make them machen, vertreiben oder anderweitig nutzen. publicly available on the internet, or to distribute or otherwise use the documents in public. Sofern die Verfasser die Dokumente unter Open-Content-Lizenzen (insbesondere CC-Lizenzen) zur Verfügung gestellt haben sollten, If the documents have been made available under an Open gelten abweichend von diesen Nutzungsbedingungen
    [Show full text]
  • Internet of Nano-Things, Things and Everything: Future Growth Trends
    future internet Review Internet of Nano-Things, Things and Everything: Future Growth Trends Mahdi H. Miraz 1 ID , Maaruf Ali 2, Peter S. Excell 3,* and Richard Picking 3 1 Centre for Financial Regulation and Economic Development (CFRED), The Chinese University of Hong Kong, Sha Tin, Hong Kong, China; [email protected] 2 International Association of Educators and Researchers (IAER), Kemp House, 160 City Road, London EC1V 2NX, UK; [email protected] 3 Faculty of Art, Science and Technology, Wrexham Glyndwrˆ University, Wrexham LL11 2AW, UK; [email protected] * Correspondence: [email protected]; Tel.: +44-797-480-6644 Received: 22 June 2018; Accepted: 25 July 2018; Published: 28 July 2018 Abstract: The current statuses and future promises of the Internet of Things (IoT), Internet of Everything (IoE) and Internet of Nano-Things (IoNT) are extensively reviewed and a summarized survey is presented. The analysis clearly distinguishes between IoT and IoE, which are wrongly considered to be the same by many commentators. After evaluating the current trends of advancement in the fields of IoT, IoE and IoNT, this paper identifies the 21 most significant current and future challenges as well as scenarios for the possible future expansion of their applications. Despite possible negative aspects of these developments, there are grounds for general optimism about the coming technologies. Certainly, many tedious tasks can be taken over by IoT devices. However, the dangers of criminal and other nefarious activities, plus those of hardware and software errors, pose major challenges that are a priority for further research. Major specific priority issues for research are identified.
    [Show full text]
  • Id, Conf 20Xx
    ID, CONF 20XX - Where is the policy enforced? -- When is the policy imposed? -- What is protected by the policy? (fine grained) -- What is protected by the policy? (coarse grained) -- Requirements of the person applying the sandbox -- Requirements of the application -- Security Policy Type -- Policy enforcements place in kill chain -- Policy Management -- Policy Construction -- Validation Claim -- Validation -- KCoFI, Oakland 2014 - Where is the policy enforced? -- System: “KCoFI protects commodity operating systems from classical control- flow hijack attacks, return-to-user attacks, and code segment modification attacks.” When is the policy imposed? -- Hybrid: “KCoFI has several unique requirements. First, it must instrument commodity OS kernel code; existing CFI enforcement mechanisms use either compiler or binary instrumentation [4], [10], [18]. Second, KCoFI must understand how and when OS kernel code interacts with the hardware. For example, it must understand when the OS is modifying hardware page tables in order to prevent errors like writeable and executable memory. Third, KCoFI must be able to control modification of interrupted program state in order to prevent ret2usr attacks.” What is protected by the policy? (fine grained) -- Code instructions: See Where is the policy enforced? What is protected by the policy? (coarse grained) -- System Level Component: See Where is the policy enforced? Requirements of the person applying the sandbox -- Install a tool: “The SVA-OS instructions described later in this section are implemented as a run-time library that is linked into the kernel.” Requirements of the application -- Use special compiler: “All software, including the operating system and/or hypervisor, is compiled to the virtual instruction set that SVA provides.” Requirements of the application -- Use sandbox as framework/library: “Because the operating system must interface with the hardware via the SVA-OS instructions, it must be ported to the SVA virtual instruction set.
    [Show full text]
  • Closed Systems” an AnTrust Problem?
    Volume 7 I Number 1 I Spring 2011 Are “Closed Systems” an Antrust Problem? Hanno F. Kaiser Latham & Watkins LLP Published in Compeon Policy Internaonal (print ISSN 1554-0189, online Copyright © 2011 ISSN 1554-6853) Spring 2011, Vol. 7. No. 1. For more arcles and Compeon Policy Internaonal, I informaon, visit www.compeonpolicyinternaonal.com Inc. Are “Closed Systems” an Antitrust Problem? By Hanno F. Kaiser* losed computer systems have come under attack as harmful to freedom, Cinnovation, and competition. Open computer systems, in contrast, are said to promote such values. This article assesses the specific claim that closed sys- tems, compared to open systems, are inherently anticompetitive. It concludes that competition policy arguments against closed systems are at best inconclu- sive and that closed systems should not be put in an antitrust suspect class. *Partner, Latham & Watkins LLP, San Francisco. The views in this article are my own, so please do not impute them to my firm or my clients. This article is licensed under a Creative Commons Attribution 3.0 license. 91 Hanno F. Kaiser I. Civic and Economic Criticisms of “Closed Systems” In his influential book The Future of the Internet and How to Stop It1 Jonathan Zittrain argues that we are headed for a future in which general purpose comput- ers, which he calls “generative systems,” will be replaced by locked-down, teth- ered computing appliances:2 “The PC revolution was launched with PCs that invited innovation by oth- ers. So, too, with the Internet. Both were generative: they were designed to accept any contribution that followed a basic set of rules (either coded for a particular operating system, or respecting the protocols of the Internet.
    [Show full text]
  • Who Owns Your Conversations?
    Who owns your conversations? We’re about to see a major shake-up in how people communicate within the workplace. It’s called Element. Element is the pioneer of Universal Secure Collaboration. The world has changed Now more than ever, organisations face challenges with people Element changes this. collaborating. Designed to provide a radical new way of messaging and collaborating, Internally and externally, they face an unmanaged mix of traditional, Element is for those who have woken up to the severe downsides out-of-date collaboration tools and consumer-grade messaging apps. inherent with traditional messaging and collaboration tools and saves This leaves organisations with data strewn across multiple services, them from: with little control or clarity about how the data is secured, managed, accessed or audited. Loss of data ownership These applications - like Microsoft Teams, Signal, Slack, Telegram, Walled garden apps hampering true, open collaboration WhatsApp and Zoom - operate on an overly centralised internet, which Flawed, obfuscated encryption leaves data vulnerable enables corporate and nation-state datamining and routine surveillance. The result? Individuals and organisations relinquish control of their data. The world has changed, it’s time to change with it 2 The need for decentralisation The endemic issues within traditional messaging and collaboration But decentralised is super-difficult and incredibly time-consuming. apps stem from centralisation. It’s why commercial firms, and most investors, have favoured centralised The centralised products and services and the now centralised, systems - they deliver a faster return. The downside, which end-users formerly, open internet puts too much power in too few hands, now feel, is their loss of control and privacy.
    [Show full text]
  • Voice Assistants Used on Smartphones
    Voice Wars: Smart Speakers, Voice Assistants, and Strategies for Building a Successful Voice Ecosystem by Hans Wang B.S. Electrical Engineering and Computer Science University of California, Berkeley, 2009 SUBMITTED TO THE SYSTEM DESIGN AND MANAGEMENT PROGRAM IN PARTIAL FULLFILLMENT OF THE REQUIREMENTS FOR THE DEGREE OF MASTER OF SCIENCE IN ENGINEERING AND MANAGEMENT AT THE MASSACHUSETTS INSTITUTE OF TECHNOLOGY JUNE 2019 @2019 Hans Wang. All rights reserved. The author hereby grants to MIT permission to reproduce and to distribute publicly paper and electronic copies of this thesis document in whole or in part in any medium now known or hereafter created. Signature redacted- Signature of Author: System Design & Management Program ^ ^ A -May 10, 2019 Signature redactea Certified by: V Michael A.M. Davies Senior Lecturer, Integra d Design & Management Program Signature redacted Thesis Supervisor Certified by: t / Blade Kotelly Senior Lecturer, Bernard M. Gordon-MIT Engineering Leadership Program Thesis Supervisor Signature redacted Accepted by: f Joan Rubin OF TECHNOLOGY Executive Director, System Design & Management Program JUN 2 72019 LIBRARIES MCHIVES This page is intentionally left blank 2 Voice Wars: Smart Speakers, Voice Assistants, and Strategies for Building a Successful Voice Ecosystem by Hans Wang Submitted to the System Design and Management Program on May 10, 2019 in Partial Fulfillment of the Requirements for the Degree of Master of Science in Engineering and Management ABSTRACT In recent years, voice-powered digital assistants have exploded into the consumer mainstream as an important new form of human-computer interaction. Powered by dramatic improvements in speech recognition and artificial intelligence (Al) technologies over the last decade, digital voice assistants are now abundantly prevalent in modem consumer electronic devices ranging from mobile phones, to smart speakers, to wearables.
    [Show full text]
  • A Comparison of Inter-Organizational Business Models of Mobile App Stores: There Is More Than Open Vs
    Journal of Theoretical and Applied Electronic Commerce Research This paper is available online at ISSN 0718–1876 Electronic Version www.jtaer.com VOL 6 / ISSUE 2 / AUGUST 2011 / 63-76 DOI: 10.4067/S0718-18762011000200007 © 2011 Universidad de Talca - Chile A Comparison of Inter-Organizational Business Models of Mobile App Stores: There is more than Open vs. Closed Roland M. Müller1, Björn Kijl2 and Josef K. J. Martens3 1 Berlin School of Economics and Law, Department of Information Systems, [email protected] University of Twente, School of Management and Governance, 2 [email protected], 3 [email protected] Received 16 January 2011; received in revised form 17 April 2011; accepted 18 May 2011 Abstract The purpose of this paper is to analyze the competition among mobile app stores for smart mobile media devices. Therefore, the business models of seven mobile app stores are analyzed with a special focus on Apple and Google. We use e3-value modelling – a formal business modelling technique – for analyzing the critical elements of these mobile ecosystems. The analysis of the app store ecosystems allows a differentiated view on the different strategies of the app store owners. Additionally, we look at the impact of network effects, economies of scale, platform differentiation, quality assurance, and transaction costs on the design of mobile application markets. This theoretical model allows a deeper discussion about the design choices and success factors in the different app store cases. Based on our analysis, we expect that the open versus closed models discussion becomes less relevant – so-called open platforms have closed aspects as well as the other way around – and that competitive differentiation and segmentation strategies will become increasingly critical in order to strengthen the competitive positioning of the different app store platforms.
    [Show full text]
  • IT Service Platforms: Their Value Creation Model and the Impact of Their Level of Openness on Their Adoption
    Available online at www.sciencedirect.com ScienceDirect Procedia Computer Science 68 ( 2015 ) 173 – 187 HOLACONF - Cloud Forward: From Distributed to Complete Computing IT Service Platforms: Their Value Creation Model and the Impact of their Level of Openness on their Adoption Selam Abrham Gebregiorgisa, Jörn Altmanna* aTechnology Management, Economics, and Policy Program, Seoul Nationa University, Gwanak-Ro 1, Seoul 151-742, South-Korea Abstract Many IT service platforms (e.g., cloud computing platforms) are built as closed systems. They do not allow their customers to interoperate with other platforms or port their data to other platforms. As switching to a different system is costly, customers of a closed IT system can be considered locked in. Consequently, potential customers, who are aware of this lock-in issue, do not adopt cloud services. Opening up an IT service platform, however, reduces users’ concerns about lock-in and its associated switching cost. It is even predicted that an IT service platform gets more attractive, if it opens up. This paper validates this prediction by analyzing the level of openness (i.e., interoperability, portability, and usability) of cloud computing platforms on their adoption. For the validation, we develop a value creation model for IT service platforms. Based on this value creation model and a specification of requirements of open cloud computing platforms, the relationship between the openness of IT service platforms and the adoption of IT service platforms (i.e., attractiveness) is analyzed in detail. In particular, our results show that the level of openness plays a major role in the adoption of IT service platforms of emerging service providers.
    [Show full text]
  • Cross-Platform Development of Mobile Applications -Evaluation of the Phonegap Framework
    Cross-platform development of mobile applications -Evaluation of the PhoneGap framework José Calla Guzmán Victor Cernea Bachelor thesis Computer Engineering CHALMERS UNIVERSITY OF TECHNOLOGY Department of Computer Science and Engineering Gothenburg 2012 Innehållet i detta häfte är skyddat enligt Lagen om upphovsrätt, 1960:729, och får inte reproduceras eller spridas i någon form utan medgivande av för fattaren. Förbudet gäller hela verket såväl som delar av verket och inkluderar lagring i elektroniska och magnetiska media, visning på bildskärm samt bandupptagning. José Calla Guzmán, Victor Cernea, Göteborg 2012 Abstract This thesis investigates the benefits and drawbacks of cross-platform mobile app development by developing a smartphone app using the PhoneGap framework. A web based thesis app is created for use on Android, iPhone and Windows Phone smartphones. The implementation of the app is based on a single codebase of the standard web development technologies - HTML, CSS and JavaScript. The application supports Android version 2.2 or later and for iOS version 4.2.1 or later is accepted. On Windows Phone the application is designed to be operational from version 7. The compatibility of the application on any tablets is not tested. The result will reveal problems that may encounter and notable issues that one must take in consideration when using the software development method of cross-platform. Sammanfattning Denna rapport utreder för- och nackdelar med plattformsoberoende mobilapputveckling genom att utveckla en smartphone app med PhoneGap-ramverket. En webbaserad konferensapp skapas för användning på Android, iPhone och Windows Phone smartphones. Implementationen av applikationen är byggd på en enda kodbas skriven i de vanliga webbutvecklingsspråken - HTML, CSS och JavaScript.
    [Show full text]
  • Developer Dilemmas in a Closed Mobile Application Market Platform
    Fool’s gold? Developer dilemmas in a closed mobile application market platform Joni Salminen, Jose Teixeira Turku School of Economics University of Turku, Finland {Joni.Salminen,Jose.Teixeira}@utu.fi Abstract. In this paper, we outline some potential conflicts that platform owners and software developers face in mobile application markets. Our arguments are based on comments captured in specialized online discussion forums, in which developers gather to share knowledge and experiences. The key findings indicate conflicts of interests, including 1) intra-platform competition, 2) discriminative promotion, 3) entry prevention, 4) restricted monetization, 5) restricted knowledge sharing, 6) substitution, and 7) strategic technology selection. Opportunistic platform owners may use their power to discriminate between third-part software developers. However, there are also potential strategic solutions that developers can apply; for example diversification (multi-homing), syndication and brand building. Keywords: Platform, Ecosystem, Technological Strategy, Software distribution, E-commerce, AppStore 1 Introduction Although the rise of mobile application markets is a fairly recent phenomenon, using platforms1 for distributing software, however, is not a new idea. For example, Linux has since long incorporated a centralized “market” for distributing software, while also introducing the one-click launch of applications. In addition to distribution2, application-platforms enable developers to monetize their offerings and capture new customers. Therefore, developers can delegate to the platform owner critical business functions while concentrating on development – a benefit often appreciated by technology-focused founders. Platforms are associated with network effects [1]: the more consumers a platform accumulates, the more feasible it is for developers to join, and vice versa. Because 1 'Platform' is used in this paper to refer to commercial platforms, consisting of a platform owner and participants.
    [Show full text]
  • 175 STCTTS 17 E Bis Original: English
    STC 175 STCTTS 17 E bis Original: English NATO Parliamentary Assembly SCIENCE AND TECHNOLOGY COMMITTEE THE INTERNET OF THINGS: PROMISES AND PERILS OF A DISRUPTIVE TECHNOLOGY REPORT Matej TONIN (Slovenia) Rapporteur Sub-Committee on Technology Trends and Security www.nato-pa.int 8 October 2017 175 STCTTS 17 E bis TABLE OF CONTENTS I. INTRODUCTION ................................................................................................................... 1 II. WHAT IS THE INTERNET OF THINGS? ............................................................................... 2 A. THE BASICS ................................................................................................................ 2 B. TECHNICAL AND ENGINEERING CHALLENGES ...................................................... 4 C. THE FUTURE OF THE IOT: THE BUSINESS CASE, SECURITY AND PRIVACY ....... 6 D. WHAT IS THE ROLE OF NATO AND THE EU ............................................................. 8 III. ARMED FORCES AND THE IOT ........................................................................................... 9 A. THE POTENTIAL OF IOT TECHNOLOGIES FOR THE ARMED FORCES .................. 9 B. RISKS OF IOT APPLICATIONS IN THE MILITARY ................................................... 10 C. THE MILITARY AND THE COMMERCIAL SECTOR .................................................. 10 IV. CRITICAL INFRASTRUCTURE AND THE IOT .................................................................... 11 V. CONCLUSIONS .................................................................................................................
    [Show full text]
  • Platform Economics in Mechanical Engineering
    Platform Economics in Mechanical Engineering Challenges – opportunities – courses of action May 2018 THE SUCCESS OF PLATFORMS – AN EXAMPLE FOR MECHANICAL ENGINEERING TO FOLLOW? Platform companies such as Amazon and Google have changed many B2C markets from the ground up. As they now penetrate the B2B segment, German engineering companies too are joining the fray. Though the correspond- ing ecosystem is still a work in progress, the trend is clear: In the industrial environment too, platform-based appli- cations are becoming the key factor of differentiation. That, however, confronts the corporate sector – especially small and medium-sized enterprises (SMEs) – with huge challenges. Further barriers to entry are raised by the complexity and diversity of the platforms currently available and the question marks that still hang over business cases, not to mention the need to acquire complete- ly different knowledge and skill sets compared to the industry's traditional core business. For this study, Germany's Mechanical Engineering Industry Association VDMA, trade fair operator Deutsche Messe and Roland Berger investigated the platform economy in the German mechanical and plant engineering sector. The 15 VDMA members that took part in a series of workshops and discussions include firms of all sizes and at every link in the value chain – from midcaps to blue chips, from traditional mechanical and plant engineering companies to providers of factory automation and software solutions. At the time of the study, all these companies had already gained relevant experience with platforms – building them, using them or engaging in early-stage operation – and each was therefore able to contribute varying perspectives.
    [Show full text]