|
|
|
|
|
Course Overview
|
|
|
This course addresses a broad
spectrum of issues in computer security and privacy,
ranging from cryptography, to systems security, to network security,
to usable security.
We will explore fundamental challenges in the design and
analysis of computer systems that must remain dependable
despite the actions of adversaries.
The goal of this course is to help you learn how to
think about, evaluate, and understand computer security issues.
back to
top
|
|
Grades will be assigned as follows:
- Projects: 40%
- Homeworks: 20%
- Textbook-style questions: 10%
- Blog postings: 10%
- Midterm: 15%
- Final: 25%
You must sign and return the Security and Privacy Code of Ethics form by the start of class on January 14 (Monday) in order to receive a non-zero grade for this course.
To check your grades on your MyUW page:
-
Go to http://myuw.washington.edu.
-
Login with your UW NetID
(this is not the same as your CSE NetID in general).
-
At the top of your MyUW page, click "Change Content".
-
On the next page, click "Browse & Choose".
-
On the next page, check the box next to the CSE channel and click "Save".
-
Finally, reload your front page again, and you should see your 484
grades in a new box.
You might also be able to view your grades at https://norfolk.cs.washington.edu/mycse.
back to
top
|
|
There will be
one midterm exam and a final exam for this course:
- Midterm : Friday, February 8, 2008, in class (date might change based on guest lecturer availability)
- Final : Wednesday, March 19, 2008, 8:30am - 10:20am, MGH 231
back to
top
|
|
There will be four kinds of
homework
assignments given throughout the class:
- Reading: You will be
given reading
assignments associated with each lecture. You
should finish the reading before coming to the lecture -- I will
assume you've done this reading, and my lectures will enhance the
material, rather than regurgitate it.
- Textbook-style questions:
I will assign written homework based on either questions
from the text, or made-up questions.
These assignments should be
handed in at the start of class on the due date.
(Make sure you read
the late policy below.)
- Blog posts: The course blog is online here.
Please read this blog post to understand
the blog posting requirements. Late blog posts will not be accepted; i.e., the late
policy does not apply to blog postings.
- Extra-credit:
From time to time, I may pose a question or give a programming
assignment that is purely extra credit. I may award extra credit
for outstanding contributions to the in-class discussions.
I may award extra credit to people contributing greatly to the
course email list or blog. I may also give you the opportunity to earn
extra credit at the end of some lectures.
back to top
|
|
As you've probably guessed
from
the allocation of grades, programming projects will be a major portion
of this class.
These programming projects will give you an opportunity to explore computer
security first hand.
At least one project will involve mounting buffer overflow attacks against
real C programs, so you should be deeply familar with C, assembly language,
and standard Unix command line development tools (like gdb).
back to
top
|
|
(Many of these policies are
taken
verbatim from previous instances of other UW CSE courses.)
|
|
back to
top
|
|
CSE Home 
