Revision as of 13:30, 16 September 2023 edit Götz (talk \| contribs) Extended confirmed users, Rollbackers 4,006 edits m →SAST weaknesses: wording ← Previous edit		Revision as of 21:21, 25 October 2023 edit undo 2607:fea8:539e:5d00:bd21:4a43:1025:9812 (talk) →SAST weaknesses Next edit →
Line 247: ==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 generated by these tools, they may lack usability.<ref>{{cite journal \|last1=Tahaei \|first1=Mohammad \|last2=Vaniea \|first2=Kami \|last3=Beznosov \|first3=Konstantin (Kosta) \|last4=Wolters \|first4=Maria K \|title=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}}</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