Wireless networks & Security

 

COURSEWORK Assignment Specification

 

Module Title	Wireless networks & Security
Module number:	xxxxxxx
Module Tutor Name(s):	xxxxxxxxxx
Academic Year:	2020/21
% Weighting (to overall module):	50%
Coursework Title:	Exploiting vulnerabilities in WLAN
Average Study Time Required by Student:	100 study hours assignment

 

Dates and mechanisms for Assessment Submission and feedback

 

Date of Handouts to Students: 13/10/2020

Mechanism for Handout to Students: elp

Date and Time of Submission by Student: on or before 24th Jan 2021 by 15:59

Mechanism for Submission of Work by Student: Turnitin

Date by which Work, Feedback and Marks will be returned to Students:

Mechanism for return of assignment work, feedback and marks to students: via Gradebook/Turnitin

Introduction

Assignment Tasks

You are to perform a study on various 802.11 wireless networks in order to choose a suitable security measures that should be put in place for a given scenario.

This assignment is divided in two parts. The study will be partially theoretical and technical. The technical part will require you to evaluate the effectiveness of using various standards against known attacks. You will then in part B identify what are the security measures that the company in the chosen scenario should consider implementing.

 

Part A: Technical flaws research

You will need to research several known security flows on the various 802.11 security protocols. You should also consider the various possible types of deployment such as in infrastructure deployment of 802.11 or in enterprise mode.

 

·         Research how to bypass WLAN authentication if SSID is hidden and if administrators use MAC filtering.

·         Research WLAN encryption flaws (WEP, WPA2).

·         Research 802.11 clients and identify flaws and they can be exploited.

 

 

Part B: Research Based Work

Based on your findings in part A, you are required to analyse results obtained and choose suitable security measures for your chosen scenario. Following this, you are expected to defend your security choices by comparing your justifications with different research papers discussing the effectiveness of wireless security protocols in different environments.

 

Effectiveness of the chosen security measures should be evaluated in term of how they can be exploited (if possible), how suitable they are for the environment they will be used in and the threats that the scenario is subject to.

 

You will need to choose one scenario from the list below:

 

·         A small company that only allows staff to access the network.

·         A coffee shop that allows its customers to access the wireless network.

·         A large company that has various levels of access controls in their company.

·         Guests only network where people can use the network for a specific time.

·         A home family wireless network.

 

Learning Outcomes

The following Learning outcomes will be addressed in this assignment:

•    LO2. Be able to describe, explain critically and assess wireless and mobile data communication technologies deployed along with associated security issues.

 

 

•    LO3. Critically analyse 802.11 protocol information and demonstrate skills in designing secure wireless networks

 

 

•    LO4. Apply suitable security measures to protect wireless networks against known weaknesses

 

 

Marking Schemes

It is advantageous if your report is structured in a manner that reflects the allocation of marks below:

 

Abstract (max 100 words (discuss scenario))	5
Introduction	15
Technical flaws - Research how to bypass WLAN authentication if SSID is hidden and if administrators use MAC filtering.	15
Technical flaws - Research WLAN encryption flaws (WEP, WPA2).	10
Technical flaws - Research 802.11 clients and identify flaws and they can be exploited	15
Choose the most suitable security measures for your scenario and justify your choice.	15
Research your chosen security measures in order to defend your choices.	10
Conclusion	10
References	5
Appendix (if needed)

 

Instruction

Your work must be presented in the form of a short technical paper and be no longer than 7 sides plus a facing page that includes the abstract. This should be formatted for A4 page size and use a font size no smaller than 10.

Any work beyond the page limit will be ignored from a marking perspective. For completeness, you may if you wish include additional material in an appendix, e.g. screenshots of all your experiments, but this will not contribute to the marks and you should not explicitly refer to any appendix to illustrate results etc. You could use an appendix to show all screenshots of all labs.

Read More

Database design and Implementation

 Faculty of Computing, Engineering and Media (CEM) – Resit Course work Specification 2020/21

 

Module name:	Database Systems and Design
Module code:	IMAT5103
Title of the Assignment:	Database design and Implementation (EER Modelling and SQL)
This coursework item is:	Summative
This summative coursework will be marked anonymously			Yes
The learning outcomes that are assessed by this coursework are: 1.    Select and comprehensively analyse a problem domain so as to identify data requirements in businesses 2.    Design and implement a database system for the identified requirements using database modelling techniques and appropriate data description and manipulation languages
This coursework is:	Individual
This coursework constitutes 70 % to the overall module mark.
Date Set:	1st November, 2020
Date & Time Due:	14th January, 2021, @ 12:00pm (midday)
Your mark and feedback will be available to you on: If for any reason this is not forthcoming by the due date your module leader will let you know why and when it can be expected. The Head of Studies (headofstudies-tec@dmu.ac.uk ) should be informed of any issues relating to the return of marked coursework and feedback.		10th February, 2021
When completed you are required to submit your summative coursework to: Blackboard shell via TurnitIn;
Late submission of coursework policy: Late submissions will be processed in accordance with current University regulations which state: “The time period during which a student may submit a piece of work late without authorisation and have the work capped at 40% [50% at PG level] if passed is 14 calendar days. Work submitted unauthorised more than 14 calendar days after the original submission date will receive a mark of 0%.  These regulations apply to a student’s first attempt at coursework. Work submitted late without authorisation which constitutes reassessment of a previously failed piece of coursework will always receive a mark of 0%.”
Academic Offences and Bad Academic Practices: These include plagiarism, cheating, collusion, copying work and reuse of your own work, poor referencing or the passing off of somebody else's ideas as your own. If you are in any doubt about what constitutes an academic offence or bad academic practice you must check with your tutor. Further information and details of how DSU can support you, if needed, is available at: http://www.dmu.ac.uk/dmu-students/the-student-gateway/academic-support-office/academic-offences.aspx and http://www.dmu.ac.uk/dmu-students/the-student-gateway/academic-support-office/bad-academic-practice.aspx
Tasks to be undertaken: You are tasked to develop a database design (both conceptual and logical) for an appropriate business situation of your choice, and then implement and subsequently query an ORACLE database that is derived from your database design.     Task 1: Selection of the case upon which the database design and implementation is to be based   You need to identify a suitable scenario and ensure that your business situation is suitably complex to provide you with at least four strong entities, and at least one specialisation: generalisation structure, Once researched and identified, a written scenario needs to be produced that (a) provides relevant background information on the organisation (e.g., its purpose, its principal operations/structure, its products/services, its target markets, etc.), and (b) provides an overview of what operations a database would need to support Task 2: Provide a conceptual database design for your scenario   Provide a conceptual database design for your scenario. The EER Diagram needs to show any weak and strong entities, the primary keys for strong entities, and any relationships between entities (including any generalisation: specialisation structures). For each entity, there should be an associated written list of all the attributes that the entity possesses which are not written on the EER Diagram. Any assumptions made during conceptual database design (i.e., anything that you assume that is not written in your scenario) should be listed.     Task 3: Create the tables using Oracle DBMS   From your conceptual database design, derive a corresponding set of well-normalised tables.  Remember to indicate all primary and foreign key fields for each of the tables using suitable and consistent notation. All key and any non-key attributes should be listed within each table. Create the tables using Oracle DBMS. You need to create all the tables that you identified within your logical database design. Populate your Oracle tables with some fictitious yet appropriate test data (about FIVE records per large table and TEN records per small table (or as many rows as is relevant) should be enough).   Task 4: SQL Query writing   Define and run the following queries and justify as to why the query would be useful to your case study organisation:   ·         Selection of particular table columns ·         Use of count and/or another similar mathematical expression ·         Use of a sorting/ordering facility ·         A condition using “<”, “>”, LIKE etc. ·         A condition using IN, NOT NULL, or similar. ·         A sub-query
Deliverables to be submitted for assessment:   The results of the above Tasks need to be submitted, i.e.: • Your case scenario, EER Diagram, and the whole conceptual database design. • The logical database design that follows from your conceptual database design. • A print out of each of the tables (i.e., the extension of each table) that you have created in ORACLE and the SQL code required to create them (including the code for the integrity rules). • A print out of each of the queries you devised, showing both the SQL query statement and the query result. You should provide a brief explanation of what you expect each query to achieve and why you think this query is relevant to your case scenario. ONE electronic copy containing all of the above aspects must be submitted for summative assessment via Blackboard’s TurnitIn. You are permitted to attach a small amount of additional and appropriate evidence to support one or more of your claims, should this be necessary. Sometime after submission, you may be asked to attend a viva lasting for up to 15 minutes with one or more tutors. You may be selected for a viva for a variety of reasons; for instance, to verify that the work you have submitted is understood/written by you, to clarify aspects of the work to aid marking or just because you were randomly selected. Your mark may go up or down as a result of a viva.  Failure to attend a viva, if you have been asked to do so, may result in you obtaining zero marks for the entire assessment.
How the work will be marked:   In order to achieve a 70%+ (Distinction) grade, the work must be excellent in almost all respects, only very minor limitations. In order to achieve a 60-69% (Merit) grade, the work should show strength in most respects. Whilst there may have some limitations in one or two areas, it is still a very good piece of work. In order to achieve a 50-59% (Pass) grade, the work should be of a satisfactory standard, showing strength in some areas, but typically let down by some other aspects. A 0-49% (Fail) grade will be given where the work contains serious errors/limitations. (0% is used either when nothing is correct or no attempt is made.)   Please refer to the criteria marking grid bellow for the details of the assessment of the work.
Module leader/tutor name:	Eirini Kalaitzopoulou
Contact details:	erini.kalaitzopoulou@dmu.ac.uk,

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Scenario, Conceptual and Logical Database Design & Oracle SQL implementation/querying

 

Criteria	0 to 49 %	50 to 59 %	60 to 69 %	70 to 100 %
Scenario – content appropriate and sufficient 20%
EERD – content quality, contains minimum standard of complexity and matches scenario 20%
Assumptions complete and appropriate to scenario 10%
Associated attribute lists appropriate and complete 10%
Tables – quantity correct and in appropriate format, with primary/foreign keys indicated and appropriate. Well normalised tables, with all appropriate non-key attributes. 20%
Development of the required syntactically correct queries; that together cover the required SQL SELECT statement elements as defined, with reason(s) for each query choice. 20%
Overall Grade

 

 

Read More