# US 2025/0097200 A1 · User space firewall manager

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2025/0097200 A1
- Document ID: US20250097200A1
- Status: Published application
- Kind: A1
- Application number: 18/532,287
- Filed: 2023-12-07
- Published: 2025-03-20
- Earliest claimed: 2023-09-14
- Assignees: McAfee, Inc.
- Applicants: McAfee, LLC
- Inventors: Li Xiao; Douglas Richard Bell
- Web page: https://patentgrep.com/patent/US20250097200A1

## CPC

- H04L 63/0263: {Rule management}
- H04L 63/0236: {Filtering by address, protocol, port number or service, e.g. IP-address or URL}
- H04L 63/1466: {Active attacks involving interception, injection, modification, spoofing of data unit addresses, e.g. hijacking, packet injection or TCP sequence number attacks}
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

There is disclosed herein a computer-implemented software system and method. The method is to execute within a non-kernel space of a host computer and includes asynchronously monitoring network activity of network-enabled applications of the host computer. Responsive to the monitoring, and based on network behavior of a userspace application, the software creates one or more firewall rules for a kernel-mode firewall and causes the kernel-mode firewall to enforce the one more firewall rules.

## Claims

### Claim at position 1

1-63. (canceled)

### Claim 64

One or more tangible, non-transitory computer-readable storage media having stored thereon executable instructions to provide a security application, the security application to:
within a non-kernel space, asynchronously monitor network activity of a network-enabled application;
based on the asynchronous monitoring, create one or more firewall rules for a kernel-mode firewall; and
cause the kernel-mode firewall to enforce the one more firewall rules.

### Claim 65 (depends on 64)

The one or more tangible, non-transitory computer-readable media of claim 64, wherein the non-kernel space is userspace.

### Claim 66 (depends on 64)

The one or more tangible, non-transitory computer-readable media of claim 64, wherein the kernel-mode firewall is an operating system native firewall or third-party firewall.

### Claim 67 (depends on 64)

The one or more tangible, non-transitory computer-readable media of claim 64, wherein the security application is not tightly integrated with the kernel-mode firewall.

### Claim 68 (depends on 67)

The one or more tangible, non-transitory computer-readable media of claim 67, wherein the security application is sourced from a vendor different from a vendor that sourced the kernel-mode firewall.

### Claim 69 (depends on 67)

The one or more tangible, non-transitory computer-readable media of claim 67, wherein the security application communicates with the kernel-mode firewall only via a published interface definition.

### Claim 70 (depends on 64)

The one or more tangible, non-transitory computer-readable media of claim 64, wherein asynchronously monitoring behavior of the networked application comprises subscribing to domain name system (DNS) query events from a local operating system.

### Claim 71 (depends on 64)

The one or more tangible, non-transitory computer-readable media of claim 64, wherein the security application is to determine, within less than approximately five seconds, a firewall action for the network-enabled application.

### Claim 72 (depends on 71)

The one or more tangible, non-transitory computer-readable media of claim 71, wherein the security application is to create a firewall rule to block an ongoing network operation for the network-enabled application, upon determining that the network-enabled application performs a malicious activity.

### Claim 73 (depends on 64)

The one or more tangible, non-transitory computer-readable media of claim 64, further comprising instructions for a browser plugin to monitor browser activity.

### Claim 74 (depends on 64)

The one or more tangible, non-transitory computer-readable media of claim 64, wherein the instructions are further to determine that the network-enabled application does not use an operating system (OS)-provided domain name system (DNS) client and is not a web browser, and block network access for the network-enabled application.

### Claim 75 (depends on 64)

The one or more tangible, non-transitory computer-readable media of claim 64, wherein the instructions are to create a firewall rule to block specific domains or internet protocol (IP) addresses for the network-enabled application.

### Claim 76 (depends on 64)

The one or more tangible, non-transitory computer-readable media of claim 64, wherein creating the one or more firewall rules comprises determining that multiple domain names resolve to a common internet protocol (IP) address, and applying a first rule to a first domain of the IP address, and a second rule to a second domain of the IP address.

### Claim 77 (depends on 76)

The one or more tangible, non-transitory computer-readable media of claim 76, wherein the first rule is to block the IP address, and the second rule is to allow the IP address.

### Claim 78 (depends on 77)

The one or more tangible, non-transitory computer-readable media of claim 77, wherein the instructions are to apply the first rule after determining that a most recent DNS query that resolved to the IP address was for the first domain, and apply the second rule after determining that the most recent DNS query that resolved to the IP address was for the second domain.

### Claim 79

A computer-implemented software method, the method to execute within a non-kernel space of a host computer, the method comprising:
asynchronously monitoring network activity of network-enabled applications of the host computer;
responsive to the monitoring, and based on network behavior of a userspace application, create one or more firewall rules for a kernel-mode firewall; and
cause the kernel-mode firewall to enforce the one more firewall rules.

### Claim 80 (depends on 79)

The computer-implemented software method of claim 79, wherein the non-kernel space is userspace.

### Claim 81 (depends on 79)

The computer-implemented software method of claim 79, wherein the one or more firewall rules are static firewall rules.

### Claim 82

A computing device, comprising:
a processor circuit and a memory;
an operating system comprising a kernel space and a non-kernel space; and
instructions encoded within the memory to instruct the processor circuit to provide a security application, the security application to:
within the non-kernel space, asynchronously monitor network activity of a network-enabled application;
based on the asynchronous monitoring, create one or more firewall rules for a kernel-mode firewall; and
cause the kernel-mode firewall to enforce the one more firewall rules.

### Claim 83 (depends on 82)

The computing device of claim 82, wherein the security application is not tightly integrated with the kernel-mode firewall.
