OWASP Hackademic Challenges Project

=Main=



{| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |-
 * valign="top" style="border-right: 1px dotted gray;padding-right:25px;" |

Introduction
The OWASP Hackademic Challenges Project helps you test your knowledge on web application security. You can use it to actually attack web applications in a realistic but also controllable and safe environment.

Download the old version (v.0.1.1) from Google Code.  the Latest Version is on GitHub.

 Developers checkout the  Development Branch.

''' The servers are down due to changes in the Uni's datacenter, it will be up soon. '''

 Live version in Greek language (includes additional challenges): http://hackademic1.teilar.gr/gr 

 You can also challenge yourself using the live version hosted here: http://hackademic1.teilar.gr/ 

Description
The Hackademic Challenges implement realistic scenarios with known vulnerabilities in a safe, controllable environment. Users can attempt to discover and exploit these vulnerabilities in order to learn important concepts of information security through the attacker's perspective.

Currently, there are 10 web application security scenarios available.

You can choose to start from the one that you find most appealing,although we suggest to follow the order presented on the first page.We intend to expand the available challenges with additional scenarios that involve cryptography, and even vulnerable systems implemented in download-able virtual machines.

Target Group
Anyone can use the OWASP Hackademic Challenges to test one's knowledge and skills.

Nevertheless, the OWASP Hackademic Challenges have been mainly developed to be used in a live classroom environment. Experience has shown increased interest and engagement from students that actually get to practice application security and see how things work in a realistic environment.

Currently they are successfully used in the security courses of the following universities:


 * TEI of Larissa (Hosting Institute)
 * University of Piraeus
 * University of Athens
 * University of Macedonia
 * TEI of Thessaloniki
 * Add your university/educational institution here - [mailto:hackademic@owasp.gr Contact us] if you are using or want to use OWASP Hackademic Challenges in your class.

Deployment
The OWASP Hackademic Challenges can be easily deployed to any PHP-capable web server running mysql/mariadb.

Current deployments (http://hackademic1.teilar.gr/) have integrated the OWASP Hackademic Challenges with well-known CMS software (e.g. Joomla) in order to provide a complete e-learning environment, where students can register and monitor their progress as they go through the challenges.

Contact
OWASP Hackademic Challenges project Mailing List mailing list. Irc Channel #hackademic-dev on freenode

Licensing
OWASP Hackademic Challenges Project is free to use. It is licensed under the Apache License V2.0


 * valign="top" style="padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;" |

What are Hackademic Challenges?
OWASP Hackademic Challenges Project provides:


 * The Hackademic Challenges is an open source project that can be used to test and improve one's knowledge of web application security.
 * The Hackademic Challenges project implements realistic scenarios with known vulnerabilities in a safe, controllable environment. Users can attempt to discover and exploit these vulnerabilities in order to learn important concepts of information security through the attacker's perspective.
 * They have been especially designed for use in a classroom environment where they have been proved a valuable educational tool. Using hackademic challenges students have the chance to experience application security in a realistic environment, something that triggers their interest and provokes a lot of interesting discussions.
 * The Hackademic Challenges are currently used in several Universities and have received very positive feedback from both professors and students.

Project Leaders
[mailto:konstantinos@owasp.org Konstantinos Papapanagiotou] [mailto:spyros.gasteratos@owasp.org Spyros Gasteratos]

[mailto:venieris@owasp.gr Andreas Venieris (Core Developer) (Founder)]

Ohloh

 * valign="top" style="padding-left:25px;width:200px;" |

Quick Download
Download

Email List

 * mailing list

Classifications

 * }

=FAQs=

= Acknowledgements =

Volunteers
The Hackademic Challenges are developed by a worldwide team of volunteers. The primary contributors to date have been:


 * [mailto:alpapanik@owasp.gr Alex Papanikolaou]


 * [mailto:vsvlachos@owasp.gr Vasileios Vlachos]


 * [mailto:anast@owasp.gr Anastasios Stasinopoulos]


 * [mailto:spyros.gasteratos@owasp.org Spyros Gasteratos]


 * [mailto:konstantinos@owasp.org Konstantinos Papapanagiotou]
 * Fotis Liatsis
 * Petros Andreou
 * Antonis Manaras
 * Daniel Kvist
 * The GSoC students and everyone who's using, or contributing on our github page

Others

 * xxx
 * xxx

= Road Map and Getting Involved =

We maintain an up to date list of open issues on the platform on our issues page on github here

For a list of features we would like implemented you can see either the issues page or our Google Summer Of Code ideas page

Involvement in the development and promotion of the Hackademic Challenges is actively encouraged! You do not have to be a security expert in order to contribute. Some of the ways you can help:
 * Write Documentation
 * Write Unit tests
 * Develop themes and plugins
 * Write Challenges or Articles or contribute security courses

=Student Programs=

In Hackademic we're participating in most of OWASP code sprints and any external ones we can. The purpose is to advertise the platform, attract contributors, get some code and also help students learn new things and perhaps learn a couple of new stuff ourselves.

Students and mentors participating in code sprints are instructed to join in the irc channel to make coordination and answering question easier. Moreover, students have to provide weekly reports and merge requests according to our coding standards.

Scoring
For potential mentors scoring student proposals we suggest that they use the following template. Of course mentors can choose to take other factors into consideration as well.


 * Project Contributor 20%
 * Has gotten in contact with a mentor or the team and is responsive 10%
 * OWASP contributor 10%
 * The student's proposal demonstrates that they have knowledge of the matter they discuss and are able to complete the project. 20%
 * The proposal mentions the tools to be used and shows understanding of the tools involved 20%
 * Proposal includes a timeline that makes sense 20%
 * The student's cv/bio show prior relevant experience or the ability to learn quickly 10%

Note that the score amounts to 110%

=Project About=