Monday,
October 07, 2024

๐Ÿฅ– Palette Cleanser

I hope you've had a magnificent week dear reader. Did you happen to get one of these emails: "This e-mail confirms that the Amazon Web Services account associated with account ID 123456789012 is permanently closed and cannot be reopened. Any content remaining in this account is inaccessible and will be erased?" ....... Me neither. ๐Ÿค•๐Ÿค’ What happens to AWS accounts after death? Is there an afterlife? Do they reincarnate after they pass through The Frame?

Last week I asked for smart readers to share their takes on the CUPS vulnerabilities. A very reputable Frenchman diligently pointed me to this Datadog summary. Has anyone even made a printer work on Linux anyway?

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

๐Ÿ“‹ Chef's selections

  • When AI Gets Hijacked: Exploiting Hosted Models for Dark Roleplaying by Ian Ahl

    I love AI. You love AI. We all love AI, including attackers who need GPU hours to host their sexy chat bots. So I guess AI loves us back? That was a plot twist I did not expect but seems obvious in retrospect. Ian explores attacks Permiso observed in AWS that leveraged the Anthropic models provided by Bedrock. A cool tidbit is the use of somewhat-documented-but-not-in-the-SDK APIs, which Nick Frichette pulls apart in this very interesting thread.

  • Explore the Power and Pain of User-Data by Rich Mogull

    Every week Rich diligently creates an awesome free practical AWS security exercise for folks to complete. I've been in a love triangle with user data and it's friend cloud-init since 2016 because they are both so very naughty. For example, did you know you could remotely modify EC2 user data to run code on every boot using the modify-instance-attribute API together with the #cloud-boothook decorator? Have a go at the lab and let Rich know what you think.

  • Defense in Depth approach using AWS by Ahmed Srebrenica and Why Multi-Account in AWS? by Marty Henderson

    Two articles in one dish? The power has gone to my head. No one can stop me! These two articles could just as well be one. The take away is to use the controls that AWS offers to create trust boundaries that require multiple failures for a catastrophe to occur. The defence-in-depth article is very EC2+networking implementation focused while the multi-account one is a sales pitch for going mad with MOAR accounts.

๐Ÿฅ— 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

๐ŸŽฎ Amazon Linux vulnerabilities

YouTube Twitter LinkedIn