CS 295A/361A--Security in Computing:
from Computer Viruses to User Privacy (Fall 2007, UVM, CRN91847/CRN91850)
- Subjects: Security in computing in a broad sense,
starting with a broad discussion of what security problems we have in
computing. Program security, OS security and trusted OS, database and data
mining security, and privacy in computing.
- Prerequisites: CS 201 Computer architecture and CS
222 Operating systems, or Permission of Instructor.
- (required text) Security
in Computing (4th Edition) by C. P. Pfleeger and S. L. Pfleeger.
Published by Prentice Hall. This book is also available (free access to
the UVM community) on Safari (need to access from within UVM, see here if
connecting from off campus)
- Required work: A written exam, some un-graded
homework assignments, a research paper or project (individualized, talk to
instructor) and associated presentation.
- Participation 30%, exam 30%, paper/project and
- Further requirements:
- Read the book chapters before and after class
- Honor code: The Computer Science Department
rigorously enforces the University's policy and procedures on Code of
Academic Integrity (PDF file). At the first suspicion of violation of
this code, the case will be immediately forwarded to the University
Coordinator of Academic Integrity. Of course, the Code applies to
your conduct in this course. In particular, all work
submitted for credit must be your own. You may discuss your homework assignments
with your classmates, TAs, and the professor. However, you should write up
solutions on your own and should not read or copy the solutions written by
others in this or previous semesters. For programming part of the
assignments, you must write your code for yourself, and are permitted to
read code written by classmates only if you are helping them debug their
programs after you have completed your own. Team projects
are collaborative efforts of the team members. Reading or copying other
team's code is not allowed (unless reading for the purpose of debugging after
your team's project is done). The UVM policy on sources also applies
to this course, which means that all sources must be acknowledged, whether
allowed by the professor or not. For example, software provided by someone
else must be acknowledged when incorporated into your work, and
discussions with classmates should be acknowledged.
- Disabilities: We encourage students with
disabilities, including "invisible" disabilities such as chronic
diseases and learning disabilities, to discuss with the professor any
appropriate accommodations that we could make on their behalf.