CSE 40567/60567 Fall 2008: Computer Security
General Information
Class Schedule
- TTh 9:30-10:45pm Aug 26 - Dec 11, 2008, at DeBartolo Hall 231
- Final exam TBA
Instructor
- Marina Blanton
- Email: mblanton AT cse.nd.edu
- Office: 356C Fitzpatrick Hall
- Office hours: MW 3-4pm or by appointment
Teaching Assistant
- Troy Raeder
- Email: traeder AT nd.edu
- Office: 254 Fitzpatrick Hall
Course Description
This course introduces undergraduate and graduate students to a wide range
of security topics with the goal to build solid understanding of the field.
A tentative list of topics covered is:
- cryptographic background and tools
- access control
- authentication
- software security, malware
- Internet security protocols and standards (SSL/TLS, IPsec, secure email)
- intrusion detection and intrusion prevention systems (firewalls)
- database security
- privacy
- identity management, phishing
- security management and risk assessment
- legal and ethical aspects (cybercrime, intellectual property)
Grading
Grading for this course will be based on homework assignments (HW), a course
project (CP), one midterm exam (ME), and the final exam (FE).
Tentatively, the grade will consist of 30% HW, 20% CP, 20% ME, and 30%
FE.
There will be several homework assignments, some of which will include
a programming element (mini-projects), and a course project of students'
choice. The project's topics must be within the scope of the course, and the
projects can be done in teams of two or individually. Further guidelines
will be provided.
Textbooks
Textbook: - William Stallings and Lawrie Brown, Computer Security:
Principles and Practice, Pearson Prentice Hall, 2008.
Additional resources:
- Charles Pfleeger and Shari Pfleeger, Security in Computing,
Prentice Hall, 2006.
- Charlie Kaufman, Radia Perlman, and Mike Speciner, Network Security:
Private Communication in a Public World, Prentice Hall, 2002.
- Edward Skoudis and Tom Liston, Counter Hack Reloaded: A Step-by-Step
Guide to Computer Attacks and Effective Defenses, Prentice Hall,
2006.
- Ross Anderson, Security Engineering: A Guide to Building Dependable
Distributed Systems, Wiley, 2001.
Assignment Policies
- All homeworks must be done individually unless announced otherwise.
- Discussion of homeworks is acceptable until you begin to formulate
individual solutions.
- Writing homeworks must be done individually.
- Homeworks will be due in class and must be typed (diagrams can be hand-drawn).
- Each student receives three days that can
be used to turn homework
assignments in late. Whenever using one or more of these days on an
assignment, you must communicate this to the instructor prior to the
deadline. Each extra day extends the deadline by 24 hours. Homework then
can be submitted by e-mail.
- No late homework beyond the three extra days is accepted.
Academic Integrity
Computer science, as a profession, requires us to seek truth not only in
scientific discoveries, but also in dealing with the public, as the public
depends on our expertise and honesty to construct their computing
infrastructure. Thus, competence and trust are essential to being a scholar
and a computing professional in particular.
Your instructor will treat you as a professional, and you should plan on
conducting yourself in an appropriate way. No behavior that compromises
academic honesty (such as use of someone else's work or code, using
prohibited materials during tests, or making your work available to others)
will be tolerated in this course. If you need assistance with anything, do
not hesitate to contact the instructor.
Both ND
Academic Code of Honor and the Graduate School's policies outlined here.
It is expected that your work represents your own understanding of
the problem. If work of others is used, it must be properly cited. Use of
properly cited material is acceptable, but no referencing is treated as
claiming the work as your own.
Lectures