Guidelines
Security
This chapter contains guidelines that are concerned specifically with ensuring security of Java-based applications. They are concerned with issues such as
- Dealing with sensitive data.
- Avoiding common injection attacks.
- Language features that can be misused to compromise security.
- Details of Java's fine-grained security mechanism.
| Content by Label | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Defensive Programming
This chapter contains guidelines for defensive programming. Defensive programming is carefully guarded programming that helps you to construct reliable software by designing each component to protect itself as much as possible, for example, by checking that undocumented assumptions remain valid [Goodliffe 2006]. These guidelines address areas of the Java language that can help to constrain the effect of an error or help to recover from an error.
| Content by Label | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
Best Practices
This chapter includes guidelines that
- Are essential for ensuring correctness of Java code.
- Contain specific, implementation-level Java coding advice.
- Have a higher normative requirement than the defensive programming category.
The guidelines deal with generally low-level Java language features that can easily be misused by the unwary.
| Content by Label | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
|
Program Understandability
Program understandability is the ease with which the program can be understood—that is, the ability to determine what a program does and how it works by reading its source code and accompanying documentation [Grubb 2013]. Another term used to describe this property of source code is readability. Understandable code is easier to maintain because software maintainers are less likely to introduce defects into code that is clear and comprehensible. Understandability helps in manual analysis of source code because it allows the auditor to more easily spot defects and vulnerabilities.
The guidelines in this chapter are mainly stylistic in nature; they will help a Java programmer to write clearer, more readable code.
| Content by Label | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Language Misconceptions
Programmer Misconceptions
This chapter contains guidelines that address
- Misconceptions about Java APIs and language features.
- Assumptions and ambiguity-laced programs.
- Situations in which the programmer wanted to do x but ended up doing y.
They address areas where developers often make unwarranted assumptions about how Java works or where ambiguities can easily be introduced.
| Content by Label | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|