Secure routing method, device, storage medium and program product

Abstract

The present application relates to a method for secure routing, an apparatus for secure routing, a non-transitory computer-readable storage medium, and a computer program product. According to one aspect of the present application, a method for secure routing is provided, the method comprising the following steps: determining a routing node and a routing attack type corresponding to a service request from a user in response to the service request; determining a risk standard metric for each routing node in the routing nodes corresponding to the service request under each routing attack type under a risk standard database, wherein the risk standard database is determined based at least on security level change data between each routing node in a private server being subjected to multiple corresponding routing attacks under each routing attack type; and determining a global optimal routing path based on the risk standard metric and scheduling data in the private server via the global optimal routing path to respond to the service request.

Description

Technical Field

[0001] The present application relates to the field of network communications, and more particularly to a secure routing method, a secure routing device, a non-transitory computer-readable storage medium, and a computer program product. Background Art

[0002] With the continuous development of the Internet and information technology, more and more business systems adopt the microservice distributed intelligent network deployment architecture. In the microservice distributed intelligent network deployment architecture, it is necessary to ensure the routing security of the data transmission in the intelligent network.

[0003] However, in intelligent networks, facing various routing attacks in complex attack scenarios, it is difficult to cover various routing attacks in complex attack scenarios with one protection method or a single protection solution due to the complexity and diversity of attack types and the variety of business scenarios. Summary of the invention

[0004] In order to solve or at least alleviate one or more of the above problems, the following technical solutions are provided.

[0005] According to a first aspect of the present application, a method for secure routing is provided, the method comprising the following steps: determining, in response to a service request from a user, a routing node and a routing attack type corresponding to the service request; determining, based on a risk standard database, a risk standard metric for each routing node in the routing nodes corresponding to the service request being subjected to a corresponding routing attack under each routing attack type, wherein the risk standard database is determined based at least on security level change data between each routing node in a private server being subjected to multiple corresponding routing attacks under each routing attack type; and determining a global optimal routing path based on the risk standard metric and scheduling data in the private server via the global optimal routing path to respond to the service request.

[0006] According to the method of secure routing described in one embodiment of the present application, determining the routing node and routing attack type corresponding to the service request includes: determining the domain name in the URL corresponding to the service request; obtaining one or more network segments in the IP field corresponding to the domain name; determining the data accessed by the service request based on the one or more network segments; and determining the routing node corresponding to the service request based on the data accessed by the service request and determining the routing attack type based on the routing node.

[0007] According to the method for secure routing according to one embodiment of the present application or any of the above embodiments, the routing attack types include one or more of the following: black hole attack, gray hole attack, wormhole attack, forged routing error attack, rushing attack, denial of service attack, forged routing discovery message attack, routing table overflow attack, false routing information attack, confirmation spoofing attack, and selective forwarding attack.

[0008] According to the secure routing method described in one embodiment of the present application or any of the above embodiments, the risk standard database is obtained in the following manner: determining the routing attack type of each routing node in the private server; simulating multiple routing attacks under each routing attack type to determine the security level of each routing node; determining the security level change data of each routing node based on the security level of each routing node between the multiple routing attacks; and obtaining the risk standard database based on the security level change data.

[0009] According to the secure routing method described in one embodiment of the present application or any of the above embodiments, simulating multiple routing attacks under each routing attack type to determine the security level of each routing node includes: simulating multiple routing attacks under each routing attack type to determine the probability measurement of each routing node being attacked by each routing attack; and determining the security level of each routing node based on the probability measurement of each routing node being attacked by each routing attack.

[0010] According to the secure routing method described in one embodiment of the present application or any of the above embodiments, determining the security level change data of each routing node based on the security level of each routing node between the multiple routing attacks includes: determining the first security level of each routing node of the first multiple routing attacks and the second security level of each routing node of the second multiple routing attacks among the multiple routing attacks; determining the ratio of the first security level to the second security level; and determining the security level change data of each routing node based at least on a logarithmic operation of the ratio.

[0011] According to the secure routing method of one embodiment of the present application or any one of the above embodiments, the number of the first multiple routing attacks is greater than the number of the second multiple routing attacks.

[0012] According to the method for secure routing described in one embodiment of the present application or any of the above embodiments, determining the risk standard metric of each routing node in the routing nodes corresponding to the service request being subjected to a corresponding routing attack under each routing attack type based on a risk standard database includes: retrieving security level change data of the routing nodes and routing attack types corresponding to the service request in the risk standard database; and determining the risk standard metric of each routing node in the routing nodes corresponding to the service request being subjected to a corresponding routing attack under each routing attack type based on the retrieved security level change data.

[0013] According to the secure routing method described in one embodiment of the present application or any of the above embodiments, determining the global optimal routing path based on the risk standard metric includes: determining one or more secure routing nodes based on the risk standard metric; determining the global optimal routing path based on the one or more secure routing nodes.

[0014] According to the secure routing method described in one embodiment of the present application or any of the above embodiments, determining one or more secure routing nodes based on the risk standard metric includes: determining the one or more secure routing nodes based on a comparison between an absolute value of the risk standard metric and a zero value.

[0015] According to a second aspect of the present application, a secure routing device is provided, the device comprising: a memory; a processor coupled to the memory; and a computer program stored on the memory, wherein when the computer program runs on the processor, it causes the steps of the secure routing method described in the first aspect of the present application to be executed.

[0016] According to a third aspect of the present application, a non-transitory computer-readable storage medium is provided, characterized in that the non-transitory computer-readable storage medium includes instructions, and the instructions execute the steps of the secure routing method described in the first aspect of the present application when running.

[0017] According to a fourth aspect of the present application, a computer program product is provided, wherein the computer program product comprises instructions, and when the instructions are executed by a processor, the steps of the secure routing method according to the first aspect of the present application are implemented.

[0018] The secure routing solution according to one or more embodiments of the present application can determine a risk standard database based at least on the security level change data between each routing node in the private server under each routing attack type and the risk standard measurement of each routing node in the routing nodes corresponding to the service request under each routing attack type, and thereby determine the global optimal routing path to schedule the data in the private server to respond to the service request, thereby effectively protecting against various routing attacks in complex attack scenarios, flexibly and efficiently meeting various protection scenario requirements in the network, and improving the efficiency and protection effect of combating routing attacks. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] The above and / or other aspects and advantages of the present application will become clearer and easier to understand through the following description of various aspects in conjunction with the accompanying drawings, in which the same or similar units are represented by the same reference numerals. In the accompanying drawings:

[0020] Figure 1 A flow chart of a secure routing method according to one or more embodiments of the present application is shown.

[0021] Figure 2 A hierarchical schematic diagram of secure routing according to one or more embodiments of the present application is shown.

[0022] Figure 3 A schematic diagram showing the security level of a typical routing node.

[0023] Figure 4 A schematic diagram of a typical risk criteria database is shown.

[0024] Figure 5 A schematic block diagram of a secure routing apparatus according to one or more embodiments of the present application is shown. DETAILED DESCRIPTION

[0025] The following describes in detail example embodiments of the present application, and examples of these embodiments are illustrated in the accompanying drawings. It should be noted that the following description is for explanation and illustration and is therefore not to be construed as limiting the present application. Without departing from the principles of the present application, those skilled in the art may make electrical, mechanical, logical and structural changes to these embodiments as needed without departing from the scope of the present application. In addition, those skilled in the art may appreciate that, for any specific application scenario or actual need, one or more features of the different embodiments described below may be combined.

[0026] Terms such as "comprising" and "including" indicate that in addition to the units and steps directly and clearly stated in the specification, the technical solution of the present application does not exclude the situation of having other units and steps that are not directly or clearly stated. Terms such as "first" and "second" do not indicate the order of units in terms of time, space, size, etc., but are only used to distinguish between units.

[0027] Hereinafter, various exemplary embodiments according to the present application will be described in detail with reference to the accompanying drawings.

[0028] Figure 1 A flow chart of a secure routing method according to one or more embodiments of the present application is shown.

[0029] like Figure 1 As shown in FIG. 1 , in step S101 , in response to a service request from a user, a routing node and a routing attack type corresponding to the service request are determined.

[0030] In one embodiment, a service request from a user may be used to request access to data of one or more routing nodes in a private server (e.g., a cluster in a private cloud). A cluster in a private cloud generally refers to a group of mutually cooperating servers deployed in a private cloud environment that provide services as a unified computing resource. These clusters may be built based on virtualization technology or on physical servers, which may be connected via a private network. Exemplarily, a cluster in a private cloud may include a Redis cluster, a Mysql cluster, an ES cluster, a RabbitMQ cluster, and the like.

[0031] Optionally, in step S101, a domain name in a URL (Uniform ResourceLocator) corresponding to a service request may be determined, one or more network segments in an IP field corresponding to the domain name may be obtained, data accessed by the service request may be determined based on the one or more network segments, and a routing node corresponding to the service request may be determined based on the data accessed by the service request, and a routing attack type may be determined based on the routing node. Exemplarily, the routing node corresponding to the service request may be implemented as a routing node in one or more private servers. Exemplarily, the data accessed by the service request may include user data (e.g., user files, documents, pictures, videos, etc.), system data (e.g., configuration files, logs, etc. of operating systems, applications, and middleware), backup data (e.g., backup copies of system and user data for disaster recovery, etc.), security data (e.g., access control lists, identity authentication information, encryption keys, etc.), monitoring data (e.g., cluster performance monitoring, resource usage, system logs, etc.), etc.

[0032] In step S103, a risk standard metric of each routing node in the routing nodes corresponding to the service request being subjected to a corresponding routing attack under each routing attack type is determined based on a risk standard database, wherein the risk standard database is determined based at least on security level change data between multiple corresponding routing attacks on each routing node in the private server under each routing attack type.

[0033] In one embodiment, the risk standard database may store the risk standard metric of each routing node in the private server being subjected to the corresponding routing attack under each routing attack type, wherein the risk standard metric may be determined based on the security level change data between each routing node in the private server being subjected to multiple corresponding routing attacks under each routing attack type. In one embodiment, the routing attack types may include black hole attack, gray hole attack, wormhole attack, forged routing error attack, rushing attack, denial of service attack, forged routing discovery message attack, routing table overflow attack, false routing information attack, confirmation spoofing attack, selective forwarding attack, etc.

[0034] In one embodiment, the routing attack type of each routing node in the private server can be determined, multiple routing attacks under each routing attack type can be simulated to determine the security level of each routing node, the security level change data of each routing node can be determined based on the security level of each routing node between multiple routing attacks, and the risk standard metric can be determined and stored based on the security level change data to obtain a risk standard database. In one embodiment, multiple routing attacks under each routing attack type can be simulated to determine the probability metric of each routing node being attacked by each routing attack, and the security level of each routing node can be determined based on the probability metric of each routing node being attacked by each routing attack. In one embodiment, the first security level of each routing node of the first multiple routing attacks and the second security level of each routing node of the second multiple routing attacks can be determined, the ratio of the first security level to the second security level can be determined, and the security level change data of each routing node can be determined based on at least a logarithmic operation of the ratio, wherein the number of the first multiple routing attacks is greater than the number of the second multiple routing attacks. Exemplarily, 50 routing attacks can be simulated for each routing node under each routing attack type and the second security level of each routing node can be determined, then 60 routing attacks can be simulated for each routing node under each routing attack type and the first security level of each routing node can be determined, the ratio of the first security level to the second security level can be determined, and the security level change data of each routing node can be determined based at least on a logarithmic operation of the ratio.

[0035] For example, the security level of each routing node can be determined by the following formula (1): :

[0036] Formula (1)

[0037] in, Indicates the number of routing attacks. Indicates the received Routing attack, Represents a routing node , Represents a routing node By the The probability metric of the secondary routing attack. For example, the probability metric Can be based on routing nodes The probability discretization index of The probability prediction value can be determined based on a test of simulating routing attacks, and the probability discretization index is It can be determined by the following formula (2):

[0038] = Formula (2)

[0039] in, Indicates the number of routing nodes involved in the service request from the user, Indicates the predefined minimum acceptable number of routing nodes.

[0040] For example, the security level change data of each routing node can be determined by the following formula (3): :

[0041] Formula (3)

[0042] in, Represents a routing node The first The security level of the secondary routing attack, Represents a routing node The first The security level of the routing attack is The second routing attack occurred in After the routing attack.

[0043] Optionally, in step S103, security level change data of the routing nodes and routing attack types corresponding to the service request may be retrieved from the risk standard database, and a risk standard metric of each routing node in the routing nodes corresponding to the service request being subjected to a corresponding routing attack under each routing attack type may be determined based on the retrieved security level change data.

[0044] In step S105, a global optimal routing path is determined based on the risk criterion metric and data in the private server is dispatched via the global optimal routing path to respond to the service request.

[0045] Optionally, in step S105, one or more secure routing nodes may be determined based on the risk standard metric, and the global optimal routing path may be determined based on the one or more secure routing nodes. In one embodiment, one or more secure routing nodes may be determined based on a comparison between an absolute value of the risk standard metric and a zero value. Figure 3 and Figure 4 The schematic diagram of security levels and the schematic diagram of risk standard database are shown to further describe the specific implementation method of determining the global optimal routing path.

[0046] The secure routing method according to one or more embodiments of the present application can determine a risk standard database based at least on the security level change data between each routing node in the private server and multiple corresponding routing attacks under each routing attack type, determine the risk standard measurement of each routing node in the routing nodes corresponding to the service request and receive the corresponding routing attack under each routing attack type based on the risk standard database, and thereby determine the global optimal routing path to schedule the data in the private server to respond to the service request, thereby effectively protecting against various routing attacks in complex attack scenarios, flexibly and efficiently meeting various protection scenario requirements in the network, and improving the efficiency and protection effect of combating routing attacks.

[0047] The following will be combined Figure 2-5 The specific implementation of secure routing according to one or more embodiments of the present application is further described.

[0048] Figure 2 A hierarchical schematic diagram of secure routing according to one or more embodiments of the present application is shown.

[0049] like Figure 2 As shown in FIG. 2 , the layer 200 of secure routing includes a service deployment node layer 210 , a service deployment retrieval layer 220 , and a service deployment protocol layer 230 .

[0050] The service deployment node layer 210 includes multiple routing nodes, which can be set in a private server (e.g., a cluster in a private cloud). Optionally, multiple routing attacks under each routing attack type can be simulated to determine the probability metric of each routing node being attacked by each routing attack, and the security level of each routing node can be determined based on the probability metric of each routing node being attacked by each routing attack. For example, the types of routing attacks may include black hole attacks, gray hole attacks, wormhole attacks, forged routing error attacks, rushing attacks, denial of service attacks, forged routing discovery message attacks, routing table overflow attacks, false routing information attacks, confirmation spoofing attacks, selective forwarding attacks, and the like.

[0051] Service deployment retrieval layer 220 is used for security level based on single routing attack To determine the security level of each routing node For example, the safety level value It can be determined by the following formula (4):

[0052] = Formula (4)

[0053] The service deployment protocol layer 230 is used to receive the security level value of each routing node from the service deployment retrieval layer 220 , and based on the security value of each routing node To determine the security level change data of each routing node as described above , and build a risk standard database. For example, based on routing nodes The first The security level of the secondary routing attack With routing nodes The first The security level of the secondary routing attack The difference between the two determines the security level change data of each routing node , among which The second routing attack occurred in After the routing attack. It is understandable that based on the routing node The first The security level of the secondary routing attack With routing nodes The first The security level of the secondary routing attack The difference can be expressed as shown in the above formula (3).

[0054] Figure 3 A schematic diagram showing the security level of a typical routing node.

[0055] like Figure 3As shown in the figure, the schematic diagram 300 of the security level of the routing node schematically shows the security level of each of the routing nodes 1-15 under each routing attack type (i.e., the value shown in the table), wherein the routing attack type may include black hole attack, gray hole attack, wormhole attack, forged routing error attack, rushing attack, denial of service attack, forged routing discovery message attack, routing table overflow attack, false routing information attack, confirmation spoofing attack, and selective forwarding attack. As an example, the security level of each routing node under each routing attack type in the schematic diagram 300 of the security level of the routing node can be determined by means of the formula (1) as described above, wherein the larger the value in the table, the greater the possibility that the routing node is attacked under the corresponding routing attack type.

[0056] It should be noted that Figure 3 The schematic diagram 300 is only used as an example to illustrate the security level of the routing node, without departing from the spirit and scope of the present application. Figure 3 The number of routing nodes and routing attack types shown may be changed or replaced.

[0057] Figure 4 A schematic diagram of a typical risk criteria database is shown.

[0058] like Figure 4 As shown in the diagram 400 of the risk standard database, each of the routing nodes 1-15 is schematically shown in the risk standard measurement under each routing attack type (i.e., the value shown in the table), wherein the routing attack type may include black hole attack, gray hole attack, wormhole attack, forged routing error attack, rushing attack, denial of service attack, forged routing discovery message attack, routing table overflow attack, false routing information attack, confirmation spoofing attack, and selective forwarding attack. As an example, the risk standard measurement of each routing node under each routing attack type in the diagram 400 of the risk standard database can be determined by means of the formula (3) as described above, wherein the larger the value in the table, the higher the risk level of the routing node under the corresponding routing attack type.

[0059] The following will be combined Figure 4 The determination of the global optimal routing path is further described. Figure 4 As shown in , assuming that the routing nodes corresponding to the service request are determined to be nodes 1-10, and the routing attack types corresponding to the service request are determined to include black hole attack, gray hole attack, wormhole attack, forged routing error attack, rushing attack, and denial of service attack, it can be based on Figure 4The risk standard metrics corresponding to nodes 1-10 and corresponding to black hole attacks, gray hole attacks, wormhole attacks, forged routing error attacks, rushing attacks, and denial of service attacks shown in the figure determine one or more secure routing nodes.

[0060] In one embodiment, one or more safe routing nodes may be determined based on the comparison between the absolute value of the risk standard metric and the zero value. As an example, the number of risk standard metrics equal to zero corresponding to each routing node under each routing attack type may be counted, and the routing node with the largest number may be regarded as a safe routing node. Figure 4 As shown, assuming that the routing nodes corresponding to the service request are determined to be nodes 1-10, and the routing attack types corresponding to the service request are determined to include black hole attack, gray hole attack, wormhole attack, forged routing error attack, Rushing attack, and denial of service attack, the number of risk standard metrics equal to zero in routing node 1 is 1, the number of risk standard metrics equal to zero in routing node 2 is 4, the number of risk standard metrics equal to zero in routing node 3 is 1, the number of risk standard metrics equal to zero in routing node 4 is 3, the number of risk standard metrics equal to zero in routing node 5 is 2, the number of risk standard metrics equal to zero in routing node 6 is 4, the number of risk standard metrics equal to zero in routing node 7 is 3, the number of risk standard metrics equal to zero in routing node 8 is 3, the number of risk standard metrics equal to zero in routing node 9 is 3, and the number of risk standard metrics equal to zero in routing node 10 is 3. Based on the comparison of the above-mentioned respective quantities, one or more of routing node 2 and routing node 6 can be determined as a secure routing node. As an example, when the risk standard metric corresponding to each routing node is not equal to zero, the absolute value of the risk standard metric under each routing attack type of each routing node can be counted and the sum of each absolute value can be determined, and one or more routing nodes corresponding to the minimum absolute value sum can be determined as safe routing nodes.

[0061] Figure 5 A schematic block diagram of a secure routing apparatus according to one or more embodiments of the present application is shown.

[0062] like Figure 5 As shown in FIG, the secure routing apparatus 500 includes a memory 510, a processor 520, and a computer program 530 stored in the memory 510 and executable on the processor 520. The processor 520 executes the computer program 530 to implement a secure routing method according to one aspect of the present application.

[0063] In addition, the present application may also be implemented as a non-transitory computer-readable storage medium, in which a program for causing a computer to execute the secure routing method according to one aspect of the present application is stored.

[0064] Here, as non-temporary computer-readable storage media, various forms of non-temporary computer-readable storage media can be used, such as disks (e.g., magnetic disks, optical disks, etc.), cards (e.g., memory cards, optical cards, etc.), semiconductor memories (e.g., ROMs, non-volatile memories, etc.), and tapes (e.g., magnetic tapes, cassettes, etc.).

[0065] In the applicable situation, hardware, software or a combination of hardware and software can be used to realize the various embodiments provided by the application. Moreover, in the applicable situation, without departing from the scope of the application, the various hardware components and / or software components set forth herein can be combined into a composite component comprising software, hardware and / or both. In the applicable situation, without departing from the scope of the application, the various hardware components and / or software components set forth herein can be divided into subcomponents comprising software, hardware or both. In addition, in the applicable situation, it is contemplated that the software component can be implemented as a hardware component, and vice versa.

[0066] Software according to the present application (such as program code and / or data) may be stored on one or more non-transitory computer-readable storage media. It is also contemplated that the software identified herein may be implemented using one or more general or special-purpose computers and / or computer systems, networked and / or otherwise. Where applicable, the order of the various steps described herein may be changed, combined into composite steps, and / or divided into sub-steps to provide the features described herein.

[0067] The embodiments and examples set forth herein are provided to best illustrate embodiments according to the present application and its specific applications, and thereby enable those skilled in the art to implement and use the present application. However, those skilled in the art will appreciate that the above description and examples are provided only for ease of illustration and example. The description set forth is not intended to cover all aspects of the present application or to limit the present application to the precise form disclosed.

Claims

1. A secure routing method, characterized in that: The method comprises the following steps: In response to a service request from a user, determining a routing node and a routing attack type corresponding to the service request; Determine, based on a risk standard database, a risk standard metric of each routing node in the routing nodes corresponding to the service request being subjected to a corresponding routing attack under each routing attack type, wherein the risk standard database is determined based at least on security level change data between each routing node in the private server being subjected to a plurality of corresponding routing attacks under each routing attack type; and determining a global optimal routing path based on the risk criteria metric and dispatching data in the private server via the global optimal routing path to respond to the service request, Wherein determining the global optimal routing path based on the risk standard measurement includes: determining one or more secure routing nodes based on the risk criteria metric; determining the globally optimal routing path based on the one or more secure routing nodes, Wherein determining one or more secure routing nodes based on the risk standard metric comprises: Count the number of risk standard metrics equal to zero for each routing node under each routing attack type and take the routing node with the largest number as a safe routing node; When the risk standard metric corresponding to each routing node is not equal to zero, the absolute value of the risk standard metric under each routing attack type of each routing node is counted and the sum of each absolute value is determined, and one or more routing nodes corresponding to the minimum absolute value sum are determined as safe routing nodes.

2. The method of claim 1, wherein determining a routing node and a routing attack type corresponding to the service request comprises: Determining a domain name in a URL corresponding to the service request; Obtain one or more network segments in the IP field corresponding to the domain name; determining data accessed by the service request based on the one or more network segments; as well as A routing node corresponding to the service request is determined based on the data accessed by the service request, and the routing attack type is determined based on the routing node.

3. The method according to claim 1, wherein the routing attack types include one or more of the following: black hole attack, gray hole attack, wormhole attack, forged routing error attack, rushing attack, denial of service attack, forged routing discovery message attack, routing table overflow attack, false routing information attack, confirmation spoofing attack, and selective forwarding attack.

4. The method according to claim 1, wherein the risk standard database is obtained by: Determining a routing attack type for each routing node in the private server; Simulating multiple routing attacks under each routing attack type to determine the security level of each routing node; Determine security level change data of each routing node based on the security level of each routing node between the multiple routing attacks; as well as The risk standard database is obtained based on the security level change data.

5. The method according to claim 4, wherein simulating multiple routing attacks under each routing attack type to determine the security level of each routing node comprises: Simulating multiple routing attacks under each routing attack type to determine a probability metric of each routing node being subjected to each routing attack; as well as The security level of each routing node is determined based on a probability metric of each routing node being attacked by each routing attack.

6. The method according to claim 4, wherein determining the security level change data of each routing node based on the security level of each routing node between the multiple routing attacks comprises: Determine a first security level of each routing node of a first plurality of routing attacks and a second security level of each routing node of a second plurality of routing attacks in the plurality of routing attacks; determining a ratio of the first security level to the second security level; as well as The security level change data of each routing node is determined based on at least a logarithmic operation of the ratio. 7 . The method according to claim 6 , wherein the number of the first multiple routing attacks is greater than the number of the second multiple routing attacks.

8. The method according to claim 1, wherein determining, based on a risk standard database, a risk standard metric of each routing node in the routing nodes corresponding to the service request being subjected to a corresponding routing attack under each routing attack type comprises: Retrieving security level change data of routing nodes and routing attack types corresponding to the service request in the risk standard database; A risk standard metric of each routing node among the routing nodes corresponding to the service request being subjected to a corresponding routing attack under each routing attack type is determined based on the retrieved security level change data.

9. A secure routing device, characterized in that: The device comprises: Memory; a processor coupled to the memory; and A computer program stored on the memory and running on the processor, the execution of the computer program results in the execution of the secure routing method according to any one of claims 1-8.

10. A non-transitory computer-readable storage medium, characterized in that: The non-transitory computer-readable storage medium includes instructions that, when executed, perform the method for secure routing according to any one of claims 1-8.

11. A computer program product, characterized in that The computer program product comprises instructions, which, when executed by a processor, implement the method for secure routing according to any one of claims 1-8.

Images