Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 55 Next »

MAINTENANCE NOTICE (UPDATE - 23 October 2017)

On 24 October 2017, we will be performing maintenance on this wiki between 7:59pm - 9:00pm EDT (23:59 UTC - 01:00 UTC 25 October 2017).  Access during this period may be limited. The maintenance is to upgrade the version of the wiki. We don't expect any significant changes to the user experience based on this upgrade, and once it's complete, behavior should be the same as before (other than features and defect remediation from the update).

MAINTENANCE NOTICE:

For a few weeks beginning 23 October 2017, we will be performing occasional maintenance on this CERT Secure Coding wiki.  This is a general notification announcing our maintenance plans.

We are planning the maintenance to minimize the impact to users. There will be several phases of maintenance, and we will provide more detailed information for each phase, such as expected maintenance periods and expected impacts.  During the most significant periods of maintenance, we will provide a read-only version of the wiki, but not allow editing.  That should only affect contributors, and not the vast majority of users of the system.  

When the maintenance is complete, user accounts and histories will be retained for registered users.  But, registered users will need to reset your password through the site’s “forgot password” mechanism.  We will provide more information and instructions before and after that phase of the maintenance.

We expect all maintenance to be complete by early November.  If you have any concerns, please send email to info@sei.cmu.edu, referencing the Secure Coding wiki.

 

--

The AndroidTM rules and recommendations in this wiki are a work in progress and reflect the current thinking of the secure coding community. Because this is a development website, many pages are incomplete or contain errors. As rules and recommendations mature, they are published in report or book form as official releases. These releases are issued as dictated by the needs and interests of the secure software development community.

Create a sign-in account if you want to comment on existing content. If you wish to be more involved and directly edit content on the site, you still need an account, but you'll also need to request edit privileges. 

Front Matter

 

Rules

Recommendations

 

Contact Us

Contact us if you

  • have questions about the Secure Coding wiki
  • have recommendations for standards in development
  • want to request privileges to participate in standards development

Rules and Recommendations by Language

 

 

 

Rules vs. Recomendations

This coding standard consists of rules and recommendations, collectively referred to as guidelines. Rules are meant to provide normative requirements for code, whereas recommendations are meant to provide guidance that, when followed, should improve the safety, reliability, and security of software systems. Learn more about the differences.

Information for Editors

  • To eliminate a section from the lists above, label it section and void.
  • To have a section listed as a recommendation, label it section and recommendation.
  • To have a section listed as a rule, label it section and rule.
  • See a complete dictionary of labels to help you label your pages correctly.
  • Link to guidelines using the Tiny Link under Tools→Link to this Page... (This URL will not change if the name of the guideline changes.)  
  • Review the guidelines for writing secure coding rules/recommendations.
  • To add a new rule, follow the steps on the Guidelines for Wiki Contributors page.

 

 


The AndroidTM robot is reproduced 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.

 

  • No labels