SRE Weekly Issue #261
📖 [The CloudSecList] Issue 78
[tl;dr sec] #74 - Building Securely on AWS, NFTs
IAM Access Analyzer now enables you to validate public and cross-account access before deploying permissions changes
AWS Security Hub adds 25 new controls to its Foundational Security Best Practices standard
How you can use Amazon GuardDuty to detect suspicious activity within your AWS account
Demystifying KMS keys operations, bring your own key (BYOK), custom key store, and ciphertext portability

Dear Architects,
You should read this long interview of @Werner about system design and more especially Amazon S3. It's just a gold mine. Let me cherry-pick some of my preferred quotes in a thread. ⬇️
cacm.acm.org/magazines/2021…



fwd:cloudsec 2021 will be in Salt Lake City, Utah on September 13 and 14! (2 days! 🤯)
We'll be at the Marriott City Center. It'll be hybrid (in-person and streamed).
CFP will open May 16; remote speakers who can't make it will be streamed in.



🤠Y’all will want to check this new feature from Access Analyzer out. Here are my reasons why…(1/8)
amzn.to/3vbu5k3



The competition of AWS services against one another is fascinating and horrifying. Why are these in Security Hub and not just AWS Config Rules?

AWS Security Hub adds 25 new controls to its Foundational Security Best Practices standard
AWS Security Hub has released 25 new controls for its Foundational Security Best Practice standard. These controls conduct fully automatic checks against sec... aws.amazon.com/about-aws/what…



With the proliferation of deepfakes, what could go wrong? 😅
Welp, here are some related tools
Some services to create deepfakes:
impressions.app
deepfakesweb.com
And a few to detect them:
sensity.ai
ambervideo.co
truepic.com



Very impressed with the team’s response to my first bug report. Also impressed it took 5 years of daily, full-time working with AWS Lambda to find my first bug. How much software can you say that about?!
3/3



The customer obsession is real. A few weeks ago I found a bug in an AWS Lambda API and reported it to AWS Support. The person on the other end of the ticket understood it, reproduced it and forwarded it to the service team.
1/3




"You have to be really consciously careful about API design. APIs are forever. Once you put the API out there, maybe you can version it, but you can't take it away from your customers once you've built it like this."



Honestly, @0xdabbad00's AWS Security Roadmap[1] feels like a much more solid baseline at this point. I also found Trusted Advisor checks[2] and AWS-managed config rules[3] to be good inspiration.
[1]summitroute.com/downloads/aws_…
[2]aws.amazon.com/premiumsupport…
[3]docs.aws.amazon.com/config/latest/…



🎉IAM Access Analyzer now lets you preview and validate access for your S3 buckets before performing permission changes! 🥳@AWSIdentity twitter.com/AWSSecurityInf…


Discover how to validate access to your S3 buckets before deploying permissions changes with IAM Access Analyzer: go.aws/3colSQM


I need your opinions about side-channel attack and access pattern infernece on computing machines on cloud system
If gcp, aws, azure cloud sysyem is susceptible to side-channel attack or access pattern inference, how they can keep up their services still without lawsuit or something?
Is it only because there was no severe attack in real?
I wanna get opinion of you guys
- 🖊️ This newsletter was fwd to you? Subscribe here
- 💌 Want to suggest new content: contact me or reply to this email
- ⚡️ Powered by Mailbrew