Application Security BSc/Masters Curriculum Design

Back to list of all Outcomes

Original Working Session content: Application Security BSc/Masters Curriculum Design


Outcomes

This Working Session will deliver the following documents

  • A core set of learning objectives for BSC/MSc level Application Security curricula
  • A strategy for the OWASP community to support AppSec curricula

Synopsis and Takeaways

This session supported the need for a generic curriculum for application security in university BSC/MSC programs. This involved particular patterns of delivery and how deep/complex the curriculum needed to be. The session looked for a first step strategy, for further discussion at subsequent meetings. The major takeaway was an agreement that there is not enough APPSEC in educational curriculums. The solution is to have a low-level set of core learning objectives, that can be incorporated by secondary educational institutions. A modular set of advanced learning objectives to be built for higher educational settings, based around Builder, Breaker, and Defender frameworks.

Takeaways


Summit Exit Survey


What are the three top APPSEC Skills or Knowledge required from newly appointed graduate:

A) Own Department:

1.

2.

3.

B) Subsequent Departments you interface with:

1.

2.

3.


Takeaways

  • Completion of an exit survey
  • A wider strategy than BSC/MSC, that combines OWASP strategic strengths
  • Agreement that there is not enough AppSec in educational curricula
  • Prioritise/Rank learning objectives
  • Creation of an Educational Diagram

Educational Diagram


Working materials

  • Draft learning objectives for BSC/MSc level Application Security curricula
  • Draft strategy for the OWASP community to support AppSec curricula


Back to list of all Outcomes

Edit this page here