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

 Software Project Plan

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

2.1 Project Goals............................................................................................................................3
2.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 Internet
came into existence. The need for security systems against the external attacks from the
hackers has always been a very crucial requirement. One vital type is the Intrusion Detection
System (IDS). Here are two major categories of the analysis techniques of IDS: the anomaly
detection and the misuse detection. The focus mainly is on the misuse detection, which is
collected the attack signatures in a database as the same as virus protection software to detect

2

the relate attacks. We propose an algorithm to use the known signature to find the signature of
the related attack quickly.
2. GOALS AND SCOPE
2.1 PROJECT GOALS
Project Goal Priority
Functional Goals:
Data Set
Data Set analysis
Support calculation and
candidate set generation
Frequent Item set
Generation
Technological Goals:
Integrated Simulation and
testing.
Quality Goals
Use of Dataset containing
the Pre-defined set of
attack signature.
Frequent Item Set
Constraints:
Known attack signature
Dataset
2.2 PROJECT SCOPE
2.2.1 Included
The tangible deliverables of this System are:-
Software Project Plan
Comment/Description/Reference
Goals that directly influence the performance of the
system
2 Data set Contains the Attack Signature which are
occurred previously in the network. Misuse Detection
mainly based on the attack signatures.
1 Reading the data set and used it for further processing.
3 Analysis of the attack signature dataset and support
calculation of each attack. Also generation of the
candidate set for the next iteration.
3 Generation of Frequent item set in each iteration from
the candidate set. This is depends on the comparison
with the minimum support.
Goals that will have direct influence on technological
aspects of the system
1 Use of generated frames for Testing of existing
deployments.
1 This should enable system to analyze the attack
signature and association between the attack
signatures.
2 This should help in generation of the attack signature.
1 The misuse detection system is concerned with the
known attack signature.
3
 Software Project Plan

1. A Source code of Modules that include

a. Graphical User Interface Module
b. Signature Data set analysis Module
c. Generation of Frequent Item Set Module
d. Generation of Candidate Set Module
2. A Project Report
3. Help Files and configuration files

3. SCHEDULE AND MILESTONES

Milestones Description Milestone Criteria Planned Date

M0 Start Project 2009-10-10
Understand the requirements Research on the domain to 2009-10-15
and define project goals and clearly identify the
scope requirements and project
synopsis and SRS
delivered
M1 Start Planning 2009-10-25
Objectives and strategy Implementation language, 2009-10-30
defined and feasibility studied standards and protocols to
be followed are fixed
M2 Start Execution 2009-10-05
Complete project plan defined User interface, libraries 2009-10-08
and reusable modules found and project plan
identified reviewed.
M3 Confirm Execution 2009-10-01
First version completed All the basic functionalities 2009-10-05
tested and verified
M4 Start Introduction 2009-10-10
First module of the project New functionalities and 2009-10-15
ready to be delivered enhancements finished
M5 Release Project 2009-10-20
Final system completed with Project system tested, 2009-01-25
enhancements documentation reviewed
M6 Close Project 2009-02-01