System and method for mapping network identifiers

1 . A method for mapping vulnerabilities to a private network identifier, comprising:

generating a request addressed to a public network identifier of a server, wherein the request includes a first beacon;

transmitting the generated request to the server, wherein upon receiving the request by the server, the request causes a registry of log in a log file of the server, wherein the log includes at least the first beacon;

in response to a query, receiving a response from the server, wherein the response includes a second beacon, and a private network identifier of the server;

associating the public network identifier with the private network identifier, when the first beacon matches the second beacon; and

mapping vulnerabilities identified with the public network identifier to associate the identified vulnerabilities with the associated public network identifier and the private network identifier.

2 . The method of claim 1 , wherein generating the request further comprises: generating the first beacon, wherein the first beacon is a unique identifier.

3 . The method of claim 1 , further comprising:

storing the associated public network identifier and the private network identifier in a storage.

4 . The method of claim 1 , wherein causing the registry of the log in the log file further comprising:

configuring the request to perform an action forcing the server to register the at least the first beacon in the log file.

5 . The method of claim 4 , wherein the action includes at least: an unauthorized request, or a legitimate request.

6 . The method of claim 1 , identifying the vulnerabilities detected with respect to at least the public network identifier further comprises:

receiving the vulnerabilities from at least one cyber-security tool.

7 . The method of claim 1 , wherein the log further comprises: the first beacon, a time stamp, a port number, a uniform resource locator (URL).

8 . The method of claim 1 , wherein the private network identifier is at least an Internet Protocol (IP) address.

9 . The method of claim 1 , wherein the public network identifier is any of: an IP address, and a uniform resource locator (URL).

10 . The method of claim 1 , wherein the request is any of: an HTTP request and an TCP/IP request, wherein the first beacon is included in a payload data of the request.

11 . The method of claim 1 , wherein the server is any one of: a physical machine, a virtual, a software container, a service, and wherein the server is deployed in a cloud computing platform.

12 . A non-transitory computer-readable medium storing a set of instructions for mapping vulnerabilities to a private network identifier, the set of instructions comprising:

one or more instructions that, when executed by one or more processors of a device, cause the device to:

generate a request addressed to a public network identifier of a server, wherein the request includes a first beacon;

 transmit the generated request to the server, wherein upon receiving the request by the server, the request causes a registry of log in a log file of the server, wherein the log includes at least the first beacon;

 in response to a query, receive a response from the server, wherein the response includes a second beacon, and a private network identifier of the server;

 associate the public network identifier with the private network identifier, when the first beacon matches the second beacon; and

 map vulnerabilities identified with the public network identifier to associate the identified vulnerabilities with the associated public network identifier and the private network identifier.

13 . A system for mapping vulnerabilities to a private network identifier comprising:

one or more processors configured to:

generate a request addressed to a public network identifier of a server, wherein the request includes a first beacon;

transmit the generated request to the server, wherein upon receiving the request by the server, the request causes a registry of log in a log file of the server, wherein the log includes at least the first beacon;

in response to a query, receive a response from the server, wherein the response includes a second beacon, and a private network identifier of the server;

associate the public network identifier with the private network identifier, when the first beacon matches the second beacon; and

map vulnerabilities identified with the public network identifier to associate the identified vulnerabilities with the associated public network identifier and the private network identifier.

14 . The system of claim 13 , wherein the one or more processors, when generating the request, are configured to:

generate the first beacon, wherein the first beacon is a unique identifier.

15 . The system of claim 13 , wherein the one or more processors are further configured to:

store the associated public network identifier and the private network identifier in a storage.

16 . The system of claim 13 , wherein the one or more processors, when causing the registry of the log in the log file, are configured to:

configure the request to perform an action forcing the server to register the at least the first beacon in the log file.

17 . The system of claim 16 , wherein the action includes at least any of:

an unauthorized and a legitimate request.

18 . The system of claim 13 , wherein the one or more processors are further configured to: receive the vulnerabilities from at least one cyber-security tool.

19 . The system of claim 13 , wherein the log further comprises:

the first beacon, a timestamp, a port number, a uniform resource locator (URL).

20 . The system of claim 13 , wherein the private network identifier is at least an Internet Protocol (IP) address.

21 . The system of claim 13 , wherein the public network identifier is any of:

an IP address, and a uniform resource locator (URL).

22 . The system of claim 13 , wherein the request is any of:

an HTTP request and q TCP/IP request, wherein the first beacon is included in a payload data of the request.

23 . The system of claim 13 , wherein the server is any one of: a physical machine, a virtual machine, a software container, a service, and wherein the server is deployed in a cloud computing platform.