Issue #277
Monday · September 07, 2026
🥖 Palate Cleanser
fwd:cloudsec Europe is on today and tomorrow in London, and I'm sure it will be an awesome event. Both days are streamed if you didn't make it over, day one and day two. Selfishly, what I'm really looking forward to is the flurry of blog posts that follows.
Act Security bought Cloud Copilot and David Kerber went with it. If you use iam-collect, iam-lens, iam-simulate or iam-expand, they moved to the act-security-labs org on 1 September and they are still AGPL-3.0. They are bundled now as Amphi with a browser UI and no signup. The small loss is that iam.cloudcopilot.io now 302s to the corporate site, so the independent blog is gone, and the posts I ran on Policy Tester in issue 192, fantastic AWS policies in 229 and testing S3 ABAC with iam-lens in 240 all live there now.
Reminder that nominations for the Top 10 AWS Security Research of 2026 close on 30 September. No login, no email address, self-nominations welcome, and I would much rather sift through too many than miss the good stuff. Go put something in.
This issue is also available to share online. Got feedback? Tell us here.
📋 Chef's selections
Reading other AWS accounts' SQL on Amazon Athena
by Act Research
Athena, the query service for S3, has an engine called Trino. Trino ships a system.runtime.queries table that lists recently executed queries, and on shared infrastructure "recently executed" means everybody's. Asking for the system catalog inside the SQL gets you "Queries of this type are not supported", but nobody was checking the same request's QueryExecutionContext, so you leave the catalog out of the SQL, pass Catalog=system as a parameter alongside it, and the query runs. What comes back is other tenants' actual query text, which means their account IDs and whatever they inlined into a WHERE or an INSERT. Across 200 runs by Act Security, 2,590 of 2,794 rows belonged to somebody else, and in a second round 102 of 109 runs caught at least one other account. It was reported on 6 August 2026, the call was disabled on the 8th, and every region fixed by the 10th, which is genuinely fast work. No CVE or bulletin though? However, AWS did publish a bulletin last month for an Athena federated connector template that leaked Secrets Manager secrets in your own account. 🤷
Password spraying campaign targets AWS root user accounts across 150+ organizations
From 24 July to 23 August somebody worked through the root user of more than 150 organisations, a median of two attempts each and up to eight, proxied through hosting and residential IPs across a spread of countries and ASNs. Apparently nothing worked. A failed root ConsoleLogin requires the root account's email address, so whoever this is either already holds a list of root emails or found them by grinding through candidates. I wonder how big the full attack was outside of DD's visibility. Root MFA has been mandatory since June 2025 but you should still be alerting on ConsoleLogin with userIdentity.type of Root, and if you have not moved to centralized root access with short-lived AssumeRoot sessions and an SCP shutting the rest down, this is the nudge. Neither of those covers your management account root though, which still needs its own answer.
💸 Sponsor shoutout
Most code shipped today is AI-generated and the triage queue grew to match. Pleri AI works out which findings are actually exploitable and submits the fix. See the platform and get a free assessment.
🥗 AWS security blogs
- 📢 AWS Transfer Family SFTP Connectors now support continuing file transfers during credential rotation
- 📢 Amazon WorkSpaces Applications adds support for NVIDIA Blackwell GPU instances
- 📢 Amazon Linux 2027 is now available in public preview
- 📢 AWS Backup now supports protecting more than 1,000 Amazon S3 buckets per account
- 📢 Amazon Cognito now supports machine-to-machine authorization without a user pool domain
- 📢 Automated Security Response on AWS adds AI Toolkit for custom remediations
- Say Hello to 158 New AWS Competency and MSP Partners Added in August by Nick Paris
- Aligning AWS to MPA security best practices for media archives – Part 3 by Jakob Rosinski
- Aligning AWS to MPA security best practices for media archives – Part 1 by Jakob Rosinski
- Reduce Traffic Interruptions with Gateway Load Balancer TCP Reset by Donathan Ratcliffe
- Implementing encryption in transit across connectivity patterns with VPC Encryption Controls by Rohit Aswani
- AWS expands its Defending Digital Campaigns offering for the 2026 election cycle by Leo Zhadanovsky
- How to secure communications beyond encryption with AWS Wickr by Chris O’Rourke
- OSPAR 2026 report now available with 167 services in scope by James Chang
- Incident response guide for AWS CloudTrail investigations – Part 2 by Oscar Diaz
- Incident response guide for AWS CloudTrail investigations – Part 1 by Oscar Diaz
- Managing identity source transition for AWS IAM Identity Center by Xiaoxue Xu
- Agentic security: Detection and response at machine speed by Gee Rittenhouse
- We invited a direct competitor into Security Hub Extended. Here’s why. by Michael Fuller
- Automate IAM Identity Center governance with continuous discovery and reporting by Jonathan Nguyen
🍛 Reddit threads on r/aws
🤖 Dessert
Every machine-tracked change this week. Nobody else assembles this.
🧁 IAM permission changes
🍪 API changes
🍹 IAM managed policy changes
☕ CloudFormation resource changes
🎮 Amazon Linux vulnerabilities
📺 AWS security bulletins
🚬 Security documentation changes
No changes this week.