Project Proposal (Santosh a

Embed Size (px)

Citation preview

  • 8/3/2019 Project Proposal (Santosh a

    1/5

    Project Specification Document

    1. Project Details

    Project Title: Different Methodology to Secure the Database

    Students Name and Id: Santosh Timilsina 11069922/1

    1st Supervisor name: Mr Tashi Wangdue

    2nd Supervisor: Mr Prakash Shrestha

    Date Approved: 13th Nov, 2011

    1 Introduction to the ProjectDatabase technologies are a core component of many computing systems. They allow data to be

    retained and shared electronically and the amount of data contained in these systems continues to grow

    at an exponential rate.

    Database security is a growing concern evidenced by an increase in the number of reported incidents of

    loss of or unauthorized exposure to sensitive data. The Privacy Rights Clearing House (2010) reports

    that more than 345 million customer records have been lost or stolen since 2005 when they began

    tracking data breach incidents and the Ponemon Institute reports the average cost of a data breach has

  • 8/3/2019 Project Proposal (Santosh a

    2/5

    tracking data breach incidents and the Ponemon Institute reports the average cost of a data breach has

    This case study will be carried out in Global Bank, situated in Kathmandu Nepal, in a database

    environment using Oracle 10g as Database management System.

    2 Aims of the project

    The aim of this project is to find out how database backup and recovery methodology, among different

    methodology to secure database can be used to secure the data of Global bank Ltd, based on the

    different cases of problem faced. So that at any circumstances like system failure, system crash, database

    crash, theft hacking etc all the data are retained properly without loss and inconsistency.

    3 Deliverables of the project

    With the end of the project, a comprehensive report of different cases of database security related

    problems solved using the backup and recovery methodology of database security would serve as a

    reference guide and solutions for similar problems in future.

    The following things are delivered at the end of the project:

    Database problems log: It logs different problems of database faced.

    Maintenance log: It contains what different procedure followed to make the data into previous

    state.

  • 8/3/2019 Project Proposal (Santosh a

    3/5

    5 Estimated Costing and Resources Required

    This project requires a database environment to carry on this research. For this, I will use the real-time

    database environment of the Global Bank. And for the testing purpose, I would set up a testing

    environment on this laptop and carry out the testing.

  • 8/3/2019 Project Proposal (Santosh a

    4/5

    6 Bibliography/References

    Baker,W. H., Hutton, A., Hylender, C. D., Novak, C., Porter, C., Sartin, B., Tippett, P., & Valentine, J.

    A.(2009). The 2009 data breach investigations report. Verizon Business.

    Defense Information Systems Agency. (2004).Database security technical implementation guide, 7(1).

    Department of Defense.

    Ponemon, L. (2009).Fourth annual US cost of data breach study. Poneomon Institute sponsored by

    PGP Corporation.

    Privacy Rights Clearing House. (2010). Chronology of data breaches.

  • 8/3/2019 Project Proposal (Santosh a

    5/5

    ID Task Name Start Finish Duration

    Nov 2011 Dec 2011

    4/12 1/1 8/1 15/1 22/1 29/1 5/2

    2 1d11/8/201111/8/2011Project Selection andDetermining the objective

    4d11/13/201111/8/2011Planning and Project

    Approval

    5 54d1/15/201211/13/2011Initial study

    7 34d1/10/201212/2/2011Literature Reviews and

    Training

    8 0d1/15/20121/15/2012Interim Report

    10

    6

    3d11/11/201111/9/2011Feasibility study

    4 0d11/13/201111/13/2011Proposal Submission alongwith the Project Plan

    3

    1

    16d11/30/201111/13/2011Requirement Analysis

    3d3/23/20123/21/2012Installation of testingenvironment

    45d3/7/20121/16/2012Observation of problems

    12

    13

    15

    16

    17

    0d3/20/20123/20/2012Problem log and

    Maintenance log

    29d4/23/20123/21/2012Testing

    26d4/23/20123/25/2012Test each problem log

    0d4/23/20124/23/2012Test log

    12d5/8/20124/25/2012Evaluation of the Project

    18

    19

    6d5/1/20124/25/2012Evaluation of the project

    6d5/8/20125/2/2012Final Project Documentation

    20 0d5/9/20125/9/2012Final Report

    Jan 2012 Feb 2012 Mar 2012 Apr 2012

    12 /2 19 /2 26 /2 4 /3 11 /3 18 /3 25 /3 1/ 4 8/ 4 15/ 4 22 /4 29 /4 6 /5

    9 55d3/20/20121/16/2012Observation and inquiries

    11 10d3/19/20123/8/2012Inquiry of Problem andMaintainance

    14

    May 2012

    Santosh Timilsina