SYSTEMS AND METHODS FOR PROVIDING ATTESTED VERIFICATION OF PERSONAL DATA

Example implementations include a method, apparatus and computer-readable medium for attested verification of personal data, comprising transmitting an access request to a verifying entity, wherein the access request is for a service, product, or information accessible solely to an authorized user. The implementations include receiving, from the verifying entity, a verification request that indicates at least one attribute of personal data that classifies a user as the authorized user. The implementations include generating a verification response indicating possession of the at least one attribute. The implementations include identifying, in a digital wallet, attested data issued by a trusted entity that confirms possession of the at least one attribute of the personal data. The implementations include transmitting, to the verifying entity, the verification response and the attested data without including the personal data. The implementations include receiving a grant or denial of the access request from the verifying entity.

TECHNICAL FIELD

The described aspects relate to data security and transaction systems.

BACKGROUND

Aspects of the present disclosure relate generally to data security and transaction systems, and more particularly, to systems and methods for providing attested verification of personal data.

Data privacy is a core concern because there is a significant impact on people and companies when data breaches occur. When a user shares sensitive information such as a date of birth, social security number, address, etc., with a company, there is a possibility that a malicious entity may intercept communications or hack into the company database, thus jeopardizing the sensitive information. In many cases, the actual information is not needed by the company. For example, a bank may simply need to confirm whether a customer has a valid social security number (SSN), but does not need to know the actual number itself. Although revealing the SSN to the bank confirms that the customer has a valid SSN, once the SSN is stored in bank records, it is at risk of being extracted in a data breach.

Conventional security and transaction systems are unable to address these issues. Accordingly, there exists a need for improvements in such systems.

SUMMARY

An example aspect includes a method for attested verification of personal data, comprising transmitting an access request to a verifying entity, wherein the access request is for a service, product, or information accessible solely to an authorized user. The method further includes receiving, from the verifying entity, a verification request that indicates at least one attribute of personal data that classifies a user as the authorized user. Additionally, the method further includes generating a verification response indicating possession of the at least one attribute. Additionally, the method further includes identifying, in a digital wallet, attested data issued by a trusted entity that confirms possession of the at least one attribute of the personal data. Additionally, the method further includes transmitting, to the verifying entity, the verification response and the attested data without including the personal data. Additionally, the method further includes receiving a grant or denial of the access request from the verifying entity.

Another example aspect includes an apparatus for attested verification of personal data, comprising one or more memories and one or more hardware processors coupled with the one or more memories. The one or more hardware processors are configured, individual or in combination, to transmit an access request to a verifying entity, wherein the access request is for a service, product, or information accessible solely to an authorized user. The one or more hardware processors are configured, individual or in combination, to receive, from the verifying entity, a verification request that indicates at least one attribute of personal data that classifies a user as the authorized user. Additionally, the one or more hardware processors are configured, individual or in combination, to generate a verification response indicating possession of the at least one attribute. Additionally, the one or more hardware processors are configured, individual or in combination, to identify, in a digital wallet, attested data issued by a trusted entity that confirms possession of the at least one attribute of the personal data. Additionally, the one or more hardware processors are configured, individual or in combination, to transmit, to the verifying entity, the verification response and the attested data without including the personal data. Additionally, the one or more hardware processors are configured, individual or in combination, to receive a grant or denial of the access request from the verifying entity.

Another example aspect includes an apparatus for attested verification of personal data, comprising means for transmitting an access request to a verifying entity, wherein the access request is for a service, product, or information accessible solely to an authorized user. The apparatus further includes means for receiving, from the verifying entity, a verification request that indicates at least one attribute of personal data that classifies a user as the authorized user. Additionally, the apparatus further includes means for generating a verification response indicating possession of the at least one attribute. Additionally, the apparatus further includes means for identifying, in a digital wallet, attested data issued by a trusted entity that confirms possession of the at least one attribute of the personal data. Additionally, the apparatus further includes means for transmitting, to the verifying entity, the verification response and the attested data without including the personal data. Additionally, the apparatus further includes means for receiving a grant or denial of the access request from the verifying entity.

Another example aspect includes a computer-readable medium having instructions stored thereon for attested verification of personal data, wherein the instructions are executable by a processor to transmit an access request to a verifying entity, wherein the access request is for a service, product, or information accessible solely to an authorized user. The instructions are further executable to receive, from the verifying entity, a verification request that indicates at least one attribute of personal data that classifies a user as the authorized user. Additionally, the instructions are further executable to generate a verification response indicating possession of the at least one attribute. Additionally, the instructions are further executable to identify, in a digital wallet, attested data issued by a trusted entity that confirms possession of the at least one attribute of the personal data. Additionally, the instructions are further executable to transmit, to the verifying entity, the verification response and the attested data without including the personal data. Additionally, the instructions are further executable to receive a grant or denial of the access request from the verifying entity.

DETAILED DESCRIPTION

The present disclosure includes apparatuses and methods that provide attestation data in place of private information. The apparatuses and methods move to leverage a secure element and digital wallet to record attested confirmation of identity and credential data by a trusted authoritative source. This allows for the data to be trusted, without sensitive information being shared (ultimately reducing the dangers of security breaches). More specifically, the present disclosure describes an attestation application that can transact with the digital wallet of a user. The attestation application may be secured by a secure element or other security method such that user information such as names, social security numbers (SSNs), date of births (DOBs), addresses, credential data, etc., can be confirmed by the authoritative sources for those data elements. For example, whether a user is over the age of 18 may be confirmed by the Department of Motor Vehicles, whether the user is a citizen may be confirmed by a different government entity such as the Department of Homeland Security, etc. With this architecture and wallet structure, sensitive data such as the date of birth or citizenship number of the user are not revealed to the verifying entity. If the verifying entity later experiences a data breach, the sensitive information is not jeopardized as it remains with the user and trusted/issuing entities alone.

FIG.1is diagram100of an attestation flowchart, in accordance with exemplary aspects of the present disclosure. User entity102represents the user and comprises device104. Device104may be any device that is capable of communicating with other devices and storing a digital wallet. Examples of device104include, but are not limited to, a smartphone, a laptop, a wearable device, and a tablet. Trusted entity106represents an institution that can reliably store and receive personal data provided by user entity102. Trusted entity106may utilize device(s)108, which include any device capable of communicating with other devices such as device104and attesting information. Examples of trusted entity106include a government institution, an employer, a school/university, a hospital, etc.

Consider an example of user entity102submitting a health record to trusted entity106, which is a hospital. The personal data may include vaccination information, address, date of birth, etc. Consider another example of user entity102submitting a bank statement (confirming residence) and a photo identification card (confirming name, age, etc.) to trusted entity106, which is a government entity such as the Department of Motor Vehicles.

In each example, device104may submit an attestation request along with the personal data. The attestation request may specifically request that trusted entity106confirm certain attributes of the personal data. These attributes may be predetermined and may be commonly requested by verifying entities. For example, the sensitive information in personal data may be the date of birth of user entity102. The attested data may confirm an attribute of whether or not a user is over 18 years of age. In another example, the sensitive information in personal data may be the address of user entity102. The attested data may simply confirm that the user resides in a particular area (e.g., town, city, state, etc.) without revealing the exact address.

In response to receiving the attestation request, device(s)108of trusted entity106may transmit attested data, which confirms the validity and authenticity of the attributes in the personal data, to device104of user entity102. Device104may store the attested data in digital wallet109.

Subsequently, user entity102may interact with a verifying entity110, which may be any entity that requests information from the user and can potentially store the received information. For example, verifying entity110may be a company or a store in which the user is performing a transaction. Device104of user entity102may issue an access request to verifying entity110. This access request may be for a particular service, product, information, etc., that is protected for authorized users only.

Suppose that verifying entity110is an airline. The user may request a boarding pass and device(s)112(e.g., any combination of servers, computers, smartphones, terminal devices, etc.) of verifying entity110may transmit a verification request to device104. The verification request may query whether the user is eligible to fly into a particular country. More particularly, the verification request seeks to confirm that user entity102has a valid passport that is unexpired. In a traditional exchange, the user provides his/her passport to the airline. The passport includes information such as name, age, height, weight, passport number, etc., which is not all relevant information for the airline and includes sensitive information.

According to the present disclosure, device104transmits a verification response and a portion of the attested data stored in digital wallet109to verifying entity110. For example, in the verification response, the user may state that he/she has a valid passport for travel and that the passport is unexpired. In this case, trusted entity106may be the government that issued the passport to user entity102. Trusted entity106may provide, via device(s)108, attested data that confirms that user entity102has a passport and that the passport is unexpired. This attested data may be stored in digital wallet109by device104.

In some aspects, in response to receiving a verification request from verifying entity110, device104may determine the relevant attested data to transmit to verifying entity110. In some aspects, each attested data may be assigned a tag (e.g., “age,” “expiration,” “identification number,” “gender,” etc.).

In some aspects, verification request may explicitly request specific attributes (e.g., whether a passport is held by the user, whether the passport is expired, etc.). of personal data rather than the actual data itself (e.g., passport number, passport expiration date, etc.). In this case, device104transmits attested data with attributes assigned corresponding tags to device(s)112. For example, an attested data tagged with “expiration” corresponds to an expiration date and whether information is expired or not.

It is also possible that verifying entity110asks for the actual data itself. In this case, device104transmits all attested data associated with the requested data to device(s)112based on the tag. For example, device(s)112may request the passport number and expiration date of the user passport and, in response, device104may transmit attested data indicating that the passport number is authentic, and the passport is unexpired.

In yet other aspects, verifying entity110may request a collection of personal data such as the passport in its entirety. In this case, device104may transmit all attested data associated with the requested collection to device(s)112. For example, device104may transmit attested data indicating that the passport number is authentic, the passport is unexpired, the issuing country is America, the gender is male, etc.

In response to receiving the attested data and verification response from device104, device(s)112may evaluate whether the verification response matches the attested data (e.g., whether the user's claim is supported by trusted entity106). Accordingly, device(s)112may transmit an attestation verification request to trusted entity106, which is configured to confirm or deny the accuracy of the verification response provided by device104.

In some aspects, the attested data provided by trusted entity106is signed by a public encryption key of trusted entity106. This prevents device104from tampering with the attested data as the private encryption key of trusted entity106(unknown to all other entities) is needed to access the attested data. For example, user entity102may be unable to change the information attested by trusted entity106for personal means.

Trusted entity106may unencrypt the attested data using its private encryption key and compare the verification response with the attested data. For example, in the verification response, user entity102may claim that the passport is unexpired and the attested data may also indicate that the passport is unexpired. Trusted entity106may thus determine that the information matches and transmit an attestation response to verifying entity110. The attestation response may indicate whether the verification response is correct or incorrect.

Verifying entity110may then determine whether to grant or deny the access request of user entity102based on the attestation response. For example, if all information is accurate and acceptable in the verification response of the user, verifying entity110may grant the user request (e.g., issue a boarding pass). If there are discrepancies in the verification response and the attested data, verifying entity110may deny the access request.

FIG.2is diagram200of personal data and attested data, in accordance with exemplary aspects of the present disclosure. In diagram200, personal data202includes a plurality of personal data points such as an image of a user, a name, an address, a date of birth, an identification number, and an identification card expiration number. In a conventional transaction, verifying entity110may receive all of these sensitive data points and store them. However, using the apparatuses and methods of the present disclosure, these data points are not shared with verifying entity110. Instead, attested data204that is particularly relevant to the verifying entity110is shared from a digital wallet of user entity102. Attested data204may be protected by encryption206such that user entity102cannot tamper with its contents.

Referring toFIG.3andFIG.4, in operation, computing device300may perform a method400for attested verification of personal data, such as via execution of attested verification component315by one or more hardware processor(s)305and/or one or more memories310.

At block402, the method400includes transmitting an access request to a verifying entity, wherein the access request is for a service, product, or information accessible solely to an authorized user. For example, in an aspect, computing device300, one or more hardware processor(s)305, one or more memories310, attested verification component315, and/or transmitting component320may be configured to or may comprise means for transmitting an access request to verifying entity110(e.g., an airline), wherein the access request is for a service, product, or information accessible solely to an authorized user (e.g., a board pass of a passenger).

At block404, the method400includes receiving, from the verifying entity, a verification request that indicates at least one attribute of personal data that classifies a user as the authorized user. For example, in an aspect, computing device300, processor(s)305, memories310, attested verification component315, and/or receiving component325may be configured to or may comprise means for receiving, from verifying entity110, a verification request that indicates at least one attribute of personal data that classifies a user as the authorized user.

For example, an airline may request information confirming that the passenger has a valid unexpired passport. This is usually provided in the form of a passport number and an expiration date.

At block406, the method400includes generating a verification response indicating possession of the at least one attribute. For example, in an aspect, computing device300, processor(s)305, memories310, attested verification component315, and/or generating component330may be configured to or may comprise means for generating a verification response indicating possession of the at least one attribute. For example, generating component330may generate a message that includes a payload comprising the verification response. Referring to the airline example, the verification response may include a user statement “I have a valid unexpired passport.”

At block408, the method400includes identifying, in a digital wallet, attested data issued by a trusted entity that confirms possession of the at least one attribute of the personal data. For example, in an aspect, computing device300, processor(s)305, memories310, attested verification component315, and/or identifying component335may be configured to or may comprise means for identifying, in digital wallet109, attested data issued by trusted entity106that confirms possession of the at least one attribute of the personal data. For example, trusted entity106may be the government entity that issued the passport to the user. At the time of passport creation, trusted entity106may provide attested data to the user (for storage in digital wallet109). The attested data may confirm that the passport is valid and unexpired.

At block410, the method400includes transmitting, to the verifying entity, the verification response and the attested data without including the personal data. For example, in an aspect, computing device300, processor(s)305, memories310, attested verification component315, and/or transmitting component335may be configured to or may comprise means for transmitting, to verifying entity110, the verification response and the attested data without including the personal data. In an alternative or additional aspect, the personal data includes a data point indicative of sensitive information and the attested data includes a confirmation that the data point is valid without revealing the data point. By not revealing personal data (such as the passport number and the expiration date), the data is protected from a potential security breach of verifying entity110. Ultimately, this limits the spread of sensitive information (i.e., information that the user would not wish to reveal to unauthorized/malicious entities or information that can be used to track or behave as the user maliciously).

In an alternative or additional aspect, access to the attested data in the digital wallet109is protected by a user credential. In this aspect, the user credential is one or more of: a username and password combination, a biometric input, or a pattern input. This prevents anyone using the device of the user from impersonating the user because additional security measures are provided.

At block412, the method400includes receiving a grant or denial of the access request from the verifying entity. For example, in an aspect, computing device300, processor(s)305, memories310, attested verification component315, and/or receiving component335may be configured to or may comprise means for receiving a grant or denial of the access request from verifying entity110. For example, verifying entity110may determine that the verification response from the user corresponds to the attested data. In the scenario given of an airline, the airline may confirm that the attested data confirms the user statement of having a valid unexpired passport.

In an alternative or additional aspect, verifying entity110is configured to confirm, with trusted entity106, whether the verification response is authentic and grant or deny the access request based on the whether the verification response is authentic. For example, verifying entity110may confirm whether the attested data is untampered by directly transacting with trusted entity106. For example, the attested data may be encrypted with a public key of trusted entity106. Trusted entity106may receive and decrypt the attested data using a private key of trusted entity106. Trusted entity106may then compare the attested data with its own records and confirm its authenticity.

Referring toFIG.5, in an alternative or additional aspect, at block502, the method400may further include transmitting the verification response and the attested data to the trusted entity. For example, in an aspect, computing device300, processor(s)305, memories310, attested verification component315, and/or transmitting component320installed on device(s)112may be configured to or may comprise means for transmitting the verification response and the attested data to trusted entity106.

In this optional aspect, at block504, the method400may further include receiving, from the trusted entity, confirmation that the verification response is authentic. For example, in an aspect, computing device300, processor(s)305, memories310, attested verification component315, and/or receiving component325on device(s)112may be configured to or may comprise means for receiving, from trusted entity106, confirmation that the verification response is authentic.

In an alternative or additional aspect, the attested data in digital wallet109is encrypted by a first encryption key (e.g., a public key) of trusted entity106and verifying entity110is configured to confirm whether verification response is authentic using blocks502and504. Between these blocks, trusted entity106is configured to decrypt the attested data using a second encryption key (e.g., a private key) of trusted entity106and confirm that the verification response is authentic in response to determining that the verification response matches with the attested data that is decrypted.

FIG.6describes how the user receives the attested data from the trusted entity. The blocks ofFIG.6occur before block402ofFIG.4. Referring toFIG.6, in an alternative or additional aspect, at block602, the method400may further include transmitting, to the trusted entity, an attestation request and the personal data, wherein the attestation request includes a plurality of attributes comprising the at least one attribute that the trusted entity should attest. For example, in an aspect, computing device300, processor(s)305, memories310, attested verification component315, and/or transmitting component320may be configured to or may comprise means for transmitting, to trusted entity106, an attestation request and the personal data, wherein the attestation request includes a plurality of attributes comprising the at least one attribute that trusted entity106should attest. In the airline example, the plurality of attributes may include the validity of a passport, the active status of a passport, the issuing country of a passport, etc.

In this optional aspect, at block604, the method400may further include receiving, from the trusted entity, a plurality of attested data points generated based on the personal data, wherein the plurality of attested data points includes the attested data confirming possession of the at least one attribute of the personal data. For example, in an aspect, computing device300, processor(s)305, memories310, attested verification component315, and/or receiving component325may be configured to or may comprise means for receiving, from trusted entity106, a plurality of attested data points generated based on the personal data, wherein the plurality of attested data points includes the attested data confirming possession of the at least one attribute of the personal data.

In this optional aspect, at block606, the method400may further include storing the plurality of attested data points in the digital wallet. For example, in an aspect, computing device300, processor(s)305, memories310, attested verification component315, and/or storing component340may be configured to or may comprise means for storing the plurality of attested data points in digital wallet109.

One or more aspects of the apparatus and method of the present disclosure are further described in the following clauses.

Clause 1. An apparatus for attested verification of personal data, comprising: one or more memories; and one or more hardware processors coupled with the one or more memories and configured, individually or in combination, to: transmit an access request to a verifying entity, wherein the access request is for a service, product, or information accessible solely to an authorized user; receive, from the verifying entity, a verification request that indicates at least one attribute of personal data that classifies a user as the authorized user; generate a verification response indicating possession of the at least one attribute; identify, in a digital wallet, attested data issued by a trusted entity that confirms possession of the at least one attribute of the personal data; transmit, to the verifying entity, the verification response and the attested data without including the personal data; and receive a grant or denial of the access request from the verifying entity.

Clause 2. The apparatus of clause 1, the verifying entity is configured to: confirm, with the trusted entity, whether the verification response is authentic; and grant or deny the access request based on the whether the verification response is confirmed to be authentic.

Clause 3. The apparatus of any of the preceding clauses, wherein the attested data in the digital wallet is encrypted by a first encryption key of the trusted entity, and wherein the verifying entity confirms whether verification response is authentic by being configured to: transmit the verification response and the attested data to the trusted entity; and receive, from the trusted entity, confirmation that the verification response is authentic.

Clause 4. The apparatus of any of the preceding clauses, wherein the trusted entity is configured to: decrypt the attested data using a second encryption key of the trusted entity; and confirm that the verification response is authentic in response to determine that the verification response matches with the attested data that is decrypted.

Clause 5. The apparatus of any of the preceding clauses, wherein the one or more hardware processors are further configured, individually or in combination, to: transmit, to the trusted entity, an attestation request and the personal data, wherein the attestation request includes a plurality of attributes comprising the at least one attribute that the trusted entity should attest; receive, from the trusted entity, a plurality of attested data points generated based on the personal data, wherein the plurality of attested data points includes the attested data confirming possession of the at least one attribute of the personal data; and store the plurality of attested data points in the digital wallet.

Clause 6. The apparatus of any of the preceding clauses, wherein the personal data includes a data point indicative of sensitive information and the attested data includes a confirmation that the data point is valid without revealing the data point.

Clause 7. The apparatus of any of the preceding clauses, wherein access to the attested data in the digital wallet is protected by a user credential.

Clause 8. The apparatus of any of the preceding clauses, wherein the user credential is one or more of: a username and password combination, a biometric input, or a pattern input.

Clause 9. A method for attested verification of personal data, comprising: transmitting an access request to a verifying entity, wherein the access request is for a service, product, or information accessible solely to an authorized user; receiving, from the verifying entity, a verification request that indicates at least one attribute of personal data that classifies a user as the authorized user; generating a verification response indicating possession of the at least one attribute; identifying, in a digital wallet, attested data issued by a trusted entity that confirms possession of the at least one attribute of the personal data; transmitting, to the verifying entity, the verification response and the attested data without including the personal data; and receiving a grant or denial of the access request from the verifying entity.

Clause 10. The method of clause 9, the verifying entity is configured to: confirm, with the trusted entity, whether the verification response is authentic; and grant or deny the access request based on the whether the verification response is confirmed to be authentic.

Clause 11. The method of any of the preceding clauses, wherein the attested data in the digital wallet is encrypted by a first encryption key of the trusted entity, and wherein the verifying entity is configured to confirm whether verification response is authentic by: transmitting the verification response and the attested data to the trusted entity; and receiving, from the trusted entity, confirmation that the verification response is authentic.

Clause 12. The method of any of the preceding clauses, wherein the trusted entity is configured to: decrypt the attested data using a second encryption key of the trusted entity; and confirm that the verification response is authentic in response to determining that the verification response matches with the attested data that is decrypted.

Clause 13. The method of any of the preceding clauses, further comprising: transmitting, to the trusted entity, an attestation request and the personal data, wherein the attestation request includes a plurality of attributes comprising the at least one attribute that the trusted entity should attest; receiving, from the trusted entity, a plurality of attested data points generated based on the personal data, wherein the plurality of attested data points includes the attested data confirming possession of the at least one attribute of the personal data; and storing the plurality of attested data points in the digital wallet.

Clause 14. The method of any of the preceding clauses, wherein the personal data includes a data point indicative of sensitive information and the attested data includes a confirmation that the data point is valid without revealing the data point.

Clause 15. The method of any of the preceding clauses, wherein access to the attested data in the digital wallet is protected by a user credential.

Clause 16. The method of any of the preceding clauses, wherein the user credential is one or more of: a username and password combination, a biometric input, or a pattern input.