Multitenant sharing anomaly cyberattack campaign detection
US-11888870-B2 · Jan 30, 2024 · US
US12174937B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-12174937-B2 |
| Application number | US-202217670105-A |
| Country | US |
| Kind code | B2 |
| Filing date | Feb 11, 2022 |
| Priority date | Feb 11, 2022 |
| Publication date | Dec 24, 2024 |
| Grant date | Dec 24, 2024 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
Methods, systems, apparatuses, and computer-readable storage mediums described herein are configured to detect anomalous post-authentication behavior with respect to a user identity. For example, one or more audit logs that specify a plurality of actions performed with respect to the user identity of a platform-based identity service, while the user identity is authenticated with the platform-based identity service, are analyzed. The audit log(s) are analyzed via an anomaly prediction model that generates an anomaly score indicating a probability whether a particular sequence of actions of the plurality of actions is indicative of anomalous behavior. A determination is made that an anomalous behavior has occurred based on the anomaly score. In response to determining that anomalous behavior has occurred, a mitigation action may be performed that mitigates the anomalous behavior.
Opening claim text (preview).
What is claimed is: 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: a user identity protection engine configured to: receive a log specifying a sequence of actions performed with respect to a user identity of a platform-based identity service, the sequence of actions occurring while the user identity is authenticated with the platform-based identity service; generate an anomaly score indicating a probability whether the sequence of actions is indicative of anomalous behavior via an anomaly prediction model; receive an authentication risk score indicating a probability whether user credentials utilized to authenticate the user identity with the platform-based identity service were compromised at the time of authentication; combine the authentication risk score and the anomaly score to generate a combined score; determine that an anomalous behavior has occurred based at least on the combined score; and based on a determination that the anomalous behavior has occurred, cause a mitigation action to be performed that mitigates the anomalous behavior. 2. The computing system of claim 1 , wherein the user identity protection engine is further configured to: determine that the anomalous behavior has occurred based on the combined score meeting a predetermined condition. 3. The computing system of claim 1 , wherein the user identity protection engine is further configured to: for each action in the sequence of actions, determine a respective probability that the action occurs after one or more other actions from the sequence of actions; and aggregate the respective probabilities determined for the sequence of actions into an aggregated probability, the anomaly score being based on the aggregated probability. 4. The computing system of claim 1 , wherein the anomaly prediction model comprises a machine learning model, wherein the machine learning model comprises at least one of: an unsupervised machine learning-based model; or a neural network-based machine learning-based model. 5. The computing system of claim 4 , wherein the machine learning model is trained by: determining a plurality of features associated with logs specifying a plurality of actions performed with respect to a plurality of user identities of the platform-based identity service; and providing the plurality of features as training data to a machine learning algorithm, wherein the machine learning algorithm is configured to determine, for each sequence of actions from the plurality of actions, a probability that a first action from the sequence of actions occurs after a second action from the sequence of actions. 6. The computing system of claim 5 , wherein the plurality of features comprises at least one of: a respective identifier for each of the plurality of actions; a respective time stamp indicating a time at which a respective action of the plurality of actions occurred; or a respective network address from which a respective action from the plurality of actions was initiated. 7. The computing system of claim 1 , wherein the user identity protection engine is further configured to perform at least one of: provide a notification that indicates that the anomalous behavior was detected; cause the user identity to be removed from the platform-based identity service; or cause access to a resource that was previously-accessible by the user identity to be restricted for the user identity. 8. A method performed by a computing system, comprising: receiving a log specifying a sequence of actions performed with respect to a user identity of a platform-based identity service, the sequence of actions occurring while the user identity is authenticated with the platform-based identity service; generating an anomaly score indicating a probability whether the sequence of actions is indicative of anomalous behavior via an anomaly prediction model; receiving an authentication risk score indicating a probability whether user credentials utilized to authenticate the user identity with the platform-based identity service were compromised at the time of authentication; combining the authentication risk score and the anomaly score to generate a combined score; determining that an anomalous behavior has occurred based at least on the combined score; and based on determining that the anomalous behavior has occurred, causing a mitigation action to be performed that mitigates the anomalous behavior. 9. The method of claim 8 , further comprising: determining that the anomalous behavior has occurred based on the combined score meeting a predetermined condition. 10. The method of claim 8 , wherein generating the anomaly score comprises: for each action in the sequence of actions, determining a respective probability that the action occurs after one or more other actions from the sequence of actions; and aggregating the respective probabilities determined for the sequence of actions into an aggregated probability, the anomaly score being based on the aggregated probability. 11. The method of claim 8 , wherein the anomaly prediction model comprises a machine learning model, wherein the machine learning model comprises at least one of: an unsupervised machine learning-based model; or a neural network-based machine learning-based model. 12. The method of claim 11 , wherein the machine learning model is trained by: determining a plurality of features associated with logs specifying a plurality of actions performed with respect to a plurality of user identities of the platform-based identity service; and providing the plurality of features as training data to a machine learning algorithm, wherein the machine learning algorithm is configured to determine, for each sequence of actions from the plurality of actions, a probability that a first action from the sequence of actions occurs after a second action from the sequence of actions. 13. The method of claim 12 , wherein the plurality of features comprises at least one of: a respective identifier for each of the plurality of actions; a respective time stamp indicating a time at which a respective action of the plurality of actions occurred; or a respective network address from which a respective action from the plurality of actions was initiated. 14. The method of claim 8 , wherein 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 the user identity to be removed from the platform-based identity service; or causing access to a resource that was previously-accessible by the user identity to be restricted for the user identity. 15. 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 a sequence of actions performed with respect to a user identity of a platform-based identity service, the sequence of actions occurring while the user identity is authenticated with the platform-based identity service; generating an anomaly score indicating a probability whether the sequence of actions is indicative of anomalous behavior via an anomaly prediction model; receiving an authentication risk score indicating a probability whether user credentials utilized to authenticate the user identity with the platform-based ident
involving event detection and direct action · CPC title
Architecture, e.g. interconnection topology · CPC title
Push-based network services · CPC title
Grouping or aggregating service requests, e.g. for unified processing · CPC title
Learning methods · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.