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.

As organizations rely on real-time data pipelines, the configuration layer behind Kafka becomes a silent source of operational risk. A single unintended change – whether accidental, automated, or malicious-can degrade throughput, break integrations, or take entire workloads offline.
Modern platform teams need more than Kafka automation. They need a backup strategy and governance model for their Confluent Cloud configuration.

Introducing Confluent Support in ControlMonkey

ControlMonkey now brings full IaC governance and automated daily configuration snapshot to Confluent Cloud, giving teams a resilient, auditable, and restorable record of every streaming configuration.

Key Capabilities

• Complete Confluent Cloud asset inventory across clusters, networks, ACLs, role bindings, and private link access
• Daily Confluent configuration backup snapshots for disaster recovery and security investigations
• Disaster Recovery – Restore any configuration with a built-in time machine.
• Rapid Terraform import for every Confluent resource
• Governance guardrails with drift detection for unapproved or unexpected changes
  

Stay Ahead by Reducing Cloud Risk in Kafka Environments

Streaming systems are mission critical-and fragile when configuration changes go unnoticed.
With ControlMonkey, Confluent teams can:

• Establish a real backup strategy for all Confluent Cloud configurations
• Reduce operational and security risk from misconfigurations or privilege misuse
• Restore environments quickly with point-in-time snapshots
• Enforce IaC discipline and eliminate ClickOps exposure
• Replicate clusters and environments confidently using generated Terraform
  

This is cloud resilience for Confluent Cloud – finally applied at the configuration layer.

Explore Confluent Cloud Backup & IaC Governance today.

 Backup all Confluent Cloud configs with daily snapshots, IaC governance, and Terraform import from ControlMonkey.

Book Intro Call

As cloud environments grow, DevOps and SRE teams often run into issues caused by unnoticed configuration changes- an Atlas cluster parameter shifts, a backup schedule is altered, or an IP allowlist is updated without a clear record. These small gaps in visibility can trigger real production incidents, slow investigations, and create compliance friction.

MongoDB is a major part of this reality. It holds roughly 46% of the NoSQL database market and consistently ranks among the top five databases on DB-Engines. With such broad adoption, Atlas configurations become a strategic asset that must be governed, tracked, and protected with the same rigor applied to application code.

What is MongoDB Atlas IaC Automation Support?

ControlMonkey brings full Infrastructure-as-Code automation to MongoDB Atlas: rapid import of existing resources, daily configuration backups for business continuity, cloud-to-code mapping, and policy alignment. It lets teams manage Atlas with the same discipline and repeatability they already apply to cloud and Kubernetes environments.

Introducing MongoDB Atlas IaC Automation Support

ControlMonkey now supports MongoDB Atlas as a 3rd party vendor, giving DevOps teams full visibility, governance, and resilience for their MongoDB clusters, projects, users, and configurations.

Key Capabilities

• Complete MongoDB Atlas visibility across clusters, projects, users, and access policies
• One-click Terraform import for rapid onboarding of existing Atlas resources
• Daily configuration backups and time machine for instant rollback and investigation, ensuring business continuity.
• Cloud-to-code mapping for governance, accountability, and policy alignment
• Consistent IaC workflows across MongoDB, cloud, and SaaS providers

Benefits of Atlas IaC Automation Support

MongoDB Atlas hosts mission-critical workloads. ControlMonkey ensures your Atlas deployment stays stable, compliant, and resilient:

• Scale multi-region or cloning workflows with confidence.
• Enhance visibility across every MongoDB Atlas component
• Reduce risk from accidental deletion, changes, misconfigurations, or malicious updates
• Strengthen infrastructure governance with Terraform-aligned workflows
• Protect availability with configuration backups and reliable rollbacks

Ready to take control of MongoDB Atlas?

Explore the MongoDB Atlas Provider Integration today

Book Intro Call

Many organizations have already standardized on Open Policy Agent (OPA) for enforcing cloud and infrastructure rules. ControlMonkey now supports running those same OPA Terraform Policies (Rego) directly inside your IaC governance workflows – no changes required. Bring your own policies. 

Introducing OPA Terraform Policy Support

• Use existing OPA logic: Run your current Rego policies as-is inside ControlMonkey.
• Keep your workflows: Reference OPA files from version control or write inline in ControlMonkey.
• Apply consistently: Map OPA policies to namespaces or stacks with the same enforcement levels used for Controlmonkey built-in policies.
• Combine sources: Use both ControlMonkey-managed policies and your own OPA rules in one place.
• No maintenance overhead: Keep using the OPA investment you already made – ControlMonkey handles execution and integration.
  

Why OPA Terraform Policies Matter for IaC Governance

This update is part of our commitment to meet customers where they are. Many large teams already maintain OPA Terraform Policies, and rewriting them isn’t practical.

With native OPA support, ControlMonkey runs your policies inside its own governance engine – letting you unify visibility, risk control, audit, and policy enforcement across your infrastructure, while keeping your existing toolchain.

Bring Your Own OPA Policies — No Rewrite Required

ControlMonkey now supports OPA natively. Keep your existing Rego policies, integrate them into IaC workflows, and enforce governance automatically.

Book Intro Call

As identity becomes the new perimeter, organizations can’t afford to treat Okta configuration as an afterthought. With ControlMonkey’s new Okta support (Okta Terraform Integration), your identity layer now gets the same automation, visibility, and resilience as your cloud infrastructure.

Why Manage Okta as Code?

Okta configurations are as critical as your production environment. Yet they’re often changed manually – creating risk and audit blind spots. Managing Okta as code ensures:

• Version Control: Every user and group policy change is tracked and reviewable.
• Rollback Safety: Instantly restore previous states after errors or malicious activity.
• Governance Consistency: Apply the same compliance guardrails across identity and infrastructure.

Introducing Okta Support for Total Identity Control

ControlMonkey now supports Okta as a native infrastructure vendor,, giving DevOps and security teams a single, governed view of identity and infrastructure. Okta resources – users, groups, roles, and permissions – can now be imported, monitored, and protected automatically.

With this release, teams gain:

Okta Inventory – Understand all your user, groups, roles and identity resources.

IaC Blind Spots – See which Okta configurations are Terraform-managed and which are not.

Import to Terraform – Bring unmanaged Okta resources under IaC control.

Daily Okta Backup Snapshots – Automated backups of Users, roles and Okta settings.

Disaster Recovery – Restore any configuration with a built-in time machine.

Daily configuration versioning allows teams to view or restore past states, investigate access histories, and ensure compliance.

Okta Backup and Governance

Most “Okta-as-Code” approaches stop once the configuration is codified. ControlMonkey goes further – adding governance, protection, and insight on top of that code.

It combines Terraform and OpenTofu parity, and real-time drift detection to create a true control layer for identity management. With built-in daily backups and a “time machine,” ControlMonkey gives teams the ability not just to manage Okta as code, but to govern identity as infrastructure.

Okta Integration with Cloud Governance and Identity Resilience

Identity and infrastructure now move together. With ControlMonkey, Okta joins your unified IaC ecosystem – monitored, versioned, backed up and compliant by design.

You gain the visibility, rollback confidence, and governance required to secure identity at enterprise scale with Okta Integration.

A 30-Minute Intro Will Save You Hours of Identity Recovery

See how ControlMonkey brings automation, visibility, and daily backup to Okta. Turn your identity configuration into code – and your code into control.

Book Intro Call

Enterprises still rely on VMware for core workloads but typically manage it outside their Terraform workflows. The result is inconsistent governance, limited version control, and higher risk of configuration drift. ControlMonkey’s new VMware Terraform Integration eliminates that gap. 

Cloud and on-prem infrastructure share one control dashboard, one audit trail, and one set of guardrails for Hybrid Cloud. VMware is now managed through the same Terraform workflows already used for cloud.

Introducing VMware Terraform Integration

ControlMonkey turns VMware into code. ControlMonkey automatically generates Terraform code for VMware resources and brings them into a unified IaC lifecycle. Every VM, load balancer, and network resource becomes part of your Terraform/OpenTofu automation – governed, backed up, and versioned.

• IaC for VMware. Auto-generate Terraform code for VMware resources to manage on-prem like cloud.
• Unified governance. Apply the same guardrails and approval flows across hybrid environments.
• Daily backups. Protect VMware with automated IaC snapshots for instant rollback and recovery.
• Drift detection. Identify and fix out-of-band changes in VMware just like in AWS, Azure, or GCP.
• Migration support. Maintain full visibility as workloads move between VMware and cloud.

Hybrid Cloud Infrastructure Through One IaC Platform

Unlike other industry solutions that focus only on cloud or policy orchestration, ControlMonkey extends full IaC automation including code generation, drift detection, and Cloud backup – to VMware itself. This unified model gives enterprises the same Terraform-driven governance for on-prem as they already have in the cloud.

ControlMonkey’s VMware integration removes the operational divide between Terraform-managed cloud and VMware environments. Security, compliance, and recovery standards are now applied consistently across VMware and cloud. DevOps teams gain control and repeatability, while risk and compliance teams gain one verifiable audit trail.

Explore VMware Terraform Integration today.