# US 2026/0089180 A1 · Explicit proxy inline security

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

- Number: US 2026/0089180 A1
- Document ID: US20260089180A1
- Status: Published application
- Kind: A1
- Application number: 18/897,911
- Filed: 2024-09-26
- Published: 2026-03-26
- Earliest claimed: 2024-09-26
- Assignees: Palo Alto Networks, Inc.
- Applicants: Palo Alto Networks, Inc.
- Inventors: Raghavaiah Avula; Arivu Mani Ramasamy; Ketul Sheth; Donna Grace Prince; Bipin Ramasare Dubey
- Web page: https://patentgrep.com/patent/US20260089180A1

## CPC

- H04L 63/1425: {Traffic logging, e.g. anomaly detection}
- H04L 63/0236: {Filtering by address, protocol, port number or service, e.g. IP-address or URL}
- H04L 63/1491: {using deception as countermeasure, e.g. honeypots, honeynets, decoys or entrapment}
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

A plurality of logs for a cloud security service for a plurality of tenants are captured. A network traffic pattern associated with the plurality of logs is analyzed and a security related impact analysis is determined. An action is performed based on the security related impact analysis.

## Claims

### Claim 1

A method, comprising:
capturing a plurality of logs for a cloud security service for a plurality of tenants;
analyzing a network traffic pattern associated with the plurality of logs and determining a security related impact analysis; and
performing an action based on the security related impact analysis.

### Claim 2 (depends on 1)

The method of claim 1, wherein the plurality of logs include at least two of a virtual private cloud log, a proxy log and tcpdump, or a firewall log.

### Claim 3 (depends on 1)

The method of claim 1, wherein the network traffic pattern is analyzed by an explicit proxy data analyzer.

### Claim 4 (depends on 3)

The method of claim 3, wherein analyzing the network traffic pattern includes analyzing the plurality of logs to identify one or more anomalies.

### Claim 5 (depends on 4)

The method of claim 4, wherein the one or more anomalies include unusual request patterns or response statuses that deviate from a normal behavior.

### Claim 6 (depends on 4)

The method of claim 4, wherein the analyzed network traffic patterns are cross referenced with threat intelligence and historical attack patterns.

### Claim 7 (depends on 4)

The method of claim 4, wherein an anomaly of the one or more anomalies is a sudden spike in requests or network traffic from a single IP address.

### Claim 8 (depends on 7)

The method of claim 7, wherein the single IP address is associated with a plurality of tenants.

### Claim 9 (depends on 8)

The method of claim 8, wherein a honeypot cluster is deploy in response to the sudden spike in requests or network traffic from the single IP address.

### Claim 10 (depends on 9)

The method of claim 9, further comprising identifying one or more IP addresses that attempt to access or access the honeypot cluster.

### Claim 11 (depends on 10)

The method of claim 10, further comprising determining whether each of the one or more identified IP addresses is a known IP address.

### Claim 12 (depends on 11)

The method of claim 11, wherein the known IP address is already included in a global honeypot list and/or a global external dynamic list.

### Claim 13 (depends on 11)

The method of claim 11, wherein in response to determining that a first identified IP address is not a known IP address, the method further comprises adding the first identified IP address to a global honeypot list and/or a global external dynamic list.

### Claim 14 (depends on 13)

The method of claim 13, further comprising pushing the global honeypot list and/or the global external dynamic list to one or more proxies.

### Claim 15 (depends on 1)

The method of claim 1, wherein the action includes implementing rate limiting rules in a proxy, updating firewall rules, and/or updating proxy settings.

### Claim 16 (depends on 1)

The method of claim 1, wherein the analyzed network traffic pattern is tenant-specific.

### Claim 17 (depends on 16)

The method of claim 16, wherein baseline patterns are established for a specific tenant of the plurality of tenants.

### Claim 18 (depends on 17)

The method of claim 17, wherein deviations from the baseline patterns are detected.

### Claim 19 (depends on 18)

The method of claim 18, wherein one or more open ports on network devices within the specific tenant's environment are identified.

### Claim 20 (depends on 19)

The method of claim 19, wherein the security implications of the one or more open ports is assessed.

### Claim 21 (depends on 19)

The method of claim 19, wherein one or more threats are detected.

### Claim 22 (depends on 21)

The method of claim 21, wherein the action includes generating a report based on the one or more detected threats.

### Claim 23 (depends on 21)

The method of claim 21, wherein the action includes recommending an updated configuration for the specific tenant based on the one or more detected threats.

### Claim 24

A system, comprising:
a processor configured to:
capturing a plurality of logs for a cloud security service for a plurality of tenants;
analyzing a network traffic pattern associated with the plurality of logs and determining a security related impact analysis; and
performing an action based on the security related impact analysis; and
a memory coupled to the processor and configured to provide the processor with instructions.

### Claim 25

A computer program product embodied in a non-transitory computer readable medium and comprising computer instructions for:
capturing a plurality of logs for a cloud security service for a plurality of tenants;
analyzing a network traffic pattern associated with the plurality of logs and determining a security related impact analysis; and
performing an action based on the security related impact analysis.
