-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathcyberdefense_syllabus.tex
105 lines (81 loc) · 5.53 KB
/
cyberdefense_syllabus.tex
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
\documentclass{article}
\usepackage{url}
\begin{document}
\section*{Course Overview}
This course is intended for students who are interested in cybersecurity and especially for those who are preparing for PRCCDC (the Pacfic Rim Collegiate Cyber Defense Comptetition). Students taking this course are expected to be self-motivated and interested in learning, with the ability to research a given topic and share their knowledge with others. Class this semester will involve hands-on tutorials involving basic hardening, attack, and defense skills on Windows and *Nix based operating systems.\\
Classes will be held in JEB 006, RADICL, at (time?).
\section*{Course Objective}
Over the semester, students will have an opportunity to practice researching and presenting on assigned topics that are relevant to PRCCDC, with the highly encouraged option to include more information as they find it useful and interesting. This is a student directed course with the purpose of competing well at PRCCDC, but prior knowledge is not necessary as this semester is targeted at raising every student's knowledge to the level at which we hope to compete.\\
***We reserve the right to select teams based on criteria including but not limited to: skill, area of skill, experience, attendance, team cohesion, etc.***
\section*{Grading}
\begin{tabular}{l l}
Attendance & 60\% \\
Discussion & 10\% \\
Tutorials & 30\% \\\\
\end{tabular}
\noindent Attendance at 80\% of classes or more is required if you are taking this class for two credits. Understanding that students have many priorities, the expectation is that if you make a reasonable effort to attend every class and communicate if you have a conflicting commitment. Attendance is also an important factor in team selection, although you can miss up to three classes before it starts affecting your eligibility to compete. Also, attending Cyber Defense Club (CDC@UI) can be done to make up for absences. \\
\noindent Discussion will involve sharing current events at the beginning of class. Good sources for news are:\\\\
\begin{tabular}{l l}
YCombinator Hacker News & \url{https://news.ycombinator.com/news?p=1} \\
ArsTechnica & \url{https://arstechnica.com/information-technology/} \\
Wired & \url{https://www.wired.com/category/security/} \\
Twitter & (depending on who you follow)
\end{tabular}\\\\
Please bring a printed summary of the news event you're planning to discuss.\\
\noindent Tutorials will be assigned and chosen at the beginning of the semester. A template with specific expectations will be given, which you are expected to follow in order to receive full credit. In the process of preparing for tutorials, you may find the following resources helpful: \\\\
\begin{tabular}{l l}
Cyberdefense Github & \url{https://github.com/GhostofGoes/ui-prccdc} \\
%Windows Command Line & \url{https://github.com/Awesome-Windows/awesome-windows-command-line}\\
%msdn
... & ...\\
\end{tabular}\\
Tutorials should be submitted at least two days prior to the presenation date. ?A student will be assigned to read through the tutorial and prepare five or more questions on the material.? The student presenting will then create a writeup afterwards to be submitted within five days.
\section*{Topics}
\begin{itemize}
\item How to research and find good resources
\item Presenting effectively
\item Commonly used acronyms
\item Nmap and making a network map
\item Persistence (sticky keys, scheduled tasks)
\item Windows firewall (basic rules that should \& shouldn't be there, not locking yourself out by denying RDP)
\item Windows command line
\item Powershell
\item Windows task manager and common tasks (detecting an intruder)
\item Sysinternals (autoruns, process explorer)
\item Group policy and active directory
\item Layer 7 firewalls (Palo Alto)
\item Layer 3 firewalls (VyOS, pfSense)
\item Bash fundamentals
\item Bash scripting
\item *nix variants and how they differ: FreeBSD, Solaris, Linux, etc.
\item Linux directory structure and contents
\item Cron
\item Networking \& the OSI model
\item IPv4 addressing
\item NAT rules
\item Git (for template, syllabus, etc, for next class and hold previous classes also, persistence over time)
\item ...
\end{itemize}
\section*{Schedule}
Quarter 1: Introduction, common acronyms and terminology, overview of PRCCDC and motivation for why and how we're preparing, expectations such as presentation templates, grading, goals, how to ask \emph{good} questions and precisely articulate problems, review of previous competitions, resources that are available, and overview of semester schedule\\
\noindent Presentations for beginning of class (by class leadership).
\noindent Quarter 2: Windows fundamentals\\\\
Quarter 3: Linux fundamentals\\\\
Quarter 4: Networks and domains? \\\\
\noindent In more detail: 15 weeks, 30 classes:\\
\noindent Week 1, Day 1: Syllabus, time, expectations, overview of course (emphasis on quality over quantity)\\
What is the competition, expectations of tema members, etc\\
Intro to course and competition \\\\
Week 1, Day 2: Understanding a virtual environment and how to set up responsibly at home\\
Assign first presentations\\
Explain terminology (ISO, checksum, etc.)\\
\noindent 1st half of semester: 2 news per day (10 min), 2 tutorials (35 min per)\\
30 slides, 1 min for each\\
Two people per presentation first round\\
\noindent 2nd half: 1 tutorial\\
One person presents\\
\noindent Week 2:\\
\noindent Intro Windows\\
Intro Linux\\
Networking/OSI Model\\
\end{document}