CI/CD Backup Guide

The DevOps Guide to Backup in CI/CD

All you need to know about shifting left approach, backup and how to integrate data protection into your pipeline. Learn how to successfully adopt DevSecOps processes now!

This guide covers:

Shifting left approach: a new business challenge
GitHub, Bitbucket, and GitLab CI/CD: PRO practices
Backup as a part of CI/CD
Shared responsibility model and backup

$CI\CD Guide$

Dive deep into backup within CI/CD proccess

Shifting left approach
Find out what are the best practices and how to implement them within your organization
Backup in CI/CD
What are the best ways to include backup as an additional step to the well-known Build, Test, and Publish scheme
Shared responsibility model
Learn how to meet all requirements. In this part we look for an answer to a possibility to reduce customer’s responsibilities

Some pages from CI/CD Guide

Still think your data is already backed-up?

SaaS providers operate in the Shared Responsibility Model. As such, they are responsible for the entire cloud infrastructure, but limit the responsibility for data protection at the account level.

Try for free Custom demo

GitHub Terms of Service

You understand that use of the cloud products necessarily involves transmission of your data over networks that we do not own, operate or control, and we are not responsible for any of your data lost, altered, intercepted or stored across such networks. We cannot guarantee that our security procedures will be error-free, that transmissions of your data will always be secure or that unauthorized third parties will never be able to defeat our security measures or those of our third party service providers.

Make sure yourself

Atlassian Security Practices

We do not use these backups to revert customer-initiated destructive changes, such as fields overwritten using scripts, or deleted issues, projects, or sites. To avoid data loss, we recommend making regular backups.

Make sure yourself

GitLab Subscription Agreement

Customer is responsible for implementing and maintaining privacy protections and security measures for components that Customer provides and controls.

Make sure yourself

Atlassian Customer Agreement

(...) neither party will have any liability arising out of or related to this Agreement for any loss of use, lost data, lost profits, interruption of business or any indirect, special, incidental, reliance or consequential damages of any kind, even if informed of their possibility in advance.

Make sure yourself

Microsoft Terms of Use

In no event shall Microsoft and/or its respective suppliers be liable for any special, indirect or consequential damages or any damages whatsoever resulting from loss of use, data or profits, whether in an action of contract, negligence or other tortious action, arising out of or in connection with the use or performance of software, documents, provision of or failure to provide services, or information available from the services.

Make sure yourself