ControlMonkey is expanding its Cyber Resilience Platform with backup and recovery coverage for Coralogix, helping teams protect the observability configurations that keep cloud operations running.

As ransomware attacks, compromised credentials, and over-permissive AI agents introduce new risks to cloud and SaaS environments, observability configurations have become a critical resilience layer. With Coralogix Backup, ControlMonkey helps DevOps, SRE, and platform teams back up and recover critical Coralogix configurations including dashboards, alerts, global routers, and webhooks – so monitoring and incident response workflows can be restored quickly after unwanted changes, deletion, misconfiguration, or malicious activity.

Introducing Coralogix Backup

Coralogix Backup extends ControlMonkey’s cyber resilience coverage into observability, giving teams a safer way to protect critical operational configurations and recover quickly when something goes wrong.

• Protect key Coralogix configurations – back up dashboards, alerts, global routers, and webhooks.
• Recover from cyber incidents faster – restore configurations impacted by ransomware, malicious changes, or compromised access.
• Reduce AI-driven change risk – protect observability workflows from over-permissive AI agents that hallucinate and make wrong configuration changes.
• Limit monitoring disruption– keep dashboards, alerts, and routing workflows available when teams need them most.
• Strengthen cyber resilience – make observability recovery part of your broader cloud disaster recovery strategy.

How does Coralogix Backup work?

ControlMonkey connects to your Coralogix environment and automatically backs up supported configurations, including dashboards, alerts, global routers, and webhooks. If a configuration is deleted, changed, misconfigured, or impacted by a cyber incident, teams can use ControlMonkey to quickly restore the previous version and reduce manual recovery work.

Make Coralogix Recovery Part of Your Cyber Resilience Strategy

Coralogix plays a critical role in how teams monitor services, investigate issues, route incidents, and trigger downstream workflows. Dashboards help teams understand system health, alerts notify the right owners, global routers support routing logic, and webhooks connect Coralogix to the wider incident response process.

When these configurations are not protected, the risk goes far beyond manual mistakes. Ransomware can disrupt operational systems. Compromised credentials can change or delete alerting logic. Over-permissive AI agents can modify dashboards, routing rules, or webhooks at machine speed. Even one broken alert or misconfigured router can create blind spots during an incident.

ControlMonkey and Coralogix Backup

With ControlMonkey, teams can bring backup and recovery to Coralogix configurations as part of a broader cyber resilience strategy. By protecting dashboards, alerts, global routers, and webhooks, organizations can improve visibility, reduce recovery risk, and keep observability operations consistent.

Coralogix Backup also helps teams move from manual recovery to structured resilience. Instead of relying on screenshots, tribal knowledge, or manual rebuilds, teams can restore critical observability configurations with confidence and scale resilience practices across cloud and DevOps environments.

Ready to Protect Your Coralogix Configurations?

ControlMonkey helps teams strengthen cyber resilience by backing up and recovering the configurations that keep cloud operations running – across infrastructure, SaaS platforms, and observability tools like Coralogix.

Ready to take control? Explore Coralogix Backup today.

ControlMonkey Cyber Resilience Platform now supports GitLab Backup and Recovery, helping DevOps, Platform Engineering, SRE, and Security teams protect and recover the GitLab configuration that keeps software delivery running.

Recent incidents across developer platforms show that DevOps configuration is now its own resilience risk category. The Grafana GitHub token breach and CISA warnings about malicious GitHub Actions workflows show how attackers can target the systems that control software delivery – from repositories and workflow configuration to credentials, permissions, access policies, and CI/CD pipelines.

While these examples involved GitHub, the same risk category applies to GitLab. GitLab also depends on a configuration layer that controls projects, groups, users, roles, permissions, CI/CD settings, and access policies. If that layer is deleted, changed, exposed, or misused, teams need a reliable way to recover a known-good state. 

These examples involved GitHub, but the same category of risk exists in GitLab. GitLab also acts as an operational control plane for engineering teams, with projects, groups, users, roles, permissions, CI/CD settings, and access policies shaping how software is built and deployed. If that configuration layer is deleted, changed, exposed, or misused, teams need a reliable way to recover a known-good state.

Introducing GitLab Backup and Recovery

ControlMonkey GitLab Backup and Recovery helps DevOps, Platform Engineering, SRE, and Security teams protect the configuration layer behind GitLab operations.

With this new capability, teams can:

• Continuously back up GitLab configuration
  Capture branch protection rules, member roles, projects, and environment configurations as versioned recovery points.
• Recover known-good configuration
  Restore GitLab configuration after accidental deletion, misconfiguration, unauthorized change, ransomware impact, or failed automation.
• Improve disaster recovery readiness
  Understand which GitLab configurations are protected, where recovery gaps exist, and what still needs coverage.
• Reduce manual recovery effort
  Give teams a repeatable recovery path instead of relying on tribal knowledge, screenshots, or manual reconstruction during an incident.
• Strengthen governance and auditability
  Track what changed, when it changed, and which configuration state can be recovered.

GitLab Operational Resilience Depends on More Than Repository Content.

Traditional backup protects code and data. But GitLab operational resilience depends on more than repository content.

Repositories, groups, permissions, CI/CD settings, access policies, and operational configurations all shape how software moves through the organization. If those settings are changed by mistake, deleted, damaged by ransomware, or modified by an over-permissive AI agent, teams need a fast and controlled way to recover.

ControlMonkey GitLab Backup and Recovery continuously captures GitLab configuration snapshots, tracks changes over time, and helps teams restore known-good configurations when something breaks.

ControlMonkey Approach 

The new capability extends ControlMonkey’s broader Cloud Configuration Disaster Recovery approach: 

1. Discover what exists
2. Create versioned recovery points
3. Give teams a controlled path to restore the operational state of critical cloud and SaaS environments.

GitLab is not only where code lives. For many organizations, it is part of the operational backbone of software delivery.If GitLab configuration is lost or changed unexpectedly, hundreds of engineers could be blocked from working… Teams needs a way  to restore the configurations required to keep engineering moving.

Ori Yemni

CTO

GitLab Backup and Recovery joins ControlMonkey’s growing coverage for cloud infrastructure and third-party configuration, including identity, networking, observability, DevOps tools, and SaaS platforms.

ControlMonkey is a Cyber Resilience Platform for Cloud Configuration Disaster Recovery. Traditional backup restores data. ControlMonkey restores the configuration required to operate.

Ready to protect your GitLab configuration? Explore GitLab Backup and Recovery today.

ControlMonkey is expanding its Cyber Resilience Platform with Data Backup Correlation, a new capability that helps CISOs and cloud teams understand whether critical data sources are protected, whether recovery points are available, and where backup-related recovery risk exists across the cloud.

The first release supports AWS Backup and Azure Backup.

The Problem: Backup Visibility is Still Fragmented

Most enterprises already invest in data backup tools and cloud-native backup services. But CISOs and cloud teams often lack full visibility into backup coverage and available recovery points across critical data sources, including databases, storage accounts, and cloud data services.

If a backup is disabled, a retention policy is changed, or a recovery setup is modified, the right teams may not know until an incident occurs.

That visibility gap can delay recovery, increase RPO exposure, lead to revenue loss, and create compliance risk.

Why this matters now

Data backup posture can change at the worst possible time. Ransomware attacks may target backup coverage before disrupting systems. Over-permissive AI agents or automation can modify cloud resources, policies, or recovery settings faster than teams can manually track. Human error can also disable backups, change retention policies, or leave recovery points missing.

When those changes are not visible across security and cloud teams, recovery plans become assumptions.

What ControlMonkey Data Backup Correlation does

Data Backup Correlation alerts teams when backup coverage changes, retention policies are violated, recovery points are missing, or expected RPO targets are at risk – then helps prioritize what to fix first based on recovery risk and business impact.

The capability also identifies missing backups, monitors RPO compliance, reviews available recovery points, and detects cross-region or cross-account protection gaps.

Why it matters for cyber resilience

Recovery is not only about having backups. Teams need to know:

• Which data sources are protected
• Which recovery points are available
• Which assets are missing backup coverage
• Which data sources are at risk of breaching RPO targets
• Which issues should be addressed first

ControlMonkey already helps organizations protect and recover cloud and SaaS configuration, including cloud resources, networking, DNS, identity, security policies, observability dashboards, repositories, and third-party configurations.

With Data Backup Correlation, ControlMonkey adds data backup posture into the same resilience view, helping organizations connect data protection status with the infrastructure, configuration, and services those data assets depend on.

Key capabilities

Unified visibility into backup coverage, available recovery points, and recovery risk across critical cloud data sources. Full Breakdown include:

• See backup coverage across critical cloud data sources
• Review available recovery points for databases, storage accounts, and cloud data services
• Identify unprotected data assets and backup gaps
• Detect data sources breaching defined RPO targets
• Monitor backup SLA and recovery policy compliance
• Identify missing cross-region and cross-account protection
• Correlate existing data backups with cloud infrastructure and configuration
• Prioritize recovery planning based on dependencies, business impact, and recovery risk

Supported in the first release – AWS Backup and Azure Backup

Data Backup Correlation is available first for:

• AWS Backup
• Azure Backup

Support for additional enterprise backup platforms, including Rubrik, Veeam, Commvault, Cohesity, and others, is planned for future releases.

Built for a broader resilience picture

Data Backup Correlation expands ControlMonkey’s Cyber Resilience Platform by bringing data backup posture into the same recovery view as cloud and SaaS configuration.

The result is a broader recovery picture across configuration and data protection systems – helping teams move from fragmented visibility to a unified control plane for resilience.

PAN-OS Backup and Recovery is now supported in ControlMonkey Cyber Resilience Platform. 

Many Networking, NetOps, and security teams manage critical firewall configurations in Palo Alto Networks PAN-OS, including security policies, NAT rules, objects, routing, VPNs, and device settings.

When it comes to DR strategy, firewall configurations are often overlooked.
A deleted rule, misconfiguration, over-permissive AI agent, ransomware attack, or risky automated change can disrupt connectivity and create significant security and operational risk.

ControlMonkey now supports PAN-OS Backup and Recovery, helping teams back up, track, compare, and recover critical firewall configurations before issues become business disruptions.

Introducing PAN-OS Backup and Recovery

With ControlMonkey’s PAN-OS Backup and Recovery support, teams can gain control over the firewall configuration layer that protects applications, cloud environments, and business-critical networks.

ControlMonkey helps teams automatically back up, track, compare, and recover critical Palo Alto Networks PAN-OS configurations, including:

• Security policies and firewall rules
• NAT rules and policy configurations
• Address objects and address groups
• Service objects and service groups
• Zones and interface configurations
• Routing-related configurations
• VPN and connectivity settings
• Device and system configuration settings
• User access, permissions, and administrative settings

This gives infrastructure, NetOps, and security teams a reliable way to understand what changed, when it changed, and how to recover when a configuration is deleted, misconfigured, damaged, or changed by an over-permissive AI agent or ransomware attack.

Why PAN-OS Backup and Recovery Matters

Palo Alto Networks firewalls are critical to enterprise security, protecting cloud environments, applications, users, and networks.

When firewall rules, NAT policies, or security settings are changed incorrectly—or damaged by ransomware or AI-driven automation – the impact can be immediate. Teams need visibility into what changed and a reliable way to recover.

How PAN-OS Backup and Recovery Works

ControlMonkey continuously connects to PAN-OS environments and captures configuration snapshots over time. Each snapshot gives teams a reliable version of their firewall configuration that can be reviewed, compared, and recovered when needed.

The process is simple:

1. Connect PAN-OS to ControlMonkey
   ControlMonkey securely connects to your Palo Alto Networks PAN-OS environment.
2. Automatically back up configurations
   Firewall rules, policies, objects, NAT rules, zones, interfaces, routing, VPN settings, and device configurations are automatically backed up.
3. Track every configuration change
   Teams can see what changed across versions, helping them identify deleted rules, risky policy updates, broken NAT changes, or suspicious configuration activity.
4. Compare versions side by side
   ControlMonkey makes it easier to understand the difference between the current configuration and a previous known-good version.
5. Recover when something goes wrong
   If a configuration is deleted, misconfigured, damaged by ransomware, or changed by an AI agent or manual action, teams can recover from a previous backup and restore operational stability faster.

Built for Modern Infrastructure and Security Teams

As infrastructure becomes more distributed, firewall configuration management becomes harder to control. Teams are managing hybrid environments, cloud connectivity, branch networks, remote access, and security policies across many systems.

ControlMonkey helps bring order to this complexity by extending configuration backup and recovery beyond cloud infrastructure and into the network security layer. PAN-OS Backup and Recovery gives teams the visibility and control they need to protect critical firewall configurations from accidental, manual, malicious, ransomware-related, or AI-driven changes.

Ready to Take Control?

Explore PAN-OS Backup and Recovery by Palo Alto Networks in ControlMonkey today and strengthen your network configuration resilience.

Azure DevOps Backup and Recovery is now supported in Controlmonkey. Many Devops manage repositories, pipelines, project settings, permissions, service connections, and release workflows. These configurations directly impact how software and infrastructure are delivered.

But while application code is usually protected, the DevOps configuration layer is often overlooked. A deleted pipeline, Ransomware, misconfigured service connection, wrong MCP-AI Change or accidental project change can slow releases, block deployments, and create operational risk.

Recent incidents show why this layer matters. In the Grafana Labs GitHub token breach, an unauthorized party reportedly accessed the company’s GitHub environment, downloaded code, and attempted extortion. While the incident involved GitHub, it highlights a broader risk for every DevOps platform: access, tokens, repositories, and delivery configurations need the same level of protection as production infrastructure.

Introducing Azure DevOps Backup and Recovery

ControlMonkey Cyber Resilience Platform now supports Azure DevOps Backup and Recovery, helping teams automatically protect, track, and restore critical Azure DevOps configurations before small changes become major delivery disruptions.

With this new support, DevOps teams gain a reliable safety net for the systems behind software delivery. Key benefits include:

• Protect critical DevOps configurations
  Back up Azure DevOps projects, pipelines, repositories, permissions, and service connections.
  
• Recover faster from accidental changes
  Restore from automated configuration snapshots when something is deleted, changed, or misconfigured—or even due to an over-permissive AI agent.
  
• Improve visibility into configuration changes
  Understand what changed, when it changed, and where the change happened.
  
• Reduce delivery risk
  Protect the systems that manage build, release, and deployment workflows.
  
• Strengthen operational resilience
  Extend disaster recovery beyond cloud infrastructure into DevOps tooling.

How Does Azure DevOps Backup and Recovery Work?

ControlMonkey connects to Azure DevOps, discovers critical configuration assets, and automatically backs them up as part of your disaster recovery strategy.

Teams can track configuration changes over time, identify accidental edits or deletions, and restore backed-up configurations when needed.

Instead of manually rebuilding pipelines, permissions, service connections, or project settings, DevOps teams get a reliable recovery path for the systems that keep software delivery moving.

Strengthen Recovery Across the DevOps Delivery Layer

Azure DevOps connects code, pipelines, permissions, service connections, and deployment workflows into one operational system. When that system breaks, teams do not just lose settings. They lose delivery speed, release confidence, and operational continuity.

ControlMonkey gives teams a practical way to protect this layer with automated backups, change visibility, and restore-ready snapshots.

This helps organizations:

• Recover faster from accidental deletions, misconfigurations, and unauthorized changes.
• Reduce downtime caused by broken pipelines, permissions, or service connections.
• Maintain visibility into configuration changes across Azure DevOps.
• Strengthen governance over the systems that support infrastructure and application delivery.
• Extend disaster recovery beyond cloud resources into the DevOps tools teams depend on every day.

ControlMonkey Extends Disaster Recovery Across the DevOps Stack

ControlMonkey helps teams automatically back up, track, and recover these critical configurations, reducing downtime, preventing configuration loss, and improving operational control.

With support for Azure DevOps Backup and Recovery, ControlMonkey helps teams protect one of the most important layers in the engineering delivery chain.

Ready to protect your DevOps configuration layer?
Explore Azure DevOps Backup and Recovery today.

Modern companies depend on Cisco Meraki to keep offices, branches, retail locations, and distributed teams connected. From employee Wi-Fi and guest access to firewall rules, VLAN segmentation, site-to-site VPNs, and traffic shaping policies, Meraki controls the network configuration layer that keeps people, devices, and business-critical applications online.

But while cloud infrastructure and application data are often covered by disaster recovery plans, office and branch network configurations are still frequently changed manually, undocumented, or left outside formal recovery strategies. One deleted firewall rule, broken VLAN, misconfigured VPN, or incorrect traffic policy can disrupt employee access, disconnect locations, or impact critical operations.

ControlMonkey now supports Cisco Meraki Backup, helping teams automatically back up, track, and recover critical Meraki configurations before network changes become business disruptions.

Introducing Cisco Meraki Backup and Recovery

With ControlMonkey, teams can protect key Cisco Meraki configurations, including:

• Firewall filtering rules that control access and network security
• VLAN configurations that define internal network segmentation
• Site-to-site VPN settings that connect offices, branches, and distributed environments
• Traffic shaping policies that manage bandwidth and application performance
• Network configuration changes that need visibility, versioning, and fast recovery

Why Do You Need a Resilience Solution for Cisco Meraki?

Cisco Meraki controls critical office and branch connectivity. If firewall rules, VLANs, site-to-site VPN settings, or traffic shaping policies are changed or deleted, the impact can be immediate: users lose access, offices go offline, security policies break, and IT teams are forced to troubleshoot under pressure.

There are few risk vectors:

• It could be an honest mistake of one of your employees
• Malicious actor trying to shut down your office
• or an over-permissive AI agent that made a change it shouldn’t.

ControlMonkey gives teams a reliable recovery path for Cisco Meraki configuration. Instead of relying on manual investigation or tribal knowledge, teams can track configuration changes over time, identify creations, modifications, and deletions, and restore a previous known-good state when needed.

How Does Cisco Meraki Disaster Recovery Work?

ControlMonkey connects to your Cisco Meraki environment and continuously scans supported network configurations, including firewall filtering rules, VLANs, site-to-site VPN settings, and traffic shaping policies.

Each configuration state is automatically backed up and versioned, so teams can track changes over time and identify what changed, when it changed, and what needs to be restored.

If a configuration is deleted, misconfigured, or changed unintentionally, ControlMonkey enables teams to recover the previous state quickly – reducing downtime risk and protecting office and branch connectivity.

You can also use the daily snapshot to replicate your Meraki configuration to a new tenant or office. This makes it easy to copy your configurations in the event of a ransomware attack or when you need to quickly spin up a new site.

How ControlMonkey Is Different

Traditional Cisco Meraki backup vendors help teams protect Meraki configurations such as firewall rules, VLANs, site-to-site VPNs, and traffic shaping policies. ControlMonkey goes further by making Meraki part of a broader cloud and SaaS configuration disaster recovery strategy.

That means Cisco Meraki is protected alongside the other configuration layers that keep the business running : cloud resources, DNS, CDN, identity, observability, databases, version control systems, and third-party SaaS platforms.

Instead of treating Meraki as a standalone network backup workflow, ControlMonkey helps teams answer a bigger resilience question: Can we restore how our environment was configured not just recover our data?

ControlMonkey vs. Traditional Cisco Meraki Backup Vendors 

Bottom line: Cisco Meraki backup is not new. What makes ControlMonkey different is that Meraki becomes part of a unified configuration disaster recovery strategy — with point-in-time snapshots, ClickOps visibility, drift detection, and remediation across the configuration layer the business depends on.

Stay Ahead with Cisco Meraki Backup and Recovery!

ControlMonkey extends disaster recovery beyond cloud resources and into the network control plane.

By supporting Cisco Meraki Disaster Recovery, ControlMonkey helps teams improve visibility, reduce operational risk, and recover faster from accidental changes, misconfigurations, unauthorized updates, or automation errors.

Now, Meraki configurations can be protected alongside cloud, SaaS, identity, observability, and infrastructure configurations — giving teams a more complete resilience strategy across the systems that keep the business running.

With ControlMonkey, teams can scale office and branch network operations with more confidence, knowing that critical Meraki configuration is backed up, versioned, and recoverable.

Ready to protect your Cisco Meraki configurations?

Explore Cisco Meraki Disaster Recovery today.

Many teams depend on Zscaler to enforce access, inspection, and traffic control policies across distributed environments. But when those policies are changed, deleted, or misconfigured, the impact can be immediate: broken access, weakened security posture, and operational disruption.

ControlMonkey now supports Zscaler Backup and Restoration, helping teams protect critical Zscaler configurations with automated backup, change visibility, and fast recovery.

Introducing Zscaler Backup and Recovery

With ControlMonkey, teams can now protect key Zscaler configurations, including:

• Firewall filtering rules
  Back up and recover traffic filtering policies that control allowed and blocked connections.
• Browser access policies
  Protect the policies that define secure browser access across users, apps, and environments.
• SSL inspection policies
  Recover inspection settings that are critical for visibility, compliance, and threat prevention.
• Configuration change visibility
  Track how Zscaler security policies change over time and identify risky or unintended modifications.
• Fast recovery from mistakes or incidents
  Restore critical Zscaler configurations after accidental deletions, misconfigurations, cyber incidents, or AI-driven changes.

Why Do You Need a Resilience Solution for Zscaler?

Zscaler policies sit directly in the path of user access, internet traffic, and security enforcement. That means even small configuration errors can create a major business impact.

• Deleted firewall rules can block critical services. 
• changed browser access policy can disrupt employee access.
•  Misconfigured SSL inspection policy can reduce security visibility or break application traffic.

For teams operating at scale, Zscaler configuration is not just a security setting. It is part of the cloud control plane.

ControlMonkey helps ensure these configurations are continuously backed up, versioned, and recoverable as part of a broader infrastructure resilience strategy.

There are several risk vectors to consider:

• an honest mistake by an employee
• a malicious actor attempting to disrupt your office operations
• an over-permissioned AI agent making changes it shouldn’t.

How Does It Work Back and Recovery works?

1. ControlMonkey connects to your Zscaler environment using secure API access and continuously scans supported configuration types.
2. It captures configuration states over time, tracks changes, and maintains recoverable snapshots of critical policies. If a configuration is accidentally deleted, changed incorrectly, or impacted by an incident, teams can review previous states and restore the required configuration.
3. This helps Security and Network teams reduce recovery time, maintain policy continuity, and avoid manual rebuilds during high-pressure incidents.

Why Zscaler Native Backup Is Not Enough for Full Configuration Resilience

Zscaler policies often work alongside cloud infrastructure, identity providers, DNS, networking, CI/CD systems, and SaaS platforms. When an incident happens, teams need more than a point-in-time restore inside Zscaler. They need visibility into what changed, how it relates to the rest of the environment, and how to recover critical configurations quickly and safely.

ControlMonkey extends Zscaler backup and recovery into a broader configuration resilience strategy.

By protecting Zscaler policies alongside the rest of the cloud control plane, teams can reduce manual recovery work, improve change visibility, and maintain business continuity across connected systems. 

Stay Ahead with Zscaler Backup and Recovery

Security configurations are now part of modern infrastructure operations. They define who can access what, how traffic is inspected, and how organizations enforce policy across cloud and SaaS environments.

By extending backup and recovery to Zscaler, ControlMonkey helps teams:

• Improve visibility into security policy changes
• Reduce risk from accidental or unauthorized configuration updates
• Strengthen resilience across cloud and SaaS control planes
• Recover faster from configuration mistakes and cyber incidents
• Scale security governance with confidence

Zscaler protects access and traffic.
ControlMonkey protects the configuration behind it.

Ready to protect your Zscaler configuration?

Explore Zscaler Backup and Recovery with ControlMonkey today.

Reference Table: Key Zscaler Configurations for Backup and Recovery

ControlMonkey now introduces Snapshot Changes Over Time a historical diff layer for your cloud, Configuration, SaaS, Network and their dependencies

ControlMonkey now compares point-in-time snapshots of your infrastructure and shows exactly what changed between them: what was created, modified, or deleted. You can drill down to the resource level, view side-by-side differences, and understand how your environment evolved over time.

Why Change Visibility Matters

As cloud environments scale, so does the volume of change. Multiple teams are constantly updating infrastructure – some through IaC, others manually. Some changes are planned. Others are not. And many go untracked.

When incidents happen, teams are left without clear answers:

• What changed?
• When did it change?
• Which version of the environment was stable?

Without this visibility, recovery becomes guesswork.

Teams need a reliable way to trace changes over time: both to investigate issues and to understand which point in time they can safely recover to. Just as importantly, they need a clear control layer to understand how their environment is evolving day by day.

The new feature works across all of your vendors: AWS, Azure, GCP, Datadog, Akamai, Cloudflare, Snowflake, Databriks, Launch Darkly and more. You have a single location to track them all.

How Snapshot Changes Over Time Works

From snapshot capture to side-by-side comparison, ControlMonkey helps teams understand exactly how their infrastructure changed over time.

Snapshot and Capture

ControlMonkey continuously captures deterministic snapshots of your infrastructure state.
This creates a reliable historical record of your environment across cloud, network, and SaaS systems.

Compare Changes Between Snapshots

ControlMonkey calculates the diff between two points in time and shows exactly what changed.
Teams can instantly see what was created, modified, or deleted between snapshots.

Drill Down to the Resource Level

Users can click into a specific resource to inspect detailed changes over time.
This includes side-by-side comparison of older and newer states, making it easy to understand the exact configuration delta.

Investigate with Context

Teams can explore change activity through a timeline view, spot unusual spikes or patterns, and understand when changes occurred.
This helps investigate incidents, trace unexpected changes, and understand how dependencies evolved.

Summarize with AI

ControlMonkey KomoAI generates an AI summary of the differences between snapshots. This gives teams a faster way to understand what changed without manually reviewing every line. Even if they’re not Infrastruccture expert.

Review and Govern

By turning infrastructure history into an explorable change record, ControlMonkey gives platform teams a clearer control layer for governance, investigation, and recovery decisions.
Teams can use this visibility to detect unauthorized changes, support audits, and identify the right recovery point with more confidence.

Stay Ahead with Cloud Governance and Change Control

As more teams, tools, and automation layers interact with your cloud, the volume of changes increases. Some are planned. Others are not. Without a clear view of how your environment evolves over time, teams are left reacting to incidents without understanding their root cause.

ControlMonkey gives you a deterministic, historical view of your infrastructure, across all of your vendors – so you can see exactly what changed, when, and how. By turning snapshots into an explorable change history, teams can investigate incidents faster, detect unauthorized changes, and confidently decide where to recover from.

Ready to take control? Explore Snapshot Changes Over Time today.

ControlMonkey now supports GitHub Configuration Backup and Recovery, enabling teams to automatically back up and restore critical GitHub configurations, including repository settings, branch protection rules, permissions, and workflows.

GitHub controls how code is shipped, who can access it, and how pipelines operate – yet its configuration layer is rarely protected by a resilience solution.

Introducing GitHub Configuration Backup and Recovery

• Protect repository configurations, access controls, and branch rules
• Continuously capture workflows, policies, and configuration states
• Restore GitHub environments quickly after incidents or misconfigurations
• Reduce risk from human error, automation failures, or malicious changes
• Extend disaster recovery to your software delivery control plane

Examples of protected GitHub configurations include:

• Repository settings that define collaboration and visibility
• Branch protection rules enforcing code quality and deployment safety
• Permissions and access controls across teams and users
• GitHub Actions workflows powering CI/CD pipelines
• Webhooks and integrations connecting GitHub to external systems 

Why Do You Need a Resilience Solution for GitHub?

GitHub is deeply embedded in your production delivery pipeline – meaning misconfigurations or compromises can immediately impact deployments, access control, and development velocity.

Here are some of the key risks teams face:

• Ransomware or account takeover – What happens if your GitHub organization is compromised? Attackers could modify repositories, remove protections, or disrupt pipelines.
• Cyber attacks / malicious actors – Unauthorized changes to workflows, permissions, or integrations can expose code, bypass controls, or break delivery processes.
• Human error – Even experienced engineers make mistakes—removing branch protection, misconfiguring access, or altering workflows in the wrong repository.
• Over-permissive AI agents – As AI-driven automation expands in CI/CD, agents with broad permissions can unintentionally introduce risky or large-scale configuration changes.

ControlMonkey helps teams safeguard GitHub by protecting the configuration layer that defines how code is managed, how pipelines run, and who has access.

Stay Ahead with GitHub Backup and Recovery

GitHub is no longer just a code repository – it is a critical layer in your infrastructure and application delivery pipeline. When configuration is lost or altered, pipelines break, access control is compromised, and recovery becomes manual and slow.

ControlMonkey brings GitHub into your Cloud Configuration Disaster Recovery strategy by continuously backing up configuration states and enabling fast, reliable restoration. This ensures that delivery workflows, governance policies, and access structures remain intact—even during outages or security incidents.

With full visibility into configuration changes and the ability to recover instantly, teams can reduce risk, maintain IaC alignment, and scale operations without losing control.

ControlMonkey now extends Cloud Configuration Disaster Recovery to identity providers, protecting identity environments across Okta, Microsoft Entra ID, OneLogin, Ping Identity, and JumpCloud.

Modern cloud operations rely heavily on identity providers. During daily operations and incidents, SSO, MFA policies, and access rules control how users interact with infrastructure, SaaS applications, and internal systems.

Yet the configurations behind these systems – authentication policies, app assignments, roles, and access controls – are rarely protected by a solution for disaster recovery.

Identity DR Key capabilities:

ControlMonkey automatically captures daily snapshots of identity configurations so teams can restore access environments and maintain operational continuity during incidents.

Protect access control configuration
Backup SSO settings, MFA policies, app assignments, roles, and identity rules created over time.

Restore identity environments quickly
Recover identity configurations from versioned snapshots instead of rebuilding access policies manually.

Detect configuration drift in identity systems
Track changes across IDP platforms and identify unexpected or unauthorized modifications.

Preserve identity-to-system relationships
Maintain consistency between identity policies, application access, and infrastructure during recovery.

Extend disaster recovery beyond infrastructure
Protect the broader cloud control plane including infrastructure, network, observability, and identity configuration.

Identity is not just another system – it’s the layer that connects users to everything else. Recovering identity in isolation doesn’t work. You need to restore it together with the infrastructure and applications it controls.

Aharon Twizer

CEO & Co-Founder

How does Identity Configuration Disaster Recovery work?

ControlMonkey Cloud DR solution continuously captures configuration snapshots from supported identity providers.

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

• SSO and federation configurations
• MFA and authentication policies
• Application assignments and integrations
• Roles, groups, and permissions
• Directory and access control structures

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

If access policies are misconfigured, applications are disconnected, or identity rules break and and cause an incident –  teams can restore identity configurations directly from a previous snapshot – without manually rebuilding/configuring access environments.

Why Disaster Recovery for the Identity Layer?

Traditional disaster recovery focuses on restoring data and storage.
But modern cloud environments depend on access.

The identity layer connects users to infrastructure, SaaS applications, and internal systems – making it a critical part of the cloud control plane.

With ControlMonkey, teams can:

• Maintain versioned backups of identity environments
• Detect configuration changes and drift
• Restore identity systems quickly during incidents
• Ensure DR visibility with a clear Resilience Score

 At scale, restoring access quickly remains a challenge. Identity configurations are complex, frequently changing, and tightly connected to other systems.

By extending configuration disaster recovery to identity providers, ControlMonkey helps teams maintain operational continuity across both systems and access.

Cross-layer recovery: identity + infrastructure + SaaS

Identity does not operate in isolation.

ControlMonkey preserves and restores the relationships between identity, infrastructure, SaaS applications, and cloud resources — ensuring systems and access remain aligned after a  recovery.

This prevents scenarios where identity is restored but underlying systems are not – or vice versa.

Ready to be Cyber Resilient?

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

Reference Table: Key Identity Provider Configurations Protected by ControlMonkeyenvironment.

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

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 Identity Provider Configurations Protected by ControlMonkey