Skip to main content

Secure my backups in AWS S3

Comments

4 comments

  • cPanelLauren
    I don't think I fully understand the concern here, if your server was hacked, they still wouldn't be able to access your bucket because the password is stored in a hashed file. Furthermore, any security measures taken for the backup server would need to be done using the AWS instructions which would be best retrieved from AWS themselves.
    0
  • ImperialTrader
    I don't think I fully understand the concern here, if your server was hacked, they still wouldn't be able to access your bucket because the password is stored in a hashed file. Furthermore, any security measures taken for the backup server would need to be done using the AWS instructions which would be best retrieved from AWS themselves.

    Yea, I know that the password is stored in a hashed file. But, is there no other way for the hacker to use the same connection between WHM and S3 to delete the backups with the same method as WHM backing up the data?
    0
  • cPanelLauren
    They'd need to have your password to establish a direct connection to the backup server. Otherwise the only other method your backups could be removed say through the automated backup system would be if your preferences for retention are changed, this wouldn't be something which would expose your password though. This would mean they had direct access to your WHM and modified your backup preferences. A restriction that would prevent something like this (though I've never seen it done before) would be utilization of host access control, information on which can be found here: Host Access Control | cPanel & WHM Documentation
    0
  • ImperialTrader
    They'd need to have your password to establish a direct connection to the backup server. Otherwise the only other method your backups could be removed say through the automated backup system would be if your preferences for retention are changed, this wouldn't be something which would expose your password though. This would mean they had direct access to your WHM and modified your backup preferences. A restriction that would prevent something like this (though I've never seen it done before) would be utilization of host access control, information on which can be found here:
    0

Please sign in to leave a comment.