Professional Documents
Culture Documents
ICT379 Security Architectures and System Administration: Unit Information Guide 2021
ICT379 Security Architectures and System Administration: Unit Information Guide 2021
ICT379 Security Architectures and System Administration: Unit Information Guide 2021
This information should be read in conjunction with the online learning materials
which can be found on your LMS page
Unit Coordinator:
Dr Hui Cui
Discipline of Information Technology, Media and
Communications, Murdoch University
Email: hui.cui @murdoch.edu.au
© Published by Murdoch University, Perth, Western Australia, 2021.
This publication is copyright. Except as permitted by the Copyright Act no part of it may in
any form or by any electronic, mechanical, photocopying, recording or any other means be
reproduced, stored in a retrieval system or be broadcast or transmitted without the prior
written permission of the publisher.
CONTENTS
UNIT INFORMATION
ONE Introduction
TWO Contact details
THREE How to study this unit
FOUR Resources for the unit
FIVE Study schedules
SIX Assessment
ONE
Introduction
Unit overview
This unit considers information technology security in detail from an architectural perspective.
That is, not only are the different layers, mechanisms and components that operate to provide a
secure computing environment reviewed in detail, but the groupings, similarities and
interrelationships between these are analysed. However, the unit also considers the limitations
of an architectural perspective of security and the reasons why security mechanisms and
primitives fail to constitute a well-designed architectural model.
Prerequisites
In order to enrol in this unit, you must have completed ICT287 Computer Security.
Learning outcomes for the unit
On completion of this unit you should be able to:
1. Understand the application of the security architecture to real-world
applications.
2. Understand access control principles and apply them to address security issues
in information systems.
3. Understand the role of authentication in security architectures, including its
applications, and design a secure authentication mechanism.
4. Understand basic cryptographic techniques and apply them to solve the issues
in practice.
5. Understand the security of networks from an architectural perspective.
6. Demonstrate how to install and manage the security of Windows server
systems and networks.
7. Analyse the architectural security of the application to identify underlying
weaknesses and suggests the mechanisms necessary to resolve these.
Online
resources
The Online Unit (i.e. the ICT379 LMS site) can be accessed from your
MyMurdoch page.
Other
references In addition to the readings from the textbook, there may be additional
readings for some topics. These will either be given out in class, freely
available on the Internet or available from the Library’s electronic reserve
(eReserve):
http://prospero.murdoch.edu.au/search~S1/
You may also make use of the library’s databases to find journal articles
and conference papers:
http://library.murdoch.edu.au/Find-information/Databases/
Computing
resources The University uses software called Urkund which checks for plagiarism.
Be aware that any work submitted electronically may be manually or
automatically submitted to Urkund. Further, please note note that when
you or your Unit Coordinator submit assignments electronically, a copy of
your work is retained on the database to check collusion and future
plagiarism. The University has a legal agreement with Urkund that it will
not share or reproduce student work in any form.
1 Introduction
2 Authentication, Authorization and Access Control.
3 Cryptography.
4 Network security.
5 Cloud security.
6 Unit Review
Assessments that are not received by the due date will be regarded as late unless an
extension has been granted by the unit coordinator. Applications for extensions should
be made as soon as a problem is experienced. Late submissions will be penalised at a
rate of 10 percent of the total marks available for the assignment per day (or part thereof).
Assignments submitted more than five (5) days after the due date will not normally be
accepted without an extension or strong justification. No submission will be accepted
more than two weeks after the due date, or after assignment returns have begun,
whichever is earlier.