IP Library Granted Patent US 10,587,651
Granted Patent B2
US 10,587,651 · App. 15/591,240 · Granted Mar 10, 2020

Protection of cloud-provider system using scattered honeypots

Inventors: Pavel Gurvich (Tel Aviv, IL); Ofri Ziv (Herzliya, IL); Yoni Rozenshein (Ramat Gan, IL)
Assignee: Guardicore Ltd.
H04L63/1491H04L61/2038H04L63/1408H04L67/1097
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 10,587,651
App. No.
15/591,240
Granted
Mar 10, 2020
Kind
B2
Abstract

An apparatus for securing a cloud-provider system includes one or more network interfaces and one or more processors. The network interfaces are configured for connecting to a network. The processors are configured to allocate resources of the cloud-provider system for use by tenants of the cloud-provider system, to allocate to the tenants one or more Internet Protocol (IP) address ranges, to assign multiple IP addresses, scattered across the IP address ranges, for use by one or more honeypot servers, and to secure the cloud-provider system against hostile attacks, by processing network traffic associated with the assigned IP addresses using at least the honeypot servers.

Claims (27)

1. An apparatus for securing a cloud-provider system, the apparatus comprising:

one or more network interfaces for connecting to a network; and

one or more processors, configured to allocate resources of the cloud-provider system for use by a plurality of tenants of the cloud-provider system, to allocate to each of the plurality of the tenants one or more Internet Protocol (IP) address ranges, to assign multiple IP addresses, scattered across the IP address ranges, for use by one or more honeypot servers, and to secure the cloud-provider system against hostile attacks, by processing network traffic associated with the assigned IP addresses using at least the one or more honeypot servers.

2. The apparatus according to claim 1 , wherein each of the IP address ranges comprises a respective IP subnet and wherein the IP addresses assigned for use by one or more honeypot servers comprise at least one IP address in the same subnet as each of the allocated IP address ranges.

3. The apparatus according to claim 1 , wherein the one or more processors are configured to secure the cloud-provider system without accessing the resources allocated to the tenants.

4. The apparatus according to claim 1 , wherein the one or more processors are configured to:

extract one or more attack parameters from the network traffic associated with the assigned IP addresses;

specify a rule based on the extracted parameters; and

apply the rule to other network traffic, which is associated with other IP addresses in the IP address ranges, different from the assigned IP addresses.

5. The apparatus according to claim 4 , wherein the rule comprises a blocking rule specifying network traffic to be blocked, or a reporting rule specifying an attack to be reported.

6. The apparatus according to claim 1 , wherein the one or more processors are configured to extract attack parameters from the network traffic associated with the assigned IP addresses, to cluster detected attacks to one or more groups, and to secure the cloud-provider system responsively to the groups.

7. The apparatus of claim 2 , wherein the subnets including the IP address ranges include subnets of a plurality of different sizes.

8. The apparatus of claim 2 , wherein the processor is configured to assign the IP addresses for use by one or more honeypot servers, at the lower edges of the IP address range in the same subnet.

9. The apparatus of claim 2 , wherein the processor is configured to assign the IP addresses for use by one or more honeypot servers, at the upper edges of the IP address range in the same subnet.

10. The apparatus of claim 2 , wherein the processor is configured to assign the IP addresses for use by one or more honeypot servers, in the middle of the IP address range in the same subnet.

11. A method for securing a cloud-provider system, the method comprising:

allocating resources of the cloud-provider system for use by a plurality of tenants of the cloud-provider system, and further allocating to each of the plurality of the tenants one or more Internet Protocol (IP) address ranges;

assigning multiple IP addresses, scattered across the IP address ranges, for use by one or more honeypot servers; and

securing the cloud-provider system against hostile attacks, by processing network traffic associated with the assigned IP addresses using at least the one or more honeypot servers.

12. The method according to claim 11 , wherein each of the IP address ranges comprises a respective IP subnet and wherein assigning the multiple IP addresses for use by the one or more honeypot servers comprises assigning at least one IP address in the same subnet as each of the allocated IP address ranges.

13. The method according to claim 11 , wherein securing the cloud-provider system is performed without accessing the resources allocated to the tenants.

14. The method according to claim 11 , wherein securing the cloud-provider system comprises:

extracting one or more attack parameters from the network traffic associated with the assigned IP addresses;

specifying a rule based on the extracted parameters; and

applying the rule to other network traffic, which is associated with other IP addresses in the IP address ranges, different from the assigned IP addresses.

15. The method according to claim 14 , wherein the rule comprises a blocking rule specifying network traffic to be blocked, or a reporting rule specifying an attack to be reported.

16. The method according to claim 11 , wherein securing the cloud-provider system comprises extracting attack parameters from the network traffic associated with the assigned IP addresses, clustering detected attacks to one or more groups, and securing the cloud-provider system responsively to the groups.

Assignments (4)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 5, 2022
From: GUARDICORE LTD.
To: AKAMAI TECHNOLOGIES, INC.
Reel/Frame 061313/0504 →
RELEASE OF SECURITY INTEREST Recorded Oct 12, 2021
From: SILICON VALLEY BANK
To: GUARDICORE LTD
Reel/Frame 057768/0936 →
SECURITY INTEREST Recorded Jan 14, 2019
From: GUARDICORE LTD
To: SILICON VALLEY BANK
Reel/Frame 047989/0806 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded May 10, 2017
From: GURVICH, PAVEL; ZIV, OFRI; ROZENSHEIN, YONI
To: GUARDICORE LTD.
Reel/Frame 042320/0488 →
Continuity (2)
Provisional Application 62339896 · May 22, 2016
Related Publication 20170339186A1 · Nov 23, 2017
Cited By (1)
US 12,293,094