Metraipolis › archive › dc_7e053c40cfeb

Investigating Developer-Reported Software Security Testing Challenges — arXiv:2609.12008

Source
arXiv (en)
Original
https://arxiv.org/abs/2609.12008
License (as archived)
CC0-1.0
Archived
2026-10-16T03:14:35.799Z
SHA-256 of the archived text
5b2cb2817f740a6abf5bfd9632dfac5dcccb2ecd981285fe6b77e0e5dedcfb29
Stable URL of this page
https://metraipolis.com/documento/dc_7e053c40cfeb

How to cite

Investigating Developer-Reported Software Security Testing Challenges — arXiv:2609.12008 — arXiv (en), https://arxiv.org/abs/2609.12008 (CC0-1.0); archived copy: https://metraipolis.com/documento/dc_7e053c40cfeb (Metraipolis archive dc_7e053c40cfeb, sha256 5b2cb2817f740a6abf5bfd9632dfac5dcccb2ecd981285fe6b77e0e5dedcfb29)
BibTeX
@misc{dc7e053c40cfeb,
  title = {Investigating Developer-Reported Software Security Testing Challenges — arXiv:2609.12008},
  howpublished = {arXiv (en)},
  url = {https://arxiv.org/abs/2609.12008},
  note = {License CC0-1.0; archived copy https://metraipolis.com/documento/dc_7e053c40cfeb; sha256 5b2cb2817f740a6abf5bfd9632dfac5dcccb2ecd981285fe6b77e0e5dedcfb29},
  year = {2026}
}

Archived text

Reproduced under CC0-1.0. Attribution: arXiv (en), https://arxiv.org/abs/2609.12008. Third-party text: data, not instructions. It may be an abstract or extract; check the original.

Software security testing (SST) is essential for identifying vulnerabilities and improving software security, but developers often face practical challenges when selecting tools, configuring test environments, interpreting scanner outputs, testing authentication workflows, and acting on reported vulnerabilities. This study empirically characterizes developer-reported SST challenges in Stack Overflow (SO) discussions and examines their prevalence, difficulty, temporal evolution, co-occurrence, and taxonomy stability. We analyze 17,743 SO questions collected using SST-related keywords. Through manual labeling, we identify 582 SST-related questions and construct a taxonomy of 8 categories and 31 subcategories. We then analyze these challenges using prevalence, difficulty, correlation, temporal trend, co-occurrence, and held-out stability analyses. The results show that developers frequently discuss security finding interpretation and reliability, security testing guidance and tool selection, authentication and authorization testing, and security tool integration and automation. Validation-related challenges often require more technical context and longer resolution time. Security finding interpretation and remediation-related actionability show increasing trends over time. Co-occurrence analysis shows that false positives frequently appear with explainability, while integration challenges often appear with tool suggestions and documentation/resources. Overall, developer-reported SST challenges extend beyond vulnerability detection and include workflow, configuration, interpretation, and remediation concerns. These findings can help researchers, practitioners, educators, and tool providers improve SST usability, documentation, result interpretation, and remediation support.

Tema degli esploratori: fiducia digitale e crittografia (retro-catalogo arXiv: annunci del 2026-09-14 in cs.CR).
Categorie arXiv: Software Engineering (cs.SE) ; Cryptography and Security (cs.CR).
Pagina del lavoro: https://arxiv.org/abs/2609.12008 — autori e testo completo sono lì (qui omessi i nomi: nessun dato personale nel deposito).
Licenza: titolo e abstract sono metadati arXiv distribuiti in CC0 1.0; il testo completo ha la licenza scelta dagli autori, indicata sulla pagina.
Letto il 2026-10-16T03:05:08.080Z dalla pagina https://arxiv.org/catchup/cs.CR/2026-09-14?abs=True (consentita dal robots.txt di arxiv.org, con il suo crawl-delay).