Patent Application
20170161746
The present disclosure is generally related to detection of attempted theft by fraud, and more particularly, to systems and methods of managing personal identifying information (PII) after the data has been compromised and of verifying customer data against the compromised data to identify potential fraud risks.
For years, there have been a large number of reported incidents of customer data being accessed by unauthorized computer users. Sometimes, such data compromises may result in theft of personal identifying information (PII), including social security numbers, email address, address data, and other information, which PII data may be used to fraudulently open additional credit accounts, gain access to user accounts, file for tax returns or gain healthcare services.
In certain embodiments, systems and methods are disclosed that may allow businesses, whose customer data has been exposed or compromised, to safely and securely share this information with other businesses, whose customers may be at risk. By alerting at-risk entities which of their consumers may be at an increased risk of identity theft, the systems and methods disclosed can protect the consumer from harm from such data breaches. Further, the systems and methods can help businesses reduce potential fraud losses. Unlike other “breach” solutions, the systems and methods herein can attempt to prevent harm rather than detecting it after the fact. Additionally, the system and methods described herein may broaden consumer protection to include account takeover, wire fraud, tax fraud and medical ID theft, among other things.
In order to avoid double-victimizing consumers whose data has been exposed, the protection and security of the compromised data is a high priority. In certain embodiments, compromised data may be disassociated and each data field may be independently encrypted using different encryption keys. Further, the encryption keys may be changed periodically.
In certain embodiments, a compromised identity exchange system may include a memory, an interface to receive encrypted personal identifying information (PII), and a processor coupled to the interface and the memory. The processor may be configured to unencrypt the PII and re-encrypt the PII to produce re-encrypted PII data using a different encryption key for each field and to store the re-encrypted PII data as compromised data in the memory.
In other certain embodiments, a computer-readable memory device including instructions that, when executed, cause a processor to receive personally identifying information (PIT) data from a computing device, unencrypt the PII data, and re-encrypt the PII data using a unique encryption key for each field. The instructions further may cause the processor to compare the re-encrypted PII data to compromised data stored in a database and determine a risk score corresponding to the re-encrypted PII data based in part on the comparison.
In still other certain embodiments, a compromised data exchange system may include a memory, an interface to receive encrypted personal identifying information (PII), and a processor coupled to the interface and the memory. The processor may be configured to process exposed PII data to disassociate the PII data, encrypt the disassociated PII data, and store the encrypted and disassociated PII data as compromised data in the memory.
In the following discussion, the same reference numbers are used in the various embodiments to indicate the same or similar elements.
In the following detailed description of embodiments, reference is made to the accompanying drawings which form a part hereof, and which are shown by way of illustrations. It is to be understood that features of various described embodiments may be combined, other embodiments may be utilized, and structural changes may be made without departing from the scope of the present disclosure. It is also to be understood that features of the various embodiments and examples herein can be combined, exchanged, or removed without departing from the scope of the present disclosure.
In accordance with various embodiments, the methods and functions described herein may be implemented as one or more software programs running on a computer processor or controller. In accordance with various embodiments, the methods and functions described herein may be implemented as one or more software programs running on a computing device, such as a tablet computer, smartphone, personal computer, server, or any other computing device. Dedicated hardware implementations including, but not limited to, application specific integrated circuits, programmable logic arrays, and other hardware devices can likewise be constructed to implement the methods and functions described herein. Further, the methods described herein may be implemented as a device, such as a computer readable storage medium or memory device, including instructions that when executed cause a processor to perform the methods.
Conventionally, in response to a breach of a company's data security, a press release may be issued, and affected customers may be notified. However, such compromised data may be used by criminals to open new credit accounts or to attempt to gain access to a customer's account. As used herein, the term “exposed data” or “compromised data” refers to any part of personally identifying information (PII) that may have been compromised or breached, such that an unauthorized individual may have gained access to such information. Further, as used herein, the term “at-risk” refers to an individual or entity that may have PII that may also be in the exposed or compromised data. For the purposes of this disclosure, if PII belonging to a customer of a company (entity) has been exposed, then that company can be considered at-risk. An at-risk entity or at-risk individual may be at risk of losing money or of reputational harm.
Further, an at-risk entity may be in danger of opening new fraudulent accounts based on the exposed data, permitting account takeover of an existing account based on the exposed data, experiencing theft of services based on the exposed data, allowing unauthorized access to further information (such as tax returns) based on the exposed data, and so on. In certain embodiments, the PII data may include names, dates of birth, addresses, social security numbers, email addresses, phone numbers, credit card numbers, bank information, other data, or any combination thereof. Such data may be used to identify a particular consumer and which may be misused to attempt to open accounts (such as new services, lines of credit, and so on), gain access to existing accounts, and so on.
Embodiments of compromised identity exchange systems and methods are described below that may be configured to host compromised data or to exchange encrypted data with distributed data sources in order to evaluate risk, to mitigate harm to companies and consumers from such data breaches, or any combination thereof. The compromised identity exchange systems and methods may include capturing compromised data in a disassociated and encrypted form, decrypting the compromised data, and re-encrypting each field of the compromised data using different encryption keys for each field. The re-encrypted compromised data may be hosted by a compromised identity data exchange and personal identifying information (PII) data may be compared to the re-encrypted compromised data to determine a match. Potential risk to a consumer or to an at-risk entity may be determined based on the results of the match. As used herein, the term “disassociated” or “disassociated PII” may refer to PII data elements (identity elements) that have been separated or disconnected from one another by the data originator. In certain embodiments, the disassociated data may be separated or disconnected in such a way that the data elements may not be re-associated to correlate the data to an actual consumer identity by anyone other than the data originator, provided the data originator has the key to map the full identity back together.
In some embodiments, some or all of the compromised data may be hosted by other sources, such as one or more compromised entities. The compromised identity exchange system may receive a query including PII data from one of an at-risk entity or a consumer. The compromised identity exchange system may disassociate and encrypt the PII data from an at-risk entity if the at risk entity did not perform the disassociation and may communicate the encrypted data to one or more of the compromised entities in response to the query. The compromised identity exchange system may receive results from the one or more entities in response to the queries where a match was made to a full PII identity or disassociated identity elements. Each match returned can include information about the data breach, which may consists of the date of the breach, the size/volume of the breach, a code indicating how the data was lost or stolen, among other attributes. In addition to these attributes, attributes associated with the consumer may also be used to measure risk. These attributes might include the number and severity of data breaches a consumer has been involved with, the location of the consumer, the event, if any, that is triggering the risk assessment, among other things. Additionally, participating at-risk entities' reported fraud data will be used to identify fraud rates within every compromised entity's compromised file, as well as attributes will be generated that reflect location of fraud, fraud linkages to email, physical address, phone number or other identity elements. All of these data can be aggregated into risk based results, the aggregated results, or any combination thereof. The compromised identity exchange system may communicate the results, a risk indicator, or any combination thereof to the requester (i.e., the at-risk entity or the consumer). One possible embodiment of a compromised identity exchange system configured to host compromised PII data is described below with respect to
In some embodiments, each encrypted data item may be stored with a breach identifier corresponding to the data exposure event in which the compromised data was exposed. In certain embodiments, a compromised company may provide the PII data with an identifier for each field provided by the company, and the compromised PII exchange system 102 may re-encrypt the PII data, the identifier, and the breach identifier. Other embodiments are also possible.
In certain embodiments, the compromised PII exchange system 102 may communicate with at-risk entities 104, 106, and 108 via a network 112. Each entity 104, 106, and 108 may maintain customer data 114, 116, and 118, respectively. The compromised PII exchange system 102 may also communicate via the network 112 with computing device 120, such as smart phones, laptops, tablets, notebooks, or other data processing devices, at least some of which may be associated with particular consumers.
In certain embodiments, a consumer or an at-risk entity may want to determine if its data may correspond in some way to the data that was exposed. In certain embodiments, the consumer or at-risk entity may communicate at least a portion of its PII data to the compromised PII exchange system 102 for comparison against the compromised PII data 122. In certain embodiments, the portion of the PII data may be disassociated and encrypted prior to transmission. The compromised PII exchange system 102 may re-encrypt the PII data in the same manner as the PII data stored in the compromised PII data 122 and may compare the re-encrypted PII data from the source to the compromised PII data 122. The compromised PII exchange system 102 may return data related to the results of the comparison.
In some embodiments, the data returned may include a risk assessment score based on the results of the comparison. For example, if the data corresponds to PII data that has previously been identified in a fraudulent transaction, or that the compromised entity data breach is actively being used in fraudulent ways, the risk assessment score may be high. In another example, if the data results correspond to a low-risk event (such as a lost laptop computer) or an older event with no known harm, the risk assessment score may be lower.
In certain embodiments, the compromised PII data 122 may include encrypted and disassociated data together with an event identifier. The event identifier may include a code or number associated with a particular data exposure event, such as a hack, a breach, or other unauthorized access or exposure of the data. Such events may include intentional or unintentional releases of secure information to an untrusted environment, including exposure due to concerted attacks or through accidental data leaks. Once exposed, the leaked data may be utilized for nefarious activities, such as account takeover, fraudulent credit applications and so on. By including an event identifier, subsequent usages of the data may be correlated to the data exposure event, making it possible to potentially fraudulent activity based on usage of such exposed data.
In certain embodiments, the compromised PII exchange system 102 may operate as a data exchange to allow companies that have experienced a data breach (e.g., a compromised entity) to share (securely) at least an indication of correspondence of particular data to their compromised customer data. In some embodiments, the compromised entity 104 may disassociate its compromised customer data and encrypt the disassociated data before sending the encrypted disassociated PII data to the compromised PII exchange system 102. The compromised PII exchange system 102 may unencrypt the encrypted disassociated PII data and may re-encrypt the data using a different key for each field, which re-encrypted data may be stored in the database of compromised data 108. In some embodiments, data from multiple compromised entities may be aggregated and stored in the database or compromised data 108. In certain embodiments, the aggregated compromised data 108 may be stored in an encrypted and disassociated form, such that even the compromised PII exchange system 102 cannot recover data corresponding to a particular customer. The data may be encrypted with an event identifier associated with the particular compromising event. In certain embodiments, the compromised data may be searched to identify matches with received customer data, and the compromised PII exchange system 102 may be configured to provide an indication of potential risk based on a match or the absence of a match with the compromised data 108. Other embodiments are also possible.
In certain embodiments, the compromised company may be unwilling to share its PII data for hosting by another party. In such an instance, the compromised PII exchange system 102 may cooperate with an installable software implementation of the PII exchange application, which may be distributed to each of the compromised systems in order to perform the risk assessment checks. One possible example of a distributed exchange system is described below with respect to
The system 200 may include the compromised PII exchange system 102 configured to communicate with the exposed or compromised entities 204, 206, and 208 through secure communications links. In certain embodiments, the exposed or compromised entities 204, 206, and 208 may store customer PII data, some of which may have been exposed. In the illustrated example, each compromised entity or system 204, 206, and 208 may install a PII exchange application 202, which may be used to disassociate and encrypt each field of the compromised PII data (using different keys) to produce re-encrypted exposed PII data 214, 216, and 218, respectively. Further, PII exchange application 202 may communicate with a PII exchange application 202 at the compromised PII exchange system 102 to verify PII data from consumers and at-risk entities as previously discussed.
In certain embodiments, each compromised system 204, 206, and 208 may maintain and host its own compromised data, which data has been disassociated and re-encrypted by the PII exchange application 202. In certain embodiments, in response to receiving PII data from a source, such as an at-risk entity 104, 106, or 108, or from a computing device 120, the PII exchange application 202 of the compromised PII exchange system 102 may re-encrypt the PII data. The compromised PII exchange system 102 may send the re-encrypted PII data to the PII exchange applications 202 at the compromised systems 204, 206, and 208 so that they may search the exposed PII data 214, 216, and 218. Each PII exchange application 202 may communicate data related to the comparison to the PII exchange application 202 at the compromised PII exchange system 102.
In certain embodiments, the compromised PII exchange system 102 may aggregate the results and provide data corresponding to the results to the source of the request (e.g., an at-risk entity 104, 106, 108, or a consumer using a computing device 120). The data corresponding to the results may include a composite risk assessment score based on the results. For example, if the particular data is associated with multiple (exposed) data sets, the composite risk assessment score may be higher than if it was associated with only one. Further, if the particular data is associated with any of the exposed data sets, the result of the comparison from the various PII exchange applications 202 may include an identifier associated with the particular exposure event (e.g., how was the data exposed?). This identifier may also contribute to the risk assessment score, since an exposure due to a hacking event may have a different risk assessment than one due to a missing laptop computer or a lost credit card. Various examples of methods of determining the risk assessment score are discussed below.
The compromised entity 204 may include the exposed PII data 214 in a database. The exposed PII data 214 may include exposed names, dates of birth, social security numbers, addresses, phone numbers, email addresses, other data, or any combination thereof. The compromised company 204 may disassociate the PII data using a disassociation module 302 to form disassociated data 304. The disassociated data 304 may include the PII data in an unassociated form so that the PII data cannot be recovered from the disassociated data 304 to associate the data to a particular consumer. The disassociated data 304 may then be encrypted using a unique key using an encryption module 306, which may be provided by or shared with the compromised PII exchange system 102. The encrypted, disassociated PII data may be sent to the compromised PII exchange system 102.
The compromised PII exchange system 102 may unencrypt the received PII data and may re-encrypt the PII data using a re-encryption module 308 of the PII exchange application 202. In certain embodiments, the re-encryption module 308 may re-encrypt the PII data using a unique key from a plurality of encryption keys 310 for each field to produce compromised PII data 122. The plurality of encryption keys 310 may be remote from the compromised PII exchange system 102. In certain embodiments, incoming compromised PII data may be formatted encrypted and aggregated with the compromised PII data 122.
In certain embodiments, since all PII data stored by the compromised PII exchange system 102 has been disassociated, there may be cases where multiple elements of the original PII data match the exposed identity database in the compromised PII data 122; however, the matching data may not necessarily be associated with each other from the same original consumer identity. For example, a common name, such as “John Smith,” and a common address, such as “123 Main Street,” might match data within the re-encrypted compromised PII data 122; however, the matching data may be sourced from different records. Because the PII data has been disassociated prior to being received by the compromised PII exchange system 102, neither the compromised PII exchange system 102 nor the end-user will know how the match was achieved. However, given the most common projected uses of this information, the cost of a “False Positive” is low, and the security gains are worth the loss of precision. (This is true but should it be in the patent)
In general, two potential attack vectors exist for attacking the compromised PII exchange system 102. One possible attack involves a bad actor able to intercept transmission of data to the compromised PII exchange system 102. Another possible attack involves a hack or breach of the compromised PII exchange system 102. However, attacks of the first kind can be handled using industry standard transmission policies, with the additional precaution of using unique public/private key combinations for each participant. The only way a third party could decrypt this data would be if they had access to a private key of the compromised PII exchange system 102, which means that attacks of the first kind rely on an attack of the second type.
In the unlikely event that the compromised PII exchange system 102 is hacked, an intruder could gain access to the database (i.e., the compromised PII data 122). However, since all the PII fields in the compromised PII data 122 are encrypted using different keys and since the PII fields are disassociated, such a hack would still not expose the data. In order to gain access to the raw data, the intruder would also need to gain access to the key-store (encryption keys 310) of the compromised PII exchange system 102, which cannot be accessed by breaching the compromised PII exchange system 102. In certain embodiments, the encryption keys 310 may be stored in another location remote from the compromised PII data 122 and remote from the compromised PII exchange system 102 to provide an additional layer of protection. Even in the event that a hacker was able to penetrate the compromised PII exchange system 102 as well as the encryption keys 310, the hacker would only be able to access individual, un-linkable (disassociated) PII elements, which are of relatively little value.
In certain embodiments, the at-risk entity 104 may include consumer data 114, which data may need to be evaluated for risk due to a data exposure event at another company. The at-risk entity 104 may extract at least a portion of the consumer data 114 and process the PII data using a disassociation module 404 to produce disassociated customer PII data 406. The at-risk entity 104 may process the disassociated customer PII data 406 using an encryption module 408 and may send the encrypted disassociated PII data to the compromised PII exchange system 102.
The compromised PII exchange system 102 may include an interface 410 coupled to the network 112 and to a processor 412, which may be coupled to compromised PII data 122 and to a memory 414. In certain embodiments, the memory 414 may include data and a PII exchange application 202. The PII exchange application 202 may be executed by the processor 412 to verify the PII data against the compromised PII data 122.
In certain embodiments, the PII exchange application 202 may include a re-encryption module 308 configured to unencrypt the encrypted PII data from the at-risk entity 104 and to re-encrypt each field of the PII data with a different one of the encryption keys 310. The PII exchange application 202 may provide the re-encrypted data to the matching logic 422, which may cause the processor 412 to compare the PII data to the compromised PII data 122 to determine whether a match exists. The PII exchange application 202 may provide the results of the comparison to the risk scoring module 430, which may determine a risk assessment score and provide the score to an alerting module 432 that, when executed, may cause the processor 412 to communicate data related to the risk assessment score to the at-risk entity 104.
In certain embodiments, the PII exchange application 202 may include one or more modules to analyze matches. In certain embodiments, the PII exchange application 202 may quantify activity level based on the number of matches as one quantitative risk factor. In some embodiments, the PII exchange application 202 may include a list proximity detection module 424 that, when executed, may cause the processor 412 to identify proximity of a particular match to other previous matches or to other matches within the PII data. In some embodiments, proximity may refer to the proximity of the data to other data in the table of data, which proximity may suggest fraudulent activity involving a portion of the compromised data. In certain embodiments, the proximity may refer to a geographic proximity of addresses suggesting that a crime syndicate may be operating within a particular region or area. In certain embodiments, the PII exchange application 202 may also include a pattern detection module 426 that, when executed, may cause the processor 412 to identify a pattern with respect to area, neighborhood, names, or other matching PII data. In certain embodiments, the PII exchange application 202 may include a credit application matching module 428 that, when executed, may cause the processor 412 to store data corresponding to matches in the compromised PII data. Further, the credit application matching module 428 may detect multiple fraudulent credit applications based on the stored credit application data. In certain embodiments, the matching logic 422 may search the stored credit application data to detect potential fraudulent activity.
In certain embodiments, the risk scoring module 430 may cause the processor to evaluate risk based on a variety of characteristics of the fraud data, the consumer and of the breach. For example, a particular data breach may involve 15 million records. In such a case, the probability that a particular data item may be misused may be approximately one out of fifteen million, indicating a relatively low risk. In contrast, if the data breach involved only 20 records, then the probability may be one out of twenty, which high probability increases the potential risk. Other factors may include facts about the data breach, including how the data was exposed, when the data was exposed and so on. A risk score for a particular consumer may increase based on the number of data breaches for which PII data of that user has been included. Further, if various instances of matches correspond to known or suspected fraud events, the matches suggest that the data is being used, and thus the risk increases substantially. Other embodiments are also possible.
In certain embodiments, the risk scoring module 430 may implement a heuristic approach that takes into account one or more factors associated with the breach and with the matching of the PII data. In certain embodiments, the matching logic 422 may cause the processor 412 to match PII elements with the data in the compromised PII data 122 to look for a number of matches, where the breach occurred, the severity of the breach, the general statistical sense of risk, and so on. The risk assessment score may then be provided to the risk scoring module 430, which may determine a risk score. In certain embodiments, the alerting module 432 may cause the processor 412 to provide the comparison results including the risk assessment score to the at-risk entity 104 through the network 112.
In the example of
In certain embodiments, the exposed company 204 may include exposed identity data 502. The exposed company 204 may utilize the PII exchange application 202 to disassociate and encrypt the data to form encrypted and disassociated data 506, which may be stored in exposed PII data 214. In certain embodiments, the PII exchange application 202 may generate one or more encryption keys or may receive one or more encryption keys from the compromised PII exchange system 102. In certain embodiments, the PII exchange application 202 may encrypt each item of disassociated data using a different encryption key. In some embodiments, each item may also be encrypted with an associated event identifier and a unique identifier that can be used to re-associate the data at a later time, if needed. The unique identifier may be stored in a table or database at another location and may be used to restore the disassociated data to recover a complete PII data set for a consumer, if desired.
In certain embodiments, a requester 514 may provide data to the compromised PII exchange system 102, which may unencrypt and re-encrypt the data using a PII exchange application 202. The re-encrypted data may be compared to compromised PII data 122 and may be sent to the PII exchange application 202 of the exposed entity 204. The PII exchange application 202 may unencrypt and re-encrypt the data and compare the data to the exposed PII data 214. The results from both comparisons may be reported to the PII exchange application 202 of the compromised PII exchange system 102, and the PII exchange application 202 may determine a risk assessment score and report the data to the requester 514.
Referring now to
In certain embodiments, a user may interact with the computing device 606 to access an Internet browser application through which the user may visit web page hosted by the compromised PII exchange system 102. The user may enter his or her PII data in the web page and submit the PII data securely as an encrypted request 608 to the compromised PII exchange system 102.
In certain embodiments, the compromised PII exchange system 102 may unencrypt the compromised identity requests at 612, and may re-encrypt the PII using unique keys at 614A, 614B, and 614C for transmission to the exposed companies 204, 206, and 208, respectively.
The PII exchange application 202 at each exposed entity 204, 206, and 208 may compare the PII data to its exposed PII data 214, 216, and 218. In certain embodiments, at each exposed entity 204, 206, and 208, the PII exchange application 202 may unencrypt the PII data and re-encrypting the PII data with keys that correspond to the keys used to encrypt the data in the exposed PII data 214, 216, and 218. The PII exchange application 202 at each of the exposed companies 204, 206, and 208 may then search the exposed PII data 214, 216, and 218 to identify a match and may return data corresponding to the comparison to the compromised PII data exchange 102.
In certain embodiments, the compromised PII data exchange 102 may aggregate the results from all of the exposed companies 620 and may provide results (response with no PII data) 610 to the computing device 606. In certain embodiments, the compromised PII exchange system 102 may analyze the aggregate data to assess the risk and may provide a report including a risk assessment to the computing device 606. Other embodiments are also possible.
In certain embodiments, each field of the encrypted PII data may be stored with an exposure event identifier and with a unique identifier. In certain embodiments, data about the exposure event may be collected over time, and the identification of a match between PII data and data stored in the database may retrieve the matching data and the event identifier. A risk assessment may be determined, in part, based on facts relating to the exposure event. As discussed above, a large data breach may reduce the chance that a particular piece of information is being misused, while a smaller data breach may enhance the statistical probability. Further, in some embodiments, if the event was a lost laptop or other personal item, the probability may be impacted by the circumstances as well as the subsequent recovery or failure to recover the device. Over time, as data about the breach is collected, such data may be stored and used to evaluate particular matches in the data set.
Further, in some embodiments, the unique identifier stored with each field may be stored in a database, for example, at a remote location or with the data source (e.g., the compromised company that sent the data). Subsequently, the unique identifiers may be used to reassemble the PII data for a single individual (for example) from the disassociated PII data. This will only be possible if the compromised company keeps a mapping between the unique ID's of each identity element and the overall identity. Other embodiments are also possible.
At 804, the method 800 may include re-encrypting the PII data using a different key for each field. In certain embodiments, the PII data may be unencrypted first and then re-encrypted using keys corresponding to those used to encrypt data in a particular database. In some embodiments, the PII data may be duplicated and separately encrypted for transmission to PII exchange applications at one or more compromised companies.
At 806, the method 800 may include comparing the encrypted PII data to a database of compromised identities. In certain embodiments, the re-encrypted PII data is compared to the data in the database locally. Further, the PII data (in encrypted form) may be sent to the compromised entities for comparison with their local data using the PII exchange applications on their systems.
At 808, the method 800 may include returning a risk score to a destination device based on the comparison. In certain embodiments, the results from the comparisons (whether from the local PII database or from the compromised companies) may be aggregated and analyzed to determine the risk score. In certain embodiments, the risk score may be based on a variety of data, including data about the breach event, data about the field that was matched (i.e., date of birth versus social security number), data about the frequency of the match (i.e., has this data been matched previously), data about other recent matches, and so on. Based on the data, a risk score may be calculated that can reflect the probability that a particular piece of consumer data may be misused. The information may be provided to the requesting company or individual, and the information may be used to make informed decisions with respect to credit applications and other decisions.
At 904, the method 900 includes determining if there are any matches. If not, the method 900 includes determining a low risk score based on the data, at 906. If there is a match at 904, the method 900 advances to 910 to determine information about each breach based on the match data. The method 900 may further include determining a risk score based on the information about each breach.
In certain embodiments, a piece of data may begin with a predetermined score, and each match may cause the system to deduct from the score. The deductions for each match may vary based on the severity of the breach that resulted in the data becoming compromised.
In certain embodiments, the deduction may be based on a received risk score, such that subsequent fraud events detected by one or more of the data sources may cause the risk score from that particular data source to be escalated. The received risk score may then be subtracted from the predetermined risk score to produce an aggregated score for that data item. In certain embodiments, reported fraud data, information about the data, and information about the breach may be used to develop a probabilistic score that can rank order the risk associated with a consumer and a certain event, which score may be used to assess risk with respect to a particular piece of data.
Once the risk score is determined (at 906 or 912), the method 900 may include returning the risk score for each data item to a destination device. In some embodiments, the risk score may represent a statistical likelihood that the data item has been compromised and may be (or have been) misused.
In some embodiments, the data returned may include a risk assessment score based on the results of the comparison. For example, if the data corresponds to PII data that has previously been identified in a fraudulent transaction, or that the compromised entity data breach is actively being used in fraudulent ways, the risk assessment score may be high. In another example, if the data results correspond to a low-risk event (such as a lost laptop computer) or an older event with no known harm, the risk assessment score may be lower. Each compromised PII data source may have different data points from which to determine a risk score. The resulting risk score data that is received by the data exchange may be aggregated to determine a composite risk score for each data item, and the composite score may be sent to the destination device.
In conjunction with the systems, methods and devices described above with respect to
In another embodiment, one or more compromised companies may host their data locally. Further, the compromised companies may use a PII exchange application configured to communicate with the PII exchange system to receive PII data, compare the PII data to the locally stored data, and return data corresponding to the match to the PII exchange system. The PII exchange system may aggregate the results from each comparison with other results and may determine a risk score based on the aggregated data. Other embodiments are also possible.
The processes, machines, and manufactures (and improvements thereof) described herein are particularly useful improvements for companies and systems that utilize PII data. Further, the embodiments and examples herein provide improvements in the technology of data security and computer-based decision systems. In addition, embodiments and examples herein provide improvements to the functioning of a computer by providing a secure PII exchange system that allows at-risk companies and consumers to determine the risk associated with particular PII data, thereby creating a specific purpose computer by adding such technology. Thus, the improvements herein provide for technical advantages, such as providing a system through which a compromised company (a company that has exposed PII data either inadvertently or through a hack or other data breach event) may share access to its exposed data in a form that cannot be misappropriated. For example, the systems and processes described herein can be particularly useful to any company offering services (including financial services) or that maintains customer information, including those that maintain customer accounts that could be compromised based on data acquired from a data exposure event. Further, the improvements herein provide additional technical advantages, such as providing a system in which the PII data is disassociated, and each field of the PII data is separately encrypted using a different encryption key, providing a secure data store of unlinked data elements such that a single PII data record cannot be re-assembled from the disassociated data. Further, the encrypted and disassociated data can be searched using similarly encrypted and disassociated data to identify potential matches, which matches may indicate a possible risk due to the exposure of the data. While technical fields, descriptions, improvements, and advantages are discussed herein, these are not exhaustive and the embodiments and examples provided herein can apply to other technical fields, can provide further technical advantages, can provide for improvements to other technologies, and can provide other benefits to technology. Further, each of the embodiments and examples may include any one or more improvements, benefits and advantages presented herein.
The illustrations, examples, and embodiments described herein are intended to provide a general understanding of the structure of various embodiments. The illustrations are not intended to serve as a complete description of all of the elements and features of apparatus and systems that utilize the structures or methods described herein. Many other embodiments may be apparent to those of skill in the art upon reviewing the disclosure. Other embodiments may be utilized and derived from the disclosure, such that structural and logical substitutions and changes may be made without departing from the scope of the disclosure. For example, in the flow diagrams presented herein, in certain embodiments, blocks may be removed or combined without departing from the scope of the disclosure. Further, structural and functional elements within the diagram may be combined, in certain embodiments, without departing from the scope of the disclosure. Moreover, although specific embodiments have been illustrated and described herein, it should be appreciated that any subsequent arrangement designed to achieve the same or similar purpose may be substituted for the specific embodiments shown.
This disclosure is intended to cover any and all subsequent adaptations or variations of various embodiments. Combinations of the examples, and other embodiments not specifically described herein, will be apparent to those of skill in the art upon reviewing the description. Additionally, the illustrations are merely representational and may not be drawn to scale. Certain proportions within the illustrations may be exaggerated, while other proportions may be reduced. Accordingly, the disclosure and the figures are to be regarded as illustrative and not restrictive.
