Back to results
US 12,647,392 B2Granted
Disaster recovery for cloud-based monitoring of internet access
AssigneeZscaler, Inc.
InventorsAbhinav Bansal, Paul Yun Ling, Vikas Mahajan
Life of this patent
Estimating the term…
Abstract
Systems and methods include receiving one or more disaster recovery configurations; identifying activation of a disaster recovery mode; and controlling traffic flow such that the traffic is any of blocked to all destinations, allowed to all destinations, and allowed to preselected destinations based on the one or more received disaster recovery configurations.
Claims20
A non-transitory computer-readable medium including instructions that, when executed, cause one or more processors to perform steps of:
- receiving one or more disaster recovery configurations;
- identifying activation of a disaster recovery mode, wherein the disaster recovery mode is triggered based on detection that a cloud-based system is unavailable to perform security processing for network traffic associated with a user device, the detection comprising receipt of or query of a Domain Name System (DNS) record signaling the unavailability;
- and
- controlling traffic flow such that the traffic is any of blocked to all destinations, allowed to all destinations, and allowed to preselected destinations based on the one or more received disaster recovery configurations, wherein the disaster recovery configurations include preconfigured actions for the user device to perform local security processing based on cached policies when the cloud-based system is unavailable, the cached policies being dynamically updated based on prior cloud-enforced actions and tenant-specific configurations, and wherein conflicts between customer-defined and global default destination lists are deterministically resolved in favor of the customer-defined lists.
1 more element
A cloud-based system comprising:
- one or more processors;
- and
- memory storing computer-executable instructions, wherein the computer-executable instructions cause the one or more processors to:
- receive one or more disaster recovery configurations;
- identify activation of a disaster recovery mode, wherein the disaster recovery mode is triggered based on detection that the cloud-based system is unavailable to perform security processing for network traffic associated with a user device, the detection comprising receipt of or query of a Domain Name System (DNS) record signaling the unavailability;
- and
- control traffic flow such that the traffic is any of blocked to all destinations, allowed to all destinations, and allowed to preselected destinations based on the one or more received disaster recovery configurations, wherein the disaster recovery configurations include preconfigured actions for the user device to perform local security processing based on cached policies when the cloud-based system is unavailable, the cached policies being dynamically updated based on prior cloud-enforced actions and tenant-specific configurations, and wherein conflicts between customer-defined and global default destination lists are deterministically resolved in favor of the customer-defined lists.
4 more elements
A method comprising steps of:
- receiving one or more disaster recovery configurations;
- identifying activation of a disaster recovery mode, wherein the disaster recovery mode is triggered based on detection that a cloud-based system is unavailable to perform security processing for network traffic associated with a user device, the detection comprising receipt of or query of a Domain Name System (DNS) record signaling the unavailability;
- and
- controlling traffic flow such that the traffic is any of blocked to all destinations, allowed to all destinations, and allowed to preselected destinations based on the one or more received disaster recovery configurations, wherein the disaster recovery configurations include preconfigured actions for the user device to perform local security processing based on cached policies when the cloud-based system is unavailable, the cached policies being dynamically updated based on prior cloud-enforced actions and tenant-specific configurations, and wherein conflicts between customer-defined and global default destination lists are deterministically resolved in favor of the customer-defined lists.
1 more element
Dependencies are inferred from the claim text.