Using Database Management System to Generate, Manage and Secure Personal Identification Numbers (PIN)

Abstract

A number of problems are associated with the generation, management and security of PINs, a subset of password. The PINs may be recharge card used by GSM operators or for authentication in ATM. The problems associated with the use of these PINs range from scratching off any of the recharge PIN numbers in recharge card to loss of PIN number or entering invalid number in the case of authentication. It usually takes time for the customer service of the service provider or system administrator to provide convincing solution to these problems promptly when it occurred. PINs generation could seem like simply arranging ranges of number and feeding it into the telecommunication systems such as mobile handsets or ATM to grant access but it requires a specialized and secured way to generate, store and manage it in order to achieve prompt access. This paper focused on the development of database concept to provide solution to these problems by desiging a system by which the PINs generated can be effectively stored and managed so that userss can have immediate access to the PINs if they can provide the identification number on the card. Succintly, the paper discusses the design of a system that generates, manages and secures PINs application using Visual Basic Version 6.0 for designing the front and interface and Microsoft Access 2007 as the database. The system was implemented using real data and the result was successful.

ATM PIN generation - a formal mathematical model to generate PIN using regular grammar, context free grammar and recognition through finite state machine, pushdown automata

“…Since they are derived from primary account number user cannot select their PIN. If the card is issued again new pin must be generated (Bond and Zielinski, 2003;Akomolafe and Afeni, 2014).…”

“…• IBM 3624 + offset: in this method user is allowed to select their PIN which is interpreted with natural PIN based on its modulo value to derive the respective offset value. The offset can be stored in the database of the issuer or on the user card track (Akomolafe and Afeni, 2014).…”

“…PVV itself is a logical value calculated from PIN validation key index (PVKI) which gets encrypted. The PVV can be stored in the database of the issuer or on the user card track (Akomolafe and Afeni, 2014).…”

“…Whether the strategy conveyed is by word technique, i.e., by converting a 'word' to corresponding numbers on keypad, date method, i.e., key dates in different configuration, saving PIN on mobile phone in unidentifiable way or using mathematical logic to mask the direct PIN, forever it is better and fine to apply a technically stronger PIN to crack (https://homesecurity. about.com/od/online/fl/Using-PINs-Safely.htm; Akomolafe and Afeni, 2014;Bond and Zielinski, 2003).…”