46 of 50 in All Controls
aws

Enable AWS Config Conformance Packs

IDAWS-SEC-007
Severity
high
Automation
Auto
Category
security
Enforcementmandatory
Complexity / Impact
medium(low impact)
Risk Profile
medium likelihood(low residual)
Cloud Scopeaws:root
Environments
all
Target Resources
AWS::Config::OrganizationConformancePack
Services
configorganizationss3
Tags
configuration-managementcomplianceconformance-packsautomationlanding-zone
Frameworks
NIST 800-53ISO 27001PCI DSSSOC 2
Depends On
Governance
Cloud Security (quarterly)
Created
2026-05-03
Last Updated
2026-11-20

Specification & Description

Deploy organization-wide AWS Config Conformance Packs from the Security delegated administrator account to standardize detective compliance rule bundles and automated remediation across all member accounts.

Technical Specifications

AWS Config Conformance Packs bundle Config rules and Systems Manager remediation actions into versioned YAML templates that deploy uniformly across an AWS Organization from the delegated administrator account (config-multiaccountsetup.amazonaws.com).

1. Standard Conformance Pack Templates

  • Base organizational packs on maintained AWS Config sample templates from awslabs/aws-config-rules (for example Operational-Best-Practices-for-NIST-800-53-rev-5.yaml and Operational-Best-Practices-for-CIS-AWS-v1.4-Level1.yaml), tailored to landing zone controls. Note that CIS AWS Foundations Benchmark v3.0 requires a custom conformance pack or AWS Security Hub's CIS v3.0 standard.

2. Delivery Bucket Naming and Exclusions

  • Organization conformance packs store packaged templates and intermediate artifacts in an S3 delivery bucket whose name begins with the required awsconfigconforms- prefix.
  • Exclude only explicitly approved accounts (such as the Management account or isolated sandbox accounts) via ExcludedAccounts.

Security Rationale

Deploying individual AWS Config rules per account does not scale across a multi-account landing zone and creates policy drift. Organization Conformance Packs enforce a uniform detective baseline from one central control point.

Business & Security Impact

Without organization conformance packs, security teams rely on manual rule deployment or ad-hoc scripts, causing inconsistent compliance coverage across accounts and slow detection of misconfigurations.

Operational & Implementation Notes

The Management account is not automatically included when deploying organization conformance packs from a delegated administrator account; deploy a standalone conformance pack in the Management account if required. Always prefix the delivery S3 bucket name with awsconfigconforms- so the Config service-linked role can write conformance pack artifacts.

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-2CM-3CA-2CA-7
4
ISO 27001:2022ISO 27001
A.5.36A.8.9
2
PCI DSS v4.0PCI DSS
2.2.112.1.1
2
SOC 2SOC 2
CC7.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

Verify that config-multiaccountsetup.amazonaws.com has an active delegated administrator, list deployed organization conformance packs, confirm pack statuses are CREATE_SUCCESSFUL or UPDATE_SUCCESSFUL, and inspect any per-account deployment failures.

AWS CLI: Verify Organization Conformance Packs and Deployment Statusbash
# 1. Verify delegated administrator for Config multi-account setup
aws organizations list-delegated-administrators \
  --service-principal config-multiaccountsetup.amazonaws.com \
  --query "DelegatedAdministrators[*].{Id:Id,Name:Name,Status:Status}" \
  --output json

# 2. List deployed organization conformance packs and overall status
aws configservice describe-organization-conformance-packs \
  --region "$HOME_REGION" \
  --query "OrganizationConformancePacks[*].{Name:OrganizationConformancePackName,Bucket:DeliveryS3Bucket,Excluded:ExcludedAccounts}" \
  --output json

aws configservice describe-organization-conformance-pack-statuses \
  --region "$HOME_REGION" \
  --query "OrganizationConformancePackStatuses[*].{Name:OrganizationConformancePackName,Status:Status,ErrorCode:ErrorCode}" \
  --output json

# 3. Inspect any member accounts where pack deployment did not succeed
aws configservice get-organization-conformance-pack-detailed-status \
  --organization-conformance-pack-name "$CONFORMANCE_PACK_NAME" \
  --region "$HOME_REGION" \
  --query "OrganizationConformancePackDetailedStatuses[?Status!='CREATE_SUCCESSFUL' && Status!='UPDATE_SUCCESSFUL'].{AccountId:AccountId,Status:Status,ErrorCode:ErrorCode}" \
  --output json

Preventative Enforcement Policies

SCP: Prevent Unauthorized Conformance Pack Deletion or Modificationjson
{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Sid": "ProtectConfigConformancePacks",
      "Effect": "Deny",
      "Action": [
        "config:DeleteOrganizationConformancePack",
        "config:DeleteConformancePack",
        "config:PutOrganizationConformancePack"
      ],
      "Resource": "*",
      "Condition": {
        "ArnNotLike": {
          "aws:PrincipalArn": [
            "arn:aws:iam::*:role/LandingZoneAdminRole"
          ]
        }
      }
    }
  ]
}

Remediation Guide & Automation

From the Security account registered as delegated administrator for `config-multiaccountsetup.amazonaws.com`, deploy organization conformance packs using versioned templates in S3 and an `awsconfigconforms-*` delivery bucket, then monitor per-account deployment status and rule compliance.

Step-by-Step Instructions

  1. Confirm the Security account is registered as delegated administrator for config-multiaccountsetup.amazonaws.com and AWS Config recorders are active across target accounts.
  2. Publish curated conformance pack templates (such as Operational-Best-Practices-for-NIST-800-53-rev-5.yaml or Operational-Best-Practices-for-CIS-AWS-v1.4-Level1.yaml) to an S3 bucket in the deployment region.
  3. Provision an S3 delivery bucket prefixed with awsconfigconforms- and deploy the organization conformance pack from the Security account.
  4. Monitor deployment status per member account using describe-organization-conformance-pack-statuses and get-organization-conformance-pack-detailed-status.
  5. Attach the protective SCP to prevent member accounts or unprivileged roles from deleting or overwriting conformance packs.
AWS CLI: Deploy an Organization Conformance Packbash
# Run in the Security account (delegated admin for config-multiaccountsetup.amazonaws.com)
# Note: CONFORMANCE_DELIVERY_BUCKET must start with "awsconfigconforms-"
# Example: CONFORMANCE_PACK_NAME="nist-800-53-rev5"
aws configservice put-organization-conformance-pack \
  --organization-conformance-pack-name "$CONFORMANCE_PACK_NAME" \
  --template-s3-uri "s3://$TEMPLATE_BUCKET/Operational-Best-Practices-for-NIST-800-53-rev-5.yaml" \
  --delivery-s3-bucket "$CONFORMANCE_DELIVERY_BUCKET" \
  --region "$HOME_REGION"
Terraform: Deploy an Organization Conformance Packhcl
variable "conformance_pack_name" {
  type        = string
  description = "Name of the AWS Config organization conformance pack (for example, nist-800-53-rev5)."
}

variable "template_s3_uri" {
  type        = string
  description = "S3 URI of the conformance pack YAML template in the same region (for example, Operational-Best-Practices-for-NIST-800-53-rev-5.yaml)."
}

variable "delivery_s3_bucket" {
  type        = string
  description = "S3 delivery bucket name prefixed with awsconfigconforms-."
}

resource "aws_config_organization_conformance_pack" "nist_800_53" {
  name               = var.conformance_pack_name
  template_s3_uri    = var.template_s3_uri
  delivery_s3_bucket = var.delivery_s3_bucket
}

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.