INTRUSION DETECTION

TITLE OF THE PROJECT: INTRUSION DETECTION PROJECT ARCHITECTURE: N-Tier SDLC METHODOLOGIES: Waterfall/Spiral Model
COURSE: ROLL NO: NAME OF THE STUDENT: TECHNOLOGY AND LANGUAGE: INTERNAL GUIDE: E-MAIL ID: MOBILE NO (STUDENT):

JAVA

ABSTRACT OF THE PROJECT: INTRODUCTION:

Intrusion detection in Wireless Sensor Network (WSN) is of practical interest in many applications such as detecting an intruder in a battlefield. The intrusion detection is defined as a mechanism for a WSN to detect the existence of inappropriate, incorrect, or anomalous moving attackers. In this paper, we consider this issue according to heterogeneous WSN models. Furthermore, we consider single detection models

FUNCTIONAL REQUIREMENTS:
Following is a list of functionalities of the system. Functional Requirements means interface between the user and the hardware. In this project, we discuss the functionality of the each module.The functional Requirements are 1. Intrusion detection WSNs by characterizing intrusion detection with respect to the network parameters. 2. The sensed information provided by a single sensor recognizing the intruder.

3. We are detecting the intruder from single sensor .

NON-FUNCTIONAL REQUIREMENTS:
24 X 7 availability Better component design to get better performance at peak time Flexible service based architecture will be highly desirable for future extension

EXISTING SYSTEM:
The existing system is manual and the manual system works in the following way: DISADVANTAGE: 1. In single-sensing detection, At a time only one intruder detected by the wsn. 2. Our work was according to single sensor in wireless sensor network 3. The sensed information provided by a single sensor might be inadequate for recognizing the intruder. 4. So that there is no guarantee for our information has been sent securely. 5. Data will not routed if primary detector fails.

PROPOSED SYSTEM:
To overcome all the difficulties of the existing system the management has proposed automated the whole system and the development of the new automated system contains the following activities, which try to automate the entire process keeping in view of the database integration approach.

1.

Intrusion detection in heterogeneous WSNs by characterizing intrusion detection with respect to the network parameters

2. Two detection models are: 3. Intrusion detection in heterogeneous WSNs by characterizing intrusion detection with respect to the network parameters 4. Detection models are: i. Single-sensing detection 5. We are detecting the intruder from single sensor .

MODULES: Constructing Sensor Network Packet Creation Find authorized and un authorized port Constructing Inter-Domain Packet Filters Receiving the valid packet

MODULE-1: In this module, we are going to connect the network . MODULE-2: In this module, browse and select the source file. MODULE-3: The intrusion detection is defined as a mechanism for a WSN to detect the existence of inappropriate, incorrect, or anomalous moving attackers. MODULE-4: If the packet is received from other than the port no it will be filtered and discarded. This

filter only removes the unauthorized packets and authorized packets send to destination. MODULE-5: In this module, after filtering the invalid packets all the valid .Packets will reach the destination. USERS OF THE SYSTEM:
This system should be designed to support the following users: user

ENVIRONMENT:
OPERATING SYSTEM SERVER: Microsoft Windows XP/2000 or Higher CLIENTS: any web browser DOCUMENTATION TOOLS: MS Office 2003/2007 DRAWING TOOLS: IBM Rational Rose Enterprise, MS Office Visio 2007 USER INTERFACE: HTML WITH JAVA SCRIPT AND CSS CODE BEHIND: JSE,JEE

REQUIREMENTS:

HARDWARE REQUIREMENTS: Number 1 Description PC With Minimum 20GB Hard-Disk And 1GB RAM

SOFTWARE REQUIREMENTS: FRONT END TOOL USED OPERATING SYSTEM

: Java : JFrameBuilder : Windows Xp

MILESTONES:
No. Milestone Name Requirements Specification Milestone Description Remarks

Technology Familiarization

Complete specification of the system including defining hierarchies constitutes this milestone. A document detailing the same should be written and a presentation on that be made. Understanding of the technology needed to implement the project.

Attempt should be made to add some more relevant functionality other than those that are listed in this document.

Database Creation

A database of at least 10 entries of users with at least 1 should application admin.

High-level Detailed Design

and

Development of Front End Functionalities.

Listing down all possible scenarios and then coming up with flow-charts or pseudo code to handle the scenario. Implementation of the main screen giving the login, screen that follows the login giving various options, screens for each of the options The front-end developed in the

The presentation should be from the point of view of being able to apply it to the project, rather than from a theoretical perspective. It is important to finalize on the database at this stage itself so that development and testing can proceed with the actual database itself. The scenarios should map to the requirement specification

During this milestone period, it would be a good idea for the team to start working on a test-plan for the entire system. This test-plan can be updated as and when new scenarios come to mind.

Integrating the

Front-end with the Database

Integration Testing

Final Review

earlier milestone will now be able to update the database. Other features should be functional at this stage. In short, the system should be ready for integration testing. The system should be thoroughly tested by running all the test cases written for the system (from milestone 5). Issues found during the previous milestone are fixed and the system is ready for the final review.

Another 2 weeks should be there to handle any issues found during testing of the system. After that, the final demo can be arranged. During the final review of the project, it should be checked that all the requirements specified during milestone number 1 are fulfilled

THE FOLLOWING STEPS WILL BE HELPFUL TO START OF THE PROJECT:

Study and be comfortable with technologies such as: HTML, JAVASCRIPT, CSS, JSP AND SQL SERVER. Gather some knowledge of product hierarchies and maintenance before starting the design. Create a user database with different access levels. Start with creating the login screen. Create menus for navigation and group the functionalities as sub menus. Create the help-pages of the application in the form of FAQ. This will helps user.