Blog da Zscaler

Receba as últimas atualizações do blog da Zscaler na sua caixa de entrada

Products & Solutions

Zero Trust, Zero Downtime: Ensure Security and Compliance Through Outages and Disruptions

image

Introduction

In the world of IT, Disaster Recovery (DR) and Business Continuity (BC) are often framed as "uptime" metrics. But for US organizations—especially those in Finance, Healthcare, and those governed by the Securities and Exchange Commission—the real challenge isn't just staying online; it's also staying compliant.

Regulatory mandates like HIPAA, FINRA, and SOX—alongside frameworks like NIST and SOC 2—do not pause during a crisis. In fact, many organizations inadvertently create their biggest compliance "gap" during a failover event by relaxing security controls to "keep the business running." Compliance frameworks themselves have evolved to address these gaps. For example, older iterations of NIST 800-53 (Contingency Planning) were centered on the simple availability of operations. Today, the focus has shifted toward maintaining the appropriate security posture at all times. 

The Compliance Matrix: Specific Controls for BC/DR

Compliance is no longer about having a "plan in a binder." Modern US frameworks and regulations require proof of Technical Controls that remain active during a disruption.

Regulation / Framework

Specific Control

The Requirement

What Auditors Look For

NIST 800-53

CP-2 & CP-7 (Contingency Planning)

"Provide controls at the alternate processing site that are equivalent to those at the primary site."

Evidence that the alternate site provides information security safeguards equivalent to the primary site.

ISO 27001

Annex A.17 (Information Security Continuity)

"...requirements for the continuity of information security management in adverse situations."

Verification that information security is embedded in BC processes and not downgraded during a disaster.

SOC 2

Security & Availability Trust Services Criteria

"The system is protected against unauthorized access and available for operation as committed."

Evidence that systems remain protected (Security) while remaining accessible (Availability) during a disruption.

HIPAA (Healthcare)

§ 164.308(a)(7) Contingency Plan

"...procedures to enable continuation of critical business processes for protection of the security of ePHI."

Establish procedures to enable continuation of critical business processes for protection of ePHI while operating in emergency mode.

FINRA (Finance)

Rule 4370 (Business Continuity Plan) Regulatory Notice 20-08

"Address (1) Data back-up and recovery... (2) All mission critical systems..."

Requirement to address "Data backup and recovery" and "Mission-critical systems" with secure access.

FFIEC (Banking)

Appendix J (Resilience)

"...ensure the alternate site has security and privacy controls commensurate with those of the primary site."

Verification that third-party resilience is tested and that the "Alternate Site" mirrors the primary security posture.

 

The "Compliance Gap" in Traditional DR Strategies

Most third-party backup solutions used by enterprises (backup VPNs, backup firewalls, or a third-party cloud security solution) fail compliance controls because they are treated as "secondary" silos. This can lead to:

- Policy Drift (ISO/NIST Violation): Security policies on DR hardware are often months out of date compared to production, failing the requirement for "equivalent safeguards."

- Audit Blind Spots (SOC 2 Violation): Legacy DR systems often lack integrated logging. If your audit trail goes dark during a 48-hour recovery window, you cannot prove the integrity of your data.

- The "Emergency Mode" Trap (HIPAA/FINRA): To ensure connectivity, teams often grant open access to the Internet and broad network access at the DR site, directly violating least privilege requirements, risking loss of sensitive information or exposing the network to external threats.

Reduce the Risk of Non-Compliance with Zscaler Business Continuity Cloud

Unlike legacy third-party backup solutions for securing Internet and private access, the Zscaler Business Continuity Cloud (BCC) ensures rapid recovery without compromising Zero Trust policies or compliance mandates. Fully managed and completely isolated from Zscaler’s primary cloud infrastructure, Business Continuity Cloud provides customer-dedicated data and control plane functionality in "last-known good" and "read-only" states. This eliminates the operational burden of maintaining complex, insufficient in-house disaster recovery infrastructure, allowing your team to focus on maintaining business operations rather than the outage.

 

The Zscaler solution provides specific technical controls that map directly to your regulatory and framework requirements:

1. Requirement: "Equivalent Safeguards" (NIST / FFIEC)

  • The Control: You meet the requirement for "equivalent safeguards" by default because the policy engine and enforcement remain while in business continuity mode.
  • The Zscaler Advantage: The Zscaler BCC solution is both physically and logically distinct from the Zero Trust ExchangeTM platform, guaranteeing a fully redundant environment. Policies are synced with the Zero Trust Exchange and maintained in a read-only state within the BCC instance. A private control plane helps ensure that critical security controls and granular access policies are enforced even when in business continuity mode.

2. Requirement: "Continuous Auditability" (SOX / SOC 2)

  • The Control: You provide a continuous audit trail via log streaming, ensuring that logs from the disaster recovery period are indistinguishable from normal operations.
  • The Zscaler Advantage: Visibility is often the first thing lost during an outage. The Zscaler solution continues to stream logs directly to your Security Information and Event Management (SIEM) system during a disruption, providing an audit trail that is indistinguishable from normal operations for private applications.

3. Requirement: "Emergency Mode Security" (HIPAA / ISO 27001)

  • The Control: This satisfies the requirement for a "secure transition," ensuring that security is deeply embedded in the continuity process rather than added as a manual, secondary step.
  • The Zscaler Advantage: Zscaler BCC maintains existing security policies and application connectivity without the need for separate rules, multiple logins, or additional endpoint agents. User sessions are seamlessly transferred and maintained during the transition to business continuity mode. By eliminating the need for users to re-authenticate or install additional software, you remove the "human error" risk factor during a crisis.

Conclusion: Not Just Continuity, But Security and Peace of Mind

For the modern enterprise, Business Continuity and Disaster Recovery are no longer just "IT Infrastructure" problems—they are legal and risk mandates.

Legacy, multi-vendor setups were built for an era where "uptime" was the only metric.

In the era of strict oversight and evolving privacy laws, how you remain secure is just as critical as if you stay online. Architecting a resilient security strategy that honors data sovereignty is what separates true Zero Trust from mere connectivity.

Read this solution brief to learn more about Zscaler Business Continuity Cloud.

For a tailored discussion: [Sign-up to Chat with an Expert]

 

This blog post has been created by Zscaler for informational purposes only and is provided "as is" without any guarantees of accuracy, completeness or reliability. Zscaler assumes no responsibility for any errors or omissions or for any actions taken based on the information provided. Any third-party websites or resources linked in this blog post are provided for convenience only, and Zscaler is not responsible for their content or practices. All content is subject to change without notice. By accessing this blog, you agree to these terms and acknowledge your sole responsibility to verify and use the information as appropriate for your needs.

form submtited
Obrigado por ler

Esta postagem foi útil??

Aviso legal: este post no blog foi criado pela Zscaler apenas para fins informativos e é fornecido "no estado em que se encontra", sem quaisquer garantias de exatidão, integridade ou confiabilidade. A Zscaler não se responsabiliza por quaisquer erros, omissões ou por quaisquer ações tomadas com base nas informações fornecidas. Quaisquer sites ou recursos de terceiros vinculados neste post são fornecidos apenas para sua conveniência, e a Zscaler não se responsabiliza por seu conteúdo ou práticas. Todo o conteúdo está sujeito a alterações sem aviso prévio. Ao acessar este blog, você concorda com estes termos e reconhece que é de sua exclusiva responsabilidade verificar e utilizar as informações conforme apropriado para suas necessidades.

Receba as últimas atualizações do blog da Zscaler na sua caixa de entrada

Ao enviar o formulário, você concorda com nossa política de privacidade.