US 8,359,278 B2Grant
Identity protection
Issue Date:2013-01-22
•11 Claims
•31 Drawing Sheets
Abstract
In general, in one aspect, the invention relates to a system for providing identity protection that, in one embodiment, includes a fraud model for specifying patterns of events indicative of identity fraud and a business rules subsystem used to identify fraud that is specified by the fraud models. The system aggregates data from a variety of sources, and has an analytical engine that operates on the aggregated data and determines, using the business rules, whether there are events that are correlative with the fraud models that are indicative of fraud.
Metadata
Assignee
- IndentityTruth, Inc.
Inventors
- Steven D. Domenikos
- Stamatis Astras
- Iris Seri
Application Information
Application Number:US 11/846,305
Filing Date:2007-08-28
Priority Date:2006-10-25
Art Unit:3629
Classifications
IPC:
G06Q99/00
Patent Drawings (31 sheets)
Description
Cross-Reference to Related Application
[0001] This application claims priority to and the benefit of, and incorporates herein by reference in its entirety, U.S. Provisional Patent Application No. 60/854,237, which was filed on Oct. 25, 2006.
Technical Field
[0002] The invention generally relates to systems and methods for protecting people from identity theft. More particularly, the invention relates to systems and methods for detecting identity theft by analyzing data from various sources.
Background
[0003] In today's society, people generally do not know where their private and privileged information may be used, by whom, and for what purpose. This gap in “identity awareness” gives rise to identity theft, which is growing at epidemic proportions.
[0004] The concept of identity is not restricted to only persons, but applies also to devices, applications, and physical assets that comprise additional identities to manage and protect in an increasingly networked, interconnected and always-on world.
Summary of the Invention
[0005] There is a need for a solution that delivers greater awareness about personal and sensitive information that may be misused to help reduce risk and better secure individuals' identities. For example, individuals would like to know whether their personal data has been breached (i.e., leaked) without their knowledge, whether their data has been exposed (e.g., traded, exchanged, or bartered), and whether their identity has been misused or compromised in some way. Further, individuals would like to know whether their personal information is properly represented in public records databases.
[0006] In general, various aspects of the systems and methods described herein provide solutions that deliver greater awareness about sensitive personal information that may be misused, thereby helping to reduce risk and better secure identities. This information may include business and financial account numbers, social security numbers, medical insurance numbers, credit card information, driver's license numbers, and any other identifying and/or sensitive personal information.
[0007] Identity fraud occurs when someone uses such sensitive personal information, possibly along with other identifying information, without permission to commit fraud or other crimes. The solution described herein addresses the problem of identity fraud, in part by considering that a person's identity is not just about data. Compromise of an individual's private data is a prelude to attacking the individual's assets such as accounts, refunds, credit capability, property, etc. To provide an effective solution, an identity model takes into consideration not only private data but also looks at movement of assets linked to that data. For example, it may be possible to monitor the traffic of personal sensitive data to determine whether it is available on the Internet, or has been traded or misused in other ways. Understanding the “traffic” of identity data is useful in understanding behavior and the ability to gain a much greater level of awareness.
[0008] Movement of sensitive data may then be associated with possible movement of personal assets. This approach enables determination of probable misuses, both within and outside the credit system, and delivers the earliest possible notification in advance of identity misuses, potentially before they result in a large scale fraud accompanied by high cost and extensive recovery time.
[0009] In various embodiments, solutions may provide answers to the following questions:
[0010] (1) Has an individual's data been breached with knowledge of the individual and/or the keeper of the data?
[0011] (2) Has an individual's sensitive personal data been detected as available, traded, or misused?
[0012] (3) Has an individual's identity been misused in any way?
[0013] (4) How relevant is a given individual's identity compromise to risk exposure?
[0014] In some implementations, a solution may be delivered as an automated service to bridge the gap in awareness by delivering time-sensitive information on a regular basis to reduce risk and help people to better secure their identities. Solutions also may be delivered “on-demand” to allow a user or a business to periodically check the state of an individual's identity compromise.
[0015] In general, in one aspect, the invention features a method for specifying an individual's risk of identity theft. The method includes determining a likelihood of identity theft of an individual's assets, specifying a risk of identify theft as a numerical measure of the determined likelihood of identity theft compared to other individuals, and storing the numerical measure as an identity theft risk indicator for that individual. In one embodiment of this aspect of the invention, determining the likelihood of identity theft includes identifying credit-related assets for the individual, determining a value of the credit-related assets that an identity thief could attack, determining a likelihood that an identity thief would attack the identified credit-related assets, and determining demographic information of the individual.
[0016] In general, in another aspect, the invention features a method for specifying an individual's risk of identity theft. The method includes identifying credit-related assets for an individual, determining a value for the credit-related assets that an identity thief could attack, determining the likelihood that an identity thief would attack the identified credit-related assets, and determining demographic information of the individual. In addition, the method includes specifying the risk of identity theft as a risk indicia in response to the determined value, the determined likelihood, and the demographic information, and communicating the risk indicia to the individual.
[0017] In general, in yet another aspect, the invention features a system for providing identity fraud risk indicia. The system includes a fraud model subsystem for specifying patterns of events indicative of identity fraud and a business rules subsystem that, based on the fraud model, specifies rules to identify fraud. The system also includes a data aggregation subsystem that collects data input from a variety of sources. These data sources include demographic data and asset data for individuals, event occurrence data, identity theft statistical data, and personal data. The system also includes an analytical engine for processing the data aggregated by the data aggregation subsystem to provide a numerical measure of identity theft risk associated with an individual. In one embodiment of this aspect of the invention, the analytical engine determines a likelihood of identity theft by evaluating the individual's credit-related assets, the value of the credit-related assets that an identity thief could attack, a likelihood that an identity thief would attack the identified credit-related assets, and the demographic information of the individual. The analytical engine may also provide a prediction of fraud events that are likely to occur, which may include a probability that such fraud events are likely to occur, and recommendations of steps to be taken to avoid the predicted fraud events.
[0018] Various embodiments of these three aspects of the invention include the following features, or implement system components for achieving the following features. The numerical measure or risk indicia may be an identity health score and may be higher for increased risk and lower for decreased risk, or vice versa. The likelihood of identity theft or the identity theft risk measure may be determined at least in part by the occurrence of a particular event with respect to an individual, for example a change or addition to the individual's personal or credit data or a data breach report from an organization. In some embodiments, the likelihood of identity theft or the measure of identity theft risk is determined at least in part by comparing a fraud model with the event that occurred.
[0019] These methods may also include, and the systems may also implement components for, identifying fraud events that are likely to occur, communicating to the individual those fraud events, and providing advice to the individual on steps to take that are relevant to the fraud detected or predicted. The fraud events may be compared to fraud scenarios, and rulesets may be used to evaluate events that have occurred. In addition, the numerical measure or risk indicia may be communicated to the individual or to a financial organization, and the individual may be alerted to a change in the numerical measure or risk indicia over time. The occurrence of identity theft for individuals with a demographic profile may also be determined.
[0020] In general, in still another aspect, the invention features a method for evaluating an individual's risk of identity theft. The method includes facilitating communication by an individual of data, determining a numerical measure of the likelihood of identity theft compared to other individuals in response to the communicated data, and communicating the numerical measure to the individual. The data communicated by the individual may include a zip code, a birth year, and a home purchase year.
[0021] In various embodiments of this aspect of the invention a communication of additional information regarding the individual is facilitated for further analysis. An indicator may be provided to indicate the usefulness of the additional information, the confidence in the numerical measure in response to the amount of data provided by the individual, and/or that more information is needed to provide the numerical measure to a high degree of confidence. The method may also include providing a display communicating the numerical measure and facilitating subscription to identify fraud monitoring and/or prediction services. Facilitating the subscription may include asking the individual about the individual's relationship to fraud-related events. Furthermore, identity fraud event information may be provided on the display, and a link to a list of events related to identity fraud may also be provided.
[0022] In general, in a further aspect, the invention features a method for providing a user interface to assist an individual in evaluating the individual's risk of identity theft. The method includes providing a summary of recent detected events relevant to the individual's risk of identity theft, providing a numeric representation of the risk, along with a descriptive label regarding the numeric representation, and providing a depiction of relevant fraud models.
[0023] In various embodiments of this aspect of the invention the numerical representation includes an identity health score. The numerical representation may be higher for increased risk and lower for decreased risk, or vice versa. In some embodiments, providing the numeric representation of risk includes identifying credit-related assets for an individual, determining a value of the credit-related assets that an identity thief could attack, determining a likelihood that the identity thief would attack the identified credit-related assets, and determining demographic information of the individual. Providing the numeric representation of risk may also include considering the occurrence of a particular event with respect to the individual, such as a change or addition to the individual's personal or credit data or a data breach report from an organization. The fraud models may each include a fraud scenario, and the method may further include communicating to the individual fraud events that are likely to occur.
[0024] In general, in yet another aspect, the invention features a method for providing a user interface to assist an individual in evaluating the individual's risk of identity theft. The method includes displaying a time-series graph depicting known breaches that have occurred throughout the population, displaying on the time-series graph a depiction of events relevant to the individual's risk of identity theft, facilitating input by the individual of confirmation that the events are relevant to the individual's risk of identity theft, facilitating indication by the individual that certain displayed breaches are relevant to the individual, and storing the input from the individual for use in evaluating the individual's risk of identity theft.
[0025] In various embodiments of this aspect of the invention an event is relevant to the individual's risk of identity theft if the individual is directly or indirectly affected by the event. The input may be facilitated by asking the individual whether the individual has a personal connection to the event. The indication may be facilitated by asking the individual whether the individual has an account or data with an entity that has been breached.
Brief Description of the Drawings
[0026] The foregoing and other objects, aspects, features, and advantages of the invention will become more apparent and may be better understood by referring to the following description, taken in conjunction with the accompanying drawings, in which:
[0027] FIG. 1 is a block diagram of an exemplary embodiment of a system in accordance with the invention;
[0028] FIG. 2 is a demonstrative example table listing data sources in one embodiment in accordance with the invention;
[0029] FIG. 3 is a demonstrative example of event and fraud scenarios in one embodiment in accordance with the invention;
[0030] FIG. 4 is an exemplary depiction of a structure of user's data in one embodiment in accordance with the invention;
[0031] FIG. 5 is a graphic depiction of data analysis in one embodiment in accordance with the invention;
[0032] FIG. 6 is a graphic depiction of data analysis in one embodiment in accordance with the invention;
[0033] FIG. 7 is a block diagram of an exemplary embodiment of a system in accordance with the invention;
[0034] FIG. 8 is an exemplary screen display in one embodiment in accordance with the invention;
[0035] FIG. 9 an exemplary screen display in one embodiment in accordance with the invention;
[0036] FIG. 10 is an exemplary screen display in one embodiment in accordance with the invention;
[0037] FIG. 11 is an exemplary screen display in one embodiment in accordance with the invention;
[0038] FIG. 12 an exemplary screen display in one embodiment in accordance with the invention;
[0039] FIG. 13 an exemplary screen display in one embodiment in accordance with the invention;
[0040] FIG. 14 is a block diagram of an exemplary embodiment of a system in accordance with the invention;
[0041] FIG. 15 is a block diagram of high-level architecture for an embodiment in accordance with the invention.
[0042] FIG. 16A and FIG. 16B depict exemplary workflows in an embodiment in accordance with the invention;
[0043] FIG. 17 is an exemplary home page of an embodiment in accordance with the invention;
[0044] FIG. 18 is an exemplary registration screen of an embodiment in accordance with the invention;
[0045] FIG. 19 is an exemplary personal information page of an embodiment in accordance with the invention;
[0046] FIG. 20 is an exemplary preferences page of an embodiment in accordance with the invention;
[0047] FIG. 21 is an exemplary payment page of an embodiment in accordance with the invention;
[0048] FIG. 22 is an exemplary start page for a free trial subscription according to an embodiment of the invention;
[0049] FIG. 23 is an exemplary dashboard according to an embodiment of the invention;
[0050] FIG. 24 is an exemplary “my identity” screen according to an embodiment of the invention;
[0051] FIG. 25 and FIG. 26 are exemplary events display screens according to an embodiment of the invention;
[0052] FIG. 27 is an exemplary “events vs. breaches” screen according to an embodiment of the invention;
[0053] FIG. 28 is an exemplary breaches list display according to an embodiment of the invention;
[0054] FIG. 29 is an exemplary identity theft risk distribution screen according to an embodiment of the invention; and
[0055] FIG. 30 is an exemplary certainty level display according to an embodiment of the invention.
Description
[0056] Referring to FIG. 1 , an exemplary, demonstrative embodiment 100 makes use of a modular architecture. The system 100 includes fraud models 110, which characterize events that reflect identity misuse scenarios. Business rules 120 specify actions to be taken for identification of patterns indicated by the fraud models 110.
[0057] Data is aggregated from a number of different sources for analysis. In one embodiment, public and private data sources provide a view into an individual's identity and asset movement. These sources may include data sources publicly available on the Internet or otherwise, and data vendors. In some embodiments, it is useful to detect activity that would not typically appear on a credit report, and might therefore go undetected for a long time. A data aggregation engine 130 receives data from multiple sources, applies relevancy scores, classifies them in the appropriate categories, and stores them in a data repository for further processing. New data sources may be added as they become available, to continuously improve the effectiveness of the service.
[0058] Referring briefly to FIG. 2 , a few demonstrative examples of data that may be used includes data from “Internet Observation Co.” 200, an exemplary wholesale broker, that observes internet activity to determine whether any user's sensitive personal data (e.g., social security numbers, credit card numbers, bank accounts, ATM accounts, and so on) are “floating,” that is, have been publicly communicated or made available over the Internet or have otherwise been traded or misused. The broker may employ search engines and other types of monitoring to identify floating data. Another data wholesale company, “Data Co.,” 201 may provide indications about whether a user's public data is being changed. This public data may be available to Data Co. from general public records. Likewise, other data wholesalers, such as “Public Records Co.,” 202 may provide information about whether records have been changed. Examples of other data wholesalers 202 who provide commercially available information include TracersInfo, MerlinData, Lexus/Nexus, Thomson-West, MelissaData, LocatePlus, Experian, TransUnion, ChexSystems, Equifax, DataQuick, and InfoUSA, among others. These wholesalers 202 may provide, for example, phone and post office records, government automobile registration and driver's license records, and so on. Telephone companies, such as “RBOCs,” 203 may provide telephone business records. These records may indicate whether there are any suspicious telephone connections or disconnections associated with a user. News sources 204 may provide information about identity fraud incidents or events. For example, there may be information about a security breach at a particular financial institution or web site. Announcement of such a breach, for example, may allow the system 100 to alert the user, or inquire as to whether the user uses such financial institution or web site, if the information is not already known to the system 100.
[0059] Government agencies, such as the post office 205 in this example, may provide information about address changes. A change of address request may be indicative of a problem, for example, when combined with other events. Like the news sources 204, private organizations that fight identity theft 206, sometimes referred to as anti-phishing organizations, and government organizations 207 that share the same objective, such as the Federal Trade Commission, may publish information about fraud and identity theft incidents, including the originating sources and types of attacks. This information may be used in developing fraud models 110 and business rules 120, and also may be events that may be correlated with other information. For example, this information may be correlated with demographic data to identify risk profiles.
[0060] Credit bureaus 208 may provide indication of new financial records being established. Details about a new record, for example, that it is associated with a different name but same social security number, or same name but different address, may be indicative of compromise. Likewise, utility company records 209 may indicate that an account has been opened for a user in an unexpected place. Again, each of these different types of information may be interesting of themselves, but when correlated with other data as described in a fraud model 110, may be useful in the aggregate to identify that identity theft has occurred and/or to analyze the risk that it will occur.
[0061] Referring again to FIG. 1 , a predictive analytical engine 150 uses the fraud models 110 and business rules 120 to correlate data, identify events in the data, and determine actions to be taken. The analytical engine 150 is responsible for analyzing the independent and highly diverse data sources. Each data source provides useful information, and the analytical engine 150 may associate and connect independent events together, creating another layer of data that may be used by the analytical engine 150 to detect fraud activities that to date may have been undetected. The raw data from the sources and the correlated data produced by the analytical engine may be stored in a secure data warehouse 140.
[0062] The results may be provided to end users in various communications, including ongoing monitoring and on-time reporting. Reports 160 may be generated for businesses that relate to the entity and/or customers of the entity, or for individuals.
[0063] The system 100 takes an approach of solving an event management problem in some ways analogous to that of network event management. Detecting signatures of identity misuse or potential identity exposure requires careful balancing between eliminating false negatives and limiting the number of false positives, while minimizing overlook.
[0064] Fraud models 110 help eliminate false positive notifications while reducing the likelihood of false negatives, just as, for example, detection of computer network intrusion. Each identity event may be analyzed, for example, to determine whether it is indicative of a positive or negative, in light of other events.
[0065] Referring briefly to FIG. 3 , various fraud scenarios may be evidenced by a combination of events. For example, the registering of a new telephone number 300, the creation of a new account (COA) 310, the reporting of social security number (SSN) exposure 320, the taking out of a new loan 330 and/or a loan discharge 340, and the purchase and/or borrowing against new equity assets 350 may be events that are evidence of identity compromise. These events may take place near each other in time or they make take place over a period of time. SSN exposure 320 followed by the creation of a new account 310, for example, may be stronger evidence of near term exposure than creation of a new account 310 long before the SSN exposure 320. The variations of the scenarios, with respect to timing, for example, or activity, as another example, may be described in the fraud models 110. Persistent analysis of new methods of fraud may be used to develop new fraud models 110 so that the fraud models 110 are kept up to date. Likewise, algorithms and business rules 120 may be continuously expanded to accommodate for new fraud permutations.
[0066] Referring again to FIG. 1 , in one embodiment, a layer of metadata (not shown) based on temporal analysis and feedback from end-users may be provided back into the engine 150 to help refine the signature detections. This metadata and a relevancy scoring system, built from individual events in comparison with the frequency of occurrence in the related population, and the individual's past history with personal feedback help prevent false positives.
[0067] Thus, the system 100 may make use of a combination of event capturing, event processing techniques, powerful predictive algorithms, and a sophisticated software engine that incorporates domain expertise in the form of the identity fraud models 110. Further, similar events and their attributes may be analyzed in aggregate in order to ascertain whether a feature vector of certain attribute values is representative of increased likelihood of fraud for that event. This may allow the system 100 to discriminate between events generated by data entry errors versus those that are generated by true fraud.
[0068] Referring to FIG. 4 , in one embodiment, the analytical engine 150 begins its work by examining the static structure of a subject's most recent data as it relates to the subject's underlying assets. As shown in the example, a loan (e.g., Loan #1 400) may be associated with an End User 410 and also with an address (e.g., Address #2 420). This examination may allow for generating scores and classifications that give a preliminary identity picture of the subject and flags any deviations from a typical identity profile.
[0069] Embodiments of the system have been developed with the understanding that compromising someone's personal data may be a prelude to compromising that person's assets. As such, the concept of identity is expanded to include the assets that may be associated with the specific data set. Thus, a graph of this data may be analyzed and compared with fraud models. Generally, this identity-asset data model is not static; its content, structure, and data relationship change as more data about the subject is gathered through monitoring.
[0070] For example, an individual may change his or her primary address, phone and other personal identities, or add new ones. The data model reflects identity transition (or addition), rather than discarding the old data. The fraud model 110 may refer to that “old” data in some identity theft scenarios. In some embodiments, the identity-asset data model is easily extendable, as new asset types and personal identities may be added to it without changing the analytical engine 150.
[0071] Referring to FIG. 5 , in some embodiments, after examining the static structure, or “graph” of data inter-connectivity, the system 100 may go beyond graph theory analysis, by correlating interconnectivity of data with events that have changed the asset/data structure in the past and the events that have most recently affected it. Each event 501, 502, 503, 504 may be scored with a matrix of values that interconnect the event to other events as shown in FIG. 5 . The resulting matrices may then be analyzed.
[0072] Referring to FIG. 6 , the events and their scoring matrices and the static structure scores 600 may be processed by the analytical engine 150, where the matrices and static structure scores are mathematically combined and arranged 610 into a series of “nodes” 620 as shown. The output of this nodal network produces meaningful results and relevant alert triggers while reducing non-relevant noise triggers.
[0073] Referring to FIG. 7 , in one exemplary embodiment, core processing takes place within a server that is hosted in a secure environment 700. Business users 705 monitoring their constituencies, or end-users 710 concerned about their own identities, may make use of services provided through one or more web portals 715, 720. This allows services to be provided without requiring deployment of either server software or client software. Use via a standard web browser with no install footprint reduces IT rollout challenges, minimizing the time to implement and to deploy the service.
[0074] The web portals 715, 720 provide user login and authentication for both the individual end-user 710 and the business user 705. Each business customer 725 may have several individuals 705 within their organization that need to login to the site to perform various different management tasks. In addition, the business 725 may be using the services on behalf of tens of thousands of end-users 710, who may also need to login to the portal 720 to manage their own individual parameters.
[0075] The portals 715, 720 may support a variety of user roles, each able to perform different administrative tasks. This is useful because the nature of the data being monitored and the ensuing results are highly sensitive and should only be viewed by the appropriate individuals.
[0076] In one embodiment, after logging in to the web portal 715, business users 705 will see a dashboard containing information that is important to them. For example, the dashboard may include high level summaries for lists of users that are being monitored, and the ability to drill down to lists of compromised consumers, and further information regarding lists of fraudulent events for a compromised user, as well as reports and graphs displaying important snapshot and time series data in a useful format.
[0077] As part of business account management, business users 705 may configure the server to send notification reports via email. These reports may be sent based on notification configuration settings including periodicity, an urgent notification threshold, etc., and may include information regarding the health of monitoring consumers similar to the information the business users 705 can see on the web portal dashboard.
[0078] A business 725 may differentiate service levels between each of their user/customer classes. They may choose to provide deeper data checks against more data sources and do this more frequently for their premium customers than their standard or economy class customers. User monitor sets allow a business 725 to carve their customer base up in any way they choose and independently attach frequency and data source parameters to each set.
[0079] Businesses 725 that have suffered one or more data breaches may create a different user monitor set for each breach, whereas each set contains just the records that were part of that breach. This allows the business 725 to better track organized use of the breached data and assess the causality between fraud on the consumer and the business data breach.
[0080] At the option of business customers 725, end-users 710 may receive direct notification for fraud alerts, suspicious activities, and regular reports on a periodic basis. These communications may be customized and co-branded or be private labeled by the business customer 725. The end-user 710 may also receive, at the business' discretion, an account to login to a site to view status and information on their history of suspicious activity and data breaches. The end-user 710 access to a web site may be private labeled or co-branded.
[0081] In some embodiments, the data collected about individual identities may include non-public and personally identifiable information. As such, security is an important factor in the design and deployment. In one embodiment, a data warehouse 730 is maintained in a physically secure hosting facility, following security practices for physical and electronic access. All non-public personal information is encrypted with advanced encryption algorithms when stored in a database or transmitted between systems. Full unencumbered non-public personal information is not available to any user through the application user interface, only the last four digits or some similar partially identifiable sub-portion. Databases may be locked down and physical and electronic access fully audited. All backups may be performed with encryption and stored offsite in a professional and highly secure data archival center.
[0082] In one embodiment, the system is built upon industry-proven technology platforms. Using Java as the foundation, there are many available components, both open source and licensable, available to help build the system. Leveraging these components drives down time to market and development cost, improves maintainability, and produces more reliable systems because much of the code has already been tested in production environments.
[0083] In some embodiments, an internet service that is marketed and sold directly to end-users combines proactive monitoring of both personal identity information as well as credit data. The service has comprehensive data sources, proactive data analysis/reporting that may alert customers to compromised identities before malicious damage occurs, and an overall user experience and ease of use. The service provides a variety of subscription options for customers with varying levels of reporting data available with each option. For example, some reports may not be available on certain plans or the completeness of the report may be increased based on the plan selected. Additionally, in some embodiments, there may be one-time service offers including a social security number security report, one time full credit report, or more services in a snapshot one time offering instead of an ongoing subscription. A variety of subscription plans allow users to select the information delivery that they prefer.
[0084] In some embodiments, customers may be able to perform most activities in a self-service function (e.g., create account, select subscription plan, upgrade subscription plan, change account details, view reporting data).
[0085] In one embodiment, the service lets users know if their private or sensitive identity data is exposed or available on the Internet. The service may inform users if their identity is misused, if there are new legal and/or financial records detected, and may provide information about the risk of becoming a victim of identity theft. In some embodiments, the service provides a measure of identity theft risk for a particular individual. The service may track events in time and construct the progress of various events as they relate to a specific identity and visibly display it. The service provides reporting output to a user in a manner that is clearly understood in the context of their identity security and provides a proactive means of response should an actual and/or potential theft instance be discovered.
[0086] In some embodiments, the service may aggregate personal data about individuals even when there is not a common key. In some embodiments, the service requests additional information from a user as necessary to associate records with an individual.
[0087] In some embodiments, the consumer service employs a three tier architecture consisting of presentation, transaction/business logic and data layers. Security concerns, as well as secure eCommerce best practices, dictate SSL access to the web application, as well as separation of the presentation and transaction engines with firewalled DMZs.
[0088] Examples of components that may be used in some embodiments include LifeRay, an open source Java Portal Server that meets the JSR 168 Portlet Specification, improves user experience and cuts development time by providing a flexible GUI framework and widely available pre-tested UI widgets. Spring is an application framework that makes development agile and improves testability and scalability of the entire application. Hibernate provides a data persistence layer that cuts development time and improves performance, making seamless integration with the variety of DBMSs. MySQL provides a database layer that keeps deployment and development costs down and supports high performance and scalability. BIRT provides an open source reporting system that consists of Report Designed and run-time Report Engine 735. Apache Service Mix provides an open source distributed Enterprise Service Bus (ESB) 740 and Service Oriented Architecture (SOA) toolkit that allows for easy and standardized integration with the data sources and other external systems. It should be understood that these components are described by way of example, and that there are many available alternatives to these components.
[0089] The combination of a powerful robust platform, third party solid components, and the described data and analytics may be used in a powerful and effective application that can detect fraud and abuse of an individual's personal data and related assets.
[0090] Referring to FIG. 8 , an exemplary screen display 800 demonstrates that identity awareness solutions 810 may be provided in a subscription service 820, in which a continuous view of a user's identity state may be provided. Identity awareness solutions 810 also may be provided as a one-time, on demand service 830 to check the state of an identity of an individual. In some embodiments, the state of a user's identity is referred to as the identity “health” of the individual. A user is healthy if risk is low, and increasingly unhealthy as risk increases and/or actual fraud occurs.
[0091] Referring to FIG. 9 , an exemplary, demonstrative system interface 900 provides a user with information about the state of their identity. The interface provides a chart 910 that presents the aggregated identity health of a population, in this example, the United States population, and also shows the state of the individual against the overall population. Here, the display shows that the individual is on the riskier side of the high curve, but still not into the tail on the right side of the graph.
[0092] Also shown on the display 900 is a list of events 920 that have been identified by the system 100. The events 920 include the compromise of a social security number 930, the opening of a new mobile telephone account at the same address 940, the opening of a new utility account at the same address 950, and a work address registered 500 miles away from the home address 960. The first event, the compromise of the social security number 930, when correlated with the other events 940, 950, 960 may be indicative of fraud. In some embodiments, event severity may be determined by the fraud models 110 with weights assigned to each event.
[0093] In this display, each event circle (“bubble”) when selected may provide more detailed information about the event. In some embodiments, each bubble has a different icon, color, or size depending on the nature and importance of the event.
[0094] In some embodiments, the user may be asked to confirm or deny a specific event.
[0095] Referring to FIG. 10 , in another demonstrative screen display 1000, information is provided to a user that includes personal identification information of the user 1010, including the credit cards 1020 known to belong to the user. The display 1000 includes a list of assets monitored 1030, which in this example indicates that one of the cards has been breached in the last 60 days.
[0096] Notifications are provided to the user, indicating 1040 that events have been identified. These include that the user's social security number was found to have been compromised 1041, that there is a new application for credit 1042, and there is a change of address 1043.
[0097] There is also a display 1050 of a user's relative risk as compared to the general population. The display shows that over the past year, the user's risk has increased significantly. The events also are displayed 1060 by severity over time, to show both the event history and how important the events are.
[0098] Fraud patterns detected are displayed 1070, indicating to the user the type of fraud pattern, and any predicted timing, based on the events and fraud models. In this example, real estate fraud is the most probable detected pattern, with three confirmed events in the model. The suggestion displayed is to watch for unauthorized mortgage activity.
[0099] A display also provides recommendations 1080 to the user about how they may address the problems identified. In this example, information about an identity theft hotline is provided.
[0100] Referring to FIG. 11 , in one embodiment, a system is provided to inform a user of the user's identity theft risk, based on demographics 1100. The system presents the user with a map of a geographic area 1110, in this case, the United States. The user may select a location within the geographic area, for example by clicking on the selected geographic area with his mouse or by providing a zip code to focus the graph on a particular location. Referring to FIG. 12 , the user is also asked when they purchased their house 1210, and their year of birth 1220. Based on the geography, length of time in their house, and their age, the system may determine the risk of identity theft as compared to the general population. It should be understood that this demographic data is demonstrative, and that other demographic data may be used instead or in addition to what is described here.
[0101] Referring to FIG. 13 , the user is presented with a risk score 1310—an evaluation of risk based on this demographic information. This score is determined using reported events of the general population for each demographic group. This information may then be provided to the user. In one embodiment, this information is provided to a user prior to the user subscribing to a service, as a way for the user to assess their need for an identity protection service.
[0102] Referring to FIG. 14 , in one embodiment, a server 1400 for providing the services described here includes a fraud model subsystem 1405 for specifying patterns of events indicative of identity fraud. The subsystem 1405 may include fraud models provided by users, generated by experts, or by some other way. The server 1400 also includes a business rules subsystem 1410, which, based on the fraud models is used to identity fraud that is specified by the fraud models. The server 1400 also includes a data aggregation subsystem 1415, which collects data input 1430 from a variety of sources such that it may be processed. The sources may be the data source described. The analytical engine 1420 operates on the data collected by the data aggregation subsystem 1415, and determines whether there are events that are correlative with the fraud models based on the business rules. Events are analyzed and stored in an output data store 1425, such as a data warehouse.
[0103] Predictive Analytical Engine 150, 1420
[0104] In some embodiments, the Predictive Analytical Engine 150, 1420 may be designed to produce meaningful reports about a user's identity including a prediction of likely fraudulent events to watch out for given events that have already happened. The engine 150, 1420 may include logic to notify the user of important events and provide the appropriate level of urgency depending on the event discovered. The design may be implemented in a manner to minimize false positives, e.g., classifying a benign or valid event as fraudulent and alarming the user unnecessarily, and also to minimize false negatives, e.g., classifying a fraudulent or potentially fraudulent event as benign or valid.
[0105] For example, in some implementations, events received by the system 100 may be assigned a score based on the likelihood each given event is fraudulent activity or contributes to an overall pattern of fraudulent activity. Using this score, the system 100 may classify into these categories: routine, fraudulent, or uncertain. The system 100 may been trained in such a way that it can usually place events with near certainty in either the routine or fraudulent classes.
[0106] The “uncertain” category is used for those cases in which the system 100 may not have and/or cannot obtain complete information concerning an event. As a result, the event score may not allow the system 100 to definitely place an event into either a routine or fraudulent category. Such “gray area” events may be placed in an uncertain category for manual adjudication. There may be degrees to this indecision. The system 100 may allow specification of how sure it must be before placing the event into either one category or the other. In one embodiment, by default, the system 100 may be 100 times more certain that an event may be classified one way rather than another. In order to minimize “false positives” (the inappropriate classifications of innocent, routine events as identity theft) and “false negatives” (the inappropriate classifications of identity fraud events as routine or innocent), the certainty threshold may be increased to 1,000, 10,000 or more.
[0107] The system 100 may be adaptive and learn from its history. In the interest of transparency, all events captured concerning a particular subscriber account may be available for review by the subscriber, along with the classification of the events into the routine, fraudulent, or uncertain categories. Subscribers may (and, in fact, may be encouraged to) provide feedback on the classification via questionnaires within the portal. Input from the subscriber may enable the system 100 to retrain its adaptive certainty threshold so as to minimize inappropriate classification of future events, while also maximizing detection of events.
[0108] Data Fraud Models 110, 1405
[0109] In some embodiments, the system 100 has the dynamic capability to add new fraud models 110 and new business rules 120 on a continuous basis. The analytical engine 150, 1420 may take into consideration the fuzzy nature of the problem. For example, this typically would not be a pattern matching based approach, but rather a comparison of events' attributes to a feature vector that has been determined to represent fraud.
[0110] It should be understood that each of these subsystems may be implemented by software modules or special-purpose hardware, or in any other suitable fashion, and, if software, that they all may be implemented on the same computer, or may be distributed individually or in groups among different computers. There may be multiple instances of some or each of the subsystems, and they may be operated in any suitable manner.
[0111] In general, in various embodiments, the server 1400 may include software running on a general-purpose computer (e.g., a PC with an INTEL processor or an APPLE MACINTOSH) capable of running such operating systems as the MICROSOFT WINDOWS family of operating systems from Microsoft Corporation of Redmond, Wash., the MACINTOSH OS X operating system from Apple Computer of Cupertino, Calif., and various varieties of Unix, such as SUN SOLARIS from SUN MICROSYSTEMS, and GNU/Linux from RED HAT, INC. of Durham, N.C. (and others). The server 1400 also may be implemented on such hardware as a smart or dumb terminal, network computer, wireless device, wireless telephone, information appliance, workstation, minicomputer, mainframe computer, or other computing device that is operated as a general purpose computer or a special purpose hardware device used for serving the purposes described here.
[0112] High-Level Architecture
[0113] Referring to FIG. 15 , an exemplary high-level architecture 1500 is shown. A transaction server 1550 is responsible for dynamically generating HTML and relaying it to the client browser 1510 via the presentation server 1530. In some embodiments, no caching of data is permitted at the presentation server 1530 for security purposes. An HTTP/HTTPS firewall 1520 is provisioned between the presentation server and the client browser 1510, and no other ports are opened. A firewall 1540 between the presentation server 1530 and the transaction server 1550 is also provisioned, secured by static IP address and socket. To meet this requirement, there may be a DMZ architecture with a firewall 1520 (e.g., Cisco PIX #1) between the Internet and the presentation server 1530. There may also be a firewall 1540 (e.g., Cisco PIX #2) between the presentation server 1530 and the transaction server 1550. Ingress ports may be limited (e.g., to port 80) so that there are a limited number of ingress ports open on the first firewall 1520 (e.g., Cisco PIX #1). A different port or ports (e.g., port 443, port 8000, and/or port 8009, etc.) may be the only ingress port(s) open on the second firewall 1540 (e.g., Cisco PIX #2). Given a Java Tomcat 5.x architecture for the transaction server 1550 (possibly embedded in JBoss), the presentation server 1530 may be an Apache HTTP server running mod_jk which is connected via the port open on the second firewall 1540 (e.g., port 8009) to the Java Tomcat server.
[0114] This exemplary architecture provides for both security and enables additional scalability (e.g. by increasing the number of presentation and/or transaction servers and load balancing access between them)
[0115] The service may support consumers (end-users) and administrators. Consumers have self-service control of their account and service parameters, including account creation, password resets, service plan selection, editing of user data, viewing of their reporting data, and submission of ID theft instances. Administrators may have access to consumer functions as well as additional privileges to change user's service plan, terminate user's account and view aggregate user reporting data.
[0116] Referring to FIG. 16A and FIG. 16B , in some embodiments, the service supports a process flow for unauthenticated users (e.g., guests) 1600, and one for authenticated users 1640. The unauthenticated user flow (FIG. 16A ) may permit unauthenticated users 1600 to browse the services offered 1610 and, if interested, select a service plan and signup 1620, and then begin using the service via the user interface 1630. The authenticated user flow (FIG. 16B ) permits registered users 1640 to log in to the service 1650 to view their identity reporting data 1660, and/or update service preferences.
[0117] User authentication may be important given the nature of the service and the sensitivity of the data handled. At the same time, it may be helpful to minimize the information needed to create a new subscription and delay asking for more sensitive data until necessary. For example, a more stringent authentication process may be needed when a user requests a credit report or when sensitive information is displayed to the user. Strong authentication may be used, such as using the Level 3 authentication process available from Experian and/or other commercially available alternatives. Level 3 authentication involves asking the user “top-of-mind” questions such as range of mortgage payments or make and model of a car owned in the past. A user passing this type of authentication (providing correct answers in a limited amount of time) may be considered the baseline to determine if the user is who they claim to be. A further description of the exemplary subscription and authentication processes is provided below.
[0118] A consumer service home page may serve as the primary vehicle to advertise service plans, educate customers, and serve as a service entry point for both new and existing users. Accordingly, it may serve multiple types of users while also adhering to goals of a consumer service user experience (e.g., simple to use, innovative/high-quality user experience, etc.).
[0119] Referring to FIG. 17 , in some embodiments, when a user first connects to the site, a “home page” 1700 for the service is provided that may include an area 1710 describing the products/services offered. A link may be provided that allows a user to obtain an on-demand look-up of a particular social security number, to see if it is “floating” on-line. There may be no requirement that users have a monthly subscription, but creation of a user account allows collection of payment information and so forth. A link may be provided to a demonstration and information about the service. The home page may also include facts, figures, news and information about identity theft breaches 1720, and an interactive graph 1730 displaying identity theft by geography. A user may provide a zip code 1740 to focus the graph on a particular location. The home page may also provide a place 1750 for existing users to enter username and password information. In some embodiments, the authentication information required from a user may be increased if the user is attempting to log in from a computer that they have not used before. A link to customer support 1760 may be provided.
[0120] Registration
[0121] In some embodiments, to aid user registration, a registration wizard may be used to guide users through the process of creating their account. The overriding goal of employing a wizard-based approach to collect user data is to provide a simple, user-friendly method to collect what may otherwise become an overwhelming amount of data.
[0122] A registration wizard serves to create the customer account and collect payment information as appropriate. Plan-specific information collected from the user may include strong authentication after the registration process is completed. A separation of registration from plan sign-up allows for a consistent registration process and allows for users to register with a site even if they have not made a plan selection, for example, to receive identification theft news, contribute to forums and/or track promotions.
[0123] In some embodiments, a wizard may implement four steps in which data requested of users is compartmentalized into logical groupings:
[0124] Step 1: Login information and security questions (e.g., FIG. 18 )
[0125] Step 2: Name/Personal information (address, date of birth, phone) and ID theft survey (e.g., FIG. 19 )
[0126] Step 3: Notification preferences (email or SMS) (e.g., FIG. 20 )
[0127] Step 4: Payment information (except for Start for Free plans in which case user may be presented with a page to enter the credentials that they want to track) (e.g., FIG. 21 ).
[0128] Referring first to FIG. 18 , a general description of the registration follows. FIG. 18 shows a login screen 1800 in an exemplary embodiment. The initial screen 1800 includes a graphic 1810 indicating that the registration area is secure. There may be a field 1820 for a user to enter his or her email address, which serves as a user ID, and a field 1830 for a user to enter a password. The password may be masked, to avoid viewing by others. There may be a field 1840 in which the user confirms the password (again, this may be masked). The user may be presented with security questions 1850 (e.g., mother's maiden name, name of high school), and a place 1860 to provide an answer to these questions. There may be a display 1870 that is not machine-readable, to confirm that the viewer is human, and not a computer. There may be a user agreement 1880 displayed in a text box. There may be a check box 1890 that the user will check to confirm that he or she agrees with the usage terms. There may be a “next” button 1895 that a user may click to proceed to the next step. If the user does not enter the appropriate information, the user may be returned to this page, with an indicator of the error. When collecting a login id, the user may be prompted for a different one if it duplicates an id already in the system. Rather than refreshing the entire page each time this cycle repeats, it is preferable to have an embedded applet which will provide a more real-time, interactive experience (e.g., AJAX).
[0129] In some embodiments, users may enter the registration wizard either by selecting a plan or by directly registering without making a plan selection. A home page or a products link from the home page presents the available plans with descriptive information for each. Users may select a plan and also confirm acceptance of applicable terms and conditions.
[0130] Referring to FIG. 19 , in an exemplary representation 1900 of step 2 of such a registration process, there may be a graphic 1910 indicating that the registration area is secure. There may be an indication of the step that the user is on as he or she moves through the registration process. The user may be made aware that the quality and accuracy of the service increases with the amount and accuracy of information provided by the end user. There may be an “information strength meter” 1920 at the bottom of the page that indicates to the user the “strength” of the information that the system has for him or her, with the objective of encouraging the user to enter as much information as possible, to maximize the strength. There may be explanatory text 1930 accompanying the meter.
[0131] In one embodiment, the strength displayed by the information strength meter 1920 is reflective of the number and type of fields of information that the user fills out. The strength is generated as the user provides various types of information. Table 1 below provides strength values that may be assigned to different pieces of information provided by the user:
[0132]
| TABLE 1 | ||
|---|---|---|
| INFORMATION STRENGTH VALUES | ||
| Information Field Provided by the User | Strength Value | |
| firstName | 2 | |
| middleName | 3 | |
| lastName | 2 | |
| nameSuffix | 3 | |
| phone | 2 | |
| streetAddress1 | 2 | |
| streetAddress2 | 0 | |
| city | 2 | |
| state | 2 | |
| zip | 2 | |
| moveInMonth | 3 | |
| moveInYear | 3 | |
| birthDay | 3 | |
| birthMonth | 3 | |
| birthYear | 3 | |
| previousStreetAddress1 | 3 | |
| previousStreetAddress2 | 0 | |
| previousCity | 3 | |
| previousState | 3 | |
| previousZip | 3 | |
| ssn | 5 | |
[0133] The total score, or “strength,” may then be placed into a range, from low to high, that is used to select the graphic that displays the information strength meter 1920 on the screen for the user to see. The information strength ranges, in one exemplary embodiment, for the different total strength scores are depicted in Table 2 below:
[0134]
| TABLE 2 | |
|---|---|
| INFORMATION STRENGTH METER RANGES | |
| Total Strength Value | Range |
| 0-4 | low0 |
| 5-9 | low1 |
| 10-19 | low2 |
| 20-29 | medium1 |
| 30-39 | medium2 |
| 40-49 | high1 |
| 50 and higher | high2 |
[0135] There may be a form 1940 with the following fields for capturing the user's personal information: first, middle, last, and suffix of user's name; date of birth; gender (e.g., male or female radio buttons); current address, city, state, and zip; move-in date; previous address, city, state, and zip; phone, and optionally a second phone. Some of this information may be optional and some of the information may be required. As depicted in Table 1 above, this information may be used in determining the strength depicted by the information strength meter 1920.
[0136] There may be questions 1950 that survey the user as to their experience with identity fraud. The questions may include such questions as “have you ever been a victim of identity theft?” The user may see a radio button control 1960 with an option of answering yes or no. If the user selects yes, he/she the user may be presented with a pick list 1970 allowing the user to indicate which type of identity theft they were victims of. Users may select more than one answer. If they select “other”, the user may enter information into an adjacent text field.
[0137] The list 1970 of identity theft problems may include, for example, Social Security Number (SSN)/Financial ID Fraud (with a description of what this fraud is), credit card fraud, other financial fraud, criminal fraud, or other. Financial ID theft typically focuses on an individual's name and Social Security number (SSN). A perpetrator may apply for telephone service, credit cards or loans, buy merchandise, lease cars or apartments. In criminal ID theft, the perpetrator provides the victim's information instead of his or her own when stopped by law enforcement. Eventually, if a warrant for arrest is issued, it is in the victim's name. In an identity cloning case, the perpetrator uses the victim's information to establish a new life. They work and live as the victim. For example, the perpetrators may be illegal aliens, criminals avoiding warrants, people hiding from abusive situations, or persons becoming a “new person” to leave behind a poor work and financial history. In business or commercial identity theft, the perpetrator may open credit cards or checking accounts in the name of the business. The business finds out when unhappy suppliers send collection notices or their business rating score is affected.
[0138] Referring to FIG. 20 , a user may set notification preferences 2000. The user may select email 2010, SMS 2020 (e.g., mobile telephone messaging), or both. If email 2010 is selected, there may be an adjacent text field 2030 for entering one's email address. By default, the field 2030 may be pre-populated with a user's login email address. The user may change it if desired. If user selects SMS 2020, the user may be able to enter either the phone number or email address for the corresponding device. In some embodiments, the messaging information may be validated such that a code, link, or other information may be provided that then may be communicated to the system to confirm receipt of the message. In some embodiments, there may be a slider control 2040 that enables the user to set the severity threshold of detected events alerts. The less severe the setting, the more alerts the user will receive, and so forth.
[0139] Referring to FIG. 21 , a payment screen 2100 may allow a user to enter a credit card and/or other payment information. The payment information may include credit card number and other information 2110, as well as billing information 2120.
[0140] A payment information step may be displayed if the user selects or enters the registration process after selecting a plan. Once credit card data is entered, it may be submitted to a payment gateway for validation only. If validation is unsuccessful, an error message detailing the reason for failure is displayed, and the wizard returns to this step to permit users to update the credit card data, enter a new card, etc. The system may support a “buy once” functionality for on-demand services and a subscription functionality that charges monthly.
[0141] Subscriber Authentication
[0142] The registration process allows users to submit information that may be used later to authenticate that the person who is logging in to the service is the person who registered with the service. After the registration flow, the user may be asked to click on a link emailed to him/her in order to activate the account. For example, the user may receive an email message with the following exemplary text:
Dear Customer,
[0143] Thank you for visiting www.identitytruth.com. You have registered your account using this email address. You may activate your account by clicking the link below and logging in with the username and password you entered during registration. https://www.identytruth.com/confirm_registration/?emailToken=0466dfa1
CONFIDENTIALITY NOTICE: This e-mail may contain information that is privileged, confidential or otherwise protected from disclosure. If you are not the intended recipient of this e-mail, please notify the sender immediately by return e-mail, purge it and do not disseminate or copy it.
Thank you,
The Identity Truth Team
CONFIDENTIALITY NOTICE: This e-mail may contain information that is privileged, confidential or otherwise protected from disclosure. If you are not the intended recipient of this e-mail, please notify the sender immediately by return e-mail, purge it and do not disseminate or copy it.
Thank you,
The Identity Truth Team
[0144] In the event of loss of password or of user id, the security questions and other data provided at registration may be used to authenticate the user. A credit card also may be verified if provided. This type of authentication may not attempt to confirm that the subscriber is who they say they are. For that, the system may strongly authenticate a subscriber, using, for example, commercially available authentication technologies.
[0145] Strong authentication may be a deterrent to legitimate users if too much information is requested to register. This type of authentication has financial costs associated with it. It therefore may be necessary to balance the need to authenticate with the data to be presented. For example, before presenting credit reporting data to a subscriber or before requesting credit reporting data about a subscriber, strong authentication may be used. Strong authentication typically will not be part of an initial registration process. If a plan includes reports that make use of credit reporting data, the strong authentication may be used as part of the plan configuration independent of the registration wizard.
[0146] In some embodiments, a price-per-credential pricing model is used. For example, for certain data, there may be a cost for each credential searched on.
[0147] In some embodiments, notification preferences are set during registration that allow users to specify initial preferences for notification of fraud activity (e.g., email, SMS text message, telephone call, and/or some combination). The email option may be pre-filled with the email address entered previously, and/or users may enter another email address.
[0148] When a user has completed the notification step, the wizard may terminate, and alert the user that an account has been successfully created. The user may be asked to click on a link emailed to their primary email address in order to activate the account. When the user clicks the link, the user is asked to sign in and if successfully authenticated may be shown the dashboard 2300 (see FIG. 23 ).
[0149] Referring to FIG. 22 , in some embodiments, if a user has selected a plan that does not require payment, he or she would proceed through Steps 1-3 of the registration process, but would not be presented with Step 4 (payment information). Instead, such users would be presented with a page 2200 that prompts them to enter the assets that they would like to be able to monitor for free.
[0150] As shown in FIG. 22 , there may be some text 2210 positioned at the top of the registration area that gives the user a general description of what he/she is supposed to do on this page. For example, the text may read “Carefully enter the assets you would like monitored.” In some embodiments, users may not change the assets once entered. The user may be presented with fields 2220 for entering information on up to a number (e.g., 1, 2, 3, 4, or more) of personal assets.
[0151] Each asset entry area may be preceded with a drop-down selector 2230 that allows the user to select the type of asset to be monitored (social security number, credit card, etc.). For example, the default for the first drop-down field may be “Social Security Number”. Subsequent fields may contain “Credit/Debit Card” as the default text within the drop-down list. Users may be restricted from entering more than one Social Security Number. In some embodiments, the SSN may be verified to be the user's SSN, for example by checking publicly and/or commercially available records.
[0152] Each asset may contain a text field for entering the SSN or account number that corresponds to the asset. The number may be masked as it is entered. There may also be a text field (also masked) for confirming the SSN or account number. If a SSN is entered, there may be logic that allows the user to only enter credit cards for the remaining unused assets. There may be logic that verifies the format of a real SSN so that the system does not incur costs for passing invalid formats to a vendor. There are commercially available services to perform this verification.
[0153] In some embodiments, the selection of other plans, including a plan requiring payment, provides similar information collection functionality for collecting user information. Thus, this page may vary as to the information collected for different services offerings. In addition, in all embodiments, the collection of user information may include collecting from the user a value for each credit-related or other asset that the user identifies.
[0154] Referring to FIG. 23 , in some embodiments, a user dashboard 2300 provides the main entry point for registered users of the system. Once logged in, users may be directed to the dashboard 2300, from which they may access general market data, news and discussions, their personal risk profile and alert information, as well as details and preferences for their account. For example, the user dashboard 2300 may include a summary of recent detected events 2305 (e.g. applications for credit, changes of address, etc.).
[0155] The events may be determined from data that the service has captured as well as data gathered from the commercial information sources. As described, the service may initially capture data on the customer during the initial signup process, in order to make the initial queries to the external data sources. Once the reports have been retrieved based on the customer-provided data, this information will also be displayed in detected events.
[0156] A consumer may never have seen all this public and private information compiled about them displayed in a navigable report. This is the raw data view of the reports retrieved.
[0157] Each data value may be hyperlinked to the supporting document that provides drilldown into the report which supplied this value, if possible. Also, there may be a place for feedback on each data item for the customer to resolve (confirm or deny that the item is in fact related to them) the data item. This information on the customer data may be saved in order to be used in future processing.
[0158] The dashboard 2300 also may include the user's identity theft risk 2310 (graphically displayed as a scale/bar with numeric representation of “risk” (i.e. a scale of 0 to 100) as well as descriptive labels (e.g. “good”, “average”, “bad”) with a marker representing where the user “scores” in relation.
[0159] The overall risk value may be used to indicate to the customer their overall identity health, analogous to a credit score. This value may be calculated based upon the number of discrepancies that the data validation rulesets found, the fraud models rulesets risk value, and the general market data and news story inference rule sets risk values. Each of these individual risk values contribute to the overall risk value with a weighting value. In this way, some risk values contribute more to the overall value. For example, the social security number found on the Internet poses a greater risk than living in a high risk metropolitan area. The overall risk value is to be normalized so that it may be trended and compared over time, even as the number of assets monitored and the ruleset evolve.
[0160] The overall risk value may be visualized by a meter, with gradations from low risk to high risk. This meter may offer drilldown capability to enable the user to get further information about why their score is what it is. The highest weighted values to the lowest weighted values contribute to the score and may be presented in a table ordered as such. There may be links to FAQs that describe what may be done to lower the score and remedy detected problems.
[0161] A user dashboard also may contain a depiction of relevant fraud models 2320 (e.g. real estate fraud). The fraud models 2320 are scenarios which allow for the detection of fraud from the individual events in the raw data. The fraud models 2320 may be compared to changes in the customer's identity profile to uncover identity compromise from the correlation of these individual events. A risk value is associated with each fraud model ruleset. As described, rulesets take as input data retrieved from the data sources and past analysis and derive results. The rulesets identify trends which might indicate fraud, identify discrepancies in the data, and calculate metrics and statistics.
[0162] As an example, a ruleset may indicate whether a social security number or credit card number has been found on the Internet. The risk value returned by such a ruleset is 1 if the asset was found on the Internet or 0 otherwise.
[0163] As another example, the data validation rules may include rules like those used generally to identify inconsistencies and anomalies in the data retrieved from external sources. These include: invalid addresses, high risk addresses/phone numbers, disconnected phones, invalid social security numbers, SSN deceased file check, SSN issued prior to date of birth, telephone number/address inconsistency, and/or other data validation.
[0164] As another example, an FTC inference ruleset may be derived from the Federal Trade Commission data, the general market data, and a variety of news stories. These rules assign a risk value to the customer, based on the general information provided by the customer such as age, address, and the number of years that the given customer has held a credit card. This may be a ‘background’ risk value, based, for example, on the population studies made by the FTC on the identity theft complaints and cases. An example would be that a customer in the age bracket 18-29, living in Phoenix, Ariz., is at the highest risk based on the reported incidents of identity theft, whereas someone in the age bracket 60-64 in Jamestown, N. Dak. is at the lowest.
[0165] Likewise, rulesets may be created based on a topical news story concerning identity theft and may extend this background risk analysis by making the risk identification more dynamic and responsive to current events. An example is a news story concerning the apprehension of suspects involved in a phishing attack on Bank of America customers in the Boston area. A story of this type would be scanned for keywords in order to create a news ruleset matching Boston and Boston metropolitan area Bank of America customers. Customers in these markets would have a higher background risk level based on this news ruleset.
[0166] In an analyzed tree view, icons may be placed beside the data items which the analysis engine 150, 1420 ‘red flag’s. The customers may then drilldown into these discrepancies to see the source of the discrepancy. An example of the type of discrepancy highlighted here may be telephone number and address mismatches.
[0167] For the analysis results which are not tied to a particular data item, but rather to the data as a whole, in this example, a separate pane may be placed above the tree view. This pane may serve as the headlines and alerts pane. Analysis outputs from the fraud model, that synthesizes results from the data as a whole, are shown in this pane. The results shown here represent significant value to the customer and power of the analysis engine and rulesets. Analysis arising from topical news stories inference rules are placed in this pane as an alert item. A FTC/market/news background risk value may be placed at the bottom of this pane. Given the nature of this value, this value may be calculated for every user for which the service has age and residence information. As a result, this headline/alert pane typically is not empty.
[0168] Each data item or analysis may provide an AJAX control to provide feedback back to the service concerning the analysis such that they may confirm, deny, and provide additional commentary upon the item. This feedback is gathered via a questionnaire and the results persisted for future processing. An advice link is offered on avoiding this type attack through a set of FAQs.
[0169] The user dashboard 2300 also may include data analysis performed by the service analysis engine on the raw data shown in the detected events view. In this view, the customer can see the output of the service analysis engine, loaded with service rulesets, and processing of the raw data. The service rulesets may include the fraud models, data validation rules, and the inference rules based on the Federal Trade Commission/News/General Market Data and/or general identity theft incidence news stories.
[0170] The user dashboard 2300 also may include a summary of general market data, and news. In addition, this default view may provide links to other data (identity information, history, in-depth risk level, events vs. data breaches). Changing the user's focus to one of the other views may not necessitate a complete page refresh. Instead, data to render all views may be retrieved at the time of initial page generation. In this way, users can toggle between the dashboard views instantaneously (or near-instantaneously).
[0171] The dashboard 2300 may provide a section containing rotating news 2330, breaches 2340, and local news 2350 headlines. Users may be able to click on a headline and view the full-text of the story/item. The dashboard 2300 may provide a link 2360 to access a view which allows users to manage their account details and preferences. Specifically, users may be able to change their address, email, user id, password, and subscription plan, update credit card information (used for subscribing to the service), and manage their preferences for notification of fraud events (email/SMS/both, email address, mobile phone number). An Account Preferences View may mask (i.e., display ‘x’, ‘*’, or some other relevant character) the characters of sensitive data entities. Specifically, the entire password may be masked as it is entered; all but the last 4 digits of the credit card number may be masked when it is displayed; all but the last 4 digits of the SSN may be masked when it is displayed.
[0172] The dashboard 2300 may prominently display references to provide users with information about more expensive subscription plans. Specifically, the default dashboard 2300 view may provide references to the information users could view if they upgraded to a more expensive plan. For example, a free trial user would also see samples of, or references to, the information available with the next levels of plans (e.g., cell phone records, credit data, etc.), similarly, a first level subscription user may see samples of the information available with the next subscription level plan. In addition, a link may be displayed which may take users through an upgrade process, including collecting credit card information, and other information if required. The general market data and news view also may provide links relating to upgrades.
[0173] An account preferences view may indicate users' current subscription plan as well as provide a link to guide users though the upgrade process. The dashboard 2300 may also provide a facility for users to request Really Simple Syndication (RSS) feeds as well as obtain additional information on RSS. At the bottom of all dashboard views, an RSS logo graphic/link may be displayed and may provide access to the RSS page where users may learn more about RSS and request any or all RSS feeds. In addition, the general market data and news view may provide RSS links within the specific content areas (e.g., “subscribe to content like this”). The following categories of content may provide RSS feeds: general news, user-submitted reports of identity theft schemes, and identity theft alerts for individual users. The RSS page may provide explanatory information on RSS (e.g., FAQ—What is RSS?, etc.), links to RSS readers (native XML, Yahoo, Google, Bloglines, Newsgater, AOL, Pluck, Rojo, etc.), and links to activate feeds for the three content areas. The dashboard 2300 may provide links to third-party service offers (e.g., credit protection insurance & identity recovery solutions). These services may be offered exclusively by providers independent of the service. Therefore, the dashboard 2300 may provide referral links to these providers' websites for signup and management functions.
[0174] The dashboard 2300 may provide a facility that permits users to make one-time purchases of additional data (initially, this may be an on-demand credit report for subscribers; some customers would already receive this data as part of their subscription so would not be offered this service). The dashboard 2300 may also provide links and a description to promote the one-time service and, if selected, may collect relevant billing (e.g., credit card) information and then display the resulting data.
[0175] The dashboard 2300 may present a link that allows the user to enter product feedback. The dashboard 2300 may present a graphical button 2365 that brings the user to a view of all confirmed items and credentials that are related to their identity (e.g. credit cards, addresses, etc.). This section may allow them to delete and edit items that are related to their identity. The dashboard 2300 may present a graphical button 2370 that brings the user to a view that provides them with all detected events related to them. The user may resolve unresolved DB-items as well as filter items by severity. The dashboard 2300 may present a graphical button 2375 that brings the user to a view that provides them with a timeline comparison of their events vs. known breaches in the general population, described further with respect to FIG. 27 below. The dashboard 2300 may present a graphical button 2380 that brings the user to a view that provides them with an overview of their personal risk level. Table 3 below depicts additional user interface features by section and describes what the user would see, in exemplary embodiments, in each section. Each section in Table 3 that presents risk or fraud data may include a help icon or information button that explains the data and includes remediation information if applicable. All or part of this information may also be shown when mousing over a graph. Where applicable, there may also be mouse over effects to highlight graph data.
[0176]
| TABLE 3 | |
|---|---|
| ADDITIONAL USER INTERFACE FEATURES | |
| User Interface/ | |
| Functionality | Description |
| Detected Events/ | This section enumerates all the events detected for the user such |
| Results Section | as Unrecognized Address found. It allows the user to view the |
| detail of the event detected and specify whether they recognize | |
| the event or not. For example, the user may be asked whether | |
| s/he has a personal connection to the event (e.g., whether s/he has | |
| been directly or indirectly affected by the event). If the user does | |
| not recognize the event, s/he is presented with remediation | |
| information that may help clarify the source of the event or lead | |
| to discovery of fraud. | |
| The data associated with detected events is moved to the user's | |
| My Identity section (see below) if the user does recognize the | |
| event detected. If the user does not recognize the event, the event | |
| is classified as possible fraud and will impact the user's health | |
| score and predicted fraud. | |
| Risk data bar graph | Depicts the Identity Health Score calculated for the user in a bar |
| graph with a range from zero (0) to a hundred (100). The colors | |
| in the graph vary from red for low scores to green for high scores. | |
| The graph also contains a link to a page that explains the score in | |
| more details to the user. | |
| Fraud model section | This section shows any fraud models that are predicted for the |
| user given his or her profile and any detected events that the user | |
| has not recognized. | |
| My Identity section - | This section contains all information that is or has ever been |
| view/add/edit | associated with the user. The information in this section may |
| personal and login | have been entered by the user directly or it may have been added |
| info | to the system via detected events that the user did recognize. |
| Track your identity - | This graph depicts the history of Identity Health Scores calculated |
| Risk data graph view | for the user. The Y-axis has a range from zero (0) to a hundred |
| (100). The X-axis shows the time of each score change. The | |
| colors in the graph vary from red for low scores to green for high | |
| scores. | |
| Track your identity - | This graph shows a measure of certainty from zero (0) to a |
| Uncertainty bar | hundred (100). The certainty refers to the Identity Health Score |
| graph | produced. Certain statistically based assumptions are made in |
| order to produce the score. If the user confirms the assumptions | |
| made, the certainty about the health score will increase. | |
| Identity Theft | A breach refers to reports of data theft or data compromise |
| breaches | reported by an organization. |
| The service monitors such reports and produces a breach alert to | |
| notify users of the breach. Breach alerts are displayed as detected | |
| events as well. | |
| Identity Theft News | The user interface may include news pertaining to identity theft |
| that will be updated regularly. | |
| Marketing campaign | The user interface will include a section(s) promoting the |
| section, e.g. refer a | different pricing options of the service and allowing users to refer |
| friend and get | the service to others. |
| something free or | |
| extra. | |
| Purchase additional | The user interface may present optional identity theft prevention |
| On Demand Services | related services that users may purchase for a fee such as |
| remediation services or insurance. | |
| Purchase System | Users have the ability to purchase the service using a variety of |
| Services | pricing options including pay per use or by subscription. |
| Logout | This takes user back to guest user home page |
| Home - | This takes user back to default page showing summary of |
| detected events. | |
| Customer Support | This takes the user to a page providing online support resources as |
| Link | well as contact information to customer support. |
| Security and partner | Security logos from authorized security certification vendors will |
| logos and privacy | be displayed in the user interface as well as authorized logos from |
| notice | partners that provide data used to deliver the service. |
| Customer feedback | This is a form to gather feedback from user on the service or on |
| the usability of the user interface. | |
[0177] Referring to FIG. 24 , a “My Identity” page area 2400 (accessed, for example, by selecting graphical button 2365 on dashboard 2300 of FIG. 23 ) contains confirmed (e.g., verified by the user) personal credentials/information 2410 about a user that was generated by licensed data (the feeds) and certified by the user, and/or that was entered by the user himself/herself (e.g. current and past addresses, phone numbers, financial accounts, etc.). The user is able to manage his/her information from this area.
[0178] The look and feel of the My Identity page 2400 may be the same as the user dashboard 2300 (e.g., same color scheme, same navigation bars, etc.). There may be tab controls denoting the various categories of personal information contained within this section. For example, the tabs may be labeled “Personal” 2420, “Financial Accounts” 2430, and “Others” 2440. The user may click on tabs to toggle between the credential information presented on each tab. There may be some way for the user to determine which tab is currently “active”. Within each tab (when necessary), there may be additional navigation in the form of text links for the sub categories within each tab (i.e. phones, emails, and addresses might be sub category links under the “personal” tab. A user may click on navigation links 2450 to toggle within sub categories on each tab (e.g. phones, emails, etc.). There may be some way for the user to determine which link is “active”.
[0179] There may be views that list the various credentials themselves (e.g. a current or past address). These may be generated from feeds or entered by the user.
[0180] Note that all addresses displayed 2460 (whether entered by the user or obtained via a feed) may be the user's “normalized” address which may be in a standard format used by the U.S. postal service.
[0181] Credential items may be displayed in a list, preceded by a date or date range 2470 (depending on the type) that is relevant to the credential (if the credential is an address, the date range would depict when the user lived at that address). By default, the lists may be in reverse chronological order. For addresses, the current address may be populated from the user's account information entered during the registration process. There may be controls that allows the user to sort the list items by date (or date range) and address.
[0182] When the list of items becomes longer than the allotted viewing space, a scroll bar may appear to the right of the window to allow the user to scroll. For those credentials that have been entered by the user, there may be icons/buttons 2480 that allows the user to edit items that he/she has entered. Clicking on the edit button 2480 may spawn a new window containing the user-created data for the item in the list that was clicked.
[0183] The user may see fields that may be populated with the information in the list. Users may be able to edit the information. Users may see a “save” and a “cancel” button which will either cancel and close or save and close the window.
[0184] There may be a graphic and description of a “Certainty Margin” 2490 showing how “complete” (on a scale of 100) the information about a user is (and, hence, how “certain” the results are).
[0185] There may be accompanying text that tells the user what they are seeing. There may also be a “call to action” in the form of a link that allows the user to provide additional information and therefore increase their certainty score.
[0186] Referring to FIG. 25 , an events view 2500 (accessed, for example, by selecting graphical button 2370 on dashboard 2300 of FIG. 23 ) may provide a user with a historical list 2540 of detected events, for example, all events that are potential fraud events that are specific to the user, as well as a graphical view 2510 of their detected events over time, weighted by severity. FIG. 25 shows the detected events with a severity graph 2510.
[0187] The severity graph view 2510 may contain a slider that allows the user to click and drag in order to change the date range shown within the graph. There may be a severity filter 2530 in the form of a drop-down list. The default setting may be “all”.
[0188] The user may select from “High”, “Medium”, and “Low”. The selection may change the appearance of the severity graph 2510 by displaying only those data points that are relevant to the category selected. Hovering over a point on the severity graph 2510 may present a tool tip window that displays the event title, the date of the event, the severity, and the status (resolved/unresolved). There may be a list of detected events 2540 positioned next to the severity graph 2510. The list 2540 may contain the title of the event as well as the date of the event. A user may sort by date or by event (presented in reverse chronological order by default). Changing the sort order of the list changes the graph 2510 displaying the corresponding data points.
[0189] Referring to FIG. 26 , a list of chronological events 2600 may be provided. The display of a list only view presents the user with a chronological (reverse by default) view of all detected events that may be similar to the detected events view within the user dashboard, only extended to accommodate all the space within the main viewing area.
[0190] There may be a column for the date of the event 2610, the name of the institution related to the event 2620, and the severity level of each event 2630.
[0191] Clicking on an item may spawn a window providing the details for that item as well as a button and text allowing the user to edit the item's resolved/unresolved state. For example, if a user has made a mistake and goes back and makes a change, then that event becomes part of their identity (e.g., they recognize the event as associated with them).
[0192] Referring to FIG. 27 , in some embodiments, an Events vs. Breaches area 2700 (accessed, for example, by selecting graphical button 2375 on dashboard 2300 of FIG. 23 ) includes two tabs. The first tab (“Events vs. Breaches”) enables a user to view a time series graph 2710 containing known breaches that have occurred throughout the population. The user also may see personal events (e.g., the same events that are listed in a My Fraud Alerts area) superimposed against the known breaches, and may be able to filter the breaches by severity 2720 and time 2730. The user also may be presented with a list of the breaches 2740 to the right of the graph, which contain functionality. Referring also to FIG. 28 , a second tab (“Breaches”) 2800 allows a user to view a list of the breaches with the same filters, and allows the user to take actions to associate or disassociate the breach with them.
[0193] Referring again to FIG. 27 , the breaches may be represented by “bubbles” 2750 on the graph 2710. The size of each bubble may represent the size of the breach, if known (i.e. how many people affected by the breach, etc.). The Y-axis of the graph may represent severity (i.e. how potentially damaging the information leaked was), based on an algorithm derived from elements such as SSN, addresses, phone numbers, etc. Therefore, the more severe the breach, the higher the bubble may be placed along the Y-axis. The X-axis may be based on time. There may be a “time period” slider control 2730 positioned above the graph. The user may be able to point, click, and drag the slider from side-to-side. Doing so will change the time range displayed in the graph's X-Axis. There may be a “severity” filter displayed as a drop-down list 2720 and positioned above the graph, adjacent to the time period slider. The default setting may be “all”. The user may select from “Low”, “Medium”, or “High”. When doing so, the graph will change by displaying only those bubbles that correspond to the severity level selected. The user's detected events may be displayed superimposed on the graph.
[0194] A breach filter area 2740 may be positioned to the right of the graph and will list the breaches including the date of the breach 2750, the name of the institution 2760, and the size 2770 (number of records lost, etc.). A user may hover over a breach in the filter area 2740 and the corresponding bubble may be illuminated and display descriptive text providing the user with a synopsis of the breach. Clicking on a breach item allows a user to associate or disassociate himself/herself with the item. In some embodiments, the items may be listed in reverse chronological order by default and may be able to be sorted. Hovering over the breach items will spawn a tool tip window which will provide a synopsis of the breach.
[0195] In one embodiment, clicking on a breach item in the filter area spawns a new browser window. This window may behave similar to the “resolve detected event” window. The pop-up window will show all information known about the breach and ask the user if they are associated with the institution that had the event (yes or no). For example, the user may be asked if he has an account and/or data with the entity that has been breached. Once a user associates a breach with themselves, the corresponding breach bubble in the graph may be highlighted, and the same item in the breach filter may be denoted with a graphic icon. Users may be able to sort the date, institution, and size columns by clicking on sort icons at the top of the columns.
[0196] With respect to the breaches tab 2800, the breach items may be listed similar to those in the breach filter area 2740 of the “Events vs. Breaches” section 2700, except that a “severity” column 2810 may be added which may display the corresponding severity values (high, medium, low). The columns may also be able to be sorted by the column headings. Users may be able to click on the breach event to associate/disassociate themselves with the event (may be the same experience as in the Events vs. Breaches filter area. Users may be able to sort the breach events by clicking on sort control at the top of the columns (date, institution, size, and severity).
[0197] Referring to FIG. 29 , a “My Risk Level” display 2900 (accessed, for example, by selecting graphical button 2380 on dashboard 2300 of FIG. 23 ) may provide the end user with his or her current risk score 2910 as well as provide the user with a “certainty score,” which may be an indicator of how certain the system is of the user's risk situation based on the quantity of information that has been provided by the user or from data feeds. Either or both the current risk score 2910 and the certainty score may be associated with a descriptive label regarding their numeric representations.
[0198] As shown, this section may contain two tabs. In one embodiment, a first tab 2915 (default) provides the user with his/her current risk score (described further herein) while the second tab 2930 provides a certainty level.
[0199] FIG. 29 depicts an exemplary representation of the current risk score tab 2915. The page may contain a title (e.g. “Current Risk Level”), along with some explanatory text that tells the user what he/she is viewing. The page may contain a graph 2940 that contains identity theft risk exposure levels for the U.S. population, along with an indicator of how the user compares with the population. The graph 2940 may contain a link to more information (the information may be displayed in a new browser window). The page may contain the user's Identity Theft Risk Score 2910 displayed numerically. The page may contain text that describes what the score means. The page may contain the user's Identity Theft Risk Percentile 2920, along with some explanatory text.
[0200] Referring to FIG. 30 , an exemplary representation of the Certainty Level tab 2930 is shown. The page may have a title (e.g. “Your Certainty Level”, etc.), along with some explanatory text. The page may have a graphic 3010 that displays the user's overall certainty score. This graphic may be in the form of a circle with a bubble inside of it, where the larger the bubble, the more certain. The page may have some text/graphics that entice the end-user to enter more information to increase his/her certainty score (text may also speak to the benefits of increasing their score). The page may have a horizontal bar graph that displays the level of completeness for the various types of personal information (addresses, credit cards, etc.) that the service has for the user (not shown). The intent is to show the user which areas have strong information and which ones are weak. Clicking on one of the elements may bring the user to their “My Identity” page 2400 for the information type that they had clicked on (addresses, etc.)
[0201] News
[0202] In some embodiments, the system 100 may provide users with different types of news information, including identity fraud news and events, breach information, and local news within the user dashboard area 2300. In various embodiments, news also may be viewable within the My Identity, My History, My Events, and My Risk Level areas. The news headline display area may be positioned near the footer of each page. The news display area may contain a section for displaying headlines as well as an area for displaying tabs that indicate the category (local news, breaches, etc.) of news that is currently active. The news category tabs may change state as each tab becomes “active”. The tabs may automatically rotate. The user may click on a tab to skip to that category (tabs may no longer rotate after doing so). Headlines may be displayed, and in some embodiments, clicking on a headline will spawn a new browser window displaying the full text of the news item.
[0203] There also may be a customer support page, and a place for users to provide general comments and feedback regarding the service.
[0204] Security
[0205] In general, in some embodiments, every user may be assigned certain roles and depending upon the privileges (or policies) associated with each role, access may be granted. The roles and privileges may be defined in a configuration, which may also contain a mapping section, describing which privileges are assigned to a particular role. The configuration may be changed to map new/existing roles to new/existing privileges. For example, there may be an Administrator role for service provider personnel, who may be responsible for managing consumer accounts and the overall administration of the application. There also may be a User role for end-users of the service, who may create accounts and edit account information. In some embodiments, this role will not have permission to downgrade a service plan or terminate service.
[0206] In various embodiments, privileges may include:
-
- [0207] 1 CREATE_CONSUMER_ACCOUNT: Privilege to create a consumer account.
- [0208] 2. UPDATE_CONSUMER_ACCOUNT: Privilege to update a consumer account.
- [0209] 3. DELETE_CONSUMER_ACCOUNT: Privilege to delete consumer accounts.
- [0210] 4. UPDATE_CONSUMER_ACCOUNT_PREFERENCES: Privilege to update consumer account's preferences.
- [0211] 5. UPDATE_CONSUMER_ACCOUNT_STATUS: Privilege to activate, deactivate, and reactivate consumer accounts.
- [0212] 6. VIEW_REPORTS: Privilege to view reports for consumer accounts.
- [0213] 7. VIEW_ADMIN_REPORTS_Privilege to view admin reports
- [0214] 8. UPDATE_MONITORING_SET_PREFERENCES—Privilege to modify the monitoring preferences for user accounts
- [0215] 9. MANAGING_FAQ & GENERAL MARKET DATA—Privilege to update FAQ & General market data & set rules
[0216] Security settings for a site may dictate the views and functionalities available to the users. The security settings, in turn, may be driven by the privileges associated with a user. A role for a user may be created, for example, by associating predefined privileges with the user, so that a single user may have multiple privileges and multiple roles. Views available to a multi-role user may include a sum total of all the privileges associated with that user.
[0217] For example, if an area of the application (e.g., text, a link, an entire section, or entire page or portlet) needs to be shown only to a subset of users, it may be associated with a named privilege. Access to the area may be shown/granted to the user only if the user has that privilege associated with their user account. The association in this case is indirect, since users are directly associated to roles, then roles to privileges. Each user account may be associated with one or more roles. A role, being its own distinct entity, may be associated with one or more privileges.
[0218] Administration Requirements
[0219] An administration area of the consumer application may be used by administrative personnel for management of customer accounts (e.g., replicating end-user self-service functions that users are unwilling and/or unable to perform themselves), as well as additional functions not available to end-users, and reporting of usage information.
[0220] An administration area may include a high-level, population-wide interface for reporting on overall service usage and providing filtered searches for account(s) meeting search criteria, as well as detailed view presenting parameters for an individual account. In some cases, administration users may be customer service representatives (CSRs) working in a call center environment to address customer requests (e.g., password resets, plan changes, etc.). Due to the typical costs attributable to CSR support, care may be taken to optimize the presentation of information in this interface such that CSRs may perform their tasks quickly and efficiently. Wherever possible, a consumer application leverages infrastructure already in place with the business application (e.g., account filter screens).
[0221] In some embodiments, a summary usage report may be viewable by internal sales and marketing personnel. The report may provide a breakout of usage by plan type, i.e. “how many plans have been sold?” with relevant filters. It may also include information about time/date purchased, geography, plan type, and percentage of conversions (e.g., how many have upgraded plans). The consumer application may provide a facility to generate a filtered list of account(s) (essentially, an account search functionality). Filter criteria may include: first name, last name, email address, user ID, SSN, and/or subscription plan. The result of the filtered search may be a pick list of accounts, permitting users to select one or more accounts for detailed views. The consumer application may provide a single page view of all information pertaining to a single account. This may include all information entered by the user via the registration wizard, as well as their subscription plan and notification selections. This page may be organized with logical groupings of data correlating to the individual steps of the registration wizard. Within this view, administrators may edit any account information, reset user ids and passwords, change the user to another subscription plan, or terminate service and close the account. In addition, this view may provide a facility to issue account credits to premium subscription plan users in the event of billing mistakes.
[0222] In one embodiment, a map is provided that indicates the location of the user. The map may have additional information related to the time zone of the user, and application—relevant information, such as recent identity incidents, and so forth.
[0223] In one embodiment, the administration area allows for creation, reading editing, and deleting of plan descriptions, pricing, site content, RSS feeds, notification messages, update fraud models, and so forth. This capability may depend on permissions assigned to the user.
[0224] With respect to notifications, the service may provide notifications to users, for example via email and/or SMS messaging for various fraud and account events.
[0225] Notification Requirements
[0226] The consumer application notification infrastructure may provide notifications to users via email, SMS messaging, and/or telephone (e.g., automatic voice recordings) for various fraud and account events. In some implementations, users may control their preferences for notification mechanism. Upon successful completion of a registration wizard, a notification may be generated welcoming the user to the service, summarizing the benefits of the service plan selected and providing links to login and customer service. Upon detection of a fraud or identity theft event (e.g., if the overall risk value for a particular customer reaches a predetermined threshold value) a notification may be generated alerting the user(s) and providing links to the Service dashboard for additional information and remediation steps. A message may be delivered according to the user's specified preferences.
[0227] An alert may direct a customer to log into the portal when their overall risk score has reached this threshold. The notification may convey an appropriate sense of urgency. The user may be able to confirm or deny the notification. A skepticism level may be applied on the model on the response of the end user. In other words, the responses themselves may be inaccurate.
[0228] In addition, the service may generate a regular, periodic notification detailing the identity health of the subscriber. Frequency of generation may be determined by the specifics of the subscribed service plan. Again, these messages may be delivered via the communication mechanism specified by the user's preferences.
[0229] Periodic email notifications may be sent to the customer to prompt them to log into the portal and check their overall identity scores, view their assets and any discrepancies that rulesets have detected.
[0230] All reporting to the customer may be done via the authenticated access to the portal over https. The transmission of pdf files and sensitive information may be performed in a manner that authenticates the recipient and controls the delivery of content to make sure it is timely.
[0231] A mechanism to create trust with the customer to alleviate their fears of a phishing attack may be used. Exemplary mechanisms, such as those used in the financial industry, for example, include allowing the user to select a graphic, and including that graphic in communication to the user.
[0232] In some embodiments, a notification is generated for a user of a trial subscription plan if the user has not converted membership to a paid plan within a predetermined number of days of the plan expiration date. This notification may provide details as to why their plan is terminating, the benefits they will receive by signing up for a paid plan, and provide links to the dashboard area where the users may upgrade their plan. In some embodiments, a dashboard provides a mechanism to change the user's subscription to a paid plan with collection of credit card billing data, even if the trial plan has terminated. If the user has not taken action by 1 day prior to plan termination, the notification may be re-generated. If the trial plan is terminated without user action, a notification may be generated acknowledging the termination of the user's service, and again providing links to convert to one of the paid plans. When the trial plan has expired, in no case may the user be able to sign up again for the trial plan with that email address. These messages may be delivered via email only.
[0233] With respect to the personal identity health score, the intent of this score is to provide subscribers with an indication of the likelihood that a loss will occur as a result of identity theft as well as, in some cases, a measure of the relative size of their possible loss. This may be accomplished by determining the number of assets susceptible to loss, examining the attributes of the subscriber, monitoring for changes in these attributes and detecting events that are known to be part of fraud models.
[0234] One factor in determining the possible loss is the number of subscriber assets for which a thief may take control. Bank accounts, credit cards, home equity credit lines and real estate are examples of assets that a thief may control. Another factor is whether or not those assets are active. Inactive assets have the most exposure, as the subscriber is not likely to find out about the loss of control for months. Credit card companies do not send bills for inactive accounts. Thus, diversion of the bill to a new address will not be discovered. For inactive home equity credit lines, the subscriber is not likely to look at the balance, since they know they have not written any checks against the credit line.
[0235] Obviously, thieves do not know which accounts are active and which are not, but the more inactive accounts there are, the higher the chances that the one that is taken over by the thief is an inactive account.
[0236] For example, inactive credit cards are prime targets of thieves. Since bills are not sent for inactive cards, the subscriber would never know that the bills are being diverted. Not seeing the bills, they are unaware of the activity. Balance and payment history information about credit cards may be determined by commercial sources, such as a credit profile.
[0237] As another example, research has shown that a significant percentage of fraud is perpetrated by someone known to the subscriber. Thus, the number of people at the residence over the age of 13 is a measure of the people closest to the subscriber and with best access to personal information. This may be determined from census data and/or from commercial sources.
[0238] As another example, live pay checks or pay stub receipts may be stolen or otherwise compromised. They may contain at least partial SSN and personal information. Given partial SSN, birthplace and age may enable a perpetrator to determine a full SSN. Direct deposit therefore may be safer, and the score may be adjusted appropriately.
[0239] As another example, bank and credit card statements delivered in U.S. mail may be stolen or otherwise diverted via change of address. Electronic delivery is safer, and the score may be adjusted appropriately.
[0240] As another example, credit card offers and pre-approvals are often delivered to prior addresses. The more offers, the more likely this is to occur. This may be determined from commercial information providers.
[0241] As yet another example, if a user has had an address change in last year, this increases the likelihood that mail will go to a prior address. This may be determined from commercial information providers.
[0242] As another example, renters are much less likely to be subjects of mortgage or real estate fraud as they have less of an established payment history and thus it is more difficult to obtain a loan in their name. This may be determined from the subscriber and from commercial information providers.
[0243] As another example, just like inactive credit cards, inactive home equity lines may not be tracked actively by a subscriber. These may be prime targets for a thief. This may be determined from the subscriber and from commercial information providers.
[0244] An another example, it may be possible to estimate a level of association with a known breach. For example, if the user may have done business with the organization that was breached then it may be indirect. This may be based on geographic proximity and/or other factors. If the user has affirmatively done business with the breached organization then it may be more direct.
[0245] As mentioned, identity fraud may vary by location and age. Young adults may be on average less careful about protecting their personal assets, for example, by not shredding papers with personal information, not processing change of address forms, or not shutting off utility service when leaving a residence. Older people may be more likely to take more care in protecting personal assets. Risk is likely to increase after a certain age due to the need to hire outside help.
[0246] Some factors that affect likelihood are more easily determined than others. A user may indicate that he shreds documents, but the service cannot be sure that they do so all the time or even shred the right documents. A user may say that he is careful not to divulge sensitive information, but the service may not be certain that they are always careful. On the other hand, it is likely that users will provide reliable answers to the following: (1) Is your incoming mailbox secure (locked)? (2) Do you receive paper bank statements? (3) Do you receive paper credit card statements? (4) Did you file a Change Of Address form with the USPS after you moved? (5) Do you receive live salary checks or direct deposit? (6) Are you a home owner? The first five factors give some indication of how exposed the subscriber is to mail theft or diversion. In addition, with respect to factor number 6, home owners are susceptible to real estate fraud, while renters are not. Other factors affecting likelihood are the number of previous addresses and the number of residents at the subscriber's address. This data may be gleaned from public records data.
[0247] There is empirical evidence from the U.S. Federal Trade Commission that zip code and age are factors in identity theft. While it is not certain that there is a correlation, it is possible to adjust an overall predicted identity risk score according to FTC data.
[0248] Calculation of an Identity Health Score
[0249] In some embodiments, an identity health score is calculated by presuming that everyone has some base risk that is a result of being a member of society. This risk is increased depending upon the size of potential losses and the relative likelihood that these losses will occur. The entire result may be adjusted based upon the subscriber's zip code and age. The concept of relative likelihood is important. Even if it is not possible to determine the exact likelihood, the relative likelihood of one subscriber to another and to the general population may be determined.
[0250] The identity health score for an individual may have three components: a base score, a score due to attributes and likelihood, and a score due to detected events. As explained below, the first two components may be weighted by demographic information (e.g., location and age). In some embodiments, the location/age factors vary from 0.8 to 1.2.
[0251] In some embodiments, the identity health score for an individual ranges from 0 to 100. A score of 100 is for an individual who has a very low risk of identity theft (e.g., an individual who lives on a deserted island and has no assets). A score of zero is for an individual who has a very high risk of identity theft and/or who has already suffered identity theft. For example, an individual who has had their identity stolen and who has suffered serious financial damage (more than incidental credit card fraud) may have an identity health score of 0.
[0252] In some such embodiments, the base score is assigned a nominal value of 20, attributes and likelihood are assigned a nominal value of 30, and events are assigned a nominal value of 50. The actual score available to the events may be such that the total score cannot exceed 100.
[0253] A general formula for the first two components (i.e., the base score and the score due to likelihood and attributes (e.g., the individual's number and use of credit cards and the individual's risk of exposure due to inactive home equity credit lines)) is given by:
HS12=100−[Db20+Dcc(10*(1−e−(all/(active+1)))+Dhe(20*(HECL))]*likelihood (1)
where, HS12 is the health score for the first two components; Db, Dcc, and Dhe are demographic constants which may be chosen based upon the individual's zip code and age; “all” is the number of credit cards the individual owns; “active” is the number of active credit cards the individual owns; “HECL” is a value representing the individual's risk of identity theft due to an inactive home equity credit line; and “likelihood” is a factor representing the likelihood that a individual will in fact suffer financial loss due to identity theft. As explained, the “likelihood” factor may be calculated using Table 7 below.
HS12=100−[Db20+Dcc(10*(1−e−(all/(active+1)))+Dhe(20*(HECL))]*likelihood (1)
where, HS12 is the health score for the first two components; Db, Dcc, and Dhe are demographic constants which may be chosen based upon the individual's zip code and age; “all” is the number of credit cards the individual owns; “active” is the number of active credit cards the individual owns; “HECL” is a value representing the individual's risk of identity theft due to an inactive home equity credit line; and “likelihood” is a factor representing the likelihood that a individual will in fact suffer financial loss due to identity theft. As explained, the “likelihood” factor may be calculated using Table 7 below.
[0254] In one embodiment, Db (a demographic base score constant), Dcc (a demographic credit card score constant), and Dhe (a demographic home equity score constant) are each chosen to lie between 0.8 and 1.2. The greater the demographic constants are chosen to be, the lower HS12 is calculated (by equation (1) above) to be, and the greater the individual's risk of identity theft is determined to be. In one particular embodiment, the demographic constants are chosen so that Db=Dcc=Dhe. Where the individual lives a region (determined, for example, by the individual's zip code) in which homes have a relatively high real estate value, Dhe may be increased to represent the greater loss to be incurred by that individual should an identity thief obtain access to the individual's inactive home equity credit line and abuse it.
[0255] With respect to the component of HS12 determined from the individual's number and use of credit cards (i.e., the variables “all” and “active”), in some embodiments a presumption is made that the individual has zero inactive credit cards when he owns only one credit card, one inactive credit card when he owns two or three credit cards, and an upper limit of two inactive credit cards when he owns four or more credit cards. In other embodiments, the individual specifies to the system exact values for the variables “all” and “active.”
[0256] With respect to the component of HS12 determined from the individual's home equity credit lines, in some embodiments the variable “HECL” is assigned a value of 0 where the individual does not have an inactive home equity credit line and a value of 1 where the individual does have an inactive home equity credit line. Alternatively, a value for “HECL” may be determined to lie between 0 and 1 from U.S. Census Bureau information found at, for example, http://www.census.gov/hhes/www/housing/hvs/qtr406/q406tab6.html and http://www.census.gov/hhes/www/housing/hvs/annual06/ann06ind.html.
[0257] As mentioned, the variable “likelihood” may be calculated using Table 7 below. As explained below, a “likelihood” value for a typical individual is 0.8. Upper and lower limits for the “likelihood” variable may be chosen to be 1.2 and 0.6, respectively.
[0258] In another embodiment, where an individual provides only his age (for example by providing his birth date) and zip code to the system, HS12 for a typical individual of the individual's age and residential location may be calculated from the following equation:
HS12=100−[Db20+Dcc(10*(1−e−(STAC/(STAC-1)))+Dhe(20*(HOF))]*0.8 (2)
HS12=100−[Db20+Dcc(10*(1−e−(STAC/(STAC-1)))+Dhe(20*(HOF))]*0.8 (2)
[0259] As can be seen from equation (2), the value for the variable “likelihood” is assumed to be 0.8. Db, Dcc, and Dhe are demographic constants as described above. The variable “STAC” represents the average number of credit cards held by a typical individual in the state the individual lives in (as determined from the zip code provided by the individual interfacing with the system), and the variable “HOF” represents a home ownership factor for a typical individual being of the same age and living in the same location as the particular individual interfacing with the system, as further explained below.
[0260] In one embodiment, knowing only the individual's age and zip code, the variable “HOF” is determined from the following table:
[0261]
| TABLE 4 | ||||
|---|---|---|---|---|
| HOME OWNERSHIP FACTOR (HOF) | ||||
| Source: U.S. Census Bureau 2006 statistics | ||||
| Age | NE or W | S | MW | |
| <35 | .38 | .43 | .49 | |
| 35-44 | .65 | .70 | .75 | |
| >44 | .72 | .78 | .80 | |
[0262] In this table: S=zip codes beginning with 27, 28, 29, 40, 41, 42, 37, 38, 39, 35, 36, 30, 31, 32, 34, 70, 71, 73, 74, 75, 76, 77, 78, 79; MW=zip codes beginning with 58, 57, 55, 56, 53, 54, 59, 48, 49, 46, 47, 60, 61, 62, 82, 83, 63, 64, 65, 66, 67, 68, 69; and NE or W=all other zip codes.
[0263] If, however, the zip code provided by the individual also matches a zip code used in a “principle city”, the HOF determined from Table 4 is, in some embodiments, multiplied by a factor of 0.785 to acknowledge the fact that home ownership in “principle cities” is 55% vs. 70% for the entire country. The U.S. Census Bureau defines which cities are considered to be “principle cities.” Examples include New York City, San Francisco, and Boston.
[0264] With knowledge of the individual's zip code, a value for the variable STAC may be obtained from the following table:
[0265]
| TABLE 5 | ||
|---|---|---|
| STATE AVERAGE CARDS (STAC) | ||
| State | Avg. cards | |
| New Hampshire | 5.3 | |
| New Jersey | 5.2 | |
| Massachusetts | 5.1 | |
| Rhode Island | 5.0 | |
| Minnesota | 4.9 | |
| Connecticut | 4.8 | |
| Maine | 4.7 | |
| North Dakota | 4.6 | |
| Michigan | 4.5 | |
| New York | 4.5 | |
| Pennsylvania | 4.5 | |
| South Dakota | 4.5 | |
| Florida | 4.4 | |
| Maryland | 4.4 | |
| Montana | 4.4 | |
| Nebraska | 4.4 | |
| Ohio | 4.4 | |
| Vermont | 4.4 | |
| Hawaii | 4.3 | |
| Virginia | 4.3 | |
| Idaho | 4.2 | |
| Illinois | 4.2 | |
| Wyoming | 4.2 | |
| Colorado | 4.1 | |
| Delaware | 4.1 | |
| Utah | 4.1 | |
| Wisconsin | 4.1 | |
| United States | 4.0 | |
| Iowa | 4.0 | |
| Missouri | 4.0 | |
| Nevada | 4.0 | |
| Washington | 4.0 | |
| California | 3.9 | |
| Kansas | 3.9 | |
| Oregon | 3.9 | |
| Indiana | 3.8 | |
| Alaska | 3.7 | |
| West Virginia | 3.6 | |
| Arkansas | 3.5 | |
| Arizona | 3.5 | |
| Kentucky | 3.5 | |
| North Carolina | 3.5 | |
| South Carolina | 3.5 | |
| Tennessee | 3.5 | |
| Georgia | 3.4 | |
| New Mexico | 3.4 | |
| Alabama | 3.3 | |
| Oklahoma | 3.3 | |
| Texas | 3.3 | |
| Louisiana | 3.2 | |
| District of | 3.0 | |
| Columbia | ||
| Mississippi | 3.0 | |
[0266] There is, however, a degree of uncertainty associated with the actual number of credit cards owned by a typical individual having the same age and residing at the same location as the individual interfacing with the system. By defining an upper limit for HS12 to be:
HS12=100−[Db20+Dcc(10*(1−e−(7/(3)))+Dhe(20*(1))]*1.2 (3)
and a lower limit to be:
HS12=100−[Db20+Dcc(10*(1−e−(7/(3)))+Dhe(20*(0))]*0.6, (4)
the individual may be told that his HS12 score (or full identity health score, HSfull, as described below) is “x” percent certain, where “x” may be determined from the following table:
HS12=100−[Db20+Dcc(10*(1−e−(7/(3)))+Dhe(20*(1))]*1.2 (3)
and a lower limit to be:
HS12=100−[Db20+Dcc(10*(1−e−(7/(3)))+Dhe(20*(0))]*0.6, (4)
the individual may be told that his HS12 score (or full identity health score, HSfull, as described below) is “x” percent certain, where “x” may be determined from the following table:
[0267]
| TABLE 6 | ||
|---|---|---|
| CERTAINTY OF IDENTITY HEALTH SCORE | ||
| State | Certainty | |
| New | 76.80% | |
| Hampshire | ||
| Massachusetts | 78.40% | |
| Minnesota | 79.31% | |
| Rhode Island | 78.63% | |
| Maine | 81.83% | |
| Vermont | 83.20% | |
| North Dakota | 82.06% | |
| New Jersey | 77.14% | |
| South Dakota | 82.29% | |
| Connecticut | 79.89% | |
| Montana | 82.86% | |
| Hawaii | 84.57% | |
| Pennsylvania | 81.83% | |
| Nebraska | 82.63% | |
| Iowa | 85.37% | |
| Maryland | 81.83% | |
| Ohio | 81.94% | |
| Michigan | 81.03% | |
| Wisconsin | 84.23% | |
| Wyoming | 83.43% | |
| Virginia | 82.97% | |
| New York | 81.26% | |
| Utah | 83.43% | |
| Delaware | 83.89% | |
| Missouri | 84.34% | |
| Illinois | 83.43% | |
| Idaho | 82.17% | |
| Florida | 81.49% | |
| Washington | 84.34% | |
| Kansas | 84.80% | |
| United States | 54.72% | |
| Oregon | 55.40% | |
| West Virginia | 58.43% | |
| Alaska | 57.11% | |
| Kentucky | 58.94% | |
| Colorado | 54.60% | |
| Indiana | 56.88% | |
| Nevada | 55.22% | |
| Tennessee | 59.79% | |
| California | 56.77% | |
| Arkansas | 59.91% | |
| South Carolina | 60.19% | |
| Alabama | 61.33% | |
| Georgia | 60.42% | |
| North Carolina | 59.96% | |
| New Mexico | 61.22% | |
| Oklahoma | 62.02% | |
| Louisiana | 88.57% | |
| Mississippi | 90.51% | |
| Arizona | 85.83% | |
| Texas | 87.54% | |
| District of | 89.71% | |
| Columbia | ||
[0268] In one embodiment, additional information may be requested from the individual through survey questions in order to calculate a more certain identity health score for the individual. For example, referring back to equation (1), the variable “likelihood” may be determined using the following table:
[0269]
| TABLE 7 | ||||
|---|---|---|---|---|
| ATTRIBUTES AND CALCULATION OF LIKELIHOOD | ||||
| Low | ||||
| Questions for the | None | (LV = | Medium | High |
| Individual | (LV = 0.00) | 0.05) | (LV = 0.10) | (LV = 0.15) |
| Number of | 0 | 1 | 2 or 3 | 4 or more |
| residents 13 years | ||||
| of age or older | ||||
| living in the | ||||
| individual's | ||||
| residence, other | ||||
| than the individual | ||||
| himself and his | ||||
| spouse? | ||||
| Live check or | Direct | Live | ||
| Direct Deposit? | Deposit | |||
| Bank statement | Electronic | Paper | ||
| delivered | ||||
| electronically or | ||||
| in paper? | ||||
| Credit Card | Electronic | Paper | ||
| statement | ||||
| delivered | ||||
| electronically or | ||||
| in paper? | ||||
| Number of prior | 0 | 1 | 2 | 3 or more |
| addresses? | ||||
| Moved in last | Changed | Did not | ||
| year? | address | change | ||
| with U.S. | address with | |||
| Postal | U.S. Postal | |||
| Service | Service | |||
| Mailbox | Locked or | Unsecured | ||
| Security? | Post | |||
| Office | ||||
| Box | ||||
| Breach | No | Indirect | Direct | |
| Affiliation? | connection | |||
[0270] Referring to Table 7, questions for individuals are listed in the left-hand column, while possible responses to those questions (attributes) are listed in one or more of the four columns labeled “None,” “Low,” “Medium,” or “High.” For each particular question, if the individual's response lies in the column “None,” the likelihood value (“LV”) for that question is 0.00. If, however, the response lies in the column “Low,” “Medium,” or “High,” the likelihood value (“LV”) for that question is 0.05, 0.10, or 0.15, respectively. The variable “likelihood” for equation (1) above may then be determined by summing the various likelihood values (“LV”) for each of the questions as follows:
Likelihood=0.4+ΣLV (5)
Likelihood=0.4+ΣLV (5)
[0271] The attributes for what is considered to be, in one embodiment, a typical individual are italicized in Table 7. As shown, the exemplary typical individual has 1 resident 13 years of age or older living at the individual's residence (LV=0.05), direct deposit (LV=0.00), paper delivery of bank (LV=0.10) and credit card (LV=0.10) statements, 1 prior address (LV=0.05), and an unsecured mailbox (LV=0.10). Accordingly, the variable “likelihood” for this exemplary typical individual is calculated as follows:
Likelihood=0.4+ΣLV=0.4+0.05+0.00+0.10+0.10+0.05 +0.10=0.8 (6)
Likelihood=0.4+ΣLV=0.4+0.05+0.00+0.10+0.10+0.05 +0.10=0.8 (6)
[0272] Having calculated HS12 for the individual, the individual's full identity health score may then be determined from the following equation:
HSfull=(HS12)*(1−(Event Score)/120) (7)
HSfull=(HS12)*(1−(Event Score)/120) (7)
[0273] In equation (7), HS12 is multiplied by a factor that depends upon particular events that are detected for the individual. In one embodiment, it is assumed that detected events are the acts of identity thieves until the individual indicates otherwise. In one embodiment, given the events that may be detected for the individual (the left-most column in Table 8 below) and follow-on events (the two middle columns in Table 8 below), a value is assigned to each possible event/follow-on event combination (the right-most column in Table 8 below). The variable “Event Score” in equation (7) is, in one embodiment, then set equal to the value for the particular event/follow-on event combination experienced by the individual. Where the individual experiences more than one event/follow-on event combination, the highest value in the right-most column of Table 8 below for those events/follow-on events may be assigned to the variable “Event Score” in equation (7).
[0274]
| TABLE 8 | |||
|---|---|---|---|
| EVENT SCORE | |||
| Event | Followed by | Followed by | Value |
| New phone for | Nothing | 6 | |
| address | |||
| New phone for | Change of address | 12 | |
| address | |||
| New phone for | New home loan | 1 if refinanced, 2 if | |
| address | application | home equity, 5 if | |
| cell phone and | |||
| refinanced, 10 if cell | |||
| phone and home equity | |||
| New phone for | Credit card | 49 if cell, 7 if | |
| address | application | landline | |
| New phone for | Loan discharged | New home loan | 18 |
| address | |||
| New phone for | Loan discharged | Title transfer | 36 |
| address | |||
| New phone for | 2nd mortgage | 45 | |
| address | |||
| New phone for | Social security | 42 | |
| address | number out of | ||
| channel | |||
| New phone for | Credit card number | 42 | |
| address | out of channel | ||
| Phone is changed | 16 | ||
| Phone is changed | Change of address | 4 | |
| Phone is changed | Home loan | 25 | |
| application | |||
| Phone is changed | Credit card | 25 | |
| application | |||
| Phone is changed | Equity credit line | 25 | |
| application | |||
| Phone is changed | Loan discharged | 45 | |
| Phone is changed | 2nd mortgage | 24 | |
| Phone is changed | Social security | 42 | |
| number out of | |||
| channel | |||
| Phone is changed | Credit card number | 42 | |
| out of channel | |||
| New telephone for | 12 | ||
| name or social | |||
| security number | |||
| New telephone for | Change of address | 24 | |
| name or social | |||
| security number | |||
| New telephone for | Home loan | 30 | |
| name or social | application | ||
| security number | |||
| New telephone for | Credit card | 36 | |
| name or social | application | ||
| security number | |||
| New telephone for | Equity credit line | 36 | |
| name or social | application | ||
| security number | |||
| New telephone for | Loan discharged | 36 | |
| name or social | |||
| security number | |||
| New telephone for | 2nd mortgage | 45 | |
| name or social | |||
| security number | |||
| New telephone for | Social security | 42 | |
| name or social | number out of | ||
| security number | channel | ||
| New telephone for | Credit card number | 42 | |
| name or social | out of channel | ||
| security number | |||
| Telephone records | 40 | ||
| purchased | |||
| Telephone records | Change of address | 56 | |
| purchased | |||
| Telephone records | New home loan | 36 | |
| purchased | application | ||
| Telephone records | Equity credit line | 36 | |
| purchased | application | ||
| Telephone records | Loan discharged | 18 | |
| purchased | |||
| Telephone records | Credit card | 18 | |
| purchased | application | ||
| Telephone records | 2nd mortgage | 45 | |
| purchased | |||
| Telephone records | Social security | 30 | |
| purchased | number out of | ||
| channel | |||
| Telephone records | Credit card number | 42 | |
| purchased | out of channel | ||
| Name/social | New address is | 40 | |
| security number | existing address | ||
| appears on national | |||
| change of address | |||
| list | |||
| Name/social | Neither address tied | 40 | |
| security number | to subscriber | ||
| appears on national | |||
| change of address | |||
| list | |||
| Name/social | Old address not tied | 40 | |
| security number | to subscriber | ||
| appears on national | |||
| change of address | |||
| list | |||
| Name/social | From existing | 32 | |
| security number | address to new | ||
| appears on national | address | ||
| change of address | |||
| list | |||
| Name/social | Credit card | 42 | |
| security number | application | ||
| appears on national | |||
| change of address | |||
| list | |||
| Name/social | Equity credit line | 36 | |
| security number | application | ||
| appears on national | |||
| change of address | |||
| list | |||
| Name/social | Loan discharged | 30 | |
| security number | |||
| appears on national | |||
| change of address | |||
| list | |||
| Name/social | 2nd mortgage | 36 | |
| security number | |||
| appears on national | |||
| change of address | |||
| list | |||
| Name/social | Social security | 42 | |
| security number | number out of | ||
| appears on national | channel | ||
| change of address | |||
| list | |||
| Name/social | Credit card number | 42 | |
| security number | out of channel | ||
| appears on national | |||
| change of address | |||
| list | |||
| New mortgage on | Property previously | 35 | |
| subscriber property | not mortgaged | ||
| New mortgage on | New phone number, | 14 if landline | |
| subscriber property | No change of | 49 if mobile | |
| address | |||
| New mortgage on | New phone number, | 14 if landline | |
| subscriber property | change of address | 56 if mobile | |
| New mortgage on | Change of address | 42 | |
| subscriber property | |||
| New mortgage on | Equity credit line | 36 | |
| subscriber property | application | ||
| New mortgage on | Credit card | 36 | |
| subscriber property | application | ||
| New mortgage on | Loan discharged | 36 | |
| subscriber property | |||
| New mortgage on | Social security | 63 | |
| subscriber property | number out of | ||
| channel | |||
| New mortgage on | Credit card number | 63 | |
| subscriber property | out of channel | ||
| New mortgage tied | No other active | 30 | |
| to subscriber name | loans | ||
| or social security | |||
| number | |||
| New mortgage tied | No other active | Change of address | 48 |
| to subscriber name | loans | ||
| or social security | |||
| number | |||
| New mortgage tied | One or more other | 24 | |
| to subscriber name | active loans | ||
| or social security | |||
| number | |||
| New mortgage tied | New cell phone | 56 | |
| to subscriber name | |||
| or social security | |||
| number | |||
| New mortgage tied | New landline phone | 14 | |
| to subscriber name | |||
| or social security | |||
| number | |||
| New mortgage tied | New equity credit | 36 | |
| to subscriber name | line | ||
| or social security | |||
| number | |||
| New mortgage tied | Loan discharge >7 | 36 | |
| to subscriber name | year | ||
| or social security | |||
| number | |||
| New mortgage tied | Credit card | 36 | |
| to subscriber name | application | ||
| or social security | |||
| number | |||
| New mortgage tied | Social security | 56 | |
| to subscriber name | number out of | ||
| or social security | channel | ||
| number | |||
| New mortgage tied | Credit card number | 56 | |
| to subscriber name | out of channel | ||
| or social security | |||
| number | |||
| New property tied to | 30 | ||
| name/social security | |||
| number | |||
| New property tied to | Property sale | 24 | |
| name/social security | |||
| number | |||
| New property tied to | New mortgage loan | 30 | |
| name/social security | |||
| number | |||
| New property tied to | New mortgage loan | Change of address | 48 |
| name/social security | |||
| number | |||
| New property tied to | New loan of X | Existing loan of Y | 24 |
| name/social security | |||
| number | |||
| New property tied to | New loan of X | Existing loans of y | 18 |
| name/social security | and z . . . | ||
| number | |||
| New property tied to | New cell phone | 64 | |
| name/social security | |||
| number | |||
| New property tied to | New landline phone | 4 | |
| name/social security | |||
| number | |||
| New property tied to | New credit card | 36 | |
| name/social security | application | ||
| number | |||
| New property tied to | New equity credit | 36 | |
| name/social security | line | ||
| number | |||
| New property tied to | Loan discharge >7 | 36 | |
| name/social security | years | ||
| number | |||
| New property tied to | Social security | 63 | |
| name/social security | number out of | ||
| number | channel | ||
| New property tied to | Credit card number | 63 | |
| name/social security | out of channel | ||
| number | |||
| Loan (mortgage) | 36 | ||
| tied to subscriber | |||
| address discharged | |||
| loan (mortgage) tied | Change of address | 36 | |
| to subscriber | |||
| address discharged | |||
| loan (mortgage) tied | New loan | 25 | |
| to subscriber | |||
| address discharged | |||
| loan (mortgage) tied | New cell phone | 64 | |
| to subscriber | |||
| address discharged | |||
| loan (mortgage) tied | New landline phone | 4 | |
| to subscriber | |||
| address discharged | |||
| loan (mortgage) tied | New equity credit | 36 | |
| to subscriber | line application | ||
| address discharged | |||
| loan (mortgage) tied | New credit card | 36 | |
| to subscriber | application | ||
| address discharged | |||
| loan (mortgage) tied | Social security | 63 | |
| to subscriber | number out of | ||
| address discharged | channel | ||
| loan (mortgage) tied | Credit card number | 63 | |
| to subscriber | out of channel | ||
| address discharged | |||
| loan (mortgage) tied | 36 | ||
| to subscriber | |||
| name/social security | |||
| number discharged | |||
| loan (mortgage) tied | Change of address | 36 | |
| to subscriber | |||
| name/social security | |||
| number discharged | |||
| loan (mortgage) tied | New loan | 25 | |
| to subscriber | |||
| name/social security | |||
| number discharged | |||
| loan (mortgage) tied | New cell phone | 64 | |
| to subscriber | |||
| name/social security | |||
| number discharged | |||
| loan (mortgage) tied | New landline phone | 4 | |
| to subscriber | |||
| name/social security | |||
| number discharged | |||
| loan (mortgage) tied | New equity credit | 36 | |
| to subscriber | line application | ||
| name/social security | |||
| number discharged | |||
| loan (mortgage) tied | New credit card | 36 | |
| to subscriber | application | ||
| name/social security | |||
| number discharged | |||
| loan (mortgage) tied | Social security | 63 | |
| to subscriber | number out of | ||
| name/social security | channel | ||
| number discharged | |||
| loan (mortgage) tied | Credit card number | 63 | |
| to subscriber | out of channel | ||
| name/social security | |||
| number discharged | |||
| Social security | 100 | ||
| number on Social | |||
| Security | |||
| Administration | |||
| Master death file | |||
| Social security | New cell phone | 45 | |
| number on Social | |||
| Security | |||
| Administration | |||
| Master death file | |||
| Social security | New landline phone | 45 | |
| number on Social | |||
| Security | |||
| Administration | |||
| Master death file | |||
| Social security | New equity credit | 81 | |
| number on Social | line application | ||
| Security | |||
| Administration | |||
| Master death file | |||
| Social security | New credit card | 49 | |
| number on Social | application | ||
| Security | |||
| Administration | |||
| Master death file | |||
| Social security | Loan discharged >7 | 72 | |
| number on Social | years | ||
| Security | |||
| Administration | |||
| Master death file | |||
| Social security | Loan discharged <7 | 72 | |
| number on Social | years | ||
| Security | |||
| Administration | |||
| Master death file | |||
| Social security | New loan on | No change of | 56 |
| number on Social | previously | address | |
| Security | unmortgaged | ||
| Administration | property | ||
| Master death file | |||
| Social security | Social security | 63 | |
| number on Social | number out of | ||
| Security | channel | ||
| Administration | |||
| Master death file | |||
| Social security | Credit card number | 63 | |
| number on Social | out of channel | ||
| Security | |||
| Administration | |||
| Master death file | |||
| New lien attached to | 35 | ||
| property | |||
| New lien attached to | New cell phone | 63 | |
| property | |||
| New lien attached to | New landline phone | 35 | |
| property | |||
| New lien attached to | New equity credit | 49 | |
| property | line application | ||
| New lien attached to | New credit card | 36 | |
| property | application | ||
| New lien attached to | Loan discharged >7 | 42 | |
| property | years | ||
| New lien attached to | Loan discharged <7 | New mortgage | 21 |
| property | years | ||
| New lien attached to | New loan on | 42 | |
| property | previously | ||
| unmortgaged | |||
| property | |||
| New lien attached to | Social security | 63 | |
| property | number out of | ||
| channel | |||
| New lien attached to | Credit card number | 63 | |
| property | out of channel | ||
| New court judgment | 42 | ||
| against subscriber | |||
| New court judgment | New cell phone | 63 | |
| against subscriber | |||
| New court judgment | New landline phone | 35 | |
| against subscriber | |||
| New court judgment | New equity credit | 49 | |
| against subscriber | line application | ||
| New court judgment | New credit card | 36 | |
| against subscriber | application | ||
| New court judgment | Loan discharged >7 | 42 | |
| against subscriber | years | ||
| New court judgment | Loan discharged <7 | 21 | |
| against subscriber | years | ||
| New court judgment | New loan on | 42 | |
| against subscriber | previously | ||
| unmortgaged | |||
| property | |||
| New court judgment | Social Security | 63 | |
| against subscriber | Number out of | ||
| channel | |||
| New court judgment | Credit card number | 63 | |
| against subscriber | out of channel | ||
| New address for | 42 | ||
| Subscriber (not a | |||
| change of address) | |||
| New address for | Change of Address | 35 | |
| subscriber | |||
| New resident at sub | 35 | ||
| address | |||
| Resident removed | 9 | ||
| from subscriber | |||
| address | |||
| Social security | 100 | ||
| number out of | |||
| channel | |||
| Credit card number | 100 | ||
| out of channel | |||
| Subscriber Bank | 100 | ||
| reports breach | |||
| Subscriber | 100 | ||
| investment account | |||
| institution or | |||
| retirement account | |||
| holder reports | |||
| breach | |||
| Credit card | 36 | ||
| application with | |||
| Subscriber social | |||
| security number | |||
| Driver's license | 48 | ||
| issued in subscriber | |||
| name in subscriber | |||
| state | |||
| Driver's lice issued | 56 | ||
| in subscriber name | |||
| out of state | |||
| Automobile loan on | 35 | ||
| car registered to | |||
| subscriber | |||
| New car registration | 35 | ||
| with subscriber | |||
| social security | |||
| number | |||
| Boat loan on boat | 42 | ||
| registered to | |||
| subscriber | |||
| Boat registration on | 42 | ||
| subscriber's social | |||
| security number in | |||
| subscriber's home | |||
| state | |||
| Boat registration on | 49 | ||
| subscriber's social | |||
| security number not | |||
| in subscriber's | |||
| home state | |||
| Warrant issued in | 60 | ||
| name of subscriber | |||
| or using subscriber | |||
| social security | |||
| number | |||
[0275] Alternatively, the identity health score may be calculated based solely on geographic location. There is data that indicates that fraud per capita varies by region. Therefore, it may be possible to assign a risk factor based on regional factors such as zip code and/or metropolitan area and on 3 digit zip. For example, the ten metropolitan areas with the highest identity fraud rates are:
1. New York, N.Y. 100-104
2. Detroit, Mich. 481-482
3. Los Angeles, Calif. 900-901
4. Little Rock, Ark. 720-722
5. Greenville, Miss. 387
6. Atlanta, Ga. 300-303
7. Phoenix, Ariz. 850, 852, 853
8. Portland, Oreg. 970-972
9. Dallas, Tex. 751-753
10. Springfield, Ill. 625-627
[0276] In a different embodiment, other factors, shown in Table 9 below, may be used in calculating the identity health score. The number of steps that would need to be taken by a thief in order to invoke fraud (the third column from the left in Table 9 below) is provided. The potential monetary damage level, “s”, (with 1 being the lowest and 10 being the highest) and the difficulty to invoke fraud, “d”, (with 1 being the most difficult and 10 being the least difficult) are also provided for each of the factors. In one embodiment of the invention, the identity health score “HS” may calculated by the following equation:
HS=s*d (8)
In such an embodiment, the greater the value of HS, the greater the risk of identity theft to the individual in question.
HS=s*d (8)
In such an embodiment, the greater the value of HS, the greater the risk of identity theft to the individual in question.
[0277] The factors may be ranked based on the resulting identity health score, “HS” (the right-most column in Table 9 below). As can be seen, for the factor of inactive credit cards (the first row in Table 9 below), the identity health score, “HS,” is 15, which is assigned a rank of 6 for the factors listed in Table 9.
[0278]
| TABLE 9 | |||||
|---|---|---|---|---|---|
| HEALTH SCORE FACTORS AND RANK | |||||
| Potential | |||||
| monetary | Difficulty to | ||||
| damage | Number of steps | invoke fraud (d) | Score | ||
| Factors | level (s) | needed to invoke fraud | (1 is most difficult) | (=s * d) | Rank |
| Inactive | 5 | Get credit card | 3 | 15 | 6 |
| credit cards | number, change | ||||
| (guess 2 for | address, go to | ||||
| now) | town | ||||
| Inactive | 10 | Get checking | 3 | 30 | 3 |
| home equity | account number, | ||||
| credit line | wash checks, go to | ||||
| town | |||||
| Number of | 3 | Get credit card | 10 | 30 | 3 |
| residents | number, social | ||||
| older than 12 | security number, | ||||
| years of age | bank account | ||||
| living in the | numbers, provide | ||||
| individual's | to others | ||||
| residence, | |||||
| other than | |||||
| the | |||||
| individual | |||||
| himself and | |||||
| his spouse | |||||
| Live check | 6 | Find full social | 3 | 18 | 5 |
| or Direct | security number, | ||||
| Deposit | apply for credit, | ||||
| receive credit | |||||
| Paper | 5 | Intercept mail, get | 5 | 25 | 4 |
| delivery of | numbers, access | ||||
| bank and | accounts. | ||||
| credit card | |||||
| statement | |||||
| Home owner | 10 | Impersonate, | 1 | 10 | 7 |
| discharge loan and | |||||
| get new loan. | |||||
| Level of | 3 | Get credit card | 4 | 12 | 6 |
| affiliation | number and use. | ||||
| with known | Get social security | ||||
| breach | number and | ||||
| impersonate. | |||||
| Number of | 4 | Apply for credit | 8 | 32 | 2 |
| prior | card offers, receive | ||||
| addresses | card, use | ||||
| (nominal = 2) | |||||
| Moved in | 5 | Apply for credit | 8 | 40 | 1 |
| last year but | card offers, receive | ||||
| no change of | card, use | ||||
| address filed | |||||
| 5 | Intercept mail, get | 5 | 25 | 4 | |
| delivered to | numbers, access | ||||
| unlocked box | accounts. | ||||
[0279] Having described certain embodiments of the invention, it will be apparent to those of ordinary skill in the art that other embodiments incorporating the concepts disclosed herein may be used without departing from the spirit and scope of the invention. For example, although the examples and calculations presented herein have focused on the United States, they may just as easily be adapted for other countries and/or regions of the world. Accordingly, the described embodiments are to be considered in all respects as only illustrative and not restrictive.
Claims
What is claimed is:
1. A computing system for providing identity fraud risk indicia, the system comprising:
a fraud model subsystem that specifies patterns of events indicative of identity fraud, wherein each pattern comprises a type of fraud and information related to event timing;
a business rules subsystem that, based on the patterns of events, specifies rules to identify fraud;
a data aggregation subsystem that collects data input from a variety of sources, the data comprising demographic data for individuals, asset data for individuals, event occurrence data, identity theft statistical data, and personal data; and
a processor for executing computer readable instructions that, when executed, employ the rules to:
examine a static structure of a subset of the data that relates to an individual relative to underlying financial and physical assets and personal attributes of the individual;
correlate interconnectivity of the subset with events that have changed the static structure in the past;
correlate interconnectivity of the subset with new events discovered during a monitoring process; and
determine whether the events and the new events are correlative with at least one of the patterns based on the rules.
2. The system of claim 1, wherein the processor further executes computer readable instructions that provide a prediction of fraud events that are likely to occur.
3. The system of claim 2, wherein the prediction comprises a probability that such fraud events are likely to occur.
4. The system of claim 2, wherein the processor further executes computer readable instructions that provide recommendations of steps to be taken to avoid predicted fraud events.
5. The system of claim 1, wherein the processor further executes computer readable instructions that identify fraud events that are likely to occur.
6. The system of claim 5, wherein the identified fraud events are compared to fraud scenarios specified in the patterns of events indicative of identity fraud.
7. The system of claim 5, further comprising rulesets, and wherein the processor further executes computer readable instructions that use the rulesets to evaluate fraud events that have occurred.
8. The system of claim 1, further comprising a communication subsystem for communicating to the first individual fraud events that are likely to occur.
9. The system of claim 1, further comprising a communication subsystem for communicating with a financial organization.
10. The system of claim 1, further comprising a communication subsystem for alerting the first individual.
11. The system of claim 1, wherein the processor further executes computer readable instructions that cause at least some of the data input from the variety of sources to be normalized.
Patent Citations (420)
| Patent | Date | Inventor | Cited By |
|---|---|---|---|
| US5274547(A) | 1993-12-01 | Zoffel et al. | Applicant |
| US5323315(A) | 1994-06-01 | Highbloom | Applicant |
| US5696965(A) | 1997-12-01 | Dedrick | Applicant |
| US5742775(A) | 1998-04-01 | King | Applicant |
| US5752242(A) | 1998-05-01 | Havens | Applicant |
| US5809478(A) | 1998-09-01 | Greco et al. | Applicant |
| US5872921(A) | 1999-02-01 | Zahariev et al. | Applicant |
| US5878403(A) | 1999-03-01 | DeFrancesco et al. | Applicant |
| US5879297(A) | 1999-03-01 | Haynor et al. | Examiner |
| US5943666(A) | 1999-08-01 | Kleewein et al. | Applicant |
| US5999907(A) | 1999-12-01 | Donner | Applicant |
| US6023694(A) | 2000-02-01 | Kouchi et al. | Applicant |
| US6029149(A) | 2000-02-01 | Dykstra et al. | Applicant |
| US6029194(A) | 2000-02-01 | Tilt | Applicant |
| US6125985(A) | 2000-10-01 | Amdahl et al. | Applicant |
| US6142283(A) | 2000-11-01 | Amdahl et al. | Applicant |
| US6144988(A) | 2000-11-01 | Kappel | Applicant |
| US6249228(B1) | 2001-06-01 | Shirk et al. | Applicant |
| US6253203(B1) | 2001-06-01 | O'Flaherty et al. | Applicant |
| US6263447(B1) | 2001-07-01 | French et al. | Applicant |
| US6282658(B2) | 2001-08-01 | French et al. | Applicant |
| US6317783(B1) | 2001-11-01 | Freishtat et al. | Applicant |
| US6321339(B1) | 2001-11-01 | French et al. | Applicant |
| US6448889(B1) | 2002-09-01 | Hudson | Applicant |
| US6456984(B1) | 2002-09-01 | Demoff et al. | Applicant |
| US6496936(B1) | 2002-12-01 | French et al. | Applicant |
| US6532459(B1) | 2003-03-01 | Berson | Applicant |
| US6553495(B1) | 2003-04-01 | Johansson et al. | Applicant |
| US6612488(B2) | 2003-09-01 | Suzuki | Applicant |
| US6700220(B2) | 2004-03-01 | Bayeur et al. | Applicant |
| US6740875(B1) | 2004-05-01 | Ishikawa et al. | Applicant |
| US6811082(B2) | 2004-11-01 | Wong | Applicant |
| US6857073(B2) | 2005-02-01 | French et al. | Applicant |
| US6866586(B2) | 2005-03-01 | Oberberger et al. | Applicant |
| US6871287(B1) | 2005-03-01 | Ellingson | Applicant |
| US6913194(B2) | 2005-07-01 | Suzuki | Applicant |
| US6918038(B1) | 2005-07-01 | Smith et al. | Applicant |
| US6930707(B2) | 2005-08-01 | Bates et al. | Applicant |
| US6965997(B2) | 2005-11-01 | Dutta | Applicant |
| US6991174(B2) | 2006-01-01 | Zuili | Applicant |
| US7028052(B2) | 2006-04-01 | Chapman et al. | Applicant |
| US7035855(B1) | 2006-04-01 | Kilger et al. | Applicant |
| US7083090(B2) | 2006-08-01 | Zuili | Applicant |
| US7089592(B2) | 2006-08-01 | Adjaoute | Applicant |
| US7092891(B2) | 2006-08-01 | Maus et al. | Applicant |
| US7104444(B2) | 2006-09-01 | Suzuki | Applicant |
| US7174335(B2) | 2007-02-01 | Kameda | Applicant |
| US7212995(B2) | 2007-05-01 | Schulkins | Applicant |
| US7222779(B1) | 2007-05-01 | Pineda-Sanchez et al. | Applicant |
| US7225977(B2) | 2007-06-01 | Davis | Examiner |
| US7234156(B2) | 2007-06-01 | French et al. | Applicant |
| US7240363(B1) | 2007-07-01 | Ellingson | Applicant |
| US7246067(B2) | 2007-07-01 | Austin et al. | Applicant |
| US7254560(B2) | 2007-08-01 | Singhal | Applicant |
| US7272857(B1) | 2007-09-01 | Everhart | Applicant |
| US7290704(B1) | 2007-11-01 | Ball et al. | Examiner |
| US7314162(B2) | 2008-01-01 | Carr et al. | Applicant |
| US7370044(B2) | 2008-05-01 | Mulhern et al. | Applicant |
| US7386506(B2) | 2008-06-01 | Aoki et al. | Examiner |
| US7392534(B2) | 2008-06-01 | Lu et al. | Applicant |
| US7398915(B1) | 2008-07-01 | Pineda-Sanchez et al. | Applicant |
| US7438226(B2) | 2008-10-01 | Helsper et al. | Applicant |
| US7458508(B1) | 2008-12-01 | Shao et al. | Examiner |
| US7466235(B1) | 2008-12-01 | Kolb et al. | Applicant |
| US7480631(B1) | 2009-01-01 | Merced et al. | Applicant |
| US7481363(B2) | 2009-01-01 | Zuili | Applicant |
| US7490052(B2) | 2009-02-01 | Kilger et al. | Applicant |
| US7497374(B2) | 2009-03-01 | Helsper et al. | Applicant |
| US7533808(B2) | 2009-05-01 | Song et al. | Applicant |
| US7536346(B2) | 2009-05-01 | Aliffi et al. | Applicant |
| US7540021(B2) | 2009-05-01 | Page | Applicant |
| US7542993(B2) | 2009-06-01 | Satterfield et al. | Applicant |
| US7543740(B2) | 2009-06-01 | Greene et al. | Applicant |
| US7548886(B2) | 2009-06-01 | Kirkland et al. | Applicant |
| US7552467(B2) | 2009-06-01 | Lindsay | Applicant |
| US7562814(B1) | 2009-07-01 | Shao et al. | Applicant |
| US7568616(B2) | 2009-08-01 | Zuili | Applicant |
| US7591425(B1) | 2009-09-01 | Zuili et al. | Applicant |
| US7593891(B2) | 2009-09-01 | Kornegay et al. | Applicant |
| US7606790(B2) | 2009-10-01 | Levy | Applicant |
| US7610229(B1) | 2009-10-01 | Kornegay et al. | Applicant |
| US7630932(B2) | 2009-12-01 | Danaher et al. | Applicant |
| US7636853(B2) | 2009-12-01 | Cluts et al. | Applicant |
| US7644868(B2) | 2010-01-01 | Hare | Applicant |
| US7647344(B2) | 2010-01-01 | Skurtovich, Jr. et al. | Applicant |
| US7647645(B2) | 2010-01-01 | Edeki et al. | Applicant |
| US7653593(B2) | 2010-01-01 | Zarikian et al. | Applicant |
| US7673793(B2) | 2010-03-01 | Greene et al. | Applicant |
| US7676418(B1) | 2010-03-01 | Chung et al. | Applicant |
| US7676433(B1) | 2010-03-01 | Ross et al. | Applicant |
| US7686214(B1) | 2010-03-01 | Shao et al. | Applicant |
| US7689007(B2) | 2010-03-01 | Bous et al. | Applicant |
| US7701364(B1) | 2010-04-01 | Zilberman | Applicant |
| US7707163(B2) | 2010-04-01 | Anzalone et al. | Applicant |
| US7708200(B2) | 2010-05-01 | Helsper et al. | Applicant |
| US7711636(B2) | 2010-05-01 | Robida et al. | Applicant |
| US7720750(B2) | 2010-05-01 | Brody et al. | Applicant |
| US7735125(B1) | 2010-06-01 | Alvarez et al. | Applicant |
| US7742982(B2) | 2010-06-01 | Chaudhuri et al. | Applicant |
| US7747559(B2) | 2010-06-01 | Leitner et al. | Applicant |
| US7752236(B2) | 2010-07-01 | Williams et al. | Applicant |
| US7761384(B2) | 2010-07-01 | Madhogarhia | Applicant |
| US7774270(B1) | 2010-08-01 | MacCloskey | Applicant |
| US7779456(B2) | 2010-08-01 | Dennis et al. | Applicant |
| US7779457(B2) | 2010-08-01 | Taylor | Applicant |
| US7788184(B2) | 2010-08-01 | Kane | Applicant |
| US7792864(B1) | 2010-09-01 | Rice | Applicant |
| US7793835(B1) | 2010-09-01 | Coggeshall et al. | Applicant |
| US7801828(B2) | 2010-09-01 | Candella et al. | Applicant |
| US7805391(B2) | 2010-09-01 | Friedlander et al. | Applicant |
| US7840459(B1) | 2010-11-01 | Loftesness et al. | Applicant |
| US7860769(B2) | 2010-12-01 | Benson | Applicant |
| US7865439(B2) | 2011-01-01 | Seifert et al. | Applicant |
| US7865937(B1) | 2011-01-01 | White et al. | Applicant |
| US7870078(B2) | 2011-01-01 | Clark et al. | Applicant |
| US7870599(B2) | 2011-01-01 | Pemmaraju | Applicant |
| US7874488(B2) | 2011-01-01 | Parkinson | Applicant |
| US7882548(B2) | 2011-02-01 | Heath et al. | Applicant |
| US7890433(B2) | 2011-02-01 | Singhal | Applicant |
| US7904360(B2) | 2011-03-01 | Evans | Applicant |
| US7904367(B2) | 2011-03-01 | Chung et al. | Applicant |
| US7908242(B1) | 2011-03-01 | Achanta | Applicant |
| US7912865(B2) | 2011-03-01 | Akerman et al. | Applicant |
| US7917715(B2) | 2011-03-01 | Tallman, Jr. | Applicant |
| US7925582(B1) | 2011-04-01 | Kornegay et al. | Applicant |
| US7929951(B2) | 2011-04-01 | Stevens | Applicant |
| US7933835(B2) | 2011-04-01 | Keane et al. | Applicant |
| US7950577(B1) | 2011-05-01 | Daniel | Applicant |
| US7962404(B1) | 2011-06-01 | Metzger, II et al. | Applicant |
| US7962467(B2) | 2011-06-01 | Howard et al. | Applicant |
| US7970679(B2) | 2011-06-01 | Kasower | Applicant |
| US7970698(B2) | 2011-06-01 | Gupta et al. | Applicant |
| US7971246(B1) | 2011-06-01 | Emigh et al. | Applicant |
| US7975299(B1) | 2011-07-01 | Balducci et al. | Applicant |
| US7983979(B2) | 2011-07-01 | Holland, IV | Applicant |
| US7984849(B2) | 2011-07-01 | Berghel et al. | Applicant |
| US7988043(B2) | 2011-08-01 | Davis | Applicant |
| US7991201(B2) | 2011-08-01 | Bous et al. | Applicant |
| US7991689(B1) | 2011-08-01 | Brunzell et al. | Applicant |
| US7995994(B2) | 2011-08-01 | Khetawat et al. | Applicant |
| US7996521(B2) | 2011-08-01 | Chamberlain et al. | Applicant |
| US8001034(B2) | 2011-08-01 | Chung et al. | Applicant |
| US8001042(B1) | 2011-08-01 | Brunzell et al. | Applicant |
| US8001153(B2) | 2011-08-01 | Skurtovich, Jr. et al. | Applicant |
| US8005749(B2) | 2011-08-01 | Ginsberg | Applicant |
| US8006291(B2) | 2011-08-01 | Headley et al. | Applicant |
| US8009873(B2) | 2011-08-01 | Chapman | Applicant |
| US8019678(B2) | 2011-09-01 | Wright et al. | Applicant |
| US8020763(B1) | 2011-09-01 | Kowalchyk et al. | Applicant |
| US8024271(B2) | 2011-09-01 | Grant | Applicant |
| US8027518(B2) | 2011-09-01 | Baker et al. | Applicant |
| US8028168(B2) | 2011-09-01 | Smithies et al. | Applicant |
| US8028326(B2) | 2011-09-01 | Palmer et al. | Applicant |
| US8028329(B2) | 2011-09-01 | Whitcomb | Applicant |
| US8028896(B2) | 2011-10-01 | Carter et al. | Applicant |
| US8032449(B2) | 2011-10-01 | Hu et al. | Applicant |
| US8032927(B2) | 2011-10-01 | Ross | Applicant |
| US8037512(B2) | 2011-10-01 | Wright et al. | Applicant |
| US8042159(B2) | 2011-10-01 | Basner et al. | Applicant |
| US8042193(B1) | 2011-10-01 | Piliouras | Applicant |
| US8049596(B2) | 2011-11-01 | Sato | Applicant |
| US8055667(B2) | 2011-11-01 | Levy | Applicant |
| US8056128(B1) | 2011-11-01 | Dingle et al. | Applicant |
| US8058972(B2) | 2011-11-01 | Mohanty | Applicant |
| US8060915(B2) | 2011-11-01 | Voice et al. | Applicant |
| US8065525(B2) | 2011-11-01 | Zilberman | Applicant |
| US8069053(B2) | 2011-11-01 | Gervais et al. | Applicant |
| US8069084(B2) | 2011-11-01 | Mackouse | Applicant |
| US8069256(B2) | 2011-11-01 | Rasti | Applicant |
| US8069485(B2) | 2011-11-01 | Carter | Applicant |
| US2002/0010684(A1) | 2002-01-01 | Moskowitz | Applicant |
| US2002/0019938(A1) | 2002-02-01 | Aarons | Applicant |
| US2002/0042879(A1) | 2002-04-01 | Gould et al. | Applicant |
| US2002/0062185(A1) | 2002-05-01 | Runge et al. | Applicant |
| US2002/0062281(A1) | 2002-05-01 | Singhal | Applicant |
| US2002/0073044(A1) | 2002-06-01 | Singhal | Applicant |
| US2002/0077178(A1) | 2002-06-01 | Oberberger et al. | Applicant |
| US2002/0080256(A1) | 2002-06-01 | Bates et al. | Applicant |
| US2002/0087460(A1) | 2002-07-01 | Hornung | Applicant |
| US2002/0130176(A1) | 2002-09-01 | Suzuki | Applicant |
| US2002/0138751(A1) | 2002-09-01 | Dutta | Applicant |
| US2002/0173994(A1) | 2002-11-01 | Ferguson | Applicant |
| US2003/0004879(A1) | 2003-01-01 | Demoff et al. | Applicant |
| US2003/0009426(A1) | 2003-01-01 | Ruiz-Sanchez | Applicant |
| US2003/0057278(A1) | 2003-03-01 | Wong | Applicant |
| US2003/0070101(A1) | 2003-04-01 | Buscemi | Applicant |
| US2003/0143980(A1) | 2003-07-01 | Choi et al. | Applicant |
| US2003/0149744(A1) | 2003-08-01 | Bierre et al. | Applicant |
| US2003/0222500(A1) | 2003-12-01 | Bayeur et al. | Applicant |
| US2003/0233278(A1) | 2003-12-01 | Marshall | Applicant |
| US2004/0004117(A1) | 2004-01-01 | Suzuki | Applicant |
| US2004/0005912(A1) | 2004-01-01 | Hubbe et al. | Applicant |
| US2004/0026496(A1) | 2004-02-01 | Zuili | Applicant |
| US2004/0107363(A1) | 2004-06-01 | Monteverde | Applicant |
| US2004/0111335(A1) | 2004-06-01 | Black et al. | Applicant |
| US2004/0149820(A1) | 2004-08-01 | Zuili | Applicant |
| US2004/0149827(A1) | 2004-08-01 | Zuili | Applicant |
| US2004/0153656(A1) | 2004-08-01 | Cluts et al. | Applicant |
| US2004/0153663(A1) | 2004-08-01 | Clark et al. | Examiner |
| US2004/0158723(A1) | 2004-08-01 | Root | Applicant |
| US2004/0230538(A1) | 2004-11-01 | Clifton et al. | Applicant |
| US2004/0234117(A1) | 2004-11-01 | Tibor | Applicant |
| US2004/0243539(A1) | 2004-12-01 | Skurtovich et al. | Applicant |
| US2004/0243567(A1) | 2004-12-01 | Levy | Applicant |
| US2004/0254868(A1) | 2004-12-01 | Kirkland et al. | Applicant |
| US2005/0001028(A1) | 2005-01-01 | Zuili | Applicant |
| US2005/0021476(A1) | 2005-01-01 | Candella et al. | Applicant |
| US2005/0021519(A1) | 2005-01-01 | Ghouri | Applicant |
| US2005/0050577(A1) | 2005-03-01 | Westbrook et al. | Applicant |
| US2005/0065874(A1) | 2005-03-01 | Lefner et al. | Applicant |
| US2005/0071282(A1) | 2005-03-01 | Lu et al. | Applicant |
| US2005/0081052(A1) | 2005-04-01 | Washington | Applicant |
| US2005/0086161(A1) | 2005-04-01 | Gallant | Applicant |
| US2005/0097364(A1) | 2005-05-01 | Edeki et al. | Applicant |
| US2005/0125226(A1) | 2005-06-01 | Magee | Applicant |
| US2005/0125686(A1) | 2005-06-01 | Brandt | Applicant |
| US2005/0144143(A1) | 2005-06-01 | Freiberg | Applicant |
| US2005/0154671(A1) | 2005-07-01 | Doan et al. | Applicant |
| US2005/0165667(A1) | 2005-07-01 | Cox | Applicant |
| US2005/0187863(A1) | 2005-08-01 | Whinery et al. | Applicant |
| US2005/0203885(A1) | 2005-09-01 | Chenevich et al. | Applicant |
| US2005/0216953(A1) | 2005-09-01 | Ellingson | Applicant |
| US2005/0242173(A1) | 2005-11-01 | Suzuki | Applicant |
| US2005/0257261(A1) | 2005-11-01 | Shraim et al. | Applicant |
| US2005/0279869(A1) | 2005-12-01 | Barklage | Applicant |
| US2006/0004622(A1) | 2006-01-01 | Fanelli et al. | Applicant |
| US2006/0004663(A1) | 2006-01-01 | Singhal | Applicant |
| US2006/0041464(A1) | 2006-02-01 | Powers et al. | Applicant |
| US2006/0045105(A1) | 2006-03-01 | Dobosz et al. | Applicant |
| US2006/0047605(A1) | 2006-03-01 | Ahmad | Applicant |
| US2006/0047725(A1) | 2006-03-01 | Bramson | Applicant |
| US2006/0064374(A1) | 2006-03-01 | Helsper et al. | Applicant |
| US2006/0069697(A1) | 2006-03-01 | Shraim et al. | Applicant |
| US2006/0074798(A1) | 2006-04-01 | Din et al. | Applicant |
| US2006/0075028(A1) | 2006-04-01 | Zager et al. | Applicant |
| US2006/0080230(A1) | 2006-04-01 | Freiberg | Applicant |
| US2006/0080263(A1) | 2006-04-01 | Willis et al. | Applicant |
| US2006/0089905(A1) | 2006-04-01 | Song et al. | Applicant |
| US2006/0101508(A1) | 2006-05-01 | Taylor | Applicant |
| US2006/0143073(A1) | 2006-06-01 | Engel et al. | Applicant |
| US2006/0144924(A1) | 2006-07-01 | Stover | Applicant |
| US2006/0149580(A1) | 2006-07-01 | Helsper et al. | Applicant |
| US2006/0149674(A1) | 2006-07-01 | Cook et al. | Applicant |
| US2006/0168202(A1) | 2006-07-01 | Reshef et al. | Applicant |
| US2006/0178971(A1) | 2006-08-01 | Owen et al. | Applicant |
| US2006/0178982(A1) | 2006-08-01 | Ramsey et al. | Applicant |
| US2006/0179004(A1) | 2006-08-01 | Fuchs | Applicant |
| US2006/0200855(A1) | 2006-09-01 | Willis | Applicant |
| US2006/0224409(A1) | 2006-10-01 | Leininger et al. | Applicant |
| US2006/0239512(A1) | 2006-10-01 | Petrillo | Applicant |
| US2006/0239513(A1) | 2006-10-01 | Song et al. | Applicant |
| US2006/0255914(A1) | 2006-11-01 | Westman | Applicant |
| US2006/0271456(A1) | 2006-11-01 | Romain et al. | Applicant |
| US2006/0271457(A1) | 2006-11-01 | Romain et al. | Examiner |
| US2006/0271507(A1) | 2006-11-01 | Anzalone et al. | Applicant |
| US2006/0271568(A1) | 2006-11-01 | Balkir et al. | Applicant |
| US2006/0273158(A1) | 2006-12-01 | Suzuki | Applicant |
| US2006/0282285(A1) | 2006-12-01 | Helsper et al. | Applicant |
| US2006/0282372(A1) | 2006-12-01 | Endres et al. | Applicant |
| US2006/0282395(A1) | 2006-12-01 | Leibowitz | Applicant |
| US2006/0287902(A1) | 2006-12-01 | Helsper et al. | Applicant |
| US2006/0294023(A1) | 2006-12-01 | Lu | Applicant |
| US2007/0011100(A1) | 2007-01-01 | Libin et al. | Applicant |
| US2007/0016521(A1) | 2007-01-01 | Wang | Applicant |
| US2007/0016522(A1) | 2007-01-01 | Wang | Applicant |
| US2007/0038568(A1) | 2007-02-01 | Greene et al. | Applicant |
| US2007/0040017(A1) | 2007-02-01 | Kozlay | Applicant |
| US2007/0040019(A1) | 2007-02-01 | Berghel et al. | Applicant |
| US2007/0043577(A1) | 2007-02-01 | Kasower | Applicant |
| US2007/0048765(A1) | 2007-03-01 | Abramson | Applicant |
| US2007/0050638(A1) | 2007-03-01 | Rasti | Applicant |
| US2007/0061273(A1) | 2007-03-01 | Greene et al. | Applicant |
| US2007/0072190(A1) | 2007-03-01 | Aggarwal | Applicant |
| US2007/0073622(A1) | 2007-03-01 | Kane | Applicant |
| US2007/0073630(A1) | 2007-03-01 | Greene et al. | Applicant |
| US2007/0078786(A1) | 2007-04-01 | Bous et al. | Applicant |
| US2007/0083460(A1) | 2007-04-01 | Bachenheimer | Applicant |
| US2007/0087795(A1) | 2007-04-01 | Aletto et al. | Applicant |
| US2007/0100774(A1) | 2007-05-01 | Abdon | Applicant |
| US2007/0106611(A1) | 2007-05-01 | Larsen | Applicant |
| US2007/0107050(A1) | 2007-05-01 | Selvarajan | Applicant |
| US2007/0109103(A1) | 2007-05-01 | Jedrey et al. | Applicant |
| US2007/0110282(A1) | 2007-05-01 | Millsapp | Applicant |
| US2007/0112667(A1) | 2007-05-01 | Rucker | Examiner |
| US2007/0112668(A1) | 2007-05-01 | Celano et al. | Examiner |
| US2007/0124270(A1) | 2007-05-01 | Page | Applicant |
| US2007/0157299(A1) | 2007-07-01 | Hare | Applicant |
| US2007/0174208(A1) | 2007-07-01 | Black et al. | Applicant |
| US2007/0179903(A1) | 2007-08-01 | Seinfeld et al. | Applicant |
| US2007/0180209(A1) | 2007-08-01 | Tallman | Applicant |
| US2007/0186276(A1) | 2007-08-01 | McRae et al. | Applicant |
| US2007/0198410(A1) | 2007-08-01 | Labgold et al. | Applicant |
| US2007/0205266(A1) | 2007-09-01 | Carr et al. | Applicant |
| US2007/0214037(A1) | 2007-09-01 | Shubert et al. | Applicant |
| US2007/0214076(A1) | 2007-09-01 | Robida et al. | Applicant |
| US2007/0219928(A1) | 2007-09-01 | Madhogarhia | Applicant |
| US2007/0220594(A1) | 2007-09-01 | Tulsyan | Applicant |
| US2007/0234427(A1) | 2007-10-01 | Gardner et al. | Applicant |
| US2007/0244807(A1) | 2007-10-01 | Andringa et al. | Applicant |
| US2007/0250704(A1) | 2007-10-01 | Hallam-Baker | Applicant |
| US2007/0250920(A1) | 2007-10-01 | Lindsay | Applicant |
| US2007/0266439(A1) | 2007-11-01 | Kraft | Examiner |
| US2007/0291995(A1) | 2007-12-01 | Rivera | Applicant |
| US2007/0292006(A1) | 2007-12-01 | Johnson | Applicant |
| US2007/0294104(A1) | 2007-12-01 | Boaz et al. | Applicant |
| US2008/0027857(A1) | 2008-01-01 | Benson | Applicant |
| US2008/0027858(A1) | 2008-01-01 | Benson | Applicant |
| US2008/0059236(A1) | 2008-03-01 | Cartier | Applicant |
| US2008/0059352(A1) | 2008-03-01 | Chandran | Applicant |
| US2008/0059366(A1) | 2008-03-01 | Fou | Applicant |
| US2008/0076386(A1) | 2008-03-01 | Khetawat et al. | Applicant |
| US2008/0098222(A1) | 2008-04-01 | Zilberman | Applicant |
| US2008/0103798(A1) | 2008-05-01 | Domenikos et al. | Applicant |
| US2008/0103799(A1) | 2008-05-01 | Domenikos et al. | Applicant |
| US2008/0103800(A1) | 2008-05-01 | Domenikos et al. | Applicant |
| US2008/0103811(A1) | 2008-05-01 | Sosa | Applicant |
| US2008/0103972(A1) | 2008-05-01 | Lanc | Applicant |
| US2008/0120237(A1) | 2008-05-01 | Lin | Applicant |
| US2008/0126116(A1) | 2008-05-01 | Singhai | Applicant |
| US2008/0162383(A1) | 2008-07-01 | Kraft | Applicant |
| US2008/0189789(A1) | 2008-08-01 | Lamontagne | Applicant |
| US2008/0208548(A1) | 2008-08-01 | Metzger et al. | Applicant |
| US2008/0208726(A1) | 2008-08-01 | Tsantes et al. | Applicant |
| US2008/0217400(A1) | 2008-09-01 | Portano | Applicant |
| US2008/0244717(A1) | 2008-10-01 | Jelatis et al. | Applicant |
| US2008/0288430(A1) | 2008-11-01 | Friedlander et al. | Applicant |
| US2008/0288790(A1) | 2008-11-01 | Wilson | Applicant |
| US2008/0294689(A1) | 2008-11-01 | Metzger et al. | Applicant |
| US2008/0296367(A1) | 2008-12-01 | Parkinson | Applicant |
| US2008/0296382(A1) | 2008-12-01 | Connell, II et al. | Applicant |
| US2008/0300877(A1) | 2008-12-01 | Gilbert et al. | Applicant |
| US2009/0007220(A1) | 2009-01-01 | Ormazabal et al. | Applicant |
| US2009/0018934(A1) | 2009-01-01 | Peng et al. | Applicant |
| US2009/0021349(A1) | 2009-01-01 | Errico et al. | Applicant |
| US2009/0024417(A1) | 2009-01-01 | Marks et al. | Applicant |
| US2009/0024636(A1) | 2009-01-01 | Shiloh | Applicant |
| US2009/0024663(A1) | 2009-01-01 | McGovern | Examiner |
| US2009/0026270(A1) | 2009-01-01 | Connell, II et al. | Applicant |
| US2009/0079539(A1) | 2009-03-01 | Johnson | Applicant |
| US2009/0099960(A1) | 2009-04-01 | Robida et al. | Applicant |
| US2009/0106153(A1) | 2009-04-01 | Ezra | Applicant |
| US2009/0106846(A1) | 2009-04-01 | Dupray et al. | Applicant |
| US2009/0125439(A1) | 2009-05-01 | Zarikian et al. | Applicant |
| US2009/0126013(A1) | 2009-05-01 | Atwood et al. | Applicant |
| US2009/0138391(A1) | 2009-05-01 | Dudley et al. | Applicant |
| US2009/0141318(A1) | 2009-06-01 | Hughes | Applicant |
| US2009/0151005(A1) | 2009-06-01 | Bell et al. | Applicant |
| US2009/0158404(A1) | 2009-06-01 | Hahn et al. | Applicant |
| US2009/0204457(A1) | 2009-08-01 | Buhrmann et al. | Applicant |
| US2009/0205032(A1) | 2009-08-01 | Hinton et al. | Applicant |
| US2009/0216560(A1) | 2009-08-01 | Siegel | Applicant |
| US2009/0222362(A1) | 2009-09-01 | Stood et al. | Applicant |
| US2009/0222897(A1) | 2009-09-01 | Carow et al. | Applicant |
| US2009/0224875(A1) | 2009-09-01 | Rabinowitz et al. | Applicant |
| US2009/0224889(A1) | 2009-09-01 | Aggarwal et al. | Applicant |
| US2009/0226056(A1) | 2009-09-01 | Vlachos et al. | Applicant |
| US2009/0248198(A1) | 2009-10-01 | Siegel et al. | Applicant |
| US2009/0248497(A1) | 2009-10-01 | Hueter | Applicant |
| US2009/0254484(A1) | 2009-10-01 | Forero et al. | Applicant |
| US2009/0257595(A1) | 2009-10-01 | de Cesare et al. | Applicant |
| US2009/0259560(A1) | 2009-10-01 | Bachenheimer | Applicant |
| US2009/0259588(A1) | 2009-10-01 | Lindsay | Applicant |
| US2009/0259855(A1) | 2009-10-01 | de Cesare et al. | Applicant |
| US2009/0261189(A1) | 2009-10-01 | Ellis, Jr. | Applicant |
| US2009/0270126(A1) | 2009-10-01 | Liu | Applicant |
| US2009/0271617(A1) | 2009-10-01 | Song et al. | Applicant |
| US2009/0272801(A1) | 2009-11-01 | Connell, II et al. | Applicant |
| US2009/0276244(A1) | 2009-11-01 | Baldwin, Jr. et al. | Applicant |
| US2009/0281945(A1) | 2009-11-01 | Shakkarwar | Applicant |
| US2009/0281951(A1) | 2009-11-01 | Shakkarwar | Applicant |
| US2009/0307778(A1) | 2009-12-01 | Mardikar | Applicant |
| US2009/0326972(A1) | 2009-12-01 | Washington | Applicant |
| US2010/0004965(A1) | 2010-01-01 | Eisen | Applicant |
| US2010/0024037(A1) | 2010-01-01 | Grzymala-Busse et al. | Applicant |
| US2010/0031030(A1) | 2010-02-01 | Kao et al. | Applicant |
| US2010/0037308(A1) | 2010-02-01 | Lin et al. | Applicant |
| US2010/0042526(A1) | 2010-02-01 | Martinov | Applicant |
| US2010/0085146(A1) | 2010-04-01 | Johnson | Applicant |
| US2010/0088338(A1) | 2010-04-01 | Pavoni, Jr. et al. | Applicant |
| US2010/0095357(A1) | 2010-04-01 | Willis et al. | Applicant |
| US2010/0100406(A1) | 2010-04-01 | Lim | Applicant |
| US2010/0132043(A1) | 2010-05-01 | Bjorn et al. | Applicant |
| US2010/0145847(A1) | 2010-06-01 | Zarikian et al. | Applicant |
| US2010/0169210(A1) | 2010-07-01 | Bous et al. | Applicant |
| US2010/0169947(A1) | 2010-07-01 | Sarmah et al. | Applicant |
| US2010/0205662(A1) | 2010-08-01 | Ibrahim et al. | Applicant |
| US2010/0218255(A1) | 2010-08-01 | Ritman et al. | Applicant |
| US2010/0229225(A1) | 2010-09-01 | Sarmah et al. | Applicant |
| US2010/0229230(A1) | 2010-09-01 | Edeki et al. | Applicant |
| US2010/0241501(A1) | 2010-09-01 | Marshall | Applicant |
| US2010/0250364(A1) | 2010-09-01 | Song et al. | Applicant |
| US2010/0250411(A1) | 2010-09-01 | Ogrodski | Applicant |
| US2010/0275265(A1) | 2010-10-01 | Fiske et al. | Applicant |
| US2010/0293090(A1) | 2010-11-01 | Domenikos et al. | Applicant |
| US2010/0302157(A1) | 2010-12-01 | Zilberman | Applicant |
| US2010/0306101(A1) | 2010-12-01 | Lefner et al. | Applicant |
| US2010/0313273(A1) | 2010-12-01 | Freas | Applicant |
| US2010/0332292(A1) | 2010-12-01 | Anderson | Applicant |
| US2011/0016042(A1) | 2011-01-01 | Cho et al. | Applicant |
| US2011/0040983(A1) | 2011-02-01 | Grzymala-Busse et al. | Applicant |
| US2011/0060905(A1) | 2011-03-01 | Stack et al. | Applicant |
| US2011/0119291(A1) | 2011-05-01 | Rice | Applicant |
| US2011/0270727(A1) | 2011-11-01 | Kasower | Applicant |
| US2011/0276496(A1) | 2011-11-01 | Neville et al. | Applicant |
| US2011/0289032(A1) | 2011-11-01 | Crooks et al. | Applicant |
| US2011/0289322(A1) | 2011-11-01 | Rasti | Applicant |
| US2011/0295721(A1) | 2011-12-01 | MacDonald | Applicant |
| US2011/0295750(A1) | 2011-12-01 | Rammal | Applicant |
| US2011/0296529(A1) | 2011-12-01 | Bhanoo et al. | Applicant |
| US2011/0302412(A1) | 2011-12-01 | Deng et al. | Applicant |
| US2011/0302641(A1) | 2011-12-01 | Hald et al. | Applicant |
| EP1519281 | 2005-03-01 | Applicant | |
| JP10-257177 | 1998-09-01 | Applicant | |
| WO-01/04799 | 2001-01-01 | Applicant | |
| WO-03/010688 | 2003-02-01 | Applicant | |
| WO-2005/076135 | 2005-08-01 | Applicant | |
| WO-2006/017937 | 2006-02-01 | Applicant | |
| WO-97/114108 | 2006-06-01 | Applicant | |
| WO-2006/058217 | 2006-06-01 | Applicant | |
| WO-2006/065882 | 2006-06-01 | Applicant |
Non-Patent Literature (23)
- “ID Analytics ID Network”, from www.idanalytics.com, as retrieved from Internet Archive, dated Nov. 20, 2005 or earlier; attached as “ID Network (IDNb)”.Examiner
- “Intersections, Inc. Identity Guard”, from www.intersections.com and www.identityguard.com, as retrieved from Internet Archive, dated Nov. 25, 2005 or earlier; attached as “Identity Guard (IDG)”.Examiner
- www.idcops.com; retrieved from www.archive.org any linkage Feb. 16, 2007.Examiner
- U.S. Appl. No. 09/557,252, filed Apr. 24, 2000, Page.Applicant
- Caruso, Denise. “Digital Commerce: Personal Information is Like Gold in the Internet Economy, and the Rush is on to Both Exploit It and Protect It.” New York Times, ProQuest Historical Newspapers—The New York Times 1851—2004, (Mar. 1, 1999), p. C4.Applicant
- Clausing, Jeri. “Report Rings Bell About Privacy on the Internet.” New York Times, ProQuest Historical Newspapers—The New York Times 1851—2004, (Feb. 7, 2000), p. C10.Applicant
- Bose, Ranjit. “Intelligent Technologies for Managing Fraud and Identity Theft.” Proceedings of the Third International Conference on Information Technology: New Generations (ITNG'06), IEEE Computer Society, (Apr. 10-12, 2006), pp. 446-451.Applicant
- Goth, Greg. “Identity Theft Solutions Disagree on Problem.” IEEE Distributed Systems Online, IEEE Computer Society (Aug. 2005), vol. 6, Issue 8, pp. 1541-4922.Applicant
- Holz, Thorsten. “A Short Visit to the Bot Zoo.” IEEE Security & Privacy Magazine, IEEE Computer Society (May/Jun. 2005), vol. 3, Issue 3, pp. 76-79.Applicant
- Lenton, Dominic. “Stand and Deliver: Modern Day Highwaymen Are Making a Mint From Cybercrime.” IEEE Review, (May 2005), vol. 51, Issue 5, pp. 24-25.Applicant
- McCarty, Bill. “Automated Identity Theft.” IEEE Security & Privacy, IEEE Computer Society, (Sep./Oct. 2003), vol. 1, Issue 5, pp. 89-92.Applicant
- Wang, WenJie et al. “A Contextual Framework for Combating Identity Theft.” IEEE Security & Privacy Magazine, IEEE Computer Society, (Mar./Apr. 2006), vol. 4, Issue 2, pp. 30-38.Applicant
- “Pioneers in Identity Theft Protection: Privacy ProBot Technology” [online]. Identity Cops Inc. [retrieved Oct. 11, 2007]. Retrieved from the Internet: <http://www.idcops.com/Default.htm>, 4 pages.Applicant
- “Identity Cops Wins ‘Best New Technology of the Year’” [online]. Identity Cops Inc., Jul. 15, 2005 [retrieved Oct. 11, 2007]. Retrieved from the Internet <http://www.idcops.com/Press%20Release%20July%2017.05%20MESDA%20award.pdf>, 1 page.Applicant
- “Our Technology: Privacy ProBot” [online]. Identity Cops Inc. [retrieved Oct. 11, 2007]. Retrieved from the Internet: <http://www.idcops.com/ourtechnology.html>, 5 pages.Applicant
- “IDetective Individual Subscriptions” [online]. Identity Cops Inc. [retrieved Oct. 11, 2007]. Retrieved from the Internet: <http://www.idcops.com/individual.html>, 4 pages.Applicant
- “Corporate Services” [online]. Identity Cops Inc. [retrieved Oct. 11, 2007]. Retrieved from the Internet: <http://www.idcops.com/corporate.html>, 6 pages.Applicant
- “Facts About Identity Theft” [online]. Identity Cops Inc. [retrieved Oct. 11, 2007]. Retrieved from the Internet: <http://www.idcops.com/idtheftfacts.html>, 10 pages.Applicant
- “ID Theft Arena” [online]. Identity Cops Inc. [retrieved Oct. 11, 2007]. Retrieved from the Internet: <http://www.idcops.com/idtheftarena.html>, 3 pages.Applicant
- “Identity Cops Launches New Product Line and Website,” [online]. Identity Cops Inc., Dec. 6, 2005 [retrieved Oct. 11, 2007]. Retrieved from the Internet: <http://www.idcops.com/Press%20Release%20Dec%206.2005.pdf>, 1 page.Applicant
- “Identity Cops Introduces its Newest Service for Corporate Identity Theft Protection and Recovery,” [online]. Identity Cops Inc., Apr. 3, 2006 [retrieved Oct. 11, 2007]. Retrieved from the Internet: <http://www.idcops.com/PR%204.3.06%20IDT%20Response.pdf>, 1 page.Applicant
- “Identity Cops Inc. Launches “IDENTI-Fl” Financial Institution Field Intelligence” [online]. Identity Cops Inc., Mar. 5, 2007 [retrieved Oct. 11, 2007]. Retrieved from the Internet: <http://www.idcops.com/Press%20Release%20March%2007%20IDENTIFI.pdf>, 2 pages.Applicant
- “Demonstration—Identity Cops Inc.: Self Defense for the 21st Century” [online]. Identity Cops Inc. [retrieved Oct. 13, 2007] <http://www.idcops.com/privacyconsole.html>, 66 pages.Applicant