t_believ-er873

For me, it's easier when I have everything done automatically. Thus, I prefer using backup tools to set up a backup copy to be run automatically. For that I use GitProtect

Hi, maybe this article can be useful: https://gitprotect.io/blog/how-to-enhance-devops-productivit...

Recently there have also been posts on that issue in other communities. Not to be tricked by this scheme, it's worth regularly searching for copies of the public repositories. Then, if any of the malicious clones are found, report them to GitHub.

Hello, your GitHub account was likely flagged for suspicious activity by GitHub's automated systems, which can cause it to become invisible to others while still allowing you to log in. This can happen due to false positives in their security checks, even if you haven’t violated any rules. To resolve this, you’ll need to contact GitHub Support directly through GitHub’s support page and request a review of your account: https://support.github.com/request/landing

Also, it's worth noting that GitHub or GitLab is not a backup solution, outages, cyber attacks, account suspicion, human errors may happen and lead to data loss. If you search for a backup solution, it better to look at those, e.g. GitProtect.io - the backup tool supports both GitHub, GitLab (as well as Bitbucket, Azure DevOps, and Jira). Moreover, it allows cross-restore, for example, like in your case, backup all the files at your GitHub account and restore them to GitLab.

I think that AI won't replace programmers, at least for now. All those codes written by AI still need review and more attention within security. Here is a good article about Copilot: https://gitprotect.io/blog/github-copilot-introduction-an-ai...

If you've identified GitHub repositories hosting malware, you can report them directly to GitHub via their Abuse Report page, providing links and any relevant details. GitHub typically removes repositories that violate their Acceptable Use Policy, but response times may vary. If the malware is actively being used for harm, you may also consider reporting it to security organizations or CERT teams.

Unfortunately, bad actors abuse GitHub more and more. Only last year there were some articles about it: https://gitprotect.io/devops-threats-unwrapped.html

That case would stay in history. However, there are so many threats and vulnerabilities that could lead to data loss nowadays: https://gitprotect.io/devops-threats-unwrapped.html

It sounds frustrating! If your recovery codes aren’t working, try reaching out to GitHub Support—they might be able to help restore access.

Nice article, thank you for sharing. Here is another blog post on the 3-2-1 backup rule, which also covers other popular backup schemes, including 3-2-1-1-0 and 4-3-2: https://xopero.com/blog/en/the-evolution-of-data-backup-is-t...

Good news

Nice article. Pair programming seems good for growing as a developer. The described process also seems well thought out and worth exploring

Is it enough to have only daily backups? Or it's better to have more frequent ones?

Take a look at this article: https://gitprotect.io/blog/exploring-best-practices-and-mode...

Also, you can find more articles on CI/CD on this blog

Try Xopero Software to back up your Windows instance - https://xopero.com/

For backing up VMs, it's possible to use Xopero Software https://xopero.com/

It's worth checking every link you get even if it's from a trusted source, like GitHub... and to be able to restore the data, it's worth having a backup

GitProtect backup and DR for DevOps

To protect both your VMs and the critical data inside them it's possible to use Xopero Software. The solution helps to ensure flexibility and resilience against data loss.

Unfortunately, outages happen... This situation is a very good reminder of why having backups and a solid Disaster Recovery plan is crucial. Of course, it’s easy to assume that cloud services are always up, but we should never forget about outages. Setting up automated backups for repos and metadata can save a ton of headaches when things go wrong. Plus, having a Disaster Recovery plan means you’re not stuck waiting for the service to come back online—you can keep working with minimal disruption.

Here is a good article on how to prepare for the situations like that, when GitHub is down: https://gitprotect.io/blog/github-restore-and-github-disaste...

You're right about "Sec" in DevSecOps. Unfortunately, often it’s just about being reactive monitoring. It’s true that monitoring alone doesn’t prevent incidents but rather just tells you after the fact that something has gone wrong. The real challenge is integrating proactive security measures that actually prevent incidents before they occur or measures that can help to handle the consequences, like MFA, encryption, regular backups and their testing, Disaster Recovery, etc.

Yes, it's worth paying attention to these questions as they are very important. If renetion is mostly related to compliance requirements of the industry. Some data should be kept for 5 years and some for 20, so it's good if a backup solution provides long-term or unlimited retention.

Regarding the cost, I think that a backup solution is always much cheaper than the cost of data loss. So it's better to have a backup than not.

And, of course, restore and recovery checks are also important. Moreover, a backup solution should foresee different disaster scenarios. for example, disaster scenarios like those described here in the article: https://gitprotect.io/blog/github-restore-and-github-disaste...

Everything depends on the security compliance needs.

Regarding backup scheduler - sometimes companies need to have frequent backups due to their RPOs and RTOs, for example, if they operate in a highly regulated industry. If someone can tolerate the loss of data of two hours, then, they need to have backup performed every 2 hours, if we speak here about 8 hours (working day), so why not to have backups on a daily basis?

Regarding rotations - everything depends on a backup solution, if it provides with immutable backups, so the entire data won't be corrupted. Thus, the faster someone notices the mistake, the faster they can restore their copy. IDF helps more to decide the issue with storage - not to overload it (here also worth mentioning deduplication and compression).

Nice! As an alternative backup tool, you can look at GitProtect Backup & Disaster Recovery for GitHub, Bitbucket, and GitLab. It allows you to pick up the storage (Cloud/local or both), automate backups by scheduling them at the most appropriate time, avoiding throttling, and restore data immediately from any point in time in case of failure, and many other features that meet pain points.

In this case it's better to have all the data backed up. And here I mean that data should be backed up on a regular basis, like every day.

I use a backup tool, Xopero, for automating by backups

To all CISOs & DevOps! Get ready and save the date!

June 26th, 10 AM PST / 7 PM CEST

Join the webinar and let's analyze the common traps and shortcomings we saw in DevOps Backup and BCDR plans used by experienced CISOs - check whether those mistakes you are likely to make too.

Find the path both CISOs and DevOps teams should follow to meet halfway and secure data processed across GitHub, GitLab, and Atlassian, without compromising agility and efficiency.

Register now

https://www.linkedin.com/events/7204475970823561216/comments...

Look at GitProtect.io for DevOps tools. It allows to back up all the repository and medata.

Backup is an important part of source code security strategy. In the perfect scenario, it's worth having a few workinf copies of your git repos and metadata in different locations. For that reason, it's possible to use diffrent backup optons, like backup scripts or DevOps backup tools (e.g. GitProtect).

Within this rule you should have at least 3 backup copies in at leat 2 different storage destinations, one of which is offsite. This backup rule esures that you can restore your data in diferent disaster scenarios, for example, if there is an infrastructure outage.

Here is apost where you can find out more about the 3-2-1 backup rule and its morden alternatives - the 4-3-2 and 3-2-1-1 backup strategies: https://xopero.com/blog/en/the-evolution-of-data-backup-is-t...