{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreihmtjkigbgjrjn5r3wphnj4mdboowls5btkhe5pegkikjoquecboe",
    "uri": "at://did:plc:qzjwstutqk2cy7df7jbzd2hx/app.bsky.feed.post/3mfpjrtkmnih2"
  },
  "coverImage": {
    "$type": "blob",
    "ref": {
      "$link": "bafkreighlnklrndzpamj2icqie67ugnhn2mgfh32gbvnhzxhxpq3zojdbe"
    },
    "mimeType": "image/jpeg",
    "size": 4360614
  },
  "path": "/article/4137501/controlmonkey-extends-configuration-disaster-recovery-to-cloud-network-vendors.html",
  "publishedAt": "2026-02-25T19:43:35.000Z",
  "site": "https://www.networkworld.com",
  "tags": [
    "Data Center, Disaster Recovery, Network Management Software, Networking",
    "Cloud Configuration Disaster Recovery",
    "Aharon Twizer"
  ],
  "textContent": "Network resiliency is about more than just DNS redundancy and using multiple regions and providers. It also requires extending resiliency to network configuration. That’s the challenge that cloud infrastructure automation startup ControlMonkey is now taking on.\n\nControlMonkey launched its Cloud Configuration Disaster Recovery capability in 2025, targeting AWS, Azure and GCP infrastructure. Today the company is expanding its configuration-level disaster recovery platform to the network control plane—specifically to the CDN configurations, firewall rules, DNS records, route tables and edge routing policies that sit outside the major cloud providers but are critical to production uptime. That support brings configuration backup capabilities for Cloudflare, Akamai, Fastly, and F5.\n\nThe goal is to close what is likely a gap in the resilience and disaster recovery posture for many organizations.\n\n“Everybody backs up their data, right? You have to be crazy not to back up your data,” Aharon Twizer, CEO and co-founder of ControlMonkey, told _Network World_. “What about your networking configuration? If your networking is down, it’s amazing that you have data, but you’re not going to get any traffic.”\n\n## How ControlMonkey addresses the network configuration gap\n\nThe expansion came from customer requests for coverage beyond AWS, Azure, and Google Cloud Platform. Twizer, citing his own customer conversations, said the gap for third-party network vendors is larger than it is for cloud infrastructure\n\n“If you look at the third party, like 90% of the people I talk to, they don’t manage their Cloudflare with Terraform, they don’t manage their Akamai with Terraform, they don’t manage their F5 with Terraform,” Twizer noted. “So, they have zero coverage.”\n\nControlMonkey uses the Terraform Infrastructure-as-Code (IaC) technology to define the environment. The platform connects to each supported vendor and reverse engineers live configurations into Terraform HCL code. It then creates versioned snapshots on a daily basis.\n\nThe workflow has three phases. First, the platform performs a full asset inventory after connecting a vendor. Second, it identifies which resources have no code coverage and flags them for the operator. Third, it enables daily configuration snapshots so teams have a known-good state to recover from.\n\n“The way to back up your configuration is with infrastructure as code,” Twizer explained. “We specifically do that with Terraform, and our core technology, our secret sauce, is to take providers or vendors of infrastructure and reverse engineer existing configuration, live configuration, to code.”\n\nRecovery is executed through a one-click restore. When an incident occurs, the platform uses Terraform automation to provision the last known-good configuration into a second tenant. Customers can also use ControlMonkey APIs to build automated recovery playbooks triggered from external alerting tools such as PagerDuty or Datadog.\n\n## Scope: Configuration recovery, not vendor availability\n\nTo be clear, ControlMonkey isn’t a solution that will solve the issue of provider outages. The platform addresses configuration recovery, not vendor availability monitoring.\n\nThe primary scenario ControlMonkey is designed for is a ransomware attack that deletes or corrupts network configurations rather than data. In that situation, workloads and data may be intact but the network control plane is gone and applications become unreachable.\n\nIf there’s an outage for the vendor in general, “there’s nothing we can do about it, really,” Twizer said. “We’re looking more at ransomware, we’re looking more at cyberattacks, we’re looking more at AI agents that make mistakes and honest mistakes by employees.”\n\nThe platform also does not provide multi-vendor failover recommendations. It shows recovery posture for existing vendor configurations, not routing guidance to alternative providers.\n\n## Roadmap points beyond networking\n\nNetwork vendors are not the end of the expansion. Twizer said customer requests are driving coverage into additional vendor categories beyond cloud and networking, with the platform eventually targeting any third-party service that enterprises rely on for production operations. Compliance is also a factor. SOC 2 and ISO 27001 both address disaster recovery and business continuity planning, and ControlMonkey positions configuration recovery as part of that cycle alongside data protection.\n\nTwizer said the thinking behind the expansion comes back to a straightforward gap in how most organizations define resilience today.\n\n“Cyber resilience in 2026 is about data, about infrastructure, and about your network control plane,” Twizer said. “You need to have all three of them. If you just have one or two, basically, you’re not resilient.”",
  "title": "ControlMonkey extends configuration disaster recovery to cloud network vendors"
}