2006
DOI: 10.1109/tse.2006.40
|View full text |Cite
|
Sign up to set email alerts
|

Threat-driven modeling and verification of secure software using aspect-oriented Petri nets

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
104
0

Year Published

2006
2006
2018
2018

Publication Types

Select...
4
4

Relationship

0
8

Authors

Journals

citations
Cited by 131 publications
(104 citation statements)
references
References 24 publications
0
104
0
Order By: Relevance
“…It generates tests in model level first and then program level tests are produced through transforming the one at model level. It specifies models in function nets, which is a type of PrT nets extended with inhibitor arcs and reset arcs [18]. It also provides a language for mapping the elements in function nets to implementation constructs so that it is possible to transform the model level tests into program level tests that can be executed against the system under test.…”
Section: Model-based Testing and Mistamentioning
confidence: 99%
“…It generates tests in model level first and then program level tests are produced through transforming the one at model level. It specifies models in function nets, which is a type of PrT nets extended with inhibitor arcs and reset arcs [18]. It also provides a language for mapping the elements in function nets to implementation constructs so that it is possible to transform the model level tests into program level tests that can be executed against the system under test.…”
Section: Model-based Testing and Mistamentioning
confidence: 99%
“…The algorithm then analyzes the nodes in the set of test sequences until every node that matches CurrentNode in every sequence is replaced with a leaf node by using the following replacement method. (1) If CurrentNode is in a test sequence that has children with an AND relationship, replace CurrentNode with these children in that sequence in the left-to-right order in which they appear in the tree (lines [12][13][14][15][16][17][18][19][20][21][22]. (2) If CurrentNode is in a test sequence that has children with an OR relationship, we create the same number of sequences as children of the CurrentNode and replace CurrentNode in each of these sequences with one of the children of the OR relationship.…”
Section: Test Sequence Generation Algorithmmentioning
confidence: 99%
“…To date, researchers have developed various security testing techniques. These include techniques that generate test cases or identify vulnerabilities focusing on specific attacks, such as SQL injection or cross-site scripting (XSS) [4][5][6][7]; generate test cases using model-based approaches, such as threat modeling or use case modeling [8][9][10][11][12]; and generate test cases from control policy specifications [13,14] (Section 2 provides details).…”
Section: Introductionmentioning
confidence: 99%
“…Several notations have been proposed for threat modeling, such as threat trees (a variation of fault trees for safety analysis) [19], threat nets (based on Petri nets) [15,24], misuse cases (based on use case modeling) [4,18]. Obviously, threat models can be used to generate security tests for exercising whether the implementation is resistant from the identified security threats.…”
Section: Background and Related Workmentioning
confidence: 99%