ControlMonkey now supports LaunchDarkly Disaster Recovery, enabling teams to automatically back up and restore critical LaunchDarkly configurations, including feature flags, segments, and views.

LaunchDarkly controls feature rollout and targeting rules in real time, yet its configuration layer is rarely protected by a resilience solution.

Why do you need a resilience solution for LaunchDarkly? 

Feature flag platforms like LaunchDarkly are deeply embedded in your production environment meaning misconfigurations or compromises can have immediate, widespread impact.

 Here are some of the key risks teams face:

• Ransomware or account takeover –  What happens if your LaunchDarkly account is compromised? An attacker could modify or disable critical flags, impacting availability and user experience. 
• Cyber attacks / malicious actors – Unauthorized changes to feature flags can be used to expose functionality, bypass controls, or disrupt your application. 
• Human error –  Even experienced engineers can make mistakes – accidentally toggling the wrong flag or applying changes to the wrong environment. 
• Over-permissive AI agents – With the rise of AI-assisted workflows (e.g., LaunchDarkly MCP server), agents operating with admin-level permissions can unintentionally introduce risky or large-scale changes.

ControlMonkey helps teams safeguard LaunchDarkly by protecting the operational logic that defines how features are released, who sees them, and how changes are rolled out.

Examples of protected LaunchDarkly configurations include:

• Feature flags controlling runtime application behavior
• Targeting rules defining rollout logic and user exposure
• Segments used for user targeting and progressive delivery
• Views organizing feature management workflows

With this capability, teams can:

• Automatically back up LaunchDarkly configurations
• Track changes to feature flags and targeting over time
• Recover quickly from accidental changes or deletions
• Reduce risk across production release processes
• Restore feature flags and targeting logic without manual reconstruction

How LaunchDarkly Disaster Recovery Works

From discovery to recovery, ControlMonkey ensures LaunchDarkly configurations are always backed up, versioned, and ready to restore in minutes. Here is the full process:

Snapshot and Backup

• ControlMonkey continuously captures the state of LaunchDarkly configurations and creates versioned snapshots.
• This provides a reliable historical record of feature flags, segments, and targeting logic across environments.

Recover – Feature Flags, Segments, and Views

• If configurations are deleted or misconfigured, teams can restore them from a known-good snapshot in minutes.
• This eliminates manual rebuilding of feature flags and targeting rules—reducing recovery time and avoiding errors.

Review & Govern

• The ControlMonkey Cloud Resilience Dashboard provides visibility into disaster recovery readiness across infrastructure and SaaS platforms like LaunchDarkly.
• Teams can monitor protection coverage and identify resilience gaps before incidents occur.

Stay Ahead with Darkly Disaster Recovery

Feature management platforms like LaunchDarkly are critical to modern software delivery. Yet while organizations focus on application code and infrastructure, the configuration layer that controls feature rollout and targeting often remains unprotected.

ControlMonkey ensures LaunchDarkly configurations are protected alongside infrastructure and SaaS platforms. By continuously backing up configuration states and enabling rapid restoration, teams can recover quickly from outages, misconfigurations, and unintended changes—and maintain control over production behavior.

Ready to take control? Explore LaunchDarkly Disaster Recovery today.

ControlMonkey now supports Snowflake Disaster Recovery, enabling teams to automatically back up and restore critical Snowflake configurations including roles, warehouses, schemas, and access policies when mistakes or incidents occur.

Snowflake powers some of the most critical data workloads in the cloud, yet its configuration layer is rarely protected by a cyber resilience solution.

Introducing Snowflake Configuration Disaster Recovery

ControlMonkey helps teams safeguard Snowflake environments by protecting the operational configuration that keeps data platforms running.

Examples of protected Snowflake configurations include:

• Roles and grants controlling data access
• Warehouses powering compute workloads
• Databases and schemas organizing data environments
• Resource monitors and policies managing usage and governance
• Platform configuration settings critical to operational stability

With this capability, teams can:

• Automatically back up Snowflake configuration
• Track configuration changes over time
• Recover quickly from accidental changes or deletions
• Reduce operational risk across data infrastructure
• Restore Snowflake environments without manual reconstruction

How Snowflake Disaster Recovery Works

ControlMonkey connects to Snowflake using secure APIs and automatically discovers configuration assets across the Snowflake environment. This discovery process maps the operational structure of the data platform, including access controls, compute resources, and governance settings.

These configurations define how Snowflake environments operate and are essential for governance, access control, and workload management.

Snapshot and Backup

ControlMonkey continuously captures the configuration state of Snowflake resources and creates versioned snapshots of those configurations.

This provides a reliable historical, good-know state record of Snowflake configurations.

Recover – Roles, Warehouses, Schemas, and Policies

If roles, warehouses, schemas, or policies are deleted or misconfigured, teams can quickly restore them from a known-good snapshot, recovering Snowflake configuration in minutes.

This eliminates the need for manual reconstruction of complex platform settings.

Review & Govern

The ControlMonkey Cloud Resilience Dashboard provides visibility into disaster recovery readiness across cloud infrastructure, observability platforms, and SaaS tools like Snowflake.

Teams can monitor protection coverage and identify resilience gaps before incidents occur.

Stay Ahead with Snowflake Disaster Recovery

Data platforms like Snowflake are critical to modern cloud operations. Yet while organizations protect data, the configuration layer often remains vulnerable.

ControlMonkey ensures Snowflake configurations are protected alongside infrastructure and SaaS platforms. By continuously backing up configuration states and enabling rapid restoration, teams can recover quickly from ransomware, cyber attacks, AI agents and configuration mistakes and maintain operational continuity.

Ready to be Cyber Resilient?

Explore Snowflake Disaster Recovery with ControlMonkey today.

Observability Disaster Recovery is the new addtioan to Controlmonkey DR Soultion. Modern cloud operations rely heavily on observability. During incidents, dashboards, alerts, and monitoring rules are often the first place engineers turn to understand what’s happening.

Yet the configurations behind these systems – dashboards, alert policies, monitors, and escalation rules – are rarely protected by disaster recovery.

Introducing Observability Configuration Disaster Recovery

ControlMonkey now extends Cloud Configuration Disaster Recovery to observability platforms, protecting monitoring environments across Datadog, New Relic, Dynatrace, Grafana Cloud, and Splunk.

ControlMonkey automatically captures daily snapshots of observability configurations so teams can restore monitoring environments and maintain operational visibility during incidents.

Observability DR Key capabilities:

• Protect operational knowledge
  Backup dashboards, monitors, alert rules, and escalation policies created over years of operational tuning.
  
• Restore monitoring environments quickly
  Recover observability configurations from versioned snapshots instead of rebuilding manually.
  
• Detect configuration drift in monitoring systems
  Track changes across observability platforms and identify unexpected modifications.
  
• Ensure monitoring visibility during incidents
  Maintain access to critical dashboards and alerts when diagnosing outages.
  
• Extend disaster recovery beyond infrastructure
  Protect the broader cloud control plane including infrastructure, network, and observability configuration.

How does Observability Configuration Disaster Recovery Works?

ControlMonkey Cloud DR solution continuously captures configuration snapshots from supported observability platforms.

Each snapshot records the structure and settings of monitoring environments, including:

• Dashboards and visualizations
• Alert rules and alert routing policies
• Monitors across metrics, logs, and traces
• Notification channels and escalation policies
• Service monitoring and APM configurations
• Click on the image to enlarge

These configurations are versioned and stored securely, allowing teams to compare changes over time and restore previous configurations when needed.

If dashboards are deleted, alerts are misconfigured, or monitoring rules break during an incident, engineers can restore observability configurations directly from a previous snapshot – without manually rebuilding monitoring environments.

Why Disaster Recovery for the Observability Layer?

Traditional disaster recovery focuses on restoring data, storage, and infrastructure.

But modern cloud environments rely on far more than compute resources. The cloud control plane – including monitoring configuration – contains the operational knowledge engineers depend on to diagnose and resolve incidents.

With ControlMonkey, teams can:

• Maintain versioned backups of observability environments
• Detect configuration changes and drift
• Restore monitoring systems quickly during incidents
• Ensure DR visibility by having clear Resilience Score
  

By extending configuration disaster recovery to observability, ControlMonkey helps teams maintain operational continuity across the entire cloud environment.

During incidents, engineers rely on monitoring systems to understand what’s happening – yet observability configurations themselves are rarely protected by disaster recovery. As a CTO, I know firsthand how valuable it would have been to restore dashboards and monitoring environments instantly instead of rebuilding them under pressure.

Ori Yemini

CTO

Real-World Impact: Datadog dashboards, monitors, and alerting policies

Our Datadog dashboards, monitors, and alerting policies represent years of operational knowledge and tuning. Losing that configuration during an incident would significantly impact our ability to diagnose issues quickly. With ControlMonkey, we know our observability configurations are versioned and recoverable, ensuring we maintain visibility when it matters most<br />

Doron Gutman

Director of DevOps and DevSecOps

Ready to be Cyber Resilient?

Explore Cloud Configuration Disaster Recovery for Observability or schedule a demo today.

Reference Table: Key APM Configurations Used in Observability Platforms

Modern cloud operations rely on observability platforms like Dynatrace to detect incidents and maintain service reliability. But while infrastructure and data may be protected, monitoring configurations themselves are often not recoverable.

With ControlMonkey, teams can now extend Cloud Disaster Recovery to Dynatrace configuration backup – ensuring dashboards, alerts, monitors, and metrics can be restored instantly in case of incidents, misconfigurations, or ransomware.

Introducing Dynatrace Configuration Backup & Recovery

ControlMonkey now protects critical Dynatrace configurations as part of its Cloud Disaster Recovery platform.

Key capabilities include:

• Automated backup of Dynatrace dashboards, metrics, monitors, and alerts
• Versioned snapshots of monitoring configurations
• Rapid recovery of observability environments after incidents
• Resilience Score across monitoring platforms
• Unified disaster recovery method across cloud infrastructure and SaaS tools

How Dynatrace Disaster Recovery Works

ControlMonkey continuously protects Dynatrace configuration so teams can restore their monitoring environment to a known-good state when incidents occur.

Discover Dynatrace configurations

ControlMonkey connects to Dynatrace using secure APIs and automatically discovers configuration assets including dashboards, monitors, alerts, and metrics.

Snapshot and Backup

On a continuous basis, ControlMonkey captures the exact configuration state of Dynatrace resources and creates versioned snapshots of those configurations.

Recover 

If dashboards, monitors, or alerts are deleted or misconfigured, teams can quickly restore them from a good known snapshot – recovering observability environments in minutes.

Review & Govern

The ControlMonkey Cloud Resilience Dashboard provides visibility into DR readiness across cloud infrastructure and SaaS tools, helping teams identify gaps before incidents occur.

Stay Ahead with Dynatrace Disaster Recovery

As a CTO, I’m proud to introduce this capability. In my previous roles, having the ability to quickly recover from mistakes and investigate configuration changes would have saved days of troubleshooting and manual work

Ori Yemini

CTO

Observability platforms are critical for detecting and resolving incidents. If monitoring configurations are lost during an outage or attack, recovery becomes significantly harder.

ControlMonkey ensures Dynatrace configurations are protected alongside infrastructure and SaaS platforms. By continuously backing up configuration states and enabling rapid restoration, teams can maintain operational visibility even during critical incidents.

This extends disaster recovery beyond data and infrastructure – ensuring the monitoring systems themselves are resilient.

Ready to be Cyber Resilient?

Explore Dynatrace Disaster Recovery with ControlMonkey today.

Microsoft Entra ID configurations are too critical to leave not backup or unversioned. With ControlMonkey’s new Entra ID support, your identity layer now receives structured backup, visibility, and recovery coverage – just like your data and cloud infrastructure.

Why Backup and Govern Your Entra ID?

Entra ID defines who can access production systems, cloud resources, and business applications. Yet many identity changes still happen manually – without versioning, drift visibility, or rollback capabilities.

Backing up and governing Entra ID ensures:

• Configuration Cyber Resilience – Recover users, roles, groups, and policies after mistakes or incidents.
• Change Visibility – Track and review identity configuration changes over time.
• Drift Detection – Identify manual changes that bypass Infrastructure as Code.
• Audit Readiness and guardrails  – Have a clear RTO/RPO number for your Idindy layer.  Apply the same compliance guardrails across identity and infrastructure.

Introducing Support for Cyber Resilience

ControlMonkey now supports Microsoft Entra ID backup and recovery.
With this release, teams gain:

• Entra ID Visibility Inventory – Full visibility into users configuration, groups, roles polices, enterprise applications, and policies.
• IaC Blind Spot Detection – See which Entra ID resources are IaC-managed and which are not.
• Daily Entra ID Backup Snapshots – Automated configuration backups.
• Disaster Recovery Time Machine – Restore Entra ID to a previous known-good state 
• Import to IaC – Bring unmanaged identity resources under IaC control.
  

Daily configuration versioning allows teams to investigate access history, recover from misconfigurations, and ensure compliance without manual reconstruction.

Identity Resilience Meets Cloud Governance

See how ControlMonkey reduces risk and brings cyber resilience  daily backup to Entra ID. Turn your identity configuration into code – and your code into control.

Book Intro Call

Azure teams often rely on Bicep alongside Terraform for managing their infrastructure with code, and without unified visibility, recovery gaps go unnoticed until it’s too late.

ControlMonkey now supports Azure Bicep as part of its IaC coverage model, extending visibility and disaster recovery awareness to Azure-native infrastructure.

This capability is available to all ControlMonkey customers starting today.

Key benefits Azure Bicep Backup & Visibility:

• Full visibility into Azure resources managed by Bicep
• Clear separation between codified and non-codified infrastructure
• Improved disaster recovery readiness for Azure-native stacks
• Reduced blind spots during ransomware or cyber incidents
• IaC visibility and recovery coverage across Terraform, CloudFormation, and Bicep

Cloud Infrastructure with Full IaC Visibility

Codified infrastructure can be restored after configuration loss or compromise. Unmanaged resources lack a reliable recovery path.

By including Azure Bicep in its IaC coverage, ControlMonkey helps teams:

• Understand recovery readiness across Azure environments
• Identify hidden DR risks caused by non-codified resources
• Strengthen cloud governance without forcing tool migrations
• Plan incident response with confidence during cyber or ransomware event.

This helps teams understand recovery readiness in environments that use multiple IaC frameworks.

Ready to see what’s recoverable and what isn’t?

Explore Azure Bicep visibility in ControlMonkey today.

In most cloud environments, no system actually stores your cloud architecture relationships.

Security groups, routing rules, IAM permissions, load balancers, and SaaS configurations exist – but the relationships between them are not saved anywhere. When a security incident or outage occurs, teams discover too late that there is no historical record of how resources were connected, what depended on what, or how access paths were structured at the time things worked.

Introducing Architecture Time Machine

Architecture Time Machine is a capability within the ControlMonkey IaC Automation Platform that preserves your cloud architecture and security posture on a timeline.

Architecture Time Machine extends ControlMonkey’s Cloud Resilience platform by preserving your cloud architecture and resource dependencies over time, not just the resources themselves.

With daily environment snapshots, you can move backward on a timeline and explore how your infrastructure was connected at any point in time.

Key benefits:

• Rewind cloud architecture in time – View how resources and dependencies looked on any given day.
• Explore historical dependencies – Understand what was connected to what before a change or incident.
• Speed up incident investigation – Quickly answer “what changed?” without guesswork.
• Visualize complex environments – Interactive dependency graphs make large architectures easier to reason about.
• Reduce recovery blind spots – Restore with architectural confidence, not assumptions.

Who Benefits from Architecture Time Machine

Cloud & DevOps Managers – Get immediate answers during incidents. Understand what changed without relying on tribal knowledge or manual reconstruction.

Security & Compliance Teams – Validate historical configurations for audits (SOC, PCI, internal reviews) and investigate configuration drift over time.

Cloud Architects – Review how architecture evolved over time, Identify unintended complexity, sprawl, or anti-pattern, Use historical views to guide standardization and governance decision

CIO & CISO:

• Gain confidence that cloud recovery is predictable and provable
• Reduce operational and compliance risk tied to configuration loss
• Understand recovery readiness without diving into technical detail

Controlmonkey Cloud Disaster Recovery – for Configuration

When traffic drops, services break, or behavior changes unexpectedly, the root cause is often a dependency change – a security group update, a route table modification, or a detached resource.

Architecture Time Machine helps you:

• Improve visibility into historical cloud states
• Reduce risk during incident response and postmortems
• Strengthen alignment between IaC, reality, and recovery
• Scale cloud environments with confidence, knowing you can always look back

Get Started: Cloud DR Readiness Assessment

Before the next audit or incident, understand your real recovery risk.

The Cloud DR Readiness Assessment gives security and compliance leaders a clear, executive-level view of cloud configuration recovery — without disrupting production.

As CDN footprints grow, Fastly configuration becomes production-critical. A single accidental change or deletion can take performance, availability, and security with it – fast.

Introducing Fastly Backup

ControlMonkey now supports Fastly with daily backups designed to keep your CDN setup recoverable and governed.

• Recover Fastly config fast when mistakes happen
• Reduce outage risk from accidental deletions and misconfigurations
• Protect WAF posture by backing up key Next-Gen WAF rules and thresholds
• Keep teams aligned with consistent, auditable configuration state
• Scale safely as services and edge compute expand

Supported Fastly resource types (daily backup):

• Next-Gen WAF Account Rule
• Next-Gen WAF Threshold
• Service
• Compute service

Benfits of Fastly and Controlmonkey Intergation

Fastly often sits directly in the blast radius of incidents – because it’s on the delivery to your customers path. ControlMonkey Backup for Fastly turns a high-pressure scramble into a controlled recovery.

With ControlMonkey, Fastly configurations are:

• RTO-ready – restore from the latest daily backup (clear recovery point, predictable path)
• More resilient – reduce impact from drift, bad changes, and ClickOps
• Governed – strengthen alignment between running configuration and your IaC intent
• Auditable – maintain a consistent record of what changed and when
• Scalable – keep protection in place as you add services and edge workloads
  

Ready to protect your CDN layer?

Explore Fastly Backup today – your workflow infrastructure recoverable, governed, and under control.

As workflow-driven systems scale, Temporal becomes a core dependency for long-running processes and background jobs. If Temporal Cloud configuration is deleted or drifts unexpectedly, workflows can fail, environments can break, and recovery turns into manual rebuilds. ControlMonkey now supports Temporal Backup so teams can restore critical workflow infrastructure configuration from a known-good daily snapshot.

Introducing Temporal Backup

Temporal is a workflow engine for running reliable, long-running processes. It powers application workflows, stateful execution, and durable background jobs—at scale.

With ControlMonkey support for Temporal Cloud, customers get daily backups of key Temporal Cloud resources, including:

• Namespaces
• Groups
• Nexus Endpoints
• Connectivity Rules

And additional supported Temporal Cloud configuration resources.

ControlMonkey Backups are captured as IaC, so recovery is repeatable and auditable.

Benfits of Temporal Backup

Temporal Cloud configuration changes are operational risk – especially when multiple teams and environments are involved. Backups provide a safety net when something goes wrong.

Temporal Cloud Backup helps teams:

• Recover faster from accidental deletions and misconfigurations
• Reduce risk from unmanaged changes and configuration drift
• Keep IaC alignment for workflow infrastructure, not just application code
• Audit changes and restore from known-good states

Ready to gain Temporal Cloud backup?

Explore Temporal Cloud Backup and keep your workflow infrastructure recoverable, governed, and under control..

As organizations rely on real-time data pipelines, the configuration layer behind New Relic Disaster Recovery and Back-up is now available in ControlMonkey, giving DevOps teams a reliable way to back up and restore New Relic APM configurations just like they backup their cloud infrastructure.

New Relic is a core Application Performance Monitoring (APM) platform used for live operations – powering dashboards, alerts, and incident response during production outages. Losing or misconfiguring it means losing visibility when it matters most.

How ControlMonkey Protects Your New Relic Configuration

ControlMonkey’s New Relic integration delivers automated New Relic backup and disaster recovery, fully managed through Terraform or OpenTufo and aligned with your cloud resources.

ControlMonkey continuously discovers existing New Relic configurations and creates daily snapshots of the full APM configuration live state, and stores them as a governed, versioned source of truth. In the event of an outage, misconfiguration, or deletion, teams can restore New Relic configurations alongside the cloud resources they monitor.

What You Get with New Relic Backup

With ControlMonkey, you can:

• Automatically back up all New Relic configurations on a daily basis
• Restore dashboards, alerts, and APM policies after outages or human error
• Recover New Relic configurations tied to affected cloud resources
• Maintain a governed, auditable source of truth for observability infrastructure

Why New Relic Needs Backup and Disaster Recovery?

New Relic is used for ongoing application and infrastructure monitoring. If its configuration is deleted or altered, teams lose monitoring and alerting during incident response and then they face undefined RTO (Recovery Time Objective) for observability. Monitoring and alerting must be rebuilt manually, delaying visibility during active incidents.

New Relic disaster recovery defines and reduces observability RTO by enabling fast, consistent restoration of monitoring configurations.

Benefits of ControlMonkey New Release Integration:

ControlMonkey ensures your New Relic environment is:

• Recoverable – Restore full APM configuration from backups
• Resilient – Protect monitoring setups from deletions and misconfigurations
• Governed – Enforce IaC alignment
• Scalable – Protect New Relic as environments grow

Ready to protect your observability stack?

Explore New Relic Disaster Recovery with ControlMonkey today.