IMPROVING MOBILE BANKING

SECURITY USING

STEGANOGRAPHY

PROJECT GUIDE :

P .Samba Siva Rao M.Tech

Assistant Professor.

PROJECT MEMBERS :

M . KavyaSri (11KD1A0563)

P . H.A . Priyanka (11KD1A0578)

V . Sravan Kumar (11KD1A05A2)

P . Joshana Kumar (11KD1A0571)

CONTENTS

1) INTRODUCTION

2) PROBLEM ANALYSIS

3) LITERATURE SURVEY

4) SYSTEM ANALYSIS

5) SYSTEM DESIGN

6) CONCLUSION

INTRODUCTION

M-banking is facing some challenges. One of these challenges is the issue

of security of this system.

In this method, instead of direct sending of the information, it is hidden in

a picture by the password.

In this method, the information is never placed on the internet and

exchanged on plain form. Thus , the possibility of disclosure of information

is very low.

In this method, the amount of information exchanged between user and the

banking system decreases, so the responding speed of the bank system

increases.

PROBLEM ANALYSIS

1) EXISTING SYSTEM :

In the existing system we had just e-banking that is accessible through

computers, here users can bank through the internet from a personal

computer located at a particular point of place or through a mobile which

uses WML (Web Markup Language), it downloads the contents from the

internet.

DISADVANTAGES OF EXISTING SYSTEM :

Time constraint.

High communication costs.

Low bandwidth and latency issues.

There is no security for the data.

2) PROPOSED SYSTEM

To solve the above mentioned problems our application uses

Steganography which is both secured and reliable.

By using our system the user is no longer needed to use the desktop for

performing transactions.

After the user gets logged in, he will have an easily understandable

interface where he can have two options to use i.e., account details and

money transfer.

The transaction is sent to the receiver in the form of a Stegoimage, by

which he can withdraw the amount.

ADVANTAGES OF PROPOSED SYSTEM

Fast data services .

Low data transfer costs.

More functionality possible (new devices with better displays and browserfunctionality).

Higher Security mechanisms.

There is no time constraints.

we can do banking from any place with less time.

There is no risk of disclosure.

LITERATURE SURVEY

What is Steganography ?

In computer terms, Steganography has evolved into the practice of hiding

a message within a larger one in such a way that others cannot discern the

presence or contents of the hidden message.

In contemporary terms, steganography has evolved into a digital strategy

of hiding a file in some form of multimedia, such as an image, an audio file

(like a .wav or mp3) or even a video file.

Steganography Tools :

An important distinction that should be made among the tools available

today is the difference between tools that do steganography, and tools that

do steganalysis, which is the method of detecting steganography and

destroying the original message.

One good place to start your search for stego tools is on Neil Johnson's

Steganography and Digital Watermarking Web site. The site includes an

extensive list of steganography tools.

Steganography and Security :

steganography is an effective means of hiding data, thereby protecting the

data from unauthorized or unwanted viewing.

It is probably best used in conjunction with another data-hiding method.

When used in combination, these methods can all be a part of a layered

security approach.

Some good complementary methods include: Encryption - Encryption is

the process of passing data or plaintext through a series of mathematical

operations that generate an alternate form of the original data known as

cipher text.

SYSTEM ANALYSIS

a)SYSTEM REQUIREMENT SPECIFICATION :

Functional requirements

1. Input Design

Input design is a part of overall system design.

The main objective during the input design is as given below:

To produce a cost-effective method of input.

To achieve the highest possible level of accuracy.

2. Input Stages

The main input stages can be listed as below:

Data verification

Data transmission

Data validation

FUNCTIONAL REQUIREMENTS

3.Output media

The main considerations when deciding about the output media are:

The suitability for the device to the particular application.

The response time required.

4.Error Detection

Even though every effort is make to avoid the occurrence of errors, still a

small proportion of errors is always likely to occur, these types of errors

can be discovered by using validations to check the input data.

5.Data validation

Data validations have been included in the system in almost every area

where there is a possibility for the user to commit errors. The system will

not accept invalid data.

NON FUNCTIONAL REQUIREMENTS:

Performance requirements

Performance should not be an issue because all of our server queries

involve small pieces of data.

Security Requirements

The database contains all of the user logins/passwords and other

information that must be protected from hackers who would try to

infiltrate the system and steal any personal or user information and try

to login under a stolen name.

Availability

If the internet service gets disrupted while sending information to the

server, the information can be send again for verification.

B) USECASE ANALYSIS A use case analysis is the primary form for gathering usage requirements for a new

software program or task to be completed .

A use case represents how a system interacts with its environment by illustrating

the activities that are performed by the users and the system’s responses.

Use cases are a means of expressing user requirements. Use cases are used

extensively in the analysis phase..System

sender

Receiver

Bank system server

Login

Get Account details

Transfer money

Generate stego image

receive stego image

Receive Payment

Decode Stego image

secure banking app

USECASE DIAGRAM

Actors :

1)Sender

2) Receiver

3)Bank System Server

Usecases :

1)Login

2)Get account details

3)Transfer Money

4)Generate stegoimage

5)receive Stegoimage

6)Decode Stegoimage

7)receive payment

C) SYSTEM REQUIREMENTS

1)Software Requirements :

Language: JAVA

Front End: Android

Back End: My SQL

Web Server: Apache Tomcat

2)Hardware Requirement

Processor : core 2 duo

Clock speed : 2GhZ

Hard Disk : 20GB

RAM : 2GB

Cache Memory : 512KB

SYSTEM DESIGN

a)System Architecture

B) UML DESIGN

Use case Diagram

Sequence Diagram

Activity Diagram

Class Diagram

USECASE DIAGRAM

A Usecase diagram is used to model the static design view of a

system. Usecase represents a set of actions performed by a system

for a specific goal.

Here this diagram shows three actors, seven usecases and the

relation ship between them.

System

sender

Receiver

Bank system server

Login

Get Account details

Transfer money

Generate stego image

receive stego image

Receive Payment

Decode Stego image

secure banking app

SEQUENCE DIAGRAM

FOR ACCOUNT DETAILS

A sequence diagram emphasizes the time ordering of messages.

This diagram shows the sequence of actions that are takes place

during a customer wants to know his/her account details.

:customer :Secure Banking App :Bank System Server

1 : login()

2 : perform authentication()

<<destroy>>

3 : valid()

4 : request for account details()

<<destroy>>

5 : show details()

<<destroy>>

SEQUENCE DIAGRAM FOR

MONEY TRANSFER:sender :Secure Banking App :Bank System Server :reciever

1 : login()

2 : perform authentication()

3 : valid

4 : Request for money transfer()

5 : ask for recipient id()

6 : enter the id()

7 : Id validation()

8 : valid

9 : ask to enter amount()

10 : amount has been entered()

11 : ask for transfer id()

12 : enter transfer id()

13 : validate()

<<destroy>>

14 : valid

15 : Perform steganography()<<destroy>>

16 : Retrieve image()

<<destroy>>

17 : transfer the stego image with id()

<<destroy>>

SEQUENCE DIAGRAM FOR

MONEY WITHDRAWAL:Receiver :Secure Banking App ;Bank system server

1 : Login()

2 : Perform authentication()

3 : Valid

4 : request for money withDrawl()

<<destroy>>

5 : ask to enter stego image()

6 : stegoimage has entered()

7 : perform decryption()

<<destroy>>

8 : receive amount()

<<destroy>>

ACTIVITY DIAGRAMcustomer Secure Banking App

loginvalidation

valid

request for money transfer ask for recipient id

enter the id

id validation

Ask to enter amount

Amount Entered

ask for transfer identer transfer id

validation

valid

perform steganogaphy

Retrieve Image

Transfer image with id

No

invalid

yes

valid

yes

No

Class diagram

A class diagram is that which represents a set of classes, interfaces,

collaborations and their relationships. Each class consists of three

compartments..1st compartment - class name,2nd compartment - attributes,3rd

compartment - operations .

Here the diagram shows 5 classes and their relationship among them…

CONCLUSION

This project presents a method for increasing

security of the information requested by users with

the use of steganography method. In this method,

instead of direct sending of the information, it is

hidden in a picture by the password. After entering

the password, the user can witness the information

extracted from the picture if the password is entered

correctly.

THANK YOU

Any Queries…….?