Bi-directional content replication logic for enterprise threat detection

Patent metadata

Field	Value
Publication number	US-11470094-B2
Application number	US-201615381567-A
Country	US
Kind code	B2
Filing date	Dec 16, 2016
Priority date	Dec 16, 2016
Publication date	Oct 11, 2022
Grant date	Oct 11, 2022

Abstract

A content replication connector receives control data associated with replication of content data from a source system. Based on the control data, the content replication connector fetches the content data from the source system, converts the content data from a first data format to a second data format, and sends the content data to a content replication server. The content replication server replicates the content data, and a target system fetches the content data from the content replication server.

First claim

What is claimed is:

1. A computer-implemented method, comprising:
connecting a content replication server to a first content replication connector and a second content replication connector, the first content replication connector and the second content replication connector each comprising an import module, an export module, and a read content replication content module, the content replication server comprising a reactive component connectable to a plurality of systems being unaware of a total number of the plurality of systems;
connecting a source system to the content replication server through the first content replication connector;
connecting a target system to the content replication server through the second content replication connector;
receiving, by the read content replication content module of the first content replication connector and from the source system, control data associated with replication of content data, wherein the control data indicates the source system and the target system; and
based on the control data:
fetching, by the import module of the first content replication connector, the content data from the source system;
converting, by the import module of the first content replication connector, the content data from a first data format to a second data format; and
sending, by the export module of the first content replication connector, the content data to the content replication server, wherein the content replication server replicates the content data, and the target system fetches the content data from the content replication server through the second content replication connector.

2. The computer-implemented method of claim 1 , wherein the source system is a productive enterprise threat detection system, the target system is a development and test enterprise threat detection system, and the content data is context data of the productive enterprise threat detection system.

3. The computer-implemented method of claim 1 , wherein the source system is a development and test enterprise threat detection system, the target system is a productive enterprise threat detection system, and the content data includes one or more development objects.

4. The computer-implemented method of claim 1 , wherein the second data format is JAVASCRIPT Object Notation (JSON).

5. The computer-implemented method of claim 1 , wherein the first content replication connector is in a workspace on a smart database streaming server connected to the source system, the workspace having a name including a system identifier of the source system.

6. The computer-implemented method of claim 1 , wherein the content replication server is in a workspace on a smart database streaming server connected to the source system or the target system.

7. The computer-implemented method of claim 1 , wherein receiving the control data from the source system includes polling the source system.

8. The computer-implemented method of claim 1 , wherein the target system is connected to the second content replication connector, wherein the second content replication connector receives the control data from the target system, and based on the control data the second content replication connector fetches the content data from the content replication server.

9. The computer-implemented method of claim 8 , wherein the second content replication connector further converts the content data from the second data format to the first data format, and sends the content data to the target system.

10. A non-transitory, computer-readable medium storing one or more instructions executable by a computer system to perform operations comprising:
connecting a content replication server to a first content replication connector and a second content replication connector, the first content replication connector and the second content replication connector each comprising an import module, an export module, and a read content replication content module, the content replication server comprising a reactive component connectable to a plurality of systems being unaware of a total number of the plurality of systems;
connecting a source system to the content replication server through the first content replication connector;
connecting a target system to the content replication server through the second content replication connector;
receiving, by the read content replication content module of the first content replication connector and from the source system, control data associated with replication of content data, wherein the control data indicates the source system and the target system; and
based on the control data:
fetching, by the import module of the first content replication connector, the content data from the source system;
converting, by the import module of the first content replication connector, the content data from a first data format to a second data format; and
sending, by the export module of the first content replication connector, the content data to the content replication server, wherein the content replication server replicates the content data, and the target system fetches the content data from the content replication server through the second content replication connector.

11. The non-transitory, computer-readable medium of claim 10 , wherein the source system is a productive enterprise threat detection system, the target system is a development and test enterprise threat detection system, and the content data is context data of the productive enterprise threat detection system.

12. The non-transitory, computer-readable medium of claim 10 , wherein the source system is a development and test enterprise threat detection system, the target system is a productive enterprise threat detection system, and the content data includes one or more development objects.

13. The non-transitory, computer-readable medium of claim 10 , wherein the second data format is JAVASCRIPT Object Notation (JSON).

14. The non-transitory, computer-readable medium of claim 10 , wherein the first content replication connector is in a workspace on a smart database streaming server connected to the source system, the workspace having a name including a system identifier of the source system.

15. The non-transitory, computer-readable medium of claim 10 , wherein the content replication server is in a workspace on a smart database streaming server connected to the source system or the target system.

16. The non-transitory, computer-readable medium of claim 10 , wherein the target system is connected to the second content replication connector, wherein the second content replication connector receives the control data from the target system, and based on the control data the second content replication connector fetches the content data from the content replication server.

17. The non-transitory, computer-readable medium of claim 16 , wherein the second content replication connector further converts the content data from the second data format to the first data format, and sends the content data to the target system.

18. A computer-implemented system, comprising:
a computer memory; and
a hardware processor interoperably coupled with the computer memory and configured to perform operations comprising:
connecting a content replication server to a first content replication connector and a second content replication connector, the first content replication connector and the second content replication connector each comprising an import module, an export module, and a read content replication content module, the

Assignees

• Sap Se

Inventors

• Kunz Thomas
• Al-Hujaj Omar-Alexander
• Baumgart Jens
• Mehta Harish
• Chrosziel Florian
• Rodeck Marco
• Menke Thorsten

Classifications

• G06F16/27

  Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor · CPC title

• H04L63/1416 Primary

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

• H04L63/1425

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