EP1794923A1 - Authentifikationssystem und -verfahren auf der basis von zufälliger teilweise digitalisierter wegerkennung - Google Patents
Authentifikationssystem und -verfahren auf der basis von zufälliger teilweise digitalisierter wegerkennungInfo
- Publication number
- EP1794923A1 EP1794923A1 EP04783539A EP04783539A EP1794923A1 EP 1794923 A1 EP1794923 A1 EP 1794923A1 EP 04783539 A EP04783539 A EP 04783539A EP 04783539 A EP04783539 A EP 04783539A EP 1794923 A1 EP1794923 A1 EP 1794923A1
- Authority
- EP
- European Patent Office
- Prior art keywords
- data
- coordinates
- client
- frame
- indicators
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Withdrawn
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
- H04L63/083—Network architectures or network communication protocols for network security for authentication of entities using passwords
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/30—Authentication, i.e. establishing the identity or authorisation of security principals
- G06F21/31—User authentication
- G06F21/36—User authentication by graphic or iconic representation
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/70—Protecting specific internal or peripheral components, in which the protection of a component leads to protection of the entire computer
- G06F21/82—Protecting input, output or interconnection devices
- G06F21/83—Protecting input, output or interconnection devices input devices, e.g. keyboards, mice or controllers thereof
Definitions
- the invention relates generally to user authentication systems, used for computer and network security access control systems; and more particularly to improved "what user knows"- based authentication factors, in client/server network architectures and other architectures.
- Standard Static Password Recognition SSPR
- the SSPR algorithm simply requires a user to enter a user name and a password for authentication. This is a "what user knows” type authentication factor.
- Other types of authentication factors are not as widely deployed, and include “what user has” (card key), and “what user is” (fingerprint).
- "What user has” and “what user is” type authentication factors require special hardware devices, such as card readers, tokens, fingerprint sensors and the like at the input terminals, and therefore are typically much more expensive and impractical than a "what user knows” type.
- "What user knows” type authentication factors are limited by the ability of a person to remember the factor involved.
- An intruder may employ a brute-force technique, known as a dictionary attack, of successively trying all the words in an exhaustive list against a password file. Each consecutive tried word gets encrypted using the same algorithm that the login program under attack is using.
- Dictionary attacks applied either to hashed passwords, intercepted on communication lines, or directly at the password entry devices, allow for quite easy password re-engineering.
- Another issue is related to password combinatorial capacities of typical passwords that are within a "comfort level" of complexity for most users. For larger organizations, a range of passwords within such comfort level may not be sufficient.
- Typical enterprise level solutions in accounting for items 1 and 2 above, require users to have at least 4-5 (or more) alphanumeric case sensitive character passwords, which should not to be simple words (but rather something, like: lpatRIOT, Lon7Don, etc.).
- This approach leads to multiple password resets by users that forget or lose their passwords, which resets have become quite costly and annoying hurdles for organizations and enterprises (or service companies) striving for higher security levels.
- Objective consideration shows that the minimum number of characters in a password is limited at a minimum by two factors: necessary combinatorial capacities and high susceptibility to combinatorial attacks. The maximum number of characters in static passwords is limited by users' "comfort level" for memorization.
- AAA Authentication- Authorization- Accounting
- biometrics There is, also, a significant public reluctance against biometric authentication methods due to religious and cultural concerns. Another strong concern, if using biometrics, is private biometrics data safety. Once stolen, the biometric data can be re-used forever to impersonate the individual that the data is taken from.
- Video- and/or audio-recording is possible from a significant distance and any time of the day, jeopardizing secret passwords or PINs entered by computer or network online users at public locations (ATM machines; customers at Point-of-Sales; Internet terminals offered at various conferences, cafes, libraries; employees sharing large offices with desktop computer terminals within everybody's visual reach, and other places).
- Every user name has a password entry in a hashed form which can be read.
- each password is an encryption key for itself to be hash encrypted.
- SSPR security technology is vulnerable to well known security breaches.
- SSPR is based on “what user knows”, as opposed to other authentication factors based on “what user has” (for instance, hardware tokens), or “what user is” (such as biometric traits, like, fingerprints, face, eye, and voice recognition). It is well known, "what user knows”-based authentication systems are the most attractive due to being cheap, user friendly, easily electronically deployable, and requiring no additional hardware, as opposed to other authentication factors. That is why numerous attempts have been made to improve SSPR technology and satisfy the requirements of the Internet mass transaction and e-commerce community.
- Several enhanced user authentication security requirements include the following:
- authentication secrets (like passwords or PINs) shared between a client and a server should not be revealed, if the data are intercepted by an intruder, while in transit on communication lines.
- Authentication system is to demonstrate strong resilience against attacks at input/output devices (see, for example, B1-B7, B9).
- Client and server have to perform mutual authentication to each other.
- Client should be able to get authenticated to by server and get access to protected resources from any computer platform on the Internet.
- Authentication system should have zero footprint downloaded software on the client computer platform.
- the present invention provides a new Random Partial Digitized Path Recognition
- RPDPR Rivest Cipheral Digital Retriety Protocol
- RPDPR authentication technology has the positive features of SSPR based security systems, but at the same time, is much stronger in terms of security.
- RPDPR technology is extremely effective against computer data processing dictionary or brute force attacks, password guessing, password file theft, shoulder surfing, eavesdropping, videotaping, Trojan Horse attack, memory sniffing attacks, keystroke monitoring, and network sniffing.
- RPDPR provides a "what user knows” authentication method with enormous combinatorial capacity, while remaining within a user's "comfort level" for memorization.
- the present invention is embodied by an interactive method for authentication of a client.
- the method is interactive in the sense that the server provides a clue to the client that has already been identified by the server, and the client enters a data suggested by the clue.
- Embodiments of the method utilize a full pattern that consists of a set of data fields, which store parameters that specify a digitized path on a reference grid for recognition. Further, embodiments of the method utilize a random partial subset of the full pattern stored in the server, for fulfilhent of the authentication factor.
- an ordered set of data fields is stored in secure memory.
- the data fields in the ordered set include respective field contents, which store coordinates of points on a digitized path on a frame of reference.
- the server provides to the client via a communication medium a clue, such as positions in the ordered set of a random subset of data fields from the ordered set, which identify a random partial pattern form the full pattern stored in the ordered set of data fields.
- a clue such as positions in the ordered set of a random subset of data fields from the ordered set, which identify a random partial pattern form the full pattern stored in the ordered set of data fields.
- random as used herein is meant to include pseudo-random.
- the server presents an input construct, as part of a graphical user interface for example which displays the clue.
- Input construct facilitates input of data corresponding to the field contents of the positions indicated by the clue.
- the input construct in one embodiment includes an instance of a representation of the frame of reference, such as a rectangular grid.
- the instance of the representation of the frame of reference includes a randomized array of indicators occupying positions having coordinates in the frame of reference, that correspond with coordinates stored in the set of data fields that specify a digitized path.
- the indicators displayed in the instance of the frame of reference displayed during an authentication session include one or more of alphanumeric characters, images and colors.
- the input construct includes input fields for inserting indicators from the randomized array of indicators.
- the client satisfies the authentication factor by inserting indicators from the instance of the frame of reference, taken from the coordinates identified by the field contents of data fields in the data set specifying the digitized path and having the positions along the digitized path specified by the clue.
- the server generates different instances of the frame of reference, in which the randomized array of indicators is changed for each random combination of data field positions on the full digitized path and for different authentication sessions.
- a particular indicator corresponds to the field contents that identify particular combination of coordinates, only during a single authentication session.
- the server verifies the indicators, with reference to the clue, the stored full pattern and the instance of the frame of reference provided for the particular authentication session. If the input data matches, successful authentication is signaled. Else, a failed authentication is signaled.
- the process involves presenting to the client an input construct for account set up.
- the input construct may comprise a graphical user interface presented using an Internet browser or a thin client software.
- a user provides field contents for an ordered set of 'data fields specifying a digitized path on a frame of reference.
- Embodiments of the invention include an initial step of detecting an attempted access to protected resources in the data network.
- the authentication procedure is initiated.
- authentication of the client is signaled, allowing access to a protected resource.
- FIG. 1 For example, in one embodiment the icon comprises a stoplight icon which displays a red light during said prompting, a yellow light while waiting for verification, and a green light after verification.
- Embodiments of the invention include a system for authentication of a client.
- the system includes a data processor including an interface to a database, an interface to a data network, and authentication system programs executable by the data processor.
- the system programs include authentication logic supporting the RPDPR authentication factor for authentication of a client based upon client credentials including an account user name.
- the invention is also embodied by authentication systems based on the client/server architecture, and other architectures.
- the process is extended to an authentication server for a large number of users.
- the process involves maintaining a secure database of user accounts, including data sets of data fields as described above.
- attempts to access a protected network resource are detected or otherwise redirected to the server.
- the server then conducts an authentication session as described above to enable a client to have access to the protected resource.
- Systems embodying the present invention include data processing resources including a processor, memory and network interfaces.
- Authentication server software being executed in the data processing resources carry out the processes for account set up and client authentication, as described above.
- RPDPR based authentication technology is as user friendly, as cost effective and as electronically deployable as Standard Static Password Technology (SSPR). At the same time, security is much higher using RPDPR based authentication, as compared to SSPR. It allows for effective protection from multiple intruding attacks at data entry devices as well as on communication lines, while data are in transit. RPDPR based authentication technology is applicable to hardware and human clients, while having scalable security allowing for trade offs involving cost, business requirements, and hardware resources.
- SSPR Standard Static Password Technology
- Fig. 1 illustrates client/server architecture for implementation of a user authentication process based on a random partial digitized path recognition RPDPR algorithm according to the present invention.
- FIG. 2 is a flowchart of a basic random partial digitized path recognition RPDPR authentication session according to the present invention.
- Figs. 3 A-3F provide a secret full digitized path selection menu and various examples of full continuous paths having ten positions for online user account set up in support of the RPDPR authentication process during the login sessions according to the present invention.
- Figs. 4A-4F provide various examples of full non-continuous paths having ten positions for online user account set up in support of the RPDPR authentication process during the login sessions according to the present invention.
- Fig. 5 illustrates a graphical user interface supporting a log-in process at the random partial path data entry state used in one example of an authentication program according to the present invention.
- Fig. 6 is a basic architecture diagram for an embodiment of a client/server system according to the present invention, including support for the RPDPR authentication processes.
- Fig. 1 illustrates a basic communication set up for a representative RPDPR authentication process, according to the present invention.
- a client subsystem 1010 communicates by communication media, such as a local area network or wide area network communications subsystem 1020, with a server subsystem 1030.
- a protected network destination 1130 controls access to resources such as secure web sites identified by URLs, links to secure networks, and the like.
- a pre-authentication session 3040 is executed by the client subsystem 1010 and server subsystem 1030.
- a user account is set up in the server subsystem 1030, the user name and a secret digitized path represented by an ordered data set of data fields is selected by the user and stored in the server subsystem 1030.
- the ordered data set characterized the user's full pattern, in which the data fields have a position in the data set and have respective field contents.
- the field contents include combinations of field coordinates on a frame of reference of points. The coordinates characterize data field locations along a directed digitized path on the frame of reference.
- the position in the data set corresponds to the position (e.g.
- the position in the data set therefore indicates such coordinates to the client, and the coordinates can be used to select an indicator to be supplied as fulfillment of a part of the authentication factor that corresponds to the position indicated by the clue.
- the user account information, user name and ordered set of data fields are stored in a secure server database, along with such other information utilized during an authentication session.
- information supporting additional authentication factors is stored in the database.
- the client subsystem To gain access to the protected network destination 1130, the client subsystem
- an authentication session is initiated when the user tries to reach a protected network destination (block 1060).
- the protected network destination redirects the user's attempted access to the authentication server, or the attempted access is otherwise detected at the authentication server 1030.
- a communication interface is returned to the user's browser including a graphical user interface including links to the authentication server 1030 (block 1070).
- the communication interface may be returned through redirection for example, by the authentication server or another network resource.
- the server prompts the user to enter a user name into a field in the graphical user interface (block 1080).
- the user enters the user name, which is returned to the authentication server (block 1090).
- the authentication server identifies a random partial subset of data fields from the ordered data set, the field contents and field positions together indicate coordinates of a set of points that together define a full digitized path on the frame of reference. For instance, in one embodiment there are ten data fields comprising a full digitized path with the starting path field having position 0, next consecutive data field having position 1, and going alike up to the last data field at the full digitized path end having position 9.
- random partial subsets identified by the authentication server (a clue) and presented to the user through the graphical user interface will look like a random set of random digit combinations, for example, 24, 019, 7, 68.
- the user is prompted to fulfill input field values that correspond to the coordinates in member data fields in the random partial subset of data fields using the graphical user interface (block 4100).
- the input field values are selected from an array of indicators located on an instance of the frame of reference, where the indicators in the array have locations on the instance of the frame of reference corresponding to candidate coordinates in the frame of reference.
- the user inputs the indicators, or other data corresponding to the coordinates for the random partial subset of the digitized path, for the input field contents, and the input data are returned to the server (block 4110). If the input data matches the field contents for the random subset, then successful authentication is signaled to the user via for example the graphical user interface, signaled to the protected network destination and/or signaled to other resources, such as authorization and accounting systems, that need to know that the authentication session has succeeded, and network connection to the requested protected network destination is allowed (block 1120).
- resources such as authorization and accounting systems
- Figs. 3 A-3F and 4A-4F illustrate how a digitized path is specified with respect to a frame of reference for use as a RPDPR authentication factor.
- the frame of reference consists of a reference grid as shown in Fig. 3 A.
- the reference grid 8010 in this embodiment consists of an array of locations (e.g. 8011) that can be characterized by coordinates along horizontal and vertical axes 8012, 8013 respectively, as in a Cartesian coordinates system. Other frames of reference may be organized according to other coordinate systems, such as polar coordinate systems.
- the location 8011 can be characterized by coordinates (6, 3).
- 3 A represents an instance of a frame of reference for display on a user interface during an account setup procedure for example, used by a client to specify a full digitized path.
- the instance includes icon 8014 at the intersection of the reference axes, used as a button for opening and closing the instance.
- the client may draw (or choose, or select) a path on the reference grid with a mouse, a keyboard, or other input devices, or the path may be provided by a server, as suits a particular instance of the set up algorithm.
- FIGs. 3B-3F illustrate representative full digitized paths which can be set up using the frame of reference 8010.
- Fig. 3B illustrates a path 8021 on an instance 8020 of the reference grid.
- the path includes a set of points beginning with a point at coordinates (9, 7).
- the path proceeds in a straight line in order with points at the coordinates (8, 7), (7, 7), (6, 7), ... , (0, 7).
- a data set corresponding with this digitized path comprises a set a data fields having positions 0 through 9 in the data set (where the positions can be represented by a field number using a data set that comprises a linear array of data fields).
- the data fields at the 10 positions respectively store combinations of coordinates (9, 7) through (0, 7) in order.
- Fig. 3C illustrates a path represented by arrows 8031, 8032, 8033 on an instance
- the path of Fig. 3C includes the coordinates in order: (0,8), (1,9), (2,9), (2,8), (2,7), (3,6), (4,5), (5,4), (6,3), and (7,2). These coordinates are stored in the data fields having positions 0 through 9 respectively in the data set used as the authentication factor based on the path in Fig. 3C.
- Fig. 3D illustrates a path represented by arrows 8041, 8042 on an instance 8040 of the frame of reference.
- the path of Fig. 3D includes the coordinates in order: (0,5), (1,6), (2,7), (3,8), (4,9), (5,9), (6,8), (7,7), (8,6), and (9,5).
- These coordinates are stored in the data fields having positions 0 through 9 respectively in the data set used as the authentication factor based on the path in Fig. 3D.
- Fig. 3E illustrates a path represented by arrows 8051, 8052 on an instance 8050 of the frame of reference.
- the path of Fig. 3E includes the coordinates in order: (9,9), (9,8), (9,7), (9,6), (9,5), (8,5), (7,5), (6,5), (5,5), and (4,5). These coordinates are stored in the data fields having positions 0 through 9 respectively in the data set used as the authentication factor based on the path in Fig. 3E.
- Fig. 3F illustrates a path represented by arrows 8061, 8062, 8063, 8064, 8065 on an instance 8060 of the frame of reference.
- the path of Fig. 3F includes the coordinates in order: (2,9), (2,8), (3,8), (3,9), (4,9), (4,8), (5,8), (5,9), (6,9), and (6,8). These coordinates are stored in the data fields having positions 0 through 9 respectively in the data set used as the authentication factor based on the path in Fig. 3F.
- digitized paths shown in Figs. 3B through 3F are considered herein continuous digitized paths, because all of the coordinates on the path are adjacent to other coordinates on the path in order. Continuous paths may be easier to remember for some clients.
- Fig. 4A illustrates a non-continuous path represented by arrows 9011, 9012, 9013 on an instance 9010 of the frame of reference.
- the path of Fig. 4A includes the coordinates in order: (0,0), (1,1), (2,2), (7,2), (8,1), (9,0), (9,6), (9,7), (9,8), and (9,9).
- a discontinuity in the path occurs between the coordinates (2, 2) and (J, 2).
- a discontinuity occurs between the coordinates (9, 0) and (9, 6).
- These coordinates are stored in the data fields having positions 0 through 9 respectively in the data set used as the authentication factor based on the path in Fig. 4A.
- Fig. 4B illustrates a non-continuous path represented by arrows 9021, 9022 on an instance 9020 of the frame of reference.
- the path of Fig. 4B includes the coordinates in order: (5,
- Fig. 4C illustrates a non-continuous path represented by arrows 9031, 9032, 9033 and cross 9034 on an instance 9030 of the frame of reference.
- the path of Fig. 4C includes the coordinates in order: (0, 0), (1, 0), (2, 0), (9, 0), (9, 1), (9, 2), (9, 9), (8, 9), (7, 9), and (0, 9).
- These coordinates are stored in the data fields having positions 0 through 9 respectively in the data set used as the authentication factor based on the path in Fig. 4C.
- Fig. 4D illustrates a non-continuous path represented by crosses 9041, 9042, 9043,
- Fig. 4D includes the coordinates in order: (0, 0), (2, 2), (4, 4), (6, 6), (8, 8), (0, 9), (2, 7), (4, 5), (6, 3), and (8, 1). These coordinates are stored in the data fields having positions 0 through 9 respectively in the data set used as the authentication factor based on the path in Fig. 4D.
- Fig. 4E illustrates a non-continuous path represented by crosses 9051, 9052, 9053,
- the path of Fig. 4E includes the coordinates in order: (0, 0), (9, 0), (9, 9), (0, 9), (2, 7), (3, 6), (4, 5), (5, 4), (6, 3), and (7, 2). These coordinates are stored in the data fields having positions 0 through 9 respectively in the data set used as the authentication factor based on the path in Fig. 4E.
- Fig. 4F illustrates a non-continuous path represented by arrows 9061, 9062, 9063 and cross 9064 on an instance 9060 of the frame of reference.
- the path of Fig. 4F includes the coordinates in order: (7, 9), (8, 9), (9, 9), (9, 8), (9, 7), (9, 6), (8, 7), (7, 8), (6, 9), and (8, 8). These coordinates are stored in the data fields having positions 0 through 9 respectively in the data set used as the authentication factor based on the path in Fig. 4F.
- Fig. 5 illustrates a graphical user interface screen 2090, which is presented at the beginning of an authentication session based on RPDPR.
- the interface 2090 prompts the client for fulfillment of the RPDPR authentication factor. Otherwise, if the user name is not accepted by the authentication server, a "random partial digitized path" prompt and its respective fields (8040, 8050), field indicators 8030, and the second stop light icon 8020 do not appear in screen 2090, while the first stop light icon 2110 will turn red signaling access denied (or user name is incorrect).
- two stoplight icons 2110, 8020 are presented. The first stoplight icon 2110 turns green after the user static user name has been recognized.
- the second stoplight icon 8020 appears during data entry for the random partial subset. It appears red before data has been entered into data fields, or before the login button is indicated. The stoplight icon 8020 appears yellow during client/server communications and before acceptance of the input data representing field contents. The stoplight icon 8020 appears green to signal successful authentication.
- Data entry fields are presented for a pattern comprising a corresponding number of fields which will constitute the random partial subset of the data set of data fields stored for the user.
- a plurality of the random partial subsets are presented to the user by sets of field position numbers (e.g. 8030), and includes set of field position numbers 27 (position 2 and position 7), set of field position numbers 049, field position number 6, out of a data set of for example 10 data fields corresponding to a digitized path comprising 10 points.
- associated with each of the data entry fields is a button 8050 with a corresponding window for entry of indicators selected by the user.
- a pop-down menu 8010 is displayed.
- the pop-down menu 8010 comprises an instance of a reference grid, such as shown in Figs. 9A- 9F and 10A- 1OF, where the points on the grid are populated by a randomized array of indicators.
- an indicator at the point having coordinates (4, 5) is the digit 5.
- the server produces a different instance of the array of indicators for each instance of the reference grid.
- the different instances of the array of indicators can be generated randomly, or pseudo-randomly, in preferred embodiments. Alternatively, a set of previously generated arrays of indicators can.be utilized in a random order.
- the look and feel of the reference grid is maintained from session to session, while the array of indicators is changed.
- the reference grid may take different forms, so long as the coordinates of the points on the digitized path may be used to identify positions on the form of the reference grid.
- Other techniques can be utilized for making the presentation of the reference grid and the arrays of indicators variable to strengthen the authentication factor.
- the graphical user interface 2090 presents clues represented by the sets the field position numbers (e.g. 8030).
- Corresponding input fields 8040 are presented to the user.
- the user fulfills the authentication factor by including the indicators from the points on the reference grid having the coordinates that correspond to the field position numbers in the sets the field position numbers that identify the random partial subset of the full path, associated as clues with the input fields.
- the indicators chosen will be the indicator at the coordinates stored in field position number 2 and at the coordinates stored in field position number 7 of the full data set.
- Field position number 2 in the example of Fig. 3B stores the coordinates (7, 7).
- the indicator at the coordinates (7, 7) is the digit 6.
- the field position number 7 in the example of Fig. 3B stores the coordinates (2, 7).
- the indicator at the coordinates (2, 7) is the digit 3. Therefore, the input field 8040 is fulfilled by inputting the indicators 6 and 3.
- a similar procedure is followed to fulfill the fields corresponding to the clues that consist of the sets the field position numbers 049 and 6 for the interface 8070 shown in Fig. 5.
- Fig. 6 illustrates a client/server system including authentication resources according to the RPDPR authentication factor of the present invention.
- the client subsystem 1010 includes data entry devices 4010 (keyboard, mouse, voice input, etc.), a display device 4020 (CRT, LCD panel, etc.), and a physical platform 4030 (personal computer, hand held computer, internet appliance, etc.) including a processing unit, memory, and other data processing resources.
- Software running in the client includes a browser 4050 or a "thin" software client 4060 such as may be provided on personal digital assistants, cell phones, and other simple internet appliances which may not support full browser functionality.
- the browser 4050 includes Java Virtual Machine or a .NET environment which supports the client/server dialog.
- the "thin" software client 4060 may support the client/server dialog.
- an interface 4040 to the network communication media 4130 is provided.
- the communication media 4130 may be a private or pubic, local area network or a wide area network using wired, wireless or optical media in representative systems.
- the server subsystem 1030 includes network server resources 4070, an account management utility 4080 for the user accounts subject of the authentication process, and a platform 4090 including a processing unit, memory, disk space and other data processing resources.
- a core program 4100 supporting the authentication process is included in the server subsystem 1030.
- the core program may be implemented using Java or .NET object-oriented technology for examples.
- a server database and database connector 4120 is included.
- an interface 4110 to communication media for server LANAVAN communication lines 4130 is provided.
- the server and server data are implemented with security features to protect user account information files from intruders.
- the present system is used for user authentication in a client/server network architecture, for authentication of hardware devices (where the clients comprise peer routers for example) and in other environments supporting interactive authentication sessions.
- Interactive authentication based on the Random Partial Digitized Path Recognition (RPDPR) algorithm provides significant security protection against multiple known intruder attacks.
- RPDPR Random Partial Digitized Path Recognition
- the interactive, multi-field pattern process of the present invention establishes a new paradigm, replacing or enhancing standard static password technology. By capitalizing on modern high clock rate client/server CPU processing power and high network throughput, the RPDPR authentication process is easy to use.
- user authentication begins with a client's initial request to a protected network destination.
- the server having known the client's user name and the shared secret full pattern (full digitized path of data fields with their positions, and respectively coordinates characterizing these positions, ordered according to their positions along the path), prompts the client through the client's GUI to fulfill a subset of the user's full pattern randomly selected by the server.
- the full pattern is a pre-set shared secret between the client and the server established during the client account set-up.
- the full pattern resides in the database on the server side.
- Each field in the random subset requested from the client is associated with a displayed sequence number corresponding to a position in the full pattern.
- Each field in the GUI allows entering any combination of objects (at least one object per field is to be entered).
- the objects entered in the field niay be selected from a randomized set of indicators on a representation of the reference grid, that are located at the coordinates stored in the subset of the data set storing the full digitized path.
- the server Upon receiving the client's response, the server compares internally computed expected combination with the client's input data, and makes a no/go authentication decision, provided the response is false/true.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Hardware Design (AREA)
- Computer Security & Cryptography (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Physics & Mathematics (AREA)
- Software Systems (AREA)
- Computing Systems (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer And Data Communications (AREA)
- User Interface Of Digital Computer (AREA)
- Information Transfer Between Computers (AREA)
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/US2004/029321 WO2006031212A1 (en) | 2004-09-09 | 2004-09-09 | Authentication system and method based upon random partial digitized path recognition |
Publications (2)
Publication Number | Publication Date |
---|---|
EP1794923A1 true EP1794923A1 (de) | 2007-06-13 |
EP1794923A4 EP1794923A4 (de) | 2010-12-29 |
Family
ID=36060325
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
EP04783539A Withdrawn EP1794923A4 (de) | 2004-09-09 | 2004-09-09 | Authentifikationssystem und -verfahren auf der basis von zufälliger teilweise digitalisierter wegerkennung |
Country Status (7)
Country | Link |
---|---|
EP (1) | EP1794923A4 (de) |
JP (1) | JP2008512765A (de) |
CN (1) | CN101057444B (de) |
AU (1) | AU2004323374B2 (de) |
CA (1) | CA2579826C (de) |
HK (1) | HK1113525A1 (de) |
WO (1) | WO2006031212A1 (de) |
Families Citing this family (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7849321B2 (en) | 2006-08-23 | 2010-12-07 | Authernative, Inc. | Authentication method of random partial digitized path recognition with a challenge built into the path |
JP5413225B2 (ja) * | 2010-02-05 | 2014-02-12 | 富士通株式会社 | プログラム、車載装置および情報処理装置 |
TWI522842B (zh) * | 2012-06-15 | 2016-02-21 | Pattern cryptographic track setting system and its method |
Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5608387A (en) * | 1991-11-30 | 1997-03-04 | Davies; John H. E. | Personal identification devices and access control systems |
EP0901060A2 (de) * | 1997-09-05 | 1999-03-10 | Fujitsu Limited | Vorrichtung und Verfahren zur sicheren Datenkontrolle |
Family Cites Families (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6209104B1 (en) * | 1996-12-10 | 2001-03-27 | Reza Jalili | Secure data entry and visual authentication system and method |
-
2004
- 2004-09-09 JP JP2007531142A patent/JP2008512765A/ja active Pending
- 2004-09-09 EP EP04783539A patent/EP1794923A4/de not_active Withdrawn
- 2004-09-09 CN CN200480044372.9A patent/CN101057444B/zh not_active Expired - Fee Related
- 2004-09-09 AU AU2004323374A patent/AU2004323374B2/en not_active Ceased
- 2004-09-09 WO PCT/US2004/029321 patent/WO2006031212A1/en active Application Filing
- 2004-09-09 CA CA2579826A patent/CA2579826C/en active Active
-
2008
- 2008-04-02 HK HK08103648.2A patent/HK1113525A1/xx not_active IP Right Cessation
Patent Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5608387A (en) * | 1991-11-30 | 1997-03-04 | Davies; John H. E. | Personal identification devices and access control systems |
EP0901060A2 (de) * | 1997-09-05 | 1999-03-10 | Fujitsu Limited | Vorrichtung und Verfahren zur sicheren Datenkontrolle |
Non-Patent Citations (1)
Title |
---|
See also references of WO2006031212A1 * |
Also Published As
Publication number | Publication date |
---|---|
WO2006031212A1 (en) | 2006-03-23 |
CA2579826C (en) | 2012-12-18 |
JP2008512765A (ja) | 2008-04-24 |
AU2004323374B2 (en) | 2008-08-28 |
CN101057444A (zh) | 2007-10-17 |
AU2004323374A1 (en) | 2006-03-23 |
EP1794923A4 (de) | 2010-12-29 |
CA2579826A1 (en) | 2006-03-23 |
HK1113525A1 (en) | 2008-10-03 |
CN101057444B (zh) | 2012-02-29 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US7073067B2 (en) | Authentication system and method based upon random partial digitized path recognition | |
US7644433B2 (en) | Authentication system and method based upon random partial pattern recognition | |
US7577987B2 (en) | Operation modes for user authentication system based on random partial pattern recognition | |
US20040225880A1 (en) | Strong authentication systems built on combinations of "what user knows" authentication factors | |
US8041954B2 (en) | Method and system for providing a secure login solution using one-time passwords | |
CA2649015C (en) | Graphical image authentication and security system | |
Pinkas et al. | Securing passwords against dictionary attacks | |
US8850519B2 (en) | Methods and systems for graphical image authentication | |
EP1829281B1 (de) | Authentifizierungseinrichtung und/oder verfahren | |
US20110197070A1 (en) | System and method for in- and out-of-band multi-factor server-to-user authentication | |
US8327420B2 (en) | Authentication system and method | |
Boonkrong et al. | Multi-factor authentication | |
CA2611549C (en) | Method and system for providing a secure login solution using one-time passwords | |
WO2000041103A1 (en) | Method and system for discriminating a human action from a computerized action | |
CA2579826C (en) | Authentication system and method based upon random partial digitized path recognition | |
Majdalawieh et al. | Assessing the Attacks Against the Online Authentication Methods Using a Comparison Matrix: A Case of Online Banking | |
Selvan et al. | An Enhanced Countermeasure Technique for Deceptive Phishing Attack | |
session SAAAAAA | SkS U33" flgis;,--CL) tSee | |
Jayapandiyan | Authentication and Access using the Multi-Layer Information Security (MLIS) Technology for E-Commerce Applications | |
IL127501A (en) | Method and system for discriminating a human action from a computerized action |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
PUAI | Public reference made under article 153(3) epc to a published international application that has entered the european phase |
Free format text: ORIGINAL CODE: 0009012 |
|
17P | Request for examination filed |
Effective date: 20070402 |
|
AK | Designated contracting states |
Kind code of ref document: A1 Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IT LI LU MC NL PL PT RO SE SI SK TR |
|
DAX | Request for extension of the european patent (deleted) | ||
A4 | Supplementary search report drawn up and despatched |
Effective date: 20101201 |
|
RIC1 | Information provided on ipc code assigned before grant |
Ipc: H04L 9/00 20060101ALI20101125BHEP Ipc: G06F 21/00 20060101AFI20101125BHEP |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: THE APPLICATION IS DEEMED TO BE WITHDRAWN |
|
18D | Application deemed to be withdrawn |
Effective date: 20150401 |