2015 IEEE 8th International Conference on Software Testing, Verification and Validation (ICST) 2015
DOI: 10.1109/icst.2015.7102630
|View full text |Cite
|
Sign up to set email alerts
|

Security Threat Identification and Testing

Abstract: Business applications are more and more collaborative (cross-domains, cross-devices, service composition). Security shall focus on the overall application scenario including the interplay between its entities/devices/services, not only on the isolated systems within it. In this paper we propose the Security Threat Identification And TEsting (STIATE) toolkit to support development teams toward security assessment of their underdevelopment applications focusing on subtle security logic flaws that may go undetect… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
4
0

Year Published

2018
2018
2022
2022

Publication Types

Select...
4
2
1

Relationship

1
6

Authors

Journals

citations
Cited by 7 publications
(5 citation statements)
references
References 11 publications
(33 reference statements)
0
4
0
Order By: Relevance
“…For example, we plan to cover participants who forget to include relevant security headers and are supported by appropriately configured monitors in this delicate task. Finally, we would like to further engineer Bulwark to make it easier to use for people who have no experience with ProVerif, e.g., by including support for a graphical notation which is compiled into ProVerif processes, similarly to the approach in [10].…”
Section: Discussionmentioning
confidence: 99%
“…For example, we plan to cover participants who forget to include relevant security headers and are supported by appropriately configured monitors in this delicate task. Finally, we would like to further engineer Bulwark to make it easier to use for people who have no experience with ProVerif, e.g., by including support for a graphical notation which is compiled into ProVerif processes, similarly to the approach in [10].…”
Section: Discussionmentioning
confidence: 99%
“…Therefore, it is essential that organizations identify as early as possible the risks that arise from improper access right management and find solutions to avoid them from occurring [64]. The article [65] described that collaboration across domains, devices, and service composition is becoming increasingly common in business applications. In addition to its isolated systems, security should focus on the general application scheme, comprising interaction between its units, devices, and services.…”
Section: Threat Identificationmentioning
confidence: 99%
“…In addition to its isolated systems, security should focus on the general application scheme, comprising interaction between its units, devices, and services. Security Threat Identification and testing is a toolkit that [65] introduce to assist development teams with security testing of their underdevelopment applications with the aim of identifying delicate security logical errors that may go hidden by using existing industrial technology [65].…”
Section: Threat Identificationmentioning
confidence: 99%
“…The analysis of satisfaction also requires the identification of user tasks as the user feedback may be referring to a particular task [4]. Security analysis highly relies on the identification and description of potential threats [9]. The analysis of possible threats on user tasks requires precise and exhaustive description of user tasks [7].…”
Section: Generic Requirements For Engineering Authentication Mechanis...mentioning
confidence: 99%