36 of 50 in All Controls
aws

Mandate Resource Tagging for Governance

IDAWS-ORG-003
Severity
medium
Automation
Auto
Category
governance
Enforcementmandatory
Complexity / Impact
medium(disruptive impact)
Risk Profile
medium likelihood(low residual)
Cloud Scopeaws:ou
Environments
productionnon-productionsandbox
Target Resources
AWS::Organizations::PolicyAWS::Config::ConfigRule
Services
organizationsec2s3rdsconfig
Tags
governancetaggingfinopsautomationscplanding-zone
Frameworks
NIST 800-53ISO 27001PCI DSSSOC 2
Governance
Cloud Security (quarterly)
Created
2026-05-03
Last Updated
2026-11-17

Specification & Description

Combine AWS Organizations Tag Policies, Service Control Policies (SCPs), and AWS Config required-tags rules to enforce mandatory tag keys and standardized tag values across landing zone workloads.

Technical Specifications

SCPs do not have a report-only mode; once attached, a Deny SCP immediately blocks non-compliant API calls. Pre-enforcement auditing and rollout use three complementary layers. First, AWS Organizations Tag Policies (TAG_POLICY) standardize tag key casing and allowed values, supporting non-blocking compliance reporting before you enable enforced_for on specific resource types. Second, AWS Config REQUIRED_TAGS detects existing or out-of-band untagged resources. Third, an SCP using Null on aws:RequestTag/KeyName blocks resource creation when mandatory tags are absent. When gating ec2:RunInstances in an SCP, scope the Resource array to instance and volume ARNs rather than a wildcard because referenced VPC, subnet, image, and security group ARNs do not carry request tags.

Security Rationale

Consistent tagging drives cost allocation, owner accountability, automated incident routing, and attribute-based access control (ABAC). Enforcing tag standards at creation time avoids expensive retroactive tagging across thousands of resources.

Business & Security Impact

Missing or inconsistent tags break FinOps chargeback, hide resource ownership during security incidents, and weaken ABAC boundaries. Scoping an ec2:RunInstances tagging SCP to Resource '*' blocks valid tagged launches whenever referenced VPC or AMI sub-resources lack request tags.

Operational & Implementation Notes

Some creation APIs (such as s3:CreateBucket) do not evaluate aws:RequestTag condition keys in SCPs. Use Tag Policies with s3:bucket in enforced_for and AWS Config REQUIRED_TAGS to cover S3 buckets and pre-existing resources.

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-8CM-2AC-3
3
ISO 27001:2022ISO 27001
A.5.9A.5.12A.8.9
3
PCI DSS v4.0PCI DSS
2.2.1
1
SOC 2SOC 2
CC6.1CC8.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

Inspect both SERVICE_CONTROL_POLICY and TAG_POLICY policies and their targets in AWS Organizations, query Resource Groups Tagging API get-compliance-summary from the Management account in us-east-1 alongside list-required-tags, and verify AWS Config required-tags rules are active. Required IAM permissions: organizations:ListPolicies, organizations:DescribePolicy, organizations:ListTargetsForPolicy, tag:GetComplianceSummary, tag:ListRequiredTags, and config:DescribeConfigRules.

Audit Tag Policies, SCPs, Tagging Compliance, and Config Rulesbash
# 1. List Tag Policies and custom SCPs, and inspect content and targets
for pid in $(aws organizations list-policies \
  --filter TAG_POLICY \
  --query "Policies[*].Id" \
  --output text); do
  aws organizations describe-policy \
    --policy-id "$pid" \
    --query "Policy.{Id:PolicySummary.Id,Name:PolicySummary.Name,Content:Content}" \
    --output json
  aws organizations list-targets-for-policy \
    --policy-id "$pid" \
    --query "Targets[*].{TargetId:TargetId,Name:Name,Type:Type}" \
    --output json
done

for pid in $(aws organizations list-policies \
  --filter SERVICE_CONTROL_POLICY \
  --query "Policies[?AwsManaged==\`false\`].Id" \
  --output text); do
  aws organizations describe-policy \
    --policy-id "$pid" \
    --query "Policy.{Id:PolicySummary.Id,Name:PolicySummary.Name,Content:Content}" \
    --output json
  aws organizations list-targets-for-policy \
    --policy-id "$pid" \
    --query "Targets[*].{TargetId:TargetId,Name:Name,Type:Type}" \
    --output json
done

# 2. Query organization-wide tag compliance summary (Management account, us-east-1) and required tag keys
aws resourcegroupstaggingapi get-compliance-summary \
  --region us-east-1 \
  --group-by TARGET_ID RESOURCE_TYPE \
  --query "SummaryList[*].{TargetId:TargetId,Region:Region,ResourceType:ResourceType,NonCompliantResources:NonCompliantResources}" \
  --output json

aws resourcegroupstaggingapi list-required-tags \
  --query "RequiredTags[*].{ResourceType:ResourceType,ReportingTagKeys:ReportingTagKeys}" \
  --output json

# 3. Verify AWS Config rules are active in the account
aws configservice describe-config-rules \
  --query "ConfigRules[*].{Name:ConfigRuleName,State:ConfigRuleState,Source:Source.SourceIdentifier}" \
  --output json

Remediation Guide & Automation

Define a canonical tag schema, deploy AWS Organizations Tag Policies and AWS Config required-tags rules first to audit non-compliant workloads without blocking, and then attach an aws:RequestTag Deny SCP to target workload OUs with properly scoped EC2 instance and volume ARNs. Required IAM permissions: organizations:ListRoots, organizations:EnablePolicyType, organizations:CreatePolicy, organizations:ListOrganizationalUnitsForParent, organizations:AttachPolicy, and config:PutConfigRule.

Step-by-Step Instructions

  1. Define mandatory tag keys (such as CostCenter, Owner, and Environment) and allowed values.
  2. Enable TAG_POLICY on the Organization Root and attach a Tag Policy without enforced_for first to collect baseline compliance metrics.
  3. Deploy the AWS Config REQUIRED_TAGS managed rule across member accounts to flag existing untagged resources.
  4. Enable enforced_for in the Tag Policy for supported resource types once teams remediate legacy drift.
  5. Attach the tag-presence Deny SCP (scoping ec2:RunInstances to instance/* and volume/* ARNs) to a sandbox OU, validate IaC templates, and promote to workload OUs.
Tag Presence Enforcement SCPjson
{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Sid": "DenyEC2RunWithoutOwnerTag",
      "Effect": "Deny",
      "Action": "ec2:RunInstances",
      "Resource": [
        "arn:aws:ec2:*:*:instance/*",
        "arn:aws:ec2:*:*:volume/*"
      ],
      "Condition": {
        "Null": {
          "aws:RequestTag/Owner": "true"
        }
      }
    },
    {
      "Sid": "DenyEC2RunWithoutCostCenterTag",
      "Effect": "Deny",
      "Action": "ec2:RunInstances",
      "Resource": [
        "arn:aws:ec2:*:*:instance/*",
        "arn:aws:ec2:*:*:volume/*"
      ],
      "Condition": {
        "Null": {
          "aws:RequestTag/CostCenter": "true"
        }
      }
    },
    {
      "Sid": "DenyRDSCreateWithoutOwnerTag",
      "Effect": "Deny",
      "Action": "rds:CreateDBInstance",
      "Resource": "*",
      "Condition": {
        "Null": {
          "aws:RequestTag/Owner": "true"
        }
      }
    },
    {
      "Sid": "DenyRDSCreateWithoutCostCenterTag",
      "Effect": "Deny",
      "Action": "rds:CreateDBInstance",
      "Resource": "*",
      "Condition": {
        "Null": {
          "aws:RequestTag/CostCenter": "true"
        }
      }
    }
  ]
}
AWS Organizations Tag Policyjson
{
  "tags": {
    "CostCenter": {
      "tag_key": {
        "@@assign": "CostCenter"
      }
    },
    "Owner": {
      "tag_key": {
        "@@assign": "Owner"
      }
    },
    "Environment": {
      "tag_key": {
        "@@assign": "Environment"
      },
      "tag_value": {
        "@@assign": [
          "production",
          "non-production",
          "sandbox"
        ]
      },
      "enforced_for": {
        "@@assign": [
          "ec2:instance",
          "ec2:volume",
          "rds:db",
          "s3:bucket"
        ]
      }
    }
  }
}
Enable and Attach Tag Policy via AWS CLIbash
# 1. Enable TAG_POLICY on Organization Root
root_id=$(aws organizations list-roots \
  --query "Roots[0].Id" \
  --output text)

aws organizations enable-policy-type \
  --root-id "$root_id" \
  --policy-type TAG_POLICY

# 2. Create and attach the Tag Policy to a target OU
tag_policy_id=$(aws organizations create-policy \
  --name 'OrgTagStandardPolicy' \
  --description 'Standardize tag keys and allowed values across landing zone OUs' \
  --type TAG_POLICY \
  --content file://tag-policy.json \
  --query "Policy.PolicySummary.Id" \
  --output text)

ou_id=$(aws organizations list-organizational-units-for-parent \
  --parent-id "$root_id" \
  --query "OrganizationalUnits[?Name=='Workloads'].Id | [0]" \
  --output text)

aws organizations attach-policy \
  --policy-id "$tag_policy_id" \
  --target-id "$ou_id"

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.