1.

INTRODUCTION
A Honey pot is a computer system on the Internet that is expressly set up to attract and "trap" people who attempt to penetrate other people's computer systems. A "honeypot" is a tool that can help protect for network from unauthorized access. The honeypot contains no data or applications critical to the company but has enough interesting data to lure a hacker. A honeypot is a computer on your network the sole purpose is to look and act like a legitimate computer but actually is configured to interact with potential hackers in such a way as to capture details of their attacks. It is a recent concept that has been adopted by the masses for production implementation to assist in a defensive network security posture. A compromised Honey pot offers a wealth of features that can assist with intelligence data gathering, incident response for a better understanding of who the attacker is, what method the attacker used to gain access and the results of the attackers unauthorized attack for possible prosecution measures. Internet security is increasing in importance as more and more business is conducted there. Yet, despite decades of research and experience, we are still unable to make secure computer systems or even measure their security. As a result, exploitation of newly discovered vulnerabilities often catches us by surprise. Exploit automation and massive global scanning for vulnerabilities enable adversaries to compromise computer systems shortly after vulnerabilities become known. We are implementing in our project in Java, based on client and server technology. We are also deployed the cryptographic procedure for maintains the security. In this concept, the alternate path selecting is main factor for eliminate the intruder in the network and also utilize the network in better manner. The more realistic the interaction, the longer the attacker will stay occupied on honeypot systems and away from your production systems. The longer the hacker stays using the honeypot, the more will be disclosed about their techniques. This information can be used to identify what they are after, what is their skill level, and what tools do they use. All this information is then used to better prepare your network and host defenses. Honeypots are neither like Firewalls that are used to limit or control the traffic coming into the network and to deter attacks neither is it like IDS (Intrusion Detection Systems) which is used to detect attacks. However it can be used along with these. Honeypots does not solve a

specific problem as such, it can be used to deter attacks, to detect attacks, to gather information, to act as an early warning or indication systems etc. They can do everything from detecting encrypted attacks in IPv4 networks to capturing the latest in on-line credit card fraud. It is this flexibility that gives honeypots their true power. It is also this flexibility that can make them challenging to define and understand. They are a resource that has no authorized activity, they do not have any production value. Honeypots are a relatively new and highly dynamic technology. Because they are so dynamic, it is difficult to define just what they are. Honeypots are unique in that they are not a solution in and of themselves; they do not solve a specific security problem. Instead, they are highly flexible tools with many different information security applications. This contrasts with such technologies as firewalls and intrusion detection systems (IDSs), which are easier to define and understand as they solve specific problems. Firewalls are a prevention technology; they are network or host solutions that keep attackers out. IDSs are a detection technology; their purpose is to detect and alert security professionals about unauthorized or malicious activity. Honeypots are tougher to define because they can be involved in aspects of prevention, detection, information gathering, and much more. For the purpose of this project, we will define a honeypot as follows A honeypot is an information system resource whose value lies in unauthorized or illicit use of that resource. This definition was developed by members of the Honeypot mail list, a public forum made up of over 5,000 security professionals. The definition was difficult to develop, as honeypots can come in so many different shapes and sizes. As a result, this definition is very broad in scope, as it has to cover many different applications of honeypots. The definition of a honeypot does not indicate how a honeypot works or what its purpose is. Instead, its definition refers to how a honeypot generates its value. Simply put, honeypots are a technology whose value depends on the bad guys interacting with it. All honeypots work on the same concept: Nobody should be using or interacting with them-any transactions or interactions with a honeypot are by definition unauthorized. A honeypot contains no value as a production-oriented component of an information infrastructure-it does no real productive service. Any transactions processed, any logins attempted, or any data files accessed on a honeypot are most likely malicious or unauthorized

activities. For example, a honeypot system can be deployed on an internal network. This honeypot would have no production value and no one in the organization should be using it. It could appear to be a file server, a web server, or even an employee's workstation. If someone interacts with that system, they are most likely committing some unauthorized or malicious activity.In fact, a honeypot does not even have to be a computer. It can be any type of digital entity (often called a honeytoken) that has no production value. For example, a hospital could create a false set of electronic patient records labeled George W. Bush.Because these records are honeypots, nobody should be accessing or interacting with them. These records could then be implanted into a hospital's patient database as a honeypot component. If any employee or attacker attempted to access these records, this would indicate unauthorized activity because no one should be using these records. If anyone or anything accesses the records, they could also generate an alert. It is the very simplicity of this concept that gives honeypots their tremendous advantages.

2. SYSTEM ANALYSIS
System analysis is defined as the process of gathering and interpreting facts ,diagnosing problems and using the facts to improve the system.The objective of system analysis phase are the establishment of the requirements for the system to be acquired, developed and installed. Fact finding or gathering is essential to any analysis of requirements. If there is no existing system ,then analysis only defines the requirement. Designs which follow ,propose a new system that meets these requirements. This new system may be built afresh or by changing the existing system. Development begins by defining a model of new system and implements ths model to working system. System design is the process of planning a new business system to replace or complement the working system. During analysis both quantitative and quantitative evaluations are conducted. Analysis are conducted with the following objectives. 1. Evaluate the proposed system concept for feasibility. 2. Performing technical and economical analysis. 3. Establish the different constraints that exist for the development of the project 4. Create a system that forms the foundation for all subsequent works

2.1Existing System
A honey pot is performed as a monitoring system on servers .Systems which possess a lot of vulnerabilities to attract the attackers.Most of the previous work on intrusion detection focuses on activities generated by a single source, resulting in many undetected intrusions. Many existing systems require manual definitions of normal and abnormal behavior (intrusion signatures). It is impossible to identify abnormalities automatically using machine learning or data mining techniques. These works analyze network or system activity logs to generate models or rules, which the system can use to detect intrusions that can potentially compromise the system integrity or reliability. However, most of the previous work on intrusion detection focuses on activities generated by a single source, resulting in many false positives and undetected intrusions. In the existing an intruder can easily enter into system and access the system. So we have to prevent this intruder entry for the security purpose.

2.2Proposed System
Honeypot utilizes idea for assigning permissions to an authenticated client.The front end server decides which client is legitimate and which client should be deflected to the