Proceedings of the IEEE/ACM International Conference on Automated Software Engineering 2010
DOI: 10.1145/1858996.1859001
|View full text |Cite
|
Sign up to set email alerts
|

Analyzing security architectures

Abstract: We present a semi-automated approach, Secoria, for analyzing a security runtime architecture for security and for conformance to an object-oriented implementation. Typecheckable annotations describe architectural intent within the code, enabling a static analysis to extract a hierarchical object graph that soundly reflects all runtime objects and runtime relations between them. In addition, the annotations can describe modular, code-level policies. A separate analysis establishes traceability between the extra… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
12
0

Year Published

2012
2012
2019
2019

Publication Types

Select...
5
1
1

Relationship

1
6

Authors

Journals

citations
Cited by 19 publications
(12 citation statements)
references
References 31 publications
0
12
0
Order By: Relevance
“…The importance of executable architecture is that it can reveal all possible communications [2]. Its advantage over other approaches is that it offers dynamic analysis to verify whether the set of allowable executions can divert from its intended behaviour, or whether it allows additional behaviours.…”
Section: Model-checking Techniquesmentioning
confidence: 99%
See 2 more Smart Citations
“…The importance of executable architecture is that it can reveal all possible communications [2]. Its advantage over other approaches is that it offers dynamic analysis to verify whether the set of allowable executions can divert from its intended behaviour, or whether it allows additional behaviours.…”
Section: Model-checking Techniquesmentioning
confidence: 99%
“…The work of Oladimeji et al [133] took a similar approach by adding tagged values to their architecture that model security details (such as SSH connection type); their focus is on determining whether or not a given software architecture model realizes a set of security policies; but like many of the surveyed works, they failed to address the requirement for architecture models to be amenable to changes in order to reflect new requirements and threats. The work of Antoun et al [2] went further to support reasoning about security at both the architecture and code level.…”
Section: Traceability and Conformancementioning
confidence: 99%
See 1 more Smart Citation
“…3.2,and 3.3]. Another previous work [10] made a simplistic assumption that dataflow edges can be approximated by reverting points-to edges, which turned out to be imprecise.…”
Section: Formalization Of the Analysismentioning
confidence: 99%
“…An OOG can be then abstracted into a standard runtime architecture. We specialized OOG to security architectures showing how an OOG maps to a DFD [10]. The OOG showed pointsto edges, but during architectural risk analysis, architects require dataflow communication edges on the OOG.…”
Section: Introductionmentioning
confidence: 99%