A comprehensive study of the principles and practices of computer systems security including operating systems security, software security, network security, and web security. Topics include common attacking techniques such as virus, trojan, worms and memory exploits; applied cryptography and key management; intrusion detection and security analytics; trusted computing; access control; password protection; and legal and ethical issues in computer security.
Basic algorithmic design and analysis (CS 5343).
System programming and operating systems concepts (CS 5348).
Class meetings and modality¶
Student learning objectives/outcomes¶
Students shall be able to understand what are the common threats faced today, what are the foundational theory behind information security, what are the basic principles and techniques when designing a secure system, how to think adversarially, how today's attacks and defenses work in practice, how to assess threats for their significance, and how to gauge the protections and limitations provided by today's technology. In particular, the students will have:
Ability to understand and explain fundamental security concepts
Ability to understand common threats and recognize vulnerabilities of information systems
Ability to understand and apply cryptographic algorithms
Ability to understand and apply network security enumeration and monitoring tools
Ability to understand and apply security policies
Course & instructor policies¶
Assignments and project will be evaluated on a ten-point scale (0-10).
Late work will be penalized 1 point per day (24-hour period).
Cheating vs. collaboration
Collaboration is a very good thing. On the other hand, cheating is considered a very serious offense and is vigorously prosecuted. Vigorous prosecution requires that you be advised of the cheating policy of the course before the offending act.
- For this semester, the policy is simple: don't cheat:
Never share code or text on the project.
Never use someone else's code or text in your solutions.
Never consult potential solutions on the Internet.
- On the other hand, for this class, you are strongly encouraged to:
Explain your code to someone to see if they know why it doesn't work.
Help someone else debug if they've run into a wall.
If you obtain help of any kind, always write the name(s) of your sources.