It is not necessary to always present the terrorist attacker that encroaches into another's antiblock system (ABS) as the dramatic example to alert the need for vehicular IT security. It may suffice to imagine some very simple encroachments on in-vehicle communication integrity or on functional availability that could cause a suddenly uncontrolled spattering windshield washer or a malfunctioning door look system that - in the wrong situation - actually can suffice to threaten life. Although most vehicular applications are developed to face (random) technical failures, they almost never consider a human malicious encroachment. Hence, many vehicular IT systems are susceptible to security issues and hence, can quickly become also safety-critical. This work describes how to identify the individual security objectives of all entities involved in a typical vehicular IT application. It describes how to deduce the corresponding security requirements that fulfill the security objectives identified before. Finally, this work indicates some helpful vantages and several constraints characteristical when establishing IT security in the automotive domain.
Security requirements engineering in the automotive domain: On specification procedures and implementational aspects
2008
14 Seiten, 2 Tabellen, 28 Quellen
Conference paper
English
Some Implementational Issues of Convection Schemes for Finite Volume Formulations
British Library Conference Proceedings | 1993
|Scene point constraints in camera auto-calibration: an implementational perspective
British Library Online Contents | 2005
|Engineering Requirements for Automotive Textiles
SAE Technical Papers | 1975
|Standard Galley System Specification Appendix II 20.0 Data Requirements and Procedures
SAE Technical Papers | 2005