# US 2023/0267198 A1 · Anomalous behavior detection with respect to control plane operations

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

- Number: US 2023/0267198 A1
- Document ID: US20230267198A1
- Status: Published application
- Kind: A1
- Application number: 17/679,553
- Filed: 2022-02-24
- Published: 2023-08-24
- Earliest claimed: 2022-02-24
- Assignees: Microsoft Technology Licensing, LLC
- Applicants: Microsoft Technology Licensing, LLC
- Inventors: Andrey KARPOVSKY; Ram Haim PLISKIN; Evgeny BOGOKOVSKY
- Web page: https://patentgrep.com/patent/US20230267198A1

## CPC

- G06F 21/552: {involving long-term monitoring or reporting}
- G06F 21/554: {involving event detection and direct action}
- H04L 63/1425: {Traffic logging, e.g. anomaly detection}
- G06F 21/6218: {to a system of files or objects, e.g. local or distributed file system or database}
- G06F 2221/034: Test or assess a computer or a system
- H04L 2463/121: Timestamp
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

Methods, systems, apparatuses, and computer-readable storage mediums described herein are configured to detect anomalous behavior with respect to control plane operations (e.g., resource management operations, resource configuration operations, resource access enablement operations, etc.). For example, a log that specifies an access enablement operation performed with respect to an entity is received. An anomaly score is generated indicating a probability whether the access enablement operation is indicative of anomalous behavior via an anomaly prediction model. A determination is made as to whether anomalous behavior has occurred with respect to the entity based at least on the anomaly score. Based on a determination that the anomalous behavior has occurred, a mitigation action may be performed that mitigates the anomalous behavior.

## Claims

### Claim 1

A computing system, comprising:
at least one processor circuit; and
at least one memory that stores program code configured to be executed by the at least one processor circuit, the program code comprising:
an anomaly detection engine configured to:
receive a log specifying an access enablement operation performed with respect to an entity of a storage platform, the access enablement operation enabling access key-based resource access operations to be performed with respect to a resource of the storage platform;
generate an anomaly score indicating a probability whether the access enablement operation is indicative of anomalous behavior via an anomaly prediction model;
determine that anomalous behavior has occurred with respect to the entity based at least on the anomaly score; and
based on a determination that the anomalous behavior has occurred, cause a mitigation action to be performed that mitigates the anomalous behavior.

### Claim 2 (depends on 1)

The computing system of claim 1, wherein the log further specifies a plurality of characteristics of the access enablement operation, the plurality of characteristics comprising at least one of:
an identifier for the access enablement operation;
an identifier of the resource;
a time stamp indicating a time at which the access enablement operation was issued;
a network address from which the access enablement operation was issued;
an application identifier that identifies an application from which the access enablement operation was issued;
a user identifier associated with a user that issued the access enablement operation;
a type of the entity that issued the access enablement operation;
a type of authentication scheme utilized by the entity that issued the access enablement operation; or
an autonomous system number associated with the entity that issued the access enablement operation.

### Claim 3 (depends on 2)

The computing system of claim 2, wherein the anomaly detection engine is configured to generate the anomaly score by:
receiving a plurality of scores generated by the anomaly prediction model, including, for each of the plurality of characteristics, receiving a respective score of the plurality of scores indicating whether a corresponding characteristic of the plurality of characteristics is anomalous; and
generating the anomaly score based on a combination of the plurality of scores.

### Claim 4 (depends on 1)

The computing system of claim 1, wherein the anomaly detection engine is configured to determine that anomalous behavior has occurred by:
determining that the anomaly score meets a threshold condition; and
responsive to determining that the anomaly score meets the threshold condition, determining that the anomalous behavior has occurred with respect to the entity.

### Claim 5 (depends on 1)

The computing system of claim 1, wherein the access enablement operation comprises a request for an access key for accessing the resource of the storage platform.

### Claim 6 (depends on 1)

The computing system of claim 1, wherein the storage platform comprises at least one of:
a cloud-based distributed database; or
a cloud-based storage repository that stores unstructured data.

### Claim 7 (depends on 1)

The computing system of claim 1, wherein the entity comprises at least one of:
a user;
a role to which a plurality of users is assigned; or
a cloud-based subscription to which the storage platform is associated.

### Claim 8 (depends on 1)

The computing system of claim 1, wherein the anomaly detection engine is configured to cause the mitigation action to be performed by performing at least one of:
providing a notification that indicates that the anomalous behavior was detected;
causing an access key utilized to access the resource to be changed; or
causing access to the resource to be restricted for the entity.

### Claim 9

A method performed by a computing system, comprising:
receiving a log specifying an access enablement operation performed with respect to an entity, the access enablement operation enabling access key-based resource access operations to be performed with respect to a resource of a storage platform;
generating an anomaly score indicating a probability whether the access enablement operation is indicative of anomalous behavior via an anomaly prediction model;
determining that anomalous behavior has occurred with respect to the entity based at least on the anomaly score; and
based on a determination that the anomalous behavior has occurred, causing a mitigation action to be performed that mitigates the anomalous behavior.

### Claim 10 (depends on 9)

The method of claim 9, wherein the log further specifies a plurality of characteristics of the access enablement operation, the plurality of characteristics comprising at least one of:
an identifier for the access enablement operation;
an identifier of the resource;
a time stamp indicating a time at which the access enablement operation was issued;
a network address from which the access enablement operation was issued;
an application identifier that identifies an application from which the access enablement operation was issued;
a user identifier associated with a user that issued the access enablement operation;
a type of the entity that issued the access enablement operation;
a type of authentication scheme utilized by the entity that issued the access enablement operation; or
an autonomous system number associated with the entity that issued the access enablement operation.

### Claim 11 (depends on 10)

The method of claim 10, wherein said generating the anomaly score comprises:
receiving a plurality of scores generated by the anomaly prediction model, including, for each of the plurality of characteristics, receiving a respective score of the plurality of scores indicating whether a corresponding characteristic of the plurality of characteristics is anomalous; and
generating the anomaly score based on a combination of the plurality of scores.

### Claim 12 (depends on 9)

The method of claim 9, wherein said determining that anomalous behavior has occurred with respect to the entity based at least on the anomaly score comprises:
determining that the anomaly score meets a threshold condition; and
responsive to determining that the anomaly score meets the threshold condition, determining that the anomalous behavior has occurred with respect to the entity.

### Claim 13 (depends on 9)

The method of claim 9, wherein the access enablement operation comprises a request for an access key for accessing the resource of the storage platform.

### Claim 14 (depends on 9)

The method of claim 9, wherein the storage platform comprises at least one of:
a cloud-based distributed database; or
a cloud-based storage repository that stores unstructured data.

### Claim 15 (depends on 9)

The method of claim 9, wherein the entity comprises at least one of:
a user;
a role to which a plurality of users is assigned; or
a cloud-based subscription to which the storage platform is associated.

### Claim 16 (depends on 9)

The method of claim 9, wherein said causing the mitigation action to be performed that mitigates the anomalous behavior comprises at least one of:
providing a notification that indicates that the anomalous behavior was detected;
causing an access key utilized to access the resource to be changed; or
causing access to the resource to be restricted for the entity.

### Claim 17

A computer-readable storage medium having program instructions recorded thereon that, when executed by at least one processor of a computing system, perform a method, the method comprising:
receiving a log specifying an access enablement operation performed with respect to an entity, the access enablement operation enabling access key-based resource access operations to be performed with respect to a resource of a storage platform;
generating an anomaly score indicating a probability whether the access enablement operation is indicative of anomalous behavior via an anomaly prediction model;
determining that anomalous behavior has occurred with respect to the entity based at least on the anomaly score; and
based on a determination that the anomalous behavior has occurred, causing a mitigation action to be performed that mitigates the anomalous behavior.

### Claim 18 (depends on 17)

The computer-readable storage medium of claim 17, wherein the log further specifies a plurality of characteristics of the access enablement operation, the plurality of characteristics comprising at least one of:
an identifier for the access enablement operation;
an identifier of the resource;
a time stamp indicating a time at which the access enablement operation was issued;
a network address from which the access enablement operation was issued;
an application identifier that identifies an application from which the access enablement operation was issued;
a user identifier associated with a user that issued the access enablement operation;
a type of the entity that issued the access enablement operation;
a type of authentication scheme utilized by the entity that issued the access enablement operation; or
an autonomous system number associated with the entity that issued the access enablement operation.

### Claim 19 (depends on 18)

The computer-readable storage medium of claim 18, wherein said generating the anomaly score comprises:
receiving a plurality of scores generated by the anomaly prediction model, including, for each of the plurality of characteristics, receiving a respective score of the plurality of scores indicating whether a corresponding characteristic of the plurality of characteristics is anomalous; and
generating the anomaly score based on a combination of the plurality of scores.

### Claim 20 (depends on 17)

The computer-readable storage medium of claim 17, wherein said determining that anomalous behavior has occurred with respect to the entity based at least on the anomaly score comprises:
determining that the anomaly score meets a threshold condition; and
responsive to determining that the anomaly score meets the threshold condition, determining that the anomalous behavior has occurred with respect to the entity.
