home > undergraduate > Computer and Network Security  > Computer and Network Security Homepage

Computer and Network Security (231.317) 6 points / Semester 2 Handbook Description The spectacular growth of the Internet has spawned an increased awareness of and interest in computer and network security issues. Although security has long been considered in the design of computer operating systems and basic Internet protocols, many applications and network services have been and are being designed with minimal attention paid to issues of confidentiality, authentication, and privacy. As our daily activities become more and more reliant upon computers and networks, an understanding of such security issues is essential. This unit provides an introduction to the topic of security in the context of computer systems and networks. It is intended for undergraduate students who have some understanding of operating systems and networks, but not necessarily any background in security. The goal of the unit is to provide students with a foundation allowing them to identify, analyze, and perhaps solve representative security problems in computer systems. The unit covers fundamentals of cryptography, authentication, and encryption technologies, protection services offered by modern operating systems, and secure and private communication in the very public world of the Internet. Unit Aims At the successful completion of this unit, students will be able to: appreciate the importance of confidentiality, authentication, and privacy in the use of computer and network systems. appreciate the role of cryptographic techniques in securing computer and network systems. appreciate the role and importance of standard protocols and specifications in the field of computer and network security. appreciate the professional and ethical responsibilities that they hold in securing information in computer and network systems. appreciate the government's role and impact in setting computer security and privacy policy in a societal and global context. Teaching Staff Coordinator/Lecturer Dr Chris McDonald Rm 2.20 Teaching assistant Asad Pirzada   Webpage for IT317 questions www.csse.uwa.edu.au/run/help317 Email for IT317 questions help317@csse.uwa.edu.au Contact Hours This unit consists of 25 hours of lectures, 33 hours of laboratories, and 7 hours of tutorials. Tutorials are held in even numbered weeks, with a revision tutorial in week 13. It is also expected that you will need to undertake additional study to achieve satisfactory progress in this unit. One additional hour per hour of formal contact is a reasonable estimate (i.e, an additional 5-6 hours per week). Assessment The assessment scheme for IT317 consists of a mid-semester test, a practical project and a two-hour examination in November. Before undertaking IT317, students should read the Guidelines for Academic Assessment in the 2004 Interfaculty Handbook. Attainment of the aims of the course will be assessed by testing fundamental knowledge in the test and written exam and assessing application of that knowledge in the project and written exam. Unsatisfactory Progress Any student who does not demonstrate satisfactory progress in this unit, as defined in the FECM Policy on Assessment Practices and Procedures, may be refused admission to the final examinations. The final deadline for notification of unsatisfactory progress is the last day of Week 10. Penalties The School of Computer Science and Software Engineering has adopted a policy on minimum penalties for late items of assessment. This is the default policy of all units unless indicated otherwise, in writing, by the specific unit coordinator. This policy shall apply to all items of continuous assessment, whether submitted either physically or electronically. Immediately after the submission deadline for an item of continuous assessment, a penalty of 20 percent will be applied PER DAY or PART THEREOF. The minimum mark possible for late submission is zero. The percentage is based on the item´s total contribution to the unit´s assessment. For example, a project contributing 40% to the unit´s assessment will incur a penalty of 8 marks for each day late until it is submitted or a mark of zero results. A more detailed description is given in this School´s Policy on Late Submission. The Faculty does have an appeals procedure, the details of which can found at the Policy for Appeals. Plagiarism Plagiarism is broadly defined to be when any portion of the work presented for assessment, can be attributed to another party. The student making the submission should acknowledge what aspects of the presented work is not directly derived by them. For the purposes of plagiarism it is irrelevant that you have been given permission by someone to copy their work and present it as your own. You are directed to the School of Computer Science and Software Engineering Policy on Plagiarism and the Faculty of Engineering,Computing and Mathematics Policy on Plagiarism. Faculty Scaling Final assessment is subject to the Faculty Scaling Policy.     home > undergraduate > Computer and Network Security  > Computer and Network Security Homepage    This information is correct as at 21-Jul-2004, but is subject to change from time to time. In particular, The University reserves the right to change the content and/or method of presentation and/or the method of assessment of any unit of study, to withdraw any unit of study or programme, and/or to vary arrangements for any programme. Copyright© 2004 School of Computer Science, & Software Engineering The University of Western Australia CRICOS Provider Code: 00126G Last updated: 21-Jul-2004