What is your first line of defense against cyberattacks? Secure endpoints! Endpoints are everywhere in the IIoT landscape. Without proper security, Industrial Internet of Things (IIoT) systems are not trustworthy, putting organizations, their missions and the greater public at increased risk. The viability of the IIoT depends on proper implementation of security to counter the growing and ever changing threats that are emerging. Addressing this challenge is critical to the success of the Industrial IoT, Industrie 4.0 and the Industrial Internet revolution. To that end, Industrial Internet Consortium members have developed a common security framework and an approach to assess cybersecurity in Industrial Internet of Things systems: The Industrial Internet Security Framework (IISF). Watch the webinar: https://youtu.be/t0GC4Fp-NXQ

1. IIoT Endpoint Security –
The Model in Practice
February 22, 2017
Industrial Internet Security Framework
#IICSeries

2. Guest Speakers
2
MARCELLUS BUCHHEIT
President and CEO, Wibu-Systems USA
Editor, Industrial Internet Consortium Security Framework
@WibuSystems
TERRENCE BARR
Head of Solutions Engineering, Electric Imp, Inc.
@electricimp

3. Motivation
3
Unprotected devices in internet are dangerous!
They can be used to:
• Intrude into local networks: stealing or deleting private data
• Block or alter websites or internet communication
• Upload viruses and start Denial-of-Service (DoS) attacks
Additional for IIoT:
• Shut down public or private services (electricity, water, sewer etc.)
• Prevent commercial usage (production, hospitals, hotels, PoS etc.),
• Damage or destroy industrial installations or produced parts

4. Motivation
4
Unprotected devices problematic for component manufacturer
• Example: FTC charges D-Link for unsecure routers and IP cameras
• https://www.ftc.gov/news-events/press-releases/2017/01/ftc-charges-d-link-put-consumers-privacy-risk-
due-inadequate
Unprotected devices problematic for users/operators
• Example: Point-of-Sale (POS) attack at Target end of 2013
• 40 million credit cards and 70 million addresses stolen
• Target paid $50M+ for settlements
• http://krebsonsecurity.com/2014/02/target-hackers-broke-in-via-hvac-company/

5. A few words about Wibu-Systems
5
• Wibu-Systems was founded in 1989 in Germany
• Global company targeting secure software licensing
• Offer security and licensing solutions for IIoT systems and devices
• More about the company: www.wibu.com
• More about the key product: http://www.wibu.com/codemeter
• More about IIoT security: http://www.wibu.com/embedded-software-
security
• And since 2015 member of the Industrial Internet Consortium (IIC)

6. About the IIC
Industrial Internet Consortium
Security Webinar
February 22, 2017
Kathy Walsh, walsh@iiconsortium.org
Director of Marketing

7. The Industrial Internet is Leading the Next Economic Revolution
7
GDP data extracted from the Futurist 2007

8. Bring Together the Players to Accelerate Adoption
8
Connectivity
Standards
Technology
Research Academia
Systems
Integration
Security
Government
Big Data Industries
The Industrial Internet:
A $32 trillion opportunity

9. The IIC: Things are Coming Together
9
Things are coming together.
Academia
Standards
Research Systems Integration
Government
IndustriesConnectivity
Technology
Big Data
Security

10. The Industrial Internet Consortium is a global, member supported
organization that promotes the accelerated growth of the Industrial
Internet of Things by coordinating ecosystem initiatives to securely
connect, control and integrate assets and systems of assets with people,
processes and data using common architectures, interoperability and
open standards to deliver transformational business and societal
outcomes across industries and public infrastructure.
Launched in March 2014 by five founding members:
AT&T, Cisco, General Electric, IBM & Intel.
The IIC is an open, neutral “sandbox” where industry, academia and
government meet to collaborate, innovate and enable.
Industrial Internet Consortium Mission
Over 250 Member Organizations
Spanning 30 Countries
10

11. Securing IIoT Endpoints --
The Model
Industrial Internet Consortium
Security Webinar
February 22, 2017
Marcellus Buchheit, mabu@wibu.com
Wibu-Systems USA Inc.

12. Overview
12
What is an endpoint?
Why endpoint security?
Security functions of an endpoint
Implementing endpoint security

13. What is an Endpoint?
13
The IIoT Landscape: Where are Endpoints?
E
P
E
PE
P
E
P
E
P
E
P
E
P

14. What is an Endpoint (II)?
14
IISF and IIC defines endpoints similar as ISO/IEC 24791-1:2010 standard does:
• An endpoint is one of two components that either implements and exposes an interface
to other components or uses the interface of another component.
IIC simplified this definition (see IIC Vocabulary, version 2.0):
• An endpoint is a component that has an interface for network communication.
… but added a note for clarification:
• An endpoint can be of various types including device endpoint or an endpoint that
provides cloud connectivity.
Endpoint 1 Endpoint 2
Communication

15. What is an Endpoint (III)?
15
The IIoT Landscape: Endpoints are
everywhere!
E
P
E
PE
P
E
P
E
P
E
P
E
P

16. What is an Endpoint (IV)?
16
Summary:
• Endpoints are everywhere in an IIoT System (including edge and cloud)
• One single (security) model for all locations
• A single computer, even a device, can have several endpoints
• Example Router: One LAN endpoint, one WAN endpoint
• Frequently shared code/data between multiple endpoints
• Endpoint and its communication is another model

17. Why endpoint security?
17
Endpoints are the only location in an IIoT system where:
• Execution code is stored, started and updated
• Data is stored, modified or applied (“Data at Rest” / “Data in Use“)
• Communication to another endpoint is initiated and protected
• Network security is analyzed, configured, monitored and managed
Result: An attack to an IIoT system typically starts in attacking one or more
endpoints:
• Try to access the execution code and analyze to find weak security
implementation
• Attack weak communication protection via network
• Modify or replace (“hijack”) the execution code in a malicious way
• ...

18. IISF Endpoint Protection Model
18

19. Threats and Vulnerabilities to an IIoT Endpoint
19
1. Hardware components
2/3. Boot process
4. Operating System
5. Hypervisor/Sep. Kernel
6. Non-OS Applications
7. Applications and their API
8. Runtime Environment
9. Containers
10. Deployment
11. Data at Rest, Data in Use
12. Monitoring/Analysis
13. Configuration/Management
14. Security Model/Policy
15. Development Environment

20. Endpoint security: Solutions
20
• Start with a clean design of the security model and policies
• Define endpoint identity, authorization, authentication
• How other endpoints see me? What can they do with me?
• Define proper data protection model
• Integrity and confidentiality, especially of shared data-in-rest but also data-in-
use
• Define secure hardware, BIOS, roots of trust
• Includes lifetime of hardware, BIOS update, consistent root of trust
• Select secure OS, hypervisor, programming language
• Consider lifetime of (open source?), dynamic of programming language
• Consider isolation principles (4 different models explained in IISF)
• Plan remote code update and provide code integrity
• Security has an unspecific expiration date: needs update
• Code integrity prevents malicious remote code-hijacking

21. Endpoint security: Solutions (II)
21
• Plan “beyond the basics” security instantly
• Plan security configuration and management
• For example: defining, replacing and updating of keys and certificates
• User-friendly setting of access rights and authorization
• Plan endpoint monitoring and analysis
• For example: log all security configuration changes
• Log all unexpected remote activity
• Provide user-friendly analysis, alerts etc.
• Implement “state of the art”:
• Have a team of experienced security implementers
• Use latest versions of development tools, OS, hypervisors, libraries
• Test a lot, including malicious attacks
• Prepare and test your first remote update

22. Securing IIoT Endpoints --
In Practice
Industrial Internet Consortium
Security Webinar
February 22, 2017
Terrence Barr, terrence@electricimp.com
Head of Solutions Engineering

23. Endpoint Security
Introduction to Electric Imp
23

24. Electric Imp
Industrial-strength IoT starts here
Secure IoT Connectivity Platform
Authorized Hardware
for connected devices
impOS™ and hardware
impCloud™
imp Enterprise API’s
BlinkUp™ & impFactory™
impSecure™
Proven IoT Deployments at Scale
• 2016: surpassed 1 Million WiFi/Ethernet devices
• 18B+ data messages per month
• 100+ customers; 105+ countries
Full Lifecycle, Trusted Security
• Passed security review
and pen-testing:
• In process: UL 2900-2-2: Cybersecurity Certification for
Industrial Controls plus first Affiliate program
• Aligned with IIC Security Framework
Fastest Prototype-to-Production
• 5 months for GE connected air conditioner
24© Property of Electric Imp, Inc.

25. Endpoint Security
Implementation Approach
25

26. Endpoint Security: Part of Integrated and Managed Security
Silicon-to-Cloud Security – Defense in Depth & Defense in Time
7. Full Lifecycle
Managed Services
1. Edge Device Security
incl. Secure Silicon &
Managed Software
4. Secure Communication
via Managed Tunnel
3. Trusted
Manufacture &
Commissioning
6. Secure Cloud and Application
Integration
2. Data Privacy, Integrity &
Confidentiality
5. Protected Public &
Private Cloud
26© Property of Electric Imp, Inc.

27. IISF Endpoint Protection Techniques Electric Imp Implementation
Protecting Endpoints: General Endpoint protection from the silicon upwards, every level tightly integrated and
tested for full coverage of security objective and no weak links
Architectural Considerations for
Protecting Endpoints
Designed from the ground up for resource-constrained IoT devices and real-world
use cases and proven in large-scale customer deployments
Endpoint Physical Security Disabled hardware interfaces, tampering destroys individual module
Establish Roots of Trust Unique per-device keys, secure provisioning via cloud device management
Endpoint Identity One-Time-Programming at module manufacturing time
Endpoint Access Control Mutual authentication with RSA certificates and ECC challenge-response
Endpoint Integrity Protection HSM protected keys, secure boot, non-execution barriers with cloud alerts
Endpoint Data Protection All processing on-die, all off-die storage with device-unique encryption.
TLS 1.2, AES-128, EDH forward secrecy.
Endpoint Monitoring and Analysis Extensive monitoring of security-sensitive operations
Endpoint Configuration and Management Endpoints managed, configured, and provisioned from the impCloud, all updates
signed, encrypted, and logged
Cryptography Techniques for Endpoint
Protection
AES-128 GCM+AEAD with device-unique keys, hardware accelerator and true
random used where available.
Isolation Techniques for Endpoint
Protection
Sandboxed application execution (VM), application updates separate from OS
updates
27© Property of Electric Imp, Inc.

28. Endpoint Security
Real-World Case Study
28

29. • Replace analogue lines
• Customer delight exceeds
expectations
• Recognized as Business
Transformation success story
1.5M
Customers
worldwide
Security
for regulated
markets
Reduce
service calls by
20%
ROI –
Payback in 45 days on
connectivity costs
alone
SmartLink™ device 29© Property of Electric Imp, Inc.

30. impSecureTM: Integrated Silicon-to-Cloud Security and Connectivity managed by Electric Imp
’Slide-In’ Postage Meter Retrofit for Device-to-Cloud Security and Connectivity
imp Application
Module
impOSTM
Meter
Integration
Code
Virtual Machine
paired Virtual Machine
Cloud
Meter
Code
Cloud
Integration
Code
Operations &
Device Lifecycle Management
Cloud Services
Electric Imp
Managed Cloud
USB
Commerce Cloud
Device-paired
Virtual Machines
Scalable to millions
of devices
No changes to meter
No changes to cloud
Audited and Tested
Meets Postal and Government
Security Requirements
WiFi
Ethernet
IP tunnel
&imp
SiliconSecurity
30© Property of Electric Imp, Inc.

31. Conclusion: Endpoint Security In Practice
Well-designed and implemented Endpoint Security is critical in IoT
• Large number of devices in field, subject to physical tampering for years
• Present or future breaches can reach disasterous proportions
Hardware-level security requires deep integration and skills
• Security boundaries, root of trust, defense-in-depth design, remote security
updates, security monitoring down to silicon, rock-solid reliability and scalability
Build on pre-integrated and proven silicon-to-cloud security platform
• Minimize time-to-market, risk of mistakes and undiscovered weak links
Must protect against future, unknown vulnerabilities
• Seperation of concerns allows offloading security maintenance to specialists
(‘Security-as-a-Service’)
31© Property of Electric Imp, Inc.

32. ®
Transforming the world
through the power
of secure connectivity
32© Property of Electric Imp, Inc.

33. Thank you!
33
Things are coming together.
Community. Collaboration. Convergence.
www.iiconsortium.org
Additional Resources available as attachments
• Industrial Internet Security Framework Document
• White Paper: Business Viewpoint of Securing the Industrial Internet
• Upcoming Monthly Webinars on IIC BrightTALK channel:
• March 2017 – Enabling & Securing the Smart Factory
• April 2017 Preview of IIC/I4.0 at Hannover Messe