Graduate Course Proposal Form Submission Detail - CIS6370
Submission Type: New
Course Change Information (for course changes only):
- Department and Contact Information
Tracking Number Date & Time Submitted 4902 2014-01-28 Department College Budget Account Number Computer Science and Engineering EN 2108 Contact Person Phone Nathanael Paul 8652351267 firstname.lastname@example.org
- Course Information
Prefix Number Full Title CIS 6370 Computer System and Data Security Is the course title variable? N Is a permit required for registration? N Are the credit hours variable? N Is this course repeatable? Y If repeatable, how many times? 3 Credit Hours Section Type Grading Option 3 C - Class Lecture (Primarily) R - Regular Abbreviated Title (30 characters maximum) Computer Sys and Data Security Course Online? Percentage Online O - Online (100% online) 0
COP 4600, COP 2510
The course is to serve as an introduction to computer system and data security issues at the graduate student level.
A. Please briefly explain why it is necessary and/or desirable to add this course.
Needed for new program/concentration/certificate
B. What is the need or demand for this course? (Indicate if this course is part of a required sequence in the major.) What other programs would this course service?
This course will be required for the new USF program in cybersecurity. As a requirement for this program, the demand will exist when the cybersecurity program is finalized.
C. Has this course been offered as Selected Topics/Experimental Topics course? If yes, how many times?
D. What qualifications for training and/or experience are necessary to teach this course? (List minimum qualifications for the instructor.)
Instructor needs a doctorate.
- Other Course Information
Students taking this course may have very little background in programming/math. We there cannot accomplish traditional assignments and projects of security courses, such as designing, implementing, and testing security systems. Instead of covering the technical details requires to design/implement/test security tools, we’ll focus on high-level concepts and how to use such tools. For this reason, credits obtained for this course may not be applied toward a degree in Computer Science or Computer Engineering.
As part of the course, will cover some security concepts including cryptography, authentication, randomness, key management, mal¬ware, web security, operating system security, network security, and hardware-based security. After taking this course, students will be better able to understand computer system and data security issues in computing systems.
B. Learning Outcomes
After taking this course, students will be better able to understand computer system and data security issues in computing systems.
C. Major Topics
cryptography, trustworthy computing, authentication, operating system security, mobile devices, network security, privacy
E. Course Readings, Online Resources, and Other Purchases
There will be assigned course readings, but those will vary. Some example material is included below:
The Protection of Information in Computer Systems
Richard E. Smith, "A Contemporary Look at Saltzer and Schroeder's 1975 Design Principles," IEEE Security & Privacy, vol. 10, no. 6, pp. 20-25, Nov.-Dec. 2012, doi:10.1109/MSP.2012.85
F. Student Expectations/Requirements and Grading Policy
Grading will be as follows:
60% Exams (both mid-term and final exam)
There will be a mid-term exam and a final exam. In addition to the exams, there will be periodic quizzes every week.
Incomplete grades (“I”): No incomplete grades will be given.
For final letter grades, I will use the standard scale of A (100-90), B (89-80), C (79-70), D (69-60), and F (59-0), without pluses or minuses.
G. Assignments, Exams and Tests
There will be two exams and approximately 8 quizzes.
H. Attendance Policy
Course Attendance at First Class Meeting – Policy for Graduate Students: For structured courses, 6000 and above, the College/Campus Dean will set the first-day class attendance requirement. Check with the College for specific information. This policy is not applicable to courses in the following categories: Educational Outreach, Open University (TV), FEEDS Program, Community Experiential Learning (CEL), Cooperative Education Training, and courses that do not have regularly scheduled meeting days/times (such as, directed reading/research or study, individual research, thesis, dissertation, internship, practica, etc.). Students are responsible for dropping undesired courses in these categories by the 5th day of classes to avoid fee liability and academic penalty. (See USF Regulation – Registration - 4.0101,
Attendance Policy for the Observance of Religious Days by Students: In accordance with Sections 1006.53 and 1001.74(10)(g) Florida Statutes and Board of Governors Regulation 6C-6.0115, the University of South Florida (University/USF) has established the following policy regarding religious observances: (http://usfweb2.usf.edu/usfgc/gc_pp/acadaf/gc10-045.htm)
In the event of an emergency, it may be necessary for USF to suspend normal operations. During this time, USF may opt to continue delivery of instruction through methods that include but are not limited to: Blackboard, Elluminate, Skype, and email messaging and/or an alternate schedule. It’s the responsibility of the student to monitor Blackboard site for each class for course specific communication, and the main USF, College, and department websites, emails, and MoBull messages for important general information.
I. Policy on Make-up Work
All deadlines are hard deadlines; extensions will not be granted. There will be no make-up quizzes or tests. If a quiz is missed, a zero will be awarded. The lowest quiz score will be dropped at the end of the class. If the mid-term exam is missed, then the final will count for both the final exam score and the mid-term exam score.
J. Program This Course Supports
M.S. in cybersecurity
- Course Concurrence Information