2017 IEEE Real-Time Systems Symposium (RTSS) 2017
DOI: 10.1109/rtss.2017.00012
|View full text |Cite
|
Sign up to set email alerts
|

Network Scheduling for Secure Cyber-Physical Systems

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
3
1
1

Citation Types

0
22
0

Year Published

2018
2018
2022
2022

Publication Types

Select...
3
3
2

Relationship

3
5

Authors

Journals

citations
Cited by 25 publications
(22 citation statements)
references
References 16 publications
0
22
0
Order By: Relevance
“…For both studies, sensor values are transmitted over an internal vehicle's network, such as commonly used CAN bus. Note that in [14], we provide additional automotive case-studies (and the overall scheduling framework) for intermittent authentication of CANbus messages from system sensors, and in [15] we show benefits of intermittent authentication on vehicle's ECU scheduling.…”
Section: Case Studiesmentioning
confidence: 98%
“…For both studies, sensor values are transmitted over an internal vehicle's network, such as commonly used CAN bus. Note that in [14], we provide additional automotive case-studies (and the overall scheduling framework) for intermittent authentication of CANbus messages from system sensors, and in [15] we show benefits of intermittent authentication on vehicle's ECU scheduling.…”
Section: Case Studiesmentioning
confidence: 98%
“…(1) Initialize a MINITEE context through invoking MINITEE-Driver: Time since the real-time task calls API TEE_InitializeContext until MINITEE-Driver issues a world switching using SMC 0; (2) SMC from Normal world handling: Time since the processor enters in the monitor's vector table until restore the Secure world context; (3) Create a new TEE task or resume a previous suspended one: Time since MINITEE scheduler occupies the CPU until the called TA starts to execute on TEE task's stack; (4) Suspend MINITEE scheduler: Time since TA finishes its execution until MINITEE scheduler issues a SMC 0 to switch world back to Normal World; (5) Handle SMC from Secure world in Monitor module: Time since the processor enters in the monitor's vector table until restore the Normal world context ; (6) Finalize the MINITEE context: Time since the processor gets back to Normal world until MINITEE-Driver frees up the shared memory and goes back to the execution of the calling real-time task. Table 4 presents the collected results.…”
Section: A Partition Ta Invokingmentioning
confidence: 99%
“…If those information are tampered with an ill-intentioned entity, the entire drone can be mis-routed, leading failed delivery [1]. Complex authentication mechanisms can improve system security, but at the price of introducing large overhead and degrading the real-time performance of the system [2]. Therefore, a platform-level security solution for such systems should not only enhance the security but also minimize the negative influence to the real-time performance.…”
Section: Introductionmentioning
confidence: 99%
“…[22], we only focus on the computational aspect of the problem and show how to guarantee timeliness for security-aware control tasks, while Ref. [21] presents our initial attempt to ensure timeliness of communication messages. Yet, Refs [21] and [22] only consider decoupled scenarios where the only concern for incorporating security is either ECU processing time (with the assumption that the network is not congested) or network bandwidth (while ECUs are not considered).…”
Section: Introductionmentioning
confidence: 99%
“…However, the problem of providing integrated QoC and security guarantees while ensuring timeliness in scenarios where both ECU processing time and network bandwidth are limited remains open, as both solutions from Refs [21] and [22] fall short in such case. Essentially, the methods from Ref.…”
Section: Introductionmentioning
confidence: 99%