Monday,
October 14, 2024

🥖 Palette Cleanser

"A security device is not the same thing as a secure device." I can't remember who said it but it describes this week beautifully as Fortinet and Palo Alto both announced critical pre-auth vulnerabilities in their software - oops. Maybe BYO on-premise security software in the cloud isn't the most optimal security architecture after all.

In happier news, after years of community projects duct taping boto3 parsers and scrapers together, AWS has published a machine readable service reference, accessible here. For now it's just a service list with "action-level permissions" so projects like permissions.cloud aren't going away just yet. But it is great to see progress on this. More like this, please AWS friends <3

Have feedback about AWS Security Digest? Tell us here. This issue is also available to share online.

📋 Chef's selections

  • Challenges with IP spoofing in cloud environments by Emile-Hugo Spir

    Sometimes your app needs to know the IP address of the connecting user/client but their web requests are passing through a bunch of those (not secure) security devices. You can't get the IP from the TCP connection so what do you do? Emile lays out the problem and various traps engineers can fall into. While it's a cloud agnostic article, he provides some AWS examples and code.

    It should be obvious to cloud professionals that IP controls are at most a mild annoyance to attackers. After all, the cost of spinning up another EC2 instance or Lambda is ~$0. Definitely unrelated: AWS Active Defence for S3.

  • Perfecting Ransomware on AWS — Using keys to the kingdom to change the locks by Harsh Varagiya

    Trigger warning: This article is guaranteed to rub some people the wrong way. It's a pretty detailed instruction manual for effective ransomeware of AWS data stores. I think it's important though. It clearly demonstrates how easy it is to execute the attack but also how easy it is to prevent. Get that SCP setup immediately if you don't intend to use XKS!!

  • My Methodology to AWS Detection Engineering (Part 3 - Variable Scoring) by Chester Le Bron

    This time Chester focuses on adjusting "risk scores" for alerts based on things like ip enrichment, users of interest, privileged identities etc. I found this post much more accessible than Part 1 and Part 2. I think Chester has discovered the secret to AWS security content distribution - split your blog posts up into a series and we'll be forced to link all of them each time.

Bonus++:

🥗 AWS security blogs

🍛 Reddit threads on r/aws


🤖 Dessert

Dessert is made by robots, for those that enjoy the industrial content.

🧁 IAM permission changes

🍪 API changes

🍹 IAM managed policy changes

☕ CloudFormation resource changes

    No resource updates this week.

🎮 Amazon Linux vulnerabilities

YouTube Twitter LinkedIn