J2EE Security for Architects

Deadline for first draft:

19/08/2006

Deadline for first review:

26/08/2006

Deadline for final draft:

11/09/2006

Deadline for final review:

20/09/2006

Design considerations

Objective:

Discuss the security implications of common J2EE architectures. This could be discussed in terms of: Authentication, Authorisation, Data Validation, Cross Site Scripting protection. Other architecture concerns such as scalability, performance and maintainability can also be mentioned, but the focus on security should not be lost.
Any other security concerns that should be addressed during the design phase should also be mentioned here.

Contributors:

Reviewers:

Architectural considerations

EJB Middle tier

Web Services Middle tier

Spring Middle tier

Noteworthy Frameworks

Objective:

Discuss important and relevant Java security frameworks that would be useful to architects. The information should be at a suitably high level, for example, by discussing the advantages and features as well as the associated costs (direct and indirect) of using the frameworks.

Contributors:

Reviewers:

Acegi

Commons validator

jGuard

Stinger seems to be parked for a while now, is this correct Jeff?

Stinger is

CVS HEAD is in a functional state; needs work on docs and new features Roman 00:15, 13 June 2006 (EDT)

Most web tier frameworks will prevent XSS attacks, so listing them all in this section is a bit verbose, would prefer to see them listed in the XSS section. --Stephendv 08:04, 12 June 2006 (EDT)

I think Struts should be covered too - Rohyt

Struts is important as a web framework, but there are many frameworks that provide the same functionality from a security point of view. I think it makes sense to discuss struts as a web framework in section on XSS below with the other popular web frameworks rather than give it a special place in this section which only covers security specific frameworks. --Stephendv 07:22, 18 June 2006 (EDT)

J2EE Security for Developers

Deadline for first draft:

19/08/2006

Deadline for first review:

26/08/2006

Deadline for final draft:

11/09/2006

Deadline for final review:

20/09/2006

Java Security Basics

Objective:

Provide an introduction into the basic security services provided by the Java language and environment. Remember to keep this relevant for web developers for the initial release - there may be a potential to expand this to thick clients in subsequent releases.

Contributors:

Reviewers:

Class Loading

Bytecode verifier

The Security Manager and security.policy file

Input Validation

Overview

SQL Injection

Objective:

Provide cursory background information on SQL injection and refer to the Guide for more indepth coverage (no need to duplicate info in the Guide). This section should provide practical advise and real-world code examples for developers. If you feel that a popular persistence framework is not covered, please add it!

Contributors:

Reviewers:

Overview

Prevention

White Listing

Prepared Statements

Stored Procedures

Hibernate

Ibatis

Spring JDBC

EJB 3.0?

JDO?

Cross Site Scripting (XSS)

Objective:

Provide cursory background information on XSS and refer to the Guide for more indepth coverage. This section should provide practical advise and real-world code examples for developers. If you would like to see coverage of a web framework that's not listed, please add it!

Contributors:

Reviewers:

Overview

Prevention

White Listing

Manual HTML Encoding

Preventing XSS in popular Web Frameworks

JSP/JSTL

Struts

Spring MVC

Java Server Faces

WebWork

Wicket

Tapestry

CSRF attack

LDAP Injection

Objective:

As with the other Injection sections, only provide cursory information on the general case. Should contain practical real-world advise and code examples for preventing LDAP injection.

Contributors:

Reviewers:

Overview

Prevention

XPATH Injection

Objective:

As with the other Injection sections, only provide cursory information on the general case. Should contain practical real-world advise and code examples for preventing XPATH injection.

Contributors:

Reviewers:

Overview

Prevention

Miscellaneous Injection Attacks

Objective:

Should contain practical real-world advise and code examples.

Contributors:

Reviewers:

HTTP Response splitting

Command injection - Runtime.getRuntime().exec()

Authentication

Objective:

Discuss authentication for Java and J2EE apps under the suggested headings below. Examples for container managed authentication of specific application servers are also welcome.

Contributors:

Reviewers:

Storing credentials

Hashing

SSL Best Practices

CAPTCHA systems (such as jcaptcha)

Container-managed authentication with Realms

JAAS Authentication

Password length & complexity

Session Management

Objective:

The generic problems and solutions for session management are covered in the Guide. This section should focus on Java specific examples.

Web application forensics and how it differs from conventional forensics. This will emphasize the importance of appropriate exception handling and logging - Rohyt

Web Services Security

Objective:

Discuss securely implementing Web Services using Java technologies. Examples using specific frameworks are welcome. The topic list is a bit light at the moment, please add more topics if they're relevant.

Contributors:

Reviewers:

SAML

WS-Security

...?

Code Analysis Tools

Objective:

The introduction should cover the advantages and short comings of code analysis tools. An overview of the current state of the art and the available tools would go well here. As a start, only open source tools are listed, but if vendors of commercial tools adhere to the Contributing to the OWASP Java project guidelines, these submissions will be gladly received.

Contributors:

Reviewers:

Introduction

FindBugs

Creating custom rules

PMD

Creating custom rules

JLint

Jmetrics

J2EE Security For Deployers

Securing Popular J2EE Servers

Securing Tomcat

Securing JBoss

Securing WebLogic

Securing WebSphere

Securing x...

Would be nice to include an example secure by default configuration file for each server that has additional comments in it which expands on the security repurcussions of the various sections.