Patent Application
20200184049
Aspects of the disclosure relate to providing information security and preventing unauthorized access to resources of an information system. In particular, one or more aspects of the disclosure relate to preventing unauthorized access to information resources by processing authentication requests to secured information systems based on machine-learned event profiles.
As organizations increasingly provide electronic portals via which various users may access, view, and/or modify information, including client information, ensuring the safety and security of information maintained by such organizations and/or made available via such portals is increasingly important. In many instances, however, it may be difficult to ensure the safety and security of such information while also optimizing the efficient and effective technical operations of the computer systems that maintain such information and/or provide such portals.
Aspects of the disclosure provide effective, efficient, scalable, and convenient technical solutions that address and overcome the technical problems associated with providing information security and preventing unauthorized access to resources of an information system by using machine-learned event profiles in processing authentication requests.
In accordance with one or more embodiments, a computing platform having at least one processor, a communication interface, and memory may receive, via the communication interface, from an account portal computing platform, a first authentication request corresponding to a request for a first user of a first client computing device to access one or more secured information resources associated with a first user account in a first client portal session. Based on receiving the first authentication request from the account portal computing platform, the computing platform may capture one or more behavioral parameters associated with the first client computing device. Subsequently, the computing platform may generate one or more authentication prompts associated with the first authentication request. Thereafter, the computing platform may receive one or more authentication prompt responses corresponding to the one or more authentication prompts associated with the first authentication request. Subsequently, the computing platform may evaluate a first event pattern associated with the first authentication request. Based on evaluating the first event pattern associated with the first authentication request and validating the one or more authentication prompt responses corresponding to the one or more authentication prompts associated with the first authentication request, the computing platform may generate one or more authentication commands directing the account portal computing platform to allow access to the one or more secured information resources associated with the first user account in the first client portal session. Subsequently, the computing platform may send, via the communication interface, to the account portal computing platform, the one or more authentication commands directing the account portal computing platform to allow access to the one or more secured information resources associated with the first user account in the first client portal session.
In some embodiments, capturing the one or more behavioral parameters associated with the first client computing device may include logging order information identifying an order of one or more computing events associated with the first authentication request, timing information identifying a timing of the one or more computing events associated with the first authentication request, and device information identifying a device used in connection with the one or more computing events associated with the first authentication request.
In some embodiments, generating the one or more authentication prompts associated with the first authentication request may include sending at least one authentication prompt to the account portal computing platform. In some embodiments, generating the one or more authentication prompts associated with the first authentication request may include sending at least one authentication prompt to at least one user device registered to the first user account.
In some embodiments, evaluating the first event pattern associated with the first authentication request may include determining that the first event pattern associated with the first authentication request is a closer match to a predetermined valid event pattern than a predetermined malicious event pattern. In some embodiments, the predetermined valid event pattern may be generated by the computing platform based on at least one previous successful login occurrence associated with the first user account. In some embodiments, the predetermined valid event pattern may include valid order data, valid timing data, and valid device data associated with the at least one previous successful login occurrence associated with the first user account. In some embodiments, the predetermined valid event pattern may be generated by the computing platform based on valid population-level authentication data. In some embodiments, the predetermined malicious event pattern may be generated by the computing platform based on malicious population-level authentication data.
In some embodiments, prior to receiving the first authentication request from the account portal computing platform, the computing platform may create a first user account profile corresponding to the first user account. In addition, the computing platform may register one or more user devices as being linked to the first user account.
In some embodiments, prior to receiving the first authentication request from the account portal computing platform, the computing platform may update the first user account profile to include a valid event pattern based on a successful login occurrence associated with the first user account. In some embodiments, prior to receiving the first authentication request from the account portal computing platform, the computing platform may update valid population-level authentication data maintained by the computing platform based on the successful login occurrence associated with the first user account.
In some embodiments, the computing platform may capture activity data associated with the first client portal session. Subsequently, the computing platform may evaluate the captured activity data using baseline activity data. In some instances, based on evaluating the captured activity data using the baseline activity data, the computing platform may continue to allow access to the one or more secured information resources associated with the first user account in the first client portal session. In some instances, based on evaluating the captured activity data using the baseline activity data, the computing platform may halt access to the one or more secured information resources associated with the first user account in the first client portal session.
In some embodiments, the computing platform may update a valid event pattern associated with the first user account based on sending the one or more authentication commands to the account portal computing platform. In some embodiments, the computing platform may update valid population-level authentication data maintained by the computing platform based on sending the one or more authentication commands to the account portal computing platform.
In some embodiments, the computing platform may receive, via the communication interface, from the account portal computing platform, a second authentication request corresponding to a request for a second user of a second client computing device to access one or more secured information resources associated with a second user account in a second client portal session. Based on receiving the second authentication request from the account portal computing platform, the computing platform may capture one or more behavioral parameters associated with the second client computing device. Subsequently, the computing platform may generate one or more authentication prompts associated with the second authentication request. Thereafter, the computing platform may receive one or more authentication prompt responses corresponding to the one or more authentication prompts associated with the second authentication request. Subsequently, the computing platform may evaluate a second event pattern associated with the second authentication request. Based on evaluating the second event pattern associated with the second authentication request and validating the one or more authentication prompt responses corresponding to the one or more authentication prompts associated with the second authentication request, the computing platform may generate one or more authentication commands directing the account portal computing platform to allow access to the one or more secured information resources associated with the second user account in the second client portal session. Subsequently, the computing platform may send, via the communication interface, to the account portal computing platform, the one or more authentication commands directing the account portal computing platform to allow access to the one or more secured information resources associated with the second user account in the second client portal session.
These features, along with many others, are discussed in greater detail below.
The present disclosure is illustrated by way of example and not limited in the accompanying figures in which like reference numerals indicate similar elements and in which:
In the following description of various illustrative embodiments, reference is made to the accompanying drawings, which form a part hereof, and in which is shown, by way of illustration, various embodiments in which aspects of the disclosure may be practiced. It is to be understood that other embodiments may be utilized, and structural and functional modifications may be made, without departing from the scope of the present disclosure.
It is noted that various connections between elements are discussed in the following description. It is noted that these connections are general and, unless specified otherwise, may be direct or indirect, wired or wireless, and that the specification is not intended to be limiting in this respect.
Some aspects of the disclosure relate to controlling user authentication based on a sequence of different authentication events. For example, using a machine-learning algorithm, a current or recent authentication event associated with a particular customer or user account may be evaluated, from a risk perspective, in connection with a sequence of other recent authentication events associated with the particular customer or user account. This may enable the machine-learning algorithm to identify potentially malicious authentication requests based on the order, timing, method, and/or other parameters of such requests. In some instances, a filtering component may be used to differentiate suspicious events from non-suspicious events (e.g., based on behavioral profiling) to determine which events should be included in the sequence of authentication events that are evaluated using the machine-learning algorithm. In some instances, a combination of user-specific models and population-level models may be used. In addition, the machine-learning system may continuously train and/or otherwise update models to account for changes in user behavior over time at both a user-specific level and at a population level (e.g., as new authentication capabilities, such as facial recognition are more widely adopted, and/or the like). In some instances, models may utilize other data sources in addition to customer-interaction gathered data, such as internal data (which may, e.g., be input by an internal malicious activity group of the financial institution) and/or industry-level data (which may, e.g., be received from other banks, retailers, and/or the like).
As illustrated in greater detail below, client authentication computing platform 110 may include one or more computing devices configured to perform one or more of the functions described herein. For example, client authentication computing platform 110 may include one or more computers (e.g., laptop computers, desktop computers, servers, server blades, or the like).
Account portal computing platform 120 may include one or more computing devices and/or other computer components (e.g., processors, memories, communication interfaces). In addition, and as illustrated in greater detail below, account portal computing platform 120 may be configured to generate, host, transmit, and/or otherwise provide one or more web pages and/or other graphical user interfaces (which may, e.g., cause one or more other computer systems to display and/or otherwise present the one or more web pages and/or other graphical user interfaces). In some instances, the web pages and/or other graphical user interfaces generated by account portal computing platform 120 may be associated with a client portal provided by an organization, such as an online banking portal and/or a mobile banking portal provided by a financial institution. Such a portal may, for instance, provide customers of the financial institution with access to financial account information (e.g., account balance information, account statements, recent transaction history information, or the like) and/or may provide customers of the financial institution with menus, controls, and/or other options to schedule and/or execute various transactions (e.g., online bill pay transactions, person-to-person funds transfer transactions, or the like).
Enterprise server infrastructure 125 may include one or more computing devices and/or other computer components (e.g., processors, memories, communication interfaces). In addition, and as illustrated in greater detail below, enterprise server infrastructure 125 may be configured to provide various enterprise and/or back-office computing functions for an organization, such as a financial institution. For example, enterprise server infrastructure 125 may include various servers and/or databases that store and/or otherwise maintain account information, such as financial account information including account balances, transaction history, account owner information, and/or other information. In addition, enterprise server infrastructure 125 may process and/or otherwise execute transactions on specific accounts based on commands and/or other information received from account portal computing platform 120 and/or other computer systems included in computing environment 100.
Client computing device 130 may be a personal computing device (e.g., desktop computer, laptop computer) or mobile computing device (e.g., smartphone, tablet) that may be linked to and/or used by a first user (e.g., of a client portal provided by account portal computing platform 120). Client computing device 140 may be a personal computing device (e.g., desktop computer, laptop computer) or mobile computing device (e.g., smartphone, tablet) that also may be linked to and/or used by the first user (e.g., of a client portal provided by account portal computing platform 120). Client computing device 150 may be a personal computing device (e.g., desktop computer, laptop computer) or mobile computing device (e.g., smartphone, tablet) that may be linked to and/or used by a second user (e.g., of a client portal provided by account portal computing platform 120) different from the first user. Client computing device 160 may be a personal computing device (e.g., desktop computer, laptop computer) or mobile computing device (e.g., smartphone, tablet) that also may be linked to and/or used by the second user (e.g., of a client portal provided by account portal computing platform 120).
Computing environment 100 also may include one or more networks, which may interconnect one or more of client authentication computing platform 110, account portal computing platform 120, enterprise server infrastructure 125, client computing device 130, client computing device 140, client computing device 150, and client computing device 160. For example, computing environment 100 may include a private network 170 (which may, e.g., interconnect client authentication computing platform 110, account portal computing platform 120, enterprise server infrastructure 125, and/or one or more other systems which may be associated with an organization, such as a financial institution) and public network 180 (which may, e.g., interconnect client computing device 130, client computing device 140, client computing device 150, and client computing device 160 with private network 170 and/or one or more other systems, public networks, sub-networks, and/or the like).
In one or more arrangements, client computing device 130, client computing device 140, client computing device 150, client computing device 160, and/or the other systems included in computing environment 100 may be any type of computing device capable of receiving a user interface, receiving input via the user interface, and communicating the received input to one or more other computing devices. For example, client computing device 130, client computing device 140, client computing device 150, client computing device 160, and/or the other systems included in computing environment 100 may, in some instances, be and/or include server computers, desktop computers, laptop computers, tablet computers, smart phones, or the like that may include one or more processors, memories, communication interfaces, storage devices, and/or other components. As noted above, and as illustrated in greater detail below, any and/or all of client authentication computing platform 110, account portal computing platform 120, enterprise server infrastructure 125, client computing device 130, client computing device 140, client computing device 150, and client computing device 160 may, in some instances, be special-purpose computing devices configured to perform specific functions.
Referring to
At step 203, client authentication computing platform 110 may create a second user account profile (e.g., by creating and/or storing one or more records in client authentication database 112b). For example, at step 203, client authentication computing platform 110 may create a second user account profile corresponding to a second user account. At step 204, client authentication computing platform 110 may register user devices with the second user account. For example, at step 204, client authentication computing platform 110 may register one or more user devices (e.g., client computing device 150, client computing device 160) as being linked to the second user account.
Referring to
At step 206, client authentication computing platform 110 may receive the authentication request from account portal computing platform 120. At step 207, client authentication computing platform 110 may capture one or more behavioral parameters associated with the authentication request received from account portal computing platform 120 at step 206. For instance, client authentication computing platform 110 may log information identifying an order of events associated with the authentication request received from account portal computing platform 120, information identifying a timing of events associated with the authentication request received from account portal computing platform 120, information identifying a communication method associated with the authentication request received from account portal computing platform 120, information about the device (e.g., client computing device 130) associated with the authentication request received from account portal computing platform 120 (e.g., one or more device identifiers, language settings, and/or other device information), and/or other information. As discussed below, any and/or all of this information may be used by client authentication computing platform 110 in building an event profile (which may, e.g., be used by client authentication computing platform 110 in evaluating future login events associated with the first user account).
At step 208, client authentication computing platform 110 may authenticate the user of client computing device 130. For example, at step 208, client authentication computing platform 110 may validate one or more authentication credentials included in and/or otherwise associated with the authentication request received from account portal computing platform 120, may validate one or more responses to one or more authentication prompts (e.g., one-time passcode prompts, biometric prompts, security question prompts, and/or the like) associated with the authentication request received from account portal computing platform 120, and/or may otherwise determine to grant and/or otherwise allow client computing device 130 to access the first user account based on exchanging information with client computing device 130 and/or one or more other systems and/or devices.
Referring to
Referring to
At step 214, client authentication computing platform 110 may capture activity data (which may, e.g., include information identifying various specific parameters of usage of the portal). For instance, client authentication computing platform 110 may capture activity data identifying specific pages, menus, and/or resources accessed by the user of client computing device 130 via the portal, activity data identifying amounts of time that specific pages, menus, and/or resources were accessed by the user of client computing device 130 via the portal, activity data identifying an order in which specific pages, menus, and/or resources were accessed by the user of client computing device 130 via the portal, and/or other activity data.
At step 215, client authentication computing platform 110 may update the first user account profile (e.g., to include the activity data captured at step 214 and/or to include event profile data determined by client authentication computing platform 110 based on the activity data). For example, at step 215, client authentication computing platform 110 may update the first user account profile to include a valid event pattern based on a successful login occurrence associated with the first user account. For instance, the valid event pattern may correspond to a user-specific machine-learned event model (which may, e.g., be generated by client authentication machine learning engine 112c and/or client authentication computing platform 110) and may be used in evaluating future authentication events, as discussed in greater detail below. In some instances, client authentication machine learning engine 112c and/or client authentication computing platform 110 may filter specific portions of the captured activity data in generating and/or otherwise determining the valid event pattern (e.g., to remove data points associated with portal functions that might only be accessed one time or sporadically, so as to improve the likelihood that the model matches the most common account access use cases for the specific user).
At step 216, client authentication computing platform 110 may update a population-level authentication model (e.g., to include the activity data captured at step 214 and/or to include event profile data determined by client authentication computing platform 110 based on the activity data). For example, at step 216, client authentication computing platform 110 may update valid population-level authentication data maintained by the computing platform (e.g., client authentication computing platform 110) based on the successful login occurrence associated with the first user account. In some instances, in addition to including the activity data captured at step 214 and/or the event profile data determined by client authentication computing platform 110 based on the activity data, the valid population-level authentication data maintained by client authentication computing platform 110 may include and/or be determined based on internal data (which may, e.g., identify specific parameters and/or patterns associated with valid usage and/or malicious usage and which may be provided by and/or obtained from an enterprise organization operating client authentication computing platform 110) and/or industry data (which also may, e.g., identify specific parameters and/or patterns associated with valid usage and/or malicious usage and which may be provided by and/or obtained from one or more other organizations different from the enterprise organization operating client authentication computing platform 110).
Subsequently, client authentication computing platform 110 may process additional authentication events involving the first user account and the same and/or other client devices, along with additional authentication events involving other user accounts. In the example steps described below, client authentication computing platform 110 may process a second authentication event involving the first user account, and client authentication computing platform 110 may evaluate whether the authentication event is legitimate or potentially malicious using the event patterns and/or models described above.
Referring to
At step 218, client authentication computing platform 110 may receive the authentication request from account portal computing platform 120. For example, at step 218, client authentication computing platform 110 may receive, via the communication interface (e.g., communication interface 113), from an account portal computing platform (e.g., account portal computing platform 120), a first authentication request corresponding to a request for a first user of a first client computing device (e.g., client computing device 140) to access one or more secured information resources associated with a first user account in a first client portal session.
At step 219, client authentication computing platform 110 may capture one or more behavioral parameters associated with the authentication request received from account portal computing platform 120 at step 218. For example, at step 219, based on receiving the first authentication request from the account portal computing platform (e.g., account portal computing platform 120), client authentication computing platform 110 may capture one or more behavioral parameters associated with the first client computing device (e.g., client computing device 140). For instance, client authentication computing platform 110 may log information identifying an order of events associated with the authentication request received from account portal computing platform 120, information identifying a timing of events associated with the authentication request received from account portal computing platform 120, information identifying a communication method associated with the authentication request received from account portal computing platform 120, information about the device (e.g., client computing device 140) associated with the authentication request received from account portal computing platform 120 (e.g., one or more device identifiers, language settings, and/or other device information), and/or other information.
In some embodiments, capturing the one or more behavioral parameters associated with the first client computing device may include logging order information identifying an order of one or more computing events associated with the first authentication request, timing information identifying a timing of the one or more computing events associated with the first authentication request, and device information identifying a device used in connection with the one or more computing events associated with the first authentication request. For example, in capturing the one or more behavioral parameters associated with the first client computing device (e.g., client computing device 140), client authentication computing platform 110 may log order information identifying an order of one or more computing events associated with the first authentication request, timing information identifying a timing of the one or more computing events associated with the first authentication request, and device information identifying a device used in connection with the one or more computing events associated with the first authentication request. For instance, the order information may identify an order in which the user of client computing device 140 selected one or more user interface elements, the timing information may indicate amounts of time that elapsed between such selections made by the user of client computing device 140, and the device information may identify specific parameters of client computing device 140 (e.g., one or more unique device identifiers, device language preferences, device version, operating system, operating system version, and/or the like). As illustrated below, any and/or all of this information may be compared (e.g., by client authentication computing platform 110) against one or more event patterns to evaluate whether the authentication request is likely legitimate or potentially malicious.
At step 220, client authentication computing platform 110 may generate one or more authentication prompts. For example, at step 220, client authentication computing platform 110 may generate one or more authentication prompts associated with the first authentication request. In some embodiments, generating the one or more authentication prompts associated with the first authentication request may include sending at least one authentication prompt to the account portal computing platform. For example, in generating the one or more authentication prompts associated with the first authentication request, client authentication computing platform 110 may send at least one authentication prompt to the account portal computing platform (e.g., account portal computing platform 120), which may, e.g., present the at least one authentication prompt to the device requesting access to the user account. In some embodiments, generating the one or more authentication prompts associated with the first authentication request may include sending at least one authentication prompt to at least one user device registered to the first user account. For example, in generating the one or more authentication prompts associated with the first authentication request, client authentication computing platform 110 may send at least one authentication prompt to at least one user device registered to the first user account. For instance, client authentication computing platform 110 may send one or more one-time passcodes, biometric authentication prompts, and/or the like to client computing device 130, client computing device 140, and/or one or more other devices registered to the first user account to confirm, using a multi-factor authentication method, that the authentication request is valid.
Referring to
At step 222, client authentication computing platform 110 may evaluate an event pattern associated with the authentication request (e.g., based on the one or more captured behavioral parameters associated with the authentication request). For example, at step 222, client authentication computing platform 110 may evaluate a first event pattern associated with the first authentication request. For instance, the event pattern may define various contours of an event profile that may be used by client authentication computing platform 110 in comparing different authentication events and differentiating between likely legitimate and likely malicious authentication events.
In some embodiments, evaluating the first event pattern associated with the first authentication request may include determining that the first event pattern associated with the first authentication request is a closer match to a predetermined valid event pattern than a predetermined malicious event pattern. For example, in evaluating the first event pattern associated with the first authentication request, client authentication computing platform 110 may determine that the first event pattern associated with the first authentication request is a closer match to a predetermined valid event pattern than a predetermined malicious event pattern. For instance, if the first event pattern associated with the first authentication request is a closer match to a predetermined valid event pattern than a predetermined malicious event pattern, the example event sequence may continue as illustrated, and if the first event pattern associated with the first authentication request is a closer match to a predetermined malicious event pattern than a predetermined valid event pattern, client authentication computing platform 110 may generate and/or send one or more error messages and/or may prevent the requesting user device (e.g., client computing device 140) from accessing the user account. In some instances, client authentication computing platform 110 may calculate and/or otherwise determine the closeness of the match by calculating distance amounts between the captured behavioral parameters associated with the authentication request and corresponding features of one or more valid event patterns and one or more malicious event patterns.
In some embodiments, the predetermined valid event pattern may be generated by the computing platform based on at least one previous successful login occurrence associated with the first user account. For example, the predetermined valid event pattern (which may, e.g., be used by client authentication computing platform 110 at step 222 in evaluating the first event pattern) may be generated by the computing platform (e.g., client authentication computing platform 110) based on at least one previous successful login occurrence associated with the first user account.
In some embodiments, the predetermined valid event pattern may include valid order data, valid timing data, and valid device data associated with the at least one previous successful login occurrence associated with the first user account. For example, the predetermined valid event pattern (which may, e.g., be used by client authentication computing platform 110 at step 222 in evaluating the first event pattern) may include valid order data (e.g., identifying an order in which specific computing operations occurred in connection with a previous login event), valid timing data (e.g., identifying amounts of time that elapsed during which specific computing operations occurred in connection with a previous login event), and valid device data (e.g., identifying one or more parameters of a device used in connection with a previous login event) associated with the at least one previous successful login occurrence associated with the first user account.
In some embodiments, the predetermined valid event pattern may be generated by the computing platform based on valid population-level authentication data. For example, in addition to and/or instead of being generated based on one or more data points in the examples described above, the predetermined valid event pattern (which may, e.g., be used by client authentication computing platform 110 at step 222 in evaluating the first event pattern) may be generated by the computing platform (e.g., client authentication computing platform 110) based on valid population-level authentication data. For instance, client authentication computing platform 110 may generate the predetermined valid event pattern based on valid population-level authentication data that may include and/or be determined based on authentication event information associated with a plurality of other users linked to other user accounts (e.g., different from the first user account) maintained by client authentication computing platform 110 and/or account portal computing platform 120.
In some embodiments, the predetermined malicious event pattern may be generated by the computing platform based on malicious population-level authentication data. For example, the predetermined malicious event pattern (which may, e.g., be used by client authentication computing platform 110 at step 222 in evaluating the first event pattern) may be generated by the computing platform (e.g., client authentication computing platform 110) based on malicious population-level authentication data. For instance, client authentication computing platform 110 may generate the predetermined malicious event pattern based on authentication data that may include and/or be determined based on authentication event information associated with a plurality of identified malicious attempts and/or events involving the same user account and/or other user accounts. In some instances, client authentication computing platform 110 may additionally or alternatively generate the predetermined malicious event pattern based on industry data obtained from external sources.
At step 223, client authentication computing platform 110 may generate one or more authentication commands (e.g., based on determining that the event pattern more closely matches the valid pattern than the malicious pattern). For example, at step 223, based on evaluating the first event pattern associated with the first authentication request and validating the one or more authentication prompt responses corresponding to the one or more authentication prompts associated with the first authentication request, client authentication computing platform 110 may generate one or more authentication commands directing the account portal computing platform (e.g., account portal computing platform 120) to allow access to the one or more secured information resources associated with the first user account in the first client portal session. Alternatively, if client authentication computing platform 110 determines that the event pattern more closely matches the malicious pattern than the valid pattern, client authentication computing platform 110 may generate and/or send one or more error messages.
At step 224, client authentication computing platform 110 may send the one or more authentication commands to account portal computing platform 120. For example, at step 224, client authentication computing platform 110 may send, via the communication interface (e.g., communication interface 113), to the account portal computing platform (e.g., account portal computing platform 120), the one or more authentication commands directing the account portal computing platform (e.g., account portal computing platform 120) to allow access to the one or more secured information resources associated with the first user account in the first client portal session.
Referring to
At step 228, client authentication computing platform 110 may capture activity data (e.g., associated with usage of the portal user interfaces being provided to client computing device 140 by account portal computing platform 120). For example, at step 228, client authentication computing platform 110 may capture activity data associated with the first client portal session. For instance, client authentication computing platform 110 may capture such activity data similar to how client authentication computing platform 110 may capture activity data in the examples steps described above.
Referring to
At step 230, client authentication computing platform 110 may continue allowing access to the user account (e.g., based on determining that the captured activity data is valid; in addition, client authentication computing platform 110 may continue monitoring and/or evaluating activity). For example, at step 230, based on evaluating the captured activity data using the baseline activity data, client authentication computing platform 110 may continue to allow access to the one or more secured information resources associated with the first user account in the first client portal session. Alternatively, if client authentication computing platform 110 determines that the captured activity data is invalid, client authentication computing platform 110 may halt the session and/or terminate the session. For example, based on evaluating the captured activity data using the baseline activity data, client authentication computing platform 110 may halt access to the one or more secured information resources associated with the first user account in the first client portal session.
At step 231, client authentication computing platform 110 may update the first user account profile (e.g., in view of the session and/or activity in the prior steps described above). For example, at step 231, client authentication computing platform 110 may update a valid event pattern associated with the first user account based on sending the one or more authentication commands to the account portal computing platform (e.g., account portal computing platform 120). For instance, client authentication computing platform 110 may update the valid event pattern stored in the user profile.
At step 232, client authentication computing platform 110 may update the population-level authentication model (e.g., in view of the session and/or activity in the prior steps described above). For example, at step 232, client authentication computing platform 110 may update valid population-level authentication data maintained by the computing platform (e.g., client authentication computing platform 110) based on sending the one or more authentication commands to the account portal computing platform (e.g., account portal computing platform 120).
Subsequently, client authentication computing platform 110 may similarly process one or more authentication events from the same and/or other devices involving the same and/or other user accounts by performing one or more actions similar to those described above. For example, client authentication computing platform 110 may receive, via the communication interface (e.g., communication interface 113), from the account portal computing platform (e.g., account portal computing platform 120), a second authentication request corresponding to a request for a second user of a second client computing device (e.g., client computing device 150) to access one or more secured information resources associated with a second user account in a second client portal session. Based on receiving the second authentication request from the account portal computing platform (e.g., account portal computing platform 120), client authentication computing platform 110 may capture one or more behavioral parameters associated with the second client computing device (e.g., client computing device 150). Subsequently, client authentication computing platform 110 may generate one or more authentication prompts associated with the second authentication request. Thereafter, client authentication computing platform 110 may receive one or more authentication prompt responses corresponding to the one or more authentication prompts associated with the second authentication request. Then, client authentication computing platform 110 may evaluate a second event pattern associated with the second authentication request. Based on evaluating the second event pattern associated with the second authentication request and validating the one or more authentication prompt responses corresponding to the one or more authentication prompts associated with the second authentication request, client authentication computing platform 110 may generate one or more authentication commands directing the account portal computing platform (e.g., account portal computing platform 120) to allow access to the one or more secured information resources associated with the second user account in the second client portal session. Subsequently, client authentication computing platform 110 may send, via the communication interface (e.g., communication interface 113), to the account portal computing platform (e.g., account portal computing platform 120), the one or more authentication commands directing the account portal computing platform (e.g., account portal computing platform 120) to allow access to the one or more secured information resources associated with the second user account in the second client portal session.
One or more aspects of the disclosure may be embodied in computer-usable data or computer-executable instructions, such as in one or more program modules, executed by one or more computers or other devices to perform the operations described herein. Generally, program modules include routines, programs, objects, components, data structures, and the like that perform particular tasks or implement particular abstract data types when executed by one or more processors in a computer or other data processing device. The computer-executable instructions may be stored as computer-readable instructions on a computer-readable medium such as a hard disk, optical disk, removable storage media, solid-state memory, RAM, and the like. The functionality of the program modules may be combined or distributed as desired in various embodiments. In addition, the functionality may be embodied in whole or in part in firmware or hardware equivalents, such as integrated circuits, application-specific integrated circuits (ASICs), field programmable gate arrays (FPGA), and the like. Particular data structures may be used to more effectively implement one or more aspects of the disclosure, and such data structures are contemplated to be within the scope of computer executable instructions and computer-usable data described herein.
Various aspects described herein may be embodied as a method, an apparatus, or as one or more computer-readable media storing computer-executable instructions. Accordingly, those aspects may take the form of an entirely hardware embodiment, an entirely software embodiment, an entirely firmware embodiment, or an embodiment combining software, hardware, and firmware aspects in any combination. In addition, various signals representing data or events as described herein may be transferred between a source and a destination in the form of light or electromagnetic waves traveling through signal-conducting media such as metal wires, optical fibers, or wireless transmission media (e.g., air or space). In general, the one or more computer-readable media may be and/or include one or more non-transitory computer-readable media.
As described herein, the various methods and acts may be operative across one or more computing servers and one or more networks. The functionality may be distributed in any manner, or may be located in a single computing device (e.g., a server, a client computer, and the like). For example, in alternative embodiments, one or more of the computing platforms discussed above may be combined into a single computing platform, and the various functions of each computing platform may be performed by the single computing platform. In such arrangements, any and/or all of the above-discussed communications between computing platforms may correspond to data being accessed, moved, modified, updated, and/or otherwise used by the single computing platform. Additionally or alternatively, one or more of the computing platforms discussed above may be implemented in one or more virtual machines that are provided by one or more physical computing devices. In such arrangements, the various functions of each computing platform may be performed by the one or more virtual machines, and any and/or all of the above-discussed communications between computing platforms may correspond to data being accessed, moved, modified, updated, and/or otherwise used by the one or more virtual machines.
Aspects of the disclosure have been described in terms of illustrative embodiments thereof. Numerous other embodiments, modifications, and variations within the scope and spirit of the appended claims will occur to persons of ordinary skill in the art from a review of this disclosure. For example, one or more of the steps depicted in the illustrative figures may be performed in other than the recited order, and one or more depicted steps may be optional in accordance with aspects of the disclosure.
