Secure Code Training 2016

Introduction

This document has been prepared to show the agenda of Secure Coding Training (SCT) that will be held probably on February by SA4T1 experts. The venue is to be determined.

Contact person: the main contact person for this issue is currently Gerard Frankowski, PSNC – gerard.frankowski@man.poznan.pl.

Experts

Currently we have the following experts (sorted alphabetically):

• Paweł Berus (PSNC) – referred as PB
• Łukasz Czarniecki (PSNC) – referred as ŁC (not talking in person but prepares some input)
• Gerard Frankowski (PNSC) – referred as GF
• Maciej Miłostan (PSNC) – referred as MM (not talking in person but prepares some input)
• Tomasz Nowak (PSNC) – referred as TN

Agenda

General information

The agenda bases upon previous SCT agendas (it was assumed no significant changes should occur). The updates to that schedule has been made basing on the following factors:

• The feedback collected from SCT 2014
• The need to introduce more practical parts and interaction

The proposed updates are as follows:

1. Agenda changes
   1. Removing the “Summer School 4 Developers” slot from the Session 1. The SS4D has already been conducted, and the next one will be much later. Anyway, a short notification about SS4D will be presented in the introduction as a part of SA4 activities.
   2. Extending the “How we support building secure MDS Tools” in Session 1. Additional information will be provided about a non-security part of SA4 portfolio, e.g. quality audit. This input will be supported by some other person from SA4 and presented by one of the SCT experts.
   3. Adding “Data sanitization – meaning and techniques” presentation to Session 1. It will be based on the presentation shown several years ago but extended – including a fine example with insufficient black list filtering from one of the performed external audits. Basing on the most recent GN3+/GN4 source code reviews, it is assumed as a fundamental topic for the developers and would be the first really deep, technical slot. An additional exercise will be prepared, dealing with building regular expressions (the presentation will be extended, comparing to the early SCT version).
   4. Prolonging the slots that are left intact in the Session 1 with 5-10 minutes each, taking into account that there should be more interaction with the attendees through these slots.
   5. Rebuilding the Web secure programming workshop. It will be completely redesigned an rebuild and will take (together with HackMe contest) the whole day (Session 2-3). OWASP Top 10 vulnerabilities will be covered – each type with the introduction and practising. The practical part may be to some extent adjusted to programming language preferences of attendees. Additionally several topics will be incorporated, that were earlier separate, more theoretical, presentations. These topics will be removed some theory and adjusted to the general contents of the workshop in order to produce smooth and consistent material.
      1.                                           i.    Encoding issues (from Session 3)
      2.                                          ii.    Secure programming in PHP (from Session 1)
      3.                                         iii.    Avoiding filesystem problems in the source code (from Session 3)
      4.                                         iv.    Does the CMS help in increasing security? OWASP Top 10, Python and Django (from Session 4)
      5. Moving the „Java encapsulation and object mutability – workshop” from Session 3 to the end of Session 1 – in order to finish the first day with a purely practical element and be more consistent with Web secure programming topics through the Sessions 2-3.
      6. Removing the “Avoiding filesystem problems in the source code” presentation from Session 3, basing on the survey feedback (Don't spend so much time on attack scenarios where the attacker already has access to the machine as in the Geant environment that will most likely not be the case.). However, some part of the content will be redesigned and moved to the Session 2-3 to the Web secure programming workshop (race conditions in Web applications).
      7. Adding an additional short code analysis workshop “From riddle to Heartbleed – catch the bug!” (Session 4) People wished more work with the source code – it will be mainly handled by the Secure Web programming workshop, but this is the place for e.g. some interesting bugs in non-Web languages. There will be code snippets containing security bugs especially crafted by the experts, but also there will be shown well known bugs (like Heartbleed) and the vulnerable place will be looked for in the source code.
      8. Extending the review of source code analysis tools with extra applications in Session 4. The additional tools will be e.g. for reviewing PHP code, but to some extent it is possible to adjust the set of tools basing on the attendees programming language preferences from the registration form). The SCT 2014 attendees expressed interest for being shown more tools.
2. Changes not directly reflected in the agenda or not concerning the contents themselves.
   1. Refreshing the workshop material with the most recent state-of-the-art.
   2. Analysis of the material whether it is still possible to remove some text from the slides or even the whole slides.
   3. Minor changes to breaks – in order to not make breaks between similar slots, but rather in the place where the topic significantly changes.

This version of the agenda may slightly be adjusted during the SCT as the interaction between the experts and the participants is of the greatest value and if the participants have more questions than expected, particular slots may be prolonged a bit and others may be shortened.

There are 4 sessions that will be handled 1-2-1 per day. Each session lasts between 3 hours – 4 hours and 15 minutes (including short breaks within the sessions). Especially the sessions 2 and 3 plus a bit longer lunch break make the whole day. There will be no parallel sessions. Particular basic programming skills will be required from the participants.

The changes made to the agenda (see the next 4 chapters) are formatted as below:

New content – with bold font

Significantly updated content – with underlined font

Session 1 (Day 1 Oct 13:00 – 17:00)

Session 2 (Day 2, 9:00 – 12:30)

Session 3 (Day 2, 13:30 – 17:00)

Session 4 (Day 3, 9:00 – 13:00)

Points to be discussed

• Registration
• Feedback
• Extra topics