Course Outline
Course Outline
Email: [email protected]
2. Course Information
Course Code: CY 377
Sessions:
Level: Undergraduate
3. Course Objective
The objective of this course is to provide students with a comprehensive
enterprise and perimeter security. Students will learn how to design, implement, and
manage security systems and protocols that protect an organization's network and
assets. By the end of this course, students will be able to understand the fundamental
concepts of enterprise and perimeter security, analyze and compare various security
technologies and protocols, design and implement security systems and protocols for
Page 1 of 6
enterprise networks, manage and maintain security systems and protocols and
understand the legal and ethical issues related to enterprise and perimeter security.
4. Course Content
Introduction to Enterprise and Perimeter Security, Network Security Fundamentals,
Firewalls and VPNs, Intrusion Detection and Prevention Systems, Security Information
and Event Management (SIEM), Access Control and Identity Management, Network
5. Mode of Delivery
Lectures (face-to-face and online using Virtual Learning Environment), tutorials,
seminars, written, oral presentations, class quizzes and practical assignment. Students
1. Northcutt, S., Zeltser, L., Winters, S., Kent, K. and Ritchey, R. W. (2020), Inside
Network Perimeter Security, Sam Publications, 2nd Edition, 250 pp.
2. Garbis, J., & Chapman, J. W. (2021). Zero trust security: An enterprise guide.
Apress. https://doi.org/10.1007/978-1-4842-6702-8.
Page 2 of 6
7. Assessment
Items Marks
Quizzes 10
Presentation 5
Class Attendance 10
Class Participation 5
Project Work 10
End of Semester 60
Total 100
*Note: There will be several quizzes that will cover lecture material, and
8. Session Outline
Page 3 of 6
• SABSA Framework for Aligning Business and Security
Needs
Page 4 of 6
Vulnerabilities
All materials submitted for grading must conform to the following guidelines, failure
to do so may result in loss of credit.
Academic Integrity
All programs submitted must be your own work, and you are expected to develop
your programs independently. You may receive as much help as you wish on the use
of the operating system, text editors, debuggers, file transfer protocols and so on. You
may consult with other members of the class about interpreting the assignment, and
you may get help in finding bugs, but not fixing bugs, but you are not allowed to look
at or copy another person's code or discuss design decisions with others, and you
cannot show your code to others. Students found to be in violation of these guidelines
will fail the project and will be reported to the HOD.
Page 5 of 6
• A Readme file describing the contents of the directory.
question.
General Guidelines
• Your work should be submitted as a zip file. This file should expand to a
directory, named after your id number, containing the answer to the question,
as described above.
• It is the responsibility of the student to submit valid, readable zip files to the
correct address and via the appropriate platform. Corrupt or incomplete files
are unacceptable and may be judged incorrect.
submitted after the due date you will lose 40% of your score for each late day. I.e.,
homework submitted one day after the deadline will bring you only 60% of earned
points; two days after the deadline it will bring you 20%.
You can also improve your submission or fix errors in your submission until the due
date. Simply upload the new version.
Office Hours
Office hours are an opportunity for you to clarify details you may have missed in class
or to resolve a serious problem you have encountered. They are not a place to get a
"second run" of the lecture if you missed the class or obtain answers on the
assignment.
Page 6 of 6