LAS16-300K2: Overview of IoT Zephyr
Speakers: Geoff Thorpe
Date: September 28, 2016
★ Session Description ★
Title: Overview of IoT Zephyr
Bio:
Geoff Thorpe heads up security within the Microcontroller group of NXP, where the intersection of device security and network security gives him a headache commonly known as “IoT”. His early experience with security topics was very software-centric, as a long-standing member of the OpenSSL team and a contributor to related open source projects. After many years veering off into semiconductors and hardware architecture, his software-bias has been domesticated to some extent but not eradicated.
★ Resources ★
Etherpad: pad.linaro.org/p/las16-300k2
Presentations & Videos: http://connect.linaro.org/resource/las16/las16-300k2/
★ Event Details ★
Linaro Connect Las Vegas 2016 – #LAS16
September 26-30, 2016
http://www.linaro.org
http://connect.linaro.org
LAS16-100K1: Welcome Keynote
Speakers: George Grey
Date: September 26, 2016
★ Session Description ★
George Grey, CEO of Linaro will welcome attendees to the conference and give an update on the latest projects taking place at Linaro.
★ Resources ★
Etherpad: pad.linaro.org/p/las16-100k1
Presentations & Videos: http://connect.linaro.org/resource/las16/las16-100k1/
★ Event Details ★
Linaro Connect Las Vegas 2016 – #LAS16
September 26-30, 2016
http://www.linaro.org
http://connect.linaro.org
BKK16-110 A Gentle Introduction to Trusted Execution and OP-TEELinaro
Smart connected devices such as mobile phones, tablets and Digital TVs are required to handle data with strong security and confidentiality requirements. A “Trusted Execution Environment” (TEE) provides an environment for processing data securely, protected from normal platform applications. This talk is intended as an introduction to Trusted Execution, and the open-source Trusted Execution Environment OP-TEE in particular. It introduces the GlobalPlatform TEE Specifications, explains how Trusted Execution is implemented by ARM TrustZone and OP-TEE, and outlines how trusted boot software manages the secure boot of an ARM platform. Finally, it gives some pointers on how to get started with OP-TEE.
Trusted Firmware is a set of foundational software components that implement security services for secure platforms, including a trusted execution environment, secure function invocation, secure device initialization and setup, and trusted boot. Trusted Firmware for A-profile systems (TF-A) is a mature open source project, while Trusted Firmware M (TF-M) builds on TF-A for M-profile devices in a more constrained manner. The Platform Security Architecture (PSA) provides standard interfaces to build secure systems, and Trusted Firmware implements PSA. TF-M development includes aligning with PSA, supporting Arm platforms and IP, and taking third-party contributions through a new open governance model hosted by Linaro
Some problems can only be solved by looking across a complete compute ecosystem. IoT Devices, Mobile Devices, Media Servers Gateways, Cloud Edge Devices.

LAS16-306: Exploring the Open Trusted ProtocolLinaro
LAS16-306: Exploring the Open Trusted Protocol
Speakers: Marc Canel
Date: September 28, 2016
★ Session Description ★
Interconnected systems require trust between devices and service providers. To deal with this problem, several companies (ARM, Solacia, Symantec, Intercede) collaborated on the Open Trust Protocol (OTrP), which combines a secure architecture with trusted code management, using technologies proven in large scale banking and sensitive data applications on mass-market devices such as smartphones and tablets.
★ Resources ★
Etherpad: pad.linaro.org/p/las16-306
Presentations & Videos: http://connect.linaro.org/resource/las16/las16-306/
★ Event Details ★
Linaro Connect Las Vegas 2016 – #LAS16
September 26-30, 2016
http://www.linaro.org
http://connect.linaro.org
Building, deploying and testing an industrial linux platform @ Open source su...SZ Lin
To introduce a robust, secure and reliable platform for the industrial environments is a key challenge. Therefore, running with the industrial-grade Linux distribution to fulfill the requirements mentioned above is imperative. The Linux distribution includes the Linux kernel and user space. Based on this testing design, the distribution will be built, deployed and tested in the device under automatic test by using continuous integration development practice to withstand the harsh industrial environments. In this presentation, SZ Lin will introduce how the industrial-grade Linux distribution is built, deployed and tested without human intervention, and review the test scope in both Linux kernel and user space. In addition, he will also address the design architecture of 24/7 long-term automated testing in all device under test with each release of new update.
LAS16-100K1: Welcome Keynote
Speakers: George Grey
Date: September 26, 2016
★ Session Description ★
George Grey, CEO of Linaro will welcome attendees to the conference and give an update on the latest projects taking place at Linaro.
★ Resources ★
Etherpad: pad.linaro.org/p/las16-100k1
Presentations & Videos: http://connect.linaro.org/resource/las16/las16-100k1/
★ Event Details ★
Linaro Connect Las Vegas 2016 – #LAS16
September 26-30, 2016
http://www.linaro.org
http://connect.linaro.org
BKK16-110 A Gentle Introduction to Trusted Execution and OP-TEELinaro
Smart connected devices such as mobile phones, tablets and Digital TVs are required to handle data with strong security and confidentiality requirements. A “Trusted Execution Environment” (TEE) provides an environment for processing data securely, protected from normal platform applications. This talk is intended as an introduction to Trusted Execution, and the open-source Trusted Execution Environment OP-TEE in particular. It introduces the GlobalPlatform TEE Specifications, explains how Trusted Execution is implemented by ARM TrustZone and OP-TEE, and outlines how trusted boot software manages the secure boot of an ARM platform. Finally, it gives some pointers on how to get started with OP-TEE.
Trusted Firmware is a set of foundational software components that implement security services for secure platforms, including a trusted execution environment, secure function invocation, secure device initialization and setup, and trusted boot. Trusted Firmware for A-profile systems (TF-A) is a mature open source project, while Trusted Firmware M (TF-M) builds on TF-A for M-profile devices in a more constrained manner. The Platform Security Architecture (PSA) provides standard interfaces to build secure systems, and Trusted Firmware implements PSA. TF-M development includes aligning with PSA, supporting Arm platforms and IP, and taking third-party contributions through a new open governance model hosted by Linaro
Some problems can only be solved by looking across a complete compute ecosystem. IoT Devices, Mobile Devices, Media Servers Gateways, Cloud Edge Devices.

LAS16-306: Exploring the Open Trusted ProtocolLinaro
LAS16-306: Exploring the Open Trusted Protocol
Speakers: Marc Canel
Date: September 28, 2016
★ Session Description ★
Interconnected systems require trust between devices and service providers. To deal with this problem, several companies (ARM, Solacia, Symantec, Intercede) collaborated on the Open Trust Protocol (OTrP), which combines a secure architecture with trusted code management, using technologies proven in large scale banking and sensitive data applications on mass-market devices such as smartphones and tablets.
★ Resources ★
Etherpad: pad.linaro.org/p/las16-306
Presentations & Videos: http://connect.linaro.org/resource/las16/las16-306/
★ Event Details ★
Linaro Connect Las Vegas 2016 – #LAS16
September 26-30, 2016
http://www.linaro.org
http://connect.linaro.org
Building, deploying and testing an industrial linux platform @ Open source su...SZ Lin
To introduce a robust, secure and reliable platform for the industrial environments is a key challenge. Therefore, running with the industrial-grade Linux distribution to fulfill the requirements mentioned above is imperative. The Linux distribution includes the Linux kernel and user space. Based on this testing design, the distribution will be built, deployed and tested in the device under automatic test by using continuous integration development practice to withstand the harsh industrial environments. In this presentation, SZ Lin will introduce how the industrial-grade Linux distribution is built, deployed and tested without human intervention, and review the test scope in both Linux kernel and user space. In addition, he will also address the design architecture of 24/7 long-term automated testing in all device under test with each release of new update.
Securing the Internet of Things - Hank ChaversWithTheBest
The document discusses security for IoT devices. It introduces GlobalPlatform, an organization that provides security standards. It then discusses IoT security use cases and how a Trusted Execution Environment (TEE) and trusted applications run within a TEE can help address these issues. The TEE provides an isolated secure area for sensitive operations and data.
"Session ID: BUD17-400
Session Name: Secure Data Path with OPTEE - BUD17-400
Speaker: Mark Gregotski
Track: LHG
★ Session Summary ★
LHG is using the ION-based secure memory allocator integrated with OPTEE as the basis for secure data path processing pipeline. LHG is following the W3C EME protocol and supporting Content Decryption Modules (CDMs) from Widevine and PlayReady.
---------------------------------------------------
★ Resources ★
Event Page: http://connect.linaro.org/resource/bud17/bud17-400/
Presentation: https://www.slideshare.net/linaroorg/bud17400-secure-data-path-with-optee
Video: https://youtu.be/6JdzsWZq4Ls
---------------------------------------------------
★ Event Details ★
Linaro Connect Budapest 2017 (BUD17)
6-10 March 2017
Corinthia Hotel, Budapest,
Erzsébet krt. 43-49,
1073 Hungary
---------------------------------------------------
Keyword: LHG, secure-data, OPTEE
http://www.linaro.org
http://connect.linaro.org
---------------------------------------------------
Follow us on Social Media
https://www.facebook.com/LinaroOrg
https://twitter.com/linaroorg
https://www.youtube.com/user/linaroorg?sub_confirmation=1
https://www.linkedin.com/company/1026961"
MultiZone is an IoT firmware that provides a trusted execution environment (TEE) for securing IoT applications on RISC-V processors. It includes pre-integrated libraries for TCP/IP, TLS, ECC and FreeRTOS to handle basic and advanced IoT requirements. MultiZone provides four separated execution environments called zones that are enforced by hardware to isolate trusted applications from untrusted third party code and libraries. It allows for building secure IoT devices, remote firmware updates, and real-time device monitoring and management without needing proprietary hardware extensions.
Hardware-assisted Isolated Execution Environment to run trusted OS and applic...Kuniyasu Suzaki
This document discusses hardware-assisted isolated execution environments (HIEE) and trusted execution environments (TEE) on RISC-V processors. It describes how TEEs are implemented using privileges worlds on ARM TrustZone and Intel SGX. For RISC-V, it summarizes proposals for TEEs including Sanctum, MultiZone, and using seL4 microkernel to implement OP-TEE. It also briefly discusses TEE implementations on FPGAs, GPUs, virtualization, and the IETF's TEE provisioning protocol.
Using SoC Vendor HALs in the Zephyr Project - SFO17-112Linaro
Session ID: SFO17-112
Session Name: Using SoC Vendor HALs in the Zephyr Project - SFO17-112
Speaker: Maureen Helm
Track: LITE
★ Session Summary ★
The Zephyr OS is a small, scalable RTOS that supports a wide variety of SoCs, many of which have existing HALs provided by the SoC vendors, especially in the ARM Cortex-M world. These HALs provide peripheral register definitions and in many cases, include bare metal peripheral drivers. Rather than reinventing the wheel, the Zephyr Project decided to proactively reuse these vendor HALs whenever possible. This session will cover how and why the Zephyr Project uses SoC vendor HALs, what are the common problems, and how to address them.
---------------------------------------------------
★ Resources ★
Event Page: http://connect.linaro.org/resource/sfo17/sfo17-112/
Presentation:
Video: https://www.youtube.com/watch?v=hHcnw4xu_Mo
---------------------------------------------------
★ Event Details ★
Linaro Connect San Francisco 2017 (SFO17)
25-29 September 2017
Hyatt Regency San Francisco Airport
---------------------------------------------------
Keyword:
'http://www.linaro.org'
'http://connect.linaro.org'
---------------------------------------------------
Follow us on Social Media
https://www.facebook.com/LinaroOrg
https://twitter.com/linaroorg
https://www.youtube.com/user/linaroorg?sub_confirmation=1
https://www.linkedin.com/company/102696
LAS16-400K2: TianoCore – Open Source UEFI Community UpdateLinaro
LAS16-400K2: TianoCore – Open Source UEFI Community Update
Speakers: Brian Richardson
Date: September 29, 2016
★ Session Description ★
Title: TianoCore – Open Source UEFI Community Update
The TianoCore project hosts EDK II, an open source implementation of the Unified Extensible Firmware Interface (UEFI). EDK II has become the defacto UEFI implementation for ARM and Intel platforms, expanding standards based firmware across multiple architectures. This keynote will provide an update on the current status of the TianoCore project, plans for future improvements, and a discussion of why firmware is critical in today’s digital ecosystem.
Bio
Brian Richardson is an Intel technical evangelist who has spent most of his career as a “BIOS guy” working on the firmware that quietly boots billions of computers. Brian has focused on the industry transition to the Unified Extensible Firmware Interface (UEFI), demystifying how firmware works and simplifying firmware development tools. Brian has presented at LinuxCon, UEFI Plugfests, and Intel Developer Forum. He is a blogger for the Intel Software Evangelists project, former writer forlinux.com, and (apropos of nothing) executive producer for DragonConTV.
★ Resources ★
Watch the video: https://www.youtube.com/watch?v=kQ5X8vqdSu0
Etherpad: pad.linaro.org/p/las16-400k2
Presentations & Videos: http://connect.linaro.org/resource/las16/las16-400k2/
★ Event Details ★
Linaro Connect Las Vegas 2016 – #LAS16
September 26-30, 2016
http://www.linaro.org
http://connect.linaro.org
Internet of Tiny Linux (IoTL): Episode IV - SFO17-100Linaro
This document discusses methods for reducing the size of Linux kernels and user space binaries to make them suitable for small IoT applications. It describes techniques like linker garbage collection, link time optimization, and selectively disabling unnecessary kernel configurations. Specific examples that have been merged into the Linux kernel mainline are given, such as removing POSIX timers and PI futexes. The goals of executing code directly from flash memory and reducing static and runtime memory usage are also covered.
OWASP Appsec USA 2014 Talk "Pwning the Pawns with Wihawk" Santhosh Kumar Santhosh Kumar
The document summarizes a presentation given by Santhosh Kumar and Anamika Singh on analyzing router vulnerabilities and the WiHawk router vulnerability scanner. The presentation covered analyzing sample routers to find issues, open source tools for firmware analysis, demonstrating exploits found, and the lack of responses from some vendors. It also described the WiHawk scanner which automates checking routers for common vulnerabilities and issues like default credentials, backdoors, and more.
HKG18-113- Secure Data Path work with i.MX8MLinaro
"Session ID: HKG18-113
Session Name: HKG18-113 - Secure Data Path work with i.MX8M
Speaker: Cyrille Fleury
Track: Digital Home
★ Session Summary ★
NXP presentation on Secure Data Path work with i.MX8M Soc. Demonstrate 4K PlayReady playback with Android 8.1 running on i.MX8M. Focus on security (MS SL3000 and Widevine level 1)
---------------------------------------------------
★ Resources ★
Event Page: http://connect.linaro.org/resource/hkg18/hkg18-113/
Presentation: http://connect.linaro.org.s3.amazonaws.com/hkg18/presentations/hkg18-113.pdf
Video: http://connect.linaro.org.s3.amazonaws.com/hkg18/videos/hkg18-113.mp4
---------------------------------------------------
★ Event Details ★
Linaro Connect Hong Kong 2018 (HKG18)
19-23 March 2018
Regal Airport Hotel Hong Kong
---------------------------------------------------
Keyword: Digital Home
'http://www.linaro.org'
'http://connect.linaro.org'
---------------------------------------------------
Follow us on Social Media
https://www.facebook.com/LinaroOrg
https://www.youtube.com/user/linaroorg?sub_confirmation=1
https://www.linkedin.com/company/1026961"
HKG18-402 - Build secure key management services in OP-TEELinaro
Session ID: HKG18-402
Session Name: HKG18-402 - Build secure key management services in OP-TEE
Speaker: Etienne Carriere
Track: Security
★ Session Summary ★
The session presents an initiative to build secure key management services in the OP-TEE project. Based on OP-TEE services (persistent storage, cryptography, time, etc) one could build a trusted application of store and use secure keys. An open source implementation for generic key services could be of interest. However there are many client APIs defined in the ecosystem which is a matter of concern for standardization of such services. The session will open a discussion on this and presents the current choice of the PKCS#11 Cryptoki. There can be lot of key attributes and cryptographic schemes to be supported. The session will present the current plans (starting from AES flavors) and what is currently missing in the OP-TEE (as certificate support, bootloader support). This session aims at getting feedback from the community on this topic, discuss about expected services and client APIs.
---------------------------------------------------
★ Resources ★
Event Page: http://connect.linaro.org/resource/hkg18/hkg18-402/
Presentation: http://connect.linaro.org.s3.amazonaws.com/hkg18/presentations/hkg18-402.pdf
Video: http://connect.linaro.org.s3.amazonaws.com/hkg18/videos/hkg18-402.mp4
---------------------------------------------------
★ Event Details ★
Linaro Connect Hong Kong 2018 (HKG18)
19-23 March 2018
Regal Airport Hotel Hong Kong
---------------------------------------------------
Keyword: Security
'http://www.linaro.org'
'http://connect.linaro.org'
---------------------------------------------------
Follow us on Social Media
https://www.facebook.com/LinaroOrg
https://www.youtube.com/user/linaroorg?sub_confirmation=1
https://www.linkedin.com/company/1026961
LAS16-300: Mini Conference 2 Cortex-M Software - Device ConfigurationLinaro
LAS16-300: Mini Conference 2 RTOS-Zephyr - Device Configuration
Speakers: Andy Gross
Date: September 28, 2016
★ Session Description ★
SoC Vendors, board vendors, software middle layers, scripting languages, etc all need to have access to system configuration information (pin muxes, what sensors are on a system, what amount of memory, flash, etc, etc). We need a means to convey this in a vendor neutral mechanism but also one that is friendly for Cortex-M/constrained footprint devices. This session will be to discuss the topic, how its done today, what kinda tooling might exist from different vendors, what we could utilize (device tree) and what issues that creates.
★ Resources ★
Etherpad: pad.linaro.org/p/las16-300
Presentations & Videos: http://connect.linaro.org/resource/las16/las16-300/
★ Event Details ★
Linaro Connect Las Vegas 2016 – #LAS16
September 26-30, 2016
http://www.linaro.org
http://connect.linaro.org
CSW2017 Privilege escalation on high-end servers due to implementation gaps i...CanSecWest
This document discusses how abusing CPU hot-add weaknesses could allow escalating privileges in server datacenters. It describes how CPU hot-add works, allowing addition of new CPUs to a running system without shutting down. Two memory regions important for hot-add are identified as assets to protect: 0x38000 holding SMI code, and 0x0e2000 holding SIPI vectors. An attack corrupting 0x38000 to inject malicious SMI code and escalate to SMM privileges is demonstrated. Mitigation using hardware protection of memory regions from DMA is discussed.
XPDDS18: Design Session - SGX deep dive and SGX Virtualization Discussion, Ka...The Linux Foundation
Software Guard Extensions (SGX) is Intel's unique security feature which has been present in Intel's processors since Skylake generation. Existing HW/SW solutions hypervisor does not protect tenants against the cloud provider and thus the supplied operating system and hardware. Intel SGX solves this by using enclave, which is a protected portion of userspace application where the code/data cannot be accessed directly from outside by any software, including privileged ones, such as BIOS and VMM. This discussion is intended for the deep dive introduction to SGX, and the design discussion of adding SGX virtualization to Xen. We will start with SGX deep dive, and then go into SGX virtualization design, from high level design to details, such as EPC management/virtualization, CPUID handling, interaction with VMX, live migration support, etc.
This document describes a protocol test generator that uses nested virtual machines and rollback mechanisms to perform exhaustive fuzz testing of protocol implementations. It proposes using a virtual test protocol to encapsulate test packets and control the target virtual machine. Special packets allow taking snapshots of the target VM state and rolling back to previous snapshots to repeatedly test protocol states with different fuzzed packets. The current prototype implements this approach with KVM and QEMU virtual machines to find bugs in TLS/SSL protocol implementations through fuzz testing of the handshake process.
This document discusses open source licenses. It begins by introducing open source/free software and different types of intellectual property like copyrights and patents. It then explains key open source licenses like the GPL, LGPL, Apache, MIT and their different permissions and conditions. Popular open source licenses used on GitHub are also shown. The document provides answers to common questions about open source licensing and references for further information.
Long-term Maintenance Model of Embedded Industrial Linux DistributionSZ Lin
To introduce a robust, secure and reliable platform for the industrial environments is a key challenge; moreover, the platform needs to survive for a long time (more than 10+ years). There are many good solutions aiming to meet these requirements, such as LTSI (Long Term Support Initiative) and CIP (Civil Infrastructure Platform). However, it still needs a high amount of maintenance and development costs in handling SoC/ hardware board in-house patch, non-upstream driver and keep source code consistent with different SoC and platform afterwards.
In this presentation, SZ Lin will introduce how to operate long-term maintenance model of embedded industrial Linux distribution. In addition, he will also address the building, deploying and testing architecture and workflow for producing a robust, secure and reliable platform.
"Session ID: SFO17-102
Session Name: Deploy STM32 family on Zephyr - SFO17-102
Speaker: Erwan Gouriou
Track: LITE
★ Session Summary ★
Objects:
-Quick intro on STM32 offer
-Strategy used to minimize code and maintenance effort and break silos
-Status on supported drivers
Slides:
-STM32 families and SoCs (highlight number of refs (>900) and need for mutualization)
-SoC naming conventions
-ST boards
-STM32Cube
-Initial deployment in Zephyr
-STM32Cube introduction and introduction in Zephyr
*HAL vs LL
*Information conveyed by CMSIS files
-Driver deployment strategy
*CMSIS (generic defines)
*LL/HAL
-Simplification brought by driver init code and pinmux generated by Device tree
---------------------------------------------------
★ Resources ★
Event Page: http://connect.linaro.org/resource/sfo17/sfo17-102/
Presentation:
Video:
---------------------------------------------------
★ Event Details ★
Linaro Connect San Francisco 2017 (SFO17)
25-29 September 2017
Hyatt Regency San Francisco Airport
---------------------------------------------------
Keyword:
http://www.linaro.org
http://connect.linaro.org
---------------------------------------------------
Follow us on Social Media
https://www.facebook.com/LinaroOrg
https://twitter.com/linaroorg
https://www.youtube.com/user/linaroorg?sub_confirmation=1
https://www.linkedin.com/company/1026961"
The De-RISC initiative aims to develop the first space-amenable RISC-V based computing platform. It involves:
1) Cobham Gaisler developing a fault-tolerant multicore MPSoC based on NOEL-V RISC-V cores.
2) FentISS developing a space-qualified hypervisor called XtratuM for RISC-V.
3) The Barcelona Supercomputing Center developing an extended statistics unit to help manage multicore interference.
4) Thales assessing the platform through benchmarking, executing a satellite software stack, and evaluating a command and data handling use case.
The goal is to have an integrated and validated platform ready
Socionext is developing low power ARM server solutions including the SC2A11 multicore processor and SC2A20 SoC switch. They aim to build scalable small core systems with optimized performance and power efficiency compared to traditional servers. Socionext has integrated their solutions into a prototype low power scalable server and is developing the necessary software including UEFI, Linux, and applications to support various server workloads.
LAS16-203: Platform security architecture for embedded devicesLinaro
LAS16-203: Platform security architecture for embedded devices
Speakers: Mark Hambleton
Date: September 27, 2016
★ Session Description ★
Heads up on what ARM are doing with the new ARMv8-M architecture from a software perspective.
★ Resources ★
Etherpad: pad.linaro.org/p/las16-203
Presentations & Videos: http://connect.linaro.org/resource/las16/las16-203/
★ Event Details ★
Linaro Connect Las Vegas 2016 – #LAS16
September 26-30, 2016
http://www.linaro.org
http://connect.linaro.org
Operating System Support for Run-Time Security with a Trusted Execution Envir...Javier González
Software services have become an integral part of our daily life. Cyber-attacks have thus become a problem of increasing importance not only for the IT industry, but for society at large. A way to contain cyber-attacks is to guarantee the integrity of IT systems at run-time. Put differently, it is safe to assume that any complex software is compromised. The problem is then to monitor and contain it when it executes in order to protect sensitive data and other sensitive assets. To really have an impact, any solution to this problem should be integrated in commodity operating systems.
In this thesis we introduce run-time security primitives that enable a number of trusted services in the context of Linux. These primitives mediate any action involving sensitive data or sensitive assets in order to guarantee their integrity and confidentiality. We introduce a general mechanism to protect sensitive assets at run-time that we denote split-enforcement, and provide an implementation for ARM-powered devices using ARM TrustZone security extensions. We design, build, and evaluate a prototype Trusted Cell that provides trusted services. We also present the first generic TrustZone driver in the Linux operating system. We are in the process of making this driver part of the mainline Linux kernel.
Securing the Internet of Things - Hank ChaversWithTheBest
The document discusses security for IoT devices. It introduces GlobalPlatform, an organization that provides security standards. It then discusses IoT security use cases and how a Trusted Execution Environment (TEE) and trusted applications run within a TEE can help address these issues. The TEE provides an isolated secure area for sensitive operations and data.
"Session ID: BUD17-400
Session Name: Secure Data Path with OPTEE - BUD17-400
Speaker: Mark Gregotski
Track: LHG
★ Session Summary ★
LHG is using the ION-based secure memory allocator integrated with OPTEE as the basis for secure data path processing pipeline. LHG is following the W3C EME protocol and supporting Content Decryption Modules (CDMs) from Widevine and PlayReady.
---------------------------------------------------
★ Resources ★
Event Page: http://connect.linaro.org/resource/bud17/bud17-400/
Presentation: https://www.slideshare.net/linaroorg/bud17400-secure-data-path-with-optee
Video: https://youtu.be/6JdzsWZq4Ls
---------------------------------------------------
★ Event Details ★
Linaro Connect Budapest 2017 (BUD17)
6-10 March 2017
Corinthia Hotel, Budapest,
Erzsébet krt. 43-49,
1073 Hungary
---------------------------------------------------
Keyword: LHG, secure-data, OPTEE
http://www.linaro.org
http://connect.linaro.org
---------------------------------------------------
Follow us on Social Media
https://www.facebook.com/LinaroOrg
https://twitter.com/linaroorg
https://www.youtube.com/user/linaroorg?sub_confirmation=1
https://www.linkedin.com/company/1026961"
MultiZone is an IoT firmware that provides a trusted execution environment (TEE) for securing IoT applications on RISC-V processors. It includes pre-integrated libraries for TCP/IP, TLS, ECC and FreeRTOS to handle basic and advanced IoT requirements. MultiZone provides four separated execution environments called zones that are enforced by hardware to isolate trusted applications from untrusted third party code and libraries. It allows for building secure IoT devices, remote firmware updates, and real-time device monitoring and management without needing proprietary hardware extensions.
Hardware-assisted Isolated Execution Environment to run trusted OS and applic...Kuniyasu Suzaki
This document discusses hardware-assisted isolated execution environments (HIEE) and trusted execution environments (TEE) on RISC-V processors. It describes how TEEs are implemented using privileges worlds on ARM TrustZone and Intel SGX. For RISC-V, it summarizes proposals for TEEs including Sanctum, MultiZone, and using seL4 microkernel to implement OP-TEE. It also briefly discusses TEE implementations on FPGAs, GPUs, virtualization, and the IETF's TEE provisioning protocol.
Using SoC Vendor HALs in the Zephyr Project - SFO17-112Linaro
Session ID: SFO17-112
Session Name: Using SoC Vendor HALs in the Zephyr Project - SFO17-112
Speaker: Maureen Helm
Track: LITE
★ Session Summary ★
The Zephyr OS is a small, scalable RTOS that supports a wide variety of SoCs, many of which have existing HALs provided by the SoC vendors, especially in the ARM Cortex-M world. These HALs provide peripheral register definitions and in many cases, include bare metal peripheral drivers. Rather than reinventing the wheel, the Zephyr Project decided to proactively reuse these vendor HALs whenever possible. This session will cover how and why the Zephyr Project uses SoC vendor HALs, what are the common problems, and how to address them.
---------------------------------------------------
★ Resources ★
Event Page: http://connect.linaro.org/resource/sfo17/sfo17-112/
Presentation:
Video: https://www.youtube.com/watch?v=hHcnw4xu_Mo
---------------------------------------------------
★ Event Details ★
Linaro Connect San Francisco 2017 (SFO17)
25-29 September 2017
Hyatt Regency San Francisco Airport
---------------------------------------------------
Keyword:
'http://www.linaro.org'
'http://connect.linaro.org'
---------------------------------------------------
Follow us on Social Media
https://www.facebook.com/LinaroOrg
https://twitter.com/linaroorg
https://www.youtube.com/user/linaroorg?sub_confirmation=1
https://www.linkedin.com/company/102696
LAS16-400K2: TianoCore – Open Source UEFI Community UpdateLinaro
LAS16-400K2: TianoCore – Open Source UEFI Community Update
Speakers: Brian Richardson
Date: September 29, 2016
★ Session Description ★
Title: TianoCore – Open Source UEFI Community Update
The TianoCore project hosts EDK II, an open source implementation of the Unified Extensible Firmware Interface (UEFI). EDK II has become the defacto UEFI implementation for ARM and Intel platforms, expanding standards based firmware across multiple architectures. This keynote will provide an update on the current status of the TianoCore project, plans for future improvements, and a discussion of why firmware is critical in today’s digital ecosystem.
Bio
Brian Richardson is an Intel technical evangelist who has spent most of his career as a “BIOS guy” working on the firmware that quietly boots billions of computers. Brian has focused on the industry transition to the Unified Extensible Firmware Interface (UEFI), demystifying how firmware works and simplifying firmware development tools. Brian has presented at LinuxCon, UEFI Plugfests, and Intel Developer Forum. He is a blogger for the Intel Software Evangelists project, former writer forlinux.com, and (apropos of nothing) executive producer for DragonConTV.
★ Resources ★
Watch the video: https://www.youtube.com/watch?v=kQ5X8vqdSu0
Etherpad: pad.linaro.org/p/las16-400k2
Presentations & Videos: http://connect.linaro.org/resource/las16/las16-400k2/
★ Event Details ★
Linaro Connect Las Vegas 2016 – #LAS16
September 26-30, 2016
http://www.linaro.org
http://connect.linaro.org
Internet of Tiny Linux (IoTL): Episode IV - SFO17-100Linaro
This document discusses methods for reducing the size of Linux kernels and user space binaries to make them suitable for small IoT applications. It describes techniques like linker garbage collection, link time optimization, and selectively disabling unnecessary kernel configurations. Specific examples that have been merged into the Linux kernel mainline are given, such as removing POSIX timers and PI futexes. The goals of executing code directly from flash memory and reducing static and runtime memory usage are also covered.
OWASP Appsec USA 2014 Talk "Pwning the Pawns with Wihawk" Santhosh Kumar Santhosh Kumar
The document summarizes a presentation given by Santhosh Kumar and Anamika Singh on analyzing router vulnerabilities and the WiHawk router vulnerability scanner. The presentation covered analyzing sample routers to find issues, open source tools for firmware analysis, demonstrating exploits found, and the lack of responses from some vendors. It also described the WiHawk scanner which automates checking routers for common vulnerabilities and issues like default credentials, backdoors, and more.
HKG18-113- Secure Data Path work with i.MX8MLinaro
"Session ID: HKG18-113
Session Name: HKG18-113 - Secure Data Path work with i.MX8M
Speaker: Cyrille Fleury
Track: Digital Home
★ Session Summary ★
NXP presentation on Secure Data Path work with i.MX8M Soc. Demonstrate 4K PlayReady playback with Android 8.1 running on i.MX8M. Focus on security (MS SL3000 and Widevine level 1)
---------------------------------------------------
★ Resources ★
Event Page: http://connect.linaro.org/resource/hkg18/hkg18-113/
Presentation: http://connect.linaro.org.s3.amazonaws.com/hkg18/presentations/hkg18-113.pdf
Video: http://connect.linaro.org.s3.amazonaws.com/hkg18/videos/hkg18-113.mp4
---------------------------------------------------
★ Event Details ★
Linaro Connect Hong Kong 2018 (HKG18)
19-23 March 2018
Regal Airport Hotel Hong Kong
---------------------------------------------------
Keyword: Digital Home
'http://www.linaro.org'
'http://connect.linaro.org'
---------------------------------------------------
Follow us on Social Media
https://www.facebook.com/LinaroOrg
https://www.youtube.com/user/linaroorg?sub_confirmation=1
https://www.linkedin.com/company/1026961"
HKG18-402 - Build secure key management services in OP-TEELinaro
Session ID: HKG18-402
Session Name: HKG18-402 - Build secure key management services in OP-TEE
Speaker: Etienne Carriere
Track: Security
★ Session Summary ★
The session presents an initiative to build secure key management services in the OP-TEE project. Based on OP-TEE services (persistent storage, cryptography, time, etc) one could build a trusted application of store and use secure keys. An open source implementation for generic key services could be of interest. However there are many client APIs defined in the ecosystem which is a matter of concern for standardization of such services. The session will open a discussion on this and presents the current choice of the PKCS#11 Cryptoki. There can be lot of key attributes and cryptographic schemes to be supported. The session will present the current plans (starting from AES flavors) and what is currently missing in the OP-TEE (as certificate support, bootloader support). This session aims at getting feedback from the community on this topic, discuss about expected services and client APIs.
---------------------------------------------------
★ Resources ★
Event Page: http://connect.linaro.org/resource/hkg18/hkg18-402/
Presentation: http://connect.linaro.org.s3.amazonaws.com/hkg18/presentations/hkg18-402.pdf
Video: http://connect.linaro.org.s3.amazonaws.com/hkg18/videos/hkg18-402.mp4
---------------------------------------------------
★ Event Details ★
Linaro Connect Hong Kong 2018 (HKG18)
19-23 March 2018
Regal Airport Hotel Hong Kong
---------------------------------------------------
Keyword: Security
'http://www.linaro.org'
'http://connect.linaro.org'
---------------------------------------------------
Follow us on Social Media
https://www.facebook.com/LinaroOrg
https://www.youtube.com/user/linaroorg?sub_confirmation=1
https://www.linkedin.com/company/1026961
LAS16-300: Mini Conference 2 Cortex-M Software - Device ConfigurationLinaro
LAS16-300: Mini Conference 2 RTOS-Zephyr - Device Configuration
Speakers: Andy Gross
Date: September 28, 2016
★ Session Description ★
SoC Vendors, board vendors, software middle layers, scripting languages, etc all need to have access to system configuration information (pin muxes, what sensors are on a system, what amount of memory, flash, etc, etc). We need a means to convey this in a vendor neutral mechanism but also one that is friendly for Cortex-M/constrained footprint devices. This session will be to discuss the topic, how its done today, what kinda tooling might exist from different vendors, what we could utilize (device tree) and what issues that creates.
★ Resources ★
Etherpad: pad.linaro.org/p/las16-300
Presentations & Videos: http://connect.linaro.org/resource/las16/las16-300/
★ Event Details ★
Linaro Connect Las Vegas 2016 – #LAS16
September 26-30, 2016
http://www.linaro.org
http://connect.linaro.org
CSW2017 Privilege escalation on high-end servers due to implementation gaps i...CanSecWest
This document discusses how abusing CPU hot-add weaknesses could allow escalating privileges in server datacenters. It describes how CPU hot-add works, allowing addition of new CPUs to a running system without shutting down. Two memory regions important for hot-add are identified as assets to protect: 0x38000 holding SMI code, and 0x0e2000 holding SIPI vectors. An attack corrupting 0x38000 to inject malicious SMI code and escalate to SMM privileges is demonstrated. Mitigation using hardware protection of memory regions from DMA is discussed.
XPDDS18: Design Session - SGX deep dive and SGX Virtualization Discussion, Ka...The Linux Foundation
Software Guard Extensions (SGX) is Intel's unique security feature which has been present in Intel's processors since Skylake generation. Existing HW/SW solutions hypervisor does not protect tenants against the cloud provider and thus the supplied operating system and hardware. Intel SGX solves this by using enclave, which is a protected portion of userspace application where the code/data cannot be accessed directly from outside by any software, including privileged ones, such as BIOS and VMM. This discussion is intended for the deep dive introduction to SGX, and the design discussion of adding SGX virtualization to Xen. We will start with SGX deep dive, and then go into SGX virtualization design, from high level design to details, such as EPC management/virtualization, CPUID handling, interaction with VMX, live migration support, etc.
This document describes a protocol test generator that uses nested virtual machines and rollback mechanisms to perform exhaustive fuzz testing of protocol implementations. It proposes using a virtual test protocol to encapsulate test packets and control the target virtual machine. Special packets allow taking snapshots of the target VM state and rolling back to previous snapshots to repeatedly test protocol states with different fuzzed packets. The current prototype implements this approach with KVM and QEMU virtual machines to find bugs in TLS/SSL protocol implementations through fuzz testing of the handshake process.
This document discusses open source licenses. It begins by introducing open source/free software and different types of intellectual property like copyrights and patents. It then explains key open source licenses like the GPL, LGPL, Apache, MIT and their different permissions and conditions. Popular open source licenses used on GitHub are also shown. The document provides answers to common questions about open source licensing and references for further information.
Long-term Maintenance Model of Embedded Industrial Linux DistributionSZ Lin
To introduce a robust, secure and reliable platform for the industrial environments is a key challenge; moreover, the platform needs to survive for a long time (more than 10+ years). There are many good solutions aiming to meet these requirements, such as LTSI (Long Term Support Initiative) and CIP (Civil Infrastructure Platform). However, it still needs a high amount of maintenance and development costs in handling SoC/ hardware board in-house patch, non-upstream driver and keep source code consistent with different SoC and platform afterwards.
In this presentation, SZ Lin will introduce how to operate long-term maintenance model of embedded industrial Linux distribution. In addition, he will also address the building, deploying and testing architecture and workflow for producing a robust, secure and reliable platform.
"Session ID: SFO17-102
Session Name: Deploy STM32 family on Zephyr - SFO17-102
Speaker: Erwan Gouriou
Track: LITE
★ Session Summary ★
Objects:
-Quick intro on STM32 offer
-Strategy used to minimize code and maintenance effort and break silos
-Status on supported drivers
Slides:
-STM32 families and SoCs (highlight number of refs (>900) and need for mutualization)
-SoC naming conventions
-ST boards
-STM32Cube
-Initial deployment in Zephyr
-STM32Cube introduction and introduction in Zephyr
*HAL vs LL
*Information conveyed by CMSIS files
-Driver deployment strategy
*CMSIS (generic defines)
*LL/HAL
-Simplification brought by driver init code and pinmux generated by Device tree
---------------------------------------------------
★ Resources ★
Event Page: http://connect.linaro.org/resource/sfo17/sfo17-102/
Presentation:
Video:
---------------------------------------------------
★ Event Details ★
Linaro Connect San Francisco 2017 (SFO17)
25-29 September 2017
Hyatt Regency San Francisco Airport
---------------------------------------------------
Keyword:
http://www.linaro.org
http://connect.linaro.org
---------------------------------------------------
Follow us on Social Media
https://www.facebook.com/LinaroOrg
https://twitter.com/linaroorg
https://www.youtube.com/user/linaroorg?sub_confirmation=1
https://www.linkedin.com/company/1026961"
The De-RISC initiative aims to develop the first space-amenable RISC-V based computing platform. It involves:
1) Cobham Gaisler developing a fault-tolerant multicore MPSoC based on NOEL-V RISC-V cores.
2) FentISS developing a space-qualified hypervisor called XtratuM for RISC-V.
3) The Barcelona Supercomputing Center developing an extended statistics unit to help manage multicore interference.
4) Thales assessing the platform through benchmarking, executing a satellite software stack, and evaluating a command and data handling use case.
The goal is to have an integrated and validated platform ready
Socionext is developing low power ARM server solutions including the SC2A11 multicore processor and SC2A20 SoC switch. They aim to build scalable small core systems with optimized performance and power efficiency compared to traditional servers. Socionext has integrated their solutions into a prototype low power scalable server and is developing the necessary software including UEFI, Linux, and applications to support various server workloads.
LAS16-203: Platform security architecture for embedded devicesLinaro
LAS16-203: Platform security architecture for embedded devices
Speakers: Mark Hambleton
Date: September 27, 2016
★ Session Description ★
Heads up on what ARM are doing with the new ARMv8-M architecture from a software perspective.
★ Resources ★
Etherpad: pad.linaro.org/p/las16-203
Presentations & Videos: http://connect.linaro.org/resource/las16/las16-203/
★ Event Details ★
Linaro Connect Las Vegas 2016 – #LAS16
September 26-30, 2016
http://www.linaro.org
http://connect.linaro.org
Operating System Support for Run-Time Security with a Trusted Execution Envir...Javier González
Software services have become an integral part of our daily life. Cyber-attacks have thus become a problem of increasing importance not only for the IT industry, but for society at large. A way to contain cyber-attacks is to guarantee the integrity of IT systems at run-time. Put differently, it is safe to assume that any complex software is compromised. The problem is then to monitor and contain it when it executes in order to protect sensitive data and other sensitive assets. To really have an impact, any solution to this problem should be integrated in commodity operating systems.
In this thesis we introduce run-time security primitives that enable a number of trusted services in the context of Linux. These primitives mediate any action involving sensitive data or sensitive assets in order to guarantee their integrity and confidentiality. We introduce a general mechanism to protect sensitive assets at run-time that we denote split-enforcement, and provide an implementation for ARM-powered devices using ARM TrustZone security extensions. We design, build, and evaluate a prototype Trusted Cell that provides trusted services. We also present the first generic TrustZone driver in the Linux operating system. We are in the process of making this driver part of the mainline Linux kernel.
I. The document discusses what the Internet of Things (IOT) is, including definitions and examples of connected devices.
II. It outlines some of the main security challenges with IOT, including that default configurations are not optimized for security and users prioritize ease-of-use over security.
III. Examples of IOT applications that are discussed include fleet tracking, home automation, connected cars, healthcare, agriculture, industrial settings, and more.
The document discusses security considerations for higher education regarding the Internet of Things (IoT). It defines IoT as physical objects embedded with electronics, software and sensors that can collect and exchange data. It notes that IoT includes many devices on college campuses and its usage is growing rapidly. However, IoT also poses security risks like vulnerabilities in unpatched devices, lack of access controls, and difficulty in device management at scale. The document recommends accommodating IoT with existing security practices and planning for its growth. It also stresses strengthening partnerships to help secure IoT technologies.
Practical real-time operating system security for the massesMilosch Meriac
Although real-time operating systems are ubiquitous in the industry, OS-level security features are silently absent in most microcontroller systems. As a result, securing these systems against active attackers becomes impractical due to the missing foundations.
We believe security does not need to cost an ARM and a leg in memory resources or device performance. Operating systems for MMU-less low-end microcontrollers should be on par with established security models. High end embedded systems security does not need to be exclusive to Cortex-A/x86 Linux systems.
uVisor is available under Apache License on Github : https://github.com/ARMmbed/uvisor
We will show how spatial isolation of process memories using the ARM v7M Memory Protection Unit (MPU) works - and how it effects interprocess-communication, memory management, thread synchronisation and internal protection of key-material.
We will then introduce temporal isolation for guaranteed operation and device safety even under local attack. To make our point we integrated an advanced security foundation into the vendor-independent RTOS abstraction layer CMSIS-RTOS. Our example implementation - the ARMmbed uVisor for CMSIS-RTOS - is available under the Apache License.
LAS16-307: Benchmarking Schedutil in AndroidLinaro
This document summarizes benchmarking results that compare the performance and power efficiency of Android's schedutil CPU scheduler against the existing ondemand and interactive schedulers. Tests were conducted on a Hikey development board using various workloads before and after applying the Energy Aware Scheduling patches. While schedutil showed competitive performance in many tests, some regressions were observed in user experience metrics like recent app switching and gallery scrolling, as well as higher energy usage when combined with the EAS patches, indicating areas for further optimization.
BKK16-200 Designing Security into low cost IO T SystemsLinaro
This document discusses security considerations for Internet of Things (IoT) systems. It outlines various security risks for IoT devices like weak cryptography, default passwords, and lack of device renewability. It then describes how security can be built into IoT systems at different levels, including device hardware with features like ARM TrustZone, software like mbed OS and mbedTLS, and cloud management platforms. The document advocates for an end-to-end secure IoT framework provided through collaboration between ARM and Linaro.
Resilient IoT Security: The end of flat security modelsMilosch Meriac
Compartmentalizing code and data on low-end MMU-less microcontrollers using the ARM memory protection unit as available on present ARM Cortex-M3 and ARM Cortex-M4 devices.
More information and source code is available at https://github.com/ARMmbed/uvisor . This slideset was presented in November at ARM TechCon 2015.
Track 5 session 2 - st dev con 2016 - security iot best practicesST_World
This document summarizes a presentation on IoT security good practices. It discusses various types of invasive and non-invasive attacks on IoT devices, as well as solutions to improve security such as adding a secure element, using an MCU's security features, and risk management practices. Cryptography methods that can be used for authentication, encryption and integrity are explained. The document also covers topics like secure boot, secure storage, secure communications, and the importance of security over the entire product lifecycle. Recommendations are made to design fortified products, understand risks, use security features and tools, and work with trusted partners.
Track 5 session 1 - st dev con 2016 - need for security for iotST_World
- The document discusses the need for security in IoT devices as the number of connected devices grows exponentially to over 30 billion by 2020.
- It outlines the various types of connected devices and assets that need protection including personal information, products, infrastructure and more.
- The main threats to IoT systems are discussed as access to services and networks, device access, data theft and counterfeiting. Specific attacks like hacking exposed data and exploiting vulnerabilities are also covered.
- The presentation recommends using cryptography, authentication, secure boot processes and other countermeasures to protect assets by mitigating vulnerabilities and reducing threats and risk. It emphasizes the importance of a layered security approach and managing risk for different asset values.
The document discusses several IoT security and privacy considerations, including using privacy by design principles to embed privacy into systems from the start, establishing accountability standards and open technology standards to build trust, and addressing common problems like lack of developer security experience, insecure communication protocols, and ensuring secure firmware updates throughout the lifecycle of IoT devices.
Ryan Wilson - ryanwilson.com - IoT SecurityRyan Wilson
This document provides a summary of an IoT security presentation. It discusses what IoT devices are, why they pose security risks, and how others have been affected by IoT compromises. The presentation then outlines a basic IoT security checklist and covers common attack vectors like weak passwords, lack of encryption and patching, and physical security issues. It emphasizes the importance of inventory, segmentation, strong unique passwords, logging, and engagement with device vendors on security responsibilities and practices.
LAS16-402: ARM Trusted Firmware – from Enterprise to EmbeddedLinaro
LAS16-402: ARM Trusted Firmware – from Enterprise to Embedded
Speakers:
Date: September 29, 2016
★ Session Description ★
ARM Trusted Firmware has established itself as a key part of the ARMv8-A software stack. Broadening its applicability across all segments, from embedded to enterprise, is challenging. This session discusses the latest developments, including extension into the 32-bit space.
★ Resources ★
Etherpad: pad.linaro.org/p/las16-402
Presentations & Videos: http://connect.linaro.org/resource/las16/las16-402/
★ Event Details ★
Linaro Connect Las Vegas 2016 – #LAS16
September 26-30, 2016
http://www.linaro.org
http://connect.linaro.org
LAS16-305: Smart City Big Data Visualization on 96BoardsLinaro
LAS16-305: Smart City Big Data Visualization on 96Boards
Speakers: Naresh Bhat, Ganesh Raju
Date: September 28, 2016
★ Session Description ★
Cities are getting identified as smart cities based on what and how data are used to do predictive analytics. Smart City as a phrase can have a wide spectrum of meaning. But there are two key things (Data and Analytics) that ‘smart’ refers to in smart city. With IoT gaining so much market attention, brings in the power to drive the implementation. Data collection, Storage and Analytics provide so much potential. This talk will go over a sample use case scenario utilizing ODPi based Hadoop eco system and H20 visualizations for analytics.
★ Resources ★
Etherpad: pad.linaro.org/p/las16-305
Presentations & Videos: http://connect.linaro.org/resource/las16/las16-305/
★ Event Details ★
Linaro Connect Las Vegas 2016 – #LAS16
September 26-30, 2016
http://www.linaro.org
http://connect.linaro.org
AWS IoT is a managed cloud platform that lets connected devices easily and securely interact with cloud applications and other devices. This webinar will introduce the best practices for IoT Security in the cloud and the access control mechanisms used by AWS IoT. These mechanisms can be used to not only securely build and provision devices, as well as integrate devices with other AWS services to create secure solutions.
Learning Objectives:
• Common IoT Thing Management Issues
• Learn about AWS IoT Security and Access Control Mechanisms
• Build Secure interactions with the AWS Cloud
Who Should Attend:
• Technical Decision Makers, Developers, Makers
AWS re:Invent 2016: IoT Security: The New Frontiers (IOT302)Amazon Web Services
Only year ago we launched AWS IoT, and at re:Invent we showed how AWS IoT makes it easy to secure millions of connected devices. However, we have learned from our customers that a number of unique security challenges for the Internet of Things (IoT) exist.
The Future of Embedded and IoT Security: Kaspersky Operating SystemKaspersky Lab
KasperskyOS – Secure Operating System for embedded connected systems with specific requirements for cyber security. KasperskyOS aims to protect software and data systems from the consequences of the intrusion of malicious code, viruses and hacker attacks. These can provoke harmful behavior in any part of the system, potentially resulting in loss or leakage of sensitive data, reduced performance and denial of service. In addition it reduces the risk of harm caused by program bugs, unintentional mistakes or premeditated abuse.
Understanding what is IoT security
What is the scope of IoT security
Uses of IoT and where do we see it in our daily life
Possible attack surface and likelihood of IoT-related attacks
IoT specific security assessment (understanding approach, IoT protocols, how it is a combination of different type assessments)
The myths of IoT security and the way it has progressed in past few years and how far fetched it can be.
Available Resources and Tools
This document discusses security issues with Internet of Things (IoT) devices and proposes solutions. It summarizes the 2016 Mirai botnet attack that took down major websites. Default passwords allow the easy compromise of hundreds of thousands of IoT devices. Proposed solutions include network segmentation of IoT devices, internal firewalls, adopting a zero trust model, and consumers pressuring manufacturers to build more secure products. An IoT nutrition label is suggested to help consumers compare security. Overall the document analyzes current IoT vulnerabilities and strategies to address them.
Dimitrios Stergiou, CISO @ NetEnt addressed a number of traditional approaches to Application Security and discussed their shortcomings at Netlight Edge X breakfast seminar. Edge X breakfast seminars at Netlight are recurring events and talks, held by external speakers as well as employees of Netlight, within topics such as trends, challenges and opportunities within IT and management. He also discussed how the Agile methodology can be combined with an Application Security approach that has been proven to offer the most benefits. He also discussed how the DevOps culture can improve security and some do’s and don’ts when deciding to go down the DevOps path.
Presentation during the Inaugural IEEE Smart Grid Cybersecurity Workshop (http://sites.ieee.org/ucw/). The talk was in Session 1: Overview of the Security Situation/Risk Managment. The presentation identifies 5 hurdles that need to be addressed before we can secure the grid. Other presentations from the event are available for download at the IEEE Smart Grid Resource Center http://resourcecenter.smartgrid.ieee.org/category/conferences/-/society-featured-articles/subcategory/913483
Fundamental Best Practices in Secure IoT Product DevelopmentMark Szewczul, CISSP
The document provides guidance on best practices for secure IoT product development. It discusses the top 5 security considerations which include implementing secure firmware updates, authentication and encryption on product interfaces, independent security assessments, securing companion mobile apps/gateways, and implementing a secure root of trust. It also highlights lessons learned from privacy and security issues with IoT products like baby monitors, fitness trackers, medical devices, drones, critical infrastructure systems, and autonomous vehicles. Recommendations provided include adopting a security-by-design approach, threat modeling products, implementing secure development processes, and incorporating privacy principles.
Domain 3: Security Engineering
Virtualization and Distributed Computing
System Vulnerabilities, Threats and Countermeasures
Cornerstone Cryptographic Concepts
History of Cryptography
Types of Cryptography
Cryptographic Attacks
Implementing Cryptography
The Internet of Things is the idea that everything around us from cars to ovens can be connected. If everything around us is linked and collecting information, these networks must be able to provide security and privacy to the end-user particularly in low-power lossy networks.
Jakub Bartoszek (Samsung Electronics) - Hardware Security in Connected WorldCodiax
The document discusses hardware security in the connected world. It notes that with 25+ billion endpoints expected by 2020 and the rise of 5G, IoT, and AI, security is more important than ever as devices have increased attack surfaces. It advocates for a comprehensive security strategy including validated hardware and firmware, secure networks, and security management infrastructure. The importance of hardware-based security is discussed, noting that truly secure computing requires addressing security at the hardware, firmware/OS, and application layers. Samsung's Knox platform is highlighted as an example of building and maintaining trust from manufacturing through runtime with features like hardware root keys, verified boot, encryption, and real-time kernel protection.
Though the potential of the IoT is vast, adoption can easily be curtailed by security worries. No company wants their products to be a victim of a hack, yet many do not appear to consider security as a primary driver of design decisions. This presentation will look at IoT security and describe what product designers – regardless of platform – need to be aware of if they want to build a secure and successful device.
IoT security encompasses requirements that are new for many product designers – such as provisioning, authentication, OTA upgrades and link encryption – and weaknesses in any one could potentially be used to compromise the security of the end product. From physical attacks to analysis of communications channels, there are many possible attack vectors that need to be considered.
From hacked routers to refrigerators sending spam email, there have been a lot of scary news stories about Internet of Things (IoT) security, or lack of it. According to the 2014 Hewlett-Packard Internet of Things Research Study, 70% of Internet connected devices they surveyed didn’t even use encrypted network connections. The US Federal Trade Commission (FTC) recently weighed in on the issue too, releasing a report that outlines potential IoT security risks, ranging from unauthorized access and misuse of personal information, to facilitation of attacks on other systems and risks to personal safety.
This document provides an introduction to Internet of Things (IoT) and firmware reversing. It defines IoT as network-connected physical devices that can collect and exchange data. Examples of IoT devices include routers, medical devices, vehicles and smart home appliances. The document discusses common IoT protocols, security risks of IoT devices, and demonstrates extracting and analyzing firmware from a D-Link router using the Binwalk tool. It concludes by outlining topics for further learning like firmware extraction methods, IDA Pro for reversing, IoT components, protocols and the OWASP IoT security risks.
This presentation by Christopher Grayson covers some lessons learned as a security professional that has made his way into software engineering full time.
- The document describes the Zephyr real-time operating system which is open source, has a vibrant community, and is built with safety and security in mind. It supports multiple architectures and hardware boards and has vendor-neutral governance.
- Key features include being highly configurable, modular, and product development ready using long-term supported releases that include security updates. It provides a range of OS services and supports over 100 sensors out of the box.
- The project focuses on safety and has established committees to improve security practices and work towards safety certification for applications requiring functional safety standards like IEC 61508.
Application security meetup k8_s security with zero trust_29072021lior mazor
The "K8S security with Zero Trust" Meetup is about K8s posture Management and runtime protection, ways to secure your software supply chain, Managing Attack Surface reduction, and How to secure K8s with Zero-Trust.
This document summarizes a presentation on secure software development given by Rod Chapman. It discusses how safety-critical systems have historically used formal methods like correctness-by-construction (CbyC) to build reliable systems. However, secure systems operate in a malicious environment and must assume arbitrary attacks. While CbyC offers confidence by verifying properties, it is not a silver bullet and still requires solid security engineering. There are also concerns that efforts focus too much on legacy code instead of prevention and that security requirements are an infinite set that cannot be fully enumerated. The future may involve combining formal verification of critical components with other techniques for less critical parts and architecting to isolate systems of differing security needs.
IoT Security: Debunking the "We Aren't THAT Connected" MythSecurity Innovation
In a world where convenience is key, consumers are adopting every new connected device that hits the shelves - and doing so with the assumption that due diligence security has been considered. But recent IoT attacks suggest otherwise.
As organizations migrate from a primarily offline to online business model, they are failing to consider IoT’s unique threats which traditional solutions are unable to secure. As a result, steps must be taken to ensure that the device, connections and infrastructure are hardened, especially software which runs IoT devices and is the source of ~90% of attacks.
This webinar is ideal for risk, technology, and security professionals that want to understand why a hacker would want to attack their “harmless” IoT device and what the stealth risk to their organization and consumers is.
Topics covered include:
- IoT security – why it’s so different….and tough
- The IoT ecosystem and attack surface
- Managing liability - IoT risks to consumers and vendors
- Auditing IoT software development
We are all aware of the current risks when developing a connected product, especially with vehicles since much is at stake both from an information and safety perspective. In this workshop, we will learn how to build Security requirements, architect, design, test and produce Safety and Security critical components using a methodology that works in harmony both with Engineering and Security
An introduction to SOC (Security Operation Center)Ahmad Haghighi
The document discusses building a security operations center (SOC). It defines a SOC as a centralized unit that deals with security issues on an organizational and technical level. It monitors, assesses, and defends enterprise information systems. The document discusses whether to build an internal SOC or outsource it. It also covers SOC technologies, personnel requirements, and the five generations of SOCs. It provides resources for learning more about designing and maturing a SOC.
Proactive Approach to OT incident response - HOUSECCON 2023Chris Sistrunk
This talk discusses practical approaches to OT incident response, that will leverage the people, processes, tools, and relationships you most likely already have.
Lessons learned from hundreds of cyber espionage breaches by TT and Ashley - ...CODE BLUE
Cyber espionage attacks have been aware of for around 10 years. Security vendors keep inventing new technology to defend against attack. Many solutions look fancy, however breaches keep happening. People spent a lot of budget to improve their fences, but the effectiveness of these security products remains doubtful. In Taiwan, we have more than 10 years history with cyber espionage attacks. Government, enterprises, and security vendors were fighting hard with threat actors, but new victims still got compromised day by day.
In recent years, a lot of Japanese government agencies, defense industry, enterprises are suffering from cyber attacks from cyber espionage groups. We keep seeing breaches and incidents from news. We believe many victims still have no good strategy to defend and control the situation.
In this talk, cyber espionage attacks in the last decade would be discussed from Asia Pacific region’s point of view. We’ll discuss why security solutions didn’t work, how actors easily bypassed those fancy solutions and adopted countermeasures quickly with very low cost. Besides, according to our incident response’s experience for hundreds times and consulting to help victim for several years, we will try to propose a design of security model to prevent, detect, react, and remediate cyber espionage threats.
Developing a Multi-Layered Defense for Your Systems and Data
Confidence in the security of your IBM i systems and data requires a solid understanding of potential vulnerabilities, the most effective best practices, and technologies that minimize the possibility of a data breach. We’ve grouped important security best practices and technologies into overlapping layers that provide multiple lines of defense. The ultimate goal is to always have another layer of security to thwart a would-be intruder.
Whether you are a systems security officer or an IBM i system administrator, you don’t want to miss this opportunity to learn about IBM i security best practices.
We’ll discuss:
• Common IBM i security vulnerabilities
• Configuring the security capabilities of the IBM i
• Implementing network security, access control, cryptography and more
The document provides an overview of how to start exploring IoT security as a beginner. It defines IoT and OT, discusses common attack vectors like networks, wireless communication, and applications. It then provides guidance on how to perform security testing for these vectors, including tools to use for tasks like network pentesting, radio communication testing, and mobile application testing. The goal is to help beginners learn about IoT security challenges and how to start assessing vulnerabilities.
Semelhante a LAS16-300K2: Geoff Thorpe - IoT Zephyr (20)
The document contains branding assets for Linaro Connect USA 2014, including logos for the Connect event brand, the dates and location for the 2014 event in Burlingame, California from September 15-19, and pictograms highlighting some of the sessions and activities at the event such as keynotes, demos, hacking, and meetings for various Linaro teams.
This document contains a floor plan and schedule for the GNU Tools Cauldron conference in 2014. It lists the locations of lecture theaters, breakout rooms, staff rooms and other facilities on the first floor. It also includes a schedule for lectures and breakout sessions taking place in the different rooms over the course of the conference. Registration information is provided at the bottom of the document.
This document contains the schedule for the GNU Tools Cauldron 2014 conference taking place on July 19-20, 2014. The schedule lists the start and end times for over 30 presentations across two lecture theaters on topics related to GNU tools like GCC, GDB, and the GNU C library. Presentations include discussions of compiler optimizations, debugging tools, sanitizers, new CPU architectures, and proposals for improving various GNU projects. The conference includes keynotes, technical talks, birds-of-a-feather sessions, and opportunities for networking.
This document provides branding assets for the Libbie beauty brand including the Libbie brand mark, brand mark square, fonts including Gotham Book and Southern Aire, colors, and Libbie icons. It was created by Shovan Sargunam on October 7, 2014 for the latest version of the Libbie beauty brand.
This document provides details for a project called SCube for client Jeya Sivan in its third stage. It was created on July 20, 2015 by Shovan Sargunam and includes font, color, and shape details for the project. The fonts listed are Snell Roundhand, Snell Roundhand Bold Script, and Roboto. The color palette includes shades of green, gray, orange, and pink. Basic shapes are also referenced.
This document provides an overview of a 50-hour online course called "FinTech 101: Understanding Financial Technologies" created by The Open University in partnership with Innovate Finance. The course aims to educate students on the evolution of financial technology and its impact on the financial services sector. It covers topics such as blockchain, alternative finance models, and the changing roles of banks and regulations. Upon completing the course, students will gain an understanding of key FinTech concepts and trends shaping the future of finance.
The document provides details for a branding project for a fashion and beauty boutique called Flawless including the project name, type, and date. It specifies the engagement font as DIN Condensed Bold and includes the hex codes and RGB values for six colors to be used in the brand including shades of off-white, pink, gray, and black. Contact information is listed at the bottom for further inquiries.
Open Data Plane Branding : By Shovan SargunamShovan Sargunam
This document provides version 5.5 of the logo design for OpenDataPlane.org created on January 23, 2013 by Shovan Sargunam. It includes the RGB, CMYK, and Pantone color codes for four colors used in the logo: yellow (#FFE817), light green (#E0E612), green (#5EE045), and dark green (#009645).
This document discusses how to build a professional online presence through the use of various platforms and content management systems. It focuses on LinkedIn and WordPress as effective tools. The process involves selecting a domain name and host, installing WordPress and a theme, and adding content to create a professional website or blog. Customizing settings and creating a vCard are also covered. The goal is to provide guidance on developing an online profile and web presence without requiring design or coding skills.
This document outlines a final logo design project for Core Recruitment created by Shovan Sargunam on November 27, 2011. The logo features the words "Core Recruitment" above "Logistics Recruitment" and "ideas accomplished" below a cube-shaped graphic representing "The SCube", with copyright information at the bottom noting that permission is required to transfer or use the concept.
This document outlines a logo design project for a client called Cakeaholic. It is marked as the final stage and was created on December 27, 2011 by Shovan Sargunam. The design includes the text "cake aholic" below an image of a cake with "Beautiful Cakes made with Love" below that.
This document outlines the first version of a logo design project for AAMP Engineering Ltd. created by Shovan Sargunam on October 25, 2011 for client Manit Pitroda. Various iterations of the AAMP logo are presented exploring different designs and layouts.
This document outlines version 1 of a logo design project for client Martin Cullen by designer Shovan Sargunam dated October 25, 2011. It explores various designs combining the numbers "one" and "seven" through typography and symbols.
This document provides a summary of the website concept for the client Prayertimes. It outlines key details like the project name, client, version number, and date. The concept focuses on providing prayer times and selecting cities, mosques, and prayers. It also includes ideas for the company page, services, and getting more users involved by adding their local mosques and prayer timetables.
This 3 sentence summary provides an overview of the key details in the document:
The document is a branding guide for MosLogi that outlines the corporate branding project details such as the logo, color palette, fonts, and contact information for the virtual design partner client MosLogi. It specifies the colors Mos-Blue, Grey, Black, and White in RGB, CMYK, and hex code and identifies the fonts Helvetica, Dekar, and Dekar Light to be used in the branding.
This document contains contact information for a photographer named Ashok Suren, including his telephone number, email address, and website. The website address provided directs to Ashok Suren's photography website and blog.
TheSCube designed the website for Couture Clinic, a fashion company with men's, women's, and accessories categories. The website includes sections for the company, fashion rehabilitation services, and an interactive clinic. It was designed and developed by TheSCube.
Product availability, pricing, descriptions, photos, shipping costs, contact details, order options, phone numbers, product comparisons, and additional resources are the top 10 types of information an ecommerce or shopping website should provide for customers. Clear information about products, purchasing, shipping, and the company are essential for users.
This document provides updates on fundraising efforts over the past 12 months to support a unique home for girls in an unspecified location. It details that £40,000 was raised for building materials through events, donations, and direct debits. Notable efforts included a city rooms event in November, a marathon run, and a visit from ABC News that will feature the home on a 60 minute program. Facebook activity and links with another foundation in Canada are also growing support for the home.
The document discusses the benefits of exercise for mental health. Regular physical activity can help reduce anxiety and depression and improve mood and cognitive functioning. Exercise causes chemical changes in the brain that may help protect against mental illness and improve symptoms.
Best 20 SEO Techniques To Improve Website Visibility In SERPPixlogix Infotech
Boost your website's visibility with proven SEO techniques! Our latest blog dives into essential strategies to enhance your online presence, increase traffic, and rank higher on search engines. From keyword optimization to quality content creation, learn how to make your site stand out in the crowded digital landscape. Discover actionable tips and expert insights to elevate your SEO game.
Have you ever been confused by the myriad of choices offered by AWS for hosting a website or an API?
Lambda, Elastic Beanstalk, Lightsail, Amplify, S3 (and more!) can each host websites + APIs. But which one should we choose?
Which one is cheapest? Which one is fastest? Which one will scale to meet our needs?
Join me in this session as we dive into each AWS hosting service to determine which one is best for your scenario and explain why!
Ivanti’s Patch Tuesday breakdown goes beyond patching your applications and brings you the intelligence and guidance needed to prioritize where to focus your attention first. Catch early analysis on our Ivanti blog, then join industry expert Chris Goettl for the Patch Tuesday Webinar Event. There we’ll do a deep dive into each of the bulletins and give guidance on the risks associated with the newly-identified vulnerabilities.
Digital Marketing Trends in 2024 | Guide for Staying AheadWask
https://www.wask.co/ebooks/digital-marketing-trends-in-2024
Feeling lost in the digital marketing whirlwind of 2024? Technology is changing, consumer habits are evolving, and staying ahead of the curve feels like a never-ending pursuit. This e-book is your compass. Dive into actionable insights to handle the complexities of modern marketing. From hyper-personalization to the power of user-generated content, learn how to build long-term relationships with your audience and unlock the secrets to success in the ever-shifting digital landscape.
Cosa hanno in comune un mattoncino Lego e la backdoor XZ?Speck&Tech
ABSTRACT: A prima vista, un mattoncino Lego e la backdoor XZ potrebbero avere in comune il fatto di essere entrambi blocchi di costruzione, o dipendenze di progetti creativi e software. La realtà è che un mattoncino Lego e il caso della backdoor XZ hanno molto di più di tutto ciò in comune.
Partecipate alla presentazione per immergervi in una storia di interoperabilità, standard e formati aperti, per poi discutere del ruolo importante che i contributori hanno in una comunità open source sostenibile.
BIO: Sostenitrice del software libero e dei formati standard e aperti. È stata un membro attivo dei progetti Fedora e openSUSE e ha co-fondato l'Associazione LibreItalia dove è stata coinvolta in diversi eventi, migrazioni e formazione relativi a LibreOffice. In precedenza ha lavorato a migrazioni e corsi di formazione su LibreOffice per diverse amministrazioni pubbliche e privati. Da gennaio 2020 lavora in SUSE come Software Release Engineer per Uyuni e SUSE Manager e quando non segue la sua passione per i computer e per Geeko coltiva la sua curiosità per l'astronomia (da cui deriva il suo nickname deneb_alpha).
Skybuffer SAM4U tool for SAP license adoptionTatiana Kojar
Manage and optimize your license adoption and consumption with SAM4U, an SAP free customer software asset management tool.
SAM4U, an SAP complimentary software asset management tool for customers, delivers a detailed and well-structured overview of license inventory and usage with a user-friendly interface. We offer a hosted, cost-effective, and performance-optimized SAM4U setup in the Skybuffer Cloud environment. You retain ownership of the system and data, while we manage the ABAP 7.58 infrastructure, ensuring fixed Total Cost of Ownership (TCO) and exceptional services through the SAP Fiori interface.
Let's Integrate MuleSoft RPA, COMPOSER, APM with AWS IDP along with Slackshyamraj55
Discover the seamless integration of RPA (Robotic Process Automation), COMPOSER, and APM with AWS IDP enhanced with Slack notifications. Explore how these technologies converge to streamline workflows, optimize performance, and ensure secure access, all while leveraging the power of AWS IDP and real-time communication via Slack notifications.
For the full video of this presentation, please visit: https://www.edge-ai-vision.com/2024/06/building-and-scaling-ai-applications-with-the-nx-ai-manager-a-presentation-from-network-optix/
Robin van Emden, Senior Director of Data Science at Network Optix, presents the “Building and Scaling AI Applications with the Nx AI Manager,” tutorial at the May 2024 Embedded Vision Summit.
In this presentation, van Emden covers the basics of scaling edge AI solutions using the Nx tool kit. He emphasizes the process of developing AI models and deploying them globally. He also showcases the conversion of AI models and the creation of effective edge AI pipelines, with a focus on pre-processing, model conversion, selecting the appropriate inference engine for the target hardware and post-processing.
van Emden shows how Nx can simplify the developer’s life and facilitate a rapid transition from concept to production-ready applications.He provides valuable insights into developing scalable and efficient edge AI solutions, with a strong focus on practical implementation.
Webinar: Designing a schema for a Data WarehouseFederico Razzoli
Are you new to data warehouses (DWH)? Do you need to check whether your data warehouse follows the best practices for a good design? In both cases, this webinar is for you.
A data warehouse is a central relational database that contains all measurements about a business or an organisation. This data comes from a variety of heterogeneous data sources, which includes databases of any type that back the applications used by the company, data files exported by some applications, or APIs provided by internal or external services.
But designing a data warehouse correctly is a hard task, which requires gathering information about the business processes that need to be analysed in the first place. These processes must be translated into so-called star schemas, which means, denormalised databases where each table represents a dimension or facts.
We will discuss these topics:
- How to gather information about a business;
- Understanding dictionaries and how to identify business entities;
- Dimensions and facts;
- Setting a table granularity;
- Types of facts;
- Types of dimensions;
- Snowflakes and how to avoid them;
- Expanding existing dimensions and facts.
How to Get CNIC Information System with Paksim Ga.pptxdanishmna97
Pakdata Cf is a groundbreaking system designed to streamline and facilitate access to CNIC information. This innovative platform leverages advanced technology to provide users with efficient and secure access to their CNIC details.
Fueling AI with Great Data with Airbyte WebinarZilliz
This talk will focus on how to collect data from a variety of sources, leveraging this data for RAG and other GenAI use cases, and finally charting your course to productionalization.
Unlock the Future of Search with MongoDB Atlas_ Vector Search Unleashed.pdfMalak Abu Hammad
Discover how MongoDB Atlas and vector search technology can revolutionize your application's search capabilities. This comprehensive presentation covers:
* What is Vector Search?
* Importance and benefits of vector search
* Practical use cases across various industries
* Step-by-step implementation guide
* Live demos with code snippets
* Enhancing LLM capabilities with vector search
* Best practices and optimization strategies
Perfect for developers, AI enthusiasts, and tech leaders. Learn how to leverage MongoDB Atlas to deliver highly relevant, context-aware search results, transforming your data retrieval process. Stay ahead in tech innovation and maximize the potential of your applications.
#MongoDB #VectorSearch #AI #SemanticSearch #TechInnovation #DataScience #LLM #MachineLearning #SearchTechnology
TrustArc Webinar - 2024 Global Privacy SurveyTrustArc
How does your privacy program stack up against your peers? What challenges are privacy teams tackling and prioritizing in 2024?
In the fifth annual Global Privacy Benchmarks Survey, we asked over 1,800 global privacy professionals and business executives to share their perspectives on the current state of privacy inside and outside of their organizations. This year’s report focused on emerging areas of importance for privacy and compliance professionals, including considerations and implications of Artificial Intelligence (AI) technologies, building brand trust, and different approaches for achieving higher privacy competence scores.
See how organizational priorities and strategic approaches to data security and privacy are evolving around the globe.
This webinar will review:
- The top 10 privacy insights from the fifth annual Global Privacy Benchmarks Survey
- The top challenges for privacy leaders, practitioners, and organizations in 2024
- Key themes to consider in developing and maintaining your privacy program
Salesforce Integration for Bonterra Impact Management (fka Social Solutions A...Jeffrey Haguewood
Sidekick Solutions uses Bonterra Impact Management (fka Social Solutions Apricot) and automation solutions to integrate data for business workflows.
We believe integration and automation are essential to user experience and the promise of efficient work through technology. Automation is the critical ingredient to realizing that full vision. We develop integration products and services for Bonterra Case Management software to support the deployment of automations for a variety of use cases.
This video focuses on integration of Salesforce with Bonterra Impact Management.
Interested in deploying an integration with Salesforce for Bonterra Impact Management? Contact us at sales@sidekicksolutionsllc.com to discuss next steps.
2. geoff.thorpe@nxp.com:/Microcontrollers/R&D/Security
Software
• Involvement in open source around security and networking (OpenSSL member)
• Interests in security scalability
• Member of Zephyr governance board
Hardware
• “Datapath” architecture for QorIQ and Layerscape SoCs (Networking)
• i.MX apps processors and Kinetis microcontrollers
Focused on new security problems (and solutions) brought on by the emergence of IoT
Based in Québec City, originally from Wellington, New Zealand. (Was not in LoTR)
3. Zephyr
• What, where and why
• Status
IoT security
• Terminology
• Disruption
• Observations
• Where does Zephyr fit into this?
Agenda
4. Zephyr
• What, where and why
• Status
IoT security
• Terminology
• Disruption
• Observations
• Where does Zephyr fit into this?
Agenda
See recording of
Anas Nashif’s
Zephyr talk from
Monday
5. Strategic Investment Best-of-Breed RTOS
for IoT
True Open Source
Development and
Governance
Established Code BasePermissively Licensed Modular
Why Zephyr?
15. Usage
“Add security to the product”
“Secure the edge-node”
“Integrated security, because security is
important”
16. Abusage
“Add security to the product”
“Secure the edge-node”
“Integrated security, because security is
important”
And by security you mean … what exactly?
17. Does “security” mean…
• Tamper-proof?
• Resistant to side-channel attack?
• Able to perform cryptographic operations fast/efficiently?
• Key-protection and other logical separation?
• Supports secure network protocols?
• Protects content restrictions against misuse?
• Is kept up-to-date through patch updates?
• Reliable/robust in the face of adversarial RF?
• You did some code reviews (this time round)?
18. Security facets, a less incomplete list
Cryptography;
• Software optimization
• Hardware IP
• Protocol security, interoperability
• Privacy, authentication, non-repudiation
Secure non-volatile storage
Inline encryption (memory, flash, …)
Trusted execution (secure boot, …)
Key management and protection
Certification
Code quality and review
Vulnerability analysis
Best practice
Process and production security
Compartmentalization/isolation
Digital Rights Management
IP protection (anti-cloning, …)
Resistance to side-channel attacks
• Power
• Timing
• Electromagnetic emissions
Emergency response
Security maintenance
Attack detection
Reliability (quality-of-service, stability, …)
20. What is “security”?
•“Security” on its own can mean almost anything
“Security” on its own means almost nothing
•It’s almost always context-dependent, in terms of
interpretation and importance of those different facets.
•“The minimization of insecurity (or ‘threats’)” ?
22. What is “IoT security”?
The meeting (perfect storm) of two domains;
•Device security
•Network and logical security
23. What is “IoT security”?
Device Security Network Security
Secure non-volatile storage Cryptographic s/w and h/w
Inline encryption (memory, flash, …) Protocol security & interoperability
Trusted execution (secure boot, …) Usability and clarity
Key management and protection Code quality and review
Certification Best practice
Vulnerability analysis Emergency response
Process and production security Security maintenance
DRM & IP protection (anti-cloning, …) Attack detection
Resistance to side-channel attacks Reliability (quality-of-service, stability, …)
24. IoT Security – when assumptions collide
Device security
• Implementation + certification are static
• Threat model is physical
Network security
• Patched early and often, via network
• Threat model is “the network”
Risk multipliers
• Widely deployed
• Physical and network accessibility
Large attack surface
High attack incentive
Defense de-multipliers
• Commodity pricing
• Finding and fixing bugs will be hard
Minimization of engineering investment
Reactive security down, zombies up
25. Traditional MCU-based engineering
Oriented around device-security (if at all);
•Industrial, medical, automotive, …
•Non-networked
•Heavily engineered for a static state of optimal security
•Once that’s done, ship it!
(And then move on to something else…)
27. Conventional computing complexity
MPU-based and even MCU-based systems are more and
more complex, resembling server, network, and smartphone
systems.
Things will go wrong! Reactive security (vulnerability
handling, incident response) is needed in the
microcontroller/IoT ecosystem.
29. Reactive security for MCUs / IoT
Is Device Lifecycle Management (DLM) the answer?
Not really, that’s mostly limited to;
• Installing a vendor’s “Root of Trust” (RoT)
• Being locked-in to that vendor’s code/patch-signing services
• The mechanics of deploying updates “Over The Air” (OTA)
30. Reactive security for MCUs / IoT
Reactive security is well-understood in traditional networked
computing;
• Servers
• High-end networking
• Smart-phones
• Desktops
• […]
Can we adopt the same methods?
31. Reactive security for MCUs / IoT
There are some complications with conventional vulnerability-
handling (CVE, CPE, etc.)
• The MCU/MPU and its software is often “hardware” to a host
• SoC subsystems often contain firmware too
• One product’s host OS is another product’s subsystem firmware
• CPE isn’t flexible about this hierarchical view
• Multiple vendors involved, supply-chain complexities
32. Certification for IoT?
Various things have been proposed, but;
• Limit themselves to evaluating the implementation
• Don’t account for the (post-production) process
• Works against responsible code maintenance
• Collapse the supply-chain
33. Certification for IoT?
Various things have been proposed, but;
• Limit themselves to evaluating the implementation
• Don’t account for the (post-production) process
• Works against responsible code maintenance
• Collapse the supply-chain
And if we certified the software process?
35. Certified/certifiable (audited/auditable, …)
A
Downstream
• Users
• OEMs
• Certified products
Upstream
A+
B
B+
merge
Merge is usually hard and expensive;
• Upstream doesn’t minimize diff(A,A+)
• delta(A,B) doesn’t account for re-certification difficulty
36. Upstream
• Mainline devel
• Stable/LTS
• Hardened tree
Certified/certifiable (audited/auditable, …)
A
Downstream
A+
B
B+
Hardened “downstream” is coupled to mainline work
• Feedback for security impact of mainline changes
• Creates incentive for a better mainline
• Minimize throttling of mainline development
…
37. Where does this happen?
Governance
Security TSC Marketing
Contributors
38. Summary
• RTOS upstream to be maintained as production-worthy and
current, i.e. reactive security in “real time”.
• Vulnerability handling needs a refresh for “LITE”-type tech.
• Security quality (certifiability, auditability, safety, …) integrated
into the project, without bogging down the mainline.
• Drive best-practice for IoT security, practicing what is preached.
Thanks George, David, Ebba and others for the organisation and invitation. Honoured to be here.
Friend said that by Wednesday people would be hungover, stoned or broke, and speaking before 9am would be nothing but crickets. Take a photo.
I work at NXP, heading up Security inside R&D inside MICR at NXP. Parallel to S/W and H/W R&D, though more h/w centric.
Background in OSS, OpenSSL, Apache and some other things, but not much coding in recent years.
Here because I’ve helped champion NXP participation in NXP and am on the governance board. (Will go into why…)
H/W architecture work at DN, and now dealing with MICR (i.MX and Kinetis)
This is the agenda I came to Connect with;
Zephyr (from a govt board view),
share my thoughts on IoT Security,
and how I see their relationship.
But there has been a lot of discussion of Zephyr already
Anas’ talk was video’d and should be available, highly recommend (re)watching that for detail on Zephyr.
I’ll just say a few words on that.
Focus on this “IoT Security” stuff, which could easily fill a day, necessarily cursory.
PARTNER DECK
Small Footprint RTOS for IoT
As small as 8kb
Enable application code to scale
Truly open source project
Apache* 2.0 License
Hosted by Linux Foundation
Transparent development
Cross Architecture
ARM, Intel, Synopsys
KATE
So, what are the key characteristics of Zephyr
Small Footprint RTOS for IoT
Built in support for real time as part of nanokernel, rather than an afterthought.
Architected to enable applications to scale in size - build in what you need
Leverages the Kconfig infrastructure that has been demonstrated to work in the linux kernel, so you only include the specific parts you need.
Can create application images that will fit in as small as 8kb
Truly open source project
Transparent development
All code is available for download & inspection - but that doesn’t make it an true open source project… we’re building a community here that respects the rights of contributors
Contributors retain their Copyright, contribute to project under DCO
Public email lists and review via maintainers
Maintainers from multiple companies
Apache* 2.0 License was selected for the project
Explicit patent license: Code includes a royalty-free license from contributors for their licensable patents which are necessary for the covered code
Permissive: Apache 2.0 code may incorporated into an open source or a proprietary product. There is no obligation to release improvements in source, but of course we hope you will, so we can all benefit.
Hosted by Linux Foundation
Neutral governance structure, leveraging lessons that have worked with the LInux Kernel development
Contributions are welcome from everyone, not just members.
TSC membership can be earned by merit from community contributions.
Cross Architecture
today we have Synopsys - ARC processors, ARM - M, and Intel x86 processors in the code base.
talking to MIPS, DSP, and other architectures…
KATE
Going forward, the governing board and technical steering committee are committed to the Zephyr project supporting:
secure IoT applications to be developed and deployed, we’re going to want to make sure the code in this project can be security and safety certified, yet still incorporate community contributions.
the code to remain modular, you don’t need to include anything in your products that you don’t need.
the code to incorporate the latest connectivity stacks, so it can be used in a wide array of systems.
the code to support multiple hardware architectures, so there are multiple options for implementing functions.
evolving this to be a technical meritocratic project, where the best code solution is incorporated in the code base, and others can build downstream distributions using this code base…
Basically, we’re starting with the practices and processes that have been shown to work with linux, but will evolve to suit the needs of the project, as long the core values are preserved.
PARTNER DECK
1. Saturated RTOS/ Small OS market translates to fragmentation
2. Majority of device solutions currently used are “roll your own” or “no OS”
3. Open source adoption is growing as part of IoT development
4. With more connected devices there’s increased risk for compromised devices
KATE
So lets start with Why?
Last year, market research that was done by our members showed us that
We’ve got a Saturated RTOS/ Small OS market, which has translated to fragmentation and frustration. This fragmentation means that there’s no real way to collaborate, and nowhere to share the cost of monitoring security and developing fixes.
Majority of device solutions currently used are “roll your own” or “no OS” - which is a security nightmare.
Open source adoption is growing as part of IoT development, this is where the software standards will emerge - “show me the code”, “more eyes, reduces risk”...
With more connected devices there’s increased risk for compromised devices, so we need practices and processes to minimize vulnerabilities during development, increase the range of expertise of reviewers, and automation.
So for the IoT space, our members wanted to come up with a solution to address these concerns.
Seeded by established multi-arch codebase that has existed for ~20 years.
Wind River has developed a commercial version of this and has deployed it via their Wind River Rocket product, which remains a downstream product.
In 2015, the Linux Foundation was approached to build a properly governed open source project and community, to leverage the combined creativity of all interested parties. And NXP was interested.
Like Linux on apps processors, there’s value in having a reliable, canonical base system that is arch-neutral (non-lock-in, portable), and “commodity” in a good sense. Connectivity, sensors, and embedded dev costs should leverage an economy of scale over time.
All parties ultimately cede control to the OSS development model for the resulting collective benefits.
There are a few open source RTOS options, but some have licensing problems, some are focused on a single architecture, some constrain the feature-set in order to monetize essential functionality, some don’t complement the community model with a critical mass of backing, governance, budget, etc.
If there is likely to be a “linux for MCUs”, it seems likely to be Zephyr.
Current platinum members
We’re tickled pink to have Linaro on-board and the LITE group ramping up.
We have high hopes for LITE, and dare I say, high expectations!
We follow tried and tested governance model through LF, codified in a charter.
Technical work is managed by the TSC, low barrier to entry, no need to be platinum, meritocratic process.
Governance board handles what you’d expect;
Legal
Budget
Sign-off on important escalations from TSC (requests for infrastructure funding, modifications to the charter, …)\
Through sub-committees;
Marketing (conferences, recruitment, branding/trademarks, …)
Security-sensitive stuff, handling commercial-value artifacts from funded security activities (the code remains open!)
TSC lead is on the governance board and acts as interface
In this way, separation between coding and community vs Zephyr the branded and funded entity.
Early participation means:
Influence over the direction of the project
Impact the SW architecture and HW architecture support
Guide the direction of the security, and marketing activities
Decision making on all aspects of the project
Join the project to impact the IoT small device market!
Extraordinary phase of creativity, innovation, disruption.
Some of the best developments are likely not to be planned, funded, scheduled work, but instead surprising things coming from people with itches to scratch.
Import to note that nasty rumours abound about open source types being shabby and hairy, with questionable personal hygiene. Not my intention to lend any support to that!!
If a picture is worth a thousand words, there are some cases where the converse is true.
What does this mean?
Let’s start with the first one.
So much hype and nonsense that IoT has been classified in all sorts of ways, and ridiculed in others.
A biz/marketing view tends to dominate, that classifies it in terms of certain new markets and form-factors. From a technical standpoint though, that says almost nothing (as the same technologies and challenges apply both inside and outside categories that are defined in this way).
Best to thing of it not as a market or set of markets, or as a technology, but in terms of what the fundamental engineering changes and consequences are.
Need it be any more complex than that? Indeed, as we’ll see, this may be a banal definition, but the consequences are not banal.
Another vexing term. Let’s look at some examples …
Have you heard or said things like this?
Do any of these sentences make any sense on their own?
The word is used almost to provide emotional or psychological effect.
It’s an axiomatically reassuring word, whatever it means.
A grammatical and emotional wild-card.
But this kind of grammatical and emotional wild-card can lead to trouble when it’s being used as though it has any precision at all.
I suggested at one point that saying this sort of inane thing should be a firing offense. It was point out that I would have been fired multiple times by now if that were the case. Mea culpa. I think we’re all guilty to some extent.
Try catching this word as it gets used, and play the mental exercise of asking whether its usage is smothering over any need to say what is really meant!
“Security” is often used to mean one of these things, where your only clue which might be the context, if you’re lucky. Otherwise the speaker is assuming one, and it’s not sure that the listener is assuming the same.
Piling on.
There are others. Insurance, risk-management, emergency planning, …
So we’ve highlighted pitfalls, but still not answered the question.
Key takeaway is that “it depends”.
If there isn’t some context that makes it implicit, then it doesn’t really mean anything.
You can invert it into another question, “what is insecurity”? This helps to perceive how wide things are, because “threats” is a potentially big set.
So, coming back to the original question.
I’ll give you my take, again in terms of what the fundamental engineering changes and consequences are
Traditional online systems (servers, networking, …) are focussed on networking and logical security. Exploitable implementation bugs, eavesdropping, MITM, …
Traditional offline systems (medical, automotive, …) are focussed on device security.
This is a very rough rearrangement of the “security facets” into two categories. Obvious limitations with this partitioning (“cryptographic sw and hw” also applies to device, “side-channel” also applies to network, e.g. timing).
These domains make an odd couple, they have fundamental differences to sort out.
Risk multipliers: proliferation combined with both device and network/logical threats is a big challenge.
Another point worth noting: IoT brings us lots of startups/makers/etc;
Defense de-multipliers: high-volumes coming from companies that don’t necessarily have armies of security experts, NoCs and devops.
Read the slide.
This is usually what you find in the embedded/MCU/RTOS world, lots of upstream code being thrown over the wall.
At least as far as central O/S functions and networking (connectivity, protocols, …), the complexity of AP and even MCU is growing.
That complexity means we cannot live under the delusion that the code is ever “final”. The path from the upstream code down the supply chain to the product (tweaks, added layers, embedded configs, keys, …) must be managed in a way that reacts properly to discovery of stability and security problems. Throwing something over the wall breaks compromises that link in the chain, w.r.t. reactive security.
A year or two ago, at the big RSA security conference in SF, you couldn’t shake a tree without 2 DLM solutions falling out of it.
It’s part of the answer.
But it’s dangerous in that it sounds/looks like the solution (“so you can update your software”), while in reality it’s the last mile.
So it’s justifiable to be a bit cynical …
(Personal hunch here: as real networking starts to reach edge-nodes, e.g. IPv6-over-mesh, it’s reasonable to assume they’ll “pull upon notification” rather than consistently being slaves to “push” models. Like a regular O/S doing its updates. How many regular O/S’s have an update mechanism that is provided from a professional service that is completely decoupled from the owner/maintainer of the code packages? I.e. that the transport itself is a notable differentiation or value-add?)
Go through the slide.
Supply-chain == not just adding of layers and packages, but modification and transformation. So whether a CVE applies or not is muddied.
“Systems of systems”.
(Or “subsystems within subsystems”)
As baby monitors continue to relay metallica songs at terrified children, and cars get run off the road remotely, the needs for metrics and certification (and regulation) will be inevitable.
Problem: certification is a computer science that tends to cease being applicable when you leave the static world. We at NXP deal with chips going into bank cards, passports, etc. It’s stuff that doesn’t change.
So perhaps we should certify the correct behaviour and process for keeping software secure?
After my numerous musings about IoT Security, what’s the relationship to Zephyr?
One challenge of certifiable/auditable code is that it’s slow, painful, and expensive. And it depends on which standards, criteria, use-case, …
So a successful Zephyr upstream can’t bog down on this.
Managing a downstream that *does* handle this then creates numerous challenges.
(Read the white stuff)
The security group in Zephyr wants to maintain a “hardened” codebase within the project itself, and couple the activities together for mutual benefit.
In a kind of feedback loop.
(Read white stuf)
That coupling needs to be a collaboration between the security group and TSC/general-dev-process.
This is what we’re trying to define right now, e.g. face-to-face coming up in Berlin where this will be a hot topic.
Summarize these security points w.r.t. Zephyr.
We need to handle security issues and the downstream like complex network application projects do. (disclosures, embargos, CERT/first.org/etc,)
The methods for describing, categorizing, and tracking such problems+fixes needs some attention. “LITE”-type tech is this subystems-within-subsystems stuff.
The “hardened stuff” (base for certification, …) has to be an activity within the project itself, that feeds it, and is kept manageable because of it.
For these things, plus other forward-leaning security work in the space (e.g. next-gen certification, covering process), we want to see Zephyr walk the walk.
Thanks again for the opportunity to share these thoughts with you today.
If you have itches to scratch, please give Zephyr a look, and if it doesn’t already fit your needs, it might with your help.