Combining Risk Analysis and Security Testing

Großmann, Jürgen; Schneider, Martin; Viehmann, Johannes; Wendland, Marc-Florian

doi:10.1007/978-3-662-45231-8_23

Cited by 13 publications

(19 citation statements)

References 12 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Grossmann et al [51] present an approach called Risk-Based Security Testing that combines risk analysis and risk-based test design activities based on formalized security test patterns. The involved security test patterns are formalized by using a minimal test design strategies language framework which is represented as a UML profile.…”

Section: Risk-based Security Testingmentioning

confidence: 99%

Security Testing

Felderer

Büchler

Johns

et al. 2016

Advances in Computers

126

View full text Add to dashboard Cite

ReuseThis article is distributed under the terms of the Creative Commons Attribution-NonCommercial-NoDerivs (CC BY-NC-ND) licence. This licence only allows you to download this work and share it with others as long as you credit the authors, but you can't change the article in any way or use it commercially. More information and the full terms of the licence here: https://creativecommons.org/licenses/ Takedown If you consider content in White Rose Research Online to be in breach of UK law, please notify us by emailing eprints@whiterose.ac.uk including the URL of the record and the reason for the withdrawal request. Identifying vulnerabilities and ensuring security functionality by security testing is a widely applied measure to evaluate and improve the security of software. Due to the openness of modern software-based systems, applying appropriate security testing techniques is of growing importance and essential to perform effective and efficient security testing. Therefore, an overview of actual security testing techniques is of high value both for researchers to evaluate and refine the techniques and for practitioners to apply and disseminate them. This chapter fulfills this need and provides an overview of recent security testing techniques. For this purpose, it first summarize the required background of testing and security engineering. Then, basics and recent developments of security testing techniques applied during the secure software development lifecycle, i.e., model-based security testing, code-based testing and static analysis, penetration testing and dynamic analysis, as well as security regression testing are discussed. Finally, the security testing techniques are illustrated by adopting them for an example three-tiered web-based business application.

show abstract

Section: Risk-based Security Testingmentioning

confidence: 99%

Security Testing

Felderer

Büchler

Johns

et al. 2016

Advances in Computers

126

View full text Add to dashboard Cite

show abstract

“…The evaluation is carried out in terms of an hypotehtical example problem applied on the NASA shuttle flight software. Großmann et al (2014aGroßmann et al ( , 2014b suggest an approach that supports both risk-driven security testing and test-driven security risk analysis. Their approach is somewhat similar to our approach in the sense that it makes use of threat scenarios to identify security tests.…”

Section: Related Workmentioning

confidence: 99%

“…The approach is supported by a tool. Großmann et al (2014b) gives an analytical evaluation of the tool, and mention that the approach will be evaluated in future case studies.…”

Section: Related Workmentioning

confidence: 99%

Assessing the Usefulness of Testing for Validating and Correcting Security Risk Models Based on Two Industrial Case Studies

Erdogan

Seehusen

Stølen

et al. 2015

International Journal of Secure Software Engineering

View full text Add to dashboard Cite

The authors present the results of an evaluation in which the objective was to assess how useful testing is for validating and correcting security risk models. The evaluation is based on two industrial case studies. In the first case study the authors analyzed a multilingual financial Web application, while in the second case study they analyzed a mobile financial application. In both case studies, the testing yielded new information which was not found in the risk assessment phase. In particular, in the first case study, new vulnerabilities were found which resulted in an update of the likelihood values of threat scenarios and risks in the risk model. New vulnerabilities were also identified and added to the risk model in the second case study. These updates led to more accurate risk models, which indicate that the testing was indeed useful for validating and correcting the risk models.

show abstract

“…Based on the literature review, we identified six approaches that focus on risk-driven security testing. These are the approaches suggested by Xu et al [166], Murthy et al [107], Zech et al [171,172], Botella et al [15], Großmann et al [57,58], and Seehusen [135].…”

Section: Risk-driven Security Testingmentioning

confidence: 99%

“…The approaches suggested by Botella et al [15], Großmann et al [57,58], and Seehusen [135] identify security risks by making use of the CORAS risk analysis language [91]. The risk models contain threat scenarios which are used in these approaches to identify high-level test procedures.…”

Section: Risk-driven Security Testingmentioning

confidence: 99%

Approaches for the combined use of risk analysis and testing: a systematic literature review

Erdogan

Runde

et al. 2014

Int J Softw Tools Technol Transfer

View full text Add to dashboard Cite

The continuous increase of sophisticated cyber security risks exposed to the public, industry, and government through the web, mobile devices, social media, as well as targeted attacks via state-sponsored cyberespionage, clearly show the need for software security. Security testing is one of the most important practices to assure an acceptable level of security. However, security testers face the problem of determining the tests that are most likely to reveal severe security vulnerabilities. This is important in order to focus security testing on the most risky aspects of a system.In response to this challenge, the security testing community has proposed an approach to support security testing with security risk assessment (risk-driven security testing). In general, the purpose of risk-driven security testing is to focus the testing on the most severe security risks that the system under test is exposed to. However, current approaches carry out risk assessment at a high-level of abstraction (for example, business level) and then perform the testing accordingly. This is a disadvantage from a testing perspective because it leaves a gap between the risks and the test cases which are defined at a low-level of abstraction (for example, implementation level). This gap makes it difficult to identify exactly where in the system risks occur, and exactly how the risks should be tested. This also indicates that current approaches focus on risk-driven test planning at a high-level of abstraction for test management purposes, and do not necessarily focus on guiding the tester in designing test cases that have the ability to reveal vulnerabilities causing the most severe risks.This thesis proposes a model-based approach to risk-driven security testing, named CORAL, which is specifically developed to help security testers select and design test cases based on the available risk picture. The CORAL approach consists of seven steps supported by a risk analysis language. The risk analysis language is a modeling language based on UML interactions, and is formalized by an abstract syntax and a schematically defined natural-language semantics.As part of the development and evaluation process of the CORAL approach we carried out three industrial case studies. In the first two case studies, we investigated how risk assessment may be used to identify security test cases, as well as how security testing may be used to improve security risk analysis results. The experiences we obtained from these two industrial case studies helped us to, among other things, shape the CORAL approach. In the third case study we carried out the CORAL approach in an industrial setting in order to evaluate its applicability. The results indicate that CORAL supports security testers in producing risk models that are valid and directly testable. By directly testable risk models we mean risk models that can be reused and specified as test cases based on the interactions in the risk models. This, in turn, helps testers to select and design test cases according to t...

show abstract

Combining Risk Analysis and Security Testing

Cited by 13 publications

References 12 publications

Security Testing

Security Testing

Assessing the Usefulness of Testing for Validating and Correcting Security Risk Models Based on Two Industrial Case Studies

Approaches for the combined use of risk analysis and testing: a systematic literature review

Contact Info

Product

Resources

About