Network Security Spring 2020
Network Security explores practical elements of securing networked systems and services. The course goals are the following:
- Provide a solid understanding of the design and analysis of network security architectures, protocols, and services
- Provide an in-depth examination of contemporary network security standards and their limitations
- Provide hands-on experience in attacking and defending network services
Topics covered by this course include:
- Security foundations
- Attacks against the network stack
- Wireless security
- Naming and routing
- Distributed systems and consensus
- Privacy and anonymity
- Web security
- Class meetings are Tuesdays and Thursdays at 13:35-15:15 in 019 INV
- Office hours are 15:00-17:00 Wednesdays and 15:30-16:30 Fridays in 618 ISEC
Grades will be assigned based on the completion of assignments, quizzes, and a final project. Points will also be awarded for class participation. Grades may be subject to a curve.
Assignments will consist of programming problems. Students will have ~1-2 weeks to complete each assignment. Assignments are expected to be completed individually by each student. Late assignments will be accepted, with the caveat that grading will be penalized by a full letter grade for each 24 hour period following the submission deadline that an assignment is late. The assignment with the lowest score will be dropped from the final grade calculation.
Quizzes will be held on a weekly basis. Questions will be multiple choice and the results will be used to gauge comprehension of the material. No make-up quizzes will be held. However, the lowest two quiz scores will be dropped from the final grade calculation.
The final project will be a group effort to develop a network security-related software program or library. Groups will consist of ~4 people. Grading will be performed on the basis of project proposals, the project itself, and project presentations. Students will also have the opportunity to submit feedback on their fellow group members.
This course requires significant “programming maturity” and a solid background in computer networking. This is a consequence of the fact that security spans many domains. Moreover, not only must you know the relevant abstractions, you must know how they are implemented in order to understand how to break them. Therefore, you must have passed a networking course covering design concepts and programming APIs for IP, TCP, and UDP, at a minimum. It is virtually impossible to learn networking concepts on the fly and pass this class. If you don’t satisfy this prerequisite, you should only take this class after you have done so.
In addition, practical familiarity with the following or the ability to refer to other references and documentation for the following is also required:
- SSH: Remote login, connection tunneling
- Source control: Git
If you aren’t familiar with these technologies or are uncomfortable referring to available documentation on your own, logic and experience both dictate that you will have significant difficulty with this course.
As a concrete example for calibration purposes: If asked to write a TCP client that connects to a remote endpoint and engages in a simple binary proof-of-work protocol from a grammar-based specification, this should take on the order of a couple of hours rather than a week.
Cheating. Work submitted for grading must represent your own effort. Group work is not allowed unless specifically stated otherwise. Similarly, use of third-party content (for code, whether as a library, service, or in source form) is only permissible in the context of the allowances explicitly made as part of a problem statement. “Use” in this context refers not only to copying in the cut-and-paste sense, but any content derived from third-party work. A non-exhaustive list of plagiarism examples include:
- Copying third-party code verbatim that was published in an online source code repository, forum, or other reference site such as GitHub, GitLab, Stack Overflow, Wikipedia, or similar
- Adapting an algorithm found in third-party code published online
- Collaborating on code with other students, such as adapting code written by another student or working together on a shared code base at any point
While referring to third-party code can be helpful in devising your own solution, it is also extremely dangerous as it is all too easy to plagiarize without realizing it. (It is for exactly this reason that viewing source code published online that may be relevant to a product is almost always strictly forbidden in corporate settings due to intellectual property concerns.) While discussing course material with other students is encouraged, it is strongly recommended that students refrain from viewing any third-party source code.
Cheating damages the reputation of the university as well as the grades of students who participate in the course in good faith. As such, there will be zero tolerance for cheating in this course. Students that participate in this course must acknowledge that they have read and understood the University Academic Integrity Policy. All cheating cases will be brought to the CCIS Academic Integrity Committee and to OSCCR on the first offense. Finally, all students found to be cheating will receive a failing grade on the first offense.
Reference Material. There is no official textbook for this course. Instead, we will rely on lectures and readings. If you need to brush up on background material on algorithms, architecture, systems, or networks, strongly reconsider whether you satisfy the course prerequisites.
Due to the fast pace of the field, much information is only available online and thus referring to third-party online sources is encouraged. However, keep in mind that referring to third-party source code is permissible only within the constraints of the class and university academic integrity policies.
Online Discussion. Online discussion and questions will be handled through Slack, not via email. A best effort attempt will be made to respond to posts within 24 hours on weekdays during normal working hours. To ensure a timely response, do not wait to ask questions until the night before a submission deadline.
Ethics. This course covers sensitive material that includes information on how to exploit vulnerable software. Attack-oriented work must be restricted to the computing resources provided. Alternatively, students can perform this work using personal resources so long as other computing resources are not affected.
In particular, attacks performed against University resources or the open Internet are expressly prohibited. Students should also be familiar with the University Appropriate Use policy.
|Tue Jan 07||Introduction||Course Overview and Security Fundamentals|
|Fri Jan 10||The Network Stack||ARP and IP Attacks|
|Tue Jan 14||The Network Stack||Open Lab QUIZ|
|Fri Jan 17||The Network Stack||TCP Flooding and Hijacking|
|Tue Jan 21||The Network Stack||Intrusion Detection and Evasion QUIZ|
|Fri Jan 24||The Network Stack||Wireless Networking|
|Tue Jan 28||Authentication||Passwords QUIZ|
|Fri Jan 31||Authentication||Kerberos|
|Tue Feb 04||Core Internet Services||DNS Spoofing and Hijacking QUIZ|
|Fri Feb 07||Core Internet Services||Securing the DNS|
|Tue Feb 11||Core Internet Services||Global Routing QUIZ|
|Fri Feb 14||Core Internet Services||BGP Hijacking|
|Tue Feb 18||Transport Layer Security||TLS and PKI QUIZ|
|Fri Feb 21||Transport Layer Security||TLS Vulnerabilities and Attacks|
|Tue Feb 25||Anonymity||Onion Routing QUIZ|
|Fri Feb 28||Anonymity||Censorship|
|Tue Mar 03||-||Spring Break|
|Fri Mar 06||-||Spring Break|
|Tue Mar 10||Web Security||The Web Security Model QUIZ|
|Fri Mar 13||Web Security||TLS and HTTPS|
|Tue Mar 17||Web Security||Revisiting the Same-Origin Policy QUIZ|
|Fri Mar 20||Web Security||Browser Extensions|
|Tue Mar 24||Web Security||SQL Injection QUIZ|
|Fri Mar 27||Web Security||Web Cache Attacks|
|Tue Mar 31||Software Security||Memory Corruption QUIZ|
|Fri Apr 03||Software Security||Fuzz Testing|
|Tue Apr 07||Software Security||Behavioral Sandboxes QUIZ|
|Fri Apr 10||Final Project||Project Presentations|
|Tue Apr 14||Final Project||Project Presentations|