t_believ-er873
t_believ-er873 on Hacker News
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
Well, GitHub, Bitbucket, or any other git hosting service isn't backup strategy, and the data stored there still needs backup and protection. Tere are some tools that can help with it, e.g. GitProtect -
https://github.com/marketplace/gitprotect-io
Posted by
t_believ-er873 on Wednesday April 02, 2025 @02:23AM
from the community.atlassian.com dept.
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/landingAlso, 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.
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.
It sounds frustrating! If your recovery codes aren’t working, try reaching out to GitHub Support—they might be able to help restore access.
Posted by
t_believ-er873 on Tuesday January 14, 2025 @11:42AM
from the gryd.io dept.
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?
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.
Posted by
t_believ-er873 on Friday August 09, 2024 @04:48AM
from the helpnetsecurity.com dept.
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.