Disaster recovery for cloud-based private application access
Systems and methods include receiving one or more disaster recovery configurations via a cloud-based system; storing the one or more received disaster recovery configurations in one or more components of the cloud-based system; identifying activation of a disaster recovery mode; and providing private application access based on one or more disaster recovery configurations.
1 . 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, each specifying access permissions limited to a subset of private applications, via a cloud-based system;
storing the one or more received disaster recovery configurations in one or more components of the cloud-based system;
identifying activation of a disaster recovery mode; and
responsive to identifying activation of the disaster recovery mode, enforcing zero trust access control by providing access exclusively to the subset of private applications specified in the disaster recovery configurations as disaster-recovery-mode applications identified in an application list of the disaster recovery configurations, while restricting access to other private applications by denying private application access to any private application not identified in the application list during the disaster recovery mode.
2 . The non-transitory computer-readable medium of claim 1 , wherein the one or more disaster recovery configurations are each associated with one or more specific tenants of the cloud-based system, and define distinct private application access permissions tailored to each tenant based on tenant-specific disaster recovery policies.
3 . The non-transitory computer-readable medium of claim 1 , wherein the one or more disaster recovery configurations include component-specific instructions identifying which components of the cloud-based system will remain operational to facilitate private application access during active disaster recovery mode, while disabling non-essential components.
4 . The non-transitory computer-readable medium of claim 1 , wherein private application access is only provided to disaster recovery applications specified in the one or more configurations.
5 . The non-transitory computer-readable medium of claim 1 , wherein the one or more components of the cloud-based system update their stored configurations based on one or more new configurations.
6 . The non-transitory computer-readable medium of claim 1 , wherein the one or more components of the cloud-based system store a plurality of configurations, and wherein any of the stored configurations can be used responsive to activation of the disaster recovery mode.
7 . The non-transitory computer-readable medium of claim 1 , wherein the activation of the disaster recovery mode is one of automatically activated and activated by an administrator associated with a tenant.
8 . 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, each specifying access permissions limited to a subset of private applications, via the cloud-based system;
store the one or more received disaster recovery configurations in one or more components of the cloud-based system;
identify activation of a disaster recovery mode; and
responsive to identifying activation of the disaster recovery mode, enforce zero trust access control by providing access exclusively to the subset of private applications specified in the disaster recovery configurations as disaster-recovery-mode applications identified in an application list of the disaster recovery configurations, while restricting access to other private applications by denying private application access to any private application not identified in the application list during the disaster recovery mode.
9 . The cloud-based system of claim 8 , wherein the one or more disaster recovery configurations are each associated with one or more specific tenants of the cloud-based system, and define distinct private application access permissions tailored to each tenant based on tenant-specific disaster recovery policies.
10 . The cloud-based system of claim 8 , wherein the one or more disaster recovery configurations include component-specific instructions identifying which components of the cloud-based system will remain operational to facilitate private application access during active disaster recovery mode, while disabling non-essential components.
11 . The cloud-based system of claim 8 , wherein private application access is only provided to disaster recovery applications specified in the one or more configurations.
12 . The cloud-based system of claim 8 , wherein the one or more components of the cloud-based system update their stored configurations based on one or more new configurations.
13 . The cloud-based system of claim 8 , wherein the one or more components of the cloud-based system store a plurality of configurations, and wherein any of the stored configurations can be used responsive to activation of the disaster recovery mode.
14 . The cloud-based system of claim 8 , wherein the activation of the disaster recovery mode is one of automatically activated and activated by an administrator associated with a tenant.
15 . A method comprising steps of:
receiving one or more disaster recovery configurations, each specifying access permissions limited to a subset of private applications, via a cloud-based system;
storing the one or more received disaster recovery configurations in one or more components of the cloud-based system;
identifying activation of a disaster recovery mode; and
responsive to identifying activation of the disaster recovery mode, enforcing zero trust access control by providing access exclusively to the subset of private applications specified in the disaster recovery configurations as disaster-recovery-mode applications identified in an application list of the disaster recovery configurations, while restricting access to other private applications by denying private application access to any private application not identified in the application list during the disaster recovery mode.
16 . The method of claim 15 , wherein the one or more disaster recovery configurations are each associated with one or more specific tenants of the cloud-based system, and define distinct private application access permissions tailored to each tenant based on tenant-specific disaster recovery policies.
17 . The method of claim 15 , wherein the one or more disaster recovery configurations include component-specific instructions identifying which components of the cloud-based system will remain operational to facilitate private application access during active disaster recovery mode, while disabling non-essential components.
18 . The method of claim 15 , wherein private application access is only provided to disaster recovery applications specified in the one or more configurations.
19 . The method of claim 15 , wherein the one or more components of the cloud-based system update their stored configurations based on one or more new configurations.
20 . The method of claim 15 , wherein the one or more components of the cloud-based system store a plurality of configurations, and wherein any of the stored configurations can be used responsive to activation of the disaster recovery mode.