Course Description
This
course explores the application of policy and techniques to securing both
public and private networks. The
course is project-based and includes such topics as threat analysis and
management, cryptography, firewalls, isolation, issues in securing wireless
networks, and certificates.
Course Goals
The goal of this course is
to prepare the student to be able to
á
Understand the
principal issues in network security.
á Define and implement a security policy.
á Evaluate the implementation of a security policy.
á Learn what one can do
This course builds on the basics of Linux systems administration covered in IT 341 Introduction to Systems Administration.
How the Course Serves
Students
IT443 is a required course
in the System Administration track of the new BS in Information Technology (IT)
degree, offered jointly by the Department of Computer Science (CSM) and the
MSIS Department (CM). The System
Administration track is offered by the Computer Science Department. The trackÕs purpose is to prepare the
student for a career in computer systems administration and/or information
technology in general.
Syllabus
á
Physical structures, including hubs, routers, switches and servers.
á
Cryptography basics
á
DNS, ipAddressing management (static and DHCP), domains, WINS and
troubleshooting NAT issues.
á
Single sign-on management
á
Wireless security
á
Router security and ACL settings
á
The internet and private networks
á
Firewalls, DMZ, and honey pots
á
Tools for monitoring event logs, and troubleshooting.
á
VPNs and routed networks
á
Virtual networks and portable media
á
Certificates
á
The effects of the operating system (Unix, Windows and Mac)
á
Sniffers and what they can or cannot see.
á
Intrusion detection
á
Hacker attacks
á
Computer forensics
á
Privacy, intellectual property and theft
Projects
Much of the material in this
course will be transmitted by way of hands-on projects, where students, working
in small teams, set up small networks of computers running Linux.
á
A threat analysis and management study and a security plan.
á
Setting up SSH.
á
Implementing single sign-on.
á
Implementing a system to monitor logs for intrusions and threats to
security.
á
White-hat hacking.
á
Installing, configuring and monitoring a network firewall.
á
Setting up a DMZ.
á
Setting up a virtual private network (VPN).
á
Implementing certificates.
á
Implementing web application authentication and security
Grading
Projects and
Engineering Notebook 50%
Midterm Exam 20%
Final Exam 30%
Textbooks and
Readings
There
are very good textbooks that address both the policy issues of system
administration, as well as the implementation details. Many are oriented
towards specific systems such as Unix, Linux, Windows and (for people with
taste) Macs.
For
this course, we will use the following:
(From
IT341)
(New
for this course)
Additional
readings will be assigned from the SAGE web site at http://www.sage.org/. SAGE is the System
Administrators Guild, a special technical group of the USENIX
Association. They maintain a fabulous web site (which Rick Martin pointed
us to) with all sorts of resources including a series of monographs on core
sysadmin subjects.
Accommodations
Section 504 of the Americans
with Disabilities Act of 1990 offers guidelines for curriculum modifications
and adaptations for students with documented disabilities. If applicable,
students may obtain adaptation recommendations from the Ross Center for
Disability Services, Campus Center 2nd Floor, 2100 Street, Room 2010,
617-287-7430. The student must present these recommendations and discuss them
with each professor within a reasonable period, preferably by the end of
Drop/Add period.
Academic Honesty
All students are expected
to follow the University's Code of Student Conduct. If you are caught cheating, we will follow the
guidelines for punishment outlined in the code.
When you turn in work that
you have discussed with someone, or which contains ideas that you found in a book,
you must indicate that fact. We
expect you to talk to each other and to read materials other than those
assigned. We also expect to see in your work evidence that you have done so.
Learning to acknowledge intellectual debts is part of learning. You should be
reading, talking to each other, and telling the world that you have done so.
When group work is called for the group solution should note whenever a part of
the project was done by only a part of the group.
Some kinds of sharing,
however, are unacceptable. You may not use the computer to copy someone's work
and submit it as your own -- even if you acknowledge that theft! You may not
have your friends do your work for you. Versions of some of the assignments in
this course may have been given in previous years. You may not use answers to
those assignments.