Notifications
Clear all
Topic starter
09/07/2026 3:27 pm
TL;DR: Modernization in cyber recovery is framed here as an operational discipline built on testing, shared visibility, isolated recovery, and cross-team coordination, according to Commvault’s STRIVE conversation with Gilman Treantos. The core message is that resilience comes from rehearsed recovery and architectural simplification, not from adding more tooling.
NHIMG editorial — based on content published by Commvault: STRIVE episode on modern cyber readiness and resilience
Questions worth separating out
Q: How should teams govern access to isolated recovery environments?
A: Treat isolated recovery environments as high-risk production-adjacent assets.
Q: Why do backup and restore processes need identity governance?
A: Because recovery succeeds or fails based on which identities can execute restore steps under pressure.
Q: What do organisations get wrong about disaster recovery testing?
A: They often test failover without testing the access paths that make failover possible.
Practitioner guidance
- Map recovery identities end to end Inventory the service accounts, break-glass users, API credentials, and operator roles that can touch backup, restore, migration, and isolated recovery environments.
- Test restoration with access validation Run disaster recovery exercises that confirm the right identities can actually perform each recovery step, including cross-team approvals, environment isolation, and data movement.
- Separate recovery access from production convenience Use distinct credentials and approval paths for recovery operations so production privilege does not automatically carry into restore workflows.
What's in the full article
Commvault's full episode covers the operational detail this post intentionally leaves for the source:
- The recovery playbook details behind live migration and isolated restoration decisions.
- The practical use of backup tooling for data center evacuation and low-loss transitions.
- The way anomaly detection is layered into backup processes to support cyber recovery.
- The discussion of how security and infrastructure teams coordinate during real disruptions.
👉 Watch Commvault's STRIVE episode on modern cyber readiness and recovery →
Modern cyber readiness: is your recovery discipline keeping up?
Explore further
09/07/2026 3:48 pm
Modern cyber readiness is an identity governance problem as much as a resilience problem. Recovery depends on who can access backup systems, isolated environments, and migration paths under pressure. If those identities are not tightly owned and tested, the organisation may be resilient in theory and fragile in practice. The practitioner conclusion is that recovery access must be governed with the same discipline as production access.
A question worth separating out:
Q: How do security teams reduce privilege sprawl in resilience operations?
A: Start by separating production access from recovery access, then remove standing permissions that are not needed for routine restoration. Review service accounts, break-glass roles, and migration credentials as a single governance surface so privilege does not accumulate silently across backup and infrastructure teams.
👉 Read our full editorial: Modern cyber readiness depends on tested recovery, not new tools
