Link Details

The CERT Secure Coding Standard for Java is a useful set of rules and recommendations that will help you write secure Java code. Problem is, whatever you write will likely be combined with legacy code, third-party components, open source or proprietary frameworks and containers and so on. How do you reduce the exposure of security vulnerabilities possibly present in the technology stack and part of the application that are not under your control?

Posted by dl113449  |   Jul 15 2010 / 15:38

Add your comment

Html tags not supported. Reply is editable for 5 minutes. Use [code lang="java|ruby|sql|css|xml"][/code] to post code snippets.

Recommended Links

Written by: Ryan Knight
Featured Refcardz: Top Refcardz:
  1. Apache Hadoop
  2. Play
  3. Akka
  4. Debugging JavaScript
  5. Design Patterns
  1. Apache Hadoop
  2. REST
  3. Java
  4. Git
  5. Java Performance
Connect with DZone