Revision as of 16:35, 6 June 2025 edit Headbomb (talk \| contribs) Edit filter managers, Autopatrolled, Extended confirmed users, Page movers, File movers, New page reviewers, Pending changes reviewers, Rollbackers, Template editors 472,932 edits Altered template type. Add: chapter-url, isbn, chapter, title. Removed or converted URL. \| Use this tool. Report bugs. \| #UCB_Gadget ← Previous edit		Revision as of 00:57, 8 June 2025 edit undo 125.63.31.244 (talk) "long out" does not mean anything Next edit →
Line 251: ==SAST weaknesses== Even though developers are positive about the usage of SAST tools, there are different challenges to the adoption of SAST tools by developers.<ref name="auto"/> The usability of the output generated by these tools may challenge how much developers can make use of these tools. Research shows that despite the long ~~out~~output generated by these tools, they may lack usability.<ref>{{cite book \|last1=Tahaei \|first1=Mohammad \|last2=Vaniea \|first2=Kami \|last3=Beznosov \|first3=Konstantin (Kosta) \|last4=Wolters \|first4=Maria K \|title=Proceedings of the 2021 CHI Conference on Human Factors in Computing Systems \|chapter=Security Notifications in Static Analysis Tools: Developers' Attitudes, Comprehension, and Ability to Act on Them \|date=6 May 2021 \|pages=1–17 \|doi=10.1145/3411764.3445616\|isbn=9781450380966 \|s2cid=233987670 \|url=https://www.research.ed.ac.uk/en/publications/e1bc04ef-ae83-4e82-8ade-ca572bc503d2 }}</ref> With Agile Processes in software development, early integration of SAST generates many bugs, as developers using this framework focus first on features and delivery.<ref>

Static application security testing: Difference between revisions