Assignment Information
Module Name: Security
Module Code: 6005CEM
Assignment Title: Coursework
Assignment Due: 1st December 2025, 18:00 UK time
If you do not pass this assessment you may have an opportunity to resit it. If you do need to resit, you will be asked to use the feedback provided to revise your original submission , so that it meets the
pass requirements for the module. You must clearly indicate the changes you have made in the new submission. Please check your SOLAR results and the submission links on your Aula module page to see when the resit is due.
Assignment Credit: 20 credits
Word Count (or equivalent): 1500 words +/- 10%
Assignment Type: Percentage Grade (Applied Core Assessment). You will be provided with an
overall grade between 0% and 100%. To pass the assignment you must achieve a grade of 40% or above.
Assignment Task
The Coursework component consists of practical work on the development of a secure IT system. In this coursework you are required design and develop a secure web application. Details of the design criteria can be found in the attached specification document. Your submission should include a report to provide details of the design of the system, discussing and justifying any security related decisions. The design of the system should be fully complete. While you are not expected to provide a fully completed working production system, you should submit a working prototype with some core functioning features demonstrating the implementation of secure components.
The submitted coursework should contain:
Part 1: Security analysis report.
In this part you should give an overview of the high level design for the site. You should discuss and evaluate the security considerations for your design.
• An overview of potential security issues that could effect each element of the design requirements
• Discussion of different Authentication and Authorisation strategies for the site.
• Discussion and recommendations of design decisions that deal with potential security / data protection elements.
For example: When discussing User based functionality, you will want to discuss:
• Session Management Strategies, how the site keeps track of user state and its impact.
• Password management, and storage
• Details of different user access levels, and requirements.
After you have implemented the application, you will use both static and dynamic analysis tools (e. Bandit, ZAP Proxy) to audit your web application. Highlight the issues found by the tools and discuss their severity, impact and mitigation.
You are expected to use the literature to support the design decisions, justifying your design choices against current best practice.
Part 2: Design and Implementation
For this part you are expected to provide the full design and implementation details of the components identified in part one of the report. This should include the specifics of how you address the issues identified, including justification and supporting your design with the literature.
You should supply the design of the individual components, to support the high-level design. This must include diagrams showing information flow, and code examples.
Submission Instructions:
• Submit the coursework by the due date using the link on Aula.
• Your assignment should be submitted as a single Microsoft Word document containing the design report.
• Your application source code must be submitted via Coventry University's Github
https://github.coventry.ac.uk/ (NOT github.com). You should include a clear link to the Github repository in an appendix in your report.
• Important: Your Github repositories, should be set to private, with the relevant teaching
staff added as collaborators. Having a publicly available repository could lead to an
academic misconduct case being raised against you, as people have been known to steal work from other students' repos.
Marking and Feedback
How will my assignment be marked?
Your assignment will be marked by the module team.
How will I receive my grades and feedback?
Provisional marks will be released once internally moderated.
Feedback will be provided by the module team alongside grades release on Turnitin.
Your provisional marks and feedback should be available within 2 weeks (10 working days). What will I be marked against?
Details of the marking criteria for this task can be found at thebottom of this assignment brief.
Assessed Module Learning Outcomes
The Learning Outcomes for this module align to the marking criteriawhich can be found at the end of this brief. Ensure you understand the marking criteria to ensure successful achievement of the assessment task. The following module learning outcomes are assessed in this task:
1. Critically evaluate a range of encryption and authentication methods for a given set of requirements.
2. Evaluate different approaches to assessing a systems security and use these to critically evaluate the security of a system.
3. Utilise systematic knowledge to create secure environments at the host or network level.
4. Develop and evaluate software that addresses the most common and most severe security concerns.