Method and apparatus for secure credential entry without physical entry

[0001] This application claims benefit from U.S. Provisional Patent Application No. 60/724,279 filed Oct. 7, 2005, the entire contents of which are incorporated herein by reference.

[0002] The invention relates to the field of computer security and more particularly to the field of automated user authentication at system startup.

[0003] In recent years, there has been growing use of security architectures whereby the user is required to provide multiple credentials at different stages of logging onto microprocessor based systems such as personal computers (PCs), Internet terminals and personal data analyzers (PDAs). In the simplest form these credentials is a user identity, which is checked against a list of valid user identities stored within the system, and a password, which is validated against stored data relating to the user identity to verify the user identity.

[0004] In these instances entering the requisite information—logging on or login—is a physical event, most commonly the typing of both user identity and password using a symbol entry device such as a keyboard attached to the system. It has therefore been a normal part of accessing computer systems for the software to display a simple login screen or window where there exist fields for the user identity and password to be entered. It was initially a pre-requisite of these login screens that the user remembered both parts of the login information. Typically, both were simple alphanumeric codes for the user to remember and consequently, they were often easily guessed or determined.

[0005] Currently, when using computer systems and software applications, a person has a large number of passwords, for example for accessing a home computer, a work computer, Internet banking, music downloads, electronic mail, secured files, encryption keys, and online auction sites amongst the most common ones. A user memorizes these passwords, writes then down, stores them on their computer, or synchronizes them all so that they are all the same. Another approach to password management is to allow the system to automatically store login data. This obviously makes the security of an individual's personal information quite weak allowing others to rapidly access said information and use it once they have access to the computer system. This is a basis of the criminal activity commonly known as “identity theft.” The requirement for an individual to validate the legitimacy of their authentication information, be it only a single application or many, lies at the very heart of the security of any information based activity, and thus it has been the matter of much research.

[0006] With the continuing advances in semiconductor circuit design, the density of memory circuits has continued to advance, whilst their power requirements have continued to decrease. As a result there has been a rapid proliferation of uses of semiconductor memory including the provision of portable solid state memory devices. This has replaced prior magnetic storage media including tapes and diskettes, which were known colloquially as “floppy discs.” Today, solid-state memory is packaged within many physical formats as the basic function is overtaken by fashion, style and marketing. A common form of solid-state memory is the USB (Universal Serial Bus) memory “key” for interfacing with a USB port of a host computer system.

[0007] Typically, these peripheral memory storage devices are “Plug and Play” devices, using existing “standard” device drivers such that they operate identically on all systems without any device driver installation. For example when using Microsoft® Windows XP™ operating system based computer systems, a computer detects that a USB device is coupled to the computer and automatically interrogates the device to learn its capabilities and requirements. Using this information, the computer then automatically associates a standard driver for supporting the determined capabilities and requirements previously loaded with the operating system. Alternatively, a device specific device driver is loaded. These drivers support existing functions and prevent operations that are either unsupported or potentially problematic. Later, when the device is disconnected from the bus, the operating system automatically disables the device from the bus and, optionally unloads its driver from the system.

[0008] It is therefore possible to store within the memory stick security information of a user to be accessed by either the user or the computer system when needed; however, since this requires accessing the memory device, the device drivers must be in execution on the host computer system prior to accessing of the data. Thus, to maintain security, device specific drivers are typically required. Unfortunately, the very first login screen for accessing Windows operating systems either prevents access to or precedes initialization of device specific drivers. Thus, security data for the first login screen always has to be entered into the system from the keyboard and from the personal memory of the user or would have to be completely automated using functionality of the operating system for the computer—stored within the hard drive of the computer and automatically entered by the operating system regardless of who is starting the operating system. Neither of these solutions is both convenient and secure.

[0009] It would therefore be advantageous to provide a method and apparatus for automatically populating the login window of a Windows® based computer system that does not require modification of the operating system and that maintains a level of security for the computer.

[0010] In accordance with the invention there is provided a method comprising: providing a computer system; providing a peripheral memory storage device coupled with an interface of the computer system for communication therewith; starting a Windows® based operating system on the computer system; displaying a Windows® login screen; and, automatically populating fields within the Windows® login screen with data extracted from the peripheral memory storage device and provided to the computer system via the interface, the interface enabled by the Windows® operating system prior to display of the login screen.

[0011] In accordance with another embodiment of the invention there is provided a method comprising providing a computer system comprising a BIOS memory having a BIOS stored therein; providing a peripheral memory storage device coupled with an interface of the computer system for communication therewith, the interface enabled by execution of default interface drivers forming part of the BIOS, the peripheral memory storage device having stored therein user authorization data of a user; in response to a system login request event, transferring from the peripheral memory storage device said user authorization data via the interface in accordance with a functionality of a manual symbol entry device.

[0012] In accordance with another embodiment of the invention there is provided a method comprising: providing a computer system comprising a BIOS memory having a BIOS stored therein, the BIOS including support programming for a first symbol entry device for having symbols manually entered therewith for provision to the computer system, the BIOS further including a default interface driver forming part of the BIOS and for supporting a default interface and peripheral devices coupled therewith; providing a peripheral memory storage device having stored therein user authorization data and coupled with the default interface for communication therewith, the default interface enabled by execution of the default interface driver; executing an operating system application of the computer system comprising a system login request event; retrieving from memory within the peripheral storage device first user authorization data; and, transferring from the peripheral storage device in response to the system login request event the first user authorization data via the default interface mimicking data entered at the first symbol entry device.

[0024] Referring to FIG. 1, shown is a block diagram illustrating interconnectivity between a computer system 115 and a flash drive peripheral memory storage device 110 for carrying out an embodiment of the invention. Illustrated is a computer system 115, with a central microprocessor and memory block 101, a first input/output controller and hardware block 102 providing access to internal storage elements such as floppy drive 118a, hard disk drive 118b and external storage elements such as CD drive 119a and DVD drive 119b. These are coupled via the computers internal bus 107 to which is also connected Flash EEPROM memory 103 which holds the BIOS for the computer. Also within the computer and accessing this internal bus 117 are a second input/output controller 109 which provides interconnectivity to generic computer connectors for the optional addition of dynamic pointer (Mouse) through connector 109a, a keyboard via 109b together with the serial port 109d, parallel port 109e and auxiliary port 109c. User visibility of computer activities is via display element 104 and its associated controllers. Additional functionality such as wireless interface is optionally provided through the use of PMCIA interface 105, which comprises sub-elements of a controller and physical sockets. Finally accessing this central communications bus 107 is the Universal Serial Bus portion of the computer 106, comprising connector ports 106a and USB controller 106b.

[0025] Interconnected to all of the different elements of the computer is a power source in the form of power supply 120.

[0026] Prior to starting the computer—power up, a user connects a peripheral memory storage device 110 to an interface port of the computer in the form of USB port 106a. Coupling is achieved by mating connector shell 111 on the peripheral memory storage device with the connector of USB port 106a. Internal to the peripheral memory storage device 110 are a third input/output controller 112, internal microprocessor 113 and memory 114.

[0027] At power up of the computer 115, the microprocessor element 101 initiates reading of the BIOS (basic input/output memory system) memory 103 thereby extracting the built-in instruction codes that determine how the computer system functions absent programming from a disk. On personal computers 115, the BIOS contains all the code required to control a keyboard 116, 104, disk drives 118a, 118b, 119a, 119b, serial communications 106, 109d and a number of other miscellaneous functions.

[0028] Referring now to FIG. 1b, after the execution of the instruction codes retrieved from the BIOS, the computer 115 begins the loading and executing of instruction data relating to an operating system defined for this machine. During this process, the display 104 optionally displays progress information and, for example, the keyboard 116 is disabled to prevent errors from invalid command entry or keyboard interrupts. At some point a software application 121 in execution in the form of the operating system software generates a prompt that typically requests the user to enter 3 fields of information. These are, for example, user name 121a, password (security credential) 121b and a name of the computer being logged into 121c, which is typically either a discrete identity of the computer system or that of a central server in the event of the computer being networked.

[0029] Now referring to FIG. 1c as the entry screen 121 is displayed, the microprocessor 101 places onto the internal bus a command 130 denoting readiness to accept input for example in response to a user initiated sequence. More commonly, the user initiates data entry from the device by actuating a control input port on the device, for example a button or imager. Sensing this, the peripheral memory storage device 110 extracts a first user credential—user name 121a—from the memory 114 wherein it is converted by circuitry within the peripheral memory storage device in the form of a microprocessor 113 to a command sequence matching an anticipated command set 131 of a user interface and placed onto the bus alongside with other necessary data of flags being set to denote completion of activity. For example, in the case of a keyboard, a tab value is inserted between the data fields and a carriage return data value is inserted after the data. This user name 121a is then typically displayed as text 104b in the appropriate field of the screen. Subsequently, the peripheral memory storage device 110 extracts the second credential—password 121b—and repeats the communication of this as a data command 132 onto the bus 107; typically, password data is obfuscated during display thereof. Finally a third credential is optionally extracted and communicated 133 representing the reference identity 121c for the computer being accessed.

[0030] As is noted, a user of the computer system is not involved in the user name and password entry process. Thus, once the peripheral memory storage device is coupled to the computer and is operational, the computer is logged into automatically without user intervention. Absent the peripheral memory storage device, the computer is accessible by way of manually providing user authorization data thereto.

[0031] Alternatively, the peripheral memory storage device is connected to a PMCIA interface 105 of the computer as opposed to USB interface 106. This is particularly applicable to systems wherein the PCMCIA interface is enabled during the login event. Further alternatively, the peripheral memory storage device is coupled to one of a parallel port and a serial port of the computer. Further alternatively, the peripheral memory storage device is wirelessly coupled to a wireless interface of the computer. Of course, it is evident to someone of skill in the art that the port to which the peripheral memory storage device is coupled is supported by the operating system at the start up logon display screen and supports the functionality described hereinabove for mimicking of a data entry device.

[0032] FIG. 2 illustrates an ability of the peripheral memory storage device to provide secure user credential information via different physical interfaces. The computer bus 201 communicates to an input/output interface 208 for physical entry management, a display interface 204 and another input/output interface 205 controlling USB ports. Optionally coupled with these interfaces is one or more of a keyboard 210, handwriting tablet 209, voice transducer 206, sound comparator 207, and a touch sensitive screen 211.

[0033] As the BIOS 213 is loaded from ROM memory, microprocessor 212 polls all recognized data entry ports to identify which of the different data input devices, namely keyboard 210, tablet 209, touch sensitive screen 21 and sound analysis elements 206 or 207 are present. As with the previous embodiment, peripheral memory storage device 212 is already coupled to a USB port, in this case 203a. As the microprocessor 212 loads the BIOS 213 and validates the presence of user interface devices, the peripheral memory storage device monitors and determines a user input device to mimic.

[0034] When the operating system prompts to accept the first user credential, the peripheral memory storage device extracts said information from its memory store, converts it to the appropriate command syntax for the device being mimicked and provides this to the USB port 203a. This sequence is repeated for each user authorization data prompted for by the operating systems boot-up procedure. In this manner the computer system is started securely without the intervention of the operator in and there is provided a compact, portable module interfacing with the communications port of the microprocessor based system or equipment.

[0035] It is therefore clear to those skilled in the art that bypassing of manual user entry of user authorization data by exploiting credentials stored within a peripheral memory storage device increases security as the user authorization data are optionally quite complex and indeterminate. Further, a user does not need to use memorable passwords, user names, or system equipment identities. Of course, with the storage of user authorization data in the peripheral memory storage device, the user authorization data are optionally radically different and without common theme even within a small group or enterprise. Optionally, the user authorization data is modified at short intervals, something that is very difficult to effect with user memorized passwords.

[0036] Further, it is evident to those skilled in the art that this automatic entry of the user authorization data is extensible and repeatable for the accessing of subsequent software applications, database access etc. In this manner the user authorization data are optionally different application-to-application, which is generally not the case today as users limit the number of passwords they have to remember.

[0037] FIG. 3 shows a typical flow diagram wherein the peripheral memory storage device has the ability to perform communication via any default driver loaded by the BIOS even where said devices are not currently present or configured for the system. This feature exploits the desire of developers of BIOS to maximize a number of computer platforms their system is deployed on. Therefore the BIOS often contains device drivers for multiple port formats, interface equipment protocols etc. Further optionally, the peripheral memory storage device mimics an element of the system such that a successful power up is achieved even if said interface is not present. One such common example is a keyboard—most personal computers do not start up without the presence of a keyboard.

[0038] At power up, the computer triggers the BIOS to load and the peripheral memory storage device monitors the computer bus for commands validating the presence of different elements. Upon detecting a command on the computer bus, the module decodes the command request to define the physical element being sought. If the element matches one that the peripheral memory storage device supports then the internal memory of the module is addressed to denote this as a valid option. Thereafter, if the real element has not responded within a pre-determined time period, the peripheral memory storage device transmits a command string mimicking a validation string from the said element. As all drivers within the BIOS are loaded, this loop repeats until it notes a completion of the BIOS loading.

[0039] At this point, the peripheral memory storage device extracts a list of valid drivers and using a prioritized look-up defines the user input device it will mimic and loads appropriate translation command structures for the selected user input device. Thereafter upon waiting and noting a prompt for input user authorization data from the operating system, the peripheral memory storage device extracts the appropriate user authorization data sequence, converts it and places the converted user authorization data sequence onto the computer bus wherein the microprocessor retrieves the sequence and undertakes validation of the user. A result of this process is a subsequent accepting or rejecting of the user authorization attempt.

[0040] Therefore, it would be evident to one skilled in the art that the peripheral memory storage device may detect the presence of and mimic multiple user interfaces including, but not limited to a keyboard, mouse, handwriting tablet, voice recognition system, etc.

[0041] Referring to FIG. 4, a further embodiment of the automation is outlined wherein the personal computer 400 has been assembled as per normal practices and thus upon system power up executes a BIOS 402. The computer 400 has USB capabilities 403 wherein a USB controller 404 addresses USB slots 405a, 405b. The computer only has, for example, two USB ports 405a, 405b that are connected to peripheral devices. In this exemplary embodiment, USB port 405a is connected to a USB enabled keyboard 411 and the second USB port 405b is connected to a USB enabled mouse 412. Therefore the only accessible interfaces are accessible via the general input/output section 406 of the computer 400. Within this input/output section 406 there is a controller circuit 407 which has several standard connector ports of which one is an industry standard serial port 408.

[0042] In this embodiment the user connects the peripheral memory storage device 410 to this serial port 408 using an adapter 409. Now at system power up the BIOS 402 is loaded and the peripheral memory storage device 410 detects the activity but also recognizes by the assigned commands on the data bus 401 provided via the serial port 408 that it is attached to serial port 408. The peripheral memory storage device implements additional coding of the user security credentials such that when provided from the peripheral memory storage device 410 to the serial port 408 and via the controller 407 to the internal system bus 401, they appear to mimic a user data input device supported on the port to which the peripheral data memory storage device is coupled. In this manner the computer is automatically provided the user authorization data.

[0043] It is apparent to those skilled in the art that this embodiment is extensable such that the peripheral memory storage device is optionally coupled to any non-occupied port of the computer supported by the BIOS and supporting mimicking of a user text data entry device therefrom. Additionally that when coupled to said non-occupied port the peripheral memory storage device is configured to mimic other physical interface devices such as handwriting tablet, microphone, image recognition etc and not simply the default embodiment of a keyboard.

[0044] FIG. 5 shows a simplified schematic of a peripheral memory storage device for secure log-on wherein additional protection is achieved. The peripheral memory storage device requires verification of a physical attribute of the user prior to releasing the internally stored credentials to an application.

[0045] The computer 500 comprises a USB interface section 501 and a USB port 502. Into the USB port 502 is plugged the peripheral memory storage device 504. At power up of the system, the microprocessor 509 begins loading the default configuration and drivers from BIOS 508 and then executes the loading of the operating system. At this point the peripheral memory storage device detects for a prompt for user data to be provided from an attached physical entry device 510 and begins the loading under its own internal processor 505 of user authorization data prior to the module interface controller 504. In doing so, the microprocessor triggers the display of a message on display 511 or alternatively an LED on the peripheral memory storage device being activated.

[0046] The message is for prompting a user to physically verify their identity directly to the peripheral memory storage device with, for example, a biometric scan. A first such embodiment comprises fingerprint verification wherein the user makes finger contact with a fingerprint sensor in the peripheral storage device 507 or in communication therewith, which forms a digital representation of a fingerprint and provides this to an analyzer 506 for comparison with a template based on a reference fingerprint and stored in memory 513.

[0047] After the fingerprint has been verified, the peripheral memory storage device controller 505 continues the process of extracting the user authorization data and placing these onto the internal bus 514 of the computer via the USB interface port and in accordance with an operation of a user data entry device in the form of a keyboard. In this manner therefore the peripheral memory storage device mimics the keyboard entry of the user authorization data and only does so after a physical verification of a biometric information sample. This enhances security, preventing unauthorized use of a peripheral memory storage device when it is found, for example after being misplaced or stolen or when it is left coupled with a computer system.

[0048] It will be evident to someone skilled in the art that the biometric transducer and analyzer are optionally other biometric recognition systems, for example, retinal scan, iris scan, facial recognition, handwriting recognition, and voice print recognition. Further, the sensor 507 and analyzer 506 are optionally a separate module to the peripheral memory storage device 503. For example, the separate module is optionally coupled to another USB port on the computer system and is controlled by the peripheral memory storage device.

[0049] The structure and content of user authorization data is of arbitrary length and arbitrary content limited by the operating system requirements. Further, the user authorization data is digitally provided to the operating system. As such, allowable characters include characters not normally accessible to users entering them at, for example, a standard keyboard. In this manner the degree of security to the system is increased dramatically as the number of combinations for a password increases substantially and the ability to try some available combinations is extremely limited and sometimes beyond the scope of available input devices.

[0050] FIG. 6 shows a simplified flow diagram for a peripheral memory storage device wherein an application prompts for reverification of user authorization data under certain circumstances. At 301 the user is prompted to verify their identity by providing a a biometric information sample to an authentication process. The process is in the form of a fingerprint authentication process. Upon placing a finger on a sensor, data relating thereto is acquired 302 and analysed to authenticate the data 303. If the authentication fails then the system returns to 301 and awaits a new sample.

[0051] If the authentication is successful then the system at 304 logs the time of this authentication 304a and resets a timer 304b. As the user progresses to use the computer system the application is repeatedly performing a sequence of tests in the background and as follows:

• • [0052] at 305 the computer system checks for a predetermined period of inactivity
  • [0053] at 306 the computer system checks for a predetermined period of time to have elapsed
  • [0054] at 307 the computer system checks for whether the user has requested to download files from certain secure information storage media
  • [0055] at the computer system 308 checks for whether the user has requested to upload files to certain secure information storage media
  • [0056] 309 the computer system checks for whether the user has been asked to provide secure information

[0057] At each check the system determines whether or not to request the user to provide a further biometric information sample to revalidate their identity. If not the system loops back to 304 otherwise it loops back to 301.

[0058] Referring to FIG. 8 an embodiment is shown wherein the failure to provide correct user authorization data for verification results in disabling of the peripheral memory storage device either temporarily or permanently.

[0059] The computer 801 comprises a USB port 805 to which is coupled a peripheral memory storage device 806 providing secure user authorization data entry via keyboard mimicking. After the software application has prompted for entry of user authorization data, the user provides a biometric sample via the sensor 809, which is analyzed by the biometric analyzer 808, and a result is provided to internal microprocessor 807 of the peripheral memory storage device 806. If the data is authenticated then the user authorization data are entered automatically and securely by mimicking keyboard function of the peripheral memory storage device and data extracted from the peripheral memory storage device's internal memory 811. However, should the data be other than authenticated, then the microprocessor 807 triggers the electronic blowing of an internal fuse array 810 within the peripheral memory storage device. Said fuses 810 isolate a portion of the module memory having security data stored therein from the external world removing the peripheral memory storage device 806 automatic login functionality. Optionally, instead of blowing fuses, software settings are altered requiring a security administrator to reset same.

[0060] Alternatively protection mechanisms such as selective overwriting of user authentication data, erasure of internal module firmware, over-writing or resetting to non-operational defaults are performed for securing the security data within the module. Additionally it is evident that said protection mechanisms are triggerable based on other pre-determined events such as number of uses or date.

[0061] Numerous other embodiments may be envisaged without departing from the spirit or scope of the invention.