EEC 688/788 Secure and Dependable Computing Lecture 1 Wenbing Zhao Department of Electrical Engineering and Computer Science Cleveland State University wenbing@ieee.org

EEC688/788 Secure and Dependable Computing Outline Motivation Syllabus 4/30/2018 EEC688/788 Secure and Dependable Computing

EEC688/788 Secure and Dependable Computing Motivation Why secure and dependable computing is important?* Increased reliance on software to optimize everything from business processes to engine fuel economy Relentlessly growing scale and complexity of systems and systems-of-systems Near-universal reliance on a commodity technology base that is not specifically designed for dependability Growing stress on legacy architectures (both hardware and software) due to ever-increasing performance demands Worldwide interconnectivity of systems Continual threats of malicious attacks on critical systems *Taken from “A high dependability computing consortium”, James H. Morris, CMU, http://www.cs.cmu.edu/%7Ejhm/hdcc.htm 4/30/2018 EEC688/788 Secure and Dependable Computing

EEC688/788 Secure and Dependable Computing More Motivation The cost of poor software is very high Annual cost to US economy of poor quality software: $60B source: US NIST Report 7007.011, May 2002. Industry needs greater dependability and security Improved quality of products Improved quality of development processes Better system and network security, to avoid: viruses, trojans, denial of service, ... network penetration, loss of confidential data, ... Improved customer satisfaction 4/30/2018 EEC688/788 Secure and Dependable Computing

Industry is Embracing Secure and Dependable Computing The hardware platforms are changing: Smartcards Pervasive computing / embedded systems IBM, Sun “autonomic computing” Major PC dependability and security initiatives under way: Trusted Computing Group Promoters: Intel, HP, Compaq, IBM, Microsoft Microsoft’s trustworthy computing push Intel’s LaGrande dependable hardware 4/30/2018 EEC688/788 Secure and Dependable Computing

The Cost of Downtime From “Assessing the Financial Impact of Downtime” by Vision Solutions, Inc. 2008 (http://www.strategiccompanies.com/pdfs/Assessing%20the%20Financial%20Impact%20of%20Downtime.pdf) Typical hourly cost of downtime by Industry Brokerage Service: $6,480,000 Energy: $2,800,000 Telecom: $2,000,000 Manufacturing: $1,600,000 Retail: $1,100,000 Healthcare: $636,000 Media: $90,000 4/30/2018

EEC688/788 Secure and Dependable Computing Course Objectives Have solid understanding of the basic concepts and theory of secure and dependable computing Getting familiar with some basic building blocks (tools and APIs) needed to build secure and dependable systems No attempt to be comprehensive: topics covered are what I am interested in and what I think important 4/30/2018 EEC688/788 Secure and Dependable Computing

EEC688/788 Secure and Dependable Computing Prerequisite Operating system principles Processes, scheduling, file systems, etc. Java programming language At least you should know how to write a Hello World program You don’t have to be a Java expert Computer networks TCP, UDP, IP, Ethernet, etc. 4/30/2018 EEC688/788 Secure and Dependable Computing

EEC688/788 Secure and Dependable Computing Outline of Lectures Dependability concepts Introduction to computer and network security Cryptography, Secure communication, Intrusion detection and prevention Dependability techniques Logging & checkpointing Recovery-oriented computing Replication Group communication systems Consensus and Paxos Byzantine fault tolerance 4/30/2018 EEC688/788 Secure and Dependable Computing

EEC688/788 Secure and Dependable Computing Outline of Labs Lab 0 – Getting familiar with Linux Lab 1 – Secure shell Lab 2 – Secure computing in Java Lab 3 – Traffic analysis and intrusion detection Lab 4 – Group communication with Spread toolkit 4/30/2018 EEC688/788 Secure and Dependable Computing

EEC688/788 Secure and Dependable Computing Course Projects Write a short survey paper on a particular topic and make a presentation. The topic must be approved by the instructor. Must be done individually. The project is expected to survey 5-10 research papers, among them at least 2 must be published within 5 years. 4/30/2018 EEC688/788 Secure and Dependable Computing

EEC688/788 Secure and Dependable Computing Exam One midterm on security One final exam on fault tolerance Exams are closed book and closed notes, except that you are allowed to bring with you a one-page cheat sheet no larger than the US letter size (double-sided allowed) There is no makeup exam! 4/30/2018 EEC688/788 Secure and Dependable Computing

EEC688/788 Secure and Dependable Computing Grading Policy Class participation (10%) Lab reports (10%) Project (20%) Exams (60%) 4/30/2018 EEC688/788 Secure and Dependable Computing

EEC688/788 Secure and Dependable Computing Grading Policy A: 90-100% A-: 85-89% B+: 80-84% B: 75-79% B-: 70-74% C: 60-69% F: <60% 4/30/2018 EEC688/788 Secure and Dependable Computing

EEC688/788 Secure and Dependable Computing Class Participation 10% of the course credit In general, there is a mock quiz in the beginning of each lecture, so that I know who is here & I get feedback for my teaching To obtain the full credit for class participation, you must satisfy ALL of the following conditions: You do not miss more than 2 lectures You do not miss any exam and lab sessions You will lose all 10% credit if you miss more than 6 lectures/labs/presentations For undergraduate students: (if you choose to the labs option) 4/30/2018 EEC688/788 Secure and Dependable Computing

EEC688/788 Secure and Dependable Computing Do not cheat! Do not copy other student’s lab report, exams or projects Do not copy someone else’s work found on the Internet Including project implementation and report You can quote a sentence or two, but put those in quote and give reference You can build your projects on top of open source libraries, but again, you should explicitly give acknowledgement and state clearly which parts are implemented by you 4/30/2018 EEC688/788 Secure and Dependable Computing

Consequences for Cheating You get 0 credit for the project/lab/exam that you have cheated If the task is worth 25% or more of the course, it is considered a major infraction Otherwise, it is considered a minor infraction For major infraction and repeated minor infractions You will get an F grade, and You may be suspended or repulsed from CSU CSU Code of Conduct http://www.csuohio.edu/sites/default/files/StudentCodeOfConduct.pdf 4/30/2018 EEC688/788 Secure and Dependable Computing

EEC688/788 Secure and Dependable Computing Reference Texts Building Dependable Distributed Systems, by Wenbing Zhao, Wiley-Scrivener, March 2014 Security in Computing (4th Edition), by Charles P. Pfleeger, Shari Lawrence Pfleeger, Prentice Hall, 2006 Replication: Theory and Practice, Editted by by Bernadette Charron-Bost, Fernando Pedone, Andre Schiper, Springer, 2010 Computer Networks (4th Edition), by Andrew S. Tanenbaum, Prentice Hall, 2003 Cryptography and Network Security: Principles and Practices (3rd Edition), by William Stallings, Prentice Hall, 2003 SSH, the Secure Shell (2nd Edition), by Daniel J. Barrett, Robert G. Byrnes, Richard E. Silverman, O'Reilly, 2005 4/30/2018 EEC688/788 Secure and Dependable Computing

EEC688/788 Secure and Dependable Computing Reference Texts Reliable Computer Systems: Design and Evaluation (3rd Edition), by Daniel P. Siewiorek and Robert S. Swarz, A K Peters, 1998 Distributed Systems: Principles and Paradigms, by Andrew S. Tanenbaum, and Maarten van Steen, Prentice Hall, 2002 Reliable Distributed Systems: Technologies, Web Services, and Applications, by Kenneth P. Birman, Springer, 2005 Network Intrusion Detection (3rd Edition), by Stephen Northcutt, Judy Novak, New Riders Publishing, 2002 4/30/2018 EEC688/788 Secure and Dependable Computing

Instructor Information Instructor: Dr. Wenbing Zhao Email: wenbing@ieee.org, w.zhao1@csuohio.edu Lecture hours: T Th 2:00-4:00 Office hours: T Th noon-2pm & by appointment Course Web site: http://academic.csuohio.edu/zhao_w/teaching/EEC688-F17/eec688.htm 4/30/2018 EEC688/788 Secure and Dependable Computing