38 of 50 in All Controls
aws

Protect Management Account from Workload Deployment

IDAWS-ORG-005
Severity
critical
Automation
Auto
Category
governance
Enforcementmandatory
Complexity / Impact
medium(low impact)
Risk Profile
medium likelihood(low residual)
Cloud Scopeaws:account
Environments
production
Target Resources
AWS::IAM::PolicyAWS::Organizations::Account
Services
organizationsiamec2rdsecsekslambda
Tags
governanceiammanagement-accountpreventativelanding-zone
Frameworks
NIST 800-53ISO 27001PCI DSSSOC 2
Governance
Cloud Security (annually)
Created
2026-05-03
Last Updated
2026-11-17

Specification & Description

Keep the AWS Organizations Management account strictly as a control plane by enforcing IAM permission boundaries, delegating service administration to dedicated member accounts, and continuously auditing for workload resources.

Technical Specifications

Service Control Policies (SCPs) do not affect users, roles, or the root user in the Management account, and the Management account cannot be placed into an Organizational Unit (OU). Relying on SCPs to block compute or database provisioning inside the Management account fails silently. Instead, enforce control-plane isolation using IAM permission boundaries or explicit Deny identity policies on Management account roles and IAM Identity Center permission sets, offload security and infrastructure administration via organizations:RegisterDelegatedAdministrator, restrict CI/CD deployment pipelines from targeting the Management account, and run continuous inventory checks for EC2, RDS, ECS, EKS, and Lambda workloads.

Security Rationale

Any workload running inside the Management account expands the attack surface of the entire organization. A compromised application role or instance profile in the Management account can tamper with SCPs, account baselines, and billing controls across every member account.

Business & Security Impact

Running application workloads or shared services in the Management account creates a single point of catastrophic compromise for the landing zone and complicates least-privilege administration.

Operational & Implementation Notes

Resource Control Policies (RCPs) apply to the Management account for supported resource-side data perimeter protections (such as S3, SQS, STS, and Secrets Manager), but they do not replace IAM permission boundaries for preventing compute provisioning.

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
AC-6CM-7SC-7
3
ISO 27001:2022ISO 27001
A.5.15A.8.2A.8.22
3
PCI DSS v4.0PCI DSS
2.2.17.2.2
2
SOC 2SOC 2
CC6.1CC6.3
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

Confirm the current Management account ID via describe-organization, inspect IAM role permission boundaries and delegated administrator registrations, and scan the Management account for EC2, RDS, ECS, EKS, and Lambda workload resources. Required IAM permissions: organizations:DescribeOrganization, organizations:ListDelegatedAdministrators, iam:ListRoles, ec2:DescribeInstances, rds:DescribeDBInstances, ecs:ListClusters, eks:ListClusters, and lambda:ListFunctions.

Audit Management Account Workloads, Boundaries, and Delegated Adminsbash
# 1. Confirm Management account ID and delegated administrators
aws organizations describe-organization \
  --query "Organization.{Id:Id,ManagementAccountId:MasterAccountId}" \
  --output json

aws organizations list-delegated-administrators \
  --query "DelegatedAdministrators[*].{Id:Id,Name:Name,Status:Status}" \
  --output json

# 2. Check IAM roles lacking a permissions boundary in the Management account
aws iam list-roles \
  --query "Roles[?PermissionsBoundary==\`null\`].{RoleName:RoleName,Path:Path}" \
  --output json

# 3. Scan Management account for compute and database workloads
aws ec2 describe-instances \
  --query "Reservations[*].Instances[*].{InstanceId:InstanceId,State:State.Name}" \
  --output json

aws rds describe-db-instances \
  --query "DBInstances[*].{Id:DBInstanceIdentifier,Status:DBInstanceStatus}" \
  --output json

aws ecs list-clusters \
  --query "clusterArns" \
  --output json

aws eks list-clusters \
  --query "clusters" \
  --output json

aws lambda list-functions \
  --query "Functions[*].FunctionName" \
  --output json

Remediation Guide & Automation

Inventory and migrate any existing compute, database, or serverless workloads out of the Management account into member accounts, attach an IAM permission boundary denying workload creation actions on Management account operator roles, and register dedicated member accounts as delegated administrators for security and infrastructure services. Required IAM permissions: iam:CreatePolicy, iam:PutRolePermissionsBoundary, organizations:RegisterDelegatedAdministrator, and organizations:ListDelegatedAdministrators.

Step-by-Step Instructions

  1. Audit the Management account for existing EC2, RDS, ECS, EKS, and Lambda resources and migrate them to member accounts.
  2. Create an IAM permission boundary policy denying workload creation APIs (ec2:RunInstances, rds:CreateDBInstance, rds:CreateDBCluster, ecs:CreateCluster, eks:CreateCluster, lambda:CreateFunction).
  3. Attach the permission boundary to all human and automation IAM roles in the Management account.
  4. Register Security Tooling and Infrastructure member accounts as delegated administrators for GuardDuty, Security Hub, Config, IAM Access Analyzer, and VPC IPAM.
  5. Restrict IAM access to the Management account to break-glass and organization administration workflows only.
Management Account IAM Permission Boundary Policyjson
{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Sid": "AllowControlPlaneBaseline",
      "Effect": "Allow",
      "Action": "*",
      "Resource": "*"
    },
    {
      "Sid": "DenyWorkloadProvisioningInManagementAccount",
      "Effect": "Deny",
      "Action": [
        "ec2:RunInstances",
        "rds:CreateDBInstance",
        "rds:CreateDBCluster",
        "ecs:CreateCluster",
        "eks:CreateCluster",
        "lambda:CreateFunction"
      ],
      "Resource": "*"
    }
  ]
}
Apply IAM Permission Boundary and Verify Delegated Adminsbash
# 1. Create the Management account workload-deny permission boundary policy
boundary_arn=$(aws iam create-policy \
  --policy-name 'DenyManagementAccountWorkloads' \
  --description 'Permission boundary preventing workload provisioning in the Management account' \
  --policy-document file://deny-mgmt-workloads.json \
  --query "Policy.Arn" \
  --output text)

# 2. Attach the permission boundary to an operator role in the Management account
aws iam put-role-permissions-boundary \
  --role-name 'OrgOperatorRole' \
  --permissions-boundary "$boundary_arn"

# 3. Verify delegated administrator accounts are registered
aws organizations list-delegated-administrators \
  --query "DelegatedAdministrators[*].{Id:Id,Name:Name,Status:Status}" \
  --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.