outline introduction cs 239
play

Outline Introduction CS 239 Subject of class Advanced Topics in - PDF document

Outline Introduction CS 239 Subject of class Advanced Topics in Network Class topics and organization Security Reading material Class web page Peter Reiher Grading April 3, 2006 Projects Office hours Lecture


  1. Outline Introduction CS 239 • Subject of class Advanced Topics in Network • Class topics and organization Security • Reading material • Class web page Peter Reiher • Grading April 3, 2006 • Projects • Office hours Lecture 1 Lecture 1 Page 1 Page 2 CS 239, Spring 2006 CS 239, Spring 2006 Subject of Class Class Organization • Problems and solutions in network security • Graduate level seminar class • Concentrating on unsolved problems and • Concerning topics of ongoing research recent research in network security • Mostly on wide area infrastructure • Based around group discussions • Not really on securing your LAN or individual machine –Not formal lectures • Intended for students with serious research interest in network security Lecture 1 Lecture 1 Page 3 Page 4 CS 239, Spring 2006 CS 239, Spring 2006 A Typical Class Topics to Be Covered • Someone (usually one of you) will spend • IP spoofing 15-20 minutes outlining a topic • Routing security • Remainder of class will be spent discussing • Secure DNS it • Security for ubiquitous networks • Whoever presented it should lead discussion • DDoS defense • Generally, everyone will lead a discussion at some point • Worm defense Lecture 1 Lecture 1 Page 5 Page 6 CS 239, Spring 2006 CS 239, Spring 2006 1

  2. More Topics Assigning Topics • Evaluating network defenses • I’ll take the first class (on IP spoofing) • Handling spam • A few will have guest lecturers • Anonymization and privacy • Each of you should volunteer to take one of the others • Security alert systems • To be decided at the end of second • Phishing and pharming class • Legal and political issues related to • First come, first served these topics Lecture 1 Lecture 1 Page 7 Page 8 CS 239, Spring 2006 CS 239, Spring 2006 Reading Material Class Web Page • No textbook • http://www.lasr.cs.ucla.edu/classes/239_3.spring06 • 2-4 papers for each class • Will show class schedule – Some selected by me • And list papers for each class – Some by class leader –With links to them • Papers will be made available on class web page • Other useful information also there • In some cases, web pages may be used instead of papers Lecture 1 Lecture 1 Page 9 Page 10 CS 239, Spring 2006 CS 239, Spring 2006 Grading Midterm Exam • 20% midterm • Essay questions based on material in first half of class • 40% class participation • Probably three questions • 40% project • Open notes • No final exam –Including papers Lecture 1 Lecture 1 Page 11 Page 12 CS 239, Spring 2006 CS 239, Spring 2006 2

  3. Class Participation Leading a Class Discussion • Should focus on: • Covers both class you lead (15%) and – Analysis of the problem participation in other classes (25%) – Critiques of existing solutions • Not graded on brilliance – Suggested improvements to those • Or new solution approaches • But on involvement and ability to • Think of it as being part of a research team contribute to discussion looking at this problem • If you can’t regularly attend this class, • Goal is to spark a discussion you won’t do well in it – Not to spend two hours reviewing the papers that were assigned Lecture 1 Lecture 1 Page 13 Page 14 CS 239, Spring 2006 CS 239, Spring 2006 Slides for Presentations Class Projects • Not required, but a good idea • Half of your grade • If possible, send them to me ahead of • Group projects (2-4 people) time • On some topic involving network –So I can post them on the web page security • I’ll bring a projector to every class • Must be a research topic –Not just implementing known stuff Lecture 1 Lecture 1 Page 15 Page 16 CS 239, Spring 2006 CS 239, Spring 2006 Project Proposals Project Status Reports • Due at end of 7 th week of classes (May • Project proposals due at end of 4 th week of class (April 28) 19) • 1-page summary of what you want to • 1-3 page summaries of the progress do you’ve made to that date • Can be submitted as hard copy or –Hint: there should be some email • Hard copy or email OK • Not graded, but required • Not graded, but required Lecture 1 Lecture 1 Page 17 Page 18 CS 239, Spring 2006 CS 239, Spring 2006 3

  4. Project Presentation Project Demonstration • Last two class days reserved for project • If not feasible to demo in class, arrange a separate demo with me presentations • Projects should (usually) produce • In-class presentation of your project something demonstrable –Demo, if feasible • Important that demo shows off • Graded as part of project itself something interesting about project • Graded as part of project Lecture 1 Lecture 1 Page 19 Page 20 CS 239, Spring 2006 CS 239, Spring 2006 Project Reports What Makes a Good Project? • Written reports on project • Probably requires coding – Hardware OK, if you can do it • Due Monday of finals week (June 12) – Theoretical work acceptable, but you’ll need • 15 pages is typical length real results • Should: • Probably requires testing and/or measurement – Describe problem and approach • Should be research – Cover difficulties and interesting points – Original work no one else has already done – Describe implementation – Based on a promising idea – Ideally, this should be capable of being – Show that you’ve learned something from it! converted to a publishable research paper Lecture 1 Lecture 1 Page 21 Page 22 CS 239, Spring 2006 CS 239, Spring 2006 Office Hours Prerequisites • Probably should have taken CS 218 • MW 2-3 • Should have taken my CS 239 on Computer • In 3532F Boelter Hall Security • I’m around a lot, so other times can be – Or similar class elsewhere arranged by appointment • I’m not going to check on this • But I’ll assume you know this material • But I’ll be away April 17-28 – I won’t be presenting reviews of this –Guest lecturers most of those days material Lecture 1 Lecture 1 Page 23 Page 24 CS 239, Spring 2006 CS 239, Spring 2006 4

  5. Kinds of Security Things You Kinds of Networking Things You Should Know About Should Know About • IPsec • TCP/IP • Security protocols • Routing protocols • Key exchange, certificates, certification • How DNS works hierarchies • Basics of security threats and mechanisms • Multicast protocols • Use of cryptography for authentication, privacy, • Basic ad hoc networking and other purposes • Basics of wireless networks • Basics of firewalls and virus protection systems • Basic design and architecture of the Internet • Basics of viruses and worms Lecture 1 Lecture 1 Page 25 Page 26 CS 239, Spring 2006 CS 239, Spring 2006 A Short Introduction What’s In • Security of routing protocols, DNS, • What is this class really about? multicast protocols, resource reservation • Protecting computer networks and the protocols machines attached to them • Network-wide attacks (DDoS, Worms) • Focusing on the network threats • Security of specialized networks (sensor –Bad things that can happen due to networks, ad hoc networks) networking • Related topics (measurement issues, privacy, legal issues) –Attacks on network components Lecture 1 Lecture 1 Page 27 Page 28 CS 239, Spring 2006 CS 239, Spring 2006 What’s Out Types of Networks Covered • Cryptography (except as a tool) • The Internet • Securing LANs (firewalls, intrusion • Ad hoc networks detection systems, etc.) • Sensor networks • Securing individual computers (e.g, • Ubiquitous environments hardening against buffer overflow attacks) • Peer overlay networks • Security policy issues • Auditing, logging, formal methods, VPNs Lecture 1 Lecture 1 Page 29 Page 30 CS 239, Spring 2006 CS 239, Spring 2006 5

  6. The Internet and Security Does the Internet Need Security? • Absolutely • The original Internet design did not • Successful network attacks every day consider security • Some network attacks have cut whole • Not surprisingly, the resulting network countries off from the network has security problems • Some attacks have been made on the infrastructure that whole Internet relies on • What are the threats? • The value of what’s done on the Internet • How do we handle them? keeps growing • So the value of stopping it also grows Lecture 1 Lecture 1 Page 31 Page 32 CS 239, Spring 2006 CS 239, Spring 2006 Example Problems Internet Realities • Routing update security • DNS security • Router compromise • IP spoofing • Distributed denial of service attacks ISP ISP • Worms Autonomous Systems (ASs) The scope is worldwide Lecture 1 Lecture 1 Page 33 Page 34 CS 239, Spring 2006 CS 239, Spring 2006 Illustrating Some Security Problems DNS Security Eventually, the packets Routing Attacks DNS will be dropped Server 127.64.12.174 131.179.192.6 lasr.cs.ucla.edu http://lasr.cs.ucla.edu lasr.cs.ucla.edu Which happens to be the hacker’s address . . . Lecture 1 Lecture 1 Page 35 Page 36 CS 239, Spring 2006 CS 239, Spring 2006 6

Download Presentation
Download Policy: The content available on the website is offered to you 'AS IS' for your personal information and use only. It cannot be commercialized, licensed, or distributed on other websites without prior consent from the author. To download a presentation, simply click this link. If you encounter any difficulties during the download process, it's possible that the publisher has removed the file from their server.

Recommend


More recommend