Backend
On Improving the Adoption, Usability, and Retention of Static Application Security Testing (SAST) Tools
arXiv cs.CR0 views
arXiv:2611.21621v1 Announce Type: cross 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.
Source:https://arxiv.org/abs/2611.21621PreviousAdaptive LLM-Driven Honeypots vs. LLM-Driven Attackers: Does Narrative Coherence Improve Deception?NextTIBECG: Temporal Information Bottleneck for Lead-Specific Demographic Privacy in ECG Waveform Release
Related posts
Driving the Style: Velocity-Conditioned Whole-Body Control from Motion Demonstrations
0arXiv cs.RO
sqrtVINS-Based 360 Visual-Inertial SLAM Systems: Hilti-Trimble SLAM Challenge 2026 Entry
0arXiv cs.RO
Ontology-Compiled Control Barrier Functions for Heterogeneous Robot Teams
0arXiv cs.RO
I Used to Get Attached to My Code. I Don't Anymore.
0dev.to AI
Securing MCP Servers: Preventing Shadow Tool Declarations and JSON-RPC Parameter Poisoning
0dev.to AI
How do I find out why users abandon conversations with my AI agent?
0dev.to AI