Proceedings of the 2008 Workshop on Static Analysis 2008
DOI: 10.1145/1394504.1394506
|View full text |Cite
|
Sign up to set email alerts
|

Securing Java code

Abstract: A secure coding standard for Java does not exist. Even if a standard did exist, it is not known how well static analysis tools could enforce it. In this work, we show how well eight static analysis tools can identify violations of a comprehensive collection of coding heuristics for increasing the quality and security of Java SE code. A new taxonomy for correlating coding heuristics with the design principles they help to achieve is also described. The taxonomy aims to make understanding, applying, and remember… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1

Citation Types

0
1
0

Year Published

2013
2013
2022
2022

Publication Types

Select...
3
1
1

Relationship

0
5

Authors

Journals

citations
Cited by 19 publications
(1 citation statement)
references
References 12 publications
0
1
0
Order By: Relevance
“…Based on the literature presented in this study, we have the following observations: (i) the field has witnessed significant research work relating to bug detection using ASAT, (ii) most of these studies are focused on evaluating the effectiveness of the tools using the standard evaluation metrics such as the number of warning 17 false positives, 36 coverage, 37 (iii) to the best of our knowledge, the evaluations are usually performed based on C/C++ source code, (iv) also, some of the tools are based on the extension of the existing tools, (v) again, there are a limited number of studies in relation to the analysis of Java source code. For instance, we noticed from our review that there are only about three studies, namely, the work presented by Ware and Fox, 38 Flanagan et al, 39 and Livshits 40 that empirically verified the effectiveness of the static application security testing tools based on Java source code files. Ware and Fox conducted a comprehensive report on the effectiveness of eight static analysis tools in relation to detecting security‐related flaws and defects in Java code.…”
Section: Related Workmentioning
confidence: 95%
“…Based on the literature presented in this study, we have the following observations: (i) the field has witnessed significant research work relating to bug detection using ASAT, (ii) most of these studies are focused on evaluating the effectiveness of the tools using the standard evaluation metrics such as the number of warning 17 false positives, 36 coverage, 37 (iii) to the best of our knowledge, the evaluations are usually performed based on C/C++ source code, (iv) also, some of the tools are based on the extension of the existing tools, (v) again, there are a limited number of studies in relation to the analysis of Java source code. For instance, we noticed from our review that there are only about three studies, namely, the work presented by Ware and Fox, 38 Flanagan et al, 39 and Livshits 40 that empirically verified the effectiveness of the static application security testing tools based on Java source code files. Ware and Fox conducted a comprehensive report on the effectiveness of eight static analysis tools in relation to detecting security‐related flaws and defects in Java code.…”
Section: Related Workmentioning
confidence: 95%