System and user context in enterprise threat detection

US11252168B2 · US · B2

Patent metadata
FieldValue
Publication numberUS-11252168-B2
Application numberUS-201816125256-A
CountryUS
Kind codeB2
Filing dateSep 7, 2018
Priority dateDec 22, 2015
Publication dateFeb 15, 2022
Grant dateFeb 15, 2022

How to read this patent

A practical reading order for non-experts. Skip the full description unless you need deep technical detail.

  1. Title

    What the patent document calls the invention.

  2. Abstract

    A short plain-language summary of the technical disclosure.

  3. Assignees and inventors

    Who owns or filed the patent and who is credited as inventor.

  4. Key dates

    Filing, priority, publication, and grant dates set the timeline.

  5. First independent claim

    The legal scope of protection — read this for what is actually claimed.

  6. CPC / IPC classifications

    Technology tags used to group this patent with similar filings.

  7. Citations and related patents

    Prior art links and similar publications in this corpus.

Abstract

Official abstract text for this publication.

A transfer of master data is executed in a backend computing system. The master data includes user data and system data. The transfer of master data includes receiving user data associated with a particular user identifier in the backend computing system, transferring the received user data to an event stream processor, receiving system data associated with a particular log providing computing system in the backend computing system, transferring the received user data to the event stream processor, and executing a transfer of log data associated with logs of computing systems connected to the backend computing system.

First claim

Opening claim text (preview).

What is claimed is: 1. A computer-implemented method, comprising: executing, by a computer, a transfer of master data in a backend computing system, wherein the master data includes user data and system data, and wherein the transfer of master data comprises: receiving, by the computer and from a user management system or an identity management system, user data associated with a particular user id in the backend computing system; transferring, by the computer, the received user data to an event stream processor (ESP); receiving, by the computer, system data associated with a particular log providing computing system in the backend computing system; and after transferring the received user data to the ESP, transferring, by the computer, the received system data to the ESP; and after executing the transfer of master data, executing, by the computer, a transfer of log data associated with logs of computing systems connected to the backend computing system, wherein one or more log entries of the transferred log data are enriched to include the particular user id, and the enriched one or more log entries are stored in a threat detection system and used by the threat detection system to identify one or more security threats associated with the computing systems. 2. The method of claim 1 , wherein, for the system data, the master data is received from system context data associated with a particular computing system connected to the backend computing system as determined by a software application executing on the backend computing system or manual maintenance data related to a particular system context. 3. The method of claim 1 , wherein the user data is associated with a single individual or a common identification associated with multiple individuals. 4. The method of claim 1 , comprising: if determined that a user context associated with the particular user id is not available to the ESP, creating a new user context associated with the particular user id; and if determined that a user context associated with the particular user id is available to the ESP, updating the user context associated with the particular user id. 5. The method of claim 1 , comprising: if determined that a system context associated with the particular log providing computing system is not available to the ESP, creating a new system context associated with the particular log providing computing system; and if determined that a system context associated with the particular log providing computing system is available to the ESP, updating the system context associated with the particular log providing computing system. 6. The method of claim 1 , wherein the transfer of log data comprises: reading log data from a particular log associated with a particular computing system, wherein the log data is read starting with the latest timestamp; transferring read log data to the ESP, wherein the read log data is transformed into a normalized format prior to transfer; and enriching each log entry of the transferred log data. 7. The method of claim 6 , wherein the enrichment of each particular log entry comprises: attempting to read a user context for a particular user id associated with the particular log entry; if a user context for the particular user id is found within the backend computing system, writing into the particular log a user context id associated with the user context; if a user context for the particular user id is not found within the backend computing system, creating a new user context within the backend computing system and writing into the particular log a user context id associated with the new user context; removing the original user id from the particular log entry; and writing a revised log entry into the backend computing system. 8. A non-transitory, computer-readable medium storing computer-readable instructions, the instructions executable by a computer and configured to: execute a transfer of master data in a backend computing system, wherein the master data includes user data and system data, and wherein the transfer of master data comprises: receive, from a user management system or an identity management system, user data associated with a particular user id in the backend computing system; transfer the received user data to an event stream processor (ESP); receive system data associated with a particular log providing computing system in the backend computing system; and after transferring the received user data to the ESP, transfer the received system data to the ESP; and after executing the transfer of master data, execute a transfer of log data associated with logs of computing systems connected to the backend computing system, wherein one or more log entries of the transferred log data are enriched to include the particular user id, and the enriched one or more log entries are stored in a threat detection system and used by the threat detection system to identify one or more security threats associated with the computing systems. 9. The non-transitory, computer-readable medium of claim 8 , wherein, for the user data, the master data is received from a user management system or an identity management system, and wherein, for the system data, the master data is received from system context data associated with a particular computing system connected to the backend computing system as determined by a software application executing on the backend computing system or manual maintenance data related to a particular system context. 10. The non-transitory, computer-readable medium of claim 8 , wherein the user data is associated with a single individual or a common identification associated with multiple individuals. 11. The non-transitory, computer-readable medium of claim 8 , the instructions further configured to: if determined that a user context associated with the particular user id is not available to the ESP, create a new user context associated with the particular user id; and if determined that a user context associated with the particular user id is available to the ESP, update the user context associated with the particular user id. 12. The non-transitory, computer-readable medium of claim 8 , the instructions further configured to: if determined that a system context associated with the particular log providing computing system is not available to the ESP, create a new system context associated with the particular log providing computing system; and if determined that a system context associated with the particular log providing computing system is available to the ESP, update the system context associated with the particular log providing computing system. 13. The non-transitory, computer-readable medium of claim 8 , wherein the transfer of log data comprises: reading log data from a particular log associated with a particular computing system, wherein the log data is read starting with the latest timestamp; transferring read log data to the ESP, wherein the read log data is transformed into a normalized format prior to transfer; and enriching each log entry of the transferred log data. 14. The non-transitory, computer-readable medium of claim 13 , wherein the enrichment of each particular log entry comprises: attempting to read a user context for a particular user id associated with the particular log entry; if a user context for the particular user id is found within the backend computing system, writing into the particular log a user context id associated with the user context; if a user context for the particular user id is not found within the backend computing system, creating a new us

Assignees

Inventors

Classifications

  • Traffic logging, e.g. anomaly detection · CPC title

  • Event detection, e.g. attack signature detection · CPC title

Patent family

Related publications grouped by family.

External sources

Frequently asked questions

Answers are generated from the same data shown on this page.

What does patent US11252168B2 cover?
A transfer of master data is executed in a backend computing system. The master data includes user data and system data. The transfer of master data includes receiving user data associated with a particular user identifier in the backend computing system, transferring the received user data to an event stream processor, receiving system data associated with a particular log providing computing …
Who is the assignee on this patent?
Sap Se
What technology area does this patent fall under?
Primary CPC classification H04L63/1425. Mapped technology areas include Electricity.
When was this patent published?
Publication date Tue Feb 15 2022 00:00:00 GMT+0000 (Coordinated Universal Time) (B2). Legal status and post-grant events are not shown on this page.
What related patents are in patentsdb?
We list 12 related publications on this page (citations in our corpus or others sharing the same primary CPC).