# US 2025/0158962 A1 · Cloud-based Intrusion Prevention System, Multi-Tenant Firewall, and Stream Scanner

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

- Number: US 2025/0158962 A1
- Document ID: US20250158962A1
- Status: Published application
- Kind: A1
- Application number: 19/024,724
- Filed: 2025-01-16
- Published: 2025-05-15
- Earliest claimed: 2015-11-17
- Assignees: Zscaler, Inc.
- Applicants: Zscaler, Inc.
- Inventors: Srikanth Devarajan; Sushil Pangeni; Vladimir Stepanenko; Ravinder Verma; Naresh kumar Povlavaram Munirathnam
- Web page: https://patentgrep.com/patent/US20250158962A1

## CPC

- H04L 63/1416: {Event detection, e.g. attack signature detection}
- G06F 21/554: {involving event detection and direct action}
- H04L 41/0681: Configuration of triggering conditions
- H04L 41/069: using logs of notifications; Post-processing of notifications
- H04L 43/028: by filtering
- H04L 43/04: Processing captured monitoring data, e.g. for logfile generation
- H04L 63/0218: {Distributed architectures, e.g. distributed firewalls}
- H04L 63/0254: {Stateful filtering}
- H04L 63/1408: {by monitoring network traffic (monitoring network traffic per se H04L43/00)}
- H04L 63/1425: {Traffic logging, e.g. anomaly detection}
- H04L 63/168: {above the transport layer}
- H04L 63/20: {for managing network security; network security policies in general (filtering policies H04L63/0227)}
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

A method of providing cloud-based security services includes receiving, at one or more distributed processing nodes in a cloud-based system, network traffic from a plurality of endpoints associated with at least one tenant; applying, by each distributed processing node, at least one cloud-based security inspection function configured to detect threats or enforce policy controls in the received network traffic; determining, via a policy engine whether to block, allow, or further analyze the network traffic based on per-tenant security policies; logging, in a cloud-based logging repository, inspection results, policy decisions, and rule matches for subsequent reporting and analytics; and updating the security inspection function at the distributed processing nodes, in real time, with newly discovered threat signatures and policy changes to provide continuous protection across the cloud-based system.

## Claims

### Claim 1

A method of providing cloud-based security services, the method comprising:
receiving, at one or more distributed processing nodes in a cloud-based system, network traffic from a plurality of endpoints associated with at least one tenant;
applying, by each distributed processing node, at least one cloud-based security inspection function configured to detect threats or enforce policy controls in the received network traffic;
determining, via a policy engine whether to block, allow, or further analyze the network traffic based on per-tenant security policies;
logging, in a cloud-based logging repository, inspection results, policy decisions, and rule matches for subsequent reporting and analytics; and
updating the security inspection function at the distributed processing nodes, in real time, with newly discovered threat signatures and policy changes to provide continuous protection across the cloud-based system.

### Claim 2 (depends on 1)

The method of claim 1, wherein the cloud-based security inspection function includes an Intrusion Prevention System (IPS) engine configured to:
identify malicious or unauthorized activity in network traffic by matching traffic flows against predefined or dynamically updated intrusion signatures; and
block, quarantine, or otherwise mitigate threats based on a tenant-specific IPS policy, regardless of endpoint location or connection type.

### Claim 3 (depends on 1)

The method of claim 1, wherein the cloud-based security inspection function includes a firewall module configured to:
classify each network flow based on at least one of source address, destination address, protocol, port, user identity, or application signature; and
enforce per-tenant firewall rules stored in a multi-tenant policy store, wherein said firewall rules permit or deny flows based on classification results.

### Claim 4 (depends on 1)

The method of claim 1, wherein the cloud-based security inspection function includes a stream scanning engine configured to:
segment network data into packets or blocks and match partial or complete payloads against Snort-style or other advanced signatures;
correlate detected matches across multiple packets to identify multi-packet threats using offsets, distances, event filters, or rate tracking; and
take action including one of block, alert, or allow, based on match results and tenant-specific threat policies.

### Claim 5 (depends on 1)

The method of claim 1, further comprising:
synchronizing each distributed processing node with newly introduced signatures, firewall rules, and stream scanning definitions from a central authority node, enabling immediate mitigation of emergent threats without on-premises hardware modification.

### Claim 6 (depends on 1)

The method of claim 1, wherein:
each network flow is tagged with a specific tenant identity to ensure traffic is inspected exclusively against that tenant's security policy, thereby preserving strict policy segregation across multiple tenants.

### Claim 7 (depends on 1)

The method of claim 1, further comprising:
dynamically scaling inspection resources at the distributed processing nodes based on observed traffic volume and complexity, thereby allowing continuous inspection of encrypted and unencrypted flows with minimal additional latency.

### Claim 8 (depends on 1)

The method of claim 1, further comprising:
terminating or transparently intercepting Secure Sockets Layer (SSL)/Transport Layer Security (TLS) sessions, decrypting payloads for inspection in the at least one cloud-based security inspection function, and re-encrypting or forwarding inspected data based on policy outcomes.

### Claim 9 (depends on 1)

The method of claim 1, wherein:
the cloud-based logging repository aggregates session-level details, including user identity, matched rules, threat classifications, and policy decisions, enabling comprehensive historical analysis and real-time dashboards for administrators.

### Claim 10 (depends on 1)

The method of claim 1, further comprising:
encrypting or obfuscating rule files containing Intrusion Protection System (IPS), firewall, and stream scanning signatures prior to distributing them to each distributed processing node, thereby preventing unauthorized signature exposure in private or virtualized deployments.

### Claim 11 (depends on 1)

The method of claim 1, further comprising:
applying network address translation (NAT) rules at each distributed processing node to rewrite source or destination IP addresses for outbound or inbound connections, wherein NAT policies are configurable on a per-tenant basis to accommodate unique IP address requirements or port-forwarding rules.

### Claim 12 (depends on 1)

The method of claim 1, wherein:
the cloud-based security inspection function enforces Domain Name System (DNS)-level policies by inspecting DNS queries and responses, blocking requests to malicious domains, or redirecting suspicious DNS traffic to a secure resolver, based on per-tenant configurations.

### Claim 13 (depends on 1)

The method of claim 1, further comprising:
integrating a sandbox environment with the inspection function, wherein suspicious files or objects identified by the at least one cloud-based security inspection function are isolated and analyzed in a virtual sandbox to determine malicious behavior before final policy actions are taken.

### Claim 14 (depends on 1)

The method of claim 1, further comprising:
correlating multiple security events from different distributed processing nodes to recognize coordinated or distributed attacks, and providing cross-tenant analytics and trending data (subject to anonymity requirements) for proactive threat intelligence.

### Claim 15 (depends on 1)

The method of claim 1, wherein:
user-level identification is maintained using session tokens or directory integrations, and each user's traffic is inspected based on a user-specific policy profile that controls permissible protocols, destinations, or application usage in the cloud-based system.

### Claim 16 (depends on 1)

The method of claim 1, further comprising:
enforcing per-user or per-department quotas on session counts or bandwidth utilization, wherein the inspection function tracks session metrics and issues drop, throttle, or alert actions once configured thresholds are exceeded.

### Claim 17 (depends on 1)

The method of claim 1, further comprising:
ingesting, by a central authority node, external threat intelligence feeds from third-party or public sources, merging them with internally generated cloud telemetry, and distributing updated threat signatures to each distributed processing node for proactive blocking or alerting.

### Claim 18 (depends on 1)

The method of claim 1, further comprising:
applying behavioral heuristic analysis to detect anomalous traffic patterns, thereby flagging or blocking unknown threats without requiring explicit static signatures.

### Claim 19 (depends on 1)

The method of claim 1, further comprising:
implementing geo-blocking rules that identify traffic origination or destination countries, regions, or IP categories, wherein a firewall module enforces allow, deny, or additional inspection actions based on tenant-defined geolocation policies.

### Claim 20 (depends on 1)

The method of claim 1, further comprising:
maintaining versioning of each tenant's security policies at a central authority node, allowing administrators, and
rolling back to a previous policy state if newly deployed or updated security rules cause unintended issues.
