Loading

Minimum Viable Company

Defining your Minimum Viable Company is the most important cyber resilience decision you'll make before an attack. Do it now, so critical services come back first on a trusted foundation. 

MVC hero ISO
Overview

Strengthen your cyber resilience by recovering what matters most first, safely and quickly.

When a destructive cyberattack hits, leadership wants one thing: to restore critical business services quickly and confidently. But attacks now move at machine speed, leaving little time to decide what must come back first or whether you can trust what you restore.  

That’s where defining and operationalizing a Minimum Viable Company (MVC) becomes essential.

An MVC is the operational capability to restore your most critical services to a trusted state. The goal is to recover them fast enough so that you minimize the impact of a cyberattack. 

Operationalizing an MVC starts with preparation. By identifying and protecting the dependencies that support your critical services, establishing a trusted recovery foundation, and validating recovery in advance, you can respond to the incident, and recover essential services. 

Why organizations like yours adopt the MVC approach

Cyber resilience depends on recovering what matters most, in a trusted state. An MVC keeps you financially, strategically, and operationally viable during a severe disruption, so you keep serving customers and meeting obligations even when large parts of your environment are unavailable or untrusted. 

With governance agreed in advance and a digital jump bag™ ready, your team makes decisions faster under pressure. And proving you can restore critical services gives regulators the evidence of operational resilience they increasingly expect. 

What you need to operationalize your MVC

Prepare the foundation now so your most critical services keep running when a destructive cyberattack hits.

Clarity on critical services

Every hour spent debating priorities in a crisis is an hour your business stays down. When every system is the top priority, nothing gets prioritized. 

Agree in advance what must work first, and what becomes critical the longer an outage lasts, starting with safety, regulatory obligations, contractual commitments, and revenue.  Map what each service depends on, including identities, applications, and data. 

A trusted foundation
(Tier 0) 

Identity is the key to every critical service. Restore it compromised and everything built on it is compromised too.  

Establish your Tier 0 capabilities first: identity systems, networking, security tooling, privileged access, and secure out-of-band communications.  These foundational services let you respond, coordinate, and bring critical services back. Until Tier 0 is trusted, nothing else can be. 

Isolation of recovery assets

Attackers don’t just go after production. They go after your ability to respond and recover. If your incident response plan, license keys, and insurance details sit inside the blast radius, they may be unavailable when you need them most.  

Assume your primary environment is compromised. Pre-position what you’ll need to respond quickly and recover safely, including immutable backups and a hardened digital jump bag™ with known-good configurations, playbooks, and contact lists, isolated from production and reachable in minutes. 

Clean room recovery capability 

Restore without validating and you risk bringing the intrusion back along with the data.

A clean room gives your teams an isolated environment to investigate, validate, and rebuild without relying on the compromised production environment.  That’s how your MVC returns in a trusted state from day one: critical services run safely, decisions are based on evidence, and you can confidently return to full operation.

Validated ability to operate

Gaps in a recovery plan only surface when you run it, and an attack is the worst time to find them.  

Validate that you can restore your critical services to a trusted state under real attack conditions. Regular simulations  let you find and fix gaps before an attacker finds them for you, and give your board, regulators, and insurers the evidence they increasingly expect. 

James Blake
Expert insights

Cyber recovery is a business decision, not a technical one

"Traditional recovery is a technical process: moving data from point A to point B. Recovery after a cyber incident is a business process. It's a risk decision." 

- James Blake, Vice President, Global Cyber Resiliency Strategy, Cohesity

Cohesity turns your MVC from concept into capability 

Work with us to define, validate, and operationalize your MVC strategy. 

Identity resilience

Recover trusted user and admin access on day one. Restore it compromised and every service above it inherits the compromise. 
 

Cyber vault

Keep your jump bag, and the applications and data your MVC depends on, recoverable in an air-gapped immutable vault, for a worst-case scenario. 

Digital jump bag

Keep the trusted tools, credentials, and configurations you need to run a response, outside the blast radius and reachable in minutes, even when your core systems can’t be trusted. 

Cyber recovery orchestration

Rehearse and automate response and recovery runbooks to turn a plan into proven capability. 

Clean room

Investigate, remediate, and validate workloads in an isolated recovery environment, then decide, with evidence, what's trusted enough to return to production. 

Immutable backups

Restore critical business services from trusted data. Backups stored in immutable snapshots help ensure what you bring back is what you protected. 

From Catalyst

Cyber resilience that runs itself, with you in the loop

Destructive cyberattacks move at machine speed. Autonomous Cyber Resilience shifts protection and recovery from manual coordination to automated execution. In this 13-minute session, see how agentic workflows speed up protection and recovery of the critical services that make up your MVC.

FAQs for Minimum Viable Company 

A Minimum Viable Company (MVC) is the operational capability to restore your most critical services to a trusted state, within defined impact tolerances, ensuring continued financial, strategic, and operational viability.  Your organization needs to be able to do this when critical systems, documentation, and identities are rendered untrustworthy or unavailable. These critical services are typically the ones that underpin safety, regulatory compliance, contractual obligations, and primary revenue generation or mission delivery.  

The Cohesity Data Cloud platform underpins a Minimum Viable Company (MVC) strategy by mapping directly to the Cohesity 5 Steps of Cyber Resilience Framework©: protect data, identity, apps & agents, ensure recoverability in all scenarios, remediate cyber & AI threats, practice application recovery, and optimize data and AI risk posture.

  • Protect data, identity, apps & agents: Cohesity Data Cloud protects the foundation of an MVC—jump bag contents, identity systems, and mission-critical workloads — CRM, ERP, databases, VMs, cloud, SaaS, AI agent infrastructure all with immutable backups stored in a modern data platform.
  • Ensure recoverability in all scenarios: Cohesity FortKnox cyber vaulting isolates the jump bag, applications, and data that make up your MVC in an air-gapped, immutable vault for an extra layer of resilience.
  • Remediate cyber & AI threats: AI-powered anomaly detection, threat intelligence, YARA rules, and threat hunting identify malware before you restore your MVC-critical workloads.
  • Practice application recovery: Prove through clean room rehearsal that the MVC can be recovered to a trusted, working state. Engage Cohesity CERT Cyber Resilience Consulting Services for expert guidance to build and test your MVC capability.
  • Optimize your data & AI risk posture: Reassess your critical services and their dependencies to keep your MVC current. 

A traditional disaster recovery (DR) plan restores full IT environments from the most recent backup after natural disasters, hardware failures, or human error. A Minimum Viable Company (MVC) plan is built for ransomware and destructive cyberattacks, where recovering the latest configurations and data can re-introduce vulnerabilities, cause reinfection, and prolong downtime. Instead, an MVC rebuilds the smallest set of critical services the business needs to keep operating, using vaulted install images, known-good configurations, and immutable data, so you can trust what comes back. 

Unlike DR's IT-only failover, an MVC needs IT, security, and business leaders making decisions together, because returning a system to production is a risk decision, not a technical one. It also needs capabilities DR doesn't: cyber vaulting, forensics and clean room validation.

Defining a Minimum Viable Business (MVB) or Minimum Viable Company (MVC) state is critical to cyber resilience because it forces organizations to prioritize the systems, applications, and data that must come back online first after a ransomware attack or destructive cyber incident. Rather than attempting to recover everything at once, the goal is to restore only what is most critical to maintain core operations  -  protecting revenue, customer trust, and regulatory compliance with frameworks like NIST CSF, DORA, and ISO 22301. An MVB/MVC state enables faster recovery time objectives (RTOs), reduces downtime costs, and transforms business continuity planning into a proactive, resilience-first strategy. 

Resources

Webinar
Webinar
Prove you can recover data and restore trust: The Minimum Viable Company
Case Study
Case Study
Clarios
Research Report
Research Report
Global Cyber Resilience Report
Blog
Blog
Minimum Viable Company is about trust
White Paper
White Paper
Improve cyber resilience with a digital jump bag™
Loading