|TA||Srinivasan Parthasarathy (Office AVW 3221; TuTh: 3:30 - 5:00)|
|Time||TuTh: 11:00 - 12:15|
|Office hours||TuTh: 1:00 - 2:00 and by appointment|
|Text||Security in Computing, Charles P. Pfleeger
The text will also be supplemented with additional papers which you can find links to on this page.
|A grade of C or better in CMSC 311 and CMSC 330.
NOTE: This course will cover a wide range of topics within computer science. If you are unable to quickly grasp these issues, you will have difficulty in the class. Review the course material here to ensure you're comfortable with the level. Also, all of the homework will include programming projects. If you are not comfortable programming, you will have great difficulty in this class.
|Until recently, information systems security has only
been a focus of the military, and the financial communities. With the recent
explosive growth and merging of telecommunications and computing, security
has become an integral element of any reliable and robust information systems
environment. Unfortunately, most current commercial products ignore security
in favor of a user friendly environment and performance. The side-effects
of this decision are now well documented in the press.
This class will cover information systems security at the under graduate level.
|There will be several homework assignments (written and
programming) as well as mid-term, and final examinations. A systems oriented
term project will also be required.
NOTE: All work that you submit in this course must be your own; unauthorized group efforts are considered academic dishonesty. See the Undergraduate Catalog for definitions and sanctions.
All written homework assignments MUST be turned in prior to the beginning of class on the date due. Assignments will be collected in the classrom prior to the start of class.
All programming assignments MUST be turned in electronically here prior to the beginning of class on the date due.
Late assignments will only be accepted under exceptional circumstances AND with prior arrangement. A penalty may apply.
|Final grades will be determined using the following distribution:|
Programming assignments and the course project will be graded on correctness as well as documentation. A project that fails on the provided test cases (and those used in grading) will not receive a favorable grade. A project that passes all tests, but does not contain reasonable documentation will also not receive a favorable grade. Security is a subset of reliability- good design and documentation increases the reliability of your code and thus the security.
Your class participation grade will be determined by your on time
attendance to class, and your participation in classroom discussions.
|Schedule of Classes|