# US 2019/0319945 A1 · Dynamic multi-factor authentication

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2019/0319945 A1
- Document ID: US20190319945A1
- Status: Published application
- Kind: A1
- Application number: 16/383,421
- Filed: 2019-04-12
- Published: 2019-10-17
- Earliest claimed: 2018-04-13
- Assignees: Sophos Limited
- Applicants: Sophos Limited
- Inventors: Joseph H. Levy; Andrew J. Thomas; Daniel Salvatore Schiappa; Kenneth D. Ray
- Web page: https://patentgrep.com/patent/US20190319945A1

## CPC

- G06F 21/45: Structures or tools for the administration of authentication
- G06F 21/6218: {to a system of files or objects, e.g. local or distributed file system or database}
- G06F 16/122: {using management policies (point-in-time backing up or restoration of persistent data G06F11/1446; file migration policies for HSM systems G06F16/185)}
- G06F 16/137: {Hash-based (content-based indexing of textual data G06F16/31)}
- G06F 16/285: {Clustering or classification}
- G06F 16/93: Document management systems
- G06F 21/577: {Assessing vulnerabilities and evaluating computer system security}
- G06F 21/64: Protecting data integrity, e.g. using checksums, certificates or signatures
- G06N 3/0675: {using electro-optical, acousto-optical or opto-electronic means}
- G06N 5/046: Forward inferencing; Production systems
- G06N 5/048: Fuzzy inferencing
- G06N 20/00: Machine learning
- H04L 9/0891: {Revocation or update of secret information, e.g. encryption key update or rekeying}
- H04L 9/16: the keys or algorithms being changed during operation
- H04L 9/3213: {using tickets or tokens, e.g. Kerberos (network architectures or network communication protocols for entities authentication using tickets in a packet data network H04L63/0807)}
- H04L 9/3226: {using a predetermined code, e.g. password, passphrase or PIN (network architectures or network communication protocols for supporting authentication of entities using passwords in a packet data network H04L63/083)}
- H04L 9/3265: {using certificate chains, trees or paths; Hierarchical trust model}
- H04L 9/3271: {using challenge-response}
- H04L 9/50: {using hash chains, e.g. blockchains or hash trees}
- H04L 41/20: {Network management software packages}
- H04L 41/22: comprising specially adapted graphical user interfaces [GUI]
- H04L 63/08: {for authentication of entities (cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32)}
- H04L 63/0807: {using tickets, e.g. Kerberos (cryptographic mechanisms or cryptographic arrangements for entity authentication using tickets or tokens H04L9/3213)}
- H04L 63/083: {using passwords (cryptographic mechanisms or cryptographic arrangements for entity authentication using a predetermined code H04L9/3226)}
- H04L 63/0838: {using one-time-passwords}
- H04L 63/0861: {using biometrical features, e.g. fingerprint, retina-scan (cryptographic mechanisms or cryptographic arrangements for entity authentication using biological data H04L9/3231)}
- H04L 63/101: {Access control lists [ACL]}
- H04L 63/102: {Entity profiles}
- H04L 63/1408: {by monitoring network traffic (monitoring network traffic per se H04L43/00)}
- H04L 63/1416: {Event detection, e.g. attack signature detection}
- H04L 63/1425: {Traffic logging, e.g. anomaly detection}
- H04L 63/1433: {Vulnerability analysis}
- H04L 63/1441: {Countermeasures against malicious traffic (countermeasures against attacks on cryptographic mechanisms H04L9/002)}
- H04L 63/20: {for managing network security; network security policies in general (filtering policies H04L63/0227)}
- H04L 63/205: {involving negotiation or determination of the one or more network security mechanisms to be used, e.g. by negotiation between the client and the server or between peers or by selection according to the capabilities of the entities involved (negotiation of communication capabilities H04L69/24)}
- G06F 2221/034: Test or assess a computer or a system
- H04L 9/3228: {One-time or temporary data, i.e. information which is sent for every authentication or authorization, e.g. one-time-password, one-time-token or one-time-key}
- H04L 9/3231: {Biological data, e.g. fingerprint, voice or retina (network architectures or network communication protocols for supporting authentication of entities using biometrical features in a packet data network H04L63/0861)}
- H04L 2463/082: applying multi-factor authentication
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- G06N: COMPUTING ARRANGEMENTS BASED ON SPECIFIC COMPUTATIONAL MODELS
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

An authentication model dynamically adjusts authentication factors required for access to a remote resource based on changes to a risk score for a user, a device, or some combination of these. For example, the authentication model may conditionally specify the number and type of authentication factors required by a user/device pair, and may dynamically alter authentication requirements based on changes to a current risk assessment for the user/device while the remote resource is in use.

## Claims

### Claim 1

A computer program product comprising computer executable code embodied in a non-transitory computer readable medium that, when executing on one or more computing devices, performs the steps of:
receiving a request for a remote resource from a compute instance in an enterprise network, the remote resource requiring authentication;
calculating a first risk score for a user of the compute instance based on global information for the user from a threat management facility for the enterprise network and a second risk score for a device associated with the compute instance based on a risk assessment for the compute instance by a local security agent executing on the device;
selecting an authentication model from a number of authentication models for access to the remote resource by the user and the device, the authentication model specifying one or more requirements for authentication to the remote resource, wherein all of the authentication models include a user name and a password, and at least one of the authentication models including at least one other authentication factor; and
authenticating the user to the remote resource according to the authentication model.

### Claim 2 (depends on 1)

The computer program product of claim 1 wherein the at least one other authentication factor includes one or more of a biometric identifier, a security token, and a challenge-response test.

### Claim 3 (depends on 1)

The computer program product of claim 1 wherein the at least one other authentication factor includes a captcha challenge-response test.

### Claim 4 (depends on 1)

The computer program product of claim 1 wherein the at least one other authentication factor includes a one-time-use passcode.

### Claim 5 (depends on 1)

The computer program product of claim 1 further comprising code that performs the steps of, after authentication according to the authentication model:
updating the first risk score and the second risk score; and
when at least one of the first risk score and the second risk score exceeds a threshold, deauthenticating the user and selecting a new authentication model for the user and the device.

### Claim 6 (depends on 5)

The computer program product of claim 5 wherein the threshold is algorithmically determined.

### Claim 7 (depends on 1)

The computer program product of claim 1 wherein the remote resource includes a domain controller for the enterprise network.

### Claim 8 (depends on 1)

The computer program product of claim 1 wherein the remote resource includes a cloud resource outside the enterprise network.

### Claim 9 (depends on 1)

The computer program product of claim 1 wherein the remote resource includes an identity and access management system.

### Claim 10 (depends on 1)

The computer program product of claim 1 wherein the authentication model is applied by the threat management facility for the enterprise network.

### Claim 11 (depends on 1)

The computer program product of claim 1 wherein the authentication model is applied by the remote resource.

### Claim 12

A method comprising:
receiving a request for a remote resource from a compute instance in an enterprise network, the remote resource requiring authentication;
calculating a first risk score for a user of the compute instance and a second risk score for a device associated with the compute instance;
selecting an authentication model for access to the remote resource by the user and the device based on the first risk score and the second risk score, the authentication model specifying one or more requirements for authentication to the remote resource; and
authenticating the user to the remote resource according to the authentication model.

### Claim 13 (depends on 12)

The method of claim 12 wherein at least one factor in the authentication model includes a user name and password.

### Claim 14 (depends on 12)

The method of claim 12 wherein at least one factor in the authentication model includes a biometric authentication factor.

### Claim 15 (depends on 12)

The method of claim 12 wherein at least one factor in the authentication model includes a challenge-response test, a captcha test, a security question, or a code from a security token.

### Claim 16 (depends on 12)

The method of claim 12 further comprising, after authentication according to the authentication model:
updating the first risk score and the second risk score; and
when at least one of the first risk score and the second risk score exceeds a threshold, deauthenticating the user and selecting a new authentication model for the user and the device.

### Claim 17 (depends on 12)

The method of claim 12 wherein the remote resource includes a domain controller for the enterprise network, a cloud resource outside the enterprise network, or an identity and access management system.

### Claim 18 (depends on 12)

The method of claim 12 wherein the authentication model is applied at least in part by a threat management facility for the enterprise network.

### Claim 19 (depends on 12)

The method of claim 12 wherein the authentication model is applied at least in part by a third party authentication platform.

### Claim 20 (depends on 12)

The method of claim 12 wherein selecting the authentication model includes selecting an authentication model that uses an additional authentication factor to permit access when at least one of the first risk score and the second risk score is below a threshold and that withholds the additional authentication factor to prevent access when at least one of the first risk score and the second risk score is above a threshold.

### Claim 21

A system comprising:
a compute instance on an enterprise network;
a remote resource accessible to the compute instance;
a memory storing a plurality of authentication models, each of the plurality of authentication models specifying a number of authentication models each containing authentication factors for use when a user accesses the remote resource from the compute instance; and
a threat management facility configured to assess a risk of the compute instance and the user, to select one of the plurality of authentication models from the memory for use in authenticating the user of the compute instance to the remote resource based on the risk, and to control authentication of the user to the remote resources with the compute instance based on the one of the plurality of authentication models.
