Selfhosted

40329 readers

368 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago

MODERATORS

HybridSarcasm@lemmy.world

HybridSarcasm@lemmy.hybridsarcasm.xyz

what if your cloud=provider gets hacked ? (www.bleepingcomputer.com)

submitted 10 months ago by kristoff@infosec.pub to c/selfhosted@lemmy.world

44 comments fedilink hide all child comments

Hi all,

As self-hosting is not just "home-hosting" I guess this post should also be on-topic here.

Beginning of the year, bleeping-computers published an interesting post on the biggest cybersecurity stories of 2023.

Item 13 is an interesing one. (see URL of this post). Summary in short A Danish cloud-provider gets hit by a ransomware attack, encrypting not only the clients data, but also the backups.

For a user, this means that a senario where, not only your VM becomes unusable (virtual disk-storage is encrypted), but also the daily backups you made to the cloud-provider S3-storage is useless, might be not as far-fetches then what your think.

So .. conclussion ??? If you have VMs at a cloud-provider and do daily backups, it might be usefull to actually get your storage for these backups from a different provider then the one where your house your VMs.

Anybody any ideas or remarks on this?

(*) https://www.bleepingcomputer.com/news/security/the-biggest-cybersecurity-and-cyberattack-stories-of-2023/

you are viewing a single comment's thread
view the rest of the comments

[–] originalucifer@moist.catsweat.com 10 points 10 months ago (5 children)

haha

"the cloud" does not change the fact that if you data does not reside in 2 physical locations you do not have a backup.

so yes, standard practices that have existed... well, since the beginning, still apply.

[–] kristoff@infosec.pub 5 points 10 months ago (4 children)

Well, the issue here is that your backup may be physically in a different location (which you can ask to host your S3 backup storage in a different datacenter then the VMs), if the servers themselfs on which the service (VMs or S3) is hosted is managed by the same technical entity, then a ransomware attack on that company can affect both services.

So, get S3 storage for your backups from a completely different company?

I just wonder to what degree this will impact the bandwidth-usage of your VM if -say- you do a complete backup of your every day to a host that will be comsidered as "of-premises"

[–] originalucifer@moist.catsweat.com 3 points 10 months ago (2 children)

yeah, you can use another cloud provider as backup.. if you do it correctly.

personally, my disaster recovery plans dont include entire offsite VMs. i only care about data in a dr situation. so you send incremental daily backups offsite.

containers have made VMs even more irrelevant/ephemeral so focus on the data.

[–] GreatBlueHeron@lemmy.ca 1 points 10 months ago (1 children)

I assume "data" includes your container configuration files in this strategy?

[–] pearsaltchocolatebar@discuss.online 1 points 10 months ago

Those are pretty easy to store off site since they shouldn't change often.

load more comments (1 replies)