NETWORK SECURITY DESIGN PROPOSAL FOR SMALL OFFICE

Software Requirements
Specification
For
PACKET SNIFFING USING WIRESHARK
Submitted By:
Aditya Dixit & Swapnil Kushwaha
CSE13
Group – B
16BCS1966 & 16BCS1786

Table of Contents

16BCS1966 & 16BCS1786 1|Page

 NETWORK SECURITY DESIGN PROPOSAL FOR SMALL OFFICE

1. Introduction .............................................................................................................................1
1.1 Purpose .......................................................................................................................................... 1
1.2 Document Conventions ................................................................................................................. 1
1.3 Intended Audience and Reading Suggestions ................................................................................1
1.4 Product Scope ................................................................................................................................ 1
1.5 References ......................................................................................................................................1
2. Overall Description .................................................................................................................2
2.1 Product Perspective ........................................................................................................................2
2.2 Product Functions ...........................................................................................................................2
2.3 User Classes and Characteristics ....................................................................................................2
2.4 Operating Environment ..................................................................................................................2
2.5 Design and Implementation Constraints ........................................................................................2
2.6 User Documentation ...................................................................................................................... 2
2.7 Assumptions and Dependencies .....................................................................................................3
3. External Interface Requirements ...........................................................................................3
3.1 User Interfaces ................................................................................................................................3
3.2 Hardware Interfaces ........................................................................................................................3
3.3 Software Interfaces .........................................................................................................................3
3.4 Communications Interfaces ............................................................................................................3
4. System Features .......................................................................................................................4
4.1 Physical connection ....................................................................................................................... 4
4.2Routing …………………………………………………………………………………………….4
4.3Applying security…..........................................................................................................................4
5. Other Nonfunctional Requirements ......................................................................................5
5.1 Performance Requirements ............................................................................................................5
5.2 Safety Requirements ......................................................................................................................5
5.3 Security Requirements ...................................................................................................................5
5.4 Software Quality Attributes ...........................................................................................................5
5.5 Business Rules ...............................................................................................................................5

16BCS1966 & 16BCS1786 2|Page

 NETWORK SECURITY DESIGN PROPOSAL FOR SMALL OFFICE

1. Introduction

1.1 Purpose

The scope of our project. Packet sniffing is that we can aware other people to use public internet
carefully and make an office network more secure from outer as well as inner threats and can
even implement those protocols in real life.

1.2 Document Conventions

The font style is Times new Roman throughout with headings being bold and of larger size in
comparison to the whole body of content.

1.3 Intended Audience and Reading Suggestions

The document is intended for developers, project managers, staff, users, testers, and
documentation writers. The rest of this SRS contains the all information about project in an
ordered manner. The sequence for reading the document is beginning with the overview sections
and proceeding through the sections that are most pertinent to each reader type.

1.4 Product Scope

The purpose of the product is to benefit the customer with more secure protection of the data
form evert way possible and we can implement this security on basis of the requirement of the
customer ie advanced security or standard .

1.5 References

There are no as such documents or Web addresses to which this SRS refers. It is complete within
itself and provides all the necessary information.

16BCS1966 & 16BCS1786 3|Page

 NETWORK SECURITY DESIGN PROPOSAL FOR SMALL OFFICE

2. Overall Description
1.About The Project
This project aims at developing a Network Packet Sniffer. Network Packet Sniffer is a piece of
software that monitors all network traffic. This is unlike standard network hosts that only receive
traffic sent specifically to them. As data streams flow across the network, the sniffer captures
each packet and eventually decodes and analyzes its content. For network monitoring purposes it
may also be desirable to monitor all data packets in a LAN and to mirror all packets passing
through a shared bus.

This system is thus very useful to the users and a network administrator in particular who is
generally responsible for monitoring things on a network.

This system is a network analyzer (also known as protocol analyzer & packet sniffer), it
performs real-time packet capturing, 24x7 network monitoring, advanced protocol analyzing, in-
depth packet decoding, and automatic expert diagnosing. It allows you to get a clear view of the
complex network, conduct packet level analysis, and troubleshoot network problems.

This system is useful for a network administrator who needs to identify, diagnose, and solve
network problems, a company manager who wants to monitor user activities on the network and
ensure that the corporation's communications assets are safe, or a consultant who has to quickly
solve network problems for clients.

This provides an administrator with a full set of reports such as Summary view, Endpoints view,
and Protocols view.

2.Project Functions

The project main function is that the user is able to see various ways in which their data and
network are protected with a working model.

2.1 User Classes and Characteristics

There are various user classes that will use this project. User classes may be differentiated based
on frequency of use, subset of product functions used, technical expertise, security or privilege
levels, educational level, or experience. The one of the user class is the common people that will
look into the standard security and the other are the higher officials those who provide higher
security for their firm.

2.2 Operating Environment

The project Network Security For Small Office can be operated on all the cisco packet tracer

2.3 Design and Implementation Constraints

16BCS1966 & 16BCS1786 4|Page

 NETWORK SECURITY DESIGN PROPOSAL FOR SMALL OFFICE

The design of are project would be based on the small office with a all access granted master
node and rest the working nodes

2.4 User Documentation

There is no user document as such required along with this as it is very much simple to use and
execute.

2.5 Assumptions and Dependencies

This project does not have any dependencies it is not affected by any external factor as long as
all the required requirements are fulfilled properly. There are no dependencies in this project so
no additional documentation required.

16BCS1966 & 16BCS1786 5|Page

 NETWORK SECURITY DESIGN PROPOSAL FOR SMALL OFFICE

3. External Interface Requirements

3.1 User Interfaces

The user interface is created with the help of Cisco Packet Tracer. This gives a attractive look to
the project with its pc and other devices connected with coloured wires
3.2 Hardware Interfaces

The hardware interface between the user and the software is the computer screen i.e. through
which the interaction is made complete. The packet tracer is displayed on the screen that the user
gets to see and act accordingly.

3.2 Software Interfaces

The Cisco Packet Tracer is the only software the we require for this project

3.3 Communications Interfaces

This project does not require any such interfaces as email, web or any other internet protocols as
it does not require any internet connection to work on. There are no protocols required in the
making or execution of the project. But we will use those internet protocol in the model of our
project

16BCS1966 & 16BCS1786 6|Page

 NETWORK SECURITY DESIGN PROPOSAL FOR SMALL OFFICE

4. System Features
This template illustrates organizing the functional requirements for the product by system
features, the major services provided by the project.

4.1 physical connection

In this we will firstly physically place all the the devices on the packet tracer and try to connect
them with wires or wireless on the basis of the requirement of the customer the connection ports
should be checked and correct wires should be used
4.2 routing
Now we try to connect these devices with different routing techniques like
 RIP
 EIGRP
 OSPF
So that the devices can transfer data with each other

4.2 Applying security

Now will apply security protocols to the devices where we want security to be implemented we
will apply

 NAT
 PAT
 PORT SECURITY
 ACL etc

16BCS1966 & 16BCS1786 7|Page

 NETWORK SECURITY DESIGN PROPOSAL FOR SMALL OFFICE

5. Other Nonfunctional Requirements

5.1 Performance Requirements

There is no any particular performance required for the completion of this project on time and
with all functionality.

5.2 Safety Requirements

This project is not any new designed but a addition the the previous securitty
5.3 Security Requirements

There are no as such security requirement as no confidential data is used in it that can be
misused.

5.4 Software Quality Attributes

The quality of the software is up to the mark. It is very clear and easily executable to get the end
result we want.

16BCS1966 & 16BCS1786 8|Page