News for hackers. Stuff that matters.
Re:Ptar: Replacing .tgz for petabyte-scale S3 archives by deathanatos on Tuesday July 08, 2025 @11:21PM (#44506077)
If someone acquires root in the AWS account, they likely then have access to the backups, too. Unless we're also assuming whatever is doing the backup runs in an alternate cloud and our attacker or insider somehow has access to only 1 of 2 clouds.

Possible, perhaps, but contrived.

Re:Ptar: Replacing .tgz for petabyte-scale S3 archives by coredog64 on Tuesday July 08, 2025 @11:26PM (#44506095)
There's account root and then there's org root. Accounts are security boundaries, meaning you'd want your backups to at least be in another account within the org.
Re:Ptar: Replacing .tgz for petabyte-scale S3 archives by tuckerman on Thursday July 10, 2025 @05:52PM (#44526031)
I think using a separate cloud with credentials stored in a safe (or the equivalent) isn’t that uncommon (worked places where we were nearly 100% AWS but had GCP for storing backups). You’d need to compromise/socially engineer a different set of people to get access to that.