Home / Services / Security and resilience

Cyber resilience: plan for the bad day, and come back from it

By Mirav Labs, led by Deepak MittalUpdated
Short answer

Cyber resilience is your ability to keep the business running through an attack or outage and recover quickly from a clean copy. We set recovery targets with the business, protect backups so attackers cannot alter or delete them, tune detection for early warning signs, rehearse restores and tabletop exercises, and write a single playbook for recovery and for each reporting deadline, including CERT-In's six hours.

Key takeaways

  • Assume an attack will eventually get through, and design for how fast and how cleanly you can come back.
  • Recovery targets should be set per business process, by the business, then tested against measured times.
  • Hold one backup copy locked against change and deletion, and another cut off from the main network.
  • Identity, DNS, secrets and infrastructure definitions need recovering too, often before anything else.
  • A restore you have never run is an assumption; rehearsals turn it into a known time.

Picture a Monday morning when the order system will not load, file shares are full of renamed files and a note on every server names a price. The next few hours decide how long the business stays down. They also decide whether the people who must be told hear about it on time and accurately. Prevention matters, but it is not the whole job, because no set of controls stops every attack.

Cyber resilience is the preparation for that morning. We work with your IT, security, operations and business teams on the recovery side, and alongside your legal counsel on the reporting side.

Resilience is a business measure

The test of resilience is how the business comes through an incident, not the number of security products in place. We start with five questions:

  • Downtime. For each critical process (orders, billing, dispatch, clinical records), how long can it stop before the harm is serious?
  • Data loss. How many hours of recent transactions could you afford to re-enter or lose?
  • Foundations. Which shared services, such as sign-in, DNS, network, certificates and secrets, must be back before anything else can be?
  • Clean ground. Where would you rebuild, and how would you know the images and data predate the intrusion?
  • Authority. Who can call an incident, cut off a network segment, or speak to a regulator, a customer or a journalist?

The business sets the first two as recovery time and recovery point targets. We then measure what the current setup can really deliver.

How we get you ready

The work runs in five steps. Each one ends with something your own staff can operate.

How we get you ready to recover, and to reportPrepare to learn
Step 1Prepare

Runbooks, contacts and both clocks

Step 2Protect backups

Immutable and offline copies

Step 3Detect and contain

Spot it early, shut the door

Step 4Recover

A restore you have already tested

Step 5Report and learn

Board, affected people, CERT-In; then review

Now:
  1. Prepare. We write the incident playbook with you: roles, escalation, the decisions that need a senior name, and a phone list kept on paper and outside your normal systems. It notes two separate moments, when the incident was first spotted and when you learned personal data was involved, since different deadlines count from each.
  2. Protect backups. Intruders usually look for the backups first. We check what is copied, where it is held and which accounts could wipe it. The target design has a locked copy that no one can alter until its retention expires, a second copy cut off from the main network under different credentials, and coverage of system configuration, directory, vault contents and infrastructure code, not only business data.
  3. Detect and contain. We set alerts on the usual early signs: privileged accounts appearing from nowhere, backup jobs being disabled, bursts of file renames, unexpected bulk uploads. Containment guides spell out how to fence off machines, revoke sessions and keys, and capture evidence before it is overwritten.
  4. Recover. We rehearse. Priority systems are rebuilt from the protected copies in an isolated environment, the restored data is checked for gaps and tampering, and each stage is timed. Where the clock beats the target, we record it; where it does not, the shortfall gets an owner and a fix date.
  5. Report and learn. The playbook walks each notice through to its deadline. Afterwards a no-blame review captures the root cause and the changes, which flow back into backups, alerts and the playbook.

The reporting clocks

An incident in India can trigger several deadlines at once. Under CERT-In's April 2022 directions, covered organisations have six hours from noticing a listed incident, ransomware among them, to report it, and must hold ICT logs for a rolling 180 days inside India. When personal data is hit, the DPDP Rules add, from 13 May 2027, notice to the Data Protection Board and to the people affected, and a fuller Board report within 72 hours. Regulators in your sector, insurers and major customers may impose their own timings. All of them go into one playbook, and the notice drafts are prepared ahead of time for counsel to sign off.

If your recovery site has to be in India, sovereign cloud and data residency covers that design. Intrusions often begin with an exposed API or a leaked key, the territory of API and supply chain security, and factories and connected equipment are handled under OT and IoT security.

What you get

DeliverableContentsUse
Recovery targetsDowntime and data-loss limits for each critical process, with the systems each one needsTurns resilience into numbers you can test
Incident playbook and call listRoles, escalation, decision rights, offline contacts and every notice deadlineSomething to follow when systems and nerves are strained
Backup architectureLocked and isolated copies, scope of what is copied, separate keys and accountsA known-good source for rebuilding
Alerting and containment guidesEarly-warning rules, isolation and revocation steps, evidence captureSlows the spread and keeps the record intact
Restore rehearsal resultsSystems rebuilt, stage timings, data checks and shortfalls with ownersProof of how fast you can really come back
Tabletop session and review templateA guided attack scenario for leaders and staff, plus a no-blame review formatExposes weak points while the stakes are low

Preparation cannot guarantee that an attack fails. It does make recovery quicker and calmer, and it means your notices rest on facts. Choices about notification and any ransom demand stay with your business, its counsel and law enforcement.

How to start

Write down the processes the business cannot run without, and find out which accounts could delete your backups today. We begin with a review of backups, logging and existing incident documents, then plan a first restore rehearsal and tabletop. To book a scoping call, talk to us.

The DPDP side of this

Our DPDP practice, DPDP Ready, has a detailed guide on how this work maps to India's data protection law. Read it on DPDP Ready →

Frequently asked questions

What is the difference between cyber resilience and cybersecurity?

Cybersecurity is mostly about keeping attackers out and detecting them early. Cyber resilience accepts that some attacks will succeed and focuses on continuing to operate and recovering quickly with your data intact. A resilient organisation has protected backups, rehearsed recovery and a clear plan for decisions and reporting under pressure.

What is an immutable backup?

An immutable backup is locked against edits and deletion until its retention period ends, and the lock applies to administrator accounts too. Attackers often try to wipe backups before they encrypt anything, so a locked copy leaves a clean source for recovery. Pair it with a second copy that sits off the main network under different credentials.

How do we set RTO and RPO for our systems?

Start with business processes, not servers. For each process, ask how long it can be down before the damage becomes serious, which gives the recovery time objective, and how much recent data you can afford to lose, which gives the recovery point objective. Then map each process to the systems it depends on and test whether the backups and recovery design can actually meet those numbers.

What happens in a ransomware tabletop exercise?

Leaders and technical staff walk through a realistic attack scenario, step by step, in a room or a call. A facilitator introduces developments such as encrypted servers, a ransom note, a press query or a regulator's question, and the team decides what to do using its real runbook and contacts. The output is a list of gaps, owners and fixes.

Should identity systems be part of the recovery plan?

Yes, and usually near the top. If your directory, single sign-on or privileged access system is compromised or unavailable, staff cannot log in to restore anything else. Plans should cover rebuilding identity from a known-clean state, break-glass accounts held securely offline, and recovery of the secrets and certificates other systems need.

Scope it with us

A 30-minute call to understand your systems and what good looks like. We aim to send a written, fixed-scope proposal within three working days.

Talk to us

Related services

This page describes engineering and security services. Where it mentions laws, rules or standards, it is general information, not legal advice.

Talk to us