Self learning firewall policy enforcer
US-2024179158-A1 · May 30, 2024 · US
US12542817B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-12542817-B2 |
| Application number | US-202418620711-A |
| Country | US |
| Kind code | B2 |
| Filing date | Mar 28, 2024 |
| Priority date | Apr 24, 2023 |
| Publication date | Feb 3, 2026 |
| Grant date | Feb 3, 2026 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
Zero trust and micro-segmentation techniques may be collectively used to enhance network security. To establish, refine, and enforce a zero-trust least-privileged policy, the network may be segmented to put each device of the network into a respective network of one, which forces all network traffic to pass through a zero-trust gatekeeper. The gatekeeper may then monitor and analyze the traffic to establish, refine, and enforce the zero-trust least-privileged policy, which reduces network access to only a limited set of network actions and/or paths. Using the gatekeeper, network traffic may be monitored to progressively establish the policy as well as to continually refine the policy. Recommended actions may be determined based on the analysis of the monitored network traffic and provided to the user to allow user feedback on the communication rules of zero-trust policy.
Opening claim text (preview).
We claim: 1 . A zero-trust microsegmentation method comprising: collecting information associated with devices of a network, each device being a respective atomic network configured to cause all device traffic to traverse a gatekeeper associated with the devices; determining, based on the collected information, network microsegments each configured to include one or more of the devices; determining a zero-trust security policy in which communication permissions for the devices of the network are denied by default unless otherwise allowed, the communication permissions including one or more communication dimensions; and iteratively performing: analyzing network traffic under the zero-trust security policy; adapting the zero-trust security policy, based on the analysis of the network traffic, to adjust the communication permissions for the one or more communication dimensions to include one or more modifications to the one or more communication dimensions; and implementing the zero-trust security policy, including one or more modifications to one or more communication dimensions. 2 . The method of claim 1 , wherein the one or more communication dimensions include an internet-intranet dimension defining a restrictiveness distinction between internet traffic and intranet traffic. 3 . The method of claim 1 , wherein the one or more communication dimensions include an input-output dimension defining a restrictiveness distinction between input traffic and output traffic. 4 . The method of claim 1 , wherein the one or more communication dimensions include a segment dimension defining a restrictiveness distinction between inter-segment traffic and intra-segment traffic. 5 . The method of claim 1 , wherein the one or more communication dimensions include: a port dimension defining a port-based traffic restrictiveness distinction; and/or a path dimension defining a communication path-based traffic restrictiveness distinction. 6 . The method of claim 1 , wherein the one or more communication dimensions include: a user dimension defining a user-based traffic restrictiveness distinction; a user group-based traffic restrictiveness distinction; an inter-group dimension defining an inter-group traffic restrictiveness distinction; and/or an intra-group dimension defining an intra-group traffic restrictiveness distinction. 7 . The method of claim 1 , wherein the one or more communication dimensions include an application dimension defining an application-based traffic restrictiveness distinction. 8 . The method of claim 1 , wherein each of the respective atomic networks are networks of one. 9 . The method of claim 1 , wherein establishing each device as a respective network-of-one comprises: assigning an individualized subnet to each device, wherein the individualized subnets cause all of the device traffic to traverse the gatekeeper. 10 . The method of claim 8 , wherein the gatekeeper is configured as a default gateway for the devices. 11 . The method of claim 9 , wherein assigning the individualized subnet comprises assigning a /32 subnet or a 255.255.255.255 subnet mask to each device. 12 . A zero-trust microsegmentation method comprising: collecting information associated with devices of a network, each device being a respective individual network configured to cause all device traffic to traverse a network device common to and associated with the devices; determining, based on the collected information, network microsegments that each include one or more of the devices within the respective individual network; determining a zero-trust security policy including communication permissions; and iteratively performing: analyzing network traffic under the communication permissions of the zero-trust security policy; and adapting one or more of the communication permissions, based on the analysis of the network traffic, to provide the zero-trust security policy including the one or more adapted communication permissions. 13 . The method of claim 12 , wherein the zero-trust security policy is configured to deny network traffic for the devices of the network by default unless otherwise allowed. 14 . The method of claim 12 , wherein adapting the one or more of the communication permissions comprises removing the one or more of the communication permissions from the zero-trust security policy. 15 . The method of claim 12 , further comprising determining a suggested modification the one or more of the communication permissions based on the analysis of the network traffic. 16 . The method of claim 12 , wherein adapting one or more of the communication permissions comprises modifying a communication dimension of the zero-trust security policy. 17 . The method of claim 12 , wherein the network device is a gatekeeper configured as a default gateway for the devices, the method further comprising enforcing, by the gatekeeper, the zero-trust security policy on the device traffic traversing the gatekeeper. 18 . The method of claim 15 , wherein the adapting the one or more of the communication permissions is based on feedback responsive to the suggested modification. 19 . The method of claim 17 , wherein collecting information associated with the devices comprises analyzing, by the gatekeeper, the device traffic traversing the gatekeeper to collect the information associated with the devices. 20 . The method of claim 18 , wherein the feedback comprises acceptance or rejection of the suggested modification.
Traffic logging, e.g. anomaly detection · CPC title
Rule management · CPC title
for managing network security; network security policies in general (filtering policies H04L63/0227) · CPC title
Filtering policies (mail message filtering H04L51/212) · CPC title
involving negotiation or determination of the one or more network security mechanisms to be used, e.g. by negotiation between the client and the server or between peers or by selection according to the capabilities of the entities involved (negotiation of communication capabilities H04L69/24) · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.