Students are introduced to some of the most common security issues involved in the development of software, including secure coding practices, secure database access, secure data communications, security of web applications, use of encryption techniques and security testing. Students are provided with a range of practical exercises to reinforce their skills, including authenticating and authorising users programmatically, user input validation, developing secure web, mobile/wireless and database applications, encrypting and hashing data programmatically, generating digital signatures programmatically, security testing, designing logging and auditing mechanisms.
2 hrs lectures/wk, 2 hrs laboratories/wk
Workload commitments per week are:
Two-hour lecture, two-hour tutorial (or laboratory) requiring preparation in advance, and a minimum of 2 hours of personal study per one-hour of contact time in order to satisfy the reading and assignment expectations.
FIT1002 and one of FIT1019 or FIT2078
Phu Dung Le
Phu Dung Le
Contact hours: Tuesday 2pm - 4pm
At the completion of this unit students will have -
A knowledge and understanding of:
Examination (3 hours): 60%; In-semester assessment: 40%
| Assessment Task | Value | Due Date |
|---|---|---|
| Assignment 1 - Identify software design and implementation vulnerabilities, and propose solutions | 20% | 4pm Friday Week 8 |
| Assignment 2 - Design and implementation of secure and trusted applications using cryptography | 20% | 4pm Friday Week 12 |
| Examination 1 | 60% | To be advised |
Monash is committed to excellence in education and regularly seeks feedback from students, employers and staff. One of the key formal ways students have to provide feedback is through SETU, Student Evaluation of Teacher and Unit. The University's student evaluation policy requires that every unit is evaluated each year. Students are strongly encouraged to complete the surveys. The feedback is anonymous and provides the Faculty with evidence of aspects that students are satisfied and areas for improvement.
For more information on Monash's educational strategy, and on student evaluations, see:
http://www.monash.edu.au/about/monash-directions/directions.html
http://www.policy.monash.edu/policy-bank/academic/education/quality/student-evaluation-policy.html
If you wish to view how previous students rated this unit, please go to
https://emuapps.monash.edu.au/unitevaluations/index.jsp
| Week | Activities | Assessment |
|---|---|---|
| 0 | ||
| 1 | Introduction to software design and implementation | |
| 2 | Computer software security problems and solutions | |
| 3 | Computer software security problems and solutions (con't) | |
| 4 | Principles of secure software design and implementation | |
| 5 | Concurrent programming and software security | |
| 6 | Concurrent programming and software security (con't) | |
| 7 | Building secure networked and distributed applications | |
| 8 | Building secure networked and distributed applications (con't) | Assignment 1 due 4pm Friday Week 8 |
| 9 | Building trusted software systems | |
| 10 | Secure software testing and verification | |
| 11 | Secure software testing and verification (con't) | |
| 12 | Research in software security and trusted systems | Assignment 2 due 4pm Friday Week 12 |
| SWOT VAC | No formal assessment is undertaken SWOT VAC | |
| Examination period | LINK to Assessment Policy: http://policy.monash.edu.au/policy-bank/ academic/education/assessment/ assessment-in-coursework-policy.html |
*Unit Schedule details will be maintained and communicated to you via your MUSO (Blackboard or Moodle) learning system.
To pass a unit which includes an examination as part of the assessment a student must obtain:
If a student does not achieve 40% or more in the unit examination or the unit non-examination total assessment, and the total mark for the unit is greater than 50% then a mark of no greater than 49-N will be recorded for the unit
Assessment will depend mainly on how well you can demonstrate a clear understanding of your work, theoretically and practically.
Assessment will depend mainly on how well you can demonstrate a clear understanding of your work, theoretically and practically.
It is a University requirement (http://www.policy.monash.edu/policy-bank/academic/education/conduct/plagiarism-procedures.html) for students to submit an assignment coversheet for each assessment item. Faculty Assignment coversheets can be found at http://www.infotech.monash.edu.au/resources/student/forms/. Please check with your Lecturer on the submission method for your assignment coversheet (e.g. attach a file to the online assignment submission, hand-in a hard copy, or use an online quiz).
Submission must be made by the due date otherwise penalties will be enforced.
You must negotiate any extensions formally with your campus unit leader via the in-semester special consideration process: http://www.infotech.monash.edu.au/resources/student/equity/special-consideration.html.
Monash has educational policies, procedures and guidelines, which are designed to ensure that staff and students are aware of the University's academic standards, and to provide advice on how they might uphold them.
You can find Monash's Education Policies at:
http://policy.monash.edu.au/policy-bank/academic/education/index.html
Key educational policies include:
The University provides many different kinds of support services for you. Contact your tutor if you need advice and see the range of services available at www.monash.edu.au/students The Monash University Library provides a range of services and resources that enable you to save time and be more effective in your learning and research. Go to http://www.lib.monash.edu.au or the library tab in my.monash portal for more information. Students who have a disability or medical condition are welcome to contact the Disability Liaison Unit to discuss academic support services. Disability Liaison Officers (DLOs) visit all Victorian campuses on a regular basis