Join our Newsletter — 33% off our NHI Course

Why do July AWS permissions widen identity blast radius?

 

(@nhi-mgmt-group)
Member Moderator
Joined: 2 years ago
Posts: 20225
Topic starter  

TL;DR: AWS privileged permissions are widening identity blast radius, as Sonrai Security says July AWS service updates added actions that can expand what existing roles control. Cloud access reviews need to catch new verbs before they slip into privileged roles.

Editorial analysis by NHI Mgmt Group, based on content published by Sonrai Security: “July Recap: New AWS Services and Privileged Permissions”.

Key questions

Q: Why do new sensitive cloud permissions increase the risk of lateral movement and defense evasion?

A: New sensitive permissions often expand the set of actions an identity can take without changing its user-facing role.

Q: How do security teams know whether least privilege is actually working?

A: Least privilege is working when identities have narrowly scoped permissions, unused credentials are removed or quarantined, and repeated access reviews consistently shrink entitlements.

Q: What breaks when new cloud service permissions are added without a role review?

A: Least privilege becomes stale as soon as the new action lands, because existing roles can suddenly control execution, routing, or security boundaries that were never in scope when the role was designed.

Practitioner guidance

  • Map new service actions to privilege tiers Classify newly introduced AWS permissions by whether they create execution, movement, policy-change, or monitoring-impact risk before they are added to roles.
  • Separate deployment from data-access authority Do not let the same role both deploy runtimes and reach sensitive artefacts, especially in AI and database services where execution and access can collapse into one permission set.
  • Review control-plane permissions as security controls Treat firewall, gateway, peering, and scan-management actions as control-boundary changes and require the same scrutiny you apply to direct data-access entitlements.

Bottom line: New AWS permissions can quietly enlarge the scope of existing cloud identities even when the underlying accounts do not change.

Glossary terms: Control-plane permission, Identity Blast Radius, Control-Plane Authority, Release-Aware Authorization

Explore further

View Full Forum →  |  NHI Foundation Course →  |  Our Services →  |  Read the full analysis →


This topic was modified 4 days ago by NHI Mgmt Group

   
Quote
(@mr-nhi)
Member Moderator
Joined: 6 months ago
Posts: 20715
 

Cloud privilege risk now starts at service release time, not only at account creation time. The article shows that new AWS permissions can change the effective power of existing identities as soon as they appear. That means cloud governance is no longer just about provisioning and review cadence, but about continuously tracking the privilege impact of platform change itself. Practitioners should treat release notes as access-control inputs, not product news.

A few things that frame the scale:

  • 92% of organisations expose NHIs to third parties, raising concerns about supply chain security, according to the Ultimate Guide to NHIs.
  • 97% of NHIs carry excessive privileges, increasing unauthorised access and broadening the attack surface, according to the Ultimate Guide to NHIs.

A question worth separating out:

Q: What should teams do when a cloud permission can change firewall, gateway, or scan settings?

A: Treat that permission as a boundary-changing control, not a routine admin right. Those actions can weaken detection, alter enforcement, or redirect traffic, so they need stricter approval paths, logging, and periodic reassessment than ordinary operational permissions.

👉 Read our full editorial: New AWS privileged permissions are widening cloud access risk



   
ReplyQuote
Share:

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.