Full Doc Security Evaluation

Security Evaluation of Pattern Classifiers under Attack
TABLE OF CONTENTS
1. Abstract
2. Introduction
Organization Profile
3. System Analysis
Existing system
Proposed System
Requirement Analysis
Requirement Specifications
Feasibility study
4. System Design
4.1 Project Modules
4.2 Data Dictionary
4.3 Hardware And Software Requirements
5. System Testing
6. Software Tools Used
7 Technical Notes
7.1 Introduction To Real-time programming
7.2 Introduction to OOPS and Windows
7.3 Introduction to Java
8. Screens
9. Conclusion
10. Bibliograph
Abstract
Security Evaluation of Pattern Classifiers under Attack Page 1

The objective of this application is Pattern classification systems are

commonly used in adversarial applications, like biometric authentication,
network intrusion detection, and spam filtering, in which data can be
purposely manipulated by humans to undermine their operation. As this
adversarial scenario is not taken into account by classical design methods,
pattern classification systems may exhibit vulnerabilities, whose exploitation
may severely affect their performance, and consequently limit their practical
utility. Extending pattern classification theory and design methods to
adversarial settings is thus a novel and very relevant research direction,
which has not yet been pursued in a systematic way. In this paper, we
address one of the main open issues: evaluating at design phase the security
of pattern classifiers, namely, the performance degradation under potential
attacks they may incur during operation. We propose a framework for
empirical evaluation of classifier security that formalizes and generalizes the
main ideas proposed in the literature, and give examples of its use in three
real applications. Reported results show that security evaluation can provide
a more complete understanding of the classifier’s behavior in adversarial
environments, and lead to better design choices
1. INTRODUCTION
1.1 ABOUT THE ORGANIZATION
1.2 About the project

The main theme of this project is to develop a system that can handle all
the details Pattern classification systems are commonly used in adversarial
applications, like biometric authentication, network intrusion detection, and
spam filtering, in which data can be purposely manipulated by humans to
undermine their operation. As this adversarial scenario is not taken into
account by classical design methods, pattern classification systems may
exhibit vulnerabilities, whose exploitation may severely affect their
performance, and consequently limit their practical utility. Extending pattern
classification theory and design methods to adversarial settings is thus a
novel and very relevant research direction, which has not yet been pursued
in a systematic way. In this paper, we address one of the main open issues:
evaluating at design phase the security of pattern classifiers, namely, the
performance degradation under potential attacks they may incur during
operation. We propose a framework for empirical evaluation of classifier
security that formalizes and generalizes the main ideas proposed in the
literature, and give examples of its use in three real applications. Reported
results show that security evaluation can provide a more complete
understanding of the classifier’s behavior in adversarial environments, and
lead to better design choices
2. PROBLEM DEFINITION AND FEASIBILITY ANALYSIS

2.1 Definition of the problem
To create or develop a new system first we have to study the prior

system, Analysis difficult problems faced by the operator of that system.
System Analysis therefore understands such problems and proposes a new
system in which the above problems are rectified.
EXISTING SYSTEM:
Pattern classification systems based on classical theory and design methods
do not take into account adversarial settings; they exhibit vulnerabilities to
several potential attacks, allowing adversaries to undermine their
effectiveness. A systematic and unified treatment of this issue is thus needed
to allow the trusted adoption of pattern classifiers in adversarial
environments, starting from the theoretical foundations up to novel design
methods, extending the classical design cycle of. In particular, three main
open issues can be identified: (i) analyze the vulnerabilities of classification
algorithms, and the corresponding attacks. (ii) Developing novel methods to
assess classifier security against these attacks, which are not possible using
classical performance evaluation methods. (iii) Developing novel design
methods to guarantee classifier security in adversarial environments.
DISADVANTAGES OF EXISTING SYSTEM:

1. Poor analyzing the vulnerabilities of classification algorithms, and the
corresponding attacks.
2. A malicious webmaster may manipulate search engine rankings to
artificially promote website.
PROPOSED SYSTEM:
In this work we address issues above by developing a framework for the
empirical evaluation of classifier security at design phase that extends the
model selection and performance evaluation steps of the classical design
cycle .We summarize previous work, and point out three main ideas that
emerge from it. We then formalize and generalize them in our framework.
First, to pursue security in the context of an arms race it is not sufficient to
react to observed attacks, but it is also necessary to proactively anticipate the
adversary by predicting the most relevant, potential attacks through a what-if
analysis; this allows one to develop suitable countermeasures before the
attack actually occurs, according to the principle of security by design.
Second, to provide practical guidelines for simulating realistic attack
scenarios, we define a general model of the adversary, in terms of her goal,
knowledge, and capability, which encompass and generalize models
proposed in previous work. Third, since the presence of carefully targeted
attacks may affect the distribution of training and testing data separately, we
propose a model of the data distribution that can formally characterize this
behaviour, and that allows us to take into account a large number of potential
attacks; we also propose an algorithm for the generation of training and
testing sets to be used for security evaluation, which can naturally
accommodate application-specific and heuristic techniques for simulating
attacks.
ADVANTAGES OF PROPOSED SYSTEM:

1. Proposed system prevents developing novel methods to assess classifier
security against these attacks.
2. The presence of an intelligent and adaptive adversary makes the

classification problem highly non-stationary.
SYSTEM ARCHITECTURE:
MODULES:
1. Attack Scenario and Model of the Adversary
2. Pattern Classification
3. Adversarial classification:
4. Security modules
MODULES DESCRIPTION:
Attack Scenario and Model of the Adversary:
Although the definition of attack scenarios is ultimately an application-
specific issue, it is possible to give general guidelines that can help the
designer of a pattern recognition system. Here we propose to specify the
attack scenario in terms of a conceptual model of the adversary that
encompasses, unifies, and extends different ideas from previous work. Our
model is based on the assumption that the adversary acts rationally to attain
a given goal, according to her knowledge of the classifier, and her capability
of manipulating data. This allows one to derive the corresponding optimal
attack strategy.
Pattern Classification:

Multimodal biometric systems for personal identity recognition have

received great interest in the past few years. It has been shown that
combining information coming from different biometric traits can overcome
the limits and the weaknesses inherent in every individual biometric,
resulting in a higher accuracy. Moreover, it is commonly believed that
multimodal systems also improve security against Spoofing attacks, which
consist of claiming a false identity and submitting at least one fake biometric
trait to the system (e.g., a “gummy” fingerprint or a photograph of a user’s
face). The reason is that, to evade multimodal system, one expects that the
adversary should spoof all the corresponding biometric traits. In this
application example, we show how the designer of a multimodal system can
verify if this hypothesis holds, before deploying the system, by simulating
spoofing attacks against each of the matchers.
Adversarial classification:
Assume that a classifier has to discriminate between legitimate and spam
emails on the basis of their textual content, and that the bag-of-words feature
representation has been chosen, with binary features denoting the occurrence
of a given set of words
Security modules:
Intrusion detection systems analyze network traffic to prevent and detect
malicious activities like intrusion attempts, ROC curves of the considered
multimodal biometric system under a simulated spoof attack against the
fingerprint or the face matcher. Port scans, and denial-of-service attacks.
When suspected malicious traffic is detected, an alarm is raised by the IDS
and subsequently handled by the system administrator. Two main kinds of
IDSs exist: misuse detectors and anomaly-based ones. Misuse detectors
match the analyzed network traffic against a database of signatures of known
malicious activities. The main drawback is that they are not able to detect
never-before-seen malicious activities, or even variants of known ones. To
overcome this issue, anomaly-based detectors have been proposed. They
build a statistical model of the normal traffic using machine learning
techniques, usually one-class classifiers, and raise an alarm when anomalous
traffic is detected. Their training set is constructed, and periodically updated
to follow the changes of normal traffic, by collecting unsupervised network
traffic during operation, assuming that it is normal (it can be filtered by a
misuse detector, and should)
2.2Feasibility study
FEASIBILITY STUDY
The feasibility of the project is analyzed in this phase and business

proposal is put forth with a very general plan for the project and some
cost estimates. During system analysis the feasibility study of the
proposed system is to be carried out. This is to ensure that the proposed
system is not a burden to the company. For feasibility analysis, some
understanding of the major requirements for the system is essential.
Three key considerations involved in the feasibility analysis are
 ECONOMICAL FEASIBILITY
 TECHNICAL FEASIBILITY
 SOCIAL FEASIBILITY
2.2.1 Operational Feasibility

In this test, the operational scope of the system is checked. The

system under consideration should have enough operational reach. It is
observed that the proposed system is very user friendly and since the system
is built with enough help, even persons with little knowledge of windows
can find the system very easy.
2.2.2 Technical Feasibility
This study is carried out to check the technical feasibility, that is, the
technical requirements of the system. Any system developed must not have
a high demand on the available technical resources. This will lead to high
demands on the available technical resources. This will lead to high
demands being placed on the client. The developed system must have a
modest requirement, as only minimal or null changes are required for
implementing this system.
2.2.3 Economical Feasibility
This study is carried out to check the economic impact that the
system will have on the organization. The amount of fund that the company
can pour into the research and development of the system is limited. The
expenditures must be justified. Thus the developed system as well within the
budget and this was achieved because most of the technologies used are
freely available. Only the customized products had to be purchased.
3. SYSTEM ANALYSIS
3.1 Hardware and Software Specifications

The development of this project deals with the following environment
 Hardware requirements
 Software requirements
Hardware Requirements:
The selection of hardware is very important in the existence and
proper working of any software. In the selection of hardware, the size and
the capacity requirements are also important.
The Web Based Manufacturing System can be efficiently run on
Pentium system with at least 128 MB RAM and Hard disk drive having 20
GB. Floppy disk drive of 1.44 MB and 14 inch Samsung color monitor suits
the information system operation.(A Printer is required for hard copy
output).
 Pentium processor -------- 233 MHZ or above
 RAM Capacity -------- 256MB
 Hard Disk -------- 20GB
 Floppy disk -------- 1.44 MB
 CD-ROM Drive -------- 32 HZ
Software Requirements:
One of the most difficult tasks is that, the selection of the software,
once system requirement is known is determining whether a particular
software package fits the requirements. After initial selection further
security is needed to determine the desirability of particular software

compared with other candidates. This section first summarizes the

application requirement question and then suggests more detailed
comparisons.
 Operating System -- Windows 98/NT/2000
 Browser -- IE
 Web/Application Server -- Tomcat Server
 Database -- MySql
 Database Connectivity -- JDBC
 Java Technologies -- Java (Servlets, jsp, java
Beans)
 Scripting Technology -- Java Script
4. SYSTEM DESIGN
Design Description
Design is essentially a blue print or it acts as a bridge between the

requirement specification and the final solution for satisfying the
requirements.
Based on the work-flow described above we can draw the following
conclusions for the Software System that has to be developed:
 The System needs to be a web-based system so that it allows the
Chairman, Branch Managers, Agents, and Customers to access the
company database over the Internet.

 Being a web-based system also enables the Company staff to

communicate with other users.
 An added advantage is chairman communicate with other employees
over the net since there could be instant responses from the Suppliers.
 The whole process depends on communications between Chairman & the
Manager, and between Customers & the Agents. If all these
communications are done through a web-based system, then the time
period for the whole process can be considerably brought down.
The System needs to store the Company details.
 The System needs to store the details of all the Premiums that are
available of the company.
 The System needs to store the details of all the Customers held in the
Company warehouse.
 The System needs to store the details of all the Agents held in the
Company.
 The System needs to store the details of all the Branch Managers details.
 Since it is a web-based system, a Login authorization should be provided
so that Chairman, Managers, Customers and Agents will be able to
lookup & use options that are specific to them.
 The System should allow the Agents to enter their Statistics.
 The System should allow the Customers to visible their next premium
dates, bonus, dues and related information.
 The System should provide an option to generate a Customers Report
and estimated of company business.

 The System should provide an option to generate a Agents Reports, with

the help of these reports estimate of their performance
 For the above to take place the system should store the Premium details
of the Customers. If any future modification required, easily modify the
Customers details.
 The System should provide an option that all customers are visible to
latest Policies and their specifications. This facility is very help to
Customers to see the all information through on line.
1.1 High level design

DATA FLOW DIAGRAMS
Data flow diagram is a structure analysis tool that is used for graphical
representation of Data processes through any organization. The data flow

approach emphasis on the logic underlying the system, by using

combination of only 4 symbols. It follows a top down approach. A full
description of a system actually consists of set of DFD s, which
comprises of various levels. And initial over view model is exploded
lower level diagrams that show additional feature of the system. Further
each process can be broken down into a more detailed DFD. This occurs
repeatedly until sufficient details are described.
DFD symbols
square
it defines a source (originator ) or destination of system data.
Arrow
It indicates data flow-data in motion. It is a pipeline through

which information flows.
Circle or Bubble

It represents a process that transforms incoming data flow(s) into outgoing

data flow(s).
Open Rectangle
it is a data store-data at rest, or a temporary repository of data. Here I am

giving only the Data Flow Diagram.
They are explained by

 GANE and SARON method
 DEMACRO YORDAN method
GANE AND SARSON NOTATION
DATA FLOW

DATA STRUCTURE
EXTERNAL ENTITY
OR DATA LINK
PROCESS
DATA BASE
DEMACRO YORDAN NOTATION
DATA FLOW

DATA STRUCTURE
EXTERNAL ENTITY
OR DATA LINK
PROCESS
DATA BASE
ENTITY-RELATIONSHIP DIAGRAMS

E-R (Entity-Relationship) Diagram is used to represents the

relationship between entities in the table.
The symbols used in E-R diagrams are:
SYMBOL PURPOSE
Represents Entity sets.
Represent attributes.
Represent Relationship Sets.
Line represents flow

Login
Check
Biometric Authendication
Admin
user
Activate new user

upload file
activate blocked users if need

specify file type
view attackers
Apply spam filter
Decrypt the Message
download file
UMLDIAGRAMS
INTRODUCTION

UML is a notation that resulted from the unification of Object

Modeling Technique and Object Oriented Software Technology .UML has
been designed for broad range of application.
Hence, it provides constructs for a broad range of systems and activities.
An Overview of UML in five notations
1.use case diagrams
Use cases are used during requirements elicitation and analysis To

represent the functionality of the system.Use cases focus on the behaviour
of the system from the external point of view.The actor are
Outside the boundary of the system,whereas the use cases are inside the
boundary of the system.
2.class diagrams
Class diagrams to describe the structure of the system. Classes Are

abstraction that specify the common structure and behaviour of a set
Class diagrams describe the system in terms of objects, classes,
attributes, operations and their associations.
3.Sequence diagrams
Sequence diagrams are used to formalize the behaviour of the

system and to visualize the communication among objects. They are useful
for identifying additional objects that participate in the use cases. A
Sequence diagram represents the interaction that take place among these
objects.
4.Statechart diagrams
State chart diagrams describe the behaviour of an individual

object as a number of states and transitions between these states. A state
represents a particular set of values for an object. The sequence diagram

focuses on the messages exchanged between objects, the state chart

diagrams focuses on the transition between states.
5.Activity diagrams
An activity diagram describes a system in terms of activities.

Activities are states that represents the execution of a set of operations.
Activity diagrams are similar to flowchart diagram and data flow.
USE CASE DIAGRAM:
A use case diagram in the Unified Modeling Language (UML) is a
type of behavioral diagram defined by and created from a Use-case analysis.
Its purpose is to present a graphical overview of the functionality provided
by a system in terms of actors, their goals (represented as use cases), and any
dependencies between those use cases. The main purpose of a use case
diagram is to show what system functions are performed for which actor.
Roles of the actors in the system can be depicted.

Register
activate user
Login
user
upload file
specify file type

Admin
apply spam filter
download file
view attackers
CLASS DIAGRAM:
In software engineering, a class diagram in the Unified Modeling Language
(UML) is a type of static structure diagram that describes the structure of a
system by showing the system's classes, their attributes, operations (or
methods), and the relationships among the classes. It explains which class
contains information.
Admin
User
Attacker;
Register
newusers
Login
blockeduser
File
Filetype
Spamfileter
uploadfile()
activate();
download()
activities();
spamfilter()
viewattacker():
SEQUENCE DIAGRAM:
A sequence diagram in Unified Modeling Language (UML) is a kind of
interaction diagram that shows how processes operate with one another and
in what order. It is a construct of a Message Sequence Chart. Sequence
diagrams are sometimes called event diagrams, event scenarios, and timing
diagrams.

Data base
User Admin
Registration
activate user
Login with biometric
upload file
specify file type
apply spam filter
download file
activate blocked user
monitor user activities
find attacker
ACTIVITY DIAGRAM:

Activity diagrams are graphical representations of workflows of stepwise

activities and actions with support for choice, iteration and concurrency. In
the Unified Modeling Language, activity diagrams can be used to describe
the business and operational step-by-step workflows of components in a
system. An activity diagram shows the overall flow of control.

Login
biometric authendication admin
Activate users
user

upload file
specify file type

view attacker
yes
apply spam filter
monitor user activities
Download file
A
Component Diagram


Deployment Diagram

Technologies Used
HTML
HTML, an initialism of Hypertext Markup Language, is the predominant
markup language for web pages. It provides a means to describe the
structure of text-based information in a document — by denoting certain text
as headings, paragraphs, lists, and so on — and to supplement that text with
interactive forms, embedded images, and other objects. HTML is written in
the form of labels (known as tags), surrounded by angle brackets. HTML can
also describe, to some degree, the appearance and semantics of a document,
and can include embedded scripting language code which can affect the
behavior of web browsers and other HTML processors.
HTML is also often used to refer to content of the MIME type text/html or
even more broadly as a generic term for HTML whether in its XML-descended
form (such as XHTML 1.0 and later) or its form descended directly from
SGML
Hyper Text Markup Language
Hypertext Markup Language (HTML), the languages of the World Wide

Web (WWW), allows users to produces Web pages that include text,
graphics and pointer to other Web pages (Hyperlinks).
HTML is not a programming language but it is an application of ISO
Standard 8879, SGML (Standard Generalized Markup Language), but
specialized to hypertext and adapted to the Web. The idea behind Hypertext
is that instead of reading text in rigid linear structure, we can easily jump
from one point to another point. We can navigate through the information
based on our interest and preference. A markup language is simply a series
of elements, each delimited with special characters that define how text or

other items enclosed within the elements should be displayed. Hyperlinks

are underlined or emphasized works that load to other documents or some
portions of the same document.
HTML can be used to display any type of document on the host computer,
which can be geographically at a different location. It is a versatile language
and can be used on any platform or desktop.
HTML provides tags (special codes) to make the document look attractive.
HTML tags are not case-sensitive. Using graphics, fonts, different sizes,
color, etc., can enhance the presentation of the document. Anything that is
not a tag is part of the document itself.
Basic HTML Tags:

<! -- --> specifies comments
<A>……….</A> Creates hypertext links
<B>……….</B> Formats text as bold
<BIG>……….</BIG> Formats text in large font.
<BODY>…</BODY> Contains all tags and text in the HTML
document
<CENTER>...</CENTER> Creates text
<DD>…</DD> Definition of a term
<DL>...</DL> Creates definition list
<FONT>…</FONT> Formats text with a particular font
<FORM>...</FORM> Encloses a fill-out form
<FRAME>...</FRAME> Defines a particular frame in a set of frames
<H#>…</H#> Creates headings of different levels( 1 – 6 )
<HEAD>...</HEAD> Contains tags that specify information about
a document
<HR>...</HR> Creates a horizontal rule
<HTML>…</HTML> Contains all other HTML tags
<META>...</META> Provides meta-information about a document

<SCRIPT>…</SCRIPT> Contains client-side or server-side script

<TABLE>…</TABLE> Creates a table
<TD>…</TD> Indicates table data in a table
<TR>…</TR> Designates a table row
<TH>…</TH> Creates a heading in a table
Attributes
The attributes of an element are name-value pairs, separated by "=", and
written within the start label of an element, after the element's name. The
value should be enclosed in single or double quotes, although values
consisting of certain characters can be left unquoted in HTML (but not
XHTML).Leaving attribute values unquoted is considered unsafe.
Most elements take any of several common attributes: id, class, style and
title. Most also take language-related attributes: lang and dir.
The id attribute provides a document-wide unique identifier for an element.
This can be used by stylesheets to provide presentational properties, by
browsers to focus attention on the specific element or by scripts to alter the
contents or presentation of an element. The class attribute provides a way of
classifying similar elements for presentation purposes. For example, an HTML
document (or a set of documents) may use the designation class="notation"
to indicate that all elements with this class value are all subordinate to the
main text of the document (or documents). Such notation classes of
elements might be gathered together and presented as footnotes on a page,
rather than appearing in the place where they appear in the source HTML.
An author may use the style non-attributal codes presentational properties to
a particular element. It is considered better practice to use an element’s son-
id page and select the element with a stylesheet, though sometimes this can
be too cumbersome for a simple ad hoc application of styled properties. The
title is used to attach subtextual explanation to an element. In most
browsers this title attribute is displayed as what is often referred to as a
tooltip. The generic inline span element can be used to demonstrate these
various non-attributes.

The preceding displays as HTML (pointing the cursor at the abbreviation

should display the title text in most browsers).
Advantages
 A HTML document is small and hence easy to send over the net.
It is small because it does not include formatted information.
 HTML is platform independent.
 HTML tags are not case-sensitive.

JavaScript
JavaScript is a script-based programming language that was developed by
Netscape Communication Corporation. JavaScript was originally called Live
Script and renamed as JavaScript to indicate its relationship with Java.
JavaScript supports the development of both client and server components of
Web-based applications. On the client side, it can be used to write programs
that are executed by a Web browser within the context of a Web page. On
the server side, it can be used to write Web server programs that can
process information submitted by a Web browser and then update the
browser’s display accordingly
Even though JavaScript supports both client and server Web programming,
we prefer JavaScript at Client side programming since most of the browsers
supports it. JavaScript is almost as easy to learn as HTML, and JavaScript
statements can be included in HTML documents by enclosing the statements
between a pair of scripting tags
<SCRIPTS>.. </SCRIPT>.
<SCRIPT LANGUAGE = “JavaScript”>
JavaScript statements
</SCRIPT>
Here are a few things we can do with JavaScript:
 Validate the contents of a form and make calculations.
 Add scrolling or changing messages to the Browser’s status line.
 Animate images or rotate images that change when we move
the mouse over them.
 Detect the browser in use and display different content for
different browsers.
 Detect installed plug-ins and notify the user if a plug-in is
required.
We can do much more with JavaScript, including creating entire application.

JavaScript Vs Java
JavaScript and Java are entirely different languages. A few of the most
glaring differences are:
 Java applets are generally displayed in a box within the web

document; JavaScript can affect any part of the Web document itself.
 While JavaScript is best suited to simple applications and adding
interactive features to Web pages; Java can be used for incredibly
complex applications.
There are many other differences but the important thing to remember is
that JavaScript and Java are separate languages. They are both useful for
different things; in fact they can be used together to combine their
advantages.
Advantages
 JavaScript can be used for Sever-side and Client-side scripting.

 It is more flexible than VBScript.
 JavaScript is the default scripting languages at Client-side since
all the browsers supports it.

Java Technology
Initially the language was called as “oak” but it was renamed as “Java” in
1995. The primary motivation of this language was the need for a platform-
independent (i.e., architecture neutral) language that could be used to create
software to be embedded in various consumer electronic devices.
 Java is a programmer’s language.
 Java is cohesive and consistent.
 Except for those constraints imposed by the Internet environment,
Java gives the programmer, full control.
 Finally, Java is to Internet programming where C was to system
programming.
Importance of Java to the Internet
Java has had a profound effect on the Internet. This is because; Java expands
the Universe of objects that can move about freely in Cyberspace. In a
network, two categories of objects are transmitted between the Server and
the Personal computer. They are: Passive information and Dynamic active
programs. The Dynamic, Self-executing programs cause serious problems in
the areas of Security and probability. But, Java addresses those concerns and
by doing so, has opened the door to an exciting new form of program called
the Applet.
Java can be used to create two types of programs
Applications and Applets : An application is a program that runs on our

Computer under the operating system of that computer. It is more or less like
one creating using C or C++. Java’s ability to create Applets makes it
important. An Applet is an application designed to be transmitted over the

Internet and executed by a Java –compatible web browser. An applet is

actually a tiny Java program, dynamically downloaded across the network,
just like an image. But the difference is, it is an intelligent program, not just
a media file. It can react to the user input and dynamically change.
Features of Java Security
Every time you that you download a “normal” program, you are risking a
viral infection. Prior to Java, most users did not download executable
programs frequently, and those who did scan them for viruses prior to
execution. Most users still worried about the possibility of infecting their
systems with a virus. In addition, another type of malicious program exists
that must be guarded against. This type of program can gather private
information, such as credit card numbers, bank account balances, and
passwords. Java answers both these concerns by providing a “firewall”
between a network application and your computer.
When you use a Java-compatible Web browser, you can safely download Java
applets without fear of virus infection or malicious intent.
Portability
For programs to be dynamically downloaded to all the various types of

platforms connected to the Internet, some means of generating portable
executable code is needed .As you will see, the same mechanism that helps
ensure security also helps create portability. Indeed, Java’s solution to these
two problems is both elegant and efficient.
The Byte code
The key that allows the Java to solve the security and portability problems is
that the output of Java compiler is Byte code. Byte code is a highly optimized
set of instructions designed to be executed by the Java run-time system,

which is called the Java Virtual Machine (JVM). That is, in its standard form,
the JVM is an interpreter for byte code.
Translating a Java program into byte code helps makes it much easier to run
a program in a wide variety of environments. The reason is, once the run-
time package exists for a given system, any Java program can run on it.
Although Java was designed for interpretation, there is technically nothing

about Java that prevents on-the-fly compilation of byte code into native
code. Sun has just completed its Just In Time (JIT) compiler for byte code.
When the JIT compiler is a part of JVM, it compiles byte code into executable
code in real time, on a piece-by-piece, demand basis. It is not possible to
compile an entire Java program into executable code all at once, because
Java performs various run-time checks that can be done only at run time.
The JIT compiles code, as it is needed, during execution.
Java Virtual Machine (JVM)
Beyond the language, there is the Java virtual machine. The Java virtual
machine is an important element of the Java technology. The virtual machine
can be embedded within a web browser or an operating system. Once a piece
of Java code is loaded onto a machine, it is verified. As part of the loading
process, a class loader is invoked and does byte code verification makes sure
that the code that’s has been generated by the compiler will not corrupt the
machine that it’s loaded on. Byte code verification takes place at the end of
the compilation process to make sure that is all accurate and correct. So byte
code verification is integral to the compiling and executing of Java code.
Overall Description
Java Source Java byte code JavaVM
Java .Class
Picture showing the development process of JAVA Program

Java programming uses to produce byte codes and executes them. The first
box indicates that the Java source code is located in a. Java file that is
processed with a Java compiler called javac. The Java compiler produces a
file called a. class file, which contains the byte code. The .Class file is then
loaded across the network or loaded locally on your machine into the
execution environment is the Java virtual machine, which interprets and
executes the byte code.
Java Architecture
Java architecture provides a portable, robust, high performing environment

for development. Java provides portability by compiling the byte codes for
the Java Virtual Machine, which is then interpreted on each platform by the
run-time environment. Java is a dynamic system, able to load code when
needed from a machine in the same room or across the planet.
Compilation of code
When you compile the code, the Java compiler creates machine code (called
byte code) for a hypothetical machine called Java Virtual Machine (JVM).
The JVM is supposed to execute the byte code. The JVM is created for
overcoming the issue of portability. The code is written and compiled for
one machine and interpreted on all machines. This machine is called Java
Virtual Machine.

Compiling and interpreting Java Source Code
During run-time the Java interpreter tricks the byte code file into thinking
that it is running on a Java Virtual Machine. In reality this could be a Intel
Pentium Windows 95 or SunSARC station running Solaris or Apple
Macintosh running system and all could receive code from any computer
through Internet and run the Applets.
Simple
Java was designed to be easy for the Professional programmer to learn and
to use effectively. If you are an experienced C++ programmer, learning Java
will be even easier. Because Java inherits the C/C++ syntax and many of the
object oriented features of C++. Most of the confusing concepts from C++
are either left out of Java or implemented in a cleaner, more approachable
manner. In Java there are a small number of clearly defined ways to
accomplish a given task.

Object-Oriented
Java was not designed to be source-code compatible with any other

language. This allowed the Java team the freedom to design with a blank
slate. One outcome of this was a clean usable, pragmatic approach to
objects. The object model in Java is simple and easy to extend, while simple
types, such as integers, are kept as high-performance non-objects.
Robust
The multi-platform environment of the Web places extraordinary demands

on a program, because the program must execute reliably in a variety of
systems. The ability to create robust programs was given a high priority in
the design of Java. Java is strictly typed language; it checks your code at
compile time and run time.
Java virtually eliminates the problems of memory management and de-
allocation, which is completely automatic. In a well-written Java program,
all run time errors can –and should –be managed by your program.

Java Database Connectivity
What Is JDBC?
JDBC is a Java API for executing SQL statements. (As a point of interest,
JDBC is a trademarked name and is not an acronym; nevertheless, JDBC is
often thought of as standing for Java Database Connectivity. It consists of a
set of classes and interfaces written in the Java programming language.
JDBC provides a standard API for tool/database developers and makes it
possible to write database applications using a pure Java API.
Using JDBC, it is easy to send SQL statements to virtually any relational
database. One can write a single program using the JDBC API, and the
program will be able to send SQL statements to the appropriate database.
The combinations of Java and JDBC lets a programmer write it once and run
it anywhere.
What Does JDBC Do?
Simply put, JDBC makes it possible to do three things:

 Establish a connection with a database
 Send SQL statements
 Process the results.
JDBC versus ODBC and other APIs
At this point, Microsoft's ODBC (Open Database Connectivity) API is that

probably the most widely used programming interface for accessing relational
databases. It offers the ability to connect to almost all databases on almost
all platforms.
So why not just use ODBC from Java? The answer is that you can use ODBC
from Java, but this is best done with the help of JDBC in the form of the
JDBC-ODBC Bridge, which we will cover shortly. The question now becomes
"Why do you need JDBC?" There are several answers to this question:
1. ODBC is not appropriate for direct use from Java because it uses a C
interface. Calls from Java to native C code have a number of

drawbacks in the security, implementation, robustness, and automatic

portability of applications.
2. A literal translation of the ODBC C API into a Java API would not be
desirable. For example, Java has no pointers, and ODBC makes
copious use of them, including the notoriously error-prone generic
pointer "void *". You can think of JDBC as ODBC translated into an
object-oriented interface that is natural for Java programmers.
3. ODBC is hard to learn. It mixes simple and advanced features
together, and it has complex options even for simple queries. JDBC, on
the other hand, was designed to keep simple things simple while
allowing more advanced capabilities where required.
4. A Java API like JDBC is needed in order to enable a "pure Java"
solution. When ODBC is used, the ODBC driver manager and drivers
must be manually installed on every client machine. When the JDBC
driver is written completely in Java, however, JDBC code is
automatically installable, portable, and secure on all Java platforms
from network computers to mainframes.
Two-tier and Three-tier Models
The JDBC API supports both two-tier and three-tier models for database
access.
In the two-tier model, a Java applet or application talks directly to the

database. This requires a JDBC driver that can communicate with the
particular database management system being accessed. A user's SQL
statements are delivered to the database, and the results of those statements
are sent back to the user. The database may be located on another machine to
which the user is connected via a network. This is referred to as a
client/server configuration, with the user's machine as the client, and the
machine housing the database as the server. The network can be an Intranet,

which, for example, connects employees within a corporation, or it can be

the Internet.
JAVA
Application Client machine
JDBC
DBMS-proprietary protocol
DBMS Database server
Java applet or
Html browser Client machine
(GUI)
HTTP, RMI, or
CORBA calls
Application
Server (Java)
JDBC Server machine
DBMS-proprietary
(business Logic)
protocol
Database server
DBMS
In the three-tier model, commands are sent to a "middle tier" of services,

which then send SQL statements to the database. The database processes
the SQL statements and sends the results back to the middle tier, which then

sends them to the user. MIS directors find the three-tier model very
attractive because the middle tier makes it possible to maintain control over
access and the kinds of updates that can be made to corporate data. Another
advantage is that when there is a middle tier, the user can employ an easy-
to-use higher-level API which is translated by the middle tier into the
appropriate low-level calls. Finally, in many cases the three-tier architecture
can provide performance advantages.
Until now the middle tier has typically been written in languages such as C or
C++, which offer fast performance. However, with the introduction of
optimizing compilers that translate Java byte code into efficient machine-
specific code, it is becoming practical to implement the middle tier in Java.
This is a big plus, making it possible to take advantage of Java's robustness,
multithreading, and security features. JDBC is important to allow database
access from a Java middle tier.
DBC Driver Types

The JDBC drivers that we are aware of at this time fit into one of four
categories:
 JDBC-ODBC bridge plus ODBC driver

 Native-API partly-Java driver
 JDBC-Net pure Java driver
 Native-protocol pure Java driver
JDBC-ODBC Bridge
If possible, use a Pure Java JDBC driver instead of the Bridge and an ODBC
driver. This completely eliminates the client configuration required by ODBC.
It also eliminates the potential that the Java VM could be corrupted by an
error in the native code brought in by the Bridge (that is, the Bridge native
library, the ODBC driver manager library, the ODBC driver library, and the
database client library).
What Is the JDBC- ODBC Bridge?
The JDBC-ODBC Bridge is a JDBC driver, which implements JDBC

operations by translating them into ODBC operations. To ODBC it appears
as a normal application program. The Bridge implements JDBC for any
database for which an ODBC driver is available. The Bridge is
implemented as the
Sun.jdbc.odbc Java package and contains a native library used to access

ODBC. The Bridge is a joint development of Innersole and Java Soft.

JDBC connectivity
The JDBC provides database-independent connectivity between the J2EE

platform and a wide range of tabular data sources. JDBC technology allows
an Application Component Provider to:
 Perform connection and authentication to a database server
 Manager transactions
 Move SQL statements to a database engine for preprocessing and
execution
 Execute stored procedures
 Inspect and modify the results from Select statements

Database:
A database management system (DBMS) is computer software designed for
the purpose of managing databases, a large set of structured data, and run
operations on the data requested by numerous users. Typical examples of
DBMSs include Oracle, DB2, Microsoft Access, Microsoft SQL Server, Firebird,
PostgreSQL, MySQL, SQLite, FileMaker and Sybase Adaptive Server
Enterprise. DBMSs are typically used by Database administrators in the
creation of Database systems. Typical examples of DBMS use include
accounting, human resources and customer support systems.
Originally found only in large companies with the computer hardware needed
to support large data sets, DBMSs have more recently emerged as a fairly
standard part of any company back office.
Description
A DBMS is a complex set of software programs that controls the organization,

storage, management, and retrieval of data in a database. A DBMS includes:
 A modeling language to define the schema of each database hosted in the

DBMS, according to the DBMS data model.
 The four most common types of organizations are the hierarchical,
network, relational and object models. Inverted lists and other
methods are also used. A given database management system may
provide one or more of the four models. The optimal structure
depends on the natural organization of the application's data, and
on the application's requirements (which include transaction rate
(speed), reliability, maintainability, scalability, and cost).
 The dominant model in use today is the ad hoc one embedded in
SQL, despite the objections of purists who believe this model is a
corruption of the relational model, since it violates several of its
fundamental principles for the sake of practicality and performance.
Many DBMSs also support the Open Database Connectivity API that
supports a standard way for programmers to access the DBMS.
 Data structures (fields, records, files and objects) optimized to deal

with very large amounts of data stored on a permanent data storage
device (which implies relatively slow access compared to volatile main
memory).
 A database query language and report writer to allow users to

interactively interrogate the database, analyze its data and update it
according to the users privileges on data.
 It also controls the security of the database.
 Data security prevents unauthorized users from viewing or
updating the database. Using passwords, users are allowed access
to the entire database or subsets of it called subschemas. For
example, an employee database can contain all the data about an
individual employee, but one group of users may be authorized to
view only payroll data, while others are allowed access to only work
history and medical data.
 If the DBMS provides a way to interactively enter and update the
database, as well as interrogate it, this capability allows for
managing personal databases. However, it may not leave an audit
trail of actions or provide the kinds of controls necessary in a multi-
user organization. These controls are only available when a set of
application programs are customized for each data entry and
updating function.
 A transaction mechanism, that ideally would guarantee the ACID

properties, in order to ensure data integrity, despite concurrent user
accesses (concurrency control), and faults (fault tolerance).
 It also maintains the integrity of the data in the database.
 The DBMS can maintain the integrity of the database by not
allowing more than one user to update the same record at the
same time. The DBMS can help prevent duplicate records via
unique index constraints; for example, no two customers with the
same customer numbers (key fields) can be entered into the
database. See ACID properties for more information (Redundancy
avoidance).

The DBMS accepts requests for data from the application program and
instructs the operating system to transfer the appropriate data.
When a DBMS is used, information systems can be changed much more

easily as the organization's information requirements change. New categories
of data can be added to the database without disruption to the existing
system.
Organizations may use one kind of DBMS for daily transaction processing and
then move the detail onto another computer that uses another DBMS better
suited for random inquiries and analysis. Overall systems design decisions
are performed by data administrators and systems analysts. Detailed
database design is performed by database administrators.
Database servers are specially designed computers that hold the actual
databases and run only the DBMS and related software. Database servers are
usually multiprocessor computers, with RAID disk arrays used for stable
storage. Connected to one or more servers via a high-speed channel,
hardware database accelerators are also used in large volume transaction
processing environments.
DBMSs are found at the heart of most database applications. Sometimes

DBMSs are built around a private multitasking kernel with built-in networking
support although nowadays these functions are left to the operating system.

SQL
Structured Query Language (SQL) is the language used to manipulate

relational databases. SQL is tied very closely with the relational model.
In the relational model, data is stored in structures called relations or tables.

SQL statements are issued for the purpose of:
Data definition: Defining tables and structures in the database (DDL used
to create, alter and drop schema objects such as tables and indexes).
Data manipulation: Used to manipulate the data within those schema

objects (DML Inserting, Updating, Deleting the data, and Querying the
Database).
A schema is a collection of database objects that can include: tables, views,

indexes and sequences
List of SQL statements that can be issued against an Oracle database schema
are:
 ALTER - Change an existing table, view or index definition (DDL)

 AUDIT - Track the changes made to a table (DDL)
 COMMENT - Add a comment to a table or column in a table (DDL)
 COMMIT - Make all recent changes permanent (DML - transactional)
 CREATE - Create new database objects such as tables or views (DDL)
 DELETE - Delete rows from a database table (DML)
 DROP - Drop a database object such as a table, view or index (DDL)
 GRANT - Allow another user to access database objects such as tables
or views (DDL)
 INSERT - Insert new data into a database table (DML)
 No AUDIT - Turn off the auditing function (DDL)

 REVOKE - Disallow a user access to database objects such as tables

and views (DDL)
 ROLLBACK - Undo any recent changes to the database (DML -
Transactional)
 SELECT - Retrieve data from a database table (DML)
 TRUNCATE - Delete all rows from a database table (can not be rolled
back) (DML)
 UPDATE - Change the values of some data items in a database table
(DML)
SERVLETS
Introduction
The Java web server is JavaSoft's own web Server. The Java web server is
just a part of a larger framework, intended to provide you not just with a web
server, but also with tools. To build customized network servers for any
Internet or Intranet client/server system. Servlets are to a web server, how
applets are to the browser.
About Servlets
Servlets provide a Java-based solution used to address the problems

currently associated with doing server-side programming, including
inextensible scripting solutions, platform-specific APIs, and incomplete
interfaces.
Servlets are objects that conform to a specific interface that can be plugged
into a Java-based server. Servlets are to the server-side what applets are to
the client-side - object byte codes that can be dynamically loaded off the net.
They differ from applets in that they are faceless objects (without graphics or
a GUI component). They serve as platform independent, dynamically
loadable, pluggable helper byte code objects on the server side that can be
used to dynamically extend server-side functionality.

For example, an HTTP Servlets can be used to generate dynamic HTML

content. When you use Servlets to do dynamic content you get the following
advantages:
 They’re faster and cleaner than CGI scripts
 They use a standard API (the Servlets API)
 They provide all the advantages of Java (run on a variety of
servers without needing to be rewritten).
Attractiveness of Servlets
There are many features of Servlets that make them easy and attractive to
use. These include:
 Easily configured using the GUI-based Admin tool
 Can be loaded and invoked from a local disk or remotely across
the network.
 Can be linked together, or chained, so that one Servlets can call
another Servlets, or several Servlets in sequence.
 Can be called dynamically from within HTML pages, using
server-side include tags.
 Are secure - even when downloading across the network, the
Servlets security model and Servlets sandbox protect your
system from unfriendly behavior.
Advantages of the Servlet API

One of the great advantages of the Servlet API is protocol independence. It
assumes nothing about:
 The protocol being used to transmit on the net
 How it is loaded
 The server environment it will be running in
These qualities are important, because it allows the Servlet API to be

embedded in many different kinds of servers. There are other advantages to
the Servlet API as well. These include:

 It’s extensible - you can inherit all your functionality from the base
classes made available to you.
 It’s simple, small, and easy to use.
Features of Servlets:
 Servlets are persistent. Servlet are loaded only by the web server
and can maintain services between requests.
 Servlets are fast. Since Servlets only need to be loaded once, they
offer much better performance over their CGI counterparts.
 Servlets are platform independent.
 Servlets are extensible. Java is a robust, object-oriented
programming language, which easily can be extended to suit your
needs
 Servlets are secure.
 Servlets can be used with a variety of clients.

Loading Servlets:
Servlets can be loaded from three places
From a directory that is on the CLASSPATH. The CLASSPATH of the

JavaWebServer includes service root/classes/ which is where the system
classes reside.
From the <SERVICE_ROOT /Servlets/ directory. This is *not* in the server’s

class path. A class loader is used to create Servlets from this directory. New
Servlets can be added - existing Servlets can be recompiled and the server
will notice these changes.
From a remote location, for this a code base like http: // nine.eng / classes /
foo / is required in addition to the Servlets class name. Refer to the admin
GUI docs on Servlet section to see how to set this up.
Loading Remote Servlets
Remote Servlets can be loaded by:
1. Configuring the Admin Tool to setup automatic loading of remote

Servlets
2. Setting up server side include tags in. shtml files
3. Defining a filter chain configuration
Invoking Servlets
A Servlet invoker is a Servlet that invokes the "service" method on a named

Servlet. If the Servlet is not loaded in the server, then the invoker first loads
the Servlet (either from local disk or from the network) and the then invokes
the "service" method. Also like applets, local Servlets in the server can be
identified by just the class name. In other words, if a Servlet name is not
absolute, it is treated as local.
A client can invoke Servlets in the following ways:
 The client can ask for a document that is served by the Servlet.

 The client (browser) can invoke the Servlet directly using a URL, once
it has been mapped using the Servlet Aliases section of the admin GUI.
 The Servlet can be invoked through server side include tags.
 The Servlet can be invoked by placing it in the Servlets/ directory.
 The Servlet can be invoked by using it in a filter chain.
Java Server Pages (JSP)
Java server Pages is a simple, yet powerful technology for creating and
maintaining dynamic-content web pages. Based on the Java programming
language, Java Server Pages offers proven portability, open standards,
and a mature re-usable component model .The Java Server Pages
architecture enables the separation of content generation from content
presentation. This separation not eases maintenance headaches; it also
allows web team members to focus on their areas of expertise. Now, web
page designer can concentrate on layout, and web application designers
on programming, with minimal concern about impacting each other’s
work.
Features of JSP
Portability:
Java Server Pages files can be run on any web server or web-enabled
application server that provides support for them. Dubbed the JSP engine,
this support involves recognition, translation, and management of the
Java Server Page lifecycle and its interaction components.
Components
It was mentioned earlier that the Java Server Pages architecture can
include reusable Java components. The architecture also allows for the
embedding of a scripting language directly into the Java Server Pages file.
The components current supported include Java Beans, and Servlets.

Processing
A Java Server Pages file is essentially an HTML document with JSP

scripting or tags. The Java Server Pages file has a JSP extension to the
server as a Java Server Pages file. Before the page is served, the Java
Server Pages syntax is parsed and processed into a Servlet on the server
side. The Servlet that is generated outputs real content in straight HTML
for responding to the client.
Access Models:
A Java Server Pages file may be accessed in at least two different ways. A
client’s request comes directly into a Java Server Page. In this scenario,
suppose the page accesses reusable Java Bean components that perform
particular well-defined computations like accessing a database. The result
of the Beans computations, called result sets is stored within the Bean as
properties. The page uses such Beans to generate dynamic content and
present it back to the client.
In both of the above cases, the page could also contain any valid Java
code. Java Server Pages architecture encourages separation of content

from presentation.
Steps in the execution of a JSP Application:
1. The client sends a request to the web server for a JSP file by giving the
name of the JSP file within the form tag of a HTML page.
2. This request is transferred to the JavaWebServer. At the server side

JavaWebServer receives the request and if it is a request for a jsp file
server gives this request to the JSP engine.
3. JSP engine is program which can under stands the tags of the jsp and
then it converts those tags into a Servlet program and it is stored at

the server side. This Servlet is loaded in the memory and then it is
executed and the result is given back to the JavaWebServer and then
it is transferred back to the result is given back to the JavaWebServer
and then it is transferred back to the client.

Eclipse IDE
Eclipse is an open-source software framework written primarily in Java. In its
default form it is an Integrated Development Environment (IDE) for Java
developers, consisting of the Java Development Tools (JDT) and the Eclipse
Compiler for Java (ECJ). Users can extend its capabilities by installing plug-
ins written for the Eclipse software framework, such as development toolkits
for other programming languages, and can write and contribute their own
plug-in modules. Language packs are available for over a dozen languages.
Architecture
The basis for Eclipse is the Rich Client Platform (RCP). The following
components constitute the rich client platform:
 OSGi - a standard bundling framework
 Core platform - boot Eclipse, run plug-ins
 the Standard Widget Toolkit (SWT) - a portable widget toolkit
 JFace - viewer classes to bring model view controller programming to
SWT, file buffers, text handling, text editors
 the Eclipse Workbench - views, editors, perspectives, wizards
Eclipse's widgets are implemented by a widget toolkit for Java called SWT,
unlike most Java applications, which use the Java standard Abstract Window
Toolkit (AWT) or Swing. Eclipse's user interface also leverages an
intermediate GUI layer called JFace, which simplifies the construction of
applications based on SWT.
Eclipse employs plug-ins in order to provide all of its functionality on top of

(and including) the rich client platform, in contrast to some other applications
where functionality is typically hard coded. This plug-in mechanism is a
lightweight software componentry framework. In addition to allowing Eclipse
to be extended using other programming languages such as C and Python,
the plug-in framework allows Eclipse to work with typesetting languages like

LaTeX, networking applications such as telnet, and database management

systems. The plug-in architecture supports writing any desired extension to
the environment, such as for configuration management. Java and CVS
support is provided in the Eclipse SDK.
The key to the seamless integration of tools with Eclipse is the plugin. With
the exception of a small run-time kernel, everything in Eclipse is a plug-in.
This means that a plug-in you develop integrates with Eclipse in exactly the
same way as other plug-ins; in this respect, all features are created equal.
The Eclipse SDK includes the Eclipse Java Development Tools, offering an IDE
with a built-in incremental Java compiler and a full model of the Java source
files. This allows for advanced refactoring techniques and code analysis. The
IDE also makes use of a workspace, in this case a set of metadata over a flat
filespace allowing external file modifications as long as the corresponding
workspace "resource" is refreshed afterwards. The Visual Editor project
allows interfaces to be created interactively, hence allowing Eclipse to be
used as a RAD tool.
The following is a list of notable projects and plugins for the Eclipse IDE.
These projects are maintained by the Eclipse community and hosted by the
Eclipse Foundation.
1. Core projects
Rich Client Platform (Platform) is the core framework that all other Eclipse
projects are built on.
Java Development Tools (JDT) provides support for core Java SE. This
includes a standalone fast incremental compiler.

Tools projects
C/C++ Development Tools (CDT) adds support for C/C++ syntax

highlighting, code formatting, debugger integration and project structures.
Unlike the JDT project, the CDT project does not add a compiler and relies on
an external tool chain.
Graphical Editing Framework (GEF) allows developers to build standalone

graphical tools. Example use include circuit diagram design tools, activity
diagram editors and WYSIWYG document editors.
Web projects
J2EE Standard Tools (JST) extends the core JDT to include support for Java
EE projects. This includes EJBs, JSPs and Servlets.
PHP Development Tools (PDT)
Web Standard Tools (WST) adds standards compliant web development

tools. These tools include editors for XML, HTML and CSS.
Modelling projects
Eclipse Modeling Framework (EMF) a modeling framework and code

generation facility for building tools and other applications based on a
structured data model, from a model specification described in XMI.
Graphical Modeling Framework (GMF) is a generative component and runtime

infrastructure for developing graphical editors based on EMF and GEF.
Other projects
Test and Performance Tools Platform (TPTP) which provides a platform that
allows software developers to build test and performance tools, such as
debuggers, profilers and benchmarking applications.

Business Intelligence and Reporting Tools Project (BIRT), an Eclipse-based

open source reporting system for web applications, especially those based on
Java EE.
Applications Server
An application server is a software engine that delivers applications to client

computers or devices, typically through the Internet and using the Hypertext
Transfer Protocol. Application servers are distinguished from web servers by
the extensive use of server-side dynamic content and frequent integration
with database engines.
Common features
Application server products typically bundle middleware to enable

applications to intercommunicate with dependent applications, like web
servers, database management systems, and chart programs. Some
application servers also provide an API, making them operating system
independent. Portals are a common application server mechanism by which a
single point of entry is provided to multiple devices.
Java application servers

Java EE Servers
Following the success of the Java platform, the term application server
sometimes refers to a Java Platform--Enterprise Edition (J2EE) or Java EE 5
application server. Among the better known Java Enterprise Edition
application servers are WebLogic Server (BEA), JBoss (Red Hat), WebSphere
(IBM), JRun (Adobe), Apache Geronimo (Apache Foundation, based on IBM
WebSphere), Oracle OC4J (Oracle Corporation), Sun Java System Application
Server (Sun Microsystems) and Glassfish Application Server (based on Sun
Java System Application Server).
JOnAS application server was the first open source application server to have
achieved official compliance with the Java Enterprise Specification. BEA
delivered the first Java EE 5 certified application server followed by Sun
Microsystems' reference implementation GlassFish.
The Web modules are servlets and JavaServer Pages, and business logic is
built into Enterprise JavaBeans (EJB-3 and later). The Hibernate project
offers an EJB-3 container implementation for the JBoss Application server.
Tomcat from Apache and JOnAS from ObjectWeb are typical of containers
into which these modules can be put.
A Java Server Page (JSP) is a servlet from Java that executes in a Web
container—the Java equivalent of CGI scripts. JSPs are a way to create HTML
pages by embedding references to the server logic within the page. HTML
coders and Java programmers can work side by side by referencing each
other's code from within their own. JavaBeans are the independent class
components of the Java architecture from Sun Microsystems.
The application servers mentioned above mainly serve Web applications.

Some application servers target networks other than the Web: Session
Initiation Protocol servers, for instance, target telephony networks.

JBOSS
JBoss Application Server (or JBoss AS) is a free software / open source Java
EE-based application server. Because it is Java-based, JBoss AS is cross-
platform, usable on any operating system that Java supports.
Environment
JBoss AS 4.0 is a J2EE 1.4 application server, with embedded Tomcat 5.5.
Any JVM between 1.4 and 1.5 is supported. JBoss can run on numerous
operating systems including Windows, Mac OS X, many POSIX platforms, and
others, as long as a suitable JVM is present.
JBoss AS 4.2 is also a J2EE 1.4 application server, but EJB 3 is deployed by
default. It requires JDK 5. Tomcat 6 is bundled with it.
Next JBoss AS 5 will be Java EE 5 application server.
Product features
 Clustering
 Failover (including sessions)
 Load balancing
 Distributed caching (using JBoss Cache, a standalone product)
 Distributed deployment (farming)
 Enterprise JavaBeans version 3

Screens
SCREEN SHOTS













Coding
DbConnection.java
package pack;
import java.sql.Connection;
import java.sql.DriverManager;
public class Dbconnection {
public static Connection getConn() throws Exception{

Class.forName("com.mysql.jdbc.Driver");
Connection
con=DriverManager.getConnection("jdbc:mysql://localhost:3306/security_evaluation","r
oot","root");
return con;
}
Activate.java:-
/*
* To change this template, choose Tools | Templates
* and open the template in the editor.
*/
package action;
import java.io.IOException;
import java.io.PrintWriter;
import java.sql.Connection;
import java.sql.ResultSet;
import java.sql.Statement;
import javax.mail.Session;
import javax.servlet.ServletException;
import javax.servlet.http.HttpServlet;
import javax.servlet.http.HttpServletRequest;
import javax.servlet.http.HttpServletResponse;
import javax.servlet.http.HttpSession;
import pack.Dbconnection;
import pack.MailUtil;
/**
*
* @author IBN33

*/
public class activate extends HttpServlet {
/**
* Processes requests for both HTTP
* <code>GET</code> and
* <code>POST</code> methods.
*
* @param request servlet request
* @param response servlet response
* @throws ServletException if a servlet-specific error occurs
* @throws IOException if an I/O error occurs
*/
protected void processRequest(HttpServletRequest request, HttpServletResponse
response)
throws ServletException, IOException {
response.setContentType("text/html;charset=UTF-8");
PrintWriter out = response.getWriter();
try {
String id=request.getQueryString();
Connection con=Dbconnection.getConn();
Statement st=con.createStatement();
int i=st.executeUpdate("update user_reg set activate='yes',count='0' where
iduser_reg='"+id+"'");
if(i!=0){
ResultSet rt=st.executeQuery("select * from user_reg where
iduser_reg='"+id+"'");
if(rt.next()){
String name=rt.getString("name");
String uname=rt.getString("username");
String[] mail=new String[]{rt.getString("mail")};

String sub="Account";
String msg="Admin activated your account. you can login ";
//sending mail
new MailUtil().sendMail(mail, mail, sub, msg);
response.sendRedirect("users.jsp");
}
else{
out.println("internal error occured...");
}
}
else{
out.println("internal error occured...");

}
catch(Exception e){
out.println(e);
}
finally {
out.close();
}
}
// <editor-fold defaultstate="collapsed" desc="HttpServlet methods. Click on the +

sign on the left to edit the code.">
/**
* Handles the HTTP
* <code>GET</code> method.
*
*/
@Override
protected void doGet(HttpServletRequest request, HttpServletResponse response)
processRequest(request, response);
}
/**
* Handles the HTTP
* <code>POST</code> method.
*
*/
@Override
protected void doPost(HttpServletRequest request, HttpServletResponse response)
processRequest(request, response);
}
/**
* Returns a short description of the servlet.
*

* @return a String containing servlet description

*/
@Override
public String getServletInfo() {
return "Short description";
}// </editor-fold>
}
TESTING
Testing is a process, which reveals errors in the

program. It is the major quality measure employed during software
development. During software development. During testing, the
program is executed with a set of test cases and the output of the
program for the test cases is evaluated to determine if the program is
performing as it is expected to perform.
In order to make sure that the system does not have
errors, the different levels of testing strategies that are applied at
differing phases of software development are:
1. Unit Testing
Unit Testing is done on individual modules as they are

completed and become executable. It is confined only to the
designer's requirements.
Each module can be tested using the following two
strategies:
i) Black Box Testing:

In this strategy some test cases are generated as

input conditions that fully execute all functional requirements
for the program. This testing has been uses to find errors in the
following categories:
a) Incorrect or missing functions
b) Interface errors
c) Errors in data structure or external database access
d) Performance errors
e) Initialization and termination errors.
In this testing only the output is checked for
correctness. The logical flow of the data is not checked.
ii) White Box testing

In this the test cases are generated on the logic of each
module by drawing flow graphs of that module and logical
decisions are tested on all the cases.
It has been uses to generate the test cases in the following
cases:
a) Guarantee that all independent paths have been executed.
b) Execute all logical decisions on their true and false sides.
c) Execute all loops at their boundaries and within their
operational bounds.
d) Execute internal data structures to ensure their validity.
2. Integrating Testing
Integration testing ensures that software and subsystems
work together as a whole. It tests the interface of all the
modules to make sure that the modules behave properly when

integrated together.
3. System Testing
Involves in-house testing of the entire system before
delivery to the user. It's aim is to satisfy the user the system
meets all requirements of the client's specifications.
4. Acceptance Testing
It is a pre-delivery testing in which entire system is tested
at client's site on real world data to find errors.
validation
The system has been tested and implemented
successfully and thus ensured that all the requirements as listed in the
software requirements specification are completely fulfilled. In case
of erroneous input corresponding error messages are displayed.
Conclusion:-
In this paper we focused on empirical security evaluation of pattern

classifiers that have to be deployed in adversarial environments, and
proposed how to revise the classical performance evaluation design step,
which is not suitable for this purpose.
Our main contribution is a framework for empirical security evaluation that

formalizes and generalizes ideas from previous work, and can be applied to
different classifiers, learning algorithms, and classification tasks. It is
grounded on a formal model of the adversary, and on a model of data
distribution that can represent all the attacks considered in previous work;
provides a systematic method for the generation of training and testing sets
that enables security evaluation; and can accommodate application-specific
techniques for attack simulation. This is a clear advancement with respect to
previous work, since without a general framework most of the proposed
techniques (often tailored to a given classifier model, attack, and
application) could not be directly applied to other problems.
An intrinsic limitation of our work is that security evaluation is carried out
empirically, and it is thus datadependent; on the other hand, model-driven
analyses [12], [17], [38] require a full analytical model of the problem and of
the adversary’s behavior, that may be very difficult to develop for real-world
applications. Another intrinsic limitation is due to fact that our method is not
application-specific, and, therefore, provides only high-level guidelines for
simulating attacks. Indeed, detailed guidelines require one to take into
account application-specific constraints and adversary models. Our future
work will be devoted to develop techniques for simulating attacks for
different applications.
Although the design of secure classifiers is a distinct problem than security
evaluation, our framework could be also exploited to this end. For instance,
simulated attack samples can be included into the training data to improve
security of discriminative classifiers (e.g., SVMs), while the proposed data
model can be exploited to design more secure generative classifiers. We
obtained encouraging preliminary results on this topic
BIBLIOGRAPHY
ORACLE Ivan Bayross
Java 2, The Complete Reference Patrick Naughton
& Herbert Schildt
Java Servlet Programming Jason Hunter

& William Crawford
HTML: The Definition Guide Musciano
Developing Java Servlet James Goodwill
Java Server pages Larne Pekowsky
REFERENCES
[1] R.N. Rodrigues, L.L. Ling, and V. Govindaraju, “Robustness of
Multimodal Biometric Fusion Methods against Spoof Attacks,” J. Visual
Languages and Computing, vol. 20, no. 3, pp. 169-179, 2009.
[2] P. Johnson, B. Tan, and S. Schuckers, “Multimodal Fusion Vulnerability

to Non-Zero Effort (Spoof) Imposters,” Proc. IEEE Int’l Workshop
Information Forensics and Security, pp. 1-5, 2010.

[3] P. Fogla, M. Sharif, R. Perdisci, O. Kolesnikov, and W. Lee,

“Polymorphic Blending Attacks,” Proc. 15th Conf. USENIX Security
Symp., 2006.
[4] G.L. Wittel and S.F. Wu, “On Attacking Statistical Spam Filters,” Proc.
First Conf. Email and Anti-Spam, 2004.
[5] D. Lowd and C. Meek, “Good Word Attacks on Statistical Spam Filters,”
Proc. Second Conf. Email and Anti-Spam, 2005.
[6] A. Kolcz and C.H. Teo, “Feature Weighting for Improved Classifier
Robustness,” Proc. Sixth Conf. Email and Anti-Spam, 2009.
[7] D.B. Skillicorn, “Adversarial Knowledge Discovery,” IEEE Intelligent

Systems, vol. 24, no. 6, Nov./Dec. 2009.

Full Doc Security Evaluation

Uploaded by

Copyright:

Available Formats

Full Doc Security Evaluation

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Full Doc Security Evaluation

Uploaded by

Copyright:

Available Formats

Security Evaluation of Pattern Classifiers under Attack

Security Evaluation of Pattern Classifiers under Attack Page 1

The objective of this application is Pattern classification systems are

1.1 ABOUT THE ORGANIZATION

1.2 About the project

Security Evaluation of Pattern Classifiers under Attack Page 2

2. PROBLEM DEFINITION AND FEASIBILITY ANALYSIS

Security Evaluation of Pattern Classifiers under Attack Page 3

2.1 Definition of the problem

To create or develop a new system first we have to study the prior

DISADVANTAGES OF EXISTING SYSTEM:

ADVANTAGES OF PROPOSED SYSTEM:

2. The presence of an intelligent and adaptive adversary makes the

Security Evaluation of Pattern Classifiers under Attack Page 6

Multimodal biometric systems for personal identity recognition have

The feasibility of the project is analyzed in this phase and business

Three key considerations involved in the feasibility analysis are

2.2.1 Operational Feasibility

Security Evaluation of Pattern Classifiers under Attack Page 8

In this test, the operational scope of the system is checked. The

2.2.2 Technical Feasibility

2.2.3 Economical Feasibility

3.1 Hardware and Software Specifications

Security Evaluation of Pattern Classifiers under Attack Page 10

compared with other candidates. This section first summarizes the

Design is essentially a blue print or it acts as a bridge between the

Security Evaluation of Pattern Classifiers under Attack Page 11

 Being a web-based system also enables the Company staff to

Security Evaluation of Pattern Classifiers under Attack Page 12

 The System should provide an option to generate a Agents Reports, with

1.1 High level design

Security Evaluation of Pattern Classifiers under Attack Page 13

DATA FLOW DIAGRAMS

Security Evaluation of Pattern Classifiers under Attack Page 14

approach emphasis on the logic underlying the system, by using

it defines a source (originator ) or destination of system data.

It indicates data flow-data in motion. It is a pipeline through

Security Evaluation of Pattern Classifiers under Attack Page 15

It represents a process that transforms incoming data flow(s) into outgoing

it is a data store-data at rest, or a temporary repository of data. Here I am

They are explained by

GANE AND SARSON NOTATION

Security Evaluation of Pattern Classifiers under Attack Page 16

DEMACRO YORDAN NOTATION

Security Evaluation of Pattern Classifiers under Attack Page 17

Security Evaluation of Pattern Classifiers under Attack Page 18

E-R (Entity-Relationship) Diagram is used to represents the

The symbols used in E-R diagrams are:

Represents Entity sets.

Represent Relationship Sets.

Line represents flow

Security Evaluation of Pattern Classifiers under Attack Page 19

Activate new user

activate blocked users if need

Apply spam filter

Decrypt the Message

Security Evaluation of Pattern Classifiers under Attack Page 20

UML is a notation that resulted from the unification of Object

An Overview of UML in five notations