2016
DOI: 10.1016/j.scico.2016.02.008
|View full text |Cite
|
Sign up to set email alerts
|

Runtime enforcement of regular timed properties by suppressing and delaying events

Abstract: Runtime enforcement is a verification/validation technique aiming at correcting possibly incorrect executions of a system of interest. In this paper, we consider enforcement monitoring for systems where the physical time elapsing between actions matters. Executions are thus modelled as timed words (i.e., sequences of actions with dates). We consider runtime enforcement for timed specifications modelled as timed automata. Our enforcement mechanisms have the power of both delaying events to match timing constrai… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

1
30
0

Year Published

2017
2017
2022
2022

Publication Types

Select...
5
3
1

Relationship

5
4

Authors

Journals

citations
Cited by 27 publications
(31 citation statements)
references
References 43 publications
1
30
0
Order By: Relevance
“…The work reported in [5] on the runtime enforcement of timed properties is also close from our offline phase. Our offline technique assumes a weaker enforcer that can only introduce delays but not shorten interval between events nor suppress events.…”
Section: B Related Worksupporting
confidence: 53%
“…The work reported in [5] on the runtime enforcement of timed properties is also close from our offline phase. Our offline technique assumes a weaker enforcer that can only introduce delays but not shorten interval between events nor suppress events.…”
Section: B Related Worksupporting
confidence: 53%
“…In this work we present a possible analysis, but there are several complementary aspects worth to be analyzed. For instance, timing aspects in runtime enforcement [30,18] have not been considered, but timing could be another source of interferences. For instance, the joint activation of two enforcers may successfully cause the enforcement of some security policies, but may cause serious slow downs that dramatically annoy users.…”
Section: Discussionmentioning
confidence: 99%
“…This approach has been pioneered by the work of Schneider [145] on security automata which halt the program whenever it deviates from a safety requirement. Since then, there has been a great effort in the RV community to define new enforcement mechanisms with primitives [146][147][148][149][150] or that support more expressive specifications [151][152][153].…”
Section: Runtime Enforcementmentioning
confidence: 99%