Sie sind auf Seite 1von 16

Presentation SRS(2.13.

3)
Team Guide-PROF. R. RADHAKRISHNAN

-By ,

Nishant Dwivedi
CSE 7th sem Section B
Class Rollno. 04

2.General Description
This section describes general factors that affect the
product and its requirements. This section does not
state specific requirements; it only makes those
requirements easier to understand.
2.1.Product Perspective
2.2.Product Functions
2.3.User Characteristics
2.4.General Constraints
2.5.Assumptions and Dependencies
2

2.1 Product Perspective

Clients

Ssl
request

re
pl
y

Access
To
Internet
request

Jdbc
Jdbc
intera
intera
ctions
ctions

(not
login)

re
pl
y

Applicat
ion
Layer
Firewall

Database
3

Contd.
DescriptionThere are two types of public usersUnregistered Users-can not access at all.
Registered Users
1.Clients before login need to login first.
2.After login firewall verifies their login info by accessing database.
3.After checking authenticity ;firewall allow clients to access internet.
4

2.2 Product Functions


1.Can block websites according to security policy.
2.Can restrict no. of users according to authentication done.
3.Can block dos ,distributed dos attacks.
4.Can resist viruses,worms,Trojan horses etc.
5.Can block malicious attacks.
6.helps in enforcing security policy of organization.
7.Provides good database security using encryption also,
where database stores required authentication information.
5

2.3 User Characteristics


There are two types of users1.Admin- uses firewall to enforce security policy.

2.Public Users-1.Unregistered Users-Need to register first.


2.Registered Users1.Can access internet after authentication by firewall.
2.Registered users will be protected from attacks using firewall.
3.Registered users will be allowed to open unblocked websites.

2.4 General Constraints


1.Firewall is built for running on windows or linux server only.
2.Firewall does not provide all the options for enforcing governing
policy.
3.It is in English and Hindi only.
4.It does not fully replaces need for internet security softwares.
5.It does not replaces intrusion detection softwares.
6.It emphasizes more on heuristic techniques.
7.Unregistered User need to register first.
8.It is an application layer firewall so is comparatively less good to
detect attacks on low layers.
7

2.5 Assumptions and Dependencies


1.Only registered users are accessing the internet
facilities provided by the organization.
2.Server used to run application is windows or linux
server.
3.It is an software application.
4.Server have jdk kit installed.
5.There is only one administrator who runs the server.
6.Governing policy is same for all registered users.
8

3 Specific Requirements
Each requirement in this section should be:
Correct
Traceable (both forward and backward to prior/future artifacts)
Unambiguous
Verifiable (i.e., testable)
Prioritized (with respect to importance and/or stability)
Complete
Consistent
Uniquely identifiable (usually via numbering like 3.4.5.6)
Attention should be paid to the carefuly organize the requirements presented
in this section so that they may easily accessed and understood.
9

3.1 External Interface Requirements


3.1.1 User Interfaces

User Interface is of two types-


1.User Interface for admin-
1.Interface for managing list of blocked websites.
2.Interface for managing set of rules
3.Interface for managing resistances for different types of attack
4.Interface for managing traffic like frequency of viruses, worms, Trojan
horses etc.
2.User Interface for Registered User-
1.Login Interface
10

3.1.2 Hardware Interfaces

11

3.1.3 Software Interfaces


1.Front End Client- Web Browser,Operating System for
registered user(any)
2.Server at admin site-Linux or windows server
3.Database-My sql
4.Back End-My sql

12

3.1.4 Communications Interfaces


1.SSL(Secured Socket Layer) will be used for encrypted
authentication
information in the network.
2.Other information transfer will be according to the site
,registered user is accessing on www(world wide web),
firewall will not change http or https into some other
protocol format.

13

3.2 Functional Requirements


Introduction -Registered user will have firewalled access to internet and
intranet facilities and admin will decide blocked list of sites and control
over traffic.

Inputs 1.Input for accessing internet and intranet facilitiesRegistered Users authentication information which includes1.Username
2.Password
2.Input for managing blocked list of websites-Admin can manage
list of blocked websites by the following steps 1.Admin can add websites in the list.
2.Admin can remove some websites in the list.
14

Contd.
Processing Processing will be done In following steps-

1.Database engine will process authentication using sql queries .


2.This authentication information will be matched to aes encrypted username and
passwords.
3.Firewalled network traffic (internet or intranet) will be provided on request.
4.Application layer firewall will inspect data for viruses, worms ,Trojan horses etc.
5.These malicious programs will be removed by firewall if found.
6.Firewall will also help to stop network attacks.
Outputs
1.For registered user-Registered user can access firewalled network as an output of
whole processing.
2.For admin-Output will be managed list of blocked websites and firewalled network
traffic.
15

3.3 Use Case Diagram

Access firewalled
internet

Access
database

Modify
database

login

Modify set of
rules of firewall
Access
firewalled
intranet

Modify
blocked list
of sites

Add unreg.users
username and
pwd in database

16

Das könnte Ihnen auch gefallen