User

GEOGRAPHIC LOCATION BASED AUTHENTICATION It proposed a new approach for resolving problems presented in existing scheme.In this approach user get provided more secure and rememberable password for authentication as compare to existing scheme by extension of mnemonics password in Geopass-Note technique for better and improved system for user authentication with addition of image captcha in registration phase. It also extended approach with use of multiple locations for password selection

such as: • Sometime users share their passwords with their friends, staff members. • Users may write their password on sticky notes and paste on the bottom of the keyboard or monitor screen. • Users usually use their husband name, child name, pet name as their password but by social engineering hacker could hack password easily. • Servers save password that may be compromised because data store on server in plain text and plain text could easily hacked by hacker. • Some users should not reuse old

attack get the information by using direct observation methods , such as while a user enters a password , the attacks records the input or watches over the user’s shoulder [1]. The attack can be applied to both touchscreen and non-touchscreen devices. To effectively prevent shoulder surfing, the disappearing stroke should be provided by default. This means that after the user has enter a stroke, it disappears. Users should be given the option to select line snaking where the line

2.2 System Analysis 2.2.1 Fact Finding It involves technical staff working with customers to find out about the application domain, the services that the system should provide and the system’s operational constraints. There is a variety of techniques can be used for analysing and designing software solution. • Interviewing and questionnaires • Brainstorming • Prototyping • Research and survey As the specific techniques will vary, based on the type of application, the skill and sophistication

Answer 1.1: The role of User master record in assignment of appropriate rights The user master record plays a critical role is assigning because it comes into play while logging into the SAP system. It decides which role is assign to the user. Generally user master records are designed as client specific. As a result, one needs to maintain each and every client’s record separately. Users can be created and maintained through Central User Administration. For instance, time limit can be set while entering

contexts of mobile users and their activities for better predicting customer preferences. In existing, only limited numbers of dimensions are considered to predict the user preferences. It cannot precisely predict about people’s daily activities, which could be extremely difficult due to the inherent randomness of human behavior. The proposed work focuses on the number of dimension combination to be increased for each event with respect to context and action rule of a user. User clustering is constructed

The Pocket Protector App is a programed that allows users to store various information such as passwords and pine codes securely into their smartphone’s. The purpose of the application is to provide users with a convenient way of organizing important security data in one application that is user-friendly and visually appealing. Emerging technologies are replacing the need for people to write things down, which creates another problem. People are finding it difficult to keep up with passwords, usernames

Adopting eLockBox to achieve Mobile Data Security Akshay Prakash Pawar1, Rohan Manoj Thakkar2, SaurabhSahebrao Salunkhe3, SarveshSuhasKapre4 1,2,3,4Student of Computer Engineering Department 1,2,3,4K. J.Somaiya College of Engineering Mumbai, Pin no.400077 1akshay070993@gmail.com,2rohan.m.thakkar@gmail.com,3saurabh.salunkhe81@gmail.com,4sarveshk1808@gmail.com Abstract: Smartphones like android are becoming common. Phones are very small in size and hence easy to misplace. Even a small inattention

contain a combination of numbers and letters like pe15 or letters only like stzm (Massachusetts Institute of Technology 2001). A transaction code is important in SAP R/3 system for a number of reasons. First, when SAP R/ 3 system is accessed by a user, a query is initiated at the application level of the data base and is performed using SQL (ERP Great 2016). Secondly, the transaction code helps in locating and according a code to data transferred to the Front End System from the Relational Database

Contents i List of Figures ii 1.0. Introduction 1 1.1. Purpose 1 1.2. Scope of Project 1 1.3. Glossary 1 1.4. References 1 1.5. Overview of Document 2 2.0. Overall Description 3 2.1 System Environment 3 2.2 Functional Requirements Specification 3 2.3 User Characteristics 3 2.4 Non-Functional Requirements 4 3.0. Requirements Specification 5 3.1 External Interface Requirements 5 3.2 Functional Requirements 5 3.3 Detailed Non-Functional Requirements 6 Index 7   List of Figures < generate here > 1