Security file · Helvedrive

Backups and recovery after ransomware: a verifiable set-up

Encrypted documents can still be deleted or made unavailable. Confidentiality and recovery capability must therefore be addressed together.

The plans describe the premium offering currently in development. The quote sets out integrations, timelines and commitments; real data is accepted after the security and restore validations.

Separating production and backup rights

The service’s administration credentials must not allow all backup copies to be deleted. The backup account, access and recovery procedure are separate. A single provider nonetheless still carries shared risks.

Protecting copies and defining their retention

Protecting copies relies on separate rights, a retention period and deletion tests using the actual administrative access. Version history or S3 compatibility is not enough: the deployment file sets out the chosen mechanism, its limitations and the test results.

Restoring before you need to

The Enterprise plan includes a quarterly exercise with a report: documents restored, permissions, versions and timings observed. The contract specifies the maximum age of the recoverable copy, the expected recovery time and the responsibilities of each party.

Preparing the response

The organisation must know the emergency contacts, containment actions, evidence preservation rules and responsibilities. Round-the-clock human monitoring and incident response are separate services, to be quoted for separately.

Scoping in confidence

Let’s define the scope of your protection.

Team, sensitive data, keys, location and recovery: let’s discuss your requirements. Please do not send any confidential documents through the form.