From 48ff96a458af4e3c41a96a56c9f16a9d0ab67d76 Mon Sep 17 00:00:00 2001 From: Marco Squarcina Date: Mon, 21 Oct 2019 17:10:26 +0200 Subject: [PATCH] added guidelines for talks and writeups --- README.md | 12 +++++++++++- 1 file changed, 11 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index b6b1947..21cabfd 100644 --- a/README.md +++ b/README.md @@ -49,4 +49,14 @@ Please submit your write-up within 2 weeks after the end of the CTF. Talks ----- -TBA \ No newline at end of file +As part of the evaluation process you are also required to present the solution to a CTF challenge in one of the scheduled meetings. The presentation can be done either individually or as a team of 2 persons. Students teaming up are expected to present more complex challenges than those handled individually. The expected duration of the talk is defined as: +* 15 minutes for individual presentations +* 30 minutes for team presentations (15 minutes each student) + +To book a slot for your talk in one of the meetings listed in the "Tentative Schedule", go to [TISS](https://tiss.tuwien.ac.at/education/course/groupList.xhtml?dswid=9829&dsrid=944&courseNr=192092&semester=2019W) and register in one of the available groups. Keep in mind anyway that there is a limited amount of slots per day, so start booking yours in one of the earliest dates if possible! TO get it approved, send a mail to [ctf@secpriv.tuwien.ac.at](mailto:ctf@secpriv.tuwien.ac.at) to propose a challenge you would like to discuss along with the chosen date. + +Some recommendations for your talk: +* Provide an overview of the intended functionalities of the application +* Describe all the attempts you made to find the vulnerabilities, including unsuccessful ones (time permitting) +* Explain the exploitation steps in an understandable manner +* If possible, describe the impact of this security threat in a realistic scenario and discuss possible countermeasures \ No newline at end of file -- 2.43.0