Colour theme
Book a consultation

Preparing SaaS records for ransomware recovery

Review cloud account access, recovery coverage and provider responsibilities so a SaaS data incident has a workable response plan.

A laptop displaying a black skull flag against a red screen.

Business records in a cloud application can still be deleted, overwritten or stolen through compromised access. A ransomware incident can involve a staff device, a cloud account, an integration or several of these at once.

The useful question is what your business could recover and who would control the response.

Identify the records and access paths

List essential SaaS records: shared documents, mailboxes, customer records and application data. Identify users, administrators and connected applications that can change or export them.

Don’t assume an attack needs malicious software installed inside the provider’s service. Stolen credentials or an over-permissioned integration may allow ordinary application functions to be misused.

Review each service separately. Different applications have different audit, retention and recovery capabilities.

Reduce access that isn’t needed

Remove unused accounts and review administrator roles and integrations. Enforce the sign-in controls your business has chosen, including MFA where supported, and protect recovery methods.

An application’s access can continue outside a user’s ordinary interactive login. Include connected tools in the review and know who can revoke their permissions.

Assign someone to receive and investigate relevant alerts. A report in a console doesn’t help unless a person can act on it.

Verify recovery coverage

The Cyber Centre’s ransomware playbook covers preparation, containment and recovery. Cloud storage still needs a recovery plan.

Ask your SaaS and backup suppliers which objects are covered, how far back recovery reaches and what access is needed to restore. Check deleted accounts, shared content, permissions and application-specific records.

Synchronization can carry unwanted changes to another copy. Version history, retention and backup also have different purposes and limits. Microsoft 365, for example, keeps deleted SharePoint and OneDrive files in its recycle bins for 93 days, which isn’t the same as a backup. Test the mechanism you’ll rely on.

Keep backup administration separate from everyday accounts, and review who could delete recovery copies.

Test a business-level restore

Choose harmless test records and restore them to a location set aside for testing. Confirm content, ownership, permissions and whether staff can complete the business task afterwards.

Record elapsed time and dependencies. Restoring one document is a long way from restoring a whole customer-management workflow, so test both.

Use the backup and continuity review to connect individual SaaS restores with business recovery priorities.

Plan the incident handoff

Keep supplier escalation contacts available outside the affected account. Establish who can restrict access, preserve logs and approve restoration. Coordinate actions so evidence isn’t overwritten unnecessarily.

A successful restore doesn’t settle possible data theft or notification obligations. Have the incident lead assess those separately with legal or privacy advice.

After testing or an incident, update the gaps and response instructions. Don’t treat a ransom payment as a guaranteed recovery method.


Featured Image Credit