Overview
This unit is the capstone to the Cyber Security specialisation of the Bachelor of Information Technology course. The unit is designed so that you can demonstrate your learning across the whole course of study before making the transition to the next stage of your career. To this end, you are to conduct a group project including the design and implementation of a cyber security plan that meets the client's requirements. Deliverables will include the formal security plan and configured secure infrastructure as part of an overall portfolio of planning and design documentation, scripts, and rules. In order to deliver a robust solution, you will need to choose and employ an appropriate project management methodology. The delivered infrastructure will undergo stress testing and simulated security attack scenarios.
Details
Pre-requisites or Co-requisites
Prerequisites: (COIS13064 ICT Project Management or COIT12208 ICT Project Management) and COIT12202 Network Security Concepts Corequisites: COIT13146 System and Network Administration and (COIT13229 Applied Distributed Systems or COIT13240 Applied Cryptography)
Important note: Students enrolled in a subsequent unit who failed their pre-requisite unit, should drop the subsequent unit before the census date or within 10 working days of Fail grade notification. Students who do not drop the unit in this timeframe cannot later drop the unit without academic and financial liability. See details in the Assessment Policy and Procedure (Higher Education Coursework).
Offerings For Term 1 - 2022
Attendance Requirements
All on-campus students are expected to attend scheduled classes – in some units, these classes are identified as a mandatory (pass/fail) component and attendance is compulsory. International students, on a student visa, must maintain a full time study load and meet both attendance and academic progress requirements in each study period (satisfactory attendance for International students is defined as maintaining at least an 80% attendance record).
Recommended Student Time Commitment
Each 12-credit Undergraduate unit at CQUniversity requires an overall time commitment of an average of 25 hours of study per week, making a total of 300 hours for the unit.
Class Timetable
Assessment Overview
Assessment Grading
This is a graded unit: your overall grade will be calculated from the marks or grades for each assessment task, based on the relative weightings shown in the table above. You must obtain an overall mark for the unit of at least 50%, or an overall grade of ‘pass’ in order to pass the unit. If any ‘pass/fail’ tasks are shown in the table above they must also be completed successfully (‘pass’ grade). You must also meet any minimum mark requirements specified for a particular assessment task, as detailed in the ‘assessment task’ section (note that in some instances, the minimum mark for a task may be greater than 50%). Consult the University’s Grades and Results Policy for more details of interim results and final grades.
All University policies are available on the CQUniversity Policy site.
You may wish to view these policies:
- Grades and Results Policy
- Assessment Policy and Procedure (Higher Education Coursework)
- Review of Grade Procedure
- Student Academic Integrity Policy and Procedure
- Monitoring Academic Progress (MAP) Policy and Procedure – Domestic Students
- Monitoring Academic Progress (MAP) Policy and Procedure – International Students
- Student Refund and Credit Balance Policy and Procedure
- Student Feedback – Compliments and Complaints Policy and Procedure
- Information and Communications Technology Acceptable Use Policy and Procedure
This list is not an exhaustive list of all University policies. The full list of University policies are available on the CQUniversity Policy site.
Feedback, Recommendations and Responses
Every unit is reviewed for enhancement each year. At the most recent review, the following staff and student feedback items were identified and recommendations were made.
Feedback from Unit Coordinator reflections
Few groups gained experience in discussing their project with a real client.
Increase the number of projects conducted for real clients such as industry partners and researchers.
Feedback from Student feedback
Costly for students to use personal or student accounts to access the range of cloud services needed for their project.
Recommend a cloud service provider that has free credits to students for the duration of the project, and offer additional credits to students when required by their project (e.g. using specialist, non-free cloud services).
Feedback from Student feedback
Some students were unclear about the depth expected in deliverables.
Provide samples of deliverables from previous projects.
- Analyse cyber security requirements to produce a comprehensive cyber security plan
- Implement well-documented and tested security technologies to meet a cyber security plan
- Evaluate security protections for compliance and effectiveness
- Produce the project management artefacts required in a typical cyber security project
- Demonstrate productive participation and contribution to a project team or work environment
- Demonstrate work readiness in terms of technical skills, communication skills, and both professional and ethical behaviour.
The Australian Computer Society (ACS) recognises the Skills Framework for the Information Age (SFIA). SFIA is adopted by organisations, governments and individuals in many countries and provides a widely used and consistent definition of ICT skills. SFIA is increasingly being used when developing job descriptions and role profiles. ACS members can use the tool MySFIA to build a skills profile.
This unit contributes to the following workplace skills as defined by SFIA 7 (the SFIA code is included)- Project Management (PRMG)
- IT Management (ITMG)
- Information Security (SCTY)
- Security Administration (SCAD)
- Enterprise IT Governance (GOVN)
- Specialist Advice (TECH)
- IT Infrastructure (ITOP)
- Systems Installation/Decommissioning (HSIN)
- Network Support (NTAS)
- Network Planning (NTPL)
- Network Design (NTDS)
- Systems Design (DESN)
- Penetration testing (PENT)
- Information Assurance (INAS)
Alignment of Assessment Tasks to Learning Outcomes
| Assessment Tasks | Learning Outcomes | |||||
|---|---|---|---|---|---|---|
| 1 | 2 | 3 | 4 | 5 | 6 | |
| 1 - Report - 40% | ||||||
| 2 - Portfolio - 20% | ||||||
| 3 - Written Assessment - 20% | ||||||
| 4 - Presentation - 20% | ||||||
Alignment of Graduate Attributes to Learning Outcomes
| Graduate Attributes | Learning Outcomes | |||||
|---|---|---|---|---|---|---|
| 1 | 2 | 3 | 4 | 5 | 6 | |
| 1 - Communication | ||||||
| 2 - Problem Solving | ||||||
| 3 - Critical Thinking | ||||||
| 4 - Information Literacy | ||||||
| 5 - Team Work | ||||||
| 6 - Information Technology Competence | ||||||
| 7 - Cross Cultural Competence | ||||||
| 8 - Ethical practice | ||||||
| 9 - Social Innovation | ||||||
| 10 - Aboriginal and Torres Strait Islander Cultures | ||||||
Textbooks
There are no required textbooks.
IT Resources
- CQUniversity Student Email
- Internet
- Unit Website (Moodle)
- Access to computer with webcam, microphone and speakers
- Zoom
- Microsoft Teams
All submissions for this unit must use the referencing style: Harvard (author-date)
For further information, see the Assessment Tasks.
s.d.gordon@cqu.edu.au
Module/Topic
Weekly meeting with project mentor (tutor)
Chapter
Events and Submissions/Topic
Module/Topic
Weekly meeting with project mentor
Chapter
Events and Submissions/Topic
Module/Topic
Weekly meeting with project mentor
Chapter
Events and Submissions/Topic
Deliverable: Skills Development Plan (9:00 AM AEST Monday 21 March 2022)
Module/Topic
Weekly meeting with project mentor
Chapter
Events and Submissions/Topic
Deliverable: Project Plan (9:00 AM AEST Monday 28 March 2022)
Deliverable: Group Progress Report 2 (9:00 AM AEST Friday 1 April 2022)
Module/Topic
Weekly meeting with project mentor
Chapter
Events and Submissions/Topic
Module/Topic
No meeting
Chapter
Events and Submissions/Topic
Module/Topic
Weekly meeting with project mentor
Chapter
Events and Submissions/Topic
Deliverable: Draft Report (9:00 AM AEST Monday 18 April 2022)
Module/Topic
Weekly meeting with project mentor
Chapter
Events and Submissions/Topic
Module/Topic
Weekly meeting with project mentor
Chapter
Events and Submissions/Topic
Deliverable: Quality Review (9:00 AM AEST Monday 2 May 2022)
Deliverable: Group Progress Report 3 (9:00 AM AEST Friday 6 May 2022)
Module/Topic
Weekly meeting with project mentor
Chapter
Events and Submissions/Topic
Module/Topic
Weekly meeting with project mentor
Chapter
Events and Submissions/Topic
Deliverable: Group Progress Report 4 (9:00 AM AEST Friday 20 May 2022)
Module/Topic
Weekly meeting with project mentor
Chapter
Events and Submissions/Topic
Module/Topic
Weekly meeting with project mentor
Chapter
Events and Submissions/Topic
Module/Topic
Presentation Day
Chapter
Events and Submissions/Topic
Deliverable: Final Report (9:00 AM AEST Monday 6 June 2022)
Deliverable: Final Presentation (9:00 AM AEST Monday 6 June 2022)
Deliverable: Project Reflection (9:00 AM AEST Friday 10 June 2022)
You will need access to a computer (laptop or PC) that supports video conferencing and any software relevant to your project. As students may undertake different projects, the specific software requirements may vary. Therefore, it is the responsibility of the project team to ensure they have sufficient hardware/software to complete the project.
Your Final Presentation will be delivered to an audience outside of your campus, and therefore may be delivered using Zoom video conferencing software (even if you are an on-campus student). Therefore, you must have a computer with webcam, microphone and speakers (for example, a headset). Note that you will be required to present with your webcam on - using a device without a webcam or not showing your face is not an acceptable method of presentation. The Schedule in this Unit Profile lists Deliverables, which give the due dates of assessment tasks. Some due dates for assessments are on a Monday at 9:00 AM AEST. Be aware that support from teaching staff may not be available over the weekend (or any public holidays) leading to the due date. Therefore, you are recommended to have draft submissions on Moodle at least two days before the due date.
1 Report
Components
This assessment is split into two (2) deliverables:
- Draft Report
- Final Report
Expectations of Final Report
Your Final Report must document technical artefacts of the entire project. The content may vary depending on the chosen topic and the problem being addressed. The following are example technical artefacts that may be included in a Final Report.
- Detailed description of the problem from a business and technical perspective
- Review of existing/competing products, solutions, or literature
- Identification, selection and justification of appropriate network and security technologies to solve the problem
- Specification of requirements, for example, functional, usability, reliability, performance, security
- Logical and/or physical network designs
- Design of network/security architectures, protocols or algorithms
- Network and security policies, for example, disaster recovery plan, password policies, business continuity plan
- Risk assessment
- Recommended security controls to solve the problem
- Rapid prototype of a solution to the problem
- Results from security/penetration testing on a system
- Deployment of network/security components, for example, database/web servers in the cloud
As different groups are undertaking different projects, you should discuss with your Project Mentor (tutor) the expected artefacts for your project.
Expectations of Draft Report
Your Draft Report consists of the latest versions of your technical artefacts produced by the deadline. See the examples of technical artefacts from the Final Report. Some of the artefacts will be complete (or close to final version), and some may be partially complete (e.g. some sections complete, other sections empty). You will normally not include artefacts that you have started, but made very little progress (e.g. less than 50% complete). The Draft Report is an opportunity to get feedback on your current progress. As with the Final Report, discuss with your Project Mentor what is expected for your project. Your Project Mentor will also advise you on which artefacts to include or omit from the Draft Report. Your Draft Report will be released to other students.
Format and Submission
The Final Report should be presented as a formal, technical document (e.g. with title, section headings, references, diagrams, tables). The report must be submitted as a Microsoft Word document. You are encouraged to use separate documents/files for different artefacts. For example, if your group has developed a privacy policy and undertaken a risk assessment, they should be submitted as separate documents, with the Final Report simply referring to them. That is, you may submit Final Report (Word doc), Privacy Policy (Word doc), Risk Assessment (Word doc), Network Design (Visio file) and so on.
The Draft Report should be presented and submitted in the same manner as the final report. Where sections are missing or incomplete, you should clearly mark them (e.g. "This section is not yet complete.").
All group documents and technical artefacts must be stored on a Microsoft Teams channel created for your group by the Unit Coordinator, and shared with your Project Mentor (tutor) and Unit Coordinator. With prior approval of the Unit Coordinator, a collaborative platform other than Microsoft Teams may be used. While documents are stored Teams, they must also be submitted on Moodle.
See the Schedule for due dates of deliverables
Certification of Grades day for Final Report; Draft Report after all Quality Reviews submitted
Contribution to Grade
- Draft Report: 10%
- Final Report: 30%
Individual and Group Contributions
Both reports are group work. In most cases, all team members will receive the same mark. However if the project mentor or Unit Coordinator detect significant differences in contributions across team members, then interviews may be held to determine individual contributions, and individual marks allocated based on those contributions.
Marking Criteria
Your Final Report will be marked based on:
- Problem definition. You must give a clear and concise statement of the problem your project is attempting to solve.
- Approach. The methodologies, tools and techniques you use to solve the problem must be appropriate.
- Solution quality and depth. Your solution must demonstrate an investigation into significant depth and the resulting outputs must be of quality expected of a graduate.
- Presentation. For example, formatting, grammar, referencing.
The reports, and especially the solution quality and depth, will be assessed taking into account the project management activities (for example, Project Plan, progress reports, quality review). For example, if the project does not deliver what the Project Plan promised and the changes are have not been justified in progress reports, then a low score may be awarded. However, if the project does deliver what is promised, but there is little technical depth in that deliverable, then a low score may still be awarded.
The Draft Report will be marked in the same manner as the Final Report.
This unit is 12 credit points, and therefore requires significant amount of work every week with frequent assessment deadlines. If you get behind and miss a deadline, then it will be very hard for you to catch up. Therefore, for all assessments any late submissions more than 7 days after the original deadline will receive 0 marks.
Detailed marking criteria are available on Moodle.
- Analyse cyber security requirements to produce a comprehensive cyber security plan
- Implement well-documented and tested security technologies to meet a cyber security plan
- Evaluate security protections for compliance and effectiveness
- Demonstrate work readiness in terms of technical skills, communication skills, and both professional and ethical behaviour.
2 Portfolio
Components
This assessment is split into five (5) deliverables:
- Skills Development Plan
- Individual Progress Report 1
- Group Progress Report 2
- Group Progress Report 3
- Group Progress Report 4
Expectations of Skills Development Plan
At the start of the project you must identify your career goals, including preferred job role upon graduation, and self-assess your current knowledge, skills and abilities against those expected for an IT professional. You will highlight gaps and identify tasks that you aim to focus on in the project to work towards filling those gaps.
Expectations of Progress Reports
Each progress report must:
- explain your technical progress since the last report (or since the start of the project)
- report on the status of tasks completed since the previous progress report, and any signficant changes with respect to your Project Plan
- list the issues and challenges that have arisen, and your approaches to addressing them
- list the priority tasks for the next phase of work (up until the next progress report and/or the end of project)
You will be expected to answer questions about your progress report.
Format and Submission
The Skills Development Plan must be submitted using the template Excel spreadsheet provided on the Moodle site.
All progress reports will be delivered verbally.
The verbal progress reports require you to briefly talk about your progress. You will be required to pre-record each progress report as a video and make that video available to the project mentor on Microsoft Teams. You will have a limited amount of time to present for each progress report (time limits to be announced via Moodle). Progress reports should not use many slides, however may show technical artefacts (e.g. network designs, code, policies). While the progress report will be pre-recorded, questions will be live.
All group documents and technical artefacts must be stored on a Microsoft Teams channel created for your group by the Unit Coordinator, and shared with your Project Mentor (tutor) and Unit Coordinator. With prior approval of the Unit Coordinator, a collaborative platform other than Microsoft Teams may be used. While documents are stored Teams, they must also be submitted on Moodle.
See the Schedule for due dates of deliverables
Two weeks after deadline
Contribution to Grade
- Skills Development Plan: 4%
- Individual Progress Report 1: 4%
- Group Progress Report 2: 4%
- Group Progress Report 3: 4%
- Group Progress Report 4: 4%
Individual and Group Contribution
The Skills Development Plan is individual work.
A separate Individual Progress Report 1 is given by every student in the group. That is, this is individual work.
Group Progress Reports are group work, however individuals may receive different scores based on their contributions. Different group members may deliver the different Group Progress Reports. All group members do not need to talk in the pre-recorded video in every Group Progress Report. However across all three Group Progress Reports, all group members must present at least once. For example, if there are four students in a group, student 1 may present Group Progress Report 2, students 2 and 3 may present Group Progress Report 3 and student 4 may present Group Progress Report 4. All group members must be available to answer questions on all Group Progress Reports.
Marking Criteria
Your Skills Development Plan will be marked based on:
- Genuine and in-depth self-assessment of knowledge, skills and abilities
- Ability to identify specific, relevant activities to fill in gaps that will contribute to future career goals
Your progress reports will be marked based on:
- Depth and quality of your technical contributions
- Ability to plan realistic and significant tasks, and to complete planned tasks
- Identification of challenges in the project, and practical approaches to deal with those challenges.
While the progress reports are pre-recorded, an important aspect of each progress report is answering questions from the Project Mentor (tutor). Therefore, attendance at your class (or scheduled project meeting) is required for each week that a progress report is due. If you do not attend (and do not have a valid reason, for example, a medical certificate) then you may receive 0 marks for the progress report (even if you contributed to the pre-recorded verbal talk).
This unit is 12 credit points, and therefore requires significant amount of work every week with frequent assessment deadlines. If you get behind and miss a deadline, then it will be very hard for you to catch up. Therefore, for all assessments any late submissions more than 7 days after the original deadline will receive 0 marks.
Detailed marking criteria are available on Moodle.
- Produce the project management artefacts required in a typical cyber security project
- Demonstrate productive participation and contribution to a project team or work environment
- Demonstrate work readiness in terms of technical skills, communication skills, and both professional and ethical behaviour.
3 Written Assessment
Components
This assessment is split into two (2) deliverables:
- Project Plan
- Quality Review
Expectations of Project Plan
Your Project Plan must:
- Define the problem your team will solve
- Identify the roles and responsibilities of team members
- Schedule a set of tasks and deliverables
- List anticipated challenges and mitigation strategies
- Report initial technical progress of the project (for example, the outputs of rapid design and prototyping)
Expectations of Quality Review
You will be required to conduct an independent review of technical artefacts of another group. The technical artefacts to review may include network design, policies, risk assessments, code, cloud services, etc (see the Project Report for more details on technical artefacts). The technical artefacts of all groups will be published, and you will be allocated a group/artefacts to review. Your Quality Review must:
- Evaluate the quality of the technical artefacts
- Propose improvements to designs, implementation and/or processes
The Unit Coordinator will assign the group/artefacts for you to review (based on the Draft Report submissions). You may be assigned multiple artefacts from one group to review. You are expected to conduct your review in an independent and professional manner. For example, you should not seek to influence reviews (for example, "I will give you a positive review if you give me a positive review") and your evaluation must be on the technical aspects (not influenced by who is in the other group).
Format and Submission
Both the Project Plan and Quality Review must be submitted as reports (for example, Microsoft Word documents). Where appropriate, other documents (for example, initial network designs) may be submitted in other file formats as an appendix to the report.
All group documents and technical artefacts must be stored on a Microsoft Teams channel created for your group by the Unit Coordinator, and shared with your Project Mentor (tutor) and Unit Coordinator. With prior approval of the Unit Coordinator, a collaborative platform other than Microsoft Teams may be used. While documents are stored Teams, they must also be submitted on Moodle.
See the Schedule for due dates of deliverables
Two weeks after deadline
Contribution to Grade
- Project Plan: 8%
- Quality Review: 12%
Individual and Group Contributions
The Project Plan is group work.
The Quality Review is performed by a pair of students. That is, your group is split into pairs of students, and each pair conducts a review of another groups' artefacts. If there is an odd number of students in your group, then one of you will conduct the review on your own.
In most cases, all group members will receive the same mark. However if the project mentor or Unit Coordinator detect significant differences in contributions across group members, then interviews may be held to determine individual contributions, and individual marks allocated based on those contributions.
Marking Criteria
Your Project Plan will be marked based on:
- Depth and quality of planning.
- Depth and quality of initial technical artefacts presented.
Your Quality Review will be marked based on:
- Demonstrated understanding of the work under review.
- Identification of strengths and weaknesses of the work under review.
- Relevance and details of recommendations made.
Typically you will review technical artefacts submitted in the Draft Report. You will not be assigned a group to review until your group has submitted your own technical artefacts to a reasonable standard for review by others. That is, you can't start your review until you have made your technical artefacts available to others for review. If your group does not submit your technical artefacts one (1) week before the Quality Review deadline, all members of your group will receive zero (0) marks for the Quality Review.
This unit is 12 credit points, and therefore requires significant amount of work every week with frequent assessment deadlines. If you get behind and miss a deadline, then it will be very hard for you to catch up. Therefore, for all assessments any late submissions more than 7 days after the original deadline will receive 0 marks.
Detailed marking criteria are available on Moodle.
- Analyse cyber security requirements to produce a comprehensive cyber security plan
- Implement well-documented and tested security technologies to meet a cyber security plan
- Evaluate security protections for compliance and effectiveness
- Produce the project management artefacts required in a typical cyber security project
4 Presentation
Components
This assessment is split into two (2) deliverables:
- Final Presentation
- Project Reflection
Expectations of Final Presentation
In your Final Presentation you must convince the audience that the work you have done is substantial, high quality and relevant for your major, and that you have applied appropriate processes to complete the work. The audience may include students from this unit, other students, your project mentor, Unit Coordinator, other academic staff, alumni, and industry representatives. The presentation will be time-limited (to be confirmed during the term). Therefore, you must design your presentation to convey the key aspects of your project, taking into account the audience and time limitations. While the content/structure of your presentation is mainly your choice, it must at least include:
- Identification of your project topic, mentor and group members
- Reflection on technical challenges, for example, what new things did you learn, what was difficult, how did you solve problems.
- Demonstration of the system you develop or problem solved.
You may use a variety of presentation tools (including live demonstrations, videos, screenshots), but must be supported by slides.
Expectations of Project Reflection
At the end of the project you must reflect on your project, your achievement in filling gaps identified at the start of the term, and identify plans for the next steps in your career. You must also make the first step in your career by publishing technical artefacts in your public portfolio (e.g. using your university Portfolium account).
Format and Submission
Your group must deliver your Final Presentation live using Zoom video conferencing. The final presentations will be scheduled in a conference-style event, running up to 1 day. Groups will be assigned to present at time slots during the day, and also be required to view presentations of other groups. The presentation day is planned for Monday 6 June 2022; the detailed schedule for presentations will be announced during the term.
You must submit at least PowerPoint slides on Moodle by the deliverable deadline. Other formats of the slides (including PDF) are not acceptable, unless permission is granted in advance by the Unit Coordinator. You may optionally submit other resources (e.g. videos) in addition to the slides.
The Project Reflection must be submitted using the template Word document provided on the Moodle site.
All group documents and technical artefacts must be stored on a Microsoft Teams channel created for your group by the Unit Coordinator, and shared with your Project Mentor (tutor) and Unit Coordinator. With prior approval of the Unit Coordinator, a collaborative platform other than Microsoft Teams may be used. While documents are stored Teams, they must also be submitted on Moodle.
See the Schedule for due dates of deliverables
Certification of Grades day for Final Presentation and Project Reflection
Contribution to Grade
- Final Presentation: 15%
- Project Reflection: 5%
Individual and Group Contributions
The Final Presention is a group presentation, however some marks will be allocated to individuals. All members of the group must present. All members will receive the same group score (unless exceptional circumstances, e.g. one member does not present). The individual score will be based on how you present your part and answer questions. Different students in your team may receive different individual scores.
The Project Reflection is individual work.
Marking Criteria
Your Final Presentation will be marked based on:
- Content quality and relevance [Group]. For example: sufficient technical depth, appropriate contributions presented, interesting and clearly explained content, reflections on learnings.
- Presentation organisation and flow [Group]. For example: keeping to time limit, preparedness, visual aids, quality of demonstrations.
- Presentation skills [Individual]. For example: speaking skills, confidence, responding to questions, demonstrated understanding of the content.
Your Project Reflection will be marked based on:
- Genuine and in-depth self-assessment of your contribution to the project
- Ability to identify specific, relevant activities to fill in gaps that will contribute to future career goals
- Publication of at least one technical artefact to personal public portfolio
Failure to publish at least one technical artefact to a personal public portfolio may result in 0 marks for the Project Reflection.
This unit is 12 credit points, and therefore requires significant amount of work every week with frequent assessment deadlines. If you get behind and miss a deadline, then it will be very hard for you to catch up. Therefore, for all assessments any late submissions more than 7 days after the original deadline will receive 0 marks.
Detailed marking criteria are available on Moodle.
- Demonstrate productive participation and contribution to a project team or work environment
As a CQUniversity student you are expected to act honestly in all aspects of your academic work.
Any assessable work undertaken or submitted for review or assessment must be your own work. Assessable work is any type of work you do to meet the assessment requirements in the unit, including draft work submitted for review and feedback and final work to be assessed.
When you use the ideas, words or data of others in your assessment, you must thoroughly and clearly acknowledge the source of this information by using the correct referencing style for your unit. Using others’ work without proper acknowledgement may be considered a form of intellectual dishonesty.
Participating honestly, respectfully, responsibly, and fairly in your university study ensures the CQUniversity qualification you earn will be valued as a true indication of your individual academic achievement and will continue to receive the respect and recognition it deserves.
As a student, you are responsible for reading and following CQUniversity’s policies, including the Student Academic Integrity Policy and Procedure. This policy sets out CQUniversity’s expectations of you to act with integrity, examples of academic integrity breaches to avoid, the processes used to address alleged breaches of academic integrity, and potential penalties.
What is a breach of academic integrity?
A breach of academic integrity includes but is not limited to plagiarism, self-plagiarism, collusion, cheating, contract cheating, and academic misconduct. The Student Academic Integrity Policy and Procedure defines what these terms mean and gives examples.
Why is academic integrity important?
A breach of academic integrity may result in one or more penalties, including suspension or even expulsion from the University. It can also have negative implications for student visas and future enrolment at CQUniversity or elsewhere. Students who engage in contract cheating also risk being blackmailed by contract cheating services.
Where can I get assistance?
For academic advice and guidance, the Academic Learning Centre (ALC) can support you in becoming confident in completing assessments with integrity and of high standard.
What can you do to act with integrity?
