Welcome to CS 526 (Information Security)!

Instructor: Christina Garman (clg@purdue.edu)

TA: Farzad Zafarani (farzad@purdue.edu)

Course catalog: Basic notions of confidentiality, integrity, availability; authentication models; protection models; security kernels; secure programming; audit; intrusion detection and response; operational security issues; physical security issues; personnel security; policy formation and enforcement; access controls; information flow; legal and social issues; identification and authentication in local and distributed systems; classification and trust modeling; and risk assessment.

You should hopefully come out of this course with a broad understanding of information security, focusing on software security, network security, cryptography, mobile platform security, and privacy technologies, as well as how these security issues can impact real world systems.

Time: M/W/F 12:30pm-1:20pm
Location: Lawson 1106
Syllabus

Prerequisites:

• CS 503 - Operating Systems: I will assume that you have had this course, and you will be responsible for knowing the material even if you have not.

• Programming experience: Some of the assignments will require programming knowledge, so you should be comfortable programming.

Farzad's office hours will be TBD.
My office hours will be TBD in my office (Lawson 1185).

I will be available by appointment as well.

Expect that there to be approximately four large projects with a few small assignments mixed in and two exams (a midterm and a final), with the approximate weights as follow. Part of your grade will include a participation component, so I do expect you to attend class, participate on Piazza, etc. If you cannot make class for any reason (such as job interviews, etc.), please let me know as you will not be penalized for this.

• Projects: 55%

• Exam 1: 20%

• Exam 2: 20%

• Class participation: 5%

Assignments are due at the beginning of class at 12:30pm on the stated due date. Late assignments will be penalized 5 percentage points per day. There is no collaboration allowed on exams. You must do only your own work. There are no textbooks, notes, or computers allowed during exams.

Final grades will be assigned on a curve at the end of the course.

This schedule is subject to change.

Date	Topics	Readings
Week 1 (8/19/19)	Introduction, Threat Modeling	Reflections on Trusting Trust The Security Mindset How to Think Like a Security Professional
	Software Security	Smashing the Stack for Fun and Profit
Week 2 (8/26/19)	Software Security	Basic Integer Overflows Exploiting Format String Vulnerabilities Optional: Memory Safety Attacks and Defenses
	Malware	Optional: How to 0wn the Internet in Your Spare Time Optional: A Report on the Internet Worm
Week 3 (9/2/19)	LABOR DAY (9/2/19)
	OS Security	Optional: Android System and Kernel Security Optional: iOS Security Guide
	Access Control	Access Control: Principles and Practice
Week 4 (9/9/19)	Intro to Networking, TCP/IP	Brief History of the Internet Optional: A Look Back at "Security Problems in the TCP/IP Protocol Suite"
	Network Security (TCP/IP)	SYN Flood Attack
Week 5 (9/16/19)	Network Security (DoS, Firewalls)
	Network Security Wrap-Up (Firewalls, DNS)	An Illustrated Guide to the Kaminsky DNS Vulnerability
Week 6 (9/23/19)	Web Security (SQL Injections)	Web Security: Are You Part of the Problem? SQL Injection
	Web Security (CSRF)	Cross-Site Request Forgery Optional: Cross-Site Request Forgery (CSRF) Prevention Cheat Sheet
Week 7 (9/30/19)	Web Security (XSS)	Optional: XSS Filter Evasion Cheat Sheet
	Passwords and Authentication	User Authentication Notes
Week 8 (10/7/19)	OCTOBER BREAK (10/7/19)
	Basics of Cryptography
Week 9 (10/14/19)	Basics of Cryptography
	MIDTERM (10/16/19)	8-10pm, SMTH 118	MIDTERM
	Symmetric Cryptography	Symmetric Key Cryptography Notes
Week 10 (10/21/19)	Symmetric Cryptography
Week 11 (10/28/19)	Symmetric Cryptography, Public Key Cryptography
	Public Key Cryptography	Public Key Cryptography Notes
Week 12 (11/4/19)	Public Key Cryptography
	PKI, SSL/TLS	Optional: Lessons Learned in Implementing and Deploying Crypto Software
Week 13 (11/11/19)	SSL/TLS and Attacks [Protocols]
	SSL/TLS and Attacks [Protocols]
Week 14 (11/18/19)	Ethics, Policy, and Law	Vulnerability Disclosure Cheat Sheet Optional: Coders' Rights Project Vulnerability Reporting FAQ
Week 15 (11/25/19)	Bitcoin, Zerocoin, Zerocash, Zcash
	THANKSGIVING BREAK (11/27/19)
	THANKSGIVING BREAK (11/29/19)
Week 16 (12/2/19)	Side-Channels, Covert Channels	Optional: Lest We Remember: Cold Boot Attacks on Encryption Keys
	Security Fails, Course Wrap-Up
TBA	FINAL EXAM	TBA	FINAL EXAM

All projects will be submitted on Blackboard unless otherwise noted.

• Project 1: Due Friday September 20th, 2019 at 12:30pm

• Project 2: Due Monday October 14th, 2019 at 12:30pm

• Project 3: Due Monday November 11th, 2019 at 12:30pm

• Project 4: Due Sunday December 1st, 2019 at 11:59pm

All assignments will be submitted on Blackboard unless otherwise noted.

• Assignment 0: Due Friday December 6th, 2019 at 11:59pm (Extra Credit)

• Assignment 1: Due Monday August 26th, 2019 at 12:30pm (included in your participation grade)

There will be readings listed for each day of class pertaining to the material we will cover, and I will expect that you have at least tried to read them (though it is okay if you do not understand everything right away!).

No textbook is required, but if you would like additional resources the following may be useful:

• Security Engineering by Ross Anderson

• Computer Security: Principles and Practice, Prentice Hall, 2007. By William Stallings and Lawrie Brown.

The Department of Computer Science expects and enforces the highest standards of academic integrity and ethics. The Department takes severe action against academic dishonesty, which may include failing grades on an assignment or in a course, up to a recommendation for dismissal from the University.

Academic dishonesty is defined as any action or practice that provides the potential for an unfair advantage to one individual or one group. Academic dishonesty includes misrepresenting facts, fabricating or doctoring data or results, representing another's work or knowledge as one's own, disrupting or destroying the work of others, or abetting anyone who engages in such practices.

Academic dishonesty is not absolute because the expectations for collaboration vary. In some courses, for example, students are assigned to work on team projects. In others, students are given permission to collaborate on homework projects or to have written materials present during an examination. Unless otherwise specified, however, the CS Department requires all work to be the result of individual effort, performed without the help of other individuals or outside sources. If a question arises about the type of external materials that may be used or the amount of collaboration that is permitted for a given task, each individual involved is responsible for verifying the rules with the appropriate authority before engaging in collaborative activities, using external materials, or accepting help from others.

A student accused of academic dishonesty must be afforded due process as defined by Purdue University procedures. The Dean of Students Office may be notified concerning an academic dishonesty incident as provided by Purdue University procedures.

Last modified Fri 18 Oct 2019.