# US 2019/0173903 A1 · User state tracking and anomaly detection in software-as-a-service environments

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

- Number: US 2019/0173903 A1
- Document ID: US20190173903A1
- Status: Published application
- Kind: A1
- Application number: 16/266,941
- Filed: 2019-02-04
- Published: 2019-06-06
- Earliest claimed: 2015-11-30
- Assignees: International Business Machines Corporation
- Applicants: International Business Machines Corporation
- Inventors: Ravi Krishnan Muthukrishnan; Jeffrey Robert Hoy; Sreekanth Ramakrishna Iyer; Kaushal Kiran Kapadia; Nataraj Nagaratnam
- Web page: https://patentgrep.com/patent/US20190173903A1

## CPC

- H04L 63/1425: {Traffic logging, e.g. anomaly detection}
- H04L 67/02: based on web technology, e.g. hypertext transfer protocol [HTTP]
- H04L 67/10: in which an application is distributed across nodes in the network (software deployment G06F8/60; multiprogramming arrangements G06F9/46)
- H04L 67/125: involving control of end-device applications over a network
- H04L 67/30: Profiles
- H04L 67/535: {Tracking the activity of the user (network monitoring arrangements H04L43/00; recording of computer activity G06F11/34)}
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

A user state tracking and anomaly detector for multi-tenant SaaS applications operates in association with a log management solution, such as a SIEM. A given SaaS application has many user STATES, and the applications often have dependencies on one another that arise, for example, when a particular application makes a request (typically on behalf of a user) to take some action with respect to another application. The detector includes a mapper that maps the large number of user STATES to a reduced number of mapped states (e.g., “red” and “green”), and a dependency module that generates user-resource dependency graphs. Using a dependency graph, a SaaS modeler in the detector checks whether a particular dependency-based request associated with a SaaS application is valid. State and dependency information generated by the mapper and dependency module are reported back to the log management solution to facilitate improved logging and anomaly detection.

## Claims

### Claim 1

A method for improving a log management system in a Software-As-A-Service (SaaS) environment having a plurality of cloud applications, the log management system normally configured to consolidate log source event data to detect anomalies, comprising:
obtaining, from each of a set of cloud applications, user state data with respect to one or more resources as users interact with the cloud application, wherein given cloud applications in the set have operating dependencies on one another based at least in part on a user state;
for a given cloud application in the set, mapping the user state data to a reduced set of states, the reduced set of states including at least a first state indicating an acceptable functioning state with respect to a user and resource at the given cloud application, and a second state indicating a malfunctioning state with respect to the user and resource at the given cloud application;
outputting the reduced set of states to the log management system to facilitate a logging operation.

### Claim 2 (depends on 1)

The method as described in claim 1 wherein user state data is collected for a single tenant enterprise in the SaaS environment.

### Claim 3 (depends on 1)

The method as described in claim 1 further including:
monitoring requests between or among the set of cloud applications; and
building a dependency graph based on dependency relationships between respective ones of the cloud applications, the dependency graph being a directed graph of nodes and edges, wherein a node in the directed graph represents a cloud application user and resource, and an edge in the directed graph represents a dependency link between resources, the dependency relationships discovered by monitoring the requests.

### Claim 4 (depends on 3)

The method as described in claim 3 further including assessing whether a dependency request is valid according to the dependency graph by executing a graph path traversal algorithm that identifies a subset of nodes reached from a dependency request starting point and determines whether a last node reached from the dependency request starting point is a given dependency.

### Claim 5 (depends on 4)

The method as described in claim 4 further including providing an indication that the dependency request has been determined to be valid.

### Claim 6 (depends on 1)

The method as described in claim 1 wherein the logging operation is provided by the log management system.

### Claim 7 (depends on 1)

The method as described in claim 1 wherein the user state data is obtained by receiving user state data provided by the given cloud application or by polling the given cloud application to provide such data.

### Claim 8

Apparatus, comprising:
a processor;
computer memory holding computer program instructions executed by the processor to improve a log management system in a Software-As-A-Service (SaaS) environment having a plurality of cloud applications, the log management system normally configured to consolidate log source event data to detect anomalies, the computer program instructions comprising program code configured to:
obtain, from each of a set of cloud applications, user state data with respect to one or more resources as users interact with the cloud application, wherein given cloud applications in the set have operating dependencies on one another based at least in part on a user state;
for a given cloud application in the set, map the user state data to a reduced set of states, the reduced set of states including at least a first state indicating an acceptable functioning state with respect to a user and resource at the given cloud application, and a second state indicating a malfunctioning state with respect to the user and resource at the given cloud application;
provide the reduced set of states to the log management system to facilitate a logging operation.

### Claim 9 (depends on 8)

The apparatus as described in claim 8 wherein user state data is collected for a single tenant enterprise in the SaaS environment.

### Claim 10 (depends on 8)

The apparatus as described in claim 8 wherein the program code is configured to:
monitor requests between or among the set of cloud applications; and
build a dependency graph based on dependency relationships between respective ones of the cloud applications, the dependency graph being a directed graph of nodes and edges, wherein a node in the directed graph represents a cloud application user and resource, and an edge in the directed graph represents a dependency link between resources, the dependency relationships discovered by monitoring the requests.

### Claim 11 (depends on 10)

The apparatus as described in claim 10 wherein the program code also assesses whether a dependency request is valid according to the dependency graph by executing a graph path traversal algorithm that identifies a subset of nodes reached from a dependency request starting point and determines whether a last node reached from the dependency request starting point is a given dependency.

### Claim 12 (depends on 11)

The apparatus as described in claim 11 wherein the program code provides an indication that the dependency request has been determined to be valid.

### Claim 13 (depends on 8)

The apparatus as described in claim 8 wherein the logging operation is provided by the log management system.

### Claim 14 (depends on 8)

The apparatus as described in claim 8 wherein the user state data is obtained by receiving user state data provided by the given cloud application or by polling the given cloud application to provide such data.

### Claim 15

A computer program product in a non-transitory computer readable medium for use in a data processing system, the computer program product holding computer program instructions executed by the data processing system to improve a log management system in a Software-As-A-Service (SaaS) environment having a plurality of cloud applications, the log management system normally configured to consolidate log source event data to detect anomalies, the computer program instructions comprising program code operative to:
obtain, from each of a set of cloud applications, user state data with respect to one or more resources as users interact with the cloud application, wherein given cloud applications in the set have operating dependencies on one another based at least in part on a user state;
for a given cloud application in the set, map the user state data to a reduced set of states, the reduced set of states including at least a first state indicating an acceptable functioning state with respect to a user and resource at the given cloud application, and a second state indicating a malfunctioning state with respect to the user and resource at the given cloud application;
provide the reduced set of states to the log management system to facilitate a logging operation.

### Claim 16 (depends on 15)

The computer program product as described in claim 15 wherein user state data is collected for a single tenant enterprise in the SaaS environment.

### Claim 17 (depends on 15)

The computer program product as described in claim 15 wherein the program code is configured to:
monitor requests between or among the set of cloud applications; and
build a dependency graph based on dependency relationships between respective ones of the cloud applications, the dependency graph being a directed graph of nodes and edges, wherein a node in the directed graph represents a cloud application user and resource, and an edge in the directed graph represents a dependency link between resources, the dependency relationships discovered by monitoring the requests.

### Claim 18 (depends on 17)

The computer program product as described in claim 17 wherein the program code also assesses whether a dependency request is valid according to the dependency graph by executing a graph path traversal algorithm that identifies a subset of nodes reached from a dependency request starting point and determines whether a last node reached from the dependency request starting point is a given dependency.

### Claim 19 (depends on 18)

The computer program product as described in claim 18 wherein the program code provides an indication that the dependency request has been determined to be valid.

### Claim 20 (depends on 15)

The computer program product as described in claim 15 wherein the logging operation is provided by the log management system.

### Claim 21 (depends on 15)

The computer program product as described in claim 15 wherein the user state data is obtained by receiving user state data provided by the given cloud application or by polling the given cloud application to provide such data.
