The Day the Screens Go Dark: Organizational Resilience in an Era of Converging Risk
Key Highlights
- Shift continuity planning from restoring systems to sustaining critical operations during outages.
- Map dependencies across cloud providers, vendors, data centers, telecommunications, and operational technology.
- Use business impact analysis to identify critical functions, acceptable downtime, and hidden single points of failure.
- Integrate security, IT, continuity, legal, HR, investigations, communications, and executive leadership.
- Test whether employees can fulfill the organization’s mission without normal systems for 24 hours, 72 hours, or longer.
Part 1: Risk Assessment, Business Impact Analysis, and the New Reality of Business Continuity
Not long ago, business continuity planning focused primarily on recovery. Organizations prepared for fires, floods and earthquakes. Those threats remain relevant, but the risk environment has fundamentally changed. Many of today's most disruptive events begin not with physical destruction but with software defects, cloud outages, cyberattacks, third-party failures and infrastructure dependencies that organizations often fail to recognize until something stops working.
Consider the FAA's Notice to Air Missions (NOTAM) system outage. A system most travelers had never heard of brought commercial aviation across the United States to a halt. Microsoft service disruptions demonstrate the same vulnerability. For many organizations, business operations effectively stop when Microsoft 365, Teams or Entra ID becomes unavailable. Banking system failures can prevent customers from accessing funds or completing transactions, turning a technology problem into an operational, reputational and regulatory crisis.
These events share a common lesson: Organizations have become extraordinarily dependent on systems they do not control. That raises a more important question than how quickly a system can be restored.
Can the organization continue performing its mission while that system remains unavailable?
That is the foundation of organizational resilience.
The Problem with Traditional Risk Assessments
One of the most common findings in my risk assessments is that organizations continue to evaluate risk through functional silos. Cybersecurity, physical security, executive protection, investigations and business continuity each perform essential functions, but disruptions rarely respect those boundaries.
A cyberattack can disable physical security systems. A utility failure can affect cybersecurity. A compromised executive can create legal, operational, regulatory and reputational consequences simultaneously. Often, the disruption itself is less significant than the cascading consequences it creates.
Too many assessments focus primarily on identifying threats. A more effective approach identifies dependencies. A mature hazard analysis asks:
- What do we depend on, and what depends on us?
- What happens when a dependency fails?
- How long can we function without it?
- What secondary and tertiary consequences emerge?
Organizations frequently discover that their greatest vulnerabilities aren't threats themselves. They are assumptions.
During a continuity exercise at a data center, I asked a client what would happen if every computer system in the building became unavailable for 72 hours following a major earthquake. The room became remarkably quiet. The organization had continuity plans, but those plans assumed technology would remain available. Customer-service personnel had no paper forms. Managers had no printed contact lists. Emergency procedures, vendor information and building access all depended on electronic systems. Most employees no longer knew how to perform critical functions manually.
A cyberattack can disable physical security systems. A utility failure can affect cybersecurity. A compromised executive can create legal, operational, regulatory and reputational consequences simultaneously. Often, the disruption itself is less significant than the cascading consequences it creates.
Technology had improved efficiency. It had also quietly eliminated resilience.
The Business Impact Analysis and the Shift to Resilience
If risk assessment asks what can go wrong, the Business Impact Analysis (BIA) determines what matters most when it does. Too many organizations treat the BIA as a compliance exercise rather than the strategic tool it should be.
A meaningful BIA identifies critical functions, recovery priorities, acceptable downtime and operational dependencies. It can uncover uncomfortable realities: a seemingly minor application supporting multiple mission-critical functions, a single vendor underpinning several business processes, or one employee possessing institutional knowledge no one else has.
These findings point to an important distinction. Recovery focuses on restoring systems. Resilience focuses on sustaining operations while restoration occurs.
That difference changes how organizations prepare for disruption. Instead of asking only, "How quickly can we recover?" resilient organizations ask, "How do we continue operating while recovery takes place?"
That mindset is central to the ASIS Organizational Resilience Standard.
Part 2: Cloud Concentration, Data Centers, SCADA, and the Hidden Fragility of Modern Operations
For years, continuity planning emphasized protecting company-owned infrastructure through backup generators, alternate work sites, redundant network connections and secondary data centers. If something failed, the organization generally controlled recovery.
Today, much of that infrastructure and functionality has moved to cloud platforms, SaaS applications and managed service providers. This creates a resilience paradox: Organizations have more redundancy than ever, yet many depend on a surprisingly small number of providers.
The Cloud Concentration Problem
During a recent risk assessment, I asked business leaders what would happen if Microsoft disappeared for 72 hours. Most initially dismissed the question as unrealistic. Then we mapped their dependencies.
Email operated on Microsoft 365. Collaboration depended on Teams. Authentication ran through Entra ID. Data resided in SharePoint and OneDrive, while applications operated in Azure. Vendor portals and business applications also indirectly relied on Microsoft infrastructure. The same concentration exists across AWS, Google Cloud, Salesforce and other major providers.
Organizations may believe they have diversified risk because they use numerous applications. However, those applications can depend on the same underlying infrastructure. The danger isn't necessarily losing one application; it is losing several business functions simultaneously.
A continuity plan that assumes email, authentication and cloud-hosted applications will remain available during an outage may not be a continuity plan at all. It may simply be a documented assumption.
Third-Party Risk Is Now Business Risk
For many organizations, third-party providers effectively operate mission-critical business processes. The organization may not own the infrastructure, but it remains accountable to its customers when something fails.
When a provider experiences a significant outage, customers often have little visibility into recovery timelines or contingency plans. The organization's name remains on the product or service, regardless of where the failure originated.
Resilience planning must include detailed dependency mapping. Security leaders need to understand not only which vendors support critical processes, but also which providers support those vendors. Significant continuity risks often exist two or three layers beyond the immediate contractual relationship.
The Data Center Nobody Thinks About
The cloud still operates in a physical world. Every cloud service depends on data centers requiring electricity, fuel, cooling, water, telecommunications and physical security.
Yet data-center concentration rarely receives sufficient attention in continuity discussions. An organization may replicate applications across multiple regions while relying on a single identity platform or telecommunications carrier.
Redundancy without an understanding of underlying dependencies creates a false sense of security.
IT, OT, and Why SCADA Changes Everything
The convergence of information technology (IT) and operational technology (OT) is among the most significant changes in organizational risk over the past two decades. IT traditionally managed information and business applications. OT controlled physical processes. Today, utilities, manufacturers, transportation providers and water-treatment facilities increasingly connect operational systems to enterprise networks and analytics platforms.
Efficiency improves, but so do attack surfaces and potential failure points.
SCADA environments deserve particular attention because they directly influence the physical world. A disruption affecting a billing platform creates financial consequences. A disruption affecting SCADA can threaten public safety and interrupt essential services.
In a modern utility, an incident might begin with a compromised employee credential that provides access to a business system connected to operational reporting, ultimately influencing field operations and service restoration. The question is no longer whether cyber and physical risks intersect. It is how far the consequences can spread when they do.
The Colonial Pipeline incident demonstrated how a business-system compromise could disrupt fuel distribution across multiple states. The larger lesson extends beyond ransomware. Technology disruptions influence operational decisions, supply chains and public confidence.
Recovery time objectives remain important, but they are no longer sufficient. Organizations must prepare for cloud services, communications, authentication platforms, vendors, operational technology and physical security systems to become unavailable simultaneously.
Part 3: The Human Dimension of Resilience
When organizations discuss resilience, the conversation often gravitates toward technology: restoration times, cloud architecture and backup sites. Those are important considerations, but they are only part of the equation.
Technology failures dominate headlines because they are visible. Human vulnerabilities often remain hidden until damage occurs. In many organizations, some of the most significant resilience risks are found not in data centers or operational technology networks, but in people.
When organizations discuss resilience, the conversation often gravitates toward technology: restoration times, cloud architecture and backup sites. Those are important considerations, but they are only part of the equation.
Executive Protection Has Become a Business Continuity Function
Historically, executive protection programs were measured by their ability to prevent physical harm. That responsibility remains essential. However, senior executives also represent concentrated sources of organizational risk.
CEOs, CFOs and general counsel possess acquisition strategies, banking relationships, earnings information and sensitive legal intelligence. An adversary seeking to influence a decision, obtain competitive information or manipulate an organization's direction may increasingly target the executives themselves.
Executive targeting rarely resembles the movies. It is often subtle: a professional networking contact, an attractive investment opportunity, a speaking invitation, a conference introduction or a social-media connection. Trust builds over time, and access expands.
The term "honeytrap" may sound antiquated, but the concept remains relevant. Only the mechanisms have evolved. Modern influence operations exploit social, professional, ideological and financial vulnerabilities, while deepfakes, voice cloning and synthetic identities make deception easier than ever.
Blackmail is similarly misunderstood as a personal-security concern. It is also an organizational continuity issue. An executive vulnerable to coercion may expose acquisition plans, contracting information or competitive intelligence. Once an executive is compromised, the consequences rarely remain personal.
Corporate Investigations and Insider Threats
Corporate investigations teams are often among the first to recognize emerging risk patterns, yet their observations frequently remain isolated. An access violation may be handled separately from a misconduct investigation or cybersecurity concern.
Viewed in isolation, individual incidents may seem manageable. Viewed together, they can reveal a much larger problem. Patterns matter more than isolated events.
Insider threats are also more complex than the espionage scenarios most people envision. Some are intentional; others result from financial distress, workplace grievances, coercion or poor judgment. From a resilience perspective, motivation matters less than potential impact.
Major insider threat cases have revealed recurring indicators: unexplained affluence or financial hardship, attempts to bypass controls, access beyond normal responsibilities, unusual work hours, excessive data downloads and efforts to retain information before departure.
Any one indicator may be insignificant. Combined, they may signal an emerging threat.
Organizations need mechanisms for sharing information across security, human resources, IT, legal and investigations teams while respecting privacy, confidentiality and applicable legal requirements. Recognizing patterns early can prevent an isolated concern from becoming an organizational crisis.
Part 4: Leadership and the Path Forward
If the FAA disruption, recurring cloud-service outages, banking interruptions and ransomware incidents demonstrate anything, it is that resilience can no longer be treated as a technical function.
The ASIS Organizational Resilience Standard approaches resilience as an integrated management system. In practice, this means organizations must coordinate security, IT, business continuity, legal, communications, human resources and executive leadership before a crisis occurs.
A ransomware attack, for example, quickly becomes more than a cybersecurity incident. It can trigger legal obligations, disrupt customer relationships, affect employees, interrupt operations and demand immediate board-level decisions.
Organizations that establish these relationships before an emergency are better positioned to adapt than those attempting to coordinate for the first time in the middle of a crisis.
From Compliance to Capability
One of the most common mistakes organizations make is confusing compliance with preparedness. Passing an audit or maintaining a business continuity plan does not guarantee resilience.
Throughout my career, the most consistent finding in risk assessments, threat assessments and continuity reviews has been the danger of assumptions. Organizations assume systems will remain available, vendors will recover quickly, insider threats will be obvious and someone else owns the problem.
Resilience begins when you challenge those assumptions.
I frequently recommend a straightforward exercise for leadership teams: Imagine every system your organization depends on becomes unavailable tomorrow morning. No email. No Microsoft Teams or Zoom. No cloud applications, access-control databases, vendor portals, dashboards or internet connectivity.
Could the organization continue fulfilling its mission for 24 hours? Seventy-two hours? Two weeks?
The discussion that follows is often more valuable than any audit report. It exposes operational dependencies, decision-making weaknesses and gaps in employee preparedness that might otherwise remain hidden.
Resilience Is Ultimately a Leadership Issue
Resilience cannot be delegated exclusively to security, IT or business continuity. Leaders establish risk tolerance, allocate resources, set priorities and determine whether resilience becomes a strategic capability or remains a compliance requirement.
Integration does not necessarily require larger budgets. It requires communication, collaboration and leadership. Most importantly, it requires organizations to stop asking, "Whose problem is this?" and start asking, "How does this affect our mission?"
Final Thoughts
The next major disruption will almost certainly look different from the last one. It may begin with a cloud provider, a ransomware attack, a compromised executive or an entirely new category of risk that receives little attention today.
The initiating event is often less important than the organization's response. What matters is whether leadership understands its dependencies, employees can function without normal systems, and resilience is embedded in organizational culture rather than documented in a binder on a shelf.
The organizations that thrive will not necessarily be those with the most sophisticated technology or the greatest number of backup systems. They will be the organizations that understand how to operate when those systems are gone.
When the screens go dark, resilience is no longer measured by what failed. It is measured by what continues to function.
Endnotes and References
-
ASIS International, ANSI/ASIS ORS 1.1-2022, Organizational Resilience: Security, Preparedness, and Continuity Management Systems Requirements with Guidance for Use.
-
National Institute of Standards and Technology (NIST), SP 800-34 Rev. 1, Contingency Planning Guide for Federal Information Systems.
-
NIST, Cybersecurity Framework (CSF) 2.0.
-
Cybersecurity and Infrastructure Security Agency (CISA), Cross-Sector Cybersecurity Performance Goals.
-
CISA, Operational Technology Security Guidance and Industrial Control Systems Resources.
-
National Insider Threat Task Force (NITTF), Insider Threat Program Maturity Framework and Related Guidance.
-
Defense Counterintelligence and Security Agency (DCSA), Insider Threat Program Resources.
-
Federal Aviation Administration (FAA), public statements and reporting regarding the NOTAM system outage.
-
U.S. Department of Homeland Security and CISA analyses related to the Colonial Pipeline ransomware incident.
-
ASIS International guidance, standards and professional practices relating to executive protection, investigations and organizational resilience.
-
Army Regulation 381-12, Subversion and Espionage Directed Against the U.S. Army (SAEDA).
-
Public reporting and after-action analyses related to Microsoft cloud-service outages, financial-sector service disruptions, data-center resilience and critical infrastructure interdependencies.
About the Author
Jeffrey A. Slotnick CPP, PSPJeffrey A. Slotnick CPP, PSP
President of Setracon ESRMS
Jeffrey A. Slotnick, CPP, PSP, President, Setracon ESRMS
Jeffrey A. Slotnick, CPP, PSP, is an internationally known Enterprise Security Risk Consultant with over 28 years of experience. Jeff is peer-recognized as a “Thought Leader and Change Agent. He focuses on all Enterprise Security Risk Management facets, including quality management programs, risk, vulnerability, threat assessments, Emergency Response Planning, Business Continuity Planning, and Physical Security System Master Planning, Design, and Integration. As a curriculum developer and master trainer, Jeff advocates for quality professional development and training of security, law enforcement, and military personnel. He is a former member of the North American Board. He is a Community Vice President for ASIS International and a Faculty Advisor for the University of Phoenix Bachelor of Science in Cyber Security and Security Management Degree Program.
Jeff is a regular contributor to Security Executive Magazine and SecurityInfoWatch.com


