Difference between revisions of "Java leading security practice"

From OWASP
Jump to: navigation, search
(Introduction)
(Class Access)
Line 10: Line 10:
 
#Fields
 
#Fields
 
#Mutable Objects
 
#Mutable Objects
 +
 +
Put simply don't have public fields or methods in a class unless required. Every method, field, class that is not private is a potential avenue of attack. Provide accessors to them so you can limit their accessibility.
 +
 
===Initialisation===
 
===Initialisation===
 
===Finality===
 
===Finality===

Revision as of 06:01, 15 August 2007

OWASP Code Review Guide Table of Contents

Contents


Introduction

This section covers the main Java-centric areas which are perscribed as leading security practice when developing java applications and code. So when we are performing a codfe review on some Java code we should look at the following areas of concern. Getting developers to adopt leading practice techniques gives the inherent basic security features all code should have, "Self Defending Code".


Class Access

  1. Methods
  2. Fields
  3. Mutable Objects

Put simply don't have public fields or methods in a class unless required. Every method, field, class that is not private is a potential avenue of attack. Provide accessors to them so you can limit their accessibility.

Initialisation

Finality

Scope

Inner Classes

Code Signing

Hard Coding

Archive Files

Cloneability

Serialization/Deserialization

Comparisons