Patent Application
20160078203
Efforts to secure computing resources often focus on preventing unauthorized users from obtaining access to the computing resources of a computing system. Recent events have shown, however, that users authorized to access computing resources may abuse such authorization to the detriment of personal, financial, and national interests.
Current approaches to computer security might not be equipped to detect when a user that is authorized to access a computing resource abuses that authorization. Therefore there is a need for improved approaches to computer security that can detect, notify, and prevent potential abuses of authorized access to computing resources.
The following presents a simplified summary of the present disclosure in order to provide a basic understanding of some aspects of the disclosure. This summary is not an extensive overview of the disclosure. It is not intended to identify key or critical elements of the disclosure or to delineate the scope of the disclosure. The following summary merely presents some concepts of the disclosure in a simplified form as a prelude to the more detailed description provided below.
A first aspect described herein provides a computer-implemented method of monitoring access of computing resources. A set of login credentials may be received from a user, and that user may be authorized to access a computing resource based on those login credentials. Actions the user requests to be performed at the computing resource may be monitored, and it may be determined whether or not those actions violate a usage constraint. If one of the actions does violate a usage constraint, performance of the action may be halted until another user authorizes the action.
A second aspect described herein provides a system for monitoring access of computing resources. A memory may store usage rules that each define a usage constraint. An authenticator may be configured to authenticate a user and authorizes that user to access a computing resources based on a set of login credentials received from the user. A usage monitor may be configured to apply one or more of the usage rules to the actions the user requests to be performed at the computing resource. The usage monitor may also be configured to determine that one of the actions violates the usage constraint of one of the usage rules and halt performance of that action until another user authorizes the action.
A third aspect described herein provides another computer-implemented method of monitoring access of computing resources. Usage rules may be stored at a memory. Each usage rule may define a usage constraint based on one or more of the actions available to be performed at the computing resources. An authenticator may receive a set of login credentials from a user. The authenticator may verify the login credentials and authorize the user to access one of the computing resources based on the verified login credentials. A request to perform an action at the computing resource may also be received from the user. A usage monitor may apply one or more of the usage rules to the requested action and determine that the requested action violates the usage constraint of one of the usage rules. The usage monitor may, in turn, halt performed of the requested action and notify another user that the requested action violates the usage constraint of one of the usage rules. The notification may identify the user that requested performance of the action, that action requested to be performed, the usage constraint violated by the action, and the usage rule that defines the usage constraint violated. The authenticator may receive and verify another set of login credentials from that other user. In response to successful verification of the additional set of login credentials, the usage monitor may resume performance of the requested action.
The details of these and other embodiments of the disclosure are set forth in the accompanying drawings and description below. Other features and advantages of aspects of the disclosure will be apparent from the description, drawings, and claims.
Aspects of the disclosure may be implemented in certain parts, steps, and embodiments that will be described in detail in the following description and illustrated in the accompanying drawings in which like reference numerals indicate similar elements. It will be appreciated with the benefit of this disclosure that the steps illustrated in the accompanying figures may be performed in other than the recited order and that one or more of the steps disclosed may be optional. It will also be appreciated with the benefit of this disclosure that one or more components illustrated in the accompanying figures may be positioned in other than the disclosed arrangement and that one or more of the components illustrated may be optional.
In accordance with various aspects of the disclosure, systems and methods are disclosed for monitoring access of computing resources of a computing system. After a user is authorized to access a computing resource, the actions the user requests to be performed at that computing resource are continuously monitored to determine whether such actions violate a usage constraint defined for the computing resource. If the requested action violates the usage constraint, then the requested action is halted, and a supervisor is notified of the usage constraint violation. The supervisor may be, for example, a computer system administrator or an employee supervisor. The supervisor may then review the usage violation and determine whether to permit performance of the requested action. If the supervisor authorizes performance of the requested action, then the action may resume and be performed at the computing resource.
The usage constraints thus allow an enterprise to define thresholds for what is considered to be typical use of the computing resources of its computing systems. By halting actions and notifying supervisors of usage constraint violations, that enterprise may advantageously ensure that users do not abuse their authorization to access those computing resources. Furthermore since the activity may resume upon authorization from a supervisor, the user experience is not significantly impacted. Access to the computing resource is only halted when use of that resource violates a usage constraint. If use of a computing resource remains within the boundaries of the usage constraint, access to that computing resource will be maintained. The supplemental authorization process thus advantageously serves as a check on the authorized use of a computing resource by allowing another individual to assess whether a user should be permitted to perform an action that exceeds typical use of a computing resource. In this way potential abuses of authorized access to computing resources may be advantageously detected and avoided. Additional benefits will be appreciated upon review of the additional disclosures set forth in further detail below.
As used in this disclosure, a computing resource refers to the hardware, software, and data elements of a computing system. Computing resources, as used in this description, include both physical and virtual resources. Physical resources include hardware such as, for example, mainframes, servers, routers, switches, disk arrays, workstations, desktop computing devices, laptop computing devices, tablet computing devices, palmtop computing devices, printers, scanners, communication devices, and the like. Virtual computing resources include software and data elements such as, for example, services, native and virtualized software applications, computer files, databases, and the like. Computing resources may also include interactive voice response (IVR) telephone systems as well as telephone systems where menu items may be selected using dual-tone multi-frequency (DTMF) signaling.
Furthermore “continuous” access monitoring, as used in this description, refers to comparing at least some of the actions a user requests to be performed at a computing resource during a user session to one or more of the usage rules defined for a computing system. While some example implementations may compare each action a user requests to be performed to the usage rules, other implementations that compare some, but not all, of the actions a user requests to be performed still fall within the scope of continuous access monitoring of a computing resource.
It is also to be understood that the phraseology and terminology used herein are for the purpose of description and should not be regarded as limiting. Rather, the phrases and terms used herein are to be given their broadest interpretation and meaning. The use of “including” and “comprising” and variations thereof is meant to encompass the items listed thereafter and equivalents thereof as well as additional items and equivalents thereof. The use of the terms “mounted,” “connected,” “coupled,” “positioned,” “engaged” and similar terms, is meant to include both direct and indirect mounting, connecting, coupling, positioning and engaging. In addition, “set” as used in this description refers to a collection that may include one element or more than one element.
Moreover, aspects of the disclosure may be implemented in non-transitory computer-readable media having instructions stored thereon that, when executed by a processor, cause the processor to perform various steps described in further detail below. As used in this description, non-transitory computer-readable media refers to all computer-readable media with the sole exception being a transitory propagating signal. The instructions may be organized into one or more program modules that may be executed by one or more computers or other devices as described herein. Program modules may include routines, programs, objects, components, data structures, and the like that perform particular tasks or implement particular data types when executed by a processor in a computer or other device. The modules may be written in a source code programming language that is subsequently compiled for execution, or may be written in a scripting language that supports scripts interpreted in a run-time environment. The instructions may be stored on a computer-readable medium as described in further detail below. Accordingly aspects of the disclosure may be embodied as a method, data processing system, or computer program product. Functionality described below may therefore be embodied at least in part in software, firmware, or hardware such as integrated circuits, field programmable gate arrays (FPGA), and the like. Furthermore data structures that implement aspects of the disclosure are considered to be within the scope of the computer-readable instructions.
The disclosure is operational within a special purpose computing systems and environments configured to authenticate and authorize users to access computing resources as well as continuously monitor such access to those computing resources. These special purpose computing systems and environments may include personal computers (PCs), server computers, hand-held or laptop devices, multiprocessor systems, microprocessor-based systems, programmable consumer electronics, network PCs, minicomputers, mainframe computers, distributed computing environments that include any of the systems or devices listed above, and the like. These special purpose computing systems may be configured to perform, execute, or otherwise carryout aspects of the disclosure described in further detail below.
With reference to
The continuous access monitoring server 101 may include a variety of computer-readable media. The computer-readable media may be any available non-transitory media that may be accessed by the continuous access monitoring server 101 and may include both volatile and non-volatile media as well as removable and non-removable media.
Computer storage media include volatile and non-volatile, removable and non-removable media implemented in any method or technology for storage of information such as computer-readable instructions, data structures, program modules, or other data. Computer storage media include, but are not limited to, random access memory (RAM), read-only memory (ROM), electronically erasable programmable read only memory (EEPROM), flash memory or other memory technology, CD-ROM discs, digital versatile discs (DVD), or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other non-transitory medium that can be used to store the desired information that can be accessed by the continuous access monitoring server 101.
The computing system environment 100 may also include optical scanners (not shown). Example uses of the optical scanners include scanning and converting paper documents, such as correspondence, data, and the like to digital files.
Although not shown, RAM 105 may include one or more applications representing the application data stored in RAM 105 while the continuous access monitoring server 101 is running and while corresponding software applications (e.g., software tasks) are executing on the continuous access monitoring server 101.
The communications module 109 may include a microphone, keypad, touch screen, stylus, or other types of input devices through which a user of the continuous access monitoring server 101 may provide input, and may also include one or more of a speaker for providing audio output and a video display device for providing textual, audiovisual, and/or graphical output.
Software may be stored within memory 115 and/or a storage device or storage media to provide instructions to the processor 103 that enable the continuous access monitoring server 101 to perform various functions. For example, memory 115 may store software used by the continuous access monitoring server 101, such as an operating system 117, application programs 119, and an associated database 121. In certain aspects, the continuous access monitoring server 101 may comprise a plurality of databases 121. Also, some or all of the computer executable instructions for the continuous access monitoring server 101 may be embodied in hardware or firmware.
The continuous access monitoring server 101 may operate in a networked environment supporting connections to one or more remote computing devices, such as computing devices 141 and 151. The computing devices 141 and 151 may be personal computing devices or servers that include many or all of the elements described above relative to the continuous access monitoring server 101.
The network connections depicted in
Additionally, one or more application programs 119 used by the continuous access monitoring server 101, according to an illustrative embodiment, may include computer-executable instructions for invoking functionality related to communication including, for example, email, short message service (SMS), and voice input and speech recognition applications. In addition, the application programs 119 may include computer-executable instructions for invoking user functionality related to access a centralized repository for performing various service tasks like routing, logging, data storage, and protocol bridging. Application programs 119 of the continuous access monitoring server 101 may also include authentication programs, authorization programs, usage monitoring programs, and other types of programs that will be appreciated with the benefit of this disclosure.
Embodiments of the disclosure may include forms of computer-readable media. Computer-readable media include any non-transitory media that can be accessed by the continuous access monitoring server 101. Storage media include volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information such as computer-readable instructions, object code, data structures, program modules, or other data.
Referring now to
According to one or more aspects, the continuous access monitoring system 200 may be associated with the computing system of an enterprise. In some instances, the enterprise may be, for example, a financial institution such as a bank. Although it will be appreciated that the enterprise may be one of many other types of entities that maintain enterprise-wide computing systems and monitoring access to their respective computing resources.
The computer network 203 may be any suitable computer network including the Internet, an intranet, a wide-area network (WAN), a local-area network (LAN), a wireless network, a digital subscriber line (DSL) network, a frame relay network, and asynchronous transfer mode network, a virtual private network (VPN), or any combination of any of the same. The communications links 202 and 205 may be any communications links suitable for communicating between the network devices 201 and the continuous access monitoring server 204, such as network links, dial-up links, wireless links, hard-wired links, and the like.
Having described examples of computing devices that may be used to implement various aspects of the disclosure and an operating environment in which various aspects of the disclosure may be implemented, various embodiments are discussed in greater detail below.
In
The session manager 306, in this example, is configured to create and maintain a user session 316 to facilitate access to the computing resource 314. The continuous access monitoring server 302, in this example, is in signal communication with the session manager 306 to facilitate monitoring user access of the computing resource 314. Upon receipt of a request to access a computing resource 314, the session manager 306 may create a new user session 316 for the user 312 that submitted the request. The request may include or be followed by receipt of login credentials associated with the user 312. If the login credentials are successfully verified (i.e., authenticated), then the user 312 may be granted access to the computing resource 314 (i.e., authorized to access the computing resource). During the user session 316, the session manager 306 may also receive requests to perform an action at the computing resource 314 and facilitate performance of the requested action. The session manager 306 may also facilitate logging or otherwise keeping track of the actions requested to be performed at the computing resource 314 including, for example, the type of action requested, the date and time the action was requested, and the target computing resource.
Some examples of the various types of actions that may be requested and performed include: invoking a function of a service such as a web service; invoking a remote procedure call; requesting and receiving a web page; uploading and downloading computer files; creating, deleting, and modifying computer files; creating, deleting, and modifying database records; and the like. In financial contexts, a financial institution (e.g., a bank) may maintain a computing system that provides access to customer financial accounts via a web server and mobile server. The web server and mobile server may be configured to respectively provide web-based and mobile-based interfaces for managing the customer financial accounts. Actions customers may request, in this example, may include viewing account balances, creating bill payees, transferring money between accounts, and the like. Users may request additional and alternative types of actions in additional and alternative contexts.
As seen in
The authenticator 318 of the continuous access monitoring server 302 may be in signal communication with the session manager 306 and facilitate authentication of the user 312. As noted above, the user 312 may submit, via an application at the computing device 308, a request to access a computing resource 314 of the computing system 304 which may include a set of login credentials (e.g., username and password). The application at the computing device 308 may be, for example, a web browser, a desktop application, a mobile application, and the like. The session manager 306 may receive the access request and forward the login credentials to the authenticator 318 for verification (e.g., in an authentication request). As described in further detail below, the authenticator 318, in this example, may be configured to determine if the login credentials received are sufficient to authenticate the user 312. If the login credentials are sufficient to authenticate the user, then the authenticator 318 may determine whether the login credentials are valid and inform the session manager 306 (e.g., in an authentication response). If the authenticator 318 verifies the login credentials received, the session manager 306 may permit the user 312 to access the target computing resource 314. If the authenticator 318 cannot verify the login credentials received, then the session manager 306 may deny the user 312 access to the target computing resource 314. Computer system administrators or security administrators may determine what sets of identity elements are sufficient to authenticate a user in various circumstances according to the level of security desired for a computing system or an individual computing resource.
In addition, if the authenticator 318 determines that the login credentials received are not sufficient to authenticate the user 312, then the session manager 306 may inform the application at the computing device 308 that additional authentication must be performed before the user 312 is permitted to perform the requested action. The application may be configured to obtain additional authentication procedures in response to receipt of a notification indicating that additional authentication is needed, e.g., by initiating two-factor authentication using a one-time password (OTP). The authenticator 318, in this example, determines whether the login credentials received are sufficient to authenticate the user 312 based on the authentication rules 330 stored at the authentication rule data store 324.
Security administrators of the enterprise that maintains the computing system 304 may create and configure the authentication rules 330. The authentication rules 330 may include various attributes such as a user type 334, an action type 336, a risk level 338 for the action type, and a set of required identity elements 340 for the action type. Security administrators may perform a risk analysis of the actions available to be performed at the computing resources 314 of the computing system 304 and assign a corresponding risk level to each action. The risk level may depend on one or more of the type of action and the type of user requesting the action. Some actions, for example, may be relatively more or less risky depending on the type of user requesting performance of that action (e.g., internal users vs. external users). Some actions may additionally or alternatively be relatively more or less risky depending on the type of action. In the financial context, for example, simply viewing an account balance may be considered to be relatively less risky than performing a money transfer. Security administrators may thus configure the authentication rules to require more or fewer identity elements based on the risk level. For example, one authentication rule may require only a username and password for an action having a relatively lower risk level while another authentication rule may require a username, password, and OTP for an action having a relatively higher risk level. The set of required identity elements 340 may further depend on additional and alternative criteria including, e.g., a day of the week, a time of day, a geographic location of the user 312, a location of the computing device 308 and so forth. The authentication rule data store 324 may store the authentication rules 330 as, for example, individual records in a database. The user type 334, action type 336, risk level 338, and required identity elements 340 may thus correspond to tables or table columns of the database.
When the authenticator 318 receives a request to access a computing resource 314 or perform an action at the computing resource, the authenticator may retrieve the appropriate authentication rule 330 from the authentication rule data store 324. The access request received may include the user type of the user 312 (e.g., customer, employee), the requested action type (e.g., view account profile, create payee, transfer money, download file, delete file), and one or more identity elements. Having retrieved the appropriate authentication rule 330, the authenticator 318 may compare the required identity elements 340 defined by the authentication rule to the identity elements received in the access request. If the received identity elements include the required identity elements 340, then the authenticator 318 verifies the received identity elements.
To verify the received identity elements, the authenticator 318 compares them to the identity elements 332 stored at the identity element data store 326 for the user. As seen in
As also seen in
The usage constraint 350 of a usage rule 328 may be based on various metrics associated with the actions the user 312 requests to be performed. One usage rule, for example, may define a usage constraint that is based on a frequency with which a type of action is performed. Security administrators may determine, for example, that users typically invoke a service an average of five times an hour and thus determine that invocation of the service more than ten times an hour constitutes a potential abuse of that service. The security administrators may thus create a usage rule for that service and configure the usage constraint such that the usage rule is violated if a user invokes the service more than ten times an hour, i.e., exceeds a usage threshold of ten times per hour. Another example usage rule may define a usage constraint that is based on a total number of computer files requested to be retrieved. Security administrators may determine, for example, that users typically retrieve an average of 25 computer files from a particular computing resource 314 per day and thus determine that requesting more than 50 computer files per day from that computing resource constitutes a potential abuse of that computing resource. The security administrators may thus create a usage rule for that computing resource 314 and configure the usage constraint such that the usage rule is violated if a user requests retrieval of more than 50 computer files from the computing resource 314 within a 24 hour period. A similar a usage rule may be created with a usage constraint that is based on a total number of database queries the user requests to be performed within a predetermined time period.
Other examples of usage rules are provided below. An example usage rule may define a usage constraint that is based on a day of the week or time of day an action is requested to be performed. Security administrators may thus configure the usage constraint of a usage rule such that the usage rule is violated when a user requests an action to be performed outside of typical working hours (e.g., 9:00 AM-5:00 PM) or outside of the typical working hours observed for that user and saved, e.g., as user metadata 352 at the identity element data store. Similarly security administrators may configure the usage constraint of a usage rule such that the usage rule is violated when a user requests an action to be performed outside of typical workdays (e.g., Monday through Friday) or outside of the preferred days the user is observed to work which may also be stored as user metadata 352. An example usage rule may define a usage constraint that is based on a geographic location of the user. Security administrators may configure the usage constraint of the usage rule such that the usage rule is violated when a user requests access to the computing resource 314 from a new geographic location, i.e., a location the user has not yet been observed at before. The identity element data store 326 may store information identifying the geographic locations the user is observed at as user metadata 344. Similarly an example usage rule may define a usage constrain that is based on a location of the end-user computing device 308, e.g., internal or external to an intranet provided by the computing system 304. An example usage rule may define a usage constraint that is based on the computing device 308 the user utilizes to access the computing resource 314. Security administrators may configure the usage constraint of the usage rule such that the usage rule is violated when the user access the computing resource 314 from a new computing device, i.e., a computing device the user has not yet been observed as using. The identity element data store 326 may store information identifying the computing devices the user utilizes as user metadata 344.
In some example implementations, the usage rules 328 may include usage rules that define respective usage constraints that are based on the total number of supplemental authorizations performed by an individual. The usage rule may be configured such that the usage constraint is based on the total number of supplemental authorizations an individual performs overall or for a particular user. The usage constraint, in this example usage rule, may also be based on a percentage of requested actions approved by the individual, again either overall or for a particular user. For example, computer security administrators may determine that approving a total of x usage constraint violations or y % of usage constraint violations for a particular user constitutes a potential abuse of such approval. Accordingly a usage rule may be created with a usage constraint that defines an approval threshold. If an administrator exceeds the approval threshold, then approval from another administrator (e.g., a super-administrator), may be required before approval of a usage constraint violation may be completed. In this way, the continuous access monitoring system may advantageously prevent a user from colluding with an individual that has the ability to approve usage constraint violations.
A usage rule 328 may be applicable to one or more of the computing resources 314 of the computing system 304. Accordingly a usage rule 328 may also include an attribute that indicates which computing resource 314 or computing resources the usage rule is applicable to. The usage rule 328 may identify a particular computing resource 314 (e.g., by a unique identifier or address) or a set of computing resources (e.g., by domain, type, location). Security administrators may, for example, create and configure a usage rule 328 that applies to each server of the computing system 304, each web server of the computing system, each database of the computing system, and so forth. Security administrators may also create a usage rule that applies to each computing resource associated with a particular business unit of an enterprise, located within a particular geographic boundary, addressed to a particular subnet of the computing system, and so forth. Security administrators may also individually select the computing resources 314 a usage rule 328 applies to. Additional and alternative examples will be appreciated with the benefit of this disclosure.
The notification of the access request received at the usage monitor 320 from the session manager 306 may thus include information used to compare the access request to the usage rules 328. The notification may, for example, identify the user, the type of user, the location of the user, the type of end-user computing device, the type of action requested to be performed, and so forth. As noted above, the usage monitor 320 may determine whether an access request violates a usage rule 328 by comparing the access request to previous actions performed for the user. The notification received at the usage monitor 320 from the session manager 306 may thus also include information describing those previous actions, e.g., the total number of times a type of action has previously been performed for the user.
As noted above, supplemental authorization from another individual may be required when a requested action violates the usage constraint of one of the usage rules. In response to violation of a usage constraint 350, the usage monitor 320 may instruct the session manager 306 to halt the action the user 312 has requested to be performed at the computing resource 314. The usage monitor 320 may also notify another individual (e.g., a supervisor or administrator) that may authorize the action. The notification may, for example, identify for that individual the user that requested the action, various user metadata associated with the user, that action the user requested to be performed, the computing resource 314 accessed, the usage constraint 350 violated by the requested action, the usage rule 328 that defines the usage constraint violated, information describing previous actions performed for the user, and so forth. The individual may review the violation notification and determine whether the user should be permitted to have the requested action performed at the computing resource 314. The individual may authorize the requested action by, for example, logging into the continuous access monitoring server 302 with assigned login credentials (e.g., username and password). Upon verification of the access credentials received, the usage monitor 320 may instruct the session manager 306 to resume performance of the action requested by the user 312.
The usage rules 328 may be modified as needed to adjust the usage constraint or other information associated with a usage rule. In this way, the continuous access monitoring server may be adaptable to changes in the usage patterns observed by an enterprise. For example, if an enterprise determines that a relatively large volume of requested actions are being halted for supplemental authorization, the usage constraints of the usage rules may be adjusted such that fewer requested actions result in usage constraint violations. The enterprise may likewise adjust the usage constraints if the enterprise determines that a relatively small volume of requested actions are being halted for supplemental authorization. In some example implementations, the continuous access monitoring system may automatically identify use patterns based on observed use of computing resources and dynamically adjust the usage constraints based on the use patterns observed.
As seen in
Referring now to
As also described above, the authenticator may determine whether additional authentication is required by applying an authentication rule 410 to the access request 404. As illustrated in
The set of identity elements 412 received in the access request 404 may include login credentials, user metadata, and device metadata as described above. The set of required identity elements 414 in the authentication rule 410 may likewise include a combination of login credentials, user metadata, and device metadata. As described above, the set of required identity elements 414 may be defined by security administrators and may be based on the type of action requested, the type of user making the request, the risk level associated with the action, and other types of criteria that will be appreciated with the benefit of this disclosure. As noted above, however, the set of required identity elements 414 is not shared with the computing device 406 to maintain the security of the computing system. Rather the access request 404 includes the set of identity elements 412 known to the computing device 406 (or application), and the authenticator determines whether those identity elements are sufficient to authenticate the user 402. The authenticator 408, however, does not inform the computing device (or application) which particular identity elements are required to authenticate the user 402, only that additional authentication is needed, i.e., additional identity elements. It is then the responsibility of the computing device 406 (or application) to obtain one or more additional identity elements such as, e.g., an OTP.
This aspect of the authentication process is illustrated by way of example in
In response to receipt of a notification that the received set of identity elements 412 is not sufficient to authenticate the user 402, a new access request may be submitted with one or more additional identity elements. As seen in
To further secure the authentication process, the identity elements required by an authentication rule may be dynamic. In particular the set of required identity elements may be randomized for each access request received. An authentication rule may define a pool of identity elements that may be used for authentication and a total number, x, of identity elements required for authentication. The authenticator may be configured to randomly select x number of required identity elements from the pool of identity elements defined for the authentication rule. The total number of identity elements required may also be randomized. The authentication rule may, for example, specify a range, x-y, of identity elements required for authentication, and the authenticator may be configured to randomly select a value between x and y as the number of identity elements to be selected as the set of required data elements. An authentication rule may also define multiple individual sets of identity elements which the authenticator 408 may select at random upon receipt of a request to access a computing resource. The randomized sets of identity elements and the randomly selected sets of identity elements may each represent a collection of identity elements sufficient to authenticate a user based on various criteria such as, e.g., action type, user type, risk level, and other types of criteria that will be appreciated with the benefit of this disclosure.
Referring now to
If the authenticator successfully authenticates the user (block 508:Y), however, then a session manager may create a new user session for the user (block 512) as also described above. A usage monitor may then initiate monitoring of the actions requested to be performed during that user session (block 514) that facilitates and manages access to the computing resource. As set forth above, the session manager may receive a request to perform an action at the computing resource (block 516), and the usage monitor may retrieve and apply one or more of the usage rules to the request (block 518). When applying a usage rule, the usage monitor determines whether the requested action violates the usage constraint of that usage rule (block 520). As noted above, the usage monitor may retrieve and analyze information describing actions previously performed by the user at the computing resource or at other computing resources when applying the usage rule. As one example, the usage monitor may retrieve and analyze information associated with a predetermined type of action (e.g., downloading a computer file or invoking a service) that has previously been performed in order to determine the frequency with which the user performs that type of action. Additional examples will be appreciated with the benefit of this disclosure.
If the usage monitor determines that the requested action does not violate the usage constraint of the applied usage rule (block 522:N), then the requested action may be performed at the computing resource and update the user session (block 524). As noted above, updating the user session may include logging or otherwise tracking the action performed such that it may be compared to subsequent actions the user requests to perform at the computing resource or other computing resources. Having performed the requested action, the usage monitor may wait for another request to perform an action is received from the user (block 516) and repeat these steps for that subsequent action. The usage monitor may, for example, transmit a response to the session manager that the requested action may be performed, and the session manager may facilitate performance of the action, e.g., by transmitting an instruction to the computing resource.
If, however, the usage monitor determines that the requested action violates a usage constraint (block 522:Y), then the usage monitor may instruct the session manager to halt performance of the requested action (block 526) as described above. The usage monitor may then notify another individual of the usage constraint violation (block 528), e.g., an administrator, in order to inform that individual that the usage constraint has been violated. Upon receipt of the usage constraint violation notification, that individual has the opportunity to review the action requested to be performed, the usage rule, and the usage constraint violated by the requested action. The individual may then determine whether the user should be permitted to or prevented from having the requested action performed at the computing resource. If the individual approves the requested action (block 530:Y), then the requested action may be performed at the computing resource and the user session may be updated (block 524) as described above. If, however, the individual does not authorize the requested action (block 530:N), then the requested action may not be performed at the computing resource (block 532). The usage monitor may, for example, transmit a response to the session manager that includes an instruction to deny, cancel, or otherwise discard the requested action. In some example implementations, the session manager may in turn transmit a response to the end-user computing device which may be presented to the user in order to inform the user that the requested action could not be performed. The response presented to the user may or may not include an explanation as to the reason the requested action could not be performed, e.g., that the action violates a usage constraint associated with the computing resource. Similarly the explanation may or may not identify the usage constraint and the usage rule applied depending on the level of security desired. In some example implementations, identification of the usage constraint and usage violation may depend on the user type of the user that submitted the request or other user-related criteria that will be appreciated with the benefit of this disclosure. If a requested action has been denied, the usage monitor may wait for another request to perform an action is received from the user (block 516) and repeat these steps for that subsequent action.
In some example implementations, the usage monitor may instruct the session manager to deny or otherwise cancel the request action if supplemental authorization is not received within a predetermined time period (e.g., 60 seconds). The usage monitor or the session manager may, for example, initiate a timer when the requested action is halted responsive to determining that the requested action violates a usage constraint. If the timer reaches zero before supplemental authorization is received, the session manager may automatically deny, cancel, or otherwise discard the requested action. In addition, the usage monitor may notify a security team when a usage constraint violation is not subsequently authorized. Upon receipt of the notification, the security team may initiate an investigation into the usage constraint violation. Furthermore the usage monitor may temporarily revoke the user's authorization to access to one or more computing resources when a usage constraint violation is not approved.
The approach to continuous access monitoring described above advantageously minimizes the intrusion of the usage monitor into the interactions between the user and the computing resource while ensuring that the user does not abuse the authorization to access that computing resource. It will be appreciated that the steps set forth above with reference to
Referring now to
A computing system may receive from an end-user computing device, a request to perform an action at a computing resource of the computing system (block 606). The computing system may also receive from the end-user computing device a set of identity elements with the request (block 608). An authenticator of the computing system may then retrieve one or more authentication rules associated with the requested action (block 610) and determine the identity elements required to authenticate the user defined in the authentication rule (block 612). As described above, the identity elements required to authenticate a user may be based on a risk level associated with the requested action, user metadata, device metadata, and the like. Security administrators may selectively configure the set of identity elements required to authenticate the user based on the level of security desired for the computing system.
Having retrieved the authentication rules associated with the requested action, the authenticator may determine whether the identity elements received are sufficient to authenticate the user based on the authentication rule (block 614). In particular, the authenticator may determine whether the set of received identity elements includes the required identity elements indicated in the authentication rule. If the received set of identity elements is not sufficient to authenticate the user (block 616:N), then a response may be transmitted to the end-user computing device indicating that additional authentication of the user is needed (block 618). As one example, the computing device or a corresponding application executing at the computing device may obtain one or more additional identity elements from the user, e.g., an OTP. Having obtained one or more additional identity elements, the end-user computing device may submit a new set of identity elements to the computing system for authentication of the user. The authenticator may thus repeat the steps described above to determine whether the new set of identity elements received are sufficient to authenticate the user based on the identity elements required by the authentication rule. As described above, the set of required identity elements sufficient to authenticate the user is a subset of the identity elements received from the user. The user, end-user computing device, and end-user application, however, do not know which particular combination of identity elements provided to the computing system with the access request are sufficient to authenticate the user.
If the authenticator determines that the set of received identity elements is sufficient to authenticate the user (block 616:Y), then the authenticator may retrieve a set of stored identity elements associated with the user that correspond to the required identity elements (block 620). The authenticator may then compare the set of stored identity elements to the set of required identity elements. If the values (or hash values) of the identity elements match (block 624:Y), then the authenticator may provide a response indicating that authentication of the user was successful (block 626). If one or more of the identity elements do not match, however, then the authenticator may provide a response indicating that authentication of the user has failed (block 628). The authenticator may, for example, provide the response to a session manager which may in turn create a user session for the user or facilitate performance of a requested action at a computing resource (e.g., if authentication was successful) or refrain from creating a user session or rejecting a request to perform an action (e.g., if authentication failed).
The approach to user authentication provided thus advantageously allows enterprise to configure their computing systems to require different degrees of authentication depending on the risk associated with the actions available to be performed at the computing resources. Furthermore by employing authentication rules, the set of identity elements required to authenticate a user may be modified if the desired level of security changes. It will be appreciated that the steps set forth above with reference to
The foregoing descriptions of the disclosure have been presented for purposes of illustration and description. They are not exhaustive and do not limit the disclosure to the precise form disclosed. Modifications and variations are possible in light of the above teachings or may be acquired from practicing of the disclosure. The described implementation includes software but may be implemented as a combination of hardware and software or in hardware alone. Additionally, although aspects of the present disclosure are described as being stored in memory, one skilled in the art will appreciate that these aspects can also be stored on other types of computer-readable media, such as secondary storage devices, like hard disks, floppy disks, CD-ROM discs, flash memory sticks, and so forth.
