Mutual Attestation of IoT Devices and TPM 2

Slides:



Advertisements
Similar presentations
November 9, 2009IETF 76 NEA WG1 NEA Working Group IETF 76 Co-chairs: Steve Hanna
Advertisements

Internet Protocol Security (IP Sec)
IPSec: Authentication Header, Encapsulating Security Payload Protocols CSCI 5931 Web Security Edward Murphy.
IKEv2 extension: MOBIKE Faisal Memon Erik Weathers CS 259.
Security at the Network Layer: IPSec
NAT TRAVERSAL FOR IPSEC Research Seminar on Datacommunications Software HIIT
Chapter 13 IPsec. IPsec (IP Security)  A collection of protocols used to create VPNs  A network layer security protocol providing cryptographic security.
IP Security IPSec 2 * Essential Network Security Book Slides. IT352 | Network Security |Najwa AlGhamdi 1.
Copyright© 2004 Trusted Computing Group - Other names and brands are properties of their respective owners. Slide #1 Putting Trust into the Network: Securing.
IKE message flow IKE message flow always consists of a request followed by a response. It is the responsibility of the requester to ensure reliability.
Faten Yahya Ismael.  It is technology creates a network that is physically public, but virtually it’s private.  A virtual private network (VPN) is a.
Chapter 6 Configuring, Monitoring & Troubleshooting IPsec
Copyright © 2005 Juniper Networks, Inc. Proprietary and Confidentialwww.juniper.net 1 Open Standards for Network Access Control Trusted Network Connect.
TNC Endpoint Compliance and Network Access Control Profiles TCG Members Meeting June 2014 Barcelona Prof. Andreas Steffen Institute for Internet Technologies.
Network Access Control for Education
Remote Access Chapter 4. Learning Objectives Understand implications of IEEE 802.1x and how it is used Understand VPN technology and its uses for securing.
Remote Access Chapter 4. Learning Objectives Understand implications of IEEE 802.1x and how it is used Understand VPN technology and its uses for securing.
1 Chapter 8 Copyright 2003 Prentice-Hall Cryptographic Systems: SSL/TLS, VPNs, and Kerberos.
1 Section 10.9 Internet Security Association and Key Management Protocol ISAKMP.
Cosc 4765 SSL/TLS and VPN. SSL and TLS We can apply this generally, but also from a prospective of web services. Multi-layered: –S-http (secure http),
1 IF-MAP: Open Standards for Coordinating Security Presentation for SAAG IETF 72, July 31, 2008 Steve Hanna
IPSec ● IP Security ● Layer 3 security architecture ● Enables VPN ● Delivers authentication, integrity and secrecy ● Implemented in Linux, Cisco, Windows.
TNC Proposals for NEA Protocols Presentation by Steve Hanna to NEA WG meeting at IETF 71 March 11, 2008.
70-293: MCSE Guide to Planning a Microsoft Windows Server 2003 Network, Enhanced Chapter 10: Planning and Managing IP Security.
NEA Working Group IETF meeting July 27, 2011 Jul 27, 2011IETF 81 - NEA Meeting1.
Lect 8 Tahani al jehain. Types of attack Remote code execution: occurs when an attacker exploits a software and runs a program that the user does not.
IPSec The Wonder Protocol Anurag Vij Microsoft IT.
IP Security (IPSec) Matt Hermanson. What is IPSec? It is an extension to the Internet Protocol (IP) suite that creates an encrypted and secure conversation.
Continuous Assessment Protocols for SACM draft-hanna-sacm-assessment-protocols-00.txt November 5, 20121IETF 85 - SACM Meeting.
Lecture 10 Page 1 CS 236 Online Encryption and Network Security Cryptography is widely used to protect networks Relies on encryption algorithms and protocols.
Copyright © 2009 Trusted Computing Group An Introduction to Federated TNC Josh Howlett, JANET(UK) 11 June, 2009.
11 SECURING NETWORK TRAFFIC WITH IPSEC Chapter 6.
Computer and Network Security
VPNs & IPsec Dr. X Slides adopted by Prof. William Enck, NCSU.
Prof. Andreas Steffen Institute for Networked Solutions
VPNs and IPSec Review VPN concepts Encryption IPSec Lab.
Chapter 5 Network Security Protocols in Practice Part I
IPSecurity.
Analysis of secured VoIP services
INF526: Secure Systems Administration
Firewall Issues Research Group GGF-15 Oct Boston, Ma Leon Gommans - University of Amsterdam Inder Monga - Nortel Networks.
CSE 4905 IPsec.
Encryption and Network Security
Virtual Private Networks
Somesh Jha University of Wisconsin
SECURING NETWORK TRAFFIC WITH IPSEC
Internet and Intranet Fundamentals
CSE 4905 IPsec II.
Network Security: IPsec
IT443 – Network Security Administration Instructor: Bo Sheng
Mutual Attestation of IoT Devices Connect Security World September 2016 Marseille Prof. Andreas Steffen Institute for Internet Technologies and Applications.
UNIT.4 IP Security.
Module 8: Securing Network Traffic by Using IPSec and Certificates
BINF 711 Amr El Mougy Sherif Ismail
Understand Networking Services
draft-fitzgeraldmckay-sacm-endpointcompliance-00
Trusted Network Connect: Open Standards for NAC
Securing Access to Mobile Operator Core Networks using IKEv2
VPN-Implementation Using UBUNTU OS and OpenVPN and Hamachi in client-server environment. By Ruphin Byamungu, Kusinza United States International University-Nairobi.
VPNs and IPSec Review VPN concepts Encryption IPSec Lab.
PANA Implementation in Open Diameter
SECURING WIRELESS LANS WITH CERTIFICATE SERVICES
Network Security (contd.)
Virtual Private Networks (VPN)
Security in the Internet: IPSec, SSL/TLS, PGP, VPN, and Firewalls
Module 8: Securing Network Traffic by Using IPSec and Certificates
Introduction to Network Security
Tero Kivinen, AuthenTec
Tero Kivinen, AuthenTec
B. R. Chandavarkar CSE Dept., NITK Surathkal
Presentation transcript:

Mutual Attestation of IoT Devices and TPM 2 Mutual Attestation of IoT Devices and TPM 2.0 Support TCG Members Meeting June 2016 Vienna Prof. Andreas Steffen Institute for Internet Technologies and Applications HSR University of Applied Sciences Rapperswil andreas.steffen@hsr.ch

Where the heck is Rapperswil? HSR

HSR - Hochschule für Technik Rapperswil University of Applied Sciences with about 1500 students Faculty of Information Technology (300-400 students) Bachelor Course (3 years), Master Course (+1.5 years)

strongSwan – the OpenSource VPN Solution Windows Active Directory Server Linux FreeRadius Server Corporate Network High-Availability strongSwan VPN Gateway Windows 7/8/10 Agile VPN Client strongSwan Linux Client N Rekeying Notification (optional) SAi Suite of cryptographic proposals for the Child SA (ESP and/or AH) Ni Initiator Nonce KEi Initiatior public factor for the Diffie-Hellman Key Exchange (optional PFS) TSi Initiator Traffic Selectors (subnets behind the Initiator) TSr Responder Traffic Selectors (subnets behind the Responder SA1r Selection of a cryptographic proposal for the IKE SA Nr Responder Nonce KEr Responder public factor for the Diffie-Hellman Key Exchange (optional PFS) Internet

Mutual Attestation of IoT Devices and TPM 2 Mutual Attestation of IoT Devices and TPM 2.0 Support TCG Members Meeting June 2016 Vienna Trusted Network Communications (TNC) Current Use Cases: Network Access Control & Endpoint Compliance

Network Access Control TNC Architecture RFC 5792 RFC 5793 RFC 6876 RFC 7171 Endpoint Compliance Lying Endpoint Network Access Control Abbreviations • AR Access Requestor • IF Interface • IMC Integrity Measurement Collector • IMV Integrity Measurement Verifier • M Measurement • PDP Policy Decision Point • PEP Policy Enforcement Point • T Transport • TNC Trusted Network Connect VPN Client VPN Gateway

Layered TNC Protocol Stack TNC Measurement Data [IMV] operating system name is 'Android' from vendor Google [IMV] operating system version is '4.2.1‘ [IMV] device ID is cf5e4cbcc6e6a2db IF-M Measurement Protocol PA-TNC (RFC 5792) [TNC] handling PB-PA message type 'IETF/Operating System' 0x000000/0x00000001 [IMV] IMV 1 "OS" received message for Connection ID 1 from IMC 1 [TNC] processing PA-TNC message with ID 0xec41ce1d [TNC] processing PA-TNC attribute type 'IETF/Product Information' 0x000000/0x00000002 [TNC] processing PA-TNC attribute type 'IETF/String Version' 0x000000/0x00000004 [TNC} processing PA-TNC attribute type 'ITA-HSR/Device ID' 0x00902a/0x00000008 IF-TNCCS TNC Client-Server Protocol PB-TNC (RFC 5793) [TNC] received TNCCS batch (160 bytes) for Connection ID 1 [TNC] PB-TNC state transition from 'Init' to 'Server Working' [TNC] processing PB-TNC CDATA batch [TNC] processing PB-Language-Preference message (31 bytes) [TNC] processing PB-PA message (121 bytes) [TNC] setting language preference to 'en‘ IF-T Transport Protocol PT-EAP (RFC 7171) [NET] received packet: from 152.96.15.29[50871] to 77.56.144.51[4500] (320 bytes) [ENC] parsed IKE_AUTH request 8 [ EAP/RES/TTLS ] [IKE] received tunneled EAP-TTLS AVP [EAP/RES/PT]

TPM-based Attestation 2010 Implemented the TCG TNC IF-TNCCS 2.0 Client/Server and TCG TNC IF-M Measurement protocols. 2011 Implemented the TCG Attestation Protocol Binding to TNC IF-M using TrouSerS stack under Linux [later ported to Windows]. 2012 Implemented TPM 1.2 based attestation using the Linux Integrity Measurement Architecture (IMA). 2015 Implemented the TCG TNC IF-M Segmentation Protocol allowing the transport of huge IF-M attributes over IF-T for EAP Methods. IF-T for TLS transport also profits from large buffer savings. 2016 Implemented TPM 2.0 based Attestation using the Intel TSS2 SAPI under Linux and an Intel PTT firmware TPM. TSS 2.0 requires an update of the Attestation Binding to IF-M !!!

Mutual Attestation of IoT Devices and TPM 2 Mutual Attestation of IoT Devices and TPM 2.0 Support TCG Members Meeting June 2016 Vienna Trusted Network Communications (TNC) New Use Case: Mutual Measurements of Endpoints

PB-TNC / IF-TNCCS 2.0 State Machine PA-TNC IF-TNCCS 2.0 Batch Types • CDATA ClientData • SDATA ServerData • CRETRY ClientRetry • SRETRY ServerRetry • RESULT Result • CLOSE Close Exchange of PB-TNC Client/Server Data Batches containing PA-TNC Messages

Mutual Measurements in Half-Duplex Mode Initiator PB-TNC Batch[PB-TNC Messages] Responder TNC Client  CDATA[PB-MUTUAL, PB-PA] TNC Server  SDATA[PB-MUTUAL, PB-PA] SDATA[] CDATA[PB-PA] RESULT[PB-ASSESSMENT] SDATA[PB-PA] CLOSE[] The initiating TNC client sends CLOSE batch last Works over PT-EAP and PT-TLS

Example: Mutually Trusted Video Phones PA-TNC IF-TNCCS 2.0 Batch Types • CDATA ClientData • SDATA ServerData • CRETRY ClientRetry • SRETRY ServerRetry • RESULT Result • CLOSE Close

Mutual Attestation of IoT Devices DB Trusted Reference DB TLS DB DB Attestation IMV Attestation IMV TNC Server TNC Server PT-EAP PT-EAP TNC Client TNC Client IKEv2 OS IMC Attestation IMC Attestation IMC OS IMC Linux OS PA-TNC IF-TNCCS 2.0 Batch Types • CDATA ClientData • SDATA ServerData • CRETRY ClientRetry • SRETRY ServerRetry • RESULT Result • CLOSE Close TPM TPM Linux OS Linux IMA* IPsec Linux IMA Video Link Video Link IoT Device 1 IoT Device 2 * IMA: Integrity Measurement Architecture

File Version Management using SWID Tags ISO/IEC 19770-2:2015 Software Asset Management Part 2: Software Identification Tag: <SoftwareIdentity xmlns=http://standards.iso.org/iso/19770/-2/2015/schema.xsd name="libssl1.0.0" tagId="Ubuntu_14.04-x86_64-libssl1.0.0-1.0.1f-1ubuntu2.15“ version="1.0.1f-1ubuntu2.15" versionScheme="alphanumeric"> <Entity name="strongSwan Project" regid="strongswan.org“ role="tagCreator"/> <Payload> <File location="/lib/x86_64-linux-gnu" name="libcrypto.so.1.0.0"/> <File location="/lib/x86_64-linux-gnu" name="libssl.so.1.0.0"/> <File location="/usr/share/doc/libssl1.0.0" name="copyright"/> <File location="/usr/share/doc/libssl1.0.0" name="changelog.Debian.gz"/> <File location="/usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines" name="libpadlock.so"/> <File location="/usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines" name="libcswift.so"/> <File location="/usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines" name="lib4758cca.so"/> <File location="/usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines" name="libaep.so"/> <File location="/usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines" name="libubsec.so"/> <File location="/usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines" name="libchil.so"/> <File location="/usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines" name="libgost.so"/> <File location="/usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines" name="libgmp.so"/> <File location="/usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines" name="libcapi.so"/> <File location="/usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines" name="libnuron.so"/> <File location="/usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines" name="libsureware.so"/> <File location="/usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines" name="libatalla.so"/> </Payload> </SoftwareIdentity>

Thank you for your attention! Questions? www.strongswan.org/tnc/