Skip to content

Secure Coding Standards and Checking Compliance

Mihály Dobos-Kovács edited this page Oct 13, 2020 · 4 revisions

Secure Coding Standards

As security is of paramount importance in this project, we define the secure coding standards the implementations should follow.

Server side

As the server side will be developed in Java, the secure coding standard followed during development should be the SEI CERT Oracle Coding Standard for Java.

The standard governs various aspects of the code, and ultimately

leads to higher quality systems that are safe, secure, reliable, dependable, robust, resilient, available, and maintainable and can be used as a metric to evaluate source code for these properties (using manual or automated processes). [source]

Native component

The server side will be implemented in C. The secure coding standard we decided to follow will be the SEI CERT C Coding Standard.

The standard deals with the security aspects of the low level C code, and its main goal

is to develop safe, reliable, and secure systems, for example by eliminating undefined behaviors that can lead to undefined program behaviors and exploitable vulnerabilities. [source]

Client side

The client side application will be an Android application, so the secure coding standard we decided upon will be the Android Secure Coding Standard.

The standard contains rules for both language and API usage, and its goal

is to develop safe, reliable, and secure systems, for example by eliminating undefined behaviors that can lead to undefined program behaviors and exploitable vulnerabilities. [source]

Clone this wiki locally