Skip to main content

Turning Foresight into Resilience: Reclaiming Prevention in the Age of Exposure

Garrett Hamilton
Reach Security

Cloudflare's recent outage is a stark reminder of how concentrated the internet has become. When a single infrastructure provider experiences disruption, the impact is immediate and global. In this case, a faulty internal database configuration bloated a key file, disrupting services worldwide until engineers rolled back the change. While there was no evidence of malicious activity, the incident underscores a broader issue: even routine anomalies can create outsized operational risk.

Cloudflare's disruption illustrates how quickly a single provider's issue cascades into widespread exposure. Many organizations don't fully realize how tightly their systems are coupled to thirdparty services, or how quickly availability and security concerns align when those services falter. Centralization delivers convenience and protection, but it also creates single points of failure that amplify the fallout.

You can't avoid these dependencies, but you can understand them. Continuous visibility, configuration awareness, and clarity around where infrastructure is fragile are now essential parts of modern resilience. Whether it's an outage or an attack, the question remains the same: where are you exposed, when the platforms you rely on stumble?

From Hindsight to Foresight

Exposure isn't limited to external providers, it often exists inside the enterprise itself. Security teams are often told to assume breaches have already occurred and focus on detection, investigation, and recovery. Yet postmortems frequently reveal that organizations already owned tools capable of preventing the incident — they simply weren't configured properly or maintained.

Rather than relying on hindsight, the industry must turn foresight into action. That means shifting security "left of boom" and helping businesses optimize the investments they've already made. The challenge lies in understanding complex environments and overcoming governance issues that hinder proactive defense.

Why Exposure Management Matters

Exposure management has become essential because modern organizations face an everexpanding attack surface. Businesses now operate across onpremises systems, cloud platforms, mobile devices, and thirdparty services, each introducing potential entry points for attackers. The sheer scale and diversity of these environments make it increasingly difficult to maintain visibility and control using traditional methods.

Older vulnerability management approaches, which focused narrowly on patching known flaws, are no longer sufficient. Exposure management goes further by continuously monitoring misconfigurations, identity gaps, and overlooked assets. This broader scope ensures that risks beyond simple vulnerabilities are identified and addressed, helping organizations stay ahead of adversaries who exploit weaknesses quickly.

Another problem is the complexity of today's tool environments. Security architects manage sprawling stacks, often with dozens of point solutions added over time. It's not unusual for a single organization to run 75 different tools, each with constant patches and updates. In 2024 alone, we counted the top 20 security tools released 380 new features. This fragmentation leaves valuable data locked away and risks hidden from view. With each tool offering multiple independent controls, the combinations are overwhelming. Teams risk burnout, mistakes, or paralysis, leaving businesses exposed despite heavy investment.

Visibility compounds the problem. Tools often operate in siloes, preventing data from being shared to strengthen defenses. Ownership issues add another layer: identity and access management (IAM) may sit with IT, limiting security architects' insight into configurations or licensing and eroding their authority to request changes for security reasons. Tracking coverage and configurations becomes a neverending task, akin to painting the Golden Gate Bridge. Reporting meaningful risk reduction to boards in such fragmented environments is equally difficult.

The result is a reactive posture that lags behind adversaries. To shift toward prevention, organizations must maximize value from existing tools, gain timely visibility into exposures, and establish measurable risk reduction strategies. Exposure assessment platforms (EAPs) help by identifying misconfigurations, but they often lack context, prioritization, and actionable fixes.

The Role of Agentic AI

Agentic AI introduces a new approach to managing exposures. Unlike static reporting, AI can contextualize exposures, prioritize them by risk, and generate actionable tickets specifying how and where fixes should occur. In advanced environments, AI agents could even implement staged fixes automatically, leaving teams to validate before deployment.

By addressing tool sprawl and configuration drift, this approach enables continuous monitoring and proactive remediation. It helps security architects move beyond surfacing risks to actually resolving them, ensuring systems remain in an optimal state even as they evolve.

Prevention Reclaimed

The next era of cybersecurity must leverage existing investments more intelligently. Prevention should once again be central, not overshadowed by detection and response. Agentic AI provides a pathway to proactive defense, helping organizations harden systems, close exploitable gaps, and stem the tide of preventable breaches.

Cloudflare's outage may have been caused by a simple misconfiguration, but its ripple effects demonstrate the scale of exposure in today's interconnected world. Organizations that embrace exposure management will be better positioned to withstand both routine anomalies and deliberate attacks, turning foresight into resilience.

Garrett Hamilton is CEO and Co-Founder of Reach Security

The Latest

Production incidents rarely announce themselves as database problems. They appear as slow transactions, timeouts, rising response times, or an application struggling under a workload it previously handled. APM provides an essential starting point. It can identify a slow transaction path, highlight an affected service, and show that a database dependency is consuming more time than expected. But identifying the database as part of the problem is not the same as explaining what is happening inside it ...

Cloud teams are under constant pressure to reduce spend without slowing development or increasing operational risk. They are deploying autoscalers, rightsizing workloads, enforcing resource requests, reviewing utilization dashboards, and building FinOps processes around cloud-native environments. Yet the results often disappoint ...

Ask most IT leaders about their biggest concern with AI and you'll hear the same answer: hallucinations ... Today, however, the conversation has shifted ... As organizations move beyond chatbots and experiments, they are increasingly deploying AI agents that perform multi-step tasks. These systems retrieve documents, query databases, call APIs, generate reports, write code, and make recommendations. The issue is not whether the model can reason. The issue is whether the organization can see, verify, and govern the decisions being made along the way ...

While organizations want to take control of their telemetry, building telemetry pipelines from scratch can be a very daunting, complicated task, even when leveraging open-source standards like OpenTelemetry. It requires specialized knowledge across distributed systems, data engineering, and security. This fragmented approach across systems causes higher operational costs; it puts a strain on resources and reduces efficiency as teams have to work with different interfaces and processes ...

For decades, enterprise networks were designed around a simple assumption: work happened inside the office. Applications lived in centralized data centers, employees connected through internal infrastructure, and security focused on protecting the perimeter that surrounded everything ... But the way organizations operate today bears little resemblance to that environment. Cloud platforms host critical applications, employees connect from homes and airports as often as they do from offices, and partners collaborate through shared systems that exist far beyond corporate walls. In short, the corporate network no longer resembles the environment it was designed to protect ...

As an analyst who researches how IT organizations design, build, and operate their networks, I find that network data is a constant source of pain. Network teams struggle with data quality, fragmentation, authority, access, and trust. And these issues undermine everything they try to do. Here are the numbers: Only 45% of network teams are completely confident in the accuracy of their network source of truth, which documents the intent of their network ...

The 2026 Global Data Center Survey from Uptime Institute reveals an industry navigating workforce constraints, escalating outage expenses, even as rising costs remain the top concern for management teams ...

The next observability gap may not be in the code. It may be under the rack. That sounds strange until you think about how AI incidents actually feel in the middle of an investigation ... The application dashboard may be accurate. It may also be stopping at the wrong boundary. AI systems depend on software, but they also depend on a dense physical stack: racks, power paths, thermal margin, maintenance activity and, in many environments, liquid cooling. Those physical dependencies can change slowly before they look like a software incident ...

Certificate expiration is the rare outage you can see coming. Every TLS certificate carries the date it stops working, so the moment it will begin breaking connections is knowable in advance. That's what makes an expired certificate such a frustrating way to lose a service. What's changing now is how often that date comes around ...

Enterprises operate different combinations of workloads across cloud, hybrid and multicloud environments. For business-critical workloads, teams need to consider monitoring and observability early so they can detect health issues, investigate failures, and understand operational impact. Organizations place workloads on cloud platforms based on a combination of technical requirements, economics, existing dependencies, organizational standards, and business priorities. Their monitoring priorities therefore depend on what they operate and where those systems run. Those priorities will not look the same for every organization ...

Turning Foresight into Resilience: Reclaiming Prevention in the Age of Exposure

Garrett Hamilton
Reach Security

Cloudflare's recent outage is a stark reminder of how concentrated the internet has become. When a single infrastructure provider experiences disruption, the impact is immediate and global. In this case, a faulty internal database configuration bloated a key file, disrupting services worldwide until engineers rolled back the change. While there was no evidence of malicious activity, the incident underscores a broader issue: even routine anomalies can create outsized operational risk.

Cloudflare's disruption illustrates how quickly a single provider's issue cascades into widespread exposure. Many organizations don't fully realize how tightly their systems are coupled to thirdparty services, or how quickly availability and security concerns align when those services falter. Centralization delivers convenience and protection, but it also creates single points of failure that amplify the fallout.

You can't avoid these dependencies, but you can understand them. Continuous visibility, configuration awareness, and clarity around where infrastructure is fragile are now essential parts of modern resilience. Whether it's an outage or an attack, the question remains the same: where are you exposed, when the platforms you rely on stumble?

From Hindsight to Foresight

Exposure isn't limited to external providers, it often exists inside the enterprise itself. Security teams are often told to assume breaches have already occurred and focus on detection, investigation, and recovery. Yet postmortems frequently reveal that organizations already owned tools capable of preventing the incident — they simply weren't configured properly or maintained.

Rather than relying on hindsight, the industry must turn foresight into action. That means shifting security "left of boom" and helping businesses optimize the investments they've already made. The challenge lies in understanding complex environments and overcoming governance issues that hinder proactive defense.

Why Exposure Management Matters

Exposure management has become essential because modern organizations face an everexpanding attack surface. Businesses now operate across onpremises systems, cloud platforms, mobile devices, and thirdparty services, each introducing potential entry points for attackers. The sheer scale and diversity of these environments make it increasingly difficult to maintain visibility and control using traditional methods.

Older vulnerability management approaches, which focused narrowly on patching known flaws, are no longer sufficient. Exposure management goes further by continuously monitoring misconfigurations, identity gaps, and overlooked assets. This broader scope ensures that risks beyond simple vulnerabilities are identified and addressed, helping organizations stay ahead of adversaries who exploit weaknesses quickly.

Another problem is the complexity of today's tool environments. Security architects manage sprawling stacks, often with dozens of point solutions added over time. It's not unusual for a single organization to run 75 different tools, each with constant patches and updates. In 2024 alone, we counted the top 20 security tools released 380 new features. This fragmentation leaves valuable data locked away and risks hidden from view. With each tool offering multiple independent controls, the combinations are overwhelming. Teams risk burnout, mistakes, or paralysis, leaving businesses exposed despite heavy investment.

Visibility compounds the problem. Tools often operate in siloes, preventing data from being shared to strengthen defenses. Ownership issues add another layer: identity and access management (IAM) may sit with IT, limiting security architects' insight into configurations or licensing and eroding their authority to request changes for security reasons. Tracking coverage and configurations becomes a neverending task, akin to painting the Golden Gate Bridge. Reporting meaningful risk reduction to boards in such fragmented environments is equally difficult.

The result is a reactive posture that lags behind adversaries. To shift toward prevention, organizations must maximize value from existing tools, gain timely visibility into exposures, and establish measurable risk reduction strategies. Exposure assessment platforms (EAPs) help by identifying misconfigurations, but they often lack context, prioritization, and actionable fixes.

The Role of Agentic AI

Agentic AI introduces a new approach to managing exposures. Unlike static reporting, AI can contextualize exposures, prioritize them by risk, and generate actionable tickets specifying how and where fixes should occur. In advanced environments, AI agents could even implement staged fixes automatically, leaving teams to validate before deployment.

By addressing tool sprawl and configuration drift, this approach enables continuous monitoring and proactive remediation. It helps security architects move beyond surfacing risks to actually resolving them, ensuring systems remain in an optimal state even as they evolve.

Prevention Reclaimed

The next era of cybersecurity must leverage existing investments more intelligently. Prevention should once again be central, not overshadowed by detection and response. Agentic AI provides a pathway to proactive defense, helping organizations harden systems, close exploitable gaps, and stem the tide of preventable breaches.

Cloudflare's outage may have been caused by a simple misconfiguration, but its ripple effects demonstrate the scale of exposure in today's interconnected world. Organizations that embrace exposure management will be better positioned to withstand both routine anomalies and deliberate attacks, turning foresight into resilience.

Garrett Hamilton is CEO and Co-Founder of Reach Security

The Latest

Production incidents rarely announce themselves as database problems. They appear as slow transactions, timeouts, rising response times, or an application struggling under a workload it previously handled. APM provides an essential starting point. It can identify a slow transaction path, highlight an affected service, and show that a database dependency is consuming more time than expected. But identifying the database as part of the problem is not the same as explaining what is happening inside it ...

Cloud teams are under constant pressure to reduce spend without slowing development or increasing operational risk. They are deploying autoscalers, rightsizing workloads, enforcing resource requests, reviewing utilization dashboards, and building FinOps processes around cloud-native environments. Yet the results often disappoint ...

Ask most IT leaders about their biggest concern with AI and you'll hear the same answer: hallucinations ... Today, however, the conversation has shifted ... As organizations move beyond chatbots and experiments, they are increasingly deploying AI agents that perform multi-step tasks. These systems retrieve documents, query databases, call APIs, generate reports, write code, and make recommendations. The issue is not whether the model can reason. The issue is whether the organization can see, verify, and govern the decisions being made along the way ...

While organizations want to take control of their telemetry, building telemetry pipelines from scratch can be a very daunting, complicated task, even when leveraging open-source standards like OpenTelemetry. It requires specialized knowledge across distributed systems, data engineering, and security. This fragmented approach across systems causes higher operational costs; it puts a strain on resources and reduces efficiency as teams have to work with different interfaces and processes ...

For decades, enterprise networks were designed around a simple assumption: work happened inside the office. Applications lived in centralized data centers, employees connected through internal infrastructure, and security focused on protecting the perimeter that surrounded everything ... But the way organizations operate today bears little resemblance to that environment. Cloud platforms host critical applications, employees connect from homes and airports as often as they do from offices, and partners collaborate through shared systems that exist far beyond corporate walls. In short, the corporate network no longer resembles the environment it was designed to protect ...

As an analyst who researches how IT organizations design, build, and operate their networks, I find that network data is a constant source of pain. Network teams struggle with data quality, fragmentation, authority, access, and trust. And these issues undermine everything they try to do. Here are the numbers: Only 45% of network teams are completely confident in the accuracy of their network source of truth, which documents the intent of their network ...

The 2026 Global Data Center Survey from Uptime Institute reveals an industry navigating workforce constraints, escalating outage expenses, even as rising costs remain the top concern for management teams ...

The next observability gap may not be in the code. It may be under the rack. That sounds strange until you think about how AI incidents actually feel in the middle of an investigation ... The application dashboard may be accurate. It may also be stopping at the wrong boundary. AI systems depend on software, but they also depend on a dense physical stack: racks, power paths, thermal margin, maintenance activity and, in many environments, liquid cooling. Those physical dependencies can change slowly before they look like a software incident ...

Certificate expiration is the rare outage you can see coming. Every TLS certificate carries the date it stops working, so the moment it will begin breaking connections is knowable in advance. That's what makes an expired certificate such a frustrating way to lose a service. What's changing now is how often that date comes around ...

Enterprises operate different combinations of workloads across cloud, hybrid and multicloud environments. For business-critical workloads, teams need to consider monitoring and observability early so they can detect health issues, investigate failures, and understand operational impact. Organizations place workloads on cloud platforms based on a combination of technical requirements, economics, existing dependencies, organizational standards, and business priorities. Their monitoring priorities therefore depend on what they operate and where those systems run. Those priorities will not look the same for every organization ...