Go Back

Git vs Secured Third Party Storage for Okta Backups


CEO and co-founder @acsense

Muli Motola

Co-founder and CEO

Git vs Secured Third Party Storage 

In an era where cybersecurity threats are escalating, the decision of where to store Identity and Access Management (IAM) backups has become crucial for organizational security.

High-profile security breaches, such as the Git RepoJacking incident in June 2023 and the Okta Git Breach in January 2023, underscore the vital importance of data security.


The question at hand is:


Should you store your IAM backups on your Git repository or in a third-party secured storage?
We’ll delve into the pros and cons of each option to help you make an informed decision.

Option 1: Third-Party Secured Storage 


  • Robust Data Protection:
    Top-tier third-party storage providers offer superior security measures including encryption, access controls, and redundancy, protecting your data (Cisco).
  • Disaster-Ready:
    Backup and disaster recovery features ensure your data can be restored in the event of unexpected data loss.
  • Scalability:
    Many providers offer flexible storage options to accommodate your growing data needs.
  • Separation of Concerns:
    Storing backups separately from your Git repository reduces the risk of accidental data corruption during development.
  • Object Connections and Correlations:
    Third-party storage maintains vital relationships between data objects, beneficial for incident investigations.
  • Incident Investigation:
    Allows for quick search and investigation of data, unlike in Git.


  • Cost Implications:
    Additional security comes at a price, and costs may increase as data storage needs expand.
  • External Provider Dependence:
    Your data access and restoration depends on the reliability and availability of the third-party provider.



Option 2: Git Repository


  • Integrated Version Control:
    Storing backups on Git provides version control functionality, enabling change tracking and version management of backups.
  • Centralized Management:
    If Git is your go-to for codebase management, storing backups in the same repository may streamline your workflow.
  • Accessible:
    Git repositories, with appropriate access controls, allow direct management and access to your backups.



  • Security Risks:
    Git repositories typically offer less security than dedicated storage providers, which may leave your backups vulnerable (Git Guardian).
  • Backup Feature Limitations:
    Git is primarily a code management system and may lack important backup features like automated backups or point-in-time recovery options.
  • Size Constraints:
    Depending on your Git hosting service, you might face restrictions on the amount of backup data you can store.
  • Object Correlation:
    Git struggles to maintain connections and correlations between large numbers of objects.

  • Data Investigation:
    Git lacks the capability for quick search and data investigation.

Based on the above analysis, it’s generally advisable to use third-party secured storage for IAM backups.

These providers typically offer stronger security, disaster recovery options, and scalability, ensuring the protection of your valuable data.

Want to learn more about how to backup and recover Okta?
Read more. 




Looking to stay in the loop on the latest IAM trends and updates?


Subscribe to the FiveNines IAM newsletter today and gain access to exclusive insights from industry leaders, groundbreaking companies, and global news outlets. Don’t miss out on the must-read monthly newsletter that delivers the juiciest edition yet of IAM resilience.


Subscribe on Linkedin now and stay ahead of the curve!

Scroll to Top
Skip to content