Bitbucket Ecosystem
The ultimate Bitbucket Protection
There may be different reasons why your organization needs backup that includes repositories and all related metadata. To just name a few: compliance with security standards like SOC 2 and ISO 27001, the Shared Responsibility Model which Atlassian follows, or any other legal regulations.
To ensure that you can access and recover your data with ease at any time your backup should include not only repositories but also metadata. It contains critical and vital information for your development process - without covering them too you will not be able to protect your Bitbucket ecosystem at full capacity.
Take a look at the metadata GitProtect.io covers in Bitbucket and Bitbucket DC:
- Repository
- Wiki
- Issues
- Issues comments
- Downloads
- Deployment Keys
- Pull requests
- Pull request comments
- Webhooks
- Pipelines / Actions
- Tags
- LFS
- Commits
- Branches.
Atlassian Cloud Shared Responsibility Model
Under this model, Atlassian is responsible for the system, hosting, and application focusing on their own business and integrity, and the user has to think about how to protect his data because account-level protection and recovery are not included in the provider’s responsibilities and competence. Service providers usually state directly that users need to use a third-party backup solution - GitProtect helps you fulfill this part of your responsibility with ease.