On Tuesday Commvault rolled out Recovery Studio, promising to automate the restoration of business services, including their data, identities and network settings. Analysts welcomed the cyber recovery effort, but warned that its usefulness will depend on how accurately customers track the connections between systems. Network security and operations teams need to check how the restored parts fit together, and getting services running again means making sure those parts can work together safely.
Recovery Studio Includes Network Controls in Recovery
Recovery Studio uses runbooks, which give step-by-step instructions for rebuilding systems and restoring the parts needed by a service, and Commvault says it can oversee recovery work across applications and infrastructure and check that work along the way. Commvault outlined what Recovery Studio is meant to cover and when it expects access to begin, with those details set out in the table below. According to Commvault, a big company may need to bring back several hundred apps and thousands of user identities, along with settings and data that have to come back in the proper sequence. Commvault said conventional recovery efforts take 28 days on average to bring back even basic operations, and that timing is still a claim from the vendor. Commvault says Recovery Studio can manage what it takes to restore data and applications, along with these other parts of the recovery process:
- Identity systems that services depend on.
- The settings that each individual application uses.
- The way the supporting infrastructure is configured.
- The network settings that restored services need to use.
- The rules used by firewalls to decide which traffic can pass through and which traffic is not allowed to pass.
- Groups used for network security, along with their settings.
| Item | Announced detail |
|---|---|
| Product | Recovery Studio |
| Early access target | December |
| General availability | Over the next few months |
According to Commvault, its runbooks can also look for signs of threats in supported resources, which may help show where systems have been compromised before anyone decides to bring services back. Nobody from Commvault was available to go into more detail before publication.
Cyber Recovery Depends on Accurate System Maps
Recovery Studio does not use AI to work out the recovery sequence. Customers have to build and keep up a map of dependencies, which lists the assets involved and shows how each one depends on the others.
At Dickson Research, principal analyst Frank Dickson said the automation follows prescribed instructions, rather than having generative AI decide which recovery actions to take. Dickson is concerned that an automated process can carry out a faulty plan quickly and accurately without changing the mistake that was already in the plan.
The results depend on how well IT knows about changes across the organization, said Aman Mahapatra, who holds the chief strategy officer role at Tribeca Softech, a technology consulting firm based in New York City. One new app, a rotated certificate or an extra firewall rule can make an earlier recovery plan less accurate. Business units may also change applications without telling IT. Mahapatra regarded Commvault’s 28 days figure as plausible, while arguing that organizations which regularly update and rehearse runbooks are better placed to benefit. Outdated instructions could simply be carried out faster.
At Infotech, principal advisory director Abbas Jaffery raised a similar concern about changing applications, moving infrastructure and integrations that come and go, since individual systems could come back successfully while the service the business relies on still does not work.
The main advance is bringing recovery workflows together, said Johnny Yu, a research manager with IDC, while noting that Commvault and competitors already have the runbooks, threat scanning and testing tools underneath it.
Yu said Recovery Studio brings checked instructions into one place, and those instructions account for recovery at the existing location or another site, whether after a disaster or a cyberattack. Getting the restored service to work still comes down to which parts are brought back first and which follow, along with the checks done as that work proceeds.
Recovery Checks and Approval Are Separate Issues
Mike Leone, who is a VP and principal analyst with Moor Insights & Strategy, welcomed the organized approach, and pointed to the checks Commvault says it runs on rebuilt parts, plus the threat scans done ahead of production use. Leone also noted that people can make mistakes when they rebuild services by hand during an outage, while trying to get those services running again.
Dickson also acknowledged the validation and scanning features that Commvault announced, while noting that automation still relies on whatever instructions it has been given. Commvault has outlined safeguards, but it has not provided more detail about how those safeguards operate or how they carry out the checks it described. Jaffery said recovery after an attack also has to deal with compromised identities, unsafe configurations and malicious mechanisms, which could still be present in the systems. He said a person should sign off on the big, risky steps, such as anything touching identities or security settings and plugging systems back into production, and testing should check the whole recovery process from the beginning through to the end.