Application profile verification across computing devices
By examining and utilizing the state and transitions of applications on user devices, combined with risk scoring and contextual factors, authentication requirements are dynamically adjusted, addressing security vulnerabilities in existing authentication systems under complex network threats and achieving a more robust authentication method.
Patent Information
- Application Number
- CN202580027629.1
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2024-05-29
- Filing Date
- 2025-03-08
- Publication Date
- 2026-11-17
AI Technical Summary
Existing multi-factor authentication systems remain vulnerable to malicious attacks when facing complex network threats. Traditional authentication methods such as passwords and PIN codes are insufficient to provide adequate security, especially in SIM card swapping attacks, where security vulnerabilities caused by OTP leaks are difficult to prevent.
By examining and leveraging the state and transitions of multiple applications installed on a user's device, combined with the characteristics of the application ecosystem, a personalized security layer is employed for authentication. Application state is determined using standardized and custom APIs or hard-coded information, and authentication requirements are dynamically adjusted based on risk scoring and contextual factors to enhance security.
It provides enhanced security against unauthorized access and fraud, prevents SIM swapping attacks, and ensures the robustness and adaptability of the authentication process to different risk levels of transactions.
Smart Images

Figure CN123125592A_ABST
Abstract
Description
Technical Field
[0001] The embodiments involve authentication. Some embodiments involve authenticating transactions on the first application using information (e.g., state or state transitions) from one or more applications different from the first application. Background Technology
[0002] In the modern digital age, transaction authentication has become a crucial aspect of ensuring security and trust across various online and mobile platforms. Traditionally, transaction authentication has relied heavily on single-factor methods, such as passwords or PINs, which may not provide sufficient security against sophisticated cyber threats on their own. As financial transactions, personal data exchanges, and other sensitive activities increasingly move online, there is a growing need for more robust authentication methods that can effectively prevent unauthorized access and fraud. Multi-factor authentication (MFA) systems have been developed to attempt to address these issues. MFA systems require users to provide multiple forms of verification before they can process a transaction. These MFA systems typically combine two or more of the things the user knows (such as a password) and the things the user possesses. Attached Figure Description
[0003] In accompanying drawings that are not necessarily drawn to scale, the same reference numerals may describe similar components in different views. The same numbers with different letter suffixes may represent different instances of similar components. The accompanying drawings generally illustrate, by way of example and not limitation, the various embodiments discussed in this document.
[0004] Figure 1 The diagram illustrates an example authentication relationship diagram based on some examples of this disclosure.
[0005] Figure 2 The diagram illustrates a system for authentication using application state, based on some examples of this disclosure.
[0006] Figure 3 The diagram illustrates a system for authentication using application state, based on some examples of this disclosure.
[0007] Figure 4 The diagram illustrates a system for authentication using application state, based on some examples of this disclosure.
[0008] Figure 5 The diagram illustrates a context-based <application, state> tuple relationship according to some examples of this disclosure.
[0009] Figure 6 The diagram illustrates how application state changes are used to authenticate transactions, based on some examples of this disclosure.
[0010] Figure 7 The illustration shows a transaction authentication component according to some examples of this disclosure.
[0011] Figure 8 This is a flowchart illustrating a method for authenticating transactions on a computing device by verifying the state of an auxiliary application, based on some examples of this disclosure.
[0012] Figure 9 This is a flowchart illustrating a method for authenticating transactions on a computing device by verifying state changes of an auxiliary application, based on some examples of this disclosure.
[0013] Figure 10 This is a flowchart illustrating a method for authenticating transactions on a computing device by verifying the state of multiple applications, based on some examples of this disclosure.
[0014] Figure 11 This is a flowchart illustrating methods for establishing applications and states for authenticating transactions, based on some examples of this disclosure.
[0015] Figure 12 This is a block diagram illustrating an example of a machine on which one or more embodiments can be implemented. Detailed Implementation
[0016] Despite the widespread use of MFA systems, malicious users can still gain access to user accounts. For example, dictionary attacks and password leaks can allow malicious users to determine the passwords of legitimate users. SIM card swapping, a technique where attackers use social engineering to transfer control of a user's telephone service to their own telephone device, allows malicious users to intercept one-time passwords (OTPs) sent via text messages to the user's mobile phone. Due to these attacks, new authentication methods are needed to ensure authentication that is both seamless and secure.
[0017] Some examples disclose methods, systems, and machine-readable media for enhancing transaction authentication of transactions of a first application by checking that the state of one or more other applications matches a pre-specified state, or that one or more of those applications transition their state within a pre-specified time period. For example, the pre-specified state may correspond to an application installed on (e.g., a user's) specified device and having an authentication session with that specified user. By using the authentication state or state transitions of other applications for transaction processing, the system provides a robust authentication framework that leverages the characteristics of a user's personal application ecosystem to provide enhanced security against unauthorized access and fraud. This approach addresses the limitations of traditional authentication methods by adding a personalized security layer that is more difficult for attackers to replicate than a traditional MFA. The use of state checks on other applications addresses the technical weaknesses of traditional authentication systems.
[0018] The authentication can be established by first identifying the applications installed on one or more devices on the user's device and their possible corresponding states. Then, security criteria can be applied to evaluate which applications and which specific states of those applications meet the security criteria to authenticate a given transaction. This evaluation considers factors such as transaction sensitivity and the security characteristics of the applications. The resulting applications and states are stored in a transaction authorization data record, which outlines the applications used to authenticate the transaction and their states (or state transitions). Additionally, the user can gain the option to interact with the system by submitting input to accept, reject, or modify the applications and / or their states used to authenticate the transaction. This user input can be used to further customize the authentication process, thereby achieving a personalized security scheme that matches the user's preferences and the specific security needs of each transaction.
[0019] In the authentication system, "application state" is defined as the various conditions or states that an application may be in on a user's device, used to determine whether a transaction can be authenticated. In some examples, primary states may include: Installed: The application is installed on the user's device. Login (Authentication) State: This state indicates that the user actively logs into the application using verified authentication credentials. Logout (Inactive) State: In this state, the user is not logged into the application, meaning there is no active session, and the application is not ready to perform actions requiring user authentication. Background (Passive) State: Here, the application is not actively used but runs in the background. It can still receive updates and notifications, but user interaction is minimal. Error or Suspended State: This state occurs when the application encounters problems such as errors, suspensions due to security issues, or other operational anomalies that may affect its functionality. In some examples, one or more states may be acceptable for authenticating transactions. For example, the Login and Passive states may allow authentication, while the Logout and Error states may not.
[0020] In the authentication system, standardized and / or custom APIs are used to determine the possible states of an application at set times or periodically. These APIs can interact directly with the application on the user's device or with the server providing the application services for those applications. Standardized APIs can be defined for applications to determine and query application states for authentication purposes. Standardized APIs provide consistent and generalizable information across a wide array of applications, capturing common states such as 'logged in,' 'logged out,' 'active,' or 'inactive.' This provides broad compatibility and facilitates the integration of different applications into the system. For applications that do not implement standardized APIs, custom APIs can be programmed into the authentication system for specific applications.
[0021] In other examples, instead of using APIs or in addition to APIs, the system may incorporate hard-coded information about the application to define specific expected states. This hard-coding, based on predefined knowledge about the application's behavior and characteristics, provides a baseline of state information that enhances the system's ability to quickly and accurately assess the application's security posture.
[0022] Once all possible states are identified through these APIs, the system allows the application of security criteria to determine which states are considered secure enough to participate in the authentication process for a given transaction. In some examples, application states can be normalized from application-specific states to corresponding authentication system states. This can be achieved, for example, using pre-defined rules or pre-defined transformation tables.
[0023] In some examples, the application state may involve a user having an authenticated session with the application. In some examples, the authenticated session may not be account-specific. That is, if a specific transaction on the first application is authenticated by having an authentication state with the second application, then any account authenticated using the second application can satisfy the application state requirement for authenticating the specific transaction. In other examples, the system may require a specific account to be in an authentication state using the second application. A specific account can be pre-specified through explicit user input. In this setup, the user is prompted to directly enter their corresponding username or identifier for another application into the first application. Then, the identifier of the specific account in the second application is "linked" or "correlated" to the account in the first application. The account identifier can be stored in a transaction authorization data record.
[0024] The transaction authorization data record stores the applications, states, and / or state changes required to authorize each potential transaction for an application. For example, the transaction authorization data record may list up to 10 different applications, each associated with one or more states that meet authentication criteria. During the authentication process, the system can verify that all listed applications are in one of their corresponding required states for authentication. Alternatively, the system can selectively use only a subset of these applications for authentication. For example, the system can randomly select a specified number of applications from all applications for a particular transaction. For successful authentication, the randomly selected applications in the subset must be in a specified state.
[0025] In some examples, the number of applications in the subset can be random. In other examples, the system can identify a threshold, which can be pre-specified or selected based on a formula that considers the risk of the transaction. The transaction can be authenticated if more than the threshold number of applications among the applications listed in the transaction authorization data record are in the required state. In yet another example, the system can utilize the transaction's risk score and the corresponding security score of the application. That is, each <application, state> combination can be scored with the authentication security level it provides (e.g., by rules, or manually by an administrator). The subset can be selected such that the sum of the <application, state> scores equals or exceeds the transaction risk score. A larger risk score increases the number of applications and / or the security level required for authentication. The risk score can be related to contextual factors of the transaction, including time of day, perceived risk of the transaction, user's geographic location, and historical security data associated with the user's account. By adjusting authentication requirements based on these contextual elements, the system can provide appropriate security for high-risk transactions and streamline the process for lower-risk activities. This context-sensitive scheme ensures that the authentication process adapts in real time to the environment surrounding each transaction.
[0026] For example, if the transaction occurs at a time of day when the user is expected to be asleep, the risk score will increase, requiring additional verification, such as authentication using a more secure application, or additional authentication by requiring authentication with more applications than when the transaction occurs at a time of day when the user is expected to be awake. Similarly, if the transaction occurs at a location where the user does not typically reside, the risk score may increase, potentially requiring additional verification, such as authentication using a more secure application, or additional authentication by requiring authentication with more applications than when the transaction occurs at a location where the user is expected to be. These factors can be combined. Therefore, if both the time and location of the transaction are unusual for the user, even more stringent authentication requirements may be required.
[0027] In some examples, the applications can all run on the same device. That is, the application used for authentication can be on the same device as the application authenticating the transaction. In other examples, the applications can be on different devices.
[0028] In some examples, authentication of the state of other applications can be performed on the computing device where the application executing the transaction to be authenticated is located. For example, the application may locally store the transaction authorization data records. In these examples, the application may utilize one or more APIs to implement inter-process communication to query the application state of other applications. In other examples, the authentication may occur on a web-based server providing web-based services to the application. In these examples, the web-based service of the first application may query one or more web-based servers that provide web-based services to other applications.
[0029] In some examples, the application can be on different devices. Embodiments where the application for authenticating transactions is on a device separate from the device for performing the transactions are useful in scenarios where a user is attempting a transaction on an untrusted device, such as a publicly available computing device. This disclosure enhances security by requiring that a transaction be authenticated on a first application (e.g., a web application) on a first computing device (e.g., an untrusted device), while other applications on other devices (e.g., trusted devices such as mobile phones) are in a specific state. This ensures that subsequent users on the untrusted device, or eavesdroppers stealing credentials on the untrusted device, cannot gain access to the transaction if they cannot simultaneously access the application on the trusted device to put it in the appropriate state.
[0030] In other examples, a transaction might require an application not only to be in a specific initial state but also to transition to a second state within a pre-specified time period. In some examples, this state change can be a direct result of user interaction or action. For instance, an application might need to transition from an inactive or logged-out state to an active or logged-in state, initiated by the user entering credentials or participating in a specific activity within the application. Other example activities used for transitioning to different states include sending text messages, sending emails, calling numbers, changing preferences, activating UI controls, etc. This requirement for state transitions adds an extra layer of verification, confirming that the individual interacting with the application is indeed an authorized user. This approach enhances security by ensuring full verification of both the user's presence and activity before processing any sensitive transactions on a potentially compromised device. Using state transitions (which can also be stored in transaction authorization data records) to transition the application's state on a trusted device can also be useful if the transaction occurs on an untrusted device. Therefore, if an eavesdropper (e.g., using a keylogger, shoulder-peeping, or other techniques) attempts to compromise a user's account after the user has performed a transaction on an untrusted device, they will also have to manipulate applications on the trusted device that may not be under the attacker's control.
[0031] This authentication system can also be extended to prevent and / or mitigate the use of SIM exchange attacks that exploit SMS-based One-Time Password (OTP) two-factor authentication. For example, SMS applications can be enhanced to incorporate the authentication methods disclosed herein. In these examples, displaying the received OTP code could be a transaction verified using the presence and state of other applications on the device. If the other applications are not in the appropriate state, the SMS is not displayed. If the other applications are in the appropriate state, the SMS is displayed.
[0032] In these examples, the transaction displaying the SMS can be linked to another transaction (e.g., a transaction requesting OTP authentication) within a second application (e.g., an application requesting OTP authentication). In these examples, the second application or its server can perform authentication against the SMS application and signal to the SMS application whether to display the SMS. In other examples, the second application or its server can provide transaction authorization data records to the SMS application or a server associated with the SMS application (e.g., a cellular carrier server), and the SMS application or server can perform authentication. This protects the code from devices that are not the user's device. That is, although an attacker may have compromised the user's SIM and could receive the user's voice calls and text messages, they are unlikely to have the application required to display SMS activity on their device and in the correct state. In some examples, in addition to not displaying the SMS, the message can also be deleted, making it inaccessible to the attacker. In yet another example, the SMS application or the second application can notify the second application server that the SMS cannot be displayed and the OTP can be canceled.
[0033] In other examples, SMS may not even be sent by the application server of the second application unless the cloud-based server (e.g., the application server of the second application) is able to verify that the required application exists and is in the appropriate state.
[0034] The authentication methods disclosed herein can also utilize local dialer applications and / or SMS applications as transactions on devices that require specific states to authenticate legitimate users. In the case of SIM swapping, the local dialer and / or SMS applications may not be in the appropriate state because these applications may be unable to connect to the network, as the network may reject their connection attempts. Thus, the application performing the transaction may cause the transaction to fail, warning the user that their SIM may be compromised.
[0035] As previously described, the applications and states required to authenticate a particular transaction may differ each time. That is, a subset of tuples is selected from the entire pool of possible <application, state> tuples for authentication. The identity and number of applications selected in this subset may be randomized based on geolocation, fraud-based indications (e.g., by requesting more applications and / or by requesting more authentication states for those applications), the type of transaction (e.g., based on the “risk” of the transaction), and / or other aspects.
[0036] Figure 1 The diagram illustrates an example authentication relationship diagram 100 according to some examples of this disclosure. Figure 1 In the diagram, five applications are represented by nodes (circles): Application A 120, Application B 130, Application C 140, Application D 150, and Application E 110. Within each application, a thick dashed circle represents a possible state that the specific application within that application might be in. Application state refers to the current condition or state of the software application at a given point in time, including all data and information defining its current configuration or execution context. Figure 1 In the diagram, application A 120 has possible states: S1 122 and S2 124; application B 130 has possible states: S1 132, S2 134, and S3 136; application C has possible states: S1 144 and S3 142; and application D has possible states: S1 152, S2 154, and S4 156. States with the same numbers across different applications (e.g., S1 122, 132, 144, and 152) can be the same state, equivalent states, or different states.
[0037] Instead of showing the state within application E 110, the non-thick dashed circles indicate two possible transaction types: transactions T1 112 and T2 114. A "transaction" refers to any action or series of actions performed by a user through an application that causes a change in the state or data within the system. This includes, but is not limited to: financial operations such as transfers and payments, requests for access to sensitive information, or any other interactive process requiring verification or authentication. Transactions are typically (but not always) initiated by the user and processed by the system, where they can interact with various other applications or services to complete the operation.
[0038] exist Figure 1In this model, each transaction is connected via edges to one or more states of one or more other applications. These edges represent authorization relationships between applications and states used to authenticate the transaction. When an application splits into more than one state, it can be in any of the states required for successful authentication. For example, to successfully authenticate transaction T1 112, application A 120 must be in state S1 122, and application B 130 can be in state S2 134 or S3 136. In some examples, all applications must be in the states indicated by the edges to authenticate the transaction; however, in other examples, only a subset of applications must be in the states indicated by the edges. Figure 1 In order to authenticate transaction T2 114, application A 120 must be in state S1122, application C 140 must be in state S1 144, and application D can be in state S2 154 or state S4 156.
[0039] Figure 2 Figure 200 illustrates a system for authentication using application state, according to some examples of this disclosure. Each component of the system is communicatively coupled to other components via a network or communication bus. The system includes a user computing device 220 with five applications AEs and application servers for each application (Application A server 214, Application B server 210, Application C server 212, Application D server 216, Application E server 218). The application servers run application services that, together with the applications running on the user's device, provide services to the end user, other applications, or devices. The application services can provide the necessary infrastructure for running and managing application software, processing requests for operations, performing data processing, and delivering content or resources as needed. The application servers can operate in a networked environment and provide business logic and functional backends for software applications, facilitating a wide range of tasks from simple data retrieval to complex transaction processing. They typically include comprehensive security, transaction management, and application services.
[0040] Applications on a user's device can be dedicated applications or web-based applications. Dedicated applications, also known as native applications, are software programs specifically developed for a particular platform or device, installed directly onto said device, and designed to leverage its resources and features to provide optimized performance and an enhanced user experience. Web-based applications, on the other hand, are hosted on remote servers (such as application servers) and accessed via the internet using a web browser. These applications do not need to be installed on the user's device and offer the flexibility to be used across different platforms and devices, although they may rely heavily on an internet connection to function.
[0041] Application E on user computing device 220 can request to execute transaction T1. This request is sent to application E server 218, which provides application services to application E. Application E server 218 can locate the transaction authorization data record for transaction T1. In some examples, the data record can be user-specific. That is, a user account authenticated using application E can have a different transaction authorization data record for transaction T1 than other users. Figure 2 In the examples shown, applications A, C, and D are used to authenticate transaction T1. In these examples, the application service of application E, represented by application server 218, contacts the application services hosting applications A, C, and D to determine the status of each application on user computing device 220 (or, in some other examples, another device). These services then respond with status information. The application service of application E can then evaluate whether the application is in an acceptable state to approve transaction T1. If the application is in an acceptable state, the transaction is approved and an approval message is sent to application E. The operation of executing the transaction can then be performed by the application service for application E or by application E itself. If the application is not in an acceptable state, the transaction is rejected, and a rejection message can be sent to application E. Application E can then notify the user of the rejection.
[0042] In some examples, application E can then notify the user of the rejection, and in some examples, inform the user of what needs to be fixed (e.g., how to change the state of other applications to the desired state). In other examples, application E may not notify the user how to fix the problem. The latter option may be safer, but at the cost of user-friendliness.
[0043] In some examples, various application services may store state information of the applications running on the user's device locally (e.g., in a data structure). In other examples, various application services may send messages to the applications on the user's device (these messages are not shown for clarity).
[0044] Figure 3Figure 300 illustrates a system for authentication using application state, according to some examples of this disclosure. Figure 300 shows in-device authentication, where, in this example application E 320, the application authenticating the transaction contacts other applications executing on the device to obtain their state information in order to make an authentication decision. In this example, application E 320 contacts applications A 312, C 318, and D 316, but not application B 314. In these examples, transaction table 322 may store one or more transaction authorization data records for the transaction. In some examples, these messages may be sent and received via inter-process communication according to one or more APIs.
[0045] although Figure 2 and Figure 3 Alternative methods for verifying the application's state are shown, but Figure 2 and Figure 3 They can be used in combination. For example, some transactions can be like... Figure 3 In this way, verification is done locally, and other transactions can be verified by network-based services, such as... Figure 2 As shown in the diagram. This can be based on transaction type. For example, risky transactions can be verified by a network-based service, while less risky transactions can be verified locally. In other examples, the transaction can be verified by a network-based service unless the network-based service is unavailable (e.g., due to network issues), in which case the transaction can be verified locally. In some examples, the application itself can directly contact various application services for other applications.
[0046] Figure 4 Figure 400 illustrates a system for authentication using application state, according to some examples of this disclosure. Figure 4 In this context, application E executes on the first computing device 420. In some examples, the first computing device 420 may be an untrusted computing device. Figure 4 In one example, the first application E executes a transaction authenticated using the application state of an application executed on the second computing device 422. In some examples, the second computing device 422 is a user's mobile device.
[0047] Application E, executing on the first computing device 420, requests the execution of transaction T1 from application E server 416. Application E server 416 consults the transaction authorization data record and determines that applications A, C, and D must be in a specific state on the second computing device 422. Figure 4In the example, application server 416 can contact application server 414, application server 412, and application server 418. Application server 414, application server 410, application server 412, and application server 418 can be servers providing services to their associated applications. Figure 4 In the example, messages, shown by dashed lines, may exist between various application servers and a second computing device 422 requesting the application's application status. Upon receiving the application's status, application server 416 determines whether the application is in an appropriate state. If the application is in an appropriate state, the transaction can be approved, and this can be notified to application E executing on the first computing device 420. The operation to implement the transaction can also be performed by application E executing on either the first computing device 420 or application server 416. If the application is not in an appropriate state, the transaction can be rejected, and the rejection can be notified to application E. In some examples, application E may notify the user why the transaction was rejected. In other examples, application E may not notify the user why the transaction was rejected.
[0048] Despite Figure 4 The example shown utilizes application E server 416 to approve or reject the transaction; however, in other examples, application E may use inter-device messaging and leverage its API to contact various application servers and / or the second computing device 422 to determine the application state. In yet another example, some application states are determined by application E on the first computing device 420, and in still another example, some of the other application states are determined by application E server 416.
[0049] As previously described, the applications and / or states required for authentication of a given transaction can vary. For example, at time T, a first group of applications might be required to be in a first group of states, and at time T+1, a second group of applications might be required to be in a second group of states. Furthermore, the applications and / or states required for authentication can also vary based on the context of the transaction. For example, transactions considered high-risk (such as large financial transfers) might require authentication from applications with stringent security features (such as banking or financial applications) that must be in a secure login state. Conversely, low-risk transactions, such as accessing content on a public news application, might only require basic authentication from an application with lower security requirements. Additionally, a user's geographic location can also influence the authentication process; transactions originating from areas known to have high fraud rates might require authentication from additional applications to more rigorously verify the user's identity. This adaptive approach allows the system to dynamically modify authentication requirements based on perceived risk from the transaction, user location, and other relevant contextual factors, thereby enhancing security while optimizing user convenience.
[0050] In some examples, a risk score for a transaction can be used to determine the application and state required to authenticate the transaction. The transaction can be scored using a risk scoring technique. Factors used in the risk score may include the type of transaction, the location of the user attempting the transaction, any recent fraudulent activity reported by the user, any other indications of fraud related to the user or transaction, etc. In some examples, each of these factors can be scored and a weighted sum can be used to determine the transaction risk score. Similarly, each <application, state> tuple can be scored for its security guarantee. The application and state can be automatically selected by the system such that the sum of the security guarantees of the <application, state> tuples satisfies or exceeds the risk score. Other algorithms can be utilized; for example, the risk score can be set to a minimum security guarantee score required to utilize the <application, state> tuples. In some examples, in addition to a minimum guarantee score, the system may have a minimum total security guarantee score for all <application, state> tuples.
[0051] Figure 5 Figure 500 illustrates a context-based <application, state> tuple relationship according to some examples of this disclosure. Figure 500 relates to a specific transaction type and has two contexts: context A 510 and context B 520. When the first context, i.e., context A 510, is present, for the transaction to be authenticated, application A must be in state W, represented by tuple 512, and application B must be in state X, represented by tuple 514. When context B 520 is present, for the transaction to be authenticated, application A must be in state V, represented by tuple 522; application C must be in state Y, represented by tuple 524; and application D must be in state Z, represented by tuple 526. A context can be defined by one or more factors. For example, in a simple case, context A is the first time—that is, a transaction placed during the period when the user is expected to wake up—and context B can be a transaction placed during the period when the user is not expected to wake up. In other examples, other more complex combinations of environments can include contexts. For example, time and the user's geographic location.
[0052] As previously described, transactions can be authenticated not only based on the state of different applications, but also based on changes in the state of different applications. Authentication can depend on state changes occurring within a pre-specified time period. These state changes can involve one or more user actions or transactions performed on different applications. Figure 6Figure 600 illustrates the use of application state changes to authenticate transactions according to some examples of this disclosure. Application B on user computing device 608 is requesting transaction T1 from application B server 610. Application B server 610 consults the transaction authorization data record corresponding to transaction T1. This record indicates that application A must change its state from S1 to S2. In response, application B server 610 may perform an initial state check on application A on user computing device 608. If the initial state is correct, application B server 610 either checks the state of application A again after a threshold time (which may be related to a pre-specified time period—for example, just before or after the expiration of a pre-specified time period), or registers a state change update from application A server 612. In these later examples, when the state of application A changes, application A server 612 identifies the change and notifies application B server 610.
[0053] If application A changes from the required first state to the required second state within the required time, transaction T1 can be authenticated and executed. If application A does not start in the required state or does not change to the required second state within the required time, the transaction can be rejected. Figure 6 As shown, in some examples, the state change may be associated with an affirmative action by the user on application A. In these examples, the user may be prompted to perform the action.
[0054] exist Figure 6 In one example, application B server and application A server communicate to determine the state of application A used to authenticate transactions on application B. In other examples, application B may directly contact application A server 612 or directly contact application A on user computing device 608. Furthermore, although the authentication of transaction T1 is based on a single application's state change (application A), in other examples, multiple state changes from multiple applications may be required. Similarly, multiple state changes may be needed to authenticate a transaction. For example, application A may have to change its state to one or more other states in a sequence of state changes, such as changing from state S1 to state S2, and finally to state S37. In yet another example, only some applications required for authentication of a transaction may need to be in a specific state, and other applications may need to change their states. Moreover, although... Figure 6 The illustration shows an application that runs on a single user computing device (such as user computing device 608), but the application can run on different computing devices.
[0055] Figure 7The illustration shows a transaction authentication component 705 according to some examples of this disclosure. The transaction authentication component 705 may be executed as part of an application, an application service (e.g., executed by an application server), or a portion of the transaction authentication component may be executed as part of an application, and other portions may be executed as part of an application service (e.g., executed by an application server).
[0056] The transaction authentication component may include a control component 714, an application communication component 716, and a settings component 710. The transaction authentication component 705 may be communicatively coupled to a data storage 712. The data storage 712 may store a transaction table 718, which stores transaction authorization data records 720 for each transaction type for an application. The transaction authorization data records 720 may store identifiers for the transaction types and a list of applications associated with authenticating the transactions. Each application associated with authenticating the transactions has one or more associated application structures that describe information about each application within those applications, including required states.
[0057] Application structure 726 may include user information (e.g., user account information for the application), device information (e.g., the device on which the application must be installed and whose state is verified), a state that allows authentication of the transaction, application information, and, in some examples, an authentication token for communicating with the application or its server via an API. In other examples where the set of applications used for authenticating transactions can vary based on context, the transaction table may store a list of application structures corresponding to each <context, transaction> tuple. That is, for each context and transaction, a list of applications necessary for authentication and their states. In examples where state transitions are required for authentication, the application structure may store an initial state, a modified state, and the time period during which the user must transition the state from the initial state to the modified state.
[0058] Additionally, data storage 712 may store a policy table 722. Policy table 722 may have a list of transactions and, for each transaction, a policy structure, such as policy structure 724. Policy structure 724 lists, for each transaction, acceptable applications for authorizing the transaction or criteria for determining acceptable applications, and options for each application. Options may include acceptable states or criteria for determining acceptable states. The policy data may list applications or accounts that the user has not installed. During the setup process for determining the user's applications, the policy structure is then queried to determine which applications and states within the user's applications are acceptable for authentication. These applications and states are then used to populate transaction table 718.
[0059] Application communication component 716 can communicate with one or more devices and / or applications to identify applications installed on one or more of a user's devices(s). In some examples, the user can identify their devices, and the application communication component can communicate with those devices to identify applications on those devices. For example, this can be done by sending discovery messages using one or more APIs, or by communicating with the operating system on those devices. Additionally, application communication component 716 can communicate with the applications on those devices and / or with application services that provide services to those applications to determine the status of those applications.
[0060] The configuration component 710 can use a list of applications and security policies (e.g., standards) (such as policy structure 724 and policy table 722) to determine which applications and which states of those applications are acceptable for authenticating a specific transaction.
[0061] The user can then be given the opportunity to select an application and state from a list of acceptable <application, state> tuples determined by policies and / or criteria to authenticate each transaction. In other examples, the system may select an application and state from a list of acceptable <application, state> tuples determined by policies and / or criteria to authenticate each transaction.
[0062] Additionally, the policy can specify a minimum or threshold number of applications. For example, each <application, state> tuple can have an associated point number, and the policy can specify a threshold number that must be exceeded for authentication. The system or user can then select <application, state> tuples until the threshold is exceeded.
[0063] Once the list of <application, state> tuples is determined, the setup component can populate the transaction table for each transaction using the application and state information. This may include authenticating using the application or the server of each application to obtain an authentication token. In some examples, the user also provides their username and device information for the device on which the application is running. The user's username and device information may include a portion of state information that can be verified by the system. That is, the application may need to be in a specific state on a specific device and associated with a specific account.
[0064] Control component 714 can receive and process transaction requests. Control component 714 can consult data store 712 for the transaction authorization data record corresponding to the requested transaction (or, in a context-based example, the transaction authorization data record corresponding to the transaction and context). Control component 714 can then read the application structure and use application communication component 716 to query the application's state. If the application's state matches the state stored in the application structure for each application (or a subset of applications in some examples), the transaction can be authenticated and executed in some examples. In the example where authentication utilizes state transition, control component 714 and application communication component 716 determine whether the application has transitioned within an allocated time period, and if so, approve and execute the transaction. If the state does not match the state stored in the application structure, or if one or more applications in the application have not transitioned (in the example utilizing state transition), the transaction can be rejected. In some examples, the authentication mechanism described herein can be part of other authentication checks and processes used to authenticate transactions. For example, the mechanism described herein can be one factor in a multi-factor authentication scheme. Other factors may include user credentials, biometrics, etc.
[0065] Figure 8 This is a flowchart of a method 800 for authenticating transactions on a computing device by verifying the state of an auxiliary application, according to some examples of this disclosure. At operation 810, the method initiates a request for a transaction corresponding to a first application executed on the computing device. This first application may be a web application accessed via a browser or a dedicated application directly installed on the device. The user may be logged into the first application, which facilitates the transaction request. The request itself may be made via a graphical user interface (GUI), where the user interacts with visual elements on a screen to initiate the transaction. Alternatively, the request may be initiated via other user interfaces such as voice commands, where the user verbally instructs the device to perform the transaction, or via an automated script that triggers the transaction based on predefined conditions or schedules.
[0066] At operation 812, the method involves identifying a transaction authorization data record corresponding to the transaction. This record specifies a second application and its desired state, indicating that the application exists on the device, and a specific user account associated with the second application having an active authentication state. In some examples, the record specifies additional applications and application states. Figure 7The illustration depicts a transaction authorization data record. In some examples, identifying the record includes reading it from a data store—for example, looking up the record using transaction type and / or context to find a list of applications and their states. In some examples, the specified second application state indicates that the second application resides on a specified computing device (such as the current device executing the first application), and that a pre-specified third user account associated with the second application has an active authentication state on the second application, the pre-specified second user account being pre-designated to authenticate transactions of the first user account for the first application. For example, the user can specify the account during the setup of the first application.
[0067] At operation 814, the method continues to determine whether the current state of the second application corresponds to a specified state by communicating with the second application, an application state service, or the application server of the second application. This communication is typically facilitated by an API that can use a previously obtained security key to ensure secure and authenticated interaction. Alternatively, an application state service, defined as a centralized service for applications to report their state, can be utilized. This service acts as a repository and verifier of state information for various applications, allowing the system to query a centralized reference point to verify the state of the second application. Specific states required for the second application may include being installed on a specific device and actively logged in, having secure session activity, and / or being in a 'ready' state indicating preparation to perform a transaction or other secure operation. In some examples, this operation verifies that the second application resides on the computing device and that a pre-designated second user account has an active authentication state with the second application.
[0068] If, at operation 814, the second application does not correspond to the specific state, the transaction can be rejected at operation 820. In some examples, the user may be notified of the reason for the rejection. In other examples, the user may not be notified. Not notifying the user may be more secure because it prevents attackers from knowing which applications they will attempt to attack next. If, at operation 814, the second application corresponds to the specific state, the transaction is authenticated at operation 816. In response to the authentication, the transaction is processed at operation 818. "Processing" the transaction can refer to a series of actions taken after the transaction has been authenticated to complete its intended operation. This may include updating records, transferring funds, executing commands, or modifying data according to the transaction's requirements.
[0069] In some examples, the transaction may require additional applications to be in a specific state; in these examples, operation 814 can be repeated for each application. As previously described, in some examples, all applications must be in a specific state to authenticate the transaction. In these examples, if a single application fails the check at operation 814, the transaction is rejected. In other examples, a pre-specified number of applications must be in a specified state for authentication. In these examples, the operation at 814 increments a counter as applications are in the specified state. If the counter exceeds a threshold, the transaction is authenticated at operation 816; otherwise, the transaction is rejected at operation 820.
[0070] Figure 9 This is a flowchart of a method 900 for authenticating transactions on a computing device by verifying state changes of an auxiliary application, based on some examples of this disclosure. In some examples, Figure 9 The illustration depicts a scenario where the second application is executed on a second computing device, different from the first computing device on which the first application is running. This could be advantageous in situations where the first computing device is untrusted (such as a public computing device).
[0071] At operation 910, the method begins by identifying a request for a transaction corresponding to a first application running on the first computing device. This request is associated with a first user account for the first application. The request can be initiated through various user interfaces such as a graphical user interface (GUI), voice commands, or automated scripts.
[0072] At operation 912, in response to the transaction request, a transaction authorization data record is identified. This record specifies a second application running on the second computing device, as well as the desired state and state changes for that second application. In some examples, additional applications and states may be identified. Figure 7 The transaction authorization data record is illustrated. In some examples, identifying the record includes reading it from a data store—for example, by looking up the record using transaction type and / or context to find a list of applications and their states. In some examples, the specified state indicates that the second application must be installed on the second computing device and that a pre-specified second user account associated with the second application has an active authentication state. In method 900, in addition to requiring the application to start in a specified state, the application must also transition to another state indicated by the transaction authorization data record within a pre-specified time period. The pre-specified time period may be specified by the administrator or designer of the authentication system, the administrator or designer of the first application specified by the user, etc. The pre-specified time period may be stored within the transaction authorization data record.
[0073] In some examples, actions that cause a state change may include a user logging in or out of the application; opening the application; user interactions such as accepting terminology, changing settings, clicking a button, or updating a profile; transaction actions related to a transaction that is different from the transaction being authenticated, such as initiating a transfer, approving a payment, sending a communication, or confirming a receipt; and biometric verification, such as providing fingerprint, facial recognition, or voice verification.
[0074] At operation 914, the method involves determining whether the current state of the second application corresponds to a specified state by communicating with the second application, an application state service, or the application server of the second application. In some examples, this determination verifies that the second application resides on the second computing device and that a pre-specified second user account has an active authentication state with the second application. If, at operation 914, the second application is not in the specified state, the transaction can be rejected at operation 922.
[0075] If the second application is in the specified state at operation 914, then at operation 916, the method checks whether the user has performed the specified action within a pre-specified time period to achieve a state change in the second application. Using a state change increases the security level of the authentication system because it not only verifies that the application is in the specified state but also verifies that the user has control over the application to achieve the state change. In some examples, to verify the state change, the authentication system may, for example, re-check the application state exactly before, during, or after the pre-specified time period. In other examples, the authentication system may register state change notifications and authenticate the transaction based on receiving a notification indicating that the desired state has changed in the desired manner before the pre-specified time period has elapsed. In some examples, the pre-specified time period begins at any time after operation 910 and extends to operation 914.
[0076] If the state change at operation 916 does not occur within a pre-specified time period, the transaction can be rejected at operation 922. If the state change at operation 916 occurs within the pre-specified time period, the transaction is authenticated at operation 918. The method then continues processing the transaction upon successful authentication at operation 920. This processing may involve updating records, transferring funds, or executing commands required for the transaction. If additional applications and states (optionally with state changes) are required to authenticate the transaction, operations 914 and 916 can be repeated for each application, and authentication of the transaction at operation 918 can be performed only if all or a threshold number of the required applications are in the required state or have transitioned to the required state.
[0077] Figure 10This is a flowchart of a method 1000 for authenticating transactions on a computing device by verifying the state of multiple applications, based on some examples of this disclosure. At operation 1010, a first application or its application server automatically identifies a request for a transaction corresponding to the first application installed on the computing device using one or more processors. The transaction is associated with a first user account of the first application. The request can be initiated through various user interfaces such as a graphical user interface (GUI), voice commands, or automated scripts.
[0078] At operation 1012, in response to the transaction request, a transaction authorization data record is identified. This record specifies one or more applications executing on the second computing device and the desired state and / or state changes for those second applications. Figure 7 The illustration shows the transaction authorization data record. In some examples, identifying the record includes reading it from a data store—for example, finding the record by using transaction type and / or context lookup to locate a list of applications and their status.
[0079] At operation 1014, in response to identifying the request and locating the transaction authorization data record, the method involves selecting, based on the attributes of the transaction, a subset of a pre-specified set of other applications from the transaction authorization data record corresponding to the transaction, and a desired state for each application in the subset. In some examples, each authentication state indicates that at least the application resides on a specified computing device, and that the application has an active authentication state of a pre-specified user account associated with the application. The selected subset differs from a second subset selected based on attributes of a second transaction that are different from the attributes of the transaction.
[0080] The attributes of a transaction that can be used to select an application for authentication purposes can include various factors, such as the random number generated for the transaction, the type of transaction, the risk associated with the transaction, the user's geographic location, and / or other security-related criteria. For example, the type of transaction can be used, as different transaction types may require different levels of security. For instance, high-value financial transactions may require authentication from banking and financial applications with robust security features, while less sensitive transactions may only require authentication from less secure, frequently used applications. Risk associated with the transaction can also be used. Risk factors such as unusual transaction amounts or destinations may suggest selecting additional or more secure applications for authentication. This ensures an increased layer of security by involving multiple checkpoints. The user's geographic location can also influence application selection. If a transaction is initiated from an unusual location for the user, the system may require authentication from an application providing location services or enhanced security measures to verify the legitimacy of the transaction and the user's identity.
[0081] Other attributes may include: Transaction timing: Transactions occurring at unusual times, such as late at night or early in the morning, may be flagged as higher risk. This may prompt the selection of more secure applications or those with additional verification steps to validate the transaction. Transaction frequency: If users initiate transactions more frequently than usual, this may trigger the use of applications and state for a higher level of security. Device security status: The overall security status of the device used for the transaction (e.g., whether the device is blocked or has enabled security features) can be used to determine which applications are selected. If the integrity of the device may be compromised, more secure applications may be required. User behavior patterns: If the transaction deviates from the user's normal behavior, applications that analyze user behavior and patterns can be selected. This can include transactions of anomalous categories or amounts that differ significantly from typical transactions. Network security level: The security level of the network initiating the transaction (e.g., public Wi-Fi versus a secure home network) may influence the choice of applications. Transactions over less secure networks may require authentication by applications that offer additional encryption or security measures. Historical fraud data: If the transaction involves an entity (such as a bank account or location) previously associated with fraudulent activities, the transaction can be authenticated by specific applications in historical data analysis and fraud detection. Regulatory Requirements: For certain types of transactions, particularly in regulated industries such as banking or healthcare, specific applications may be required to comply with legal and regulatory standards. These applications will ensure that transactions meet all necessary compliance checks.
[0082] In some examples, the set of applications used for authentication can be random and can change over time—for example, based on the current time.
[0083] At operation 1016, based on the transaction authorization data record, for each specific application in the subset, the method determines whether the current state of the specific application corresponds to a specified authentication state by communicating with the specific application, the application state service, or the application server of the specific application. In some examples, this determination verifies that the specific application resides on a specified computing device and that the specific application has an active authentication state of a pre-specified user account associated with the application.
[0084] If, at operation 1016, the application in the subset is not in a correct state, the transaction can be rejected at operation 1022. If, at operation 1016, the application in the subset is in a prohibited state, the transaction is authenticated at operation 1018 and processed at operation 1020. This processing may involve updating records, transferring funds, or executing commands required for the transaction.
[0085] Figure 11 This is a flowchart of a method 1100 for establishing applications and states for transaction authentication, based on some examples of this disclosure. At operation 1110, multiple applications associated with a user are identified. This operation can be performed by accessing one or more of the user's devices directly or via a network connection. The system can query the device's operating system or a dedicated application management service to retrieve a list of installed applications. This may involve calling APIs that provide information about applications currently installed or running on the device. Additionally, the system can access user-specific data, such as login records or application usage logs, to determine which applications are not only installed but also actively used and associated with the user.
[0086] At operation 1112, for a specific type of transaction to be initiated by the first application, a subset of multiple applications that meet specified authentication criteria are selected. In some examples, these criteria can be predefined by a system administrator or security policy manager based on the security requirements of the transaction, the sensitivity of the data involved, and the organization's overall security posture. These criteria can be defined during system setup and can be updated as needed to adapt to new security challenges or changes in organizational policies. Administrators can set and modify these criteria using an administration console or dedicated configuration files. The authentication criteria can specify one or more applications or one or more attributes of the applications allowed based on the transaction. The application attributes can be determined via an API or a central service. The authentication criteria can then be compared with the application attributes to determine whether the application meets the authentication criteria for the transaction. For example, the criteria can indicate that a particular application is a trusted application.
[0087] At operation 1114, operations 1116-1122 are performed for each of the filtered applications. At operation 1116, the state information of each specific application that meets the specified authentication criteria is determined. The state of each application can be determined using the previously described API or application management service. In some examples, the state can be obtained using the application information previously retrieved for operation 1112. In some examples, the state can be converted to a standardized state. For example, each application can have its own specific state, and the state can be converted to a standardized state before determining which states meet the authentication criteria. The state can be converted based on conversion rules for each application. In some examples, the criteria can directly specify which states of which applications are acceptable for each transaction. In other examples, the criteria can specify rules for states with a minimum security level. The attributes of the state can be obtained via the API or application management service and compared with the rules to determine whether the state meets the rules.
[0088] At operation 1118, authentication is performed with the specific application, its application server, or an application state service to obtain an authentication key. For example, this operation can be performed to obtain an authentication key to query the application's state when initiating a transaction. To obtain the authentication key in some examples, the process may involve several steps. Initially, the user must authorize the requesting application to access the target application, typically facilitated by an OAuth flow. During this phase, the user is redirected to the service provider's authentication page to log in and be granted the necessary permissions. Upon successful authorization, the service provider redirects back to the requesting application using an authorization code, a short-lived token that can be exchanged for an access token. The requesting application then submits this authorization code along with its client ID and client secret to the service provider's token endpoint. These credentials, obtained during the application's registration with the service provider, are used to verify the application's identity. If the authorization code, client ID, and client secret are verified, the service provider issues an access token to the requesting application. This access token is used by the application to make API requests on behalf of the user, including as a bearer token in the HTTP header of the API request. This includes notifying the service provider associated with the user and ensuring the authorization of the request. Access tokens typically have a limited lifespan; once expired, the application can obtain a new access token using a refresh token received along with the original access token, without requiring further user authorization. In some examples, these tokens may be stored in transaction authorization data records, such as those stored in the application architecture that stores application information, such as... Figure 7 Application structure 726.
[0089] At operation 1120, a user identifier for a specific application and a unique device identifier for the application are used. For example, the user can provide a username for the application. In some examples, this operation occurs in conjunction with operation 1118 when a user logs into another application.
[0090] At operation 1122, application data for a specific application is stored in the transaction authorization data record in the database. The application data includes status information, user identifier, authentication key, and device identifier.
[0091] At operation 1124, a transaction request from a first application corresponding to a specific type of transaction to be initiated is received, and in response, at operation 1126, a transaction authorization data record for the transaction type is retrieved from the database.
[0092] At operation 1128, the transaction is authenticated by verifying that the specific application indicated in the transaction authorization data record is executing on a device with the correct device identifier and that the specific application is in the required state, wherein the verification uses a stored user identifier, communication channel information and authentication key to interact with the application, its server or application state service.
[0093] Figure 12 A block diagram of an example machine 1200 on which any one or more of the techniques (e.g., methods) discussed herein can be performed. In alternative embodiments, machine 1200 may operate as a standalone device or may be connected (e.g., networked) to other machines. In a networked deployment, machine 1200 may operate as a server machine, a client machine, or both in a server-client network environment. In the example, machine 1200 may act as a peer-to-peer (P2P) (or other distributed) network environment. Machine 1200 may be in the form of a server, personal computer (PC), tablet PC, set-top box (STB), personal digital assistant (PDA), mobile phone, smartphone, web device, network router, switch, or bridge, or any machine capable of executing instructions (sequentially or otherwise) specifying actions to be taken by the machine. Furthermore, although only a single machine is illustrated, the term "machine" should also be considered as any collection of machines that individually or jointly execute a set (or more sets) of instructions to perform any one or more of the methods discussed herein, such as cloud computing, Software as a Service (SaaS), and other computer cluster configurations. In some examples, machine 1200 may be or be configured to store... Figure 1 The relationship shown in 5 is or is realized. Figure 2-4 , Figure 6 and Figure 7 Any component in the component, and implement Figure 8-11 The method.
[0094] As described herein, examples may include or may operate on one or more logical units, components, or mechanisms (hereinafter referred to as "components"). A component is a tangible entity (e.g., hardware) capable of performing a specified operation and which may be configured or arranged in a particular manner. In the examples, circuitry may be arranged as a component in a specified manner (e.g., internally or relative to external entities, such as other circuitry). In the examples, all or part of one or more computer systems (e.g., standalone, client, or server computer systems) or one or more hardware processors may be configured by firmware or software (e.g., instructions, application portions, or applications) to operate as a component to perform the specified operation. In the examples, the software may reside on a machine-readable medium—also referred to as a computer-readable medium or machine-readable medium. In the examples, the software, when run by the underlying hardware of the component, causes the hardware to perform the specified operation of the component.
[0095] Therefore, the term "component" is understood to encompass tangible entities that are physically constructed, specifically configured (e.g., hardwired), or temporarily (e.g., provisionally) configured (e.g., programmed) to operate in a specified manner or perform any of the operations described herein, in part or in whole. Consider the example of components being provisionally configured, where each component does not need to be instantiated at any given time. For example, in the case where a component includes a general-purpose hardware processor configured using software, the general-purpose hardware processor can be configured as different components at different times. The software can accordingly configure the hardware processor, for example, to constitute a specific module at one time and different components at different times.
[0096] Machine (e.g., computer system) 1200 may include one or more hardware processors, such as processor 1202. Processor 1202 may be a central processing unit (CPU), a graphics processing unit (GPU), a hardware processor core, or any combination thereof. Machine 1200 may include main memory 1204 and static memory 1206, some or all of which may communicate with each other via interconnect (e.g., bus) 1208. Examples of main memory 1204 may include synchronous dynamic random access memory (SDRAM), such as double data rate memory, such as DDR4 or DDR5. Interconnect 1208 may be one or more different types of interconnects, such that one type of interconnect can be used to connect one or more components, and another type of interconnect can be used to connect one or more components. Example interconnects may include a memory bus, peripheral component interconnect (PCI), peripheral component interconnect fast (PCIe) bus, universal serial bus (USB), etc.
[0097] Machine 1200 may also include a display unit 1210, an alphanumeric input device 1212 (e.g., a keyboard), and a user interface (UI) navigation device 1214 (e.g., a mouse). In this example, the display unit 1210, input device 1212, and UI navigation device 1214 may be a touchscreen display. Machine 1200 may additionally include a storage device (e.g., a drive unit) 1216, a signal generation device 1218 (e.g., a speaker), a network interface device 1220, and one or more sensors 1221, such as a Global Positioning System (GPS) sensor, a compass, an accelerometer, or other sensors. Machine 1200 may include an output controller 1228, such as serial (e.g., Universal Serial Bus (USB), parallel, or other wired or wireless (e.g., infrared (IR), near field communication (NFC), etc.) connections, to communicate with or control one or more peripheral devices (e.g., a printer, a card reader, etc.).
[0098] Storage device 1216 may include machine-readable medium 1222 thereon storing one or more sets of data structures or instructions 1224 (e.g., software) embodying or utilized by any one or more of the techniques or functions described herein. Instructions 1224 may also reside wholly or at least partially within main memory 1204, static memory 1206, or hardware processor 1202 during execution by machine 1200. In this example, one or any combination of hardware processor 1202, main memory 1204, static memory 1206, or storage device 1216 may constitute a machine-readable medium.
[0099] Although machine-readable medium 1222 is illustrated as a single medium, the term "machine-readable medium" can include a single medium or multiple media (e.g., a centralized or distributed database and / or associated caches and servers) configured to store one or more instructions 1224.
[0100] The term "machine-readable medium" can include any medium capable of storing, encoding, or carrying instructions for execution by machine 1200 and causing machine 1200 to perform any one or more of the technologies disclosed herein, or any medium capable of storing, encoding, or carrying data structures used by or associated with such instructions. Examples of non-limiting machine-readable media can include solid-state memory, as well as optical and magnetic media. Specific examples of machine-readable media can include: non-volatile memory, such as semiconductor memory devices (e.g., electrically programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM)) and flash memory devices; disks, such as internal hard disks and removable disks; magneto-optical disks; random access memory (RAM); solid-state drives (SSDs); and CD-ROMs and DVD-ROMs. In some examples, machine-readable media can include non-transitory machine-readable media. In some examples, machine-readable media can include machine-readable media that are not transient propagating signals.
[0101] Commands 1224 can also be transmitted or received on the communication network 1226 via the network interface device 1220 using a transmission medium. Machine 1200 can communicate wired or wirelessly with one or more other machines using any of a variety of transmission protocols, such as Frame Relay, Internet Protocol (IP), Transmission Control Protocol (TCP), User Datagram Protocol (UDP), Hypertext Transfer Protocol (HTTP), etc. Example communication networks may include local area networks (LANs), wide area networks (WANs), packet data networks (e.g., the Internet), mobile phone networks (e.g., cellular networks), conventional telephone (POTS) networks, and wireless data networks such as the IEEE 802.11 family of standards (known as Wi-Fi®), the IEEE 802.15.4 family of standards, the 5G New Radio (NR) family of standards, the Long Term Evolution (LTE) family of standards, the Universal Mobile Telecommunications System (UMTS) family of standards, peer-to-peer (P2P) networks, etc. In the example, network interface device 1220 may include one or more physical jacks (e.g., Ethernet, coaxial, or telephone jacks) or one or more antennas for connection to communication network 1226. In the example, network interface device 1220 may include multiple antennas to perform wireless communication using at least one of single-input multiple-output (SIMO), multiple-input multiple-output (MIMO), or multiple-input single-output (MISO) technologies. In some examples, network interface device 1220 may use multi-user MIMO technology for wireless communication.
[0102] Other notes and examples
[0103] Example 1 is a method for authenticating transactions on a computing device, comprising: automatically, using one or more processors, at a first application or an application server of the first application: identifying a request for a transaction corresponding to the first application executing on the computing device, the transaction being associated with a first user account of the first application; and in response to identifying the request: identifying a transaction authorization data record corresponding to the transaction, the transaction authorization data record specifying a second application and a specified second application state corresponding to the transaction, wherein the specified second application state indicates that the second application resides on the computing device and a pre-specified second user account associated with the second application has an active authentication state on the second application, the pre-specified second application state indicating that the second application resides on the computing device and a pre-specified second user account associated with the second application has an active authentication state on the second application. Two user accounts are pre-assigned for authenticating transactions for the first user account in relation to the first application; based on the transaction authorization data record, by communicating with the second application, an application status service, or the application server of the second application, it is determined whether the current state of the second application corresponds to the designated second application state, wherein the determination verifies that the second application resides on the computing device and that the pre-assigned second user account has an active authentication state corresponding to the second application; and in response to determining that the current state of the second application corresponds to the designated second application state based on the transaction authorization data record: authenticating the transaction based on verifying that the second application is in the designated second application state; and processing the transaction upon successful authentication.
[0104] In Example 2, the subject of Example 1 includes, wherein the transaction authorization data record includes a list of applications and their corresponding states required for transaction verification based on the type of transaction.
[0105] In Example 3, the subject of Examples 1-2 includes the following steps: if the second application is not logged in, send a notification to the user to log in to the second application.
[0106] In Example 4, the subject matter of Examples 1-3 includes: identifying a second request for a second transaction of a different type from the first transaction, the second transaction corresponding to the first application and associated with the first user account of the first application; and in response to identifying the second request: identifying a third application, a fourth application, a specified third application state, and a specified fourth application state based on the second transaction authorization data record and the second transaction; identifying the current state of the third application by communicating with the third application, the application state service, or the third application server of the third application; identifying the current state of the fourth application by communicating with the fourth application, the application state service, or the fourth application server of the fourth application; determining that the current state of the third application corresponds to the specified third application state and that the current state of the fourth application corresponds to the specified fourth application state; and in response to determining that the current state of the third application corresponds to the specified third application state and that the current state of the fourth application corresponds to the specified fourth application state: authenticating the second transaction; and processing the second transaction upon successful authentication.
[0107] In Example 5, the subject of Examples 1-4 includes the following: the second application is selected from a set of applications pre-selected by the user.
[0108] In Example 6, the subject matter of Examples 1-5 includes, wherein identifying the current state of the second application also includes verifying that the unique identifier of the authentication session of the second application corresponds to the unique identifier of the computing device.
[0109] In Example 7, the subject matter of Examples 1-6 includes: identifying a second request for a second transaction of a different type from the first transaction, the second transaction corresponding to the first application and associated with the first user account of the first application; and in response to identifying the second request: identifying a third application and a specified third application state based on transaction authorization data records and the transaction, wherein the specified third application state indicates whether the third application is logged in or not logged out relative to a third-defined user account associated with the third application, the third-defined user account having a pre-specified relationship with the first user account of the first application; identifying the current state of the third application by communicating with the third application, the application state service, or the third application server of the third application; determining that the current state of the third application corresponds to the specified third application state; and in response to determining that the current state of the third application corresponds to the specified third application state: authenticating the second transaction based on verifying that the third application is in the specified third application state; and processing the second transaction upon successful authentication.
[0110] In Example 8, the subject matter of Examples 1-7 includes: identifying a second request for a second transaction of a different type from the transaction, the second transaction corresponding to the first application and associated with the first user account of the first application; and in response to identifying the second request: identifying a third application state of the second application based on the second transaction, the third application state being different from the specified second application state; identifying the current state of the second application by communicating with the second application, the application state service, or the application server of the first application; determining that the current state of the second application corresponds to the third application state; and in response to determining that the current state of the second application corresponds to the third application state: authenticating the transaction based on verifying that the second application is in the third application state; and processing the second transaction upon successful authentication.
[0111] In Example 9, the topics of Examples 1-8 include where the operation is performed without user input.
[0112] In Example 10, the subject matter of Examples 1-9 includes: receiving an identifier of the transaction, the second application, and the pre-specified second user account from a user in a graphical user interface; and populating the transaction authorization data record using the received identifier, the second application, and the pre-specified second user account.
[0113] In Example 11, the subject of Examples 1-10 includes, wherein the transaction is to authenticate a user to the first application.
[0114] In Example 12, the subject matter of Examples 1-11 includes: identifying a second request for a second transaction corresponding to a first application executed on the computing device, the second transaction being associated with a first user account of the first application; and in response to identifying the second request: identifying a second transaction authorization data record corresponding to the second transaction, the second transaction authorization data record specifying a second transaction authorization data record corresponding to the second transaction, the second application, and a specified third application state, wherein the specified third application state is different from the specified second application state; determining, based on the second transaction authorization data record, whether the current state of the second application corresponds to the specified third application state by communicating with the second application, the application state service, or the application server of the second application; and in response to determining, based on the transaction authorization data record, that the current state of the second application does not correspond to the specified third application state, causing the authentication to fail and rejecting the transaction.
[0115] In Example 13, the subject matter of Examples 1-12 includes: identifying a second request for a second transaction of a different type from the first transaction, the second transaction corresponding to the first application and associated with the first user account of the first application; and in response to identifying the second request: identifying a third application, a fourth application, a specified third application state, and a fourth application state based on the second transaction authorization data record and the second transaction; identifying the current state of the third application by communicating with the third application, the application state service, or the third application server of the third application; identifying the current state of the fourth application by communicating with the fourth application, the application state service, or the fourth application server of the fourth application; determining that the current state of the third application does not correspond to the specified third application state or the current state of the fourth application does not correspond to the fourth application state; and in response to determining that the current state of the third application does not correspond to the specified third application state or the current state of the fourth application does not correspond to the fourth application state: rejecting the authentication and canceling the transaction.
[0116] Example 14 is a computing device for authenticating transactions, the computing device comprising: a hardware processor; and a memory storing instructions that, when executed by the hardware processor, cause the hardware processor to perform operations including: automatically at a first application or an application server of the first application: identifying a request for a transaction corresponding to the first application executing on the computing device, the transaction being associated with a first user account of the first application; and in response to identifying the request: identifying a transaction authorization data record corresponding to the transaction, the transaction authorization data record specifying a second application and a specified second application state corresponding to the transaction, wherein the specified second application state indicates that the second application resides on the computing device and a pre-specified second user account associated with the second application is... The second application has an active authentication state, and the pre-designated second user account is pre-designated for authenticating the transaction of the first user account for the first application; based on the transaction authorization data record, by communicating with the second application, the application state service, or the application server of the second application, it is determined whether the current state of the second application corresponds to the designated second application state, the determination verifies that the second application resides on the computing device and that the pre-designated second user account has an active authentication state corresponding to the second application; and in response to determining that the current state of the second application corresponds to the designated second application state based on the transaction authorization data record: authenticating the transaction based on verifying that the second application is in the designated second application state; and processing the transaction upon successful authentication.
[0117] In Example 15, the subject of Example 14 includes, wherein the transaction authorization data record includes a list of applications and their corresponding states required for transaction verification based on the type of transaction.
[0118] In Example 16, the subject of Examples 14-15 includes, wherein the operation further includes: if the second application is not logged in, sending a notification to the user to log in to the second application.
[0119] In Example 17, the subject matter of Examples 14-16 includes, wherein the operation further includes: identifying a second request for a second transaction of a different type from the transaction, the second transaction corresponding to the first application and associated with the first user account of the first application; and in response to identifying the second request: identifying a third application, a fourth application, a specified third application state, and a specified fourth application state based on the second transaction authorization data record and the second transaction; identifying the current state of the third application by communicating with the third application, the application state service, or the third application server of the third application; identifying the current state of the fourth application by communicating with the fourth application, the application state service, or the fourth application server of the fourth application; determining that the current state of the third application corresponds to the specified third application state and that the current state of the fourth application corresponds to the specified fourth application state; and in response to determining that the current state of the third application corresponds to the specified third application state and that the current state of the fourth application corresponds to the specified fourth application state: authenticating the second transaction; and processing the second transaction upon successful authentication.
[0120] In Example 18, the subject of Examples 14-17 includes the following: the second application is selected from a set of applications pre-selected by the user.
[0121] In Example 19, the subject matter of Examples 14-18 includes, wherein the operation of identifying the current state of the second application further includes: verifying that a unique identifier of the authentication session of the second application corresponds to a unique identifier of the computing device.
[0122] In Example 20, the subject matter of Examples 14-19 includes, wherein the operation further includes: identifying a second request for a second transaction of a different type from the transaction, the second transaction corresponding to the first application and associated with the first user account of the first application; and in response to identifying the second request: identifying a third application and a specified third application state based on transaction authorization data records and the transaction, wherein the specified third application state indicates whether the third application is logged in or not logged in relative to a third-defined user account associated with the third application, the third-defined user account having a pre-specified relationship with the first user account of the first application; identifying the current state of the third application by communicating with the third application, the application state service, or the third application server of the third application; determining that the current state of the third application corresponds to the specified third application state; and in response to determining that the current state of the third application corresponds to the specified third application state: authenticating the second transaction based on verifying that the third application is in the specified third application state; and processing the second transaction upon successful authentication.
[0123] In Example 21, the subject matter of Examples 14-20 includes, wherein the operation further includes: identifying a second request for a second transaction of a different type from the transaction, the second transaction corresponding to the first application and associated with the first user account of the first application; and in response to identifying the second request: identifying a third application state of the second application based on the second transaction, the third application state being different from the specified second application state; identifying the current state of the second application by communicating with the second application, the application state service, or the application server of the first application; determining that the current state of the second application corresponds to the third application state; and in response to determining that the current state of the second application corresponds to the third application state: authenticating the transaction based on verifying that the second application is in the third application state; and processing the second transaction upon successful authentication.
[0124] In Example 22, the subject of Examples 14-21 includes the operation being performed without user input.
[0125] In Example 23, the subject matter of Examples 14-22 includes, wherein the operation further includes: receiving from a user in a graphical user interface the transaction, the second application, and the identifier of the pre-specified second user account; and populating the transaction authorization data record using the received identifier, the second application, and the pre-specified second user account.
[0126] In Example 24, the subject of Examples 14-23 includes, wherein the transaction is authenticating a user to the first application.
[0127] In Example 25, the subject matter of Examples 14-24 includes, wherein the operation further includes: identifying a second request for a second transaction corresponding to a first application executed on the computing device, the second transaction being associated with a first user account of the first application; and in response to identifying the second request: identifying a second transaction authorization data record corresponding to the second transaction, the second transaction authorization data record specifying a second application corresponding to the second transaction and a specified third application state, wherein the specified third application state is different from the specified second application state; determining, based on the second transaction authorization data record, whether the current state of the second application corresponds to the specified third application state by communicating with the second application, the application service state, or the application server of the second application; and in response to determining, based on the transaction authorization data record, that the current state of the second application does not correspond to the specified third application state, causing the authentication to fail and rejecting the transaction.
[0128] In Example 26, the subject matter of Examples 14-25 includes, wherein the operation further includes: identifying a second request for a second transaction of a different type from the transaction, the second transaction corresponding to the first application and associated with the first user account of the first application; and in response to identifying the second request: identifying a third application, a fourth application, a specified third application state, and a fourth application state based on the second transaction authorization data record and the second transaction; identifying the current state of the third application by communicating with the third application, the application state service, or the third application server of the third application; identifying the current state of the fourth application by communicating with the fourth application, the application state service, or the fourth application server of the fourth application; determining that the current state of the third application does not correspond to the specified third application state, or that the current state of the fourth application does not correspond to the fourth application state; and in response to determining that the current state of the third application does not correspond to the specified third application state or that the current state of the fourth application does not correspond to the fourth application state: rejecting the authentication and canceling the transaction.
[0129] Example 27 is a computer-readable storage device that stores instructions for authenticating a transaction at a first application or an application server of the first application. When executed by a computing device, the instructions cause the computing device to perform the following operations: identifying a request for a transaction corresponding to the first application executed on the computing device, the transaction being associated with a first user account of the first application; and in response to identifying the request: identifying a transaction authorization data record corresponding to the transaction, the transaction authorization data record specifying a second application and a specified second application state corresponding to the transaction, wherein the specified second application state indicates that the second application resides on the computing device and a pre-specified second user account associated with the second application is active on the second application. The authentication status includes: a pre-designated second user account being pre-designated for authenticating transactions for the first user account of the first application; determining, based on the transaction authorization data record, whether the current state of the second application corresponds to the designated second application state by communicating with the second application, an application state service, or the application server of the second application; verifying that the second application resides on the computing device and that the pre-designated second user account has an active authentication status corresponding to the second application; and in response to determining that the current state of the second application corresponds to the designated second application state based on the transaction authorization data record: authenticating the transaction based on verifying that the second application is in the designated second application state; and processing the transaction upon successful authentication.
[0130] In Example 28, the subject of Example 27 includes, wherein the transaction authorization data record includes a list of applications and their corresponding states required for transaction verification based on the type of transaction.
[0131] In Example 29, the subject of Examples 27-28 includes, wherein the operation further includes: if the second application is not logged in, sending a notification to the user to log in to the second application.
[0132] In Example 30, the subject matter of Examples 27-29 includes, wherein the operation further includes: identifying a second request for a second transaction of a different type from the transaction, the second transaction corresponding to the first application and associated with the first user account of the first application; and in response to identifying the second request: identifying a third application, a fourth application, a specified third application state, and a specified fourth application state based on the second transaction authorization data record and the second transaction; identifying the current state of the third application by communicating with the third application, the application state service, or the third application server of the third application; identifying the current state of the fourth application by communicating with the fourth application, the application state service, or the fourth application server of the fourth application; determining that the current state of the third application corresponds to the specified third application state and that the current state of the fourth application corresponds to the specified fourth application state; and in response to determining that the current state of the third application corresponds to the specified third application state and that the current state of the fourth application corresponds to the specified fourth application state: authenticating the second transaction; and processing the second transaction upon successful authentication.
[0133] In Example 31, the subject of Examples 27-30 includes the following: the second application is selected from a set of applications pre-selected by the user.
[0134] In Example 32, the subject matter of Examples 27-31 includes, wherein the operation of identifying the current state of the second application further includes verifying that a unique identifier of the authentication session of the second application corresponds to a unique identifier of the computing device.
[0135] In Example 33, the subject matter of Examples 27-32 includes, wherein the operation further includes: identifying a second request for a second transaction of a different type from the transaction, the second transaction corresponding to the first application and associated with the first user account of the first application; and in response to identifying the second request: identifying a third application and a specified third application state based on transaction authorization data records and the transaction, wherein the specified third application state indicates whether the third application is logged in or not logged out relative to a third-defined user account associated with the third application, the third-defined user account having a pre-specified relationship with the first user account of the first application; identifying the current state of the third application by communicating with the third application, the application state service, or the third application server of the third application; determining that the current state of the third application corresponds to the specified third application state; and in response to determining that the current state of the third application corresponds to the specified third application state: authenticating the second transaction based on verifying that the third application is in the specified third application state; and processing the second transaction upon successful authentication.
[0136] In Example 34, the subject matter of Examples 27-33 includes, wherein the operation further includes: identifying a second request for a second transaction of a different type from the transaction, the second transaction corresponding to the first application and associated with the first user account of the first application; and in response to identifying the second request: identifying a third application state of the second application based on the second transaction, the third application state being different from the specified second application state; identifying the current state of the second application by communicating with the second application, the application state service, or the application server of the first application; determining that the current state of the second application corresponds to the third application state; and in response to determining that the current state of the second application corresponds to the third application state: authenticating the transaction based on verifying that the second application is in the third application state; and processing the second transaction upon successful authentication.
[0137] In Example 35, the subject of Examples 27-34 includes the operation being performed without user input.
[0138] In Example 36, the subject matter of Examples 27-35 includes, wherein the operation further includes: receiving from a user an identifier of the transaction, the second application, and the pre-specified second user account in a graphical user interface; and populating the transaction authorization data record using the received identifier, the second application, and the pre-specified second user account.
[0139] In Example 37, the subject of Examples 27-36 includes, wherein the transaction is authenticating a user to the first application.
[0140] In Example 38, the subject matter of Examples 27-37 includes, wherein the operation further includes: identifying a second request for a second transaction corresponding to a first application executed on the computing device, the second transaction being associated with a first user account of the first application; and in response to identifying the second request: identifying a second transaction authorization data record corresponding to the second transaction, the second transaction authorization data record specifying a second application corresponding to the second transaction and a specified third application state, wherein the specified third application state is different from the specified second application state; determining, based on the second transaction authorization data record, whether the current state of the second application corresponds to the specified third application state by communicating with the second application, the application state service, or the application server of the second application; and in response to determining, based on the transaction authorization data record, that the current state of the second application does not correspond to the specified third application state, causing the authentication to fail and rejecting the transaction.
[0141] In Example 39, the subject matter of Examples 27-38 includes, wherein the operation further includes: identifying a second request for a second transaction of a different type from the transaction, the second transaction corresponding to the first application and associated with the first user account of the first application; and in response to identifying the second request: identifying a third application, a fourth application, a specified third application state, and a fourth application state based on the second transaction authorization data record and the second transaction; identifying the current state of the third application by communicating with the third application, the application state service, or the third application server of the third application; identifying the current state of the fourth application by communicating with the fourth application, the application state service, or the fourth application server of the fourth application; determining that the current state of the third application does not correspond to the specified third application state, or that the current state of the fourth application does not correspond to the fourth application state; and in response to determining that the current state of the third application does not correspond to the specified third application state or that the current state of the fourth application does not correspond to the fourth application state: rejecting the authentication and canceling the transaction.
[0142] Example 40 is a method for authenticating a transaction of a first application executing on a first computing device, the method comprising: automatically, using one or more processors at the first application or an application server of the first application, identifying a request for a transaction corresponding to the first application, the transaction being associated with a first user account of the first application; in response to identifying the request, identifying a transaction authorization data record corresponding to the transaction, the transaction authorization data record specifying, for the transaction, a second application executing on a second computing device, a specified second application state, and a specified second application state change, wherein the specified second application state indicates that: the second application resides on the second computing device, a pre-specified second user account associated with the second application has an active authentication state on the second application, and wherein the second application state change includes an action performed by a user at the second application within a pre-specified time period, the pre-specified second... A user account is pre-designated for authenticating transactions for the first user account in relation to the first application; based on the transaction authorization data record, it is determined, through communication with the second application, an application state service, or the application server of the second application: whether the current state of the second application corresponds to the designated second application state, the determination verifies that the second application resides on the first computing device and that the pre-designated second user account has an active authentication state corresponding to the second application; and whether the user has performed the designated action within the pre-specified time period to change the state of the second application; and in response to determining, based on the transaction authorization data record, that the current state of the second application corresponds to the designated second application state and that the user has performed the designated action within the pre-specified time period: authenticating the transaction based on verifying that the second application is in the designated second application state; and processing the transaction upon successful authentication.
[0143] In Example 41, the subject of Example 40 includes, wherein the first application, the second application, or both are web applications.
[0144] In Example 42, the subject of Examples 40-41 includes the following: the specified action performed by the user on the second application is to activate a user interface control.
[0145] In Example 43, the subject matter of Examples 40-42 includes, wherein the first computing device is an untrusted public device.
[0146] In Example 44, the subject matter of Examples 40-43 includes, wherein using the transaction to search the transaction authorization data record to identify the second application on the second computing device and the specified second application state includes searching the transaction authorization data record using the type of the transaction being authenticated.
[0147] In Example 45, the subject matter of Examples 40-44 includes, wherein using the transaction to search the transaction authorization data record to identify the second application on the second computing device and the specified second application state includes using a risk score associated with the user, the first computing device, or the transaction to search the transaction authorization data record.
[0148] In Example 46, the subject matter of Examples 40-45 includes, wherein using the transaction to search the transaction authorization data record to identify the second application on the second computing device and the specified second application state includes using the user's geographic location to search the transaction authorization data record.
[0149] In Example 47, the subject of Examples 40-46 includes: providing a notification on one of the first application and the second application, or on both the first application and the second application, to perform the specified action.
[0150] Example 48 is a first computing device that executes a first application or part of a first application server for authenticating transactions of the first application. The computing device includes: a hardware processor; and a memory storing instructions that, when executed by the hardware processor, cause the computing device to perform operations including: identifying a request for a transaction corresponding to the first application, the transaction being associated with a first user account of the first application; and, in response to identifying the request: identifying a transaction authorization data record corresponding to the transaction, the transaction authorization data record specifying a second application executed on a second computing device, a specified second application state, and a specified second application state change corresponding to the transaction, wherein the specified second application state indicates that: the second application resides on the second computing device, a pre-specified second user account associated with the second application has an active authentication state on the second application, and wherein the second application state change includes, within a pre-specified time period, a change in the second application's state. The system determines, based on the transaction authorization data record, whether the current state of the second application corresponds to the designated second application state by communicating with the second application, an application state service, or the application server of the second application; whether the user has performed the designated action to change the state of the second application within the pre-specified time period; and in response to determining, based on the transaction authorization data record, that the current state of the second application corresponds to the designated second application state and that the user has performed the designated action within the pre-specified time period: authenticating the transaction based on verifying that the second application is in the designated second application state; and processing the transaction upon successful authentication.
[0151] In Example 49, the subject of Example 48 includes, wherein the first application, the second application, or both are web applications.
[0152] In Example 50, the subject of Examples 48-49 includes the following: the specified action performed by the user on the second application is to activate a user interface control.
[0153] In Example 51, the subject of Examples 48-50 includes, wherein the first computing device is an untrusted public device.
[0154] In Example 52, the subject matter of Examples 48-51 includes the operation of using the transaction to search the transaction authorization data record to identify the second application on the second computing device and the specified second application state, which includes searching the transaction authorization data record using the type of the transaction being authenticated.
[0155] In Example 53, the subject matter of Examples 48-52 includes the operation of using the transaction to search the transaction authorization data record to identify the second application on the second computing device and the specified second application state, which includes using a risk score associated with the user, the first computing device, or the transaction to search the transaction authorization data record.
[0156] In Example 54, the subject matter of Examples 48-53 includes the operation of using the transaction to search the transaction authorization data record to identify the second application on the second computing device and specify the state of the second application, which includes using the user's geographic location to search the transaction authorization data record.
[0157] In Example 55, the subject of Examples 48-54 includes, wherein the operation further includes: providing a notification on one of the first application and the second application, or on both the first application and the second application, to perform the specified action.
[0158] Example 56 is a computer-readable storage device that stores instructions for authenticating a transaction at a first application or an application server of the first application. When executed by a first computing device, the instructions cause the first computing device to perform the following operations: identifying a request for a transaction corresponding to the first application, the transaction being associated with a first user account of the first application; and, in response to identifying the request, identifying a transaction authorization data record corresponding to the transaction, the transaction authorization data record specifying a second application executing on a second computing device, a specified second application state, and a specified second application state change corresponding to the transaction, wherein the specified second application state indicates that the second application resides on the second computing device, a pre-specified second user account associated with the second application has an active authentication state on the second application, and wherein the second application state change includes an action performed by a user at the second application within a pre-specified time period. A designated second user account is pre-assigned for authenticating transactions for the first user account in the first application; based on the transaction authorization data record, it is determined, through communication with the second application, an application state service, or the application server of the second application: whether the current state of the second application corresponds to the designated second application state, the determination verifies that the second application resides on the first computing device and that the pre-assigned second user account has an active authentication state corresponding to the second application; and whether the user performed the designated action to change the state of the second application within the pre-specified time period; and in response to determining, based on the transaction authorization data record, that the current state of the second application corresponds to the designated second application state and that the user performed the designated action within the pre-specified time period: authenticating the transaction based on verifying that the second application is in the designated second application state; and processing the transaction upon successful authentication.
[0159] In Example 57, the subject of Example 56 includes, wherein the first application, the second application, or both are web applications.
[0160] In Example 58, the subject of Examples 56-57 includes the following: the specified action performed by the user on the second application is to activate a user interface control.
[0161] In Example 59, the subject of Examples 56-58 includes the following: the first computing device is an untrusted public device.
[0162] In Example 60, the subject matter of Examples 56-59 includes the operation of using the transaction to search the transaction authorization data record to identify the second application on the second computing device and the specified second application state, which includes searching the transaction authorization data record using the type of the transaction being authenticated.
[0163] In Example 61, the subject matter of Examples 56-60 includes the following: the operation of using the transaction to search the transaction authorization data record to identify the second application on the second computing device and the specified second application state includes searching the transaction authorization data record using a risk score associated with the user, the first computing device, or the transaction.
[0164] In Example 62, the subject matter of Examples 56-61 includes the operation of using the transaction to search the transaction authorization data record to identify the second application on the second computing device and the specified second application state, which includes using the user's geographic location to search the transaction authorization data record.
[0165] In Example 63, the subject of Examples 56-62 includes, wherein the operation further includes: providing a notification on one of the first application and the second application, or on both the first application and the second application, to perform the specified action.
[0166] Example 64 is a method for authenticating transactions on a computing device, comprising: using one or more processors at a first application or an application server of the first application to automatically: identify a request for a transaction corresponding to the first application installed on the computing device, the transaction being associated with a first user account of the first application; in response to identifying the request: selecting, based on attributes of the transaction and from transaction authorization data records corresponding to the transaction, a subset of a plurality of other applications from a pre-specified set of other applications and an authentication status for each application in the subset, wherein each authentication status indicates that at least the application resides on a specified computing device and the application has an active authentication status for a pre-specified user account associated with the application, the pre-specified user account being pre-specified for authenticating transactions on the first application. The selected subset of transactions for the first user account of the first application is different from the second subset selected based on attributes of a second transaction that are different from the attributes of the first application; based on the transaction authorization data record, for each specific application in the subset, it is determined whether the current state of the specific application corresponds to the specified authentication state by communicating with the specific application, the application state service, or the application server of the specific application, wherein the determination verifies that the specific application resides on the specified computing device and that the specific application has an active authentication state of the pre-specified user account associated with the application; and in response to determining that the current state of all applications in the subset corresponds to their authentication state: the transaction is authenticated based on verification that all applications in the subset are in their authentication state; and the transaction is processed upon successful authentication.
[0167] In Example 65, the subject of Example 64 includes, wherein the attribute of the transaction is transaction time, and wherein the attribute of the second transaction is different transaction time.
[0168] In Example 66, the subject of Example 65 includes the fact that, except for the transaction time, the transaction and the second transaction are the same.
[0169] In Example 67, the subject of Examples 64-66 includes, wherein the attribute of the first transaction is a prior indication of fraudulent activity on the first user account, the attribute of the second transaction is a prior indication of no fraudulent activity on the first user account, and wherein the selected subset includes more applications than the second subset.
[0170] In Example 68, the subject matter of Examples 64-67 includes, based on the attributes of the transaction and selecting a subset of a pre-specified set of other applications from the transaction authorization data record corresponding to the transaction, and the authentication status for each application in the subset, both of which also include: using the user's historical application usage data to select applications that the user normally used during the transaction.
[0171] In Example 69, the subject of Examples 64-68 includes the use of application security ranking, which is based on the attributes of the transaction and the selection of a subset of multiple other applications from a pre-specified set of other applications from the transaction authorization data records corresponding to the transaction, and the authentication status for each application in the subset.
[0172] In Example 70, the subject of Examples 64-69 includes the following: at least one subset of the plurality of other applications is being executed on a second computing device different from the specified computing device.
[0173] In Example 71, the subject of Example 70 includes the fact that at least one distinct application from a subset of the plurality of other applications is being executed on the specified computing device.
[0174] Example 72 is a computing device for authenticating transactions, the computing device comprising: a hardware processor; and a memory storing instructions that, when executed by the hardware processor, cause the hardware processor to perform operations including: automatically at a first application or an application server of the first application: identifying a request for a transaction corresponding to the first application installed on the computing device, the transaction being associated with a first user account of the first application; in response to identifying the request: selecting, based on attributes of the transaction and from transaction authorization data records corresponding to the transaction, a subset of a plurality of other applications from a pre-specified set of other applications and an authentication status for each application in the subset, wherein each authentication status indicates that at least the application resides on the specified computing device and that the application has an active authentication status of a pre-specified user account associated with the application. A pre-specified user account is pre-assigned for authenticating the transaction for the first user account of the first application, and the selected subset is different from the second subset selected based on the attributes of a second transaction that are different from the attributes of the transaction; based on the transaction authorization data record, for each specific application in the subset, it is determined whether the current state of the specific application corresponds to the specified authentication state by communicating with the specific application, the application state service, or the application server of the specific application, verifying that the specific application resides on the specified computing device and that the specific application has an active authentication state of the pre-specified user account associated with the application; and in response to determining that the current state of all applications in the subset corresponds to their authentication state: authenticating the transaction based on verifying that all applications in the subset are in their authentication state; and processing the transaction upon successful authentication.
[0175] In Example 73, the subject of Example 72 includes, wherein the property of the transaction is transaction time, and wherein the property of the second transaction is different transaction time.
[0176] In Example 74, the subject of Example 73 includes the fact that, except for the transaction time, the transaction and the second transaction are the same.
[0177] In Example 75, the subject matter of Examples 72-74 includes, wherein the attribute of the first transaction is a prior indication of fraudulent activity on the first user account, the attribute of the second transaction is a prior indication of no fraudulent activity on the first user account, and wherein the selected subset includes more applications than the second subset.
[0178] In Example 76, the subject matter of Examples 72-75 includes, based on the attributes of the transaction and selecting a subset of multiple other applications from a pre-specified set of other applications from the transaction authorization data record corresponding to the transaction, and the authentication status for each application in the subset, both of which also include: using the user's historical application usage data to select applications that the user typically uses during the transaction.
[0179] In Example 77, the subject matter of Examples 72-76 includes the selection of a subset of multiple other applications from a pre-specified set of other applications based on the attributes of the transaction and from the transaction authorization data record corresponding to the transaction, as well as the authentication status for each application in the subset, both of which also include the use of application security ranking.
[0180] In Example 78, the subject of Examples 72-77 includes the following: at least one of the subsets of the plurality of other applications is being executed on a second computing device that is different from the specified computing device.
[0181] In Example 79, the subject of Example 78 includes the following: at least one different application from the subset of the plurality of other applications is being executed on the specified computing device.
[0182] Example 80 is a computer-readable storage device that stores instructions for authenticating a transaction at a first application or an application server of the first application, the instructions, when executed by a computing device, causing the computing device to perform operations including: identifying a request for a transaction corresponding to the first application installed on the computing device, the transaction being associated with a first user account of the first application; and, in response to identifying the request: selecting, based on attributes of the transaction and from transaction authorization data records corresponding to the transaction, a subset of a plurality of other applications from a pre-specified set of other applications and an authentication status for each application in the subset, wherein each authentication status indicates that at least the application resides on the specified computing device and that the application has an active authentication status for a pre-specified user account associated with the application, the pre-specified user account being... The transaction for authenticating the first user account for the first application is pre-specified, and the selected subset is different from the second subset selected based on the attributes of a second transaction that are different from the attributes of the first application; based on the transaction authorization data record, for each specific application in the subset, the current state of the specific application is determined by communicating with the specific application, the application state service, or the application server of the specific application to verify that the specific application resides on the specified computing device and that the specific application has an active authentication state of the pre-specified user account associated with the application; and in response to determining that the current state of all applications in the subset corresponds to their authentication state: the transaction is authenticated based on verifying that all applications in the subset are in their authentication state; and the transaction is processed upon successful authentication.
[0183] In Example 81, the subject of Example 80 includes, wherein the attribute of the transaction is transaction time, and wherein the attribute of the second transaction is different transaction time.
[0184] In Example 82, the subject of Example 81 includes the fact that, except for the transaction time, the transaction and the second transaction are the same.
[0185] In Example 83, the subject matter of Examples 80-82 includes, wherein the attribute of the first transaction is a prior indication of fraudulent activity on the first user account, the attribute of the second transaction is a prior indication of no fraudulent activity on the first user account, and wherein the selected subset includes more applications than the second subset.
[0186] In Example 84, the subject matter of Examples 80-83 includes, based on the attributes of the transaction and selecting a subset of multiple other applications from a pre-specified set of other applications from the transaction authorization data record corresponding to the transaction, and the authentication status for each application in the subset, both of which also include: using the user's historical application usage data to select applications that the user normally used during the transaction.
[0187] In Example 85, the subject matter of Examples 80-84 includes the selection of a subset of multiple other applications from a pre-specified set of other applications based on the attributes of the transaction and from the transaction authorization data record corresponding to the transaction, as well as the authentication status for each application in the subset, both of which also include the use of application security ranking.
[0188] In Example 86, the subject of Examples 80-85 includes the following: at least one application from a subset of the plurality of other applications is being executed on a second computing device that is different from the specified computing device.
[0189] In Example 87, the subject of Example 86 includes the following: at least one distinct application from a subset of the plurality of other applications is being executed on the specified computing device.
[0190] Example 88 is a method for verifying a transaction, the method comprising: identifying a plurality of applications associated with a user; selecting a subset of the plurality of applications that satisfy specified authentication criteria for a specific type of transaction to be initiated by a first application; for each specific application in the subset: determining state information of the specific application that satisfies the specified authentication criteria; authenticating using the specific application, the application server of the specific application, or an application state service to obtain an authentication key; identifying a user identifier for the user and a unique device identifier in which the application is installed on the specific application; and storing application data for the specific application in a transaction authorization data record in a database, the application data including the state information, the user identifier, the authentication key, and the device identifier; receiving a transaction request in the first application corresponding to the specific type of transaction to be initiated, and in response: retrieving the transaction authorization data record for the transaction type from the database; and authenticating the transaction by verifying that the specific application is being executed on a device with the correct device identifier and that the specific application is in the required state for each specific application indicated in the transaction authorization data record, wherein the verification uses the stored user identifier, communication channel information, and authentication key to interact with the application, its server, or the application state service.
[0191] In Example 89, the subject of Example 88 includes, wherein identifying the plurality of applications associated with the user includes: communicating with an application service; scanning the user's user device; or receiving identifiers of the plurality of applications from a user interface.
[0192] In Example 90, the subject of Examples 88-89 includes, wherein the plurality of applications includes at least one web application.
[0193] In Example 91, the subject of Examples 88-90 includes, wherein the specified authentication criteria include a security threshold, and wherein, for the transaction initiated by the first application, selecting the subset of the plurality of applications that meet the specified authentication criteria includes: comparing a pre-specified security level of each of the plurality of applications with the security threshold, and selecting those applications that meet the security threshold for the subset.
[0194] In Example 92, the subject matter of Examples 88-91 includes, wherein the unique device identifier comprises or is based on one or more of the following: the device's MAC address, a Universal Unique Identifier (UUID), or an Internet Protocol (IP) address.
[0195] In Example 93, the subject of Examples 88-92 includes, wherein the application data further includes communication channel information for communicating with each specific application, the communication channel information including the API endpoints of the specific application.
[0196] In Example 94, the subject matter of Examples 88-93 includes, wherein, identifying the user identifier for the user on the particular application includes receiving the user identifier from one of: a user interface or the application server of the application.
[0197] Example 95 is a computing device for verifying transactions, the computing device comprising: a hardware processor; and a memory storing instructions that, when executed by the hardware processor, cause the computing device to perform operations including: identifying a plurality of applications associated with a user; selecting a subset of the plurality of applications that satisfy specified authentication criteria for a specific type of transaction to be initiated by a first application; for each specific application in the subset: determining state information of the specific application that satisfies the specified authentication criteria; authenticating using the specific application, the application server of the specific application, or an application state service to obtain an authentication key; and identifying a user identifier for the user on the specific application and a unique device identifier in which the application is installed. The system stores application data for the specific application in a transaction authorization data record in a database, the application data including the status information, user identifier, authentication key, and device identifier; receives a transaction request corresponding to the specific type of transaction to be initiated in the first application, and in response: retrieves the transaction authorization data record for the transaction type from the database; authenticates the transaction by verifying that the specific application is being executed on a device with the correct device identifier and in the required state for each specific application indicated in the transaction authorization data record, wherein the verification uses the stored user identifier, communication channel information, and authentication key to interact with the application, its server, or application status service.
[0198] In Example 96, the subject of Example 95 includes the following, wherein the operation of identifying the plurality of applications associated with the user includes: communicating with an application service; scanning the user's user device; or receiving identifiers of the plurality of applications from a user interface.
[0199] In Example 97, the subject of Examples 95-96 includes, wherein the plurality of applications includes at least one web application.
[0200] In Example 98, the subject matter of Examples 95-97 includes, wherein the specified authentication criteria includes a security threshold, and wherein, the operation of selecting a subset of the plurality of applications that meet the specified authentication criteria for the transaction initiated by the first application includes: comparing a pre-specified security level of each of the plurality of applications with the security threshold, and selecting those applications that meet the security threshold for the subset.
[0201] In Example 99, the subject matter of Examples 95-98 includes, wherein the unique device identifier comprises or is based on one or more of the following: the device's MAC address, a Universal Unique Identifier (UUID), or an Internet Protocol (IP) address.
[0202] In Example 100, the subject of Examples 95-99 includes, wherein the application data further includes communication channel information for communicating with each specific application, the communication channel information including the API endpoint of the specific application.
[0203] In Example 101, the subject of Examples 95-100 includes the following, wherein the operation of identifying the user identifier for the user on the particular application includes receiving the user identifier from one of: a user interface or the application server of the application.
[0204] Example 102 is a computer-readable storage device that stores instructions for verifying transactions. When executed by a computing device, the instructions cause the computing device to perform the following operations: identifying multiple applications associated with a user; selecting a subset of the multiple applications that satisfy specified authentication criteria for a specific type of transaction to be initiated by a first application; for each specific application in the subset: determining state information of the specific application that satisfies the specified authentication criteria; authenticating using the specific application, the application server of the specific application, or an application state service to obtain an authentication key; identifying a user identifier for the user on the specific application and a unique device identifier in which the application is installed; and assigning the authentication key to the user on the specific application. Application data for a specific application is stored in transaction authorization data records in a database. This application data includes the status information, user identifier, authentication key, and device identifier. In the first application, a transaction request corresponding to the specific type of transaction to be initiated is received, and in response: the transaction authorization data record for the transaction type is retrieved from the database; the transaction is authenticated by verifying that the specific application is executing on a device with the correct device identifier and in the required state for each specific application indicated in the transaction authorization data record, wherein the verification uses the stored user identifier, communication channel information, and authentication key to interact with the application, its server, or an application status service.
[0205] In Example 103, the subject of Example 102 includes the following, wherein the operation of identifying the plurality of applications associated with the user includes: communicating with an application service; scanning the user's user device; or receiving identifiers of the plurality of applications from a user interface.
[0206] In Example 104, the subject of Examples 102-103 includes, wherein the plurality of applications includes at least one web application.
[0207] In Example 105, the subject matter of Examples 102-104 includes, wherein the specified authentication criteria includes a security threshold, and wherein the operation of selecting a subset of a plurality of applications that meet the specified authentication criteria for a transaction initiated by a first application includes: comparing a pre-specified security level of each of the plurality of applications with the security threshold, and selecting those applications that meet the security threshold for the subset.
[0208] In Example 106, the subject matter of Examples 102-105 includes, wherein the unique device identifier comprises or is based on one or more of the following: the device's MAC address, a Universal Unique Identifier (UUID), or an Internet Protocol (IP) address.
[0209] In Example 107, the subject matter of Examples 102-106 includes, wherein the application data further includes communication channel information for communicating with each specific application, the communication channel information including the API endpoint of the specific application.
[0210] In Example 108, the subject matter of Examples 102-107 includes the following, wherein the operation of identifying the user identifier for the user on the particular application includes receiving the user identifier from one of: a user interface or the application server of the application.
[0211] Example 109 is at least one machine-readable medium including instructions that, when executed by processing circuitry, cause the processing circuitry to perform the operation of any of the implementations of Examples 1-108.
[0212] Example 110 is a device that includes a unit for implementing any one of Examples 1-108.
[0213] Example 111 is a system that implements any one of Examples 1-108.
[0214] Example 112 is a method to implement any one of Examples 1-108.
Claims
1. A method for authenticating transactions of a first application executed on a first computing device, the method comprising: Automatically using one or more processors at the first application or the application server of the first application: Identify a request for a transaction corresponding to the first application, the transaction being associated with a first user account of the first application [Figures 9, 910]; In response to the request identified as follows: A transaction authorization data record is identified corresponding to the transaction, the transaction authorization data record corresponding to the transaction and specifying a second application executed on a second computing device, a specified second application state, and a specified second application state change, wherein the specified second application state indicates that: the second application resides on the second computing device, a pre-specified second user account associated with the second application has an active authentication state on the second application, and wherein the second application state change includes an action performed by a user on the second application within a pre-specified time, the pre-specified second user account being pre-specified for authenticating the transaction for the first user account of the first application [Figures 9, 912]; Based on the transaction authorization data record, this is determined through communication with the second application, the application status service, or the application server of the second application: Whether the current state of the second application corresponds to the specified second application state, the determination verifies that the second application resides on the first computing device and that the pre-specified second user account has an activity authentication state corresponding to the second application [Figures 9, 914]; and Whether the user performed the specified action within the pre-specified time to achieve the second application state change [Figure 9, 916]; and In response to determining, based on the transaction authorization data record, that the current state of the second application corresponds to the specified second application state, and that the user has performed the specified action within the pre-specified time period: The transaction is authenticated based on verifying that the second application is in the specified second application state [Figures 9, 918]; and The transaction is processed upon successful authentication [Figure 9, 920].
2. The method according to claim 1, wherein, The first application, the second application, or both are web applications.
3. The method according to claim 1, wherein, The specified action performed by the user on the second application is to activate a user interface control.
4. The method according to claim 1, wherein, The first computing device is an untrusted public device.
5. The method according to claim 1, wherein, Using the transaction to search the transaction authorization data record to identify the second application on the second computing device and the specified second application status includes: searching the transaction authorization data record using the type of the transaction being authenticated.
6. The method according to claim 1, wherein, Using the transaction to search the transaction authorization data record to identify the second application on the second computing device and the specified second application status includes: using a risk score associated with the user, the first computing device, or the transaction to search the transaction authorization data record.
7. The method according to claim 1, wherein, Using the transaction to search the transaction authorization data record to identify the second application on the second computing device and the specified second application status includes: using the user's geographic location to search the transaction authorization data record.
8. The method according to claim 1, further comprising: A notification may be provided on one of the first application, the second application, or both the first application and the second application to perform the specified action.
9. A first computing device that executes a first application or part of a first application server for authenticating transactions of the first application, said computing device comprising: Hardware processor; The memory stores instructions that, when executed by the hardware processor, cause the computing device to perform operations including: Identify a request for a transaction corresponding to the first application, the transaction being associated with a first user account of the first application [Figures 9, 910]; In response to the request identified as follows: A transaction authorization data record is identified corresponding to the transaction, the transaction authorization data record corresponding to the transaction and specifying a second application executed on a second computing device, a specified second application state, and a specified second application state change, wherein the specified second application state indicates that: the second application resides on the second computing device, a pre-specified second user account associated with the second application has an active authentication state on the second application, and wherein the second application state change includes an action performed by a user on the second application within a pre-specified time, the pre-specified second user account being pre-specified for authenticating the transaction for the first user account of the first application [Figures 9, 912]; Based on the transaction authorization data record, this is determined through communication with the second application, the application status service, or the application server of the second application: Whether the current state of the second application corresponds to the specified second application state, the determination verifies that the second application resides on the first computing device and that the pre-specified second user account has an activity authentication state corresponding to the second application [Figures 9, 914]; and Whether the user performed the specified action within the pre-specified time to achieve the second application state change [Figure 9, 916]; and In response to determining, based on the transaction authorization data record, that the current state of the second application corresponds to the specified second application state, and that the user has performed the specified action within the pre-specified time period: The transaction is authenticated based on verifying that the second application is in the specified second application state [Figures 9, 918]; and The transaction is processed upon successful authentication [Figure 9, 920].
10. The first computing device according to claim 9, wherein, The first application, the second application, or both are web applications.
11. The first computing device according to claim 9, wherein, The specified action performed by the user on the second application is to activate a user interface control.
12. The first computing device according to claim 9, wherein, The first computing device is an untrusted public device.
13. The first computing device according to claim 9, wherein, The operation of using the transaction to search the transaction authorization data record to identify the second application on the second computing device and the specified second application state includes: searching the transaction authorization data record using the type of the transaction being authenticated.
14. The first computing device according to claim 9, wherein, The operation of using the transaction to search the transaction authorization data record to identify the second application on the second computing device and the specified second application state includes: searching the transaction authorization data record using a risk score associated with the user, the first computing device, or the transaction.
15. The first computing device according to claim 9, wherein, The operation of using the transaction to search the transaction authorization data record to identify the second application on the second computing device and the specified second application state includes: using the user's geographic location to search the transaction authorization data record.
16. The first computing device according to claim 9, wherein, The operation also includes providing a notification on one of the first application, the second application, or both the first application and the second application to perform the specified action.
17. A computer-readable storage device storing instructions for authenticating transactions at a first application or an application server of the first application, the instructions, when executed by a first computing device, causing the first computing device to perform operations including: Identify a request for a transaction corresponding to the first application, the transaction being associated with a first user account of the first application [Figures 9, 910]; In response to the request identified as follows: A transaction authorization data record is identified corresponding to the transaction, wherein the transaction authorization data record, corresponding to the transaction, specifies a second application to be executed on a second computing device, a specified second application state, and a specified second application state change, wherein... The specified second application state indicates that the second application resides on the second computing device, a pre-specified second user account associated with the second application has an active authentication state on the second application, and wherein the change of the second application state includes an action performed by a user on the second application within a pre-specified time period, the pre-specified second user account being pre-specified for authenticating the transaction of the first user account for the first application [Figures 9, 912]. Based on the transaction authorization data record, this is determined through communication with the second application, the application status service, or the application server of the second application: Whether the current state of the second application corresponds to the specified second application state, the determination verifies that the second application resides on the first computing device and that the pre-specified second user account has an activity authentication state corresponding to the second application [Figures 9, 914]; and Whether the user performed the specified action within the pre-specified time to achieve the second application state change [Figure 9, 916]; and In response to determining, based on the transaction authorization data record, that the current state of the second application corresponds to the specified second application state, and that the user has performed the specified action within the pre-specified time period: The transaction is authenticated based on verifying that the second application is in the specified second application state [Figures 9, 918]; and The transaction is processed upon successful authentication [Figure 9, 920].
18. The computer-readable storage device according to claim 17, wherein, The first application, the second application, or both are web applications.
19. The computer-readable storage device according to claim 17, wherein, The specified action performed by the user on the second application is to activate a user interface control.
20. The computer-readable storage device of claim 17, wherein, The first computing device is an untrusted public device.
