Newshot

On Improving the Adoption, Usability, and Retention of Static Application Security Testing (SAST) Tools

Summary

arXiv:2611.21621v1 Announce Type: new Abstract: As the Internet connects more of the world, software vulnerabilities create growing security risks. Because software developers are responsible for building and maintaining secure applications, they rely on tools and techniques that help identify vulnerabilities early in development. Static Application Security Testing (SAST) tools analyze source code to identify potential security weaknesses before software is deployed. Although SAST can help developers address vulnerabilities proactively, these tools also present usability and adoption challenges. This thesis examines those challenges and explores ways to improve the adoption, usability, and continued use of SAST. First, a literature review of 89 research works related to SAST implementation and continued usage identifies recurring developer concerns, including false positives and other usability barriers that can reduce trust in SAST results. Second, the thesis presents a process for a…

Original text(via arXiv cs.SE)

Computer Science > Software Engineering

Title:On Improving the Adoption, Usability, and Retention of Static Application Security Testing (SAST) Tools

Abstract:As the Internet connects more of the world, software vulnerabilities create growing security risks. Because software developers are responsible for building and maintaining secure applications, they rely on tools and techniques that help identify vulnerabilities early in development. Static Application Security Testing (SAST) tools analyze source code to identify potential security weaknesses before software is deployed. Although SAST can help developers address vulnerabilities proactively, these tools also present usability and adoption challenges. This thesis examines those challenges and explores ways to improve the adoption, usability, and continued use of SAST. First, a literature review of 89 research works related to SAST implementation and continued usage identifies recurring developer concerns, including false positives and other usability barriers that can reduce trust in SAST results. Second, the thesis presents a process for automating the execution of SAST tools and formatting their output so that findings are more meaningful and actionable to developers. A real-world use case evaluates an implementation of this process and gathers developer feedback. Participants reported satisfaction with several aspects of the process and indicated that it increased their willingness to use the SAST tool.
Comments:56 pages, 8 figures. M.S. thesis in Cybersecurity, Montana State University
Subjects:Software Engineering (cs.SE) ; Cryptography and Security (cs.CR)
ACM classes:D.2.5; K.6.5
Cite as:arXiv:2611.21621 [cs.SE]
(or arXiv:2611.21621v1 [cs.SE] for this version)
https://doi.org/10.48550/arXiv.2611.21621 arXiv-issued DOI via DataCite (pending registration)

Submission history

Access Paper:

  • HTML (experimental)

Additional Features

  • Audio Summary

Current browse context:

References & Citations

  • Google Scholar
  • Semantic Scholar

BibTeX formatted citation

Bookmark

Bibliographic and Citation Tools

Code, Data and Media Associated with this Article

Demos

Recommenders and Search Tools

arXivLabs: experimental projects with community collaborators

arXivLabs is a framework that allows collaborators to develop and share new arXiv features directly on our website.

Both individuals and organizations that work with arXivLabs have embraced and accepted our values of openness, community, excellence, and user data privacy. arXiv is committed to these values and only works with partners that adhere to them.

Have an idea for a project that will add value for arXiv's community? Learn more about arXivLabs.

The text above was extracted automatically from the source page and may miss images, tables or code blocks. The original is authoritative.

Published by arXiv cs.SE
This site only summarises and aggregates; copyright stays with the original author. Headlines and summaries follow the source — where they differ, the original wins.
Read the original ↗