Backup and Disaster Recovery

Purpose

This page describes DefectDojo, Inc.’s current practices for backing up and recovering DefectDojo Cloud environments, including its approach to the loss of a cloud region.

This page is provided for information only. It is not a service level agreement and does not create any warranty, commitment, or obligation. A customer’s rights and DefectDojo’s obligations are set out solely in the customer’s agreement with DefectDojo, which controls if it differs from this page. DefectDojo may change these practices and update this page at any time, subject to any commitments in the customer’s agreement.

This page applies to environments operated by DefectDojo, Inc. Customers who self-host DefectDojo within their own infrastructure are responsible for their own backups and recovery.

Backups

DefectDojo’s standard practice is to take a backup of each customer environment once per day and to retain each backup for 7 days. Backups older than 7 days are deleted on a rolling basis and cannot be recovered, so a problem discovered more than 7 days after it occurred cannot be corrected by a restore.

When a customer’s data retention period ends, customer data is removed as described in our Data Retention Policy. Backups containing that data are not deleted individually. They are removed when they expire under the 7-day rolling retention described above, which is within 7 days after the data is removed from the environment.

Recovery Objectives

DefectDojo’s internal planning targets are:

  • Recovery Point Objective (RPO): 24 hours, reflecting the daily backup schedule.
  • Recovery Time Objective (RTO): 4 hours, measured from the time DefectDojo begins a recovery.

These targets apply to restoring a single environment from an available backup while its cloud region is operating. They do not apply to the loss of a cloud region, for which DefectDojo publishes no recovery time target.

These are internal planning targets only. They are not guarantees, and actual results depend on the circumstances of the event, the availability of backups and of the cloud provider, and the size of the environment.

Regional Outages

Each customer environment runs in the Google Cloud region selected for that customer. If that region becomes unavailable, DefectDojo’s disaster recovery plans provide for restoring affected environments from backup and returning them to service. Any such recovery is subject to the data residency terms, if any, in the customer’s agreement.

Requesting a Restore

Restores are performed by DefectDojo; customers cannot start a restore themselves. To request one, contact DefectDojo Support with the environment and the backup date you need. DefectDojo reviews each request, and restores are subject to the customer’s agreement.

Restoring from a backup can disrupt the environment and can undo changes made after that backup, including legitimate ones. Backups are intended for recovery from broad failures and are not designed as a way to undo unwanted changes made by a script or integration. We recommend testing automation against a non-production instance first.

Testing

DefectDojo’s disaster recovery plans are tested in accordance with our Business Continuity Policy. A summary of DefectDojo’s most recent disaster recovery exercise may be made available to customers and prospective customers under a non-disclosure agreement. To request it, contact your account team.

Customer-run recovery exercises are not part of the standard service. Contact your account team to discuss your requirements.

Relevant Documents

  • Business Continuity Policy
  • Incident Management Policy
  • Data Retention Policy
  • Cloud and Infrastructure Security Policy