Cyber Security Requirements Engineering


Practice
 Methods
Cyber Security Requirements Engineering
Hands-on guidance for developing and managing security requirements
Written by Christof Ebert

29. October 2015 · 14 minutes read
Print Mail
Sophisticated functionality and ever-increasing perfection of embedded and distributed IT systems

have been made possible through an increasing amount of interconnected components. Open
interfaces, standardized platforms, and a variety of heterogeneous networks drive complexity and
security risks. For any given system it is only a question of time before the resulting security
vulnerabilities are systematically identified and exploited at the harm and expense of users and
manufacturers. This article provides experience and guidance concerning how information security
can be successfully achieved with a security requirements engineering perspective. Our experiences
from embedded security in automotive, transport, and automation show that security is only
successful with a systematic understanding and handling of security requirements and their
interaction with functional requirements. Four requirements engineering (RE) related levers for
achieving embedded security are addressed: security requirements elicitation, security analysis,
security design, and security validation. We will show for each of these levers how security is analyzed
and implemented. Only systematic and disciplined security requirements engineering will ensure that
security needs are met end-to-end from concept to architecture to verification and test and – most
relevant – operations, service and maintenance.
1. Cyber Security Requirements
Security is a quality attribute which interacts heavily with other such attributes, including availability,
safety, and robustness. It is the sum of all of the attributes of an information system or product which
contributes towards ensuring that processing, storing, and communicating of information sufficiently
protects confidentiality, integrity, and authenticity. Cyber security implies that it is not possible to do
anything with the processed or managed information which is not explicitly intended by the specification
of the embedded system [1] [2].
To better illustrate evolving cyber security needs, we will look to modern automotive systems. Figure 1
shows the interaction of functions in their distributed networks being an essential part for our today’s
modern infrastructures with their needs for safety and comfort. Besides the further development of
innovative sensors like radar and camera systems and the analysis of the signals in highly complex
systems, the connected cars will be a driving factor for tomorrow‘s innovation. Internet connections will
not only provide the need for information to the passenger - functions like eCall, communication
between cars, and car to infrastructure (vehicle2x) shows high potential for revolutionizing the individual
traffic. This includes the improvement of the traffic flow controlled by intelligent traffic lights, warnings
from roadside stations, or brake indication of adjacent cars. This builds the basis for enhanced driver
assistant systems and automated driving. But the connection to the outer world also bears the risk for
attacks to the car.
Figure 1: Car with remote connections
Figure 1 shows interworking for vehicle2x and external communication that are already available today
or will become available in the near future. Each connection to the car has a potential risk for an attack,
regardless whether it is wireless or wired - only the threat is different. The access through a connector is
only possible for a limited amount of cars, whereas a far field connection can be accessed from
anywhere in the world. But also near field connections play an important role, such as a tire pressure
monitoring system, Bluetooth, and wireless LAN. Security and reliability of these connections will be
essential for the acceptance and success of these systems. With the introduction of this technology
precautions must be taken to increase the reliability and to reduce the vulnerability to the system.
Functional safety needs cyber security. Based on the specific challenges of cyber security, OEMs and
suppliers have to realize an effective protection against manipulations of automotive electronic and
electric (E/E) systems. Key points in the development of protected E/E systems are the proper
identification of security requirements, the systematic realization of security functions, and a security
validation to demonstrate that security requirements have been met. The following items need to be
considered to achieve security in the car development process:
 Standardized process models for a systematic approach which are anchored in the complete
development process. This starts in the requirements analysis phase, and continues through the
design and development to the test and integration of components and the network.
 Quick software updates to close vulnerabilities in ECU software.
 Reliable protocols that are state-of-the-art and meet long-term security demands. Related to
security, this is often combined with cryptographic keys. So a key management over the lifecycle
of the vehicle must be maintained.
 In-vehicle networks and a system architecture that provide flexibility and scalability and are
designed with consideration of security aspects.

Cyber Security Requirements Engineering

Uploaded by

Copyright:

Available Formats

Cyber Security Requirements Engineering

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Cyber Security Requirements Engineering

Uploaded by

Copyright:

Available Formats



Cyber Security Requirements Engineering

Hands-on guidance for developing and managing security requirements

Written by Christof Ebert

Sophisticated functionality and ever-increasing perfection of embedded and distributed IT systems

1. Cyber Security Requirements

Figure 1: Car with remote connections

 Quick software updates to close vulnerabilities in ECU software.

You might also like