CIS 607 Seminar: How to Design a Robust Communication Structure for Internet Security Monitors?
Instructor: Prof. Jun Li
Annoucements
- Join the mailing list: simply run
grpmod -ag 607sequoia your-CIS-account-name
- The current presentation schedule is as below:
Week 2: Jacob & Darren
Week 3: Smita & Kushal
Week 4: Katie & Tom B
Week 5: Eric Wills & Shelby
Week 6: Shad & Zhen
Week 7: Andrew & < a brave volunteer>
Week 8: Xun & Zebin
Week 9: Brian & Toby
Week 10:Dan & Eric Purpus
Course Info
- CRN: 28180
- Prerequisites: CIS 432/532 or instructor approval
- Time: Fridays, 14:00 - 15:20 (may change)
- Location: 200 Deschutes
- Credits: 2, P/NP only
- Office Hours: Thursdays, 14:00 - 15:00 p.m., 334 Deschutes
- Web page:
http://www.cs.uoregon.edu/classes/05W/cis607sequoia
- Readings: TBA
Description
Centralized security monitoring cannot scale with the Internet;
a fully distributed, collaborative approach to security monitoring and
distribution of alerts is critical to robust growth. In this seminar,
we together discuss how to design, evaluate, and deploy a robust
communication architecture for the next generation of Internet-scale
security monitoring systems.
Winter 2005 Schedule
- Week 1 (1/7): Syllabus; Intro
- Week 2 (1/14): Topology awareness and neighbor discovery for security monitors
- Week 3 (1/21): Building a hierarchy: Who should stay at higher level?
- Week 4 (1/28): Graph theory vs. virtual monitor networking practice
- Week 5 (2/4): Self-management of the virtual monitor network
- Week 6 (2/11): Path discovery for a rich set of communication patterns
- Week 7 (2/18): Trust and Security
- Week 8 (2/25): Support for sharing blacklists
- Week 9 (3/4): Support for collaborative monitoring of Internet worms
- Week 10 (3/11): Deployment and evaluation and Wrap up
Course Design
Weekly reading summary
Each week we will have assigned materials regarding a specific topic.
Every student should read the assigned material, write a reading summary,
and email that to the instructor before the class starts.
The reading summary, preferably 200-300 words, should state the problem or topic that
the material addresses, briefly describe the solution or direction that the authors
come up with, and comments on the material (such as its strength and the weakness).
Weekly postmortem summary
Each week after the class, you should send the instructor a postmortem summary,
describing in 100+ words what you've found interesting (or boring) after the discussion
on a topic, what are those problems that should be further studied, what would
be your preferred solution, etc.
Class participation and presentation
During the winter term, every student also needs to make a presentation on the topic
for a chosen week, mainly by summarizing and commenting the mateiral he has just
read for the week. The student should then lead the discussion during and after the
presentation, with the help of the instructor.
We will decide the presentation schedule in the first meeting.
Small project [Optional]
If you like to test your own creativity and/or have some fun, you can also come up a project
that is small, fun, and has some wrinkles in the solution. I'll be happy to advise on it
throughout the term. It won't be counted toward your final grade, though (well, you may
get something interesting out of it, or even a paper).
Grading Policy
Pass or not pass. You have to pass each of the following in order to pass the course.
- Weekly reading and postmortem summaries
- Class participation and presentation
In other words, those who miss more than one summary, or more than one class,
or fail to do a class presentation, will not pass.
No mid-term exam. No final exam.
Useful Links