2024Unpublished venueRequires access

A Disambiguation of Security-based Software Testing

Robert Dilworth, Charan Gudla, Md. Shohel Rana, Feroz Ahmed

Open publisher page 0 citations

Abstract

This paper reviews security testing, covering the concepts and notions essential to the discipline. The following analysis uses an inverted funnel approach to reduce the broad topic of software testing into its constituent parts. With this framework in mind, the paper will attempt to answer the following questions. Why is software testing significant? What are the roles of users and developers as they relate to software? What techniques are commonly used when testing software? Is the discipline of software testing unified; if not, what controversies exist, and what do they concern? What is security testing? What is the purpose of security testing? What metrics are used to guide security testing? What are common threats that hamper or impede security testing? How can developers mitigate the risk posed by security threats; what defensive options are available? What improvements can be made to software testing? What can occur in the absence of software/security testing?

About this research paper

What this paper is about

This paper reviews security testing, covering the concepts and notions essential to the discipline. The following analysis uses an inverted funnel approach to reduce the broad topic of software testing into its constituent parts. With this framework in mind, the paper will attempt to answer the following questions. Why is software testing significant? What are the roles of users and developers as they relate to software? What techniques are commonly used when testing software? Is the discipline of software testing unified; if not, what controversies exist, and what do they concern? What is security testing? What is the purpose of security testing? What metrics are used to guide security testing? What are common threats that hamper or impede security testing? How can developers mitigate the risk posed by security threats; what defensive options are available? What improvements can be made to software testing? What can occur in the absence of software/security testing?

Why it matters

A significance statement is not available in the OpenAlex record.

Key contribution

A contribution statement is not available in the OpenAlex record.

Method / approach

Method details are not available in the OpenAlex metadata.

Main findings

Findings are not separately available in the OpenAlex metadata.

Limitations

Limitations are not available in the OpenAlex metadata.

Applications

Application details are not available in the OpenAlex metadata.

Available abstract

This paper reviews security testing, covering the concepts and notions essential to the discipline. The following analysis uses an inverted funnel approach to reduce the broad topic of software testing into its constituent parts. With this framework in mind, the paper will attempt to answer the following questions. Why is software testing significant? What are the roles of users and developers as they relate to software? What techniques are commonly used when testing software? Is the discipline of software testing unified; if not, what controversies exist, and what do they concern? What is security testing? What is the purpose of security testing? What metrics are used to guide security testing? What are common threats that hamper or impede security testing? How can developers mitigate the risk posed by security threats; what defensive options are available? What improvements can be made to software testing? What can occur in the absence of software/security testing?

Key concepts: Security testing, Software security assurance, Computer science, Security bug, System integration testing, Software performance testing, Software testing, Test strategy

Related papers

Back to paper searchBrowse research topicsOriginal source
A Disambiguation of Security-based Software Testing — Research Paper | ScholarLens