This site supports the development of coding standards for commonly used programming languages such as C, C++, Java, and Perl, and the Android™ platform. These standards are developed through a broad-based community effort by members of the software development and software security communities.
For more information about this project and to see tips on how to contribute, please see the Development Guidelines.
The following development areas enable you to learn about and contribute to secure coding standards for commonly used programming languages C, C++, Java, and Perl. Contact us to comment on existing items, submit recommendations, or request privileges to directly edit content on this site.
The Android robot is reproduced or modified from work created and shared by Google and used according to terms described in the Creative Commons 3.0 Attribution License.
Android is a trademark of Google Inc.
December 2016: The Fall 2016 Edition of the newsletter was published on 9 December 2016.
November 2016: Will Klieber, Will Snavely, and David Svoboda each present at SecDev 2016.
September 2016: Aaron Ballman writes in the SEI Blog about newly developed rules for Secure Coding in C++11 and C++14.
September 2016: David Svoboda presents Common Exploits and How to Prevent Them at the Secure Coding Symposium.
September 2016: Summer 2016 Edition of the newsletter is published.
August 2016: Watch Bob Schiela and Mark Sherman talk about adopting Secure Coding on the From Secure Coding to Secure Software webinar, recorded August 17.
August 2016: The Secure Coding in Java certificate program becomes available.
The Secure Coding eNewsletter provides timely information about CERT secure coding standards.
The Fall 2016 Edition of the newsletter was published on 9 December 2016.
The Top 10 Secure Coding Practices provides some language-independent recommendations.
The CERT Secure Coding Style Sheet provides guidance on writing about the Secure Coding Initiative.
Visit the the Secure Coding section of the CERT website for the latest publications written by the Secure Coding team.
Contact us if you