Skip to content

Commit

Permalink
Update aws_organizations_defaults.md
Browse files Browse the repository at this point in the history
final updates
  • Loading branch information
WebbinRoot authored Dec 10, 2023
1 parent 1777ce1 commit 2f7e000
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions content/aws/general-knowledge/aws_organizations_defaults.md
Original file line number Diff line number Diff line change
Expand Up @@ -35,15 +35,15 @@ These things combined mean that, should an attacker compromise the management ac

For defensive security teams, it would be a good idea to ensure no infrastructure is deployed into the management account to reduce attack surface. Additionally, carefully controlling who has access to it and monitoring that access would also help to reduce risk.

Note Scott Weston (See References) has added a module to Pacu to brute force this role name or a list of role names. So if a management account is compromised, and the user wants to attempt to assume one to many role names on all accounts, they can run the following Pacu Module
Scott Weston (See References) has added a module to Pacu to brute force this role name or a list of role names. So if a management account is compromised, and the user wants to attempt to assume one to many role names on all accounts, they can run the following Pacu Module
```
Pacu (role:ManagementAccount) > run organizations__assume_role
[ Review the results to see if any of the following roles are assumed]
```

## Inviting Pre-Existing Member Accounts: Trusted Access & Delegated Administration

When a pre-existing AWS account is **invited** to join an organization, it does not auto-generate a default role with AdministratorAccess like the account creation workflow. As a pentester, one can look into trusted access and delegated administration to see if there are any more avenues to pivot such that you can move from the compromised management account/delegated admin to another member account in the organization.
When a pre-existing AWS account is **invited** to join an organization, it does not auto-generate a default role with AdministratorAccess like the account creation workflow. As a pentester, one can look into trusted access and delegated administration to see if there are any more avenues to pivot such that you can move from the compromised management account/delegated admin to another member account in the organization. Depending on the features available, this might allow for indirect access to other member accounts (ex. IAM Access Analyzer), or direct access with some setup (IAM Identity Center).

### Organization-Integrated Features

Expand Down

0 comments on commit 2f7e000

Please sign in to comment.