Description

Security
16.-17. January 2019/Espoo (FI)
Only 3 seats left
Register before 21st December
2 days
EUR 1.650

Request more information

Leevi Lehtinen
phone: +358 40 546 1469
leevi.lehtinen@nohau.se

Lena Bernhardsson
phone: +46 (0) 40 59 22 09
lena.bernhardsson@nohau.se

This introduction to automotive embedded security course will explain the issues, show how to address the risks and provide an introduction for the importance of having the correct procedures and processes in place to develop secure systems.

The Problem

Modern automobiles contain between 60 and 100 microcontrollers and microprocessors which are connected on complex internal networks and some of which are connected externally via wireless communications protocols.
This connectivity increases the security risk of the whole system and insecure devices can result in brand damage, financial liabilities, expensive product returns and even safety issues.

Aims of the course

  • To raise awareness of the need for security in the automotive industry.
  • To identify specific security requirements participants might need to meet.
  • To improve understanding of how security can be become part of the design/development/test process.

Who is this course for?

Program managers, team leaders, senior developers and testers responsible for design, implementation and testing of embedded automotive and other moving vehicles security products.

Training Scope

This course provides an introduction to understanding the risks associated with embedded systems and to ensure that security is “built in” from the start.

Expected outcomes. Participants should be able to…

  • Identify the security issues for automotive embedded devices.
  • Give examples of the consequences of embedded security failure.
  • Identify security technologies that are available to help.
  • Explain the security terminology commonly used in security requirements.
  • Identify specific security requirements that are directly applicable to their business.
  • Explain the connection between security, safety and functional requirements.
  • Use a high-level threat model to identify possible security vulnerabilities and their mitigations.
  • Create an action plan for meeting the security needs of their current processes.

This is a technical training course but does not assume prior security knowledge.

Content:

Day 1:

  • Security and the Secure Software Development Lifecycle (SSDL)
    – 
    In this session we describe the current automotive embedded system security landscape, identifying the risks and the threats and the reasons why embedded systems need different security measures to other computer systems. We also explain the need in embedded systems for system hardening as well as the targeted measures required for normal application security. We discuss how existing standards for safety and security address these requirements.
    Adopting a Secure Software Development Lifecycle (SSDL) can help to build security into your products, so this session explains what that involves as well as introduce some useful security terminology.
  • Hardware security
    Topics like: hardware encryption engines, secure boot, key storage and management and provisioning.
  • Common software attacks and mitigations
    The mechanisms behind vulnerabilities and other common attacks on embedded systems.
    Identify practical steps to mitigate against these attacks with best practices.
  • Common attacks – practical examples
    In this session, participants can try their skills as the attacker of a vulnerable system. Working through increasingly complex levels of vulnerability, each successful exploit is followed by a practical exercise showing the techniques that could have been used to protect the system.

Day 2:

  • Threat modelling and implementation
    This session introduces threat modelling using data flow diagrams and STRIDE analysis to identify potential vulnerabilities in a design and covers how to design mitigations for these vulnerabilities using standard control measures.
  • Threat modelling example
    In this session participants produce their own threat model of a typical consumer electronics product. Using the techniques from the previous session, possible threats and mitigations will be identified.
  • Security architecture and design
    This session we explain how to identify your security goals and what you need to protect in your product and how to use these along with functional, safety and other compliance requirements to create your security requirements.
  • Testing deployment and maintenance
    In this final session we take a look at security testing practices such as threat model driven tests, automated tests and vulnerability assessment and penetration testing. We also discuss deploying and maintaining your secure products.

Do you wish more information!

Contact us for offers, information or advice!