2018
DOI: 10.1016/j.cose.2018.04.008
|View full text |Cite
|
Sign up to set email alerts
|

Building an automotive security assurance case using systematic security evaluations

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
31
0

Year Published

2019
2019
2024
2024

Publication Types

Select...
4
4
1

Relationship

0
9

Authors

Journals

citations
Cited by 43 publications
(36 citation statements)
references
References 20 publications
0
31
0
Order By: Relevance
“…The proposed approach requires very few configurations at the cloud side, and can be offered through the Security-as-a-Service paradigm. (Cheah et al, 2018) considered the automotive world, where cases are generated after evaluating the severity of threats. Threats are found through threat modeling and confirmed with a penetration testing.…”
Section: Comparison With Existing Solutionsmentioning
confidence: 99%
See 1 more Smart Citation
“…The proposed approach requires very few configurations at the cloud side, and can be offered through the Security-as-a-Service paradigm. (Cheah et al, 2018) considered the automotive world, where cases are generated after evaluating the severity of threats. Threats are found through threat modeling and confirmed with a penetration testing.…”
Section: Comparison With Existing Solutionsmentioning
confidence: 99%
“…Although they provide outstanding benefits on the perceived trust, they lack of generality and cannot be easily adapted to current scenarios, where different services deployed on hybrid public and private infrastructures are composed at run time. Many of these solutions are in fact ad hoc (Cheah et al, 2018;Elsayed and Zulkernine, 2018), meaning they cannot handle a modern IT system as a whole. Moreover, existing assurance techniques, and corresponding frameworks, require some effort for being integrated with the target system, interfering with its normal operation (e.g., performance), and introducing not-negligible (monetary and business) costs.…”
Section: Introductionmentioning
confidence: 99%
“…The presented approach has been applied by some automotive manufacturers and been proven by a few projects. An automotive testing and evaluation methodology is proposed and validated for the case study of automotive Bluetooth interface [90]. The testing is carried out based on the EVITA threat model and the attack trees after the analysis.…”
Section: Evitamentioning
confidence: 99%
“…The SAE refers to two security classification methods, which provide engineering process suggestions aligned to ISO 26262 (Martin et al, 2017;Salay et al, 2018) standard: HEAVENS (HEAling Vulnerabilities to ENhance Software security and safety) and EVITA (E-Safety Vehicle Intrusion Protected Applications) (Cheah et al, 2018). Now I will describe the EVITA method and define additional improvement suggestion in regard to its methodology.…”
Section: Classification Of Security Levelsmentioning
confidence: 99%