2001
DOI: 10.3233/jcs-2001-9303
|View full text |Cite
|
Sign up to set email alerts
|

Model checking security properties of control flow graphs

Abstract: A fundamental problem in software-based security is whether local security checks inserted into the code are sufficient to implement a global security property. This article introduces a formalism based on a linear-time temporal logic for specifying global security properties pertaining to the control flow of the program, and illustrates its expressive power with a number of existing properties. We define a minimalistic, security-dedicated program model that only contains procedure call and run-time security c… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
4
1

Citation Types

0
76
0

Year Published

2005
2005
2023
2023

Publication Types

Select...
6
1

Relationship

1
6

Authors

Journals

citations
Cited by 57 publications
(76 citation statements)
references
References 39 publications
0
76
0
Order By: Relevance
“…Perhaps the principal division between previous approaches to the enforcement of trace based program properties is between those systems that detect errors at run-time [26,22,31,7,6,1,13], vs. those that detect errors at compile-time [3,11,8,30]. Run-time approaches are more accurate since a compiletime analysis must conservatively approximate what events could occur; the compiletime analysis will also reject some safe programs, due to the need to be conservative.…”
Section: Compile-time Vs Run-time Verificationmentioning
confidence: 99%
See 3 more Smart Citations
“…Perhaps the principal division between previous approaches to the enforcement of trace based program properties is between those systems that detect errors at run-time [26,22,31,7,6,1,13], vs. those that detect errors at compile-time [3,11,8,30]. Run-time approaches are more accurate since a compiletime analysis must conservatively approximate what events could occur; the compiletime analysis will also reject some safe programs, due to the need to be conservative.…”
Section: Compile-time Vs Run-time Verificationmentioning
confidence: 99%
“…Trace Specification Logics and Model Checking Some of the aforecited systems also automatically verify assertions at compile-time via model-checking, including [3,11,8], though none of these define a rigorous process for extracting an LTS from higherorder programs. In these works, the specifications are temporal logics, regular languages, or finite automata, and the abstract control flow is extracted as an LTS in the form of a finite automaton, grammar, or PDA.…”
Section: Compile-time Vs Run-time Verificationmentioning
confidence: 99%
See 2 more Smart Citations
“…Most static analyses approximate stack inspection in terms of permissions [4,5,1,2,11]. Our proposed analysis is unique in that it compute success or fail information in terms of permission checks.…”
Section: Related Workmentioning
confidence: 99%