IP Library Granted Patent US 12,683,995
Granted Patent B2
US 12,683,995 · App. 18/897,911 · Granted Jul 14, 2026

Explicit proxy inline security

Inventors: Raghavaiah Avula (San Jose, CA); Arivu Mani Ramasamy (San Jose, CA); Ketul Sheth (San Jose, CA); Donna Grace Prince (Dublin, CA); Bipin Ramasare Dubey (Santa Clara, CA)
Assignee: Palo Alto Networks, Inc.
H04L63/1425H04L63/0236H04L63/1491
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,683,995
App. No.
18/897,911
Granted
Jul 14, 2026
Kind
B2
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 (31)

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, wherein the network traffic pattern is analyzed by an explicit proxy data analyzer, wherein analyzing the network traffic pattern includes analyzing the plurality of logs to identify one or more anomalies, wherein an anomaly of the one or more anomalies is a sudden spike in requests or network traffic from a single IP address, wherein the single IP address is associated with a plurality of tenants, wherein a honeypot cluster is deployed in response to the sudden spike in requests or network traffic from the single IP address; and

performing an action based on the security related impact analysis.

2 . 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.

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

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

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

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

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

8 . The method of claim 6 , 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.

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

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

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

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

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

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

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

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

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

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

19 . 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, wherein the network traffic pattern is analyzed by an explicit proxy data analyzer, wherein analyzing the network traffic pattern includes analyzing the plurality of logs to identify one or more anomalies, wherein an anomaly of the one or more anomalies is a sudden spike in requests or network traffic from a single IP address, wherein the single IP address is associated with a plurality of tenants, wherein a honeypot cluster is deployed in response to the sudden spike in requests or network traffic from the single IP address; 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.

20 . 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, wherein the network traffic pattern is analyzed by an explicit proxy data analyzer, wherein analyzing the network traffic pattern includes analyzing the plurality of logs to identify one or more anomalies, wherein an anomaly of the one or more anomalies is a sudden spike in requests or network traffic from a single IP address, wherein the single IP address is associated with a plurality of tenants, wherein a honeypot cluster is deployed in response to the sudden spike in requests or network traffic from the single IP address; and

performing an action based on the security related impact analysis.