Efficiently updating device-level security configurations based on changes to security intent policy models

Abstract

Embodiments of the present disclosure relate to efficiently updating device-level security configurations based on changes to a security intent policy model. A system can identify a security intent policy model associated with an initial time. The system can generate one or more delta snapshots respectively indicating one or more incremental changes to the security intent policy model after the initial time. The system can determine that the system is to deploy an updated version of the security intent policy model to a device, and can thereby determine a previous deployment time at which the system deployed a previous version of the security intent policy model to the device. The system can generate a cumulative delta snapshot based on the one or more delta snapshots and the previous deployment time, and can thereby update a low-level security intent policy model associated with the device. The system can generate device-level security configuration information for the device based on the low-level security intent policy model.

Description

Technical Field

[0001] This disclosure generally relates to networking technologies, and more specifically to the efficient updating of device-level security configurations based on changes to security intent policy models. Background Technology

[0002] Network devices typically include mechanisms for configuring the network device locally or remotely, such as a management interface. By interacting with the management interface, administrators can perform configuration tasks such as configuring the network device's interface cards, adjusting parameters for supported network protocols used by the network device, specifying physical components within the network device, modifying routing information maintained by the network device, accessing software modules and other resources residing on the network device, and / or other configuration tasks.

[0003] Network devices can be configured by a network management system based on declarative network operation models, such as intent-based networking models. The network management system allows administrators to describe one or more intent states of a network device, such as the intended network state, execution state, storage state, and / or another state. Intents can be categorized as stateful intents and stateless intents. Stateful intents (also known as "business policies") can be resolved based on the current state of the network device. Stateless intents can be resolved regardless of the current state of the network.

[0004] Intents can be represented in an intent data model, which can be modeled using a unified graph. For example, an intent data model can be represented as a connected graph with vertices (e.g., representing configuration objects) connected by edges (e.g., representing relationships between configuration objects). To configure a network device to execute an intent, a translator translates high-level configuration information (e.g., including instructions based on the intent data model, which can be represented as a connected graph) into low-level configuration information for the network device (e.g., including instructions based on a device configuration model). Summary of the Invention

[0005] Some implementations described herein relate to a method. This method may include identifying a security intent policy model associated with an initial time by the system. This method may include generating one or more delta snapshots by the system, each indicating one or more incremental changes to the security intent policy model after the initial time. This method may include determining, by the system, an updated version of the security intent policy model to be deployed to the device. This method may include determining, by the system and based on the determination of the updated version of the security intent policy model to be deployed, a previous deployment time when the system deployed a previous version of the security intent policy model to the device. This method may include generating a cumulative delta snapshot by the system and based on one or more delta snapshots and the previous deployment time. This method may include updating the low-level security intent policy model associated with the device by the system and based on the cumulative delta snapshot. This method may include generating device-level security configuration information for the device by the system and based on the low-level security intent policy model.

[0006] Some implementations described herein relate to a non-transitory computer-readable medium storing a set of instructions for a system. When executed by one or more processors of the system, this set of instructions can cause the system to generate one or more differential snapshots, each indicating one or more incremental changes to a security intent policy model at a time following an initial time. When executed by one or more processors of the system, this set of instructions can cause the system to determine that an updated version of the security intent policy model should be deployed to a device. When executed by one or more processors of the system, this set of instructions can cause the system to generate a cumulative differential snapshot based on the determination that an updated version of the security intent policy model should be deployed to a device and based on the one or more differential snapshots. When executed by one or more processors of the system, this set of instructions can cause the system to update a low-level security intent policy model associated with the device based on the cumulative differential snapshot. When executed by one or more processors of the system, this set of instructions can cause the system to generate device-level security configuration information for the device based on the low-level security intent policy model.

[0007] Some implementations described herein relate to a system. This system may include one or more memories and one or more processors. One or more processors may be configured to generate one or more differential snapshots, each indicating one or more incremental changes to a security intent policy model at a time following an initial time. One or more processors may be configured to determine an updated version of the security intent policy model to be deployed to a device. One or more processors may be configured to update a low-level security intent policy model associated with the device based on the determined updated version of the security intent policy model and based on at least some of the differential snapshots. One or more processors may be configured to generate device-level security configuration information for the device based on the low-level security intent policy model. Attached Figure Description

[0008] Figures 1A to 1F This is a diagram of one or more example implementations described in this article.

[0009] Figure 2 It is a diagram of an example environment in which the systems and / or methods described in this article can be implemented.

[0010] Figure 3 This is a diagram of example components of a device associated with efficient updates of device-level security configurations based on changes to the security intent policy model.

[0011] Figure 4 This is a diagram of example components of a device associated with efficient updates of device-level security configurations based on changes to the security intent policy model.

[0012] Figure 5 This is a flowchart of an example process associated with the efficient updating of device-level security configurations based on changes to the security intent policy model. Detailed Implementation

[0013] The following specific implementation of the example is illustrated in the accompanying drawings. The same reference numerals in different drawings may identify the same or similar elements.

[0014] Network management systems can generate device-level configuration information based on a security intent policy model (e.g., a security policy describing rules associated with security objects) and provide this information to network devices for deployment. However, in many cases, changes to the security intent policy model are made after the device-level configuration information has been deployed. Therefore, network devices may need to be updated to reflect changes in their device-level configuration information corresponding to these changes to the security intent policy model.

[0015] Generating and deploying different device-level configuration information based on an updated security intent policy model consumes the computing resources (e.g., processing resources, memory resources, communication resources, and / or power resources) of the network management system and network devices—resources that could otherwise be used for other tasks. This impacts the performance of the network management system and network devices. In some cases, the network management system can use a "snapshot" approach to track changes to the security intent policy model over various time periods since its inception. This allows the network management system to then generate and deploy device-level configuration information patches that only include changes to the security intent policy model since its inception. However, managing and storing all changes to the security intent policy model at different points in time requires additional computing resources (e.g., processing resources, memory resources, communication resources, and / or power resources). Furthermore, in many cases, the security intent policy model is constantly updated, so generating and deploying device-level configuration information patches that include changes since its inception often leads to excessive use of computing resources, such as when the current version of the device-level configuration information deployed on a network device only needs to be updated based on some recent changes to the security intent policy model.

[0016] Some implementations described herein provide a Network Management System (NMS). The NMS identifies a security intent policy model. A security intent policy model can be represented as a graph having multiple nodes connected by multiple edges. For example, a security intent policy model may include a policy node associated with a policy, one or more rule nodes associated with one or more rules of the policy, and one or more security object nodes associated with one or more rules of the policy. Each node includes information indicating, for example, a version indicator associated with that node and / or the time of that node's previous update. Additionally or alternatively, each of the one or more security object nodes includes information indicating the total number of rule nodes connected to the security object node and / or an identifier associated with each rule node connected to the security object node.

[0017] In some implementations, NMS generates one or more differential snapshots, each indicating one or more incremental changes to the security intent policy model at a time following an initial time associated with the security intent policy model (e.g., with one or more delete operations, one or more create operations, and / or one or more update operations). That is, each of the one or more differential snapshots indicates a change to the security intent policy model at a specific time since the time associated with the immediately preceding differential snapshot.

[0018] In some implementations, the NMS determines whether to deploy an updated version of the security intent policy model to the device (e.g., based on received messages). The NMS therefore determines the previous version of the security intent policy model deployed to the device and / or the previous deployment time of the previous version of the security intent policy model deployed to the device. Accordingly, the NMS identifies a set of one or more differential snapshots that were generated since the deployment of a previous version of the security intent policy model and / or since the previous deployment time, and generates a cumulative differential snapshot based on the set of one or more differential snapshots.

[0019] In some implementations, the NMS maintains a low-level security intent policy model associated with the device. For example, the low-level security intent policy model includes one or more security object nodes that were included in the security intent policy model (e.g., included in a previous version of the security intent policy model during a previous deployment). The NMS then updates the low-level security intent policy model based on cumulative differential snapshots. For example, the NMS may update the low-level security intent policy model to include one or more security object nodes that were included in the current version of the security intent policy model. Thus, the NMS generates and provides device-level security configuration information to the device (e.g., to enable the deployment of an updated version of the security intent policy model on the network device).

[0020] In this way, NMS enables efficient use of the computational resources (e.g., processing resources, memory resources, communication resources, and / or power resources) of both the NMS and the device. For example, by using differential snapshots to track incremental changes to the security intent policy model at a specific time, NMS uses fewer computational resources than a network management system that tracks the total changes to the security intent policy at a specific time. Furthermore, NMS can more efficiently generate and provide device-level security configuration information to the device, enabling the deployment of updated versions of the security intent policy model on the device. For example, fewer computational resources are used because only changes since the last deployment of device-level security configuration information are included in the device-level security configuration information, rather than all changes since the initial deployment. This also enables the rapid deployment (e.g., real-time or near real-time) of updated versions of the intent policy model on the device after a decision has been made to deploy an updated version on the device.

[0021] Figures 1A to 1F This is a diagram illustrating one or more example implementations of 100 described in this article. For example... Figures 1A to 1F As shown, (multiple) example implementations 100 may include NMS and network devices. The following section combines... Figures 2 to 4 A more detailed description of NMS and network devices. For example... Figures 1A to 1FAs shown, NMS may include a security intent policy model management module, a snapshot module, and a provisioning module.

[0022] like Figure 1A As shown by reference numeral 102 in the attached figure, the NMS (e.g., using a security intent policy model management module) can identify the security intent policy model. The security intent policy model can be a graph-based policy model, where security intent policy objects are represented as nodes and relationships between them are represented as edges, or it can be another type of intent-based model. For example, as... Figure 1A As shown, a security intent policy model can be represented as a graph with multiple nodes connected by multiple edges. The multiple nodes may include policy nodes associated with a policy (e.g., a security policy). The multiple nodes may include one or more rule nodes (e.g., each rule node is associated with a rule of the policy), which are connected to the policy node via one or more "has" edges (e.g., to indicate that the policy includes one or more rules). The multiple nodes may include one or more security object nodes (e.g., each security object node is associated with a security object of the policy), which are connected to one or more rule nodes via one or more "reference" edges (e.g., to indicate that one or more rules are applied to one or more security object nodes). As a concrete example, such as... Figure 1A As shown, the security intent policy model can be represented as a graph including the following: a policy node associated with policy A, a first rule node associated with rule 1 and a second rule node associated with rule 2, a first security object node associated with security object 1, a second security object node associated with security object 2, and a third security object node associated with security object 3. The policy node can be connected to the first rule node and the second rule node via corresponding edges. The first rule node can be connected to the first security object node and the second object node via corresponding reference edges, and the second rule node can be connected to the second security object node and the third object node via corresponding reference edges.

[0023] In some implementations, each node in the security intent policy model may include information. This information may indicate, for example, the node's name, an identifier associated with the node (e.g., a universally unique identifier (UUID) or another identifier associated with the node), the node's type (e.g., indicating whether the node is a policy node, rule node, security object node, or another type of node), a version indicator associated with the node, and / or the time of the node's previous update. Additionally or alternatively, each security object node may include, for example, information indicating the total number of rule nodes connected to the security object node and / or an identifier associated with each rule node connected to the security object node. For example, a first security object node (e.g., associated with security object 1) may include information indicating that the first security object node is associated with a rule node (a first rule node (e.g., associated with rule 1)); a second security object node (e.g., associated with security object 2) may include information indicating that the second security object node is associated with two rule nodes (a first rule node (e.g., associated with rule 1) and a second rule node (e.g., associated with rule 1)); and a third security object node (e.g., associated with security object 3) may include information indicating that the third security object node is associated with a rule node (a second rule node (e.g., associated with rule 2)).

[0024] like Figure 1B As shown by reference numeral 104 in the accompanying drawings, the NMS (e.g., using a snapshot module) can generate one or more differential snapshots. For example, the NMS can identify the initial time associated with the security intent policy model, such as the time when the NMS identifies the security intent policy model (e.g., as described herein regarding...). Figure 1A (As described by reference numeral 102 in the accompanying figure). The initial time can indicate a time when the security intent policy model has not yet changed (e.g., when the security intent policy model is a "basic" security intent policy model). The NMS can then generate one or more differential snapshots, each indicating one or more incremental changes to the security intent policy model after the initial time. For example, as... Figure 1B As shown, NMS can generate an initial differential snapshot (D0) indicating one or more first changes to the intent policy model from the initial time to the first time T1; it can generate a first differential snapshot (D1) indicating one or more changes to the intent policy model from the first time T1 to the second time T2; it can generate a second differential snapshot (D2) indicating one or more changes to the intent policy model from the second time T2 to the third time T3; and so on.

[0025] like Figure 1CAs shown by reference numeral 106 in the attached figure, the NMS (e.g., using a Security Intent Policy Model Management Module) can receive a message. This message can instruct the NMS to deploy an updated version of the Security Intent Policy Model to a device, such as a network device. For example, the NMS can receive the message from a network device or another device (e.g., a user device associated with the network device's administrator). Therefore, the NMS can determine that it wants to deploy an updated version of the Security Intent Policy Model to the device.

[0026] As indicated by reference numeral 108 in the accompanying drawings, the NMS (e.g., using a snapshot module) can determine (e.g., based on a message and / or determining that the NMS wants to deploy an updated version of the security intent policy model to the device) a previous version of the security intent policy model deployed by the NMS to the device, and / or the previous deployment time when the NMS deployed a previous version of the security intent policy model to the device. For example, the NMS can process (e.g., read and / or parse) a message to identify the device. The NMS can search for entries indicating a previous version and / or previous deployment time of the intent policy model in a data structure (e.g., a database, table, file, or another type of data structure) based on the identified device. The NMS can process (e.g., read and / or parse) this entry to determine the previous version and / or previous deployment time of the intent policy model.

[0027] like Figure 1D As shown by reference numeral 110, the NMS (e.g., using a snapshot module) can generate cumulative differential snapshots (e.g., based on one or more differential snapshots, a previous version of the security intent policy model, and / or a previous deployment time). In some implementations, the NMS can identify a set of one or more differential snapshots within one or more differential snapshots and can generate a cumulative differential snapshot based on this set of one or more differential snapshots, which has been generated since a previous version of the security intent policy model was deployed, such as since a previous deployment time. In this way, the cumulative differential snapshot can indicate one or more changes to the security intent policy model since a previous version of the security intent policy model and / or a previous deployment time (e.g., one or more changes associated with a time later than the previous deployment time).

[0028] In some implementations, the NMS (e.g., using a Security Intent Policy Model Management Module) can maintain a low-level security intent policy model associated with the device. The low-level security intent policy model may include one or more security object nodes. For example, the low-level security intent policy model may include one or more security object nodes included in the security intent policy model. That is, the low-level security intent policy model may include one or more security object nodes that were included in a previous version of the security intent policy model (e.g., at a previous deployment time). Therefore, each security object node in the low-level security intent policy model may include information indicating, for example, the name of the security object node, an identifier associated with the security object node, a version indicator associated with the security object node, the time of the security object node's previous update, the total number of rules associated with the security object node, and / or an identifier associated with each rule associated with the security object node.

[0029] like Figure 1E As shown by reference numeral 112, the NMS (e.g., using a snapshot module and / or a security intent policy model management module) can update the low-level security intent policy model associated with the device (e.g., based on cumulative deployment snapshots). In some implementations, the NMS can update the low-level security intent policy model to include one or more security object nodes that are included in the current version of the security intent policy model.

[0030] For example, to update a low-level security intent policy model, the NMS can identify deletion operations in the cumulative differential snapshot indicating security objects and rules (e.g., rules associated with security objects deleted from the security intent policy model). The NMS can then update information in the security object nodes associated with the security objects included in the low-level security intent policy model, such as by removing identifiers associated with rules, decrementing the total number of rules associated with the security object node, and / or updating the time of the previous update of the security object node (e.g., to the current time). As another example, the NMS can identify creation operations in the cumulative differential snapshot indicating security objects and rules (e.g., rules associated with security objects created in the security intent policy model). The NMS can then generate security object nodes associated with the security objects in the low-level security intent policy model and update information included in the security objects, such as by including identifiers associated with rules, setting the total number of rules associated with the security objects to one, and / or updating the time of the previous update of the security object nodes (e.g., to the current time). In an additional example, the NMS can identify update operations in the cumulative differential snapshot that indicate security objects and rules (e.g., rules associated with security objects updated in the security intent policy model). The NMS can therefore update information in the security object node associated with the security object in the low-level security intent policy model, such as by updating the identifier associated with the rule and / or updating the time of the previous update of the security object node (e.g., to the current time).

[0031] like Figure 1F As shown by reference numeral 114 in the attached figure, the NMS (e.g., using a provisioning module) can generate and provide device-level security configuration information for the device (e.g., based on a low-level security intent policy model, such as as described herein). Figure 1E (As described by reference numeral 112 in the attached figure). For example, the NMS can identify one or more security object nodes in a low-level security intent policy model that have been updated since a previous deployment time, and can generate device-level security configuration information for network devices based on these security object nodes (e.g., based on information related to the resources and capabilities of network devices accessible to the NMS). The NMS can send the device-level security configuration information to the network devices. The network devices can then process the device-level security configuration information to include one or more changes to the security intent policy model since the previous deployment time. In this way, providing device-level security configuration information allows an updated version of the security intent policy model to be deployed on the network devices.

[0032] In some implementations, such as after updating the low-level security intent policy model and / or generating and providing device-level security configuration information, the information in the security object nodes included in the low-level security intent policy model can indicate that the number of rules associated with the security object node is zero (e.g., based on one or more deletion operations included in a cumulative deployment snapshot). Therefore, the NMS (e.g., using a snapshot module and / or a security intent policy model management module) can remove security object nodes from the low-level security intent policy model. In this way, the NMS can make the low-level security intent policy model exclude one or more security object nodes not included in the current version of the security intent policy model, thus including only one or more security object nodes included in the current version of the security intent policy model.

[0033] As mentioned above, Figures 1A to 1F This is provided as one or more examples only. Other examples may differ from those provided. Figures 1A to 1F As described.

[0034] Figure 2 This is a diagram of an example environment 200 in which the systems and / or methods described in this paper can be implemented. (See diagram 200 for example.) Figure 2 As shown, environment 200 may include network management system 201, which may include one or more elements of cloud computing system 202 and / or may execute within cloud computing system 202. Cloud computing system 202 may include one or more elements 203 to 212, as described in more detail below. Figure 2 As further shown, environment 200 may include network 220 and / or network device 230. Devices and / or elements of environment 200 may be interconnected via wired and / or wireless connections.

[0035] The cloud computing system 202 may include computing hardware 203, a resource management component 204, a host operating system (OS) 205, and / or one or more virtual computing systems 206. The cloud computing system 202 may run on, for example, an Amazon Web Services platform, a Microsoft Azure platform, or a Snowflake platform. The resource management component 204 may perform virtualization (e.g., abstraction) of the computing hardware 203 to create one or more virtual computing systems 206. Using virtualization, the resource management component 204 enables a single computing device (e.g., a computer or server) to operate as multiple computing devices, such as by creating multiple isolated virtual computing systems 206 from the computing hardware 203 of a single computing device. In this way, the computing hardware 203 can operate more efficiently, with lower power consumption, higher reliability, higher availability, higher utilization, greater flexibility, and lower cost compared to using separate computing devices.

[0036] Computing hardware 203 may include hardware and corresponding resources from one or more computing devices. For example, computing hardware 203 may include hardware from a single computing device (e.g., a single server) or from multiple computing devices (e.g., multiple servers), such as multiple computing devices in one or more data centers. As shown, computing hardware 203 may include one or more processors 207, one or more memories 208, and / or one or more networking components 209. Examples of processors, memories, and networking components (e.g., communication components) are described elsewhere herein.

[0037] Resource management component 204 may include virtualization applications (e.g., executing on hardware, such as computing hardware 203) capable of virtualizing computing hardware 203 to start, stop, and / or manage one or more virtual computing systems 206. For example, resource management component 204 may include a hypervisor (e.g., a bare-metal or Type 1 hypervisor, a managed or Type 2 hypervisor, or another type of hypervisor) or a virtual machine monitor, such as when virtual computing system 206 is virtual machine 210. Alternatively or additionally, resource management component 204 may include a container manager, such as when virtual computing system 206 is container 211. In some implementations, resource management component 204 executes within and / or cooperates with host operating system 205.

[0038] Virtual computing system 206 may include a virtual environment that uses computing hardware 203 to implement cloud-based execution of the operations and / or processes described herein. As shown, virtual computing system 206 may include virtual machines 210, containers 211, or a hybrid environment 212 including virtual machines and containers, among other examples. Virtual computing system 206 may use a file system to execute one or more applications, which includes binaries, software libraries, and / or other resources required to execute the applications on a guest operating system (e.g., within virtual computing system 206) or host operating system 205.

[0039] Although the network management system 201 may include one or more components 203-212 of the cloud computing system 202, may execute within the cloud computing system 202, and / or may be hosted within the cloud computing system 202, in some implementations, the network management system 201 may not be cloud-based (e.g., may be implemented outside the cloud computing system) or may be partially cloud-based. For example, the network management system 201 may include one or more devices that are not part of the cloud computing system 202, such as... Figure 3 Equipment 300 or Figure 4The device 400 may include a standalone server or another type of computing device. The network management system 201 may perform one or more operations and / or processes, which are described in more detail elsewhere herein.

[0040] Network 220 may include one or more wired and / or wireless networks. For example, network 220 may include cellular networks, public land mobile networks (PLMNs), local area networks (LANs), wide area networks (WANs), private networks, the Internet, and / or combinations of these or other types of networks. Network 220 enables communication between devices in environment 200.

[0041] Network device 230 includes one or more devices capable of receiving, processing, storing, routing, and / or providing traffic (e.g., packets or other information or metadata) in the manner described herein. For example, network device 230 may include routers such as label switching routers (LSRs), label edge routers (LERs), ingress routers, egress routers, provider routers (e.g., provider edge routers or provider core routers), virtual routers, or other types of routers. Alternatively, network device 230 may include gateways, switches, firewalls, hubs, bridges, reverse proxies, servers (e.g., proxy servers, cloud servers, or data center servers), load balancers, and / or similar devices. In some implementations, network device 230 may be a physical device implemented within a enclosure (such as a chassis). In some implementations, network device 230 may be a virtual device implemented by one or more computer devices in a cloud computing environment or data center. In some implementations, a group of network devices 230 may be a group of data center nodes used to route traffic flows through network 220.

[0042] Figure 2 The number and arrangement of devices and networks shown are provided as examples. In reality, there may be different arrangements. Figure 2 The examples shown are compared to additional equipment and / or networks, fewer equipment and / or networks, different equipment and / or networks, or equipment and / or networks with different arrangements. Furthermore, Figure 2 The two or more devices shown can be implemented within a single device, or Figure 2 The single device shown can be implemented as multiple distributed devices. Alternatively, the set of devices in environment 200 (e.g., one or more devices) can perform one or more functions described as being performed by another set of devices in environment 200.

[0043] Figure 3This is a diagram of example components of device 300 associated with efficient updates of device-level security configurations based on changes to a security intent policy model. Device 300 may correspond to network management system 201, computing hardware 203, and / or network device 230. In some implementations, network management system 201, computing hardware 203, and / or network device 230 may include one or more devices 300 and / or one or more components of device 300. Figure 3 As shown, device 300 may include bus 310, processor 320, memory 330, input component 340, output component 350 and / or communication component 360.

[0044] Bus 310 may include one or more components that enable wired and / or wireless communication between components of device 300. Bus 310 can... Figure 3 Two or more components are coupled together, such as via operational coupling, communication coupling, electronic coupling, and / or electrical coupling. For example, bus 310 may include electrical connections (e.g., wires, traces, and / or leads) and / or wireless buses. Processor 320 may include a central processing unit, graphics processing unit, microprocessor, controller, microcontroller, digital signal processor, field-programmable gate array, application-specific integrated circuit, and / or another type of processing component. Processor 320 may be implemented in hardware, firmware, or a combination of hardware and software. In some implementations, processor 320 may include one or more processors capable of being programmed to perform one or more operations or processes described elsewhere herein.

[0045] Memory 330 may include volatile and / or non-volatile memory. For example, memory 330 may include random access memory (RAM), read-only memory (ROM), hard disk drive, and / or another type of memory (e.g., flash memory, magnetic storage, and / or optical storage). Memory 330 may include internal memory (e.g., RAM, ROM, or hard disk drive) and / or removable memory (e.g., removable via a universal serial bus). Memory 330 may be a non-transitory computer-readable medium. Memory 330 may store information related to the operation of device 300, one or more instructions, and / or software (e.g., one or more software applications). In some implementations, memory 330 may include one or more memories, such as those coupled (e.g., communicationally coupled) to one or more processors (e.g., processor 320) via bus 310. The communication coupling between processor 320 and memory 330 enables processor 320 to read and / or process information stored in memory 330 and / or store information in memory 330.

[0046] Input component 340 enables device 300 to receive input, such as user input and / or sensed input. For example, input component 340 may include a touchscreen, keyboard, keypad, mouse, button, microphone, switch, sensor, GPS sensor, accelerometer, gyroscope, and / or actuator. Output component 350 enables device 300 to provide output, such as via a display, speaker, and / or light-emitting diode. Communication component 360 enables device 300 to communicate with other devices via wired and / or wireless connections. For example, communication component 360 may include a receiver, transmitter, transceiver, modem, network interface card, and / or antenna.

[0047] Device 300 may perform one or more operations or procedures described herein. For example, a non-transitory computer-readable medium (e.g., memory 330) may store a set of instructions (e.g., one or more instructions or code) for execution by processor 320. Processor 320 may execute the set of instructions to perform one or more operations or procedures described herein. In some implementations, execution of the set of instructions by one or more processors 320 causes one or more processors 320 and / or device 300 to perform one or more operations or procedures described herein. In some implementations, hard-wired circuitry may be used in place of or in combination with instructions to perform one or more operations or procedures described herein. Additionally or alternatively, processor 320 may be configured to perform one or more operations or procedures described herein. Therefore, the implementations described herein are not limited to any particular combination of hardware circuitry and software.

[0048] Figure 3 The number and arrangement of components shown are provided as an example. Device 300 may include components with... Figure 3 The components shown are additional, fewer, different, or differently arranged compared to those in the diagram. Alternatively, the set of components of device 300 (e.g., one or more components) may perform one or more functions described as being performed by another set of components of device 300.

[0049] Figure 4 This is a diagram of example components of device 400 associated with efficient updates of device-level security configurations based on changes to the security intent policy model. Device 400 may correspond to network management system 201, computing hardware 203, and / or network device 230. In some implementations, network management system 201, computing hardware 203, and / or network device 230 may include one or more devices 400 and / or one or more components of device 400. Figure 4As shown, device 400 may include one or more input components 410-1 to 410-B (B≥1) (hereinafter collectively referred to as input components 410, and individually referred to as input components 410), switching component 420, one or more output components 430-1 to 430-C (C≥1) (hereinafter collectively referred to as output components 430, and individually referred to as output components 430), and controller 440.

[0050] Input component 410 may be one or more attachment points for a physical link and one or more entry points for incoming traffic (such as packets). Input component 410 may process incoming traffic, such as by performing data link layer encapsulation or decapsulation. In some implementations, input component 410 may transmit and / or receive packets. In some implementations, input component 410 may include an input line card that includes one or more packet processing components (e.g., in the form of integrated circuits), such as one or more interface cards (IFCs), packet forwarding components, line card controller components, input ports, processors, memory, and / or input queues. In some implementations, device 400 may include one or more input components 410.

[0051] Switching component 420 interconnects input component 410 with output component 430. In some implementations, switching component 420 may be implemented via one or more crossbar switches, via a bus, and / or using shared memory. Shared memory may act as a temporary buffer to store packets from input component 410 before they are ultimately scheduled for transmission to output component 430. In some implementations, switching component 420 enables input component 410, output component 430, and / or controller 440 to communicate with each other.

[0052] Output component 430 can store packets and schedule packets for transmission on the output physical link. Output component 430 can support data link layer encapsulation or decapsulation, and / or various higher-level protocols. In some implementations, output component 430 can transmit and / or receive packets. In some implementations, output component 430 may include an output line card that includes one or more packet processing components (e.g., in the form of integrated circuits), such as one or more IFCs, packet forwarding components, line card controller components, output ports, processors, memory, and / or output queues. In some implementations, device 400 may include one or more output components 430. In some implementations, input component 410 and output component 430 may be implemented from the same set of components (e.g., and the input / output component may be a combination of input component 410 and output component 430).

[0053] Controller 440 includes processors in the form of, for example, a CPU, a graphics processing unit (GPU), an accelerated processing unit (APU), a microprocessor, a microcontroller, a digital signal processor (DSP), a field-programmable gate array (FPGA), an application-specific integrated circuit (ASIC), and / or another type of processor. The processor is implemented in hardware, firmware, or a combination of hardware and software. In some implementations, controller 440 may include one or more processors that can be programmed to perform functions.

[0054] In some implementations, controller 440 may include RAM, ROM and / or another type of dynamic or static storage device (e.g., flash memory, magnetic storage, optical storage, etc.) for storing information and / or instructions for use by controller 440.

[0055] In some implementations, controller 440 can communicate with other devices, networks, and / or systems connected to device 400 to exchange information about the network topology. Controller 440 can create routing tables based on the network topology information, create forwarding tables based on the routing tables, and forward the forwarding tables to input component 410 and / or output component 430. Input component 410 and / or output component 430 can use the forwarding tables to perform route looks for incoming and / or outgoing packets.

[0056] Controller 440 may execute one or more processes described herein. Controller 440 may execute these processes in response to executing software instructions stored on a non-transitory computer-readable medium. A computer-readable medium is defined herein as a non-transitory memory device. A memory device includes memory space within a single physical storage device or memory space distributed across multiple physical storage devices.

[0057] Software instructions may be read from another computer-readable medium or from another device into the memory and / or storage components associated with controller 440 via a communication interface. When executed, the software instructions stored in the memory and / or storage components associated with controller 440 may cause controller 440 to perform one or more processes described herein. Alternatively or additionally, hardwired circuitry may be used in place of or in combination with the software instructions to perform one or more processes described herein. Therefore, the implementations described herein are not limited to any particular combination of hardware circuitry and software.

[0058] Figure 4 The number and arrangement of components shown are provided as an example. In practice, device 400 may include components with... Figure 4The components shown are additional, fewer, different, or differently arranged compared to those in the diagram. Alternatively, the set of components of device 400 (e.g., one or more components) may perform one or more functions described as being performed by another set of components of device 400.

[0059] Figure 5 This is a flowchart of an example process 500 associated with the efficient updating of device-level security configurations based on changes to the security intent policy model. In some implementations, Figure 5 One or more process frames are executed by the system (e.g., network management system 201). In some implementations, Figure 5 One or more process frames are executed by another device or group of devices that are separate from or include the system, such as a network device (e.g., network device 230). Alternatively, Figure 5 One or more process frames may be executed by one or more components of device 300, such as processor 320, memory 330, input component 340, output component 350 and / or communication component 360; one or more components of device 400, such as input component 410, switching component 420, output component 430 and / or controller 440; and / or one or more components of another device.

[0060] like Figure 5 As shown, process 500 may include identifying a security intent policy model associated with the initial time (block 510). For example, the system may identify a security intent policy model associated with the initial time, as described above.

[0061] like Figure 5 As further shown, process 500 may include generating one or more differential snapshots, each indicating one or more incremental changes to the security intent policy model at a time after the initial time (box 520). For example, the system may generate one or more differential snapshots, each indicating one or more incremental changes to the security intent policy model at a time after the initial time, as described above.

[0062] like Figure 5 As further shown, process 500 may include determining that the system needs to deploy an updated version of the security intent policy model to the device (box 530). For example, the system may determine that it needs to deploy an updated version of the security intent policy model to the device, as described above.

[0063] like Figure 5As further shown, process 500 may include determining the previous deployment time (box 540) of a previous version of the security intent policy model deployed to the device based on determining that an updated version of the security intent policy model to be deployed by the system. For example, the system may determine the previous deployment time of a previous version of the security intent policy model deployed to the device based on determining that an updated version of the security intent policy model to be deployed by the system, as described above.

[0064] like Figure 5 As further shown, process 500 may include generating a cumulative differential snapshot based on one or more differential snapshots and previous deployment times (box 550). For example, the system may generate a cumulative differential snapshot based on one or more differential snapshots and previous deployment times, as described above.

[0065] like Figure 5 As further shown, process 500 may include updating the low-level security intent policy model associated with the device based on a cumulative differential snapshot (box 560). For example, the system may update the low-level security intent policy model associated with the device based on a cumulative differential snapshot, as described above.

[0066] like Figure 5 As further shown, process 500 may include generating device-level security configuration information for the device based on a low-level security intent policy model (box 570). For example, the system may generate device-level security configuration information for the device based on a low-level security intent policy model, as described above.

[0067] Process 500 may include additional implementations, such as any single implementation or any combination of implementations of one or more other processes described below and / or elsewhere herein.

[0068] In the first implementation, the security intent policy model is represented as a graph having multiple nodes connected by multiple edges, wherein the multiple nodes include policy nodes associated with a policy, and the multiple nodes include one or more rule nodes connected to the policy nodes via one or more of the multiple edges having an edge, wherein each rule node is associated with a rule of the policy, and the multiple nodes include one or more security object nodes connected to the one or more rule nodes via one or more of the multiple edges having a reference edge, wherein each security object node is associated with a security object of the policy.

[0069] In the second implementation, either alone or in combination with the first implementation, each of the multiple nodes in the security intent policy model includes information indicating at least one of the following: the name of the node, the identifier associated with the node, the type of the node, the version indicator associated with the node, or the time of the node's previous update.

[0070] In the third implementation, either alone or in combination with one or more implementations in the first and second implementations, each of the one or more security object nodes includes information indicating at least one of the following: the total number of rule nodes connected to the security object node in the one or more rule nodes, or an identifier associated with each rule node connected to the security object node.

[0071] In the fourth implementation, either alone or in combination with one or more of the first to third implementations, the low-level security intent policy model includes one or more security object nodes, wherein each security object node includes information indicating at least one of the following: the name of the security object node, the type of the security object node, the identifier associated with the security object node, the version indicator associated with the security object node, the time of the previous update of the security object node, the total number of rules associated with the security object node, or the identifier associated with each rule associated with the security object node.

[0072] In the fifth implementation, either alone or in combination with one or more of the first to fourth implementations, updating the low-level security intent policy model includes identifying deletion operations of indicated security objects and rules in the cumulative differential snapshot, and updating the information included in the security object node associated with the security object in the low-level security intent policy model by: removing the identifier associated with the rule, decrementing the total number of rules associated with the security object node by one, and updating the time of the previous update of the security object node.

[0073] In the sixth implementation, either alone or in combination with one or more of the first to fifth implementations, updating the low-level security intent policy model includes identifying the creation operations of indicated security objects and rules in the cumulative differential snapshot, generating security object nodes associated with security objects in the low-level security intent policy model, and updating the information included in the security object nodes by: including the identifier associated with the rules, setting the total number of rules associated with the security object node to one, and updating the time of the previous update of the security object node.

[0074] In the seventh implementation, either alone or in combination with one or more of the first through sixth implementations, updating the low-level security intent policy model includes identifying update operations that indicate security objects and rules in the cumulative differential snapshot, and updating information included in the security object node associated with the security object in the low-level security intent policy model by updating the identifier associated with the rule and updating the time of the previous update of the security object node.

[0075] In the eighth implementation, generating device-level security configuration information for the device, either alone or in combination with one or more of the first to seventh implementations, includes: representing one or more security object nodes in the low-level security intent policy model that have been updated since the previous deployment time, and generating device-level provisioning configuration information based on one or more security object nodes.

[0076] In the ninth implementation, alone or in combination with one or more of the first to eighth implementations, process 500 includes providing device-level security configuration information to the device, wherein providing device-level security configuration information allows an updated version of the security intent policy model to be deployed on the device.

[0077] although Figure 5 An example box of process 500 is shown, but in some implementations, process 500 includes... Figure 5 The additional boxes, fewer boxes, different boxes, or boxes with different arrangements depicted in the diagram. Alternatively, two or more boxes in process 500 can be executed in parallel.

[0078] The foregoing disclosure provides illustrations and descriptions, but is not intended to be exhaustive or to limit implementations to the precise forms disclosed. Modifications and changes can be made based on the foregoing disclosure, or can be derived from the practice of implementation.

[0079] As used herein, the term "component" is intended to be broadly interpreted as hardware, firmware, or a combination of hardware and software. It will be apparent that the systems and / or methods described herein can be implemented in various forms of hardware, firmware, and / or combinations of hardware and software. The actual dedicated control hardware or software code used to implement these systems and / or methods is not limited in its implementation. Therefore, the operation and behavior of the systems and / or methods are described herein without reference to specific software code—it should be understood that software and hardware can be used to implement the systems and / or methods based on the description herein.

[0080] Although specific combinations of features are described in the claims and / or disclosed in the specification, these combinations are not intended to limit the disclosure of various implementations. In fact, many of these features can be combined in ways not specifically described in the claims and / or disclosed in the specification. Although each dependent claim listed below may directly depend on one claim, the disclosure of various implementations includes combinations of each dependent claim with each other claim in the claim set. As used herein, the phrase “at least one” in the list of items refers to any combination of those items, including single members. For example, “at least one of the following: a, b, or c” is intended to cover a, b, c, ab, ac, bc, and abc, as well as any combination having multiple identical items.

[0081] Unless explicitly stated otherwise, no element, action, or instruction used herein should be construed as critical or necessary. Furthermore, as used herein, the articles “a” and “an” are intended to include one or more items and are interchangeable with “one or more.” Furthermore, as used herein, the article “the” is intended to include one or more items referenced in connection with the article “the” and is interchangeable with “the one or more.” Furthermore, as used herein, the term “collection” is intended to include one or more items (e.g., related items, unrelated items, or a combination of related and unrelated items) and is interchangeable with “one or more.” In cases involving only one item, the phrase “only one” or similar language is used. Furthermore, as used herein, the terms “has,” “have,” “having,” etc., are intended to be open-ended terms. Furthermore, unless explicitly stated otherwise, the phrase “based on” is intended to mean “at least partially based on.” Furthermore, as used herein, the term “or” is intended to be included when used in a series and may be used interchangeably with “and / or” unless otherwise expressly stated (e.g., if used in combination with “any” or “only one of them”).

[0082] Example 1. A method comprising: identifying a security intent policy model associated with an initial time by a system; generating one or more differential snapshots by the system, each differential snapshot indicating one or more incremental changes to the security intent policy model at a time after the initial time; determining, by the system, an updated version of the security intent policy model to be deployed to a device; determining, by the system, a previous deployment time when a previous version of the security intent policy model was deployed to the device, based on the determination of the updated version of the security intent policy model to be deployed; generating a cumulative differential snapshot by the system based on the one or more differential snapshots and the previous deployment time; updating a low-level security intent policy model associated with the device by the system based on the cumulative differential snapshot; and generating device-level security configuration information for the device by the system based on the low-level security intent policy model.

[0083] Example 2. The method of Example 1, wherein the security intent policy model is represented as a graph having multiple nodes connected by multiple edges, wherein: the multiple nodes include policy nodes associated with a policy; and the multiple nodes include one or more rule nodes connected to the policy nodes via one or more edges of the multiple edges, wherein each rule node is associated with a rule of the policy, and the multiple nodes include one or more security object nodes connected to one or more rule nodes via one or more reference edges of the multiple edges, wherein each security object node is associated with a security object of the policy.

[0084] Example 3. The method of Example 2, wherein each of the multiple nodes in the security intent policy model includes information indicating at least one of the following: the name of the node, the identifier associated with the node, the type of the node, the version indicator associated with the node, or the time of the node's previous update.

[0085] Example 4. The method of Example 2, wherein each of one or more security object nodes includes information indicating at least one of the following: the total number of rule nodes connected to the security object node in one or more rule nodes, or an identifier associated with each rule node connected to the security object node.

[0086] Example 5. The method of Example 1, wherein the low-level security intent policy model includes one or more security object nodes, wherein each security object node includes information indicating at least one of the following: the name of the security object node, the type of the security object node, the identifier associated with the security object node, the version indicator associated with the security object node, the time of the previous update of the security object node, the total number of rules associated with the security object node, or the identifier associated with each rule associated with the security object node.

[0087] Example 6. The method of Example 1, wherein updating the low-level security intent policy model includes: identifying the deletion operation of the indication security object and rule in the cumulative differential snapshot; and updating the information included in the security object node associated with the security object in the low-level security intent policy model by: removing the identifier associated with the rule, decrementing the total number of rules associated with the security object node by one, and updating the time of the previous update of the security object node.

[0088] Example 7. The method of Example 1, wherein updating the low-level security intent policy model includes: identifying the creation operations of the indicated security objects and rules in the cumulative differential snapshot; generating a security object node associated with the security object in the low-level security intent policy model; and updating the information included in the security object node by including the identifier associated with the rule, setting the total number of rules associated with the security object node to one, and updating the time of the previous update of the security object node.

[0089] Example 8. The method of Example 1, wherein updating the low-level security intent policy model includes: identifying update operations that indicate security objects and rules in the cumulative differential snapshot; and updating information included in the security object node associated with the security object in the low-level security intent policy model by: updating the identifier associated with the rule, and updating the time of the previous update of the security object node.

[0090] Example 9. The method of Example 1, wherein generating device-level security configuration information for a device includes: identifying one or more security object nodes in a low-level security intent policy model that have been updated since the previous deployment time; and generating device-level provisioning configuration information based on one or more security object nodes.

[0091] Example 10. The method of Example 1 further includes: providing device-level security configuration information to the device, wherein providing device-level security configuration information allows an updated version of the security intent policy model to be deployed on the device.

[0092] Example 11. A non-transitory computer-readable medium storing a set of instructions, the set of instructions comprising: one or more instructions, which, when executed by one or more processors of the system, cause the system to: generate one or more differential snapshots, the one or more differential snapshots respectively indicating one or more incremental changes to a security intent policy model at a time after an initial time; determine that the system should deploy an updated version of the security intent policy model to a device; based on the determination that the system should deploy an updated version of the security intent policy model to the device and based on the one or more differential snapshots, generate a cumulative differential snapshot; update a low-level security intent policy model associated with the device based on the cumulative differential snapshot; and generate device-level security configuration information for the device based on the low-level security intent policy model.

[0093] Example 12. The non-transitory computer-readable medium of Example 11, wherein one or more instructions that cause the system to generate a cumulative differential snapshot cause the system to: determine a previous deployment time when the system deployed a previous version of the security intent policy model to the device based on determining that an updated version of the security intent policy model to be deployed by the system; identify a set of one or more differential snapshots generated since the previous deployment time; and generate a cumulative differential snapshot based on the set of one or more differential snapshots.

[0094] Example 13. The non-transitory computer-readable medium of Example 11, wherein one or more instructions that cause the system to update a low-level security intent policy model cause the system to: identify deletion operations of indications of security objects and rules in a cumulative differential snapshot; and update information included in security object nodes associated with security objects in the low-level security intent policy model by: removing identifiers associated with rules, decrementing the total number of rules associated with security object nodes by one, and updating the time of previous updates of security object nodes.

[0095] Example 14. The non-transitory computer-readable medium of Example 11, wherein one or more instructions causing the system to update a low-level security intent policy model cause the system to: identify the creation operation of the indication security object and rule in the cumulative differential snapshot; generate a security object node associated with the security object in the low-level security intent policy model; and update the information included in the security object by: including the identifier associated with the rule, setting the total number of rules associated with the security object node to one, and updating the time of the previous update of the security object node.

[0096] Example 15. A nontransitory computer-readable medium of Example 11, wherein one or more instructions that cause the system to update a low-level security intent policy model cause the system to: identify update operations indicating security objects and rules in a cumulative differential snapshot; and update information included in security object nodes associated with security objects in the low-level security intent policy model by: updating identifiers associated with rules, and updating the time of previous updates of security object nodes.

[0097] Example 16. The nontransitory computer-readable medium of Example 11, wherein one or more instructions that cause the system to generate device-level security configuration information for a device cause the system to: generate device-level security configuration information based on one or more security object nodes in a low-level security intent policy model, the one or more security object nodes having been updated since a previous version of the security intent policy model was deployed to the device at a previous deployment time.

[0098] Example 17. The nontransitory computer-readable medium of Example 11, wherein one or more instructions further cause the system to: provide device-level security configuration information to the device, wherein providing device-level security configuration information allows an updated version of the security intent policy model to be deployed on the device.

[0099] Example 18. A system comprising: one or more memories; and one or more processors: generating one or more differential snapshots, each of the one or more differential snapshots indicating one or more incremental changes to a security intent policy model at a time following an initial time; determining that the system should deploy an updated version of the security intent policy model to a device; updating a low-level security intent policy model associated with the device based on the determination that the system should deploy the updated version of the security intent policy model and based on at least some of the one or more differential snapshots; and generating device-level security configuration information for the device based on the low-level security intent policy model.

[0100] Example 19. The system of Example 18, wherein one or more processors, in order to update a low-level security intent policy model,: determine a previous deployment time when the system deployed a previous version of the security intent policy model to the device, based on determining that the system should deploy an updated version of the security intent policy model; generate a cumulative differential snapshot based on one or more differential snapshots and the previous deployment time; and update the low-level security intent policy model associated with the device based on the cumulative differential snapshot.

[0101] Example 20. The system of Example 18, wherein one or more processors further: provide device-level security configuration information to the device, wherein providing device-level security configuration information allows an updated version of the security intent policy model to be deployed on the device.

Claims

1. A method comprising: A security intent policy model that associates system identifiers with initial time; The system generates one or more differential snapshots, each of which indicates one or more incremental changes to the security intent policy model over a time after the initial time. The system determines whether to deploy an updated version of the security intent policy model to the device; The system determines the previous deployment time when it deployed the previous version of the security intent policy model to the device based on the updated version of the security intent policy model that it needs to deploy. The system generates a cumulative differential snapshot based on the one or more differential snapshots and the previous deployment time; The system updates the low-level security intent policy model associated with the device based on the cumulative differential snapshot; as well as The system generates device-level security configuration information for the device based on the low-level security intent policy model.

2. The method of claim 1, wherein the security intent policy model is represented as a graph having multiple nodes connected by multiple edges, wherein: The plurality of nodes includes policy nodes associated with the policy; and The plurality of nodes includes one or more rule nodes, which are connected to the policy node via one or more of the plurality of edges. Each rule node is associated with a rule of the policy, and The plurality of nodes includes one or more security object nodes, which are connected to the one or more rule nodes via one or more reference edges among the plurality of edges. Each security object node is associated with a security object of the policy.

3. The method of claim 2, wherein each of the plurality of nodes of the security intent policy model includes information indicating at least one of the following: The name of the node, The identifier associated with the node. The type of the node, The version indicator associated with the node, or The time of the previous update of the node.

4. The method of claim 2, wherein each of the one or more security object nodes includes information indicating at least one of the following: The total number of rule nodes connected to the security object node in the one or more rule nodes, or An identifier associated with each rule node connected to the security object node.

5. The method according to claim 1, wherein the low-level security intent policy model includes one or more security object nodes. Each security object node includes information indicating at least one of the following: The name of the security object node, The type of the security object node, The identifier associated with the security object node, The version indicator associated with the security object node, The previous update time of the security object node, The total number of rules associated with the security object node, or An identifier associated with each rule associated with the security object node.

6. The method of claim 1, wherein updating the low-level security intent policy model comprises: Identify the deletion operations of the indicated security objects and rules in the cumulative differential snapshot; as well as The information included in the security object node associated with the security object in the low-level security intent policy model is updated as follows: Remove the identifier associated with the rule. Subtract one from the total number of rules associated with the security object node, and Update the time of the previous update of the security object node.

7. The method of claim 1, wherein updating the low-level security intent policy model comprises: Identify the creation operations of the indicated security objects and rules in the cumulative differential snapshot; In the low-level security intent policy model, a security object node associated with the security object is generated; as well as The information included in the security object node is updated as follows: This includes identifiers associated with the rules. Set the total number of rules associated with the security object node to one, and Update the time of the previous update of the security object node.

8. The method of claim 1, wherein updating the low-level security intent policy model comprises: Identify the update operations of the indicated security objects and rules in the cumulative differential snapshot; as well as The information included in the security object node associated with the security object in the low-level security intent policy model is updated as follows: Update the identifier associated with the rule, and Update the time of the previous update of the security object node.

9. The method of claim 1, wherein generating the device-level security configuration information for the device comprises: Identify one or more security object nodes in the low-level security intent policy model that have been updated since the previous deployment time; as well as Device-level provisioning configuration information is generated based on the one or more security object nodes.

10. The method according to claim 1, further comprising: Provide the device-level security configuration information to the device. The provision of the device-level security configuration information allows the updated version of the security intent policy model to be deployed on the device.

11. A non-transitory computer-readable medium storing a set of instructions, the set of instructions comprising: One or more instructions, which, when executed by one or more processors of the system, cause the system to: Generate one or more differential snapshots, each of which indicates one or more incremental changes to the security intent policy model over a time period after the initial time. Determine whether the system needs to deploy an updated version of the security intent policy model to the device; Based on determining that the system needs to deploy the updated version of the security intent policy model to the device, and based on the one or more differential snapshots, a cumulative differential snapshot is generated; The low-level security intent policy model associated with the device is updated based on the cumulative differential snapshot; and Based on the low-level security intent policy model, device-level security configuration information for the device is generated.

12. The non-transitory computer-readable medium of claim 11, wherein the one or more instructions that cause the system to generate the cumulative differential snapshot cause the system to: Based on determining that the system needs to deploy the updated version of the security intent policy model, the previous deployment time when the system deployed the previous version of the security intent policy model to the device is determined; Identify a set of one or more differential snapshots generated since the previous deployment time; as well as The cumulative differential snapshot is generated based on the set of one or more differential snapshots.

13. The non-transitory computer-readable medium of claim 11, wherein the one or more instructions causing the system to update the low-level security intent policy model cause the system to: Identify the deletion operations of the indicated security objects and rules in the cumulative differential snapshot; and The information included in the security object node associated with the security object in the low-level security intent policy model is updated as follows: Remove the identifier associated with the rule. Subtract one from the total number of rules associated with the security object node, and Update the time of the previous update of the security object node.

14. The non-transitory computer-readable medium of claim 11, wherein the one or more instructions causing the system to update the low-level security intent policy model cause the system to: Identify the creation operations of the indicated security objects and rules in the cumulative differential snapshot; In the low-level security intent policy model, a security object node associated with the security object is generated; as well as The information included in the security object is updated as follows: This includes identifiers associated with the rules. Set the total number of rules associated with the security object node to one, and Update the time of the previous update of the security object node.

15. The non-transitory computer-readable medium of claim 11, wherein the one or more instructions causing the system to update the low-level security intent policy model cause the system to: Identify the update operations of the indicated security objects and rules in the cumulative differential snapshot; and The information included in the security object node associated with the security object in the low-level security intent policy model is updated as follows: Update the identifier associated with the rule, and Update the time of the previous update of the security object node.

16. The non-transitory computer-readable medium of claim 11, wherein the one or more instructions that cause the system to generate the device-level security configuration information for the device cause the system to: The device-level security configuration information is generated based on one or more security object nodes in the low-level security intent policy model, wherein the one or more security object nodes have been updated since the previous deployment time when the previous version of the security intent policy model was deployed to the device.

17. The non-transitory computer-readable medium of claim 11, wherein one or more instructions further cause the system to: Provide the device-level security configuration information to the device. The provision of the device-level security configuration information allows the updated version of the security intent policy model to be deployed on the device.

18. A system comprising: One or more memory units; as well as One or more processors: Generate one or more differential snapshots, each of which indicates one or more incremental changes to the security intent policy model over a time period after the initial time. Determine whether the system needs to deploy an updated version of the security intent policy model to the device; Based on the determination that the system needs to deploy the updated version of the security intent policy model, and based on at least some of the differential snapshots from the one or more differential snapshots, update the low-level security intent policy model associated with the device; and Based on the low-level security intent policy model, device-level security configuration information for the device is generated.

19. The system of claim 18, wherein the one or more processors update the low-level security intent policy model by: Based on determining that the system needs to deploy the updated version of the security intent policy model, the previous deployment time when the system deployed the previous version of the security intent policy model to the device is determined; A cumulative differential snapshot is generated based on the one or more differential snapshots and the previous deployment time; as well as Based on the cumulative differential snapshot, update the low-level security intent policy model associated with the device.

20. The system of claim 18, wherein the one or more processors further: Provide the device-level security configuration information to the device. The provision of the device-level security configuration information allows the updated version of the security intent policy model to be deployed on the device.

Images