WO2016094590A1

WO2016094590A1 - System and method for replacing common identifying data

Info

Publication number: WO2016094590A1
Application number: PCT/US2015/064845
Authority: WO
Inventors: Anthony R. Perez; Justin SOENKE
Original assignee: Perez Anthony R; Soenke Justin
Priority date: 2014-12-12
Filing date: 2015-12-09
Publication date: 2016-06-16
Also published as: EP3231131B1; CA2970338A1; US9710641B2; US10204217B2; AU2015360509B2; CA2970338C; EP3961978A1; ES2904538T3; EP3231131A1; AU2015360509A1; MX371003B; JP6538872B2; DK3231131T3; EP3231131A4; MX2017007610A; US20160171209A1; JP2018502410A; US20170286666A1; CA3056461A1

Abstract

A system and method for generating a unique identifier for a user. A processor hosted by the system transmits a prompt for user selection of a digital image and receives the selected digital image from the user. The received digital image is stored in a data storage device. The processor identifies a first code associated with the user. The processor embeds the first code into the digital image and generates a first modified digital image in response. The first modified digital image is also stored in the data storage device. The processor transmits the first modified digital image to the user over a data communications network. The modified digital image is then used as the unique identifier for the user.

Description

SYSTEM AND METHOD FOR REPLACING COMMON IDENTIFYING

DATA

BACKGROUND

[0001] One of the benefits of the World Wide Web is that it generally allows people to connect globally without substantial barriers. However, this has also led to lack of proper security for users communicating via the web. The lack of proper security exposes users to cyber- criminals, hackers, and others, who want to steal information from people using the web.

[0002] One attempt to provide protection against unauthorized access to data is to

authenticate users prior to giving them access to such data. For example, users may be required to provide a password that only the user should know before allowing the access. However, users often store passwords or other authentication information in devices such as the user's computer, cell phone, or the like. In this case, cyber-criminals may hack the user's device and obtain the user's authentication information to impersonate the user and unlawfully access data.

[0003] Accordingly, what is desired is a system and method for authenticating users while limiting exposure to data used for authentication purposes.

SUMMARY

[0004] According to one embodiment, the present invention is directed to a system and method for generating a unique identifier for a user. The system includes a processor and memory where the memory stores instructions that, when executed by the processor, cause the processor to take the following actions. The processor transmits a prompt for user selection of a digital image and receives the selected digital image from the user. The received digital image is stored in a data storage device. The processor identifies a first code associated with the user. The processor embeds the first code into the digital image and generates a first modified digital image in response. The first modified digital image is also stored in the data storage device. The processor transmits the first modified digital image to the user over a data communications network.

[0005] According to one embodiment, the digital image is stored in an end user device accessible to the user,

[0006] According to one embodiment, the first code is personal information of the user. The personal information may be at least one of address, telephone number, birthdate, name, driver license number, social security number, credit card number, user identifier, or password.

[0007] According to one embodiment, the first code is a randomly generated code.

[0008] According to one embodiment, the processor further receives an alphanumeric string provided by the user, and encrypts the first code based on the alphanumeric string. According to this embodiment, the first code embedded into the digital image is the encrypted code.

[0009] According to one embodiment, the embedding includes identifying bits of the digital image that do not contribute in creating a visual depiction of the digital image.

[0010] According to one embodiment, the processor further receives a request including the first modified digital image, retrieves the embedded first code from the digital image, compares the retrieved first code against a stored version of the first code, and takes a success action associated with the first modified digital image in response to a match of the retrieved first code against the stored version of the first code.

[0011] According to one embodiment, the processor further receives a request including the first modified digital image, transmits a security code to a mobile telephone number associated with a user, and verifies the transmitted security code against a security code received from the mobile telephone number.

[0012] According to one embodiment, the processor identifies a second code associated with the user. The processor further embeds the second code into the digital image and generates a second modified digital image in response. The second modified digital image is stored in the data storage device. The processor transmits the second modified digital image to the user over a data communications network. According to this embodiment, a success action associated with the second modified digital image is different from the success action associated with the first modified digital image.

[0013] According to one embodiment, the success action includes transmitting an alert of a duress situation involving the user.

[0014] According to one embodiment, the processor receives an answer to a math problem provided by the user, and determines whether the answer is correct. In response to determining that the answer is incorrect, the processor takes a failure action.

[0015] According to one embodiment, the success action is retrieving account information of the user for an e-commerce transaction.

BRIEF DESCRIPTION OF THE DRAWINGS

[0016] FIG. 1 is a schematic block diagram of a system for authenticating a user via a code encoded in a digital image according to one embodiment of the invention;

[0017] FIG. 2 is a flow diagram of a process for creating a unique ID according to one embodiment of the invention;

[0018] FIG. 3 is a more detailed flow diagram of an act for generating a unique ID according to one embodiment of the invention;

[0019] FIG. 4A is a flow diagram of a process for authenticating a user based on a submitted unique ID according to one embodiment of the invention; [0020] FIG. 4B is a flow diagram of a process for authenticating a user based on a submitted unique ID according to another embodiment of the invention;

[0021] FIG. 5A illustrates code for generating a typical HTML login form according to existing mechanisms;

[0022] FIG. 5B illustrates code for generating a login form according to embodiments of the present invention; and

[0023] FIG. 6 is a schematic layout diagram of a unique ID 300 according to one

embodiment of the invention.

[0024] These and other features, aspects and advantages of the present invention will be more fully understood when considered with respect to the following detailed description, appended claims, and accompanying drawings. Of course, the actual scope of the invention is defined by the appended claims.

DETAILED DESCRIPTION

[0025] Embodiments of the present invention are directed to a system and method that generates and uses a unique ID for user authentication, identification, and/or the like

(collectively referred to as authentication). The unique ID, as is used herein, is a digital image that contains an embedded code. The embedded code may be personal or sensitive data of a user, such as, for example, the user's name, birthdate, driver's license number, social security number, user ID, password, secret questions/answers, credit card numbers, phone numbers, and/or the like. In addition or in lieu of personal data, the embedded code may be random text and/or numbers automatically generated by the system and assigned to the user. Although embodiments of the present invention envision that the code embedded in the image is encrypted, non-encrypted codes may also be embedded. According to one embodiment, the code is stored in unused or insignificant bits of the digital image. The digital image may be generated using any one of many well-known image file formats conventional in the art, including but not limited to jpeg, tiff, gif, bmp, png, Netpbm, WebP, and the like.

[0026] According to one embodiment, a user provides the encoded image to a computer device to trigger a particular action. Such action may be, for example, authentication of the user for access or login to a network, computer, mobile device, electronic tablet, webpage, and/or the like (hereinafter "target site"). Once allowed into the target site, the user may access data, applications, and the like, stored at the target site. The level of access may depend on preset configuration settings on the computer device and/or target site. Another action triggered upon providing the code may be, for example, completion of a transaction. The transaction may be, for example, a purchase transaction with a particular merchant.

[0027] According to one embodiment, the computer device evaluating a received unique ID for purposes of user authentication is physically separate from a target device storing data/applications to which the user wants access. In this manner, the target device need not store codes or other authentication information for the user. Instead, such sensitive data is stored and managed by the separate device, and provided to the target device as needed after the user has been authenticated. Thus, even if a hacker penetrates the target site, codes or other authentication information for the user are not compromised.

[0028] FIG. 1 is a schematic block diagram of a system for authenticating a user via a code encoded in a digital image according to one embodiment of the invention. The system includes an authentication server 10 coupled to a customer server 12 over a data

communications network 14. According to one embodiment, the data communications network is a public wide area network such as the Internet.

[0029] The system also includes an end user device 16 configured to access the customer server 12 over the data communications network 14. The end user device 16 may be any computing device conventional in the art such as, for example, a desktop, laptop, smart phone, electronic tablet, and the like. The end user device includes one or more processors, memory, input devices (e.g. mouse and keyboard), output devices (e.g. one or more display screens), and a wired or wireless network interfaces. According to one embodiment, the end user device 16 also includes web browsing software for communicating with the customer server 12 over the web.

[0030] According to one embodiment, the customer server 12 is a web server provided by a business in a relationship with another business hosting the authentication server 10. The customer server 12 is configured with web server software 18 that communicates with the application program interface (API) module 20. The web server software 18 includes instructions for receiving HTTP requests from the end user device 16 and delivering web pages in response to the requests. A particular web page delivered to an end user device 16 may be a login form for giving the user access to resources provided by the customer server 12. The login form may include one or more fields where each field prompts the user for different user data. For example, one field may prompt the user for his login ID, another field may prompt the user for his social security number, and yet another field may prompt the user for his credit card number. The user invokes his end user device 16 to submit his unique ID having the corresponding code in response to each prompt. According to one

embodiment, a different unique ID may be provided in response to each prompt.

[0031] The authentication server 10 includes a central processing unit (CPU) that executes software instructions and interacts with other system components to perform the methods of the present invention. The server 10 also includes a mass storage device 26 that provides long-term storage of data and software programs to perform the methods of the present invention. The mass storage device 26 may be implemented as a hard disk drive or other suitable mass storage device. The stored data may be, for example, image files to be used for authenticating one or more users, code embedded in each of the image files, and user data stored in association with a corresponding code. According to one embodiment, codes may be encrypted via an encryption algorithm prior to being stored in the storage device 26.

[0032] The server 10 further includes an addressable memory for storing software instructions to be executed by the CPU. The memory is implemented using a standard memory device, such as random access memory (RAM). In one embodiment, the memory stores a number of software objects or modules, including an API module 20, a unique ID generating module 22 and a unique ID processing module 24. Although these modules are assumed to be separate functional units, a person of skill in the art will recognize that the functionality of the modules may be combined or integrated into a single module, or further subdivided into further sub-modules without departing from the spirit of the invention.

[0033] According to one embodiment, the API module 20 includes instructions for forwarding the received unique ID(s) to the authentication server 10. In this regard, the API module 20 is an interface for communicating between the customer server 12 and the authentication server 10.

[0034] According to one embodiment, the ID generating module 22 includes instructions for receiving a digital image from the end user device 16, embedding code into the image, and outputting the image with the embedded code. According to one embodiment, instead of receiving the digital image from the end user device 16, the ID generating module may simply retrieve one of various available images from the mass storage device 26, and use that image for embedding the code. According to one embodiment, the code is encrypted using an encryption algorithm prior to being embedded into the image. The image containing the embedded code is then provided to the user for use as his unique identifier (unique ID).

[0035] The unique ID processing module 24 includes instructions for receiving an image file, having an embedded code, from a user desiring access to resources provided by the customer server 12. The unique ID processing module 24 is configured to extract the code from the image file, compare the extracted code against corresponding code stored in the storage device 26, and execute an action in response to the match. The action may be, for example, serving a particular web page to the end user device 16, effectuating a transaction, invoking an application, initiating communication with another device, retrieving and forwarding to the customer server 12 data associated with the user, and/or authorizing access to other resources provided by the customer server 12.

[0036] FIG. 2 is a flow diagram of a process for creating a unique ID according to one embodiment of the invention. The process may be initiated by an administrator of a business associated with, for example, the customer server 12. The business may create accounts for groups, employees, contractors and their customers (hereinafter "end users") depending on the services and resources they are sharing. In order for such customers to access the shared services and resources, unique IDs are created for each end user. [0037] The process starts, and in act 80, the end user receives an invitation from the customer server 12 to create an account. The invitation may be, for example, an email or text message including a URL link. Upon actuating the URL link, the end user device 16 may be directed to a front end process running on the authentication server 10. The front end process may interact with the end user to prompt the end user, in act 82, for one or more images that the user wants to use as his unique ID's. The user may select, for example, one or more photographs stored on the end user device 16.

[0038] In act 84, the front end process may also prompt the end user for the user's personal or sensitive data, such as, for example, the end user's name, birthdate, driver's license number, social security number, user ID, password, secret questions/answers, credit card number, phone number, or the like, that is to be embedded into the image. Optionally in act 84, the front end process also prompts the end user to provide one or more alphanumeric strings. The strings provided by the end user may be, for example, random strings or phrases selected by the end user. According to one embodiment, the random strings or phrases provided by the end user allow for increased entropy (randomness or unpredictability) for the code within the unique ID.

[0039] In act 86, the front end process may also prompt the end user to optionally enter his cell phone number for a 2-step authentication process. During such 2-step authentication process, the user is prompted via a message on his cell phone (or other electronic device) to enter a second authentication factor such as, for example, a security code sent by SMS/Text or a verification code generated by a code generating application running on the user's cell phone or another electronic device.

[0040] In act 88, the front end process receives all data provided by the user and forwards the data to the unique ID generating module 22. According to one embodiment, the end user device 16 transmits the data securely (e.g. over a secure data communications link).

[0041] In act 90, the front end process saves the original image(s) received from the user in the mass storage device 26, in association with, for example, a portion of the received user data.

[0042] In act 92, the unique ID generating module 22 generates one or more unique IDs based on the received images and user data. According to one embodiment, the unique ID generating module 22 generates three unique IDs. The first unique ID is generated as a single-use ID. Such a unique ID may be selected to be used when the end-user device is accessing the customer server 12 from a public setting where he may be concerned with lack of privacy or the possibility that the unique ID may be compromised by the environment. According to one embodiment, the single-use unique ID is configured to expire after the first use.

[0043] The second unique ID is generated as a duress unique ID to be used during a duress situation. Such a unique ID may be selected to be used when the end-user is compromised or at risk of fraud or physical harm and needs to access the customer server 12 to maintain his or her safety. According to one embodiment, the duress unique ID is configured to trigger certain defensive actions such as, for example, sending a pre-written alert message by SMS/Text, email or wearable technology (ie, Apple Watch, Google Glass, or the like) to a pre-selected recipient (such as an IT manager or security officer and/or family member), as well as optionally triggering a defense mechanism by the authentication server 10 that may, among other things, notify administrators, limit data visibility, erase data or disable the account.

[0044] The third unique ID is generated as a regular use unique ID. This unique ID is intended to be used during situations other than single-use and duress.

[0045] In act 94, the generated unique IDs are transmitted to the user via electronic delivery, such as, for example, email, or via a physical a medium, such as, for example, a disk, flash drive, or the like.

[0046] FIG. 3 is a more detailed flow diagram of act 90 for generating a unique ID according to one embodiment of the invention. In act 100, the ID generating module 22 identifies a received image to be used for the unique ID.

[0047] In act 102, the unique ID generating module 22 identifies any random strings provided by the end user.

[0048] In act 104, the unique ID generating module 22 identifies data to be embedded for the end user. Such data may be, for example, part of the user data provided by the user in act 84 (FIG. 2). In other embodiments, the data is one that is automatically generated by the system (e.g. randomly generated text or numbers). Different data is embedded depending on whether the type of unique ID that is being generated is a single-use ID, regular-use ID, or duress ID. The image that is used, however, may be the same. In other embodiments, different images may be used depending on the type of unique ID that is generated.

[0049] In act 106, the unique ID generating module 22 generates a code for being embedded in the image as the user's unique identification code. According to one embodiment, the unique ID generating module 22 uses the random strings identified in act 102, as a seed value for encrypting the data and generating the code. According to one embodiment, certain properties of the image in which the code is to be embedded are also used in the encryption algorithm to strengthen the encryption. Such properties may include, for example, size of the image, time in which the image was generated, and the like. The encrypted code is stored in the mass storage device 26 in association with the original image and user data.

[0050] In step 108, the unique ID generating module 22 embeds the code into the identified image. In this regard, the unique ID generating module 22 identifies unused or insignificant bits of the image. The insignificant or unused bits may be, for example, hidden or invisible layers or color channels inside an image. Changes to these bits are undetectable to the naked eye because they are not used in the visual depiction/rendering of the image. Once the unused or insignificant bits are identified, the identified bits are used to store portions of the code. The code, therefore, is distributed throughout the identified unused bits of the image. In this regard, the image acts as a vessel for concealing the code. The stored code does not create any noticeable visual alterations to the image. To the naked eye, the image that contains the code is no different than the image that does not contain the code.

[0051] In step 1 10, the unique ID generating module 22 outputs the modified image containing the concealed code as the unique ID for the user.

[0052] FIG. 4A is a flow diagram of a process executed by the unique ID processing module 22 for authenticating a user based on a submitted unique ID according to one embodiment of the invention. According to one embodiment, the end user device 16 interacts with the HTTP software 18 to fill out a login form. The login form may prompt the user to provide, at a minimum, a single unique ID. Once filled, the login form (also referred to as a request) is forwarded by the HTTP software 18 to the unique ID processing module 24.

[0053] In act 200, the unique ID processing module 24 receives the login form including a unique ID. According to one embodiment, the unique ID is accompanied with information specific to the customer server 12 transmitting the request, such as, for example, a client ID and/or client key (collectively referred to as client credentials) unique to the particular customer server. In act 200, the unique ID processing module 24 identifies a particular user to which the unique ID is associated. This may be done, for example, based on information provided in the login form, based on the unique ID that is provided, and or the like.

[0054] In response to receipt of the login form and identification of the particular user, the unique ID processing module 22 determines whether a 2-step authentication process has been enabled for the particular user. The 2-step authentication process is deemed to be enabled if, for example, the user submitted a cell phone number in step 86 of FIG. 2.

[0055] If the 2-step authentication process has been enabled, the unique ID processing module 22 proceeds generate a code challenge in act 202. For example, a random code may be generated and texted to the user-provided cell phone number. The HTTP software 18 requests the user to enter the code they received, and then the code is sent to the API module 20 for additional authentication before proceeding to the customer's site.

[0056] In act 204, the unique ID processing module 22 transmits the generated code challenge to the user's cell phone. The user may be prompted to respond to the received message with the same code challenge to verify that the user transmitting the login request is the user that is associated with the cell phone.

[0057] In act 206, the unique ID processing module 22 receives and verifies the challenge code.

[0058] In act 208, the unique ID processing module 22 proceeds to verify the unique ID received with the login request. According to one embodiment, a first check of the verification process is to determine whether the expected customer ID and/or key were received with the request. A failure to receive such client credentials is indicative that the request was not transmitted by the customer server 12, but transmitted by an unauthorized system, and the authentication will fail.

[0059] If the correct client credentials have been received, the unique ID processing module 22 proceeds to verify the unique ID. In this regard, the unique ID processing module 22 retrieves the original image stored in the mass storage device 26 and compares the received image against the image that is retrieved. According to one embodiment, the comparison outputs differences between the original image and the received image. The differences are then compared against the stored encrypted code.

[0060] As discussed above, three different types of codes may be stored for a user: single-use code, regular-use code, and duress code. A comparison is made against each stored code to determine a match. If a match is not made against one of the codes, authentication fails, and the unique ID processing module 24 transmits a failure action URL to the end-user device 16 in act 212. The URL may, according to one embodiment, be a link to a random website with no association to the customer server 12. Other actions such as display of error messages and the like are also contemplated as will be appreciated by a person of skill in the art.

[0061] If there is a match of the embedded code against one of the stored codes, a success action URL is transmitted to the end-user device 16 in act 210. The type of success action to be invoked via the URL depends on the type of unique ID type that was received. For example, if a single-use unique ID was received, the unique ID processing module 24 disqualifies that unique ID from being re-used again. In addition, the unique ID generating module 22 issues a new unique ID by generating and embedding a new code, and transmits the unique ID to the user. According to one embodiment, the automatically deactivating of the received unique ID and reissuing a replacement unique ID can be done manually or automatically without a specific request from the user. Also, according to one embodiment, the replacement unique ID uses the same image that is used by the previous unique ID. However, the embedded code in the image differs from the code that was embedded in the received image.

[0062] If a match is made against a duress unique ID, the unique ID processing module 24 responds with a scalable response based on the threat to the user. The automated behavior may be configured by the administrator of the customer server 12. For example, the administrator may configure the automated behavior to be to send an email, SMS/text, alert or the like to a designated email address, phone number, wearable technology, or the like. In other examples, the behavior may be to disable access for other users, limit the availability of data, or display an error screen during login designed to convince the perpetrator that the site is currently unavailable.

[0063] If a match is made against a regular use unique ID, the unique ID processing module 24 may respond by taking a success action such as, for example, retrieving user data stored in association with the received code, and forwarding the user data to the customer server 12 via the API module 20. In this embodiment, it is assumed that the code itself does not contain the user data, but the user data is stored in the mass storage device in association with the code. In other embodiments, the success action may be giving access to resources of the customer server 12, completing a purchase transaction using the user data, and the like.

[0064] FIG. 4B is a flow diagram of a process executed by the unique ID processing module 22 for authenticating a user based on a submitted unique ID according to another embodiment of the invention. The process of FIG. 4B is similar to the process of FIG. 4A, except that the login form provided by the customer server 12 also includes a math challenge that a user is to solve in order to proceed with the authentication process. The math challenge may be a simple math problem which changes each time the login form is accessed. For example, the math challenge may prompt the user to provide an answer to the following math problem: 1 1 + 22.

[0065] In act 222, the unique ID processing module 24 (or some other module of the authentication server 10) evaluates the math challenge to determine if the correct answer has been provided within an allotted time. If the challenge is completed successfully by receiving from the user the expected value within the allotted time, as determined in act 224, the authentication process proceeds to check for 2-step authentication in act 228, similar to what is described in FIG. 4A.

[0066] If, however, the math challenge is not completed successfully, one or more failure actions are invoked in act 226. In this regard, failures may be treated the same as if the user were entering the wrong password. For example, a certain number of failed attempts may lockout the user, the user's device, or even permanently blacklist the user and/or device from further login attempts.

[0067] According to one embodiment, the login form that is submitted to the unique ID processing module for authentication differs from login forms that are typically transmitted in the art. FIG. 5A illustrates code for generating a typical HTML login form according to existing mechanisms. As depicted in FIG. 5A, the login form prompts and expects a username or password values in the corresponding username and password fields.

[0068] FIG. 5B illustrates code for generating a login form according to embodiments of the present invention. According to the illustrated embodiment, a "file" field 208 prompts for a MIME value containing bit data (image data) that makes up the unique ID. The MIME data is interpreted by an "action" page and saved as a photo in the mass storage device 26 where it can be validated during the authentication process.

[0069] FIG. 6 is a schematic layout diagram of a unique ID 300 according to one

embodiment of the invention. The unique ID 300 is composed of image bits 302 and encrypted code bits 304. The image bits 302 together form the image, which, in this example, is an image of a sun wearing sunglasses. As a person of skill in the art will appreciate, each time a photo of an object is taken, the image bits 302 making up the image differ for each instance of the photo even if the subject of the photo remains the same. This is due to the varying circumstances surrounding the taking of the photo. For example, the lighting, position of the object, position of the person taking the photo, and the like, may differ for each instance the photo is taken, resulting in differences in the image bits 302.

[0070] The encrypted code bits 304 that are embedded in the image together form a code that is used for identifying a user. The bits of the code are spread out over various bytes of the image file, taking up unused or insignificant bits of those bytes. In the illustrated example, the encrypted code is "01100101."

[0071] According to one embodiment, the authentication server 10 acts as a gatekeeper for e- commerce systems, protecting and authenticating end users during checkout of an online purchase. In this regard, the server 10 may handle the basic user authentication for accessing user records stored on the customer server 12, or store the end user data on behalf of the customer server and provide the data to the customer server upon successful authentication of the end user. According to one embodiment, each time the unique ID is used on an e- commerce site, the authentication server automatically retires the unique ID and issues a new unique ID, which prevents fraudulent transactions and/or ID theft.

[0072] According to one embodiment, the end user data is stored at an e-commerce/merchant site (e.g. the customer server 12), but the authentication server 10 authenticates the end-user with his unique ID instead of a user name and password. The name or username of the shopper is not stored in the e-commerce/merchant server. Instead, the e-commerce site stores an account number or account identifier in association with the payment data. Upon successful authentication of the end-user by the authentication server 10, the server provides the e-commerce site with the user's account ID so that the e-commerce site knows which payment and/or shipping details to access. This process maintains consistent protection of the users' identifying information so that the e-commerce site stores, according to one embodiment, credit card data, address, shopping cart identifier, and the like, but does not store personal identification information of the users including a user name and/or password.

[0073] According to another embodiment of the invention, the name or username of a user along with the user's credit card data and address are encrypted and stored in the mass storage device 26. This information is passed to the e-commerce site upon successful authentication of the end-user. This helps prevent the storage of sensitive data on the merchant's server which may be subject to hacking by unauthorized users,

[0074] According to yet another embodiment, the authentication server provides merchant services in addition to authentication services. According to this embodiment, the e- commerce site makes a transaction request, and the authentication server approves or disapproves the transaction. The e-commerce site merely stores the shopping cart data and forwards such data to the authentication sever for approval or disapproval. User identification information, credit card information, address, and the like, are securely stored in the mass storage device 26.

[0075] It is the Applicant's intention to cover by claims all such uses of the invention and those changes and modifications which could be made to the embodiments of the invention herein chosen for the purpose of disclosure without departing from the spirit and scope of the invention. Thus, the present embodiments of the invention should be considered in all respects as illustrative and not restrictive.

Claims

CLAIMS:

1. A method for generating a unique identifier for a user, the method comprising: transmitting, by a processor, a prompt for user selection of a digital image;

receiving, by the processor, the selected digital image;

saving, by the processor, the received digital image in a data storage device;

identifying, by the processor, a first code associated with the user;

embedding, by the processor, the first code into the digital image and generating a first modified digital image in response;

storing, by the processor, the first modified digital image in the data storage device; and

transmitting, by the processor, the first modified digital image to the user over a data communications network.

2. The method of claim 1 , wherein the digital image is stored in an end user device accessible to the user.

3. The method of claim 1, wherein the first code is personal information of the user.

4. The method of claim 3, wherein the personal information is at least one of address, telephone number, birthdate, name, driver license number, social security number, credit card number, user identifier, or password.

5. The method of claim 1, wherein the first code is a randomly generated code.

6. The method of claim 1 further comprising:

receiving, by the processor, an alphanumeric string provided by the user; and encrypting, by the processor, the first code based on the alphanumeric string, wherein the first code embedded into the digital image is the encrypted code.

7. The method of claim 1, wherein the embedding includes identifying bits of the digital image that do not contribute in creating a visual depiction of the digital image.

8. The method of claim 1 further comprising:

receiving, by the processor, a request including the first modified digital image;

retrieving, by the processor, the embedded first code from the digital image;

comparing, by the processor, the retrieved first code against a stored version of the first code; and taking, by the processor, a success action associated with the first modified digital image in response to a match of the retrieved first code against the stored version of the first code.

9. The method of claim 8 further comprising:

transmitting, by the processor, a security code to a mobile telephone number associated with a user; and

verifying, by the processor, the transmitted security code against a security code received from the mobile telephone number.

10. The method of claim 8 further comprising:

identifying, by the processor, a second code associated with the user;

embedding, by the processor, the second code into the digital image and generating a second modified digital image in response;

storing, by the processor, the second modified digital image in the data storage device; and

transmitting, by the processor, the second modified digital image to the user over a data communications network, wherein a success action associated with the second modified digital image is different from the success action associated with the first modified digital image.

1 1. The method of claim 10, wherein the success action includes transmitting an alert of a duress situation involving the user.

12. The method of claim 8 further comprising:

receiving, by the processor, an answer to a math problem provided by the user;

determining, by the processor, whether the answer is correct; and

in response to determining that the answer is incorrect, taking, by the processor, a failure action.

13. The method of claim 8, wherein the success action is retrieving account information of the user for an e-commerce transaction.

14. A system for generating a unique identifier for a user, the system comprising: processor; and

memory, wherein the memory has stored therein instructions that, when executed by the processor, cause the processor to: transmit a prompt for user selection of a digital image;

receive the selected digital image;

save the received digital image in a data storage device;

identify a first code associated with the user;

embed the first code into the digital image and generating a first modified digital image in response;

store the first modified digital image in the data storage device; and transmit the first modified digital image to the user over a data communications network.

15. The system of claim 14, wherein the digital image is stored in an end user device accessible to the user.

16. The system of claim 14, wherein the first code is personal information of the user.

17. The system of claim 16, wherein the personal information is at least one of address, telephone number, birthdate, name, driver license number, social security number, credit card number, user identifier, or password.

18. The system of claim 14, wherein the first code is a randomly generated code.

19. The system of claim 14, wherein the instructions further cause the processor to:

receive an alphanumeric string provided by the user; and

encrypt the first code based on the alphanumeric string, wherein the first code embedded into the digital image is the encrypted code.

20. The system of claim 20, wherein the embedding includes identifying bits of the digital image that do not contribute in creating a visual depiction of the digital image.

21. The system of claim 14, wherein the instructions further cause the processor to:

receive a request including the first modified digital image;

retrieve the embedded first code from the digital image;

compare the retrieved first code against a stored version of the first code; and take a success action associated with the first modified digital image in response to a match of the retrieved first code against the stored version of the first code.

22. The system of claim 21, wherein the instructions further cause the processor to:

receive a request including the first modified digital image;

transmit a security code to a mobile telephone number associated with a user; and verify the transmitted security code against a security code received from the mobile telephone number.

23. The system of claim 21 , wherein the instructions further cause the processor to:

identify a second code associated with the user;

embed the second code into the digital image and generating a second modified digital image in response;

store the second modified digital image in the data storage device; and

transmit the second modified digital image to the user over a data communications network, wherein a success action associated with the second modified digital image is different from the success action associated with the first modified digital image.

24. The system of claim 23, wherein the success action includes transmitting an alert of a duress situation involving the user.

25. The system of claim 21, wherein the instructions further cause the processor to:

receive an answer to a math problem provided by the user;

determine whether the answer is correct; and

in response to determining that the answer is incorrect, take, by the processor, a failure action.

26. The system of claim 21, wherein the success action is retrieving account information of the user for an e-commerce transaction.

27. A system substantially as hereinbefore described with reference to the accompanying drawings.

28. A method substantially as hereinbefore described with reference to the accompanying drawings.