39 of 50 in All Controls
aws

Implement Account Provisioning Automation

IDAWS-ORG-006
Severity
high
Automation
Auto
Category
governance
Enforcementmandatory
Complexity / Impact
high(low impact)
Risk Profile
medium likelihood(low residual)
Cloud Scopeaws:root
Environments
productionnon-productionsandbox
Target Resources
AWS::ControlTower::LandingZoneAWS::ServiceCatalog::CloudFormationProvisionedProductAWS::Organizations::Account
Services
control-towerorganizationsservice-catalogcloudformation
Tags
governanceautomationaccount-factoryprovisioninglanding-zone
Frameworks
NIST 800-53ISO 27001PCI DSSSOC 2
Depends On
Governance
Cloud Security (quarterly)
Created
2026-05-03
Last Updated
2026-11-17

Specification & Description

Automate AWS account vending through AWS Control Tower Account Factory, Account Factory for Terraform (AFT), or an IaC-backed account pipeline so every new account receives baseline guardrails and OU placement at creation.

Technical Specifications

Manual account creation is error-prone and does not scale across an enterprise landing zone. Automated account vending via AWS Control Tower Account Factory (backed by AWS Service Catalog ProvisionProduct, where ManagedOrganizationalUnit must use the "OU_NAME (OU_ID)" format), Account Factory for Terraform (AFT), Customizations for Control Tower (CfCT), or organizations:CreateAccount paired with service-managed CloudFormation StackSets ensures every new account lands in its target OU with CloudTrail, AWS Config, IAM Identity Center roles, and security baselines already active.

Security Rationale

Inconsistent account setup introduces unmonitored accounts with missing guardrails. Automated vending guarantees every account starts with a uniform security posture and traceable approval metadata.

Business & Security Impact

Manual provisioning creates snowflake accounts lacking baseline logging, Config recorders, or OU guardrails, slowing delivery teams and opening blind spots between account creation and security onboarding.

Compliance Framework Mappings (4)

Regulatory baselines and industry standards mapped to this control specification.

Beta
Framework / StandardMapped Requirements & ControlsControls
NIST 800-53 Rev 5NIST 800-53
CM-2AC-2CM-6
3
ISO 27001:2022ISO 27001
A.5.15A.8.9A.8.32
3
PCI DSS v4.0PCI DSS
2.2.1
1
SOC 2SOC 2
CC6.2CC8.1
2

* Compliance framework mappings are provided for informational architectural reference. Always verify control alignment against your organization's formal audit requirements.

Automated Detection & Rule Logic

Detection Engine: aws-api • Automated: Yes

Query AWS Control Tower for active landing zones and enabled OU baselines, search Service Catalog for Account Factory provisioned products, and inspect AWS Organizations account creation history and joined methods to verify accounts are vended through automation. Required IAM permissions: controltower:ListLandingZones, controltower:ListEnabledBaselines, servicecatalog:SearchProvisionedProducts, organizations:ListAccounts, and organizations:ListCreateAccountStatus.

Audit Landing Zone Baselines, Provisioned Accounts, and Account Creation Statusbash
# 1. Check Control Tower landing zone and enabled baselines
aws controltower list-landing-zones \
  --query "landingZones[*].arn" \
  --output json

aws controltower list-enabled-baselines \
  --query "enabledBaselines[*].{Baseline:baselineIdentifier,Target:targetIdentifier,Status:statusSummary.status}" \
  --output json

# 2. Search provisioned products via Service Catalog (Account Factory)
aws servicecatalog search-provisioned-products \
  --access-level-filter Key=Account,Value=self \
  --query "ProvisionedProducts[*].{Name:Name,Id:Id,Status:Status,ProductName:ProductName}" \
  --output json

# 3. Review Organizations account creation requests and account inventory
aws organizations list-create-account-status \
  --query "CreateAccountStatuses[*].{Id:Id,AccountName:AccountName,State:State,AccountId:AccountId}" \
  --output json

aws organizations list-accounts \
  --query "Accounts[*].{Id:Id,Name:Name,Status:Status,JoinedMethod:JoinedMethod}" \
  --output json

Remediation Guide & Automation

Deploy AWS Control Tower Account Factory (with AFT or CfCT for GitOps customizations) or build an automated vending pipeline using organizations:CreateAccount and SERVICE_MANAGED CloudFormation StackSets. Require all account requests to specify target OU, account owner, and baseline tags. Required IAM permissions: servicecatalog:ProvisionProduct, organizations:CreateAccount, organizations:MoveAccount, and controltower:EnableBaseline.

Step-by-Step Instructions

  1. Deploy an AWS Control Tower landing zone or standardized account vending pipeline.
  2. Configure baseline customizations (CloudTrail, AWS Config, GuardDuty, Security Hub, and VPC defaults) in AFT, CfCT, or StackSets.
  3. Enforce target OU selection using the Control Tower 'OU_NAME (OU_ID)' parameter format so inherited SCPs and RCPs apply immediately.
  4. Integrate account requests with ITSM or Git pull-request approvals and disallow ad-hoc CreateAccount usage outside the pipeline.
  5. Audit Control Tower landing zone baselines and Service Catalog provisioned products periodically for drift.
Verify Control Tower Landing Zone and Service Catalog Account Factory Productsbash
# 1. Confirm Control Tower Landing Zone is deployed
aws controltower list-landing-zones \
  --query "landingZones[*].arn" \
  --output json

# 2. List provisioned Account Factory products in Service Catalog
aws servicecatalog search-provisioned-products \
  --access-level-filter Key=Account,Value=self \
  --query "ProvisionedProducts[*].{Name:Name,Id:Id,Status:Status,ProductName:ProductName}" \
  --output json

We value your privacy

We use analytics cookies to understand how visitors interact with our site and to improve the user experience. You can choose to accept or decline these cookies.