Detecting Anonymous Proxy Usage Final Report

Download 0.59 Mb.

Page	8/20
Date	16.07.2017
Size	0.59 Mb.
	#23501

1 ... 4 5 6 7 8 9 10 11 ... 20

4.5 Risk Management
5. Design

4.4 Working with Supervisor

I have arranged with my supervisor to have a meeting every week. This meeting is scheduled for Thursdays after class. The meeting is generally face to face, however if either of us cannot make it or any major problems arise, we can keep in contact via email or phone. Each meeting has to be well prepared for in order for me to get the most out of the meeting. The supervisor has set out clear goals that he wants met for the project. The first part of the project that has to be completed is the interim report. Table shows what has to be done before, during and after the meeting.

Before Meeting	During Meeting	After Meeting
Make sure all the tasks from last week’s meeting are completed	Discuss possible solutions for any problems encountered	Read over notes taken during the meeting
Make a list of any problems encountered	Discuss goals/tasks for next week	Create a list of the goals/tasks required to be completed
Make a list of any other relevant questions	Take notes throughout the meeting	Assess any risks that could occur from the goals/tasks
	Discuss any other questions related to the project

Table - Working with Supervisor

Table outlines the main guideline to be taken when having a meeting with the supervisor; however this can be altered if anything else related to the project occurs.

4.5 Risk Management

Risk management is an important part to any project. To ensure my project is completed in time I have made a table to analyse the risks involved and to plan the best way to overcome these risks. The possible risks that could occur in the project can be seen in Table , this table is updated weekly after my supervisor meeting.

Risks	Event type	Classification	RAG Grade	Trigger	Alleviate Method
PC Failure	Even-Driven	Non-Technical	8	Noticing irregularities with the computer	Contingency- Have a backup PC ready
Loss of work due to virus or crash	Event-Driven	Non-Technical	10	N/A	Avoidance- Always back-up work on USB pen and use Google Drive
Illness	Event-Driven	Non-Technical	3	N/A	Avoidance- Try to ensure work is completed ahead of schedule
Family Issue	Event-Driven	Non-Technical	3	N/A	Avoidance- Try to ensure work is completed ahead of schedule
Insufficient technical ability	Evolving	Technical	15	Unfamiliar with development language	Avoidance-Assign time to complete more tutorials Contingency- Inform supervisor about difficulties
Falling behind on the project plan	Evolving	Non-Technical	10	Milestones taking longer than expected	Avoidance- Keep monitoring the milestones and try to get them completed ahead of schedule

Table - Risk Management

5. Design

This section will detail the planning and design of the system. Within this section, the technical details and the different software required for the system will be discussed.

It is important for network administrators to monitor traffic that is entering and exiting the network. Security is very important therefore it is vital that any proxy or onion routing applications used can be identified. If a proxy is in use, more often than not it is not being used for legitimate reasons. There can however be a valid reason for someone in the company to use a proxy, for instance, if they wanted to block certain web scripts from being used or if they needed to test an application that is being mistakenly blocked online, the user should contact the network administrator to allow the blocked application to be made available, the latter however should not happen.

Download 0.59 Mb.

Share with your friends:

1 ... 4 5 6 7 8 9 10 11 ... 20