New S3 Encryption Feature, Is Amazon’s Encryption Move Enough?

data-sleeping.png

You be the judge… Essentially, all are targeted at data-and-objects-at-rest, rather than in-motion (except, perhaps the new cross-region replication feature with KMS).

Regardless, all of the annouced new features are welcome (in my currently rather jaded opinion). Now, if we can just overcome human error (not to mention blatant developer and data-owner lack-of-attention-to-detail, read about that here)…

  • Default Encryption – You can now mandate that all objects in a bucket must be stored in encrypted form without having to construct a bucket policy that rejects objects that are not encrypted.
  • Permission Checks – The S3 Console now displays a prominent indicator next to each S3 bucket that is publicly accessible.
  • Cross-Region Replication ACL Overwrite – When you replicate objects across AWS accounts, you can now specify that the object gets a new ACL that gives full access to the destination account.
  • Cross-Region Replication with KMS – You can now replicate objects that are encrypted with keys that are managed by AWS Key Management Service (KMS).
  • Detailed Inventory Report – The S3 Inventory report now includes the encryption status of each object. The report itself can also be encrypted. – via Jeff Barr, writing at the AWS Blog

And, thanks for the H/T go out to Trey Blalock over at rapidly growing Firewall Consultants!

Permalink

This is a Security Bloggers Network syndicated blog post authored by Marc Handelman. Read the original post at: Infosecurity.US