8/6/2019 4.SoftwareProjectPlan_NIDS

1/4

Vishwakarma Institute of Technology, Pune-37.

NIDS: Network Intrusion Detection System

Software Project Plan

Approvals Signature Block

Project Responsibility Signature Date

Project Guide (Internal)

Project Guide (External)

Documentation Leader

Table of Contents

1. OVERVIEW .....................................................................................................................2

Department of Computer Engineering

8/6/2019 4.SoftwareProjectPlan_NIDS

2/4

Software Project Plan

2. GOALS AND SCOPE .........................................................................................................3

2.1 Project Goals ................................................................................................................... .........32.2 Project Scope ...........................................................................................................................3

2.2.1 Included .........................................................................................................................................3

3. SCHEDULE AND MILESTONES ...........................................................................................................4

1. OVERVIEW

Network security has been a very important concept and issue, ever since the Internetcame into existence. The need for security systems against the external attacks from thehackers has always been a very crucial requirement. One vital type is the Intrusion DetectionSystem (IDS). Here are two major categories of the analysis techniques of IDS: the anomalydetection and the misuse detection. The focus mainly is on the misuse detection, which iscollected the attack signatures in a database as the same as virus protection software to detect

2

8/6/2019 4.SoftwareProjectPlan_NIDS

3/4

Software Project Plan

the relate attacks. We propose an algorithm to use the known signature to find the signature ofthe related attack quickly.

2. GOALS AND SCOPE

2.1 PROJECT GOALS

Project Goal Priority Comment/Description/Reference

Functional Goals: Goals that directly influence the performance of thesystem

Data Set 2 Data set Contains the Attack Signature which areoccurred previously in the network. Misuse Detectionmainly based on the attack signatures.

Data Set analysis 1 Reading the data set and used it for further processing.

Support calculation andcandidate set generation

3 Analysis of the a ttack signature dataset and supportcalculation of each attack. Also generation of thecandidate set for the next iteration.

Frequent Item setGeneration

3 Generation of Frequent item set in each iteration fromthe candidate set. This is depends on the comparisonwith the minimum support.

Technological Goals: Goals that will have direct influence on technologicalaspects of the system

Integrated Simulation andtesting.

1 Use o f generated frames for Testing of e xistingdeployments.

Quality Goals

Use of Dataset containingthe Pre-defined set ofattack signature.

1 This should enable system to analyze the attacksignature and association between the attacksignatures.

Frequent Item Set 2 This should help in generation of the attack signature.

Constraints:

Known attack signature

Dataset

1 The misuse detection system is concerned with the

known attack signature.

2.2 PROJECT SCOPE

2.2.1 Included

The tangible deliverables of this System are:-

3

8/6/2019 4.SoftwareProjectPlan_NIDS

4/4

Software Project Plan

1. A Source code of Modules that includea. Graphical User Interface Module

b. Signature Data set analysis Modulec. Generation of Frequent Item Set Moduled. Generation of Candidate Set Module

2. A Project Report

3. Help Files and configuration files

3. SCHEDULEAND MILESTONES

Milestones Description Milestone Criteria Planned Date

M0 Start Project 2009-10-10

Understand the requirements

and define project goals andscope

Research on the domain to

clearly identify therequirements and projectsynopsis and SRSdelivered

2009-10-15

M1 Start Planning 2009-10-25

Objectives and strategydefined and feasibility studied

Implementation language,standards and protocols tobe followed are fixed

2009-10-30

M2 Start Execution 2009-10-05

Complete project plan definedand reusable modulesidentified

User interface, librariesfound and project planreviewed.

2009-10-08

M3 Confirm Execution 2009-10-01First version completed All the basic functionalities

tested and verified2009-10-05

M4 Start Introduction 2009-10-10

First module of the projectready to be delivered

New functionalities andenhancements finished

2009-10-15

M5 Release Project 2009-10-20

Final system completed withenhancements

Project system tested,documentation reviewed

2009-01-25

M6 Close Project 2009-02-01

4