Secure Coding Guidelines for Java SE
By milton smith-Oracle on Apr 17, 2014
With so much happening around the Java platform, it’s understandable if you missed the recent improvements we made to the Secure Coding Guidelines for Java SE. In January 2014 the Java Platform Group released a significant update, Java 7 Update 51 establishing code-signing as the default for Applets and Web Start applications. Following in March 2014, we hit another major milestone with the long anticipated release of Java SE 8.
There are a number of improvements to the Secure Coding Guidelines for Java SE. On the surface, the larger domains of the coding guidelines like Fundamentals and Denial of Service are the same but content has been improved throughout each domain based upon changes to Java’s threat landscape. Likewise, small but noteworthy improvements to content navigation were made to the domains in table of contents facilitating quick navigation for readers.