CS 525 – Network Security

1. CS 525 – Network Security Spring 2012 Instructor Craig Shue, Ph.D. cshue@cs.wpi.edu

2. Who Are You? • 4 Graduate CS • 3 Graduate ECE • 5 Undergrad CS

3. Professor Background • Dr. Craig Shue • Assistant Professor of Computer Science • Background: • Indiana University – MS: 2006; Ph.D – 2009 • Oak Ridge National Laboratory – Cyber Security Research Scientist – 2009 to present • Courses: • Networking, Network Security • Research: • New Internet Architectures • Security Measurements • Developing protocols and techniques

4. What is the Goal? • Instructor • Help students develop skills in CS research • Applies broadly, not just network security • Help students learn to share their ideas • Presentations • Research papers • Provide career foundation • Net. Sec. Jobs • MQPs • Theses/ISPs • Students • Learn to read/understand research papers quickly • Learn to present ideas to peers • Actively participate in discussion • Learn how to build/evaluate an experiment • Produce peer-review quality papers • Literature Reviews • LaTeX/BibTeX

5. What to Expect in Lecture • A student-led paper discussion • Occasional instructor-led discussions • Tools/Techniques of the Trade Discussion • Research project progress reports

6. You need to talk! • Presenting papers • Asking questions • Sharing ideas • Advancing the discussion • Oral communication influences success in life • You will be called on if you do not participate • Your choice: being “cold called” or offering things you’ve thought about more • Also, it is half your grade in this class

7. But you need to listen too! • We are not politicians… we actually have to listen and respond to each other • Take notes if you think you’ll forget a point • Remember to keep your cool • People will disagree with you all the time, but it isn’t personal. Hear them out. • People will be wrong. Get over it. Try to provide correct information politely.

8. You can talk to me! • Drop by my office • Set up an appointment • Email me • This class is different from most • It is loosely structured, but intense • Research is an acquired skill; you can’t just study • So if you’re having trouble, ask! • Other people likely have the same concerns

9. Class Structure • Class Participation (50%) • Reviews of papers by 9am on class day • Discussions and participation • Research Project (50%) • Individual or pairs • Topics • Instructor provided • Your own ideas with instructor approval • Outside of class research meetings • Keeps class sessions for shared discussion

10. Official Communication • Class discussion • Hand-outs • Emails • Course Web page • Team Meetings • If something is transmitted through one of these mediums, it has been communicated • If you miss class, you’re responsible for missed material (have a friend give you notes) • You are responsible for receiving class emails

11. Research Project

12. What is original research? • US Federal Government: • “Research means a systematic investigation, including research development, testing and evaluation, designed to develop or contribute to generalizable knowledge.” • Code of Federal Regulations: Title 45, Part 46 • Original research indicates this investigation cannot simply be drawing from other sources

13. Scientific Research • Theory or experimentation that must be • Replicable • Others must be able to confirm your results • Falsifiable • There must be a means to prove the idea wrong • “A will be better than B” • Not falsifiable: no metrics to evaluate “better than” • “A will be twice as fast as B” • Falsifiable: test the speed of both • Unbiased • Yes, you want the work to succeed, but you must be distanced enough to give it a chance to fail. • To do otherwise is,well, fraud.

14. Example Network Security Research Directions • Build (Innovate) • Measure • Analyze • Test • Attack

15. Propose the Project • Decide on a research project and write a proposal for it by January 25 • Proposal should be a one-page write-up • You should talk to me about your idea before you formally write it up to make sure it’s sufficient • Don’t have ideas? • No sweat. I have avenues I’d like to see explored. You can take one and run with it or use it for inspiration.

16. LaTeX and BibTeX • Scholarly work in Computer Science is often done in LaTeX and BibTeX • Some use Word still. It does not look as nice. • You will do your work in this class in LaTeX with BibTeX for your references • It uses markup like writing HTML • Fairly easy to get started. Harder to become an expert. • Resource: http://www.maths.tcd.ie/~dwilkins/LaTeXPrimer/

17. Using LaTeX • The project proposal must be created with LaTeX. Send both the PDF and the source code.

18. The Heilmeier Catechism • Named after George Heilmeier (CEO Belcore) • What are you trying to do? Articulate your objectives using absolutely no jargon. • How is it done today, and what are the limits of current practice? • What's new in your approach and why do you think it will be successful? • Who cares? If you're successful, what difference will it make? • What are the risks and the payoffs? • How much will it cost? How long will it take? • What are the midterm and final "exams" to check for success?

19. Project Ideas • Covert Channels • Marco Polo • Haven’t we met? • ISP Subnetting Reverse Engineering • Protecting Privacy with Pollution • Protecting Privacy with Privacy-Enhanced Advertising

20. Today’s Readings • P. Fong, "Reading a computer science research paper," Inroads, the SIGCSE Bulletin, 2009. • S. Keshav, "How to read a paper," ACM Computer Communication Review, 2007.

21. Reading for Next Time • R. Dingledine, N. Mathewson, and P. Syverson, "Tor: The second-generation onion router," in Proceedings of the 13th conference on USENIX Security Symposium-Volume 13. USENIX Association, 2004, pp. 21 - 21.