5 ms·
> but not implementing anti-tampering on local and remote backups i.e. protection from root. How do you accomplish this? I have some ideas/assumptions, but I'
by mywittyname 5y ago
> but not implementing anti-tampering on local and remote backups i.e. protection from root.
How do you accomplish this? I have some ideas/assumptions, but I'd like to hear more about the best practices here.
- sdave 5y ago1st level of protection is by keeping your live production data & backup data in separate accounts. (If 1 account gets compromised the other is still available) Perhaps 2nd level is by using cloud specific features - such as AWS S3 Object locks (even owner can't delete the object till the retention period). my 2cents
- mjw_byrne 5y agoSeparate storage of file hashes would make tampering detectable. Actually preventing root modifying a file probably has to be done at the hardware level.
- andi999 5y agoHeard of a case where an admin was bribed by competition to delete everything.
- nicolaslem 5y agoBackups sent to a remote system should be append only so that if a machine is compromised, a malicious actor cannot delete or corrupt previous backups.
- cma 5y agoMaybe something like the write protect switch on LTO tape cartridges, so that if compromised you never overwrite the tape when trying to restore.
- gumby 5y agoAn easy way is to stream the backups to tape, and have someone swap the tapes. Typically people who do this take the recorded tapes offsite, but to prevent against an electronic attack it’s adequate to have the removed tapes even in the same room, just not in the tape drive.