27 of 50 in All Controls
aws

Log Archive Account Isolation and Immutability Guardrails

IDAWS-LOG-005
Severity
critical
Automation
Auto
Category
logging
Enforcementmandatory
Complexity / Impact
high(disruptive impact)
Risk Profile
high likelihood(low residual)
Cloud Scopeaws:ou
Environments
all
Target Resources
AWS::Organizations::PolicyAWS::IAM::RoleAWS::KMS::KeyAWS::S3::Bucket
Services
aws-organizationss3kmscloudwatch-logsiam
Tags
logginglog-archivescpgovernanceimmutabilityisolationlanding-zone
Frameworks
NIST 800-53ISO 27001SOC 2PCI DSSHIPAA
Governance
Cloud Security (quarterly)
Created
2026-05-03
Last Updated
2026-08-21

Specification & Description

Enforce strict account-level isolation and preventative Service Control Policies (SCPs) on the dedicated Log Archive account to prohibit deletion of log groups, destruction of encryption keys, tampering with lifecycle rules, and unauthorized interactive administrative access.

Technical Specifications

The dedicated Log Archive account is the central vault for all security audit trails across the AWS Landing Zone. Because it stores forensic evidence, it requires the most restrictive account boundary in the entire organization.

1. Preventative SCP Guardrails on the Log Archive OU

  • Attached to the dedicated Core/Security Organizational Unit containing the Log Archive account.
  • Denies deletion or modification of CloudWatch log groups (logs:DeleteLogGroup, logs:DeleteRetentionPolicy).
  • Denies KMS key destruction or disablement (kms:ScheduleKeyDeletion, kms:DisableKey).
  • Denies modification of S3 lifecycle policies (s3:PutLifecycleConfiguration, s3:DeleteBucketLifecycle) to prevent accelerating log expiration.
  • Denies tampering with organization trails or S3 Object Lock settings.

2. Zero Standing Privileges & Break-Glass Access Model

  • No engineers, developers, or standard administrators should have standing interactive access or permanent IAM credentials in the Log Archive account.
  • Access is restricted exclusively to automated service principals (CloudTrail, VPC Flow Logs, Config) and an audited, MFA-gated Break-Glass Emergency Role monitored by automated alerts.

Security Rationale

If an adversary compromises an organization administrator credential, account-level guardrails and SCPs prevent the attacker from destroying historical audit logs, deleting KMS keys, or shortening S3 lifecycle retention. Strict isolation guarantees that forensic evidence survives even worst-case organization-level security compromises.

Business & Security Impact

Without account-level isolation, an adversary with elevated privileges can delete log streams, destroy KMS encryption keys, or alter bucket retention policies to permanently erase evidence of a breach.

Compliance Framework Mappings (5)

Regulatory baselines and industry standards mapped to this control specification.

Beta
Framework / StandardMapped Requirements & ControlsControls
NIST 800-53 Rev 5NIST 800-53
AU-9AC-6SC-28
3
ISO 27001:2022ISO 27001
A.8.15A.5.15
2
SOC 2SOC 2
CC6.1CC7.1
2
PCI DSS v4.0PCI DSS
10.5.110.5.2
2
HIPAA Security RuleHIPAA
164.312(b)
1

* 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: custom • Automated: Yes

Evaluates AWS Organizations policy attachments to verify that the Log Archive Isolation SCP is attached to the Log Archive account's OU and that no unapproved standing IAM roles exist in the account.

AWS CLI: List Attached SCPs for Log Archive Accountbash
aws organizations list-policies-for-target \
  --target-id LOG_ARCHIVE_ACCOUNT_ID \
  --filter SERVICE_CONTROL_POLICY \
  --output json
Python (Boto3): Verify Log Archive SCP Attachmentpython
import json
import boto3

org = boto3.client('organizations')

def verify_log_archive_isolation(account_id='LOG_ARCHIVE_ACCOUNT_ID', expected_policy_name='LogArchiveProtectionSCP'):
    policies = org.list_policies_for_target(
        TargetId=account_id,
        Filter='SERVICE_CONTROL_POLICY'
    ).get('Policies', [])

    attached_names = [p['Name'] for p in policies]
    if any(expected_policy_name.lower() in name.lower() for name in attached_names):
        return {"status": "COMPLIANT", "attached_policies": attached_names}
    return {
        "status": "NON_COMPLIANT",
        "reason": f"Expected isolation policy '{expected_policy_name}' not found",
        "attached": attached_names
    }

if __name__ == "__main__":
    result = verify_log_archive_isolation()
    print(json.dumps(result, indent=2))

Preventative Enforcement Policies

SCP: Comprehensive Log Archive Account Tamper-Proof Guardrailjson
{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Sid": "DenyKMSKeyDestruction",
      "Effect": "Deny",
      "Action": [
        "kms:ScheduleKeyDeletion",
        "kms:DisableKey",
        "kms:DeleteAlias"
      ],
      "Resource": "*",
      "Condition": {
        "ArnNotLike": {
          "aws:PrincipalArn": [
            "arn:aws:iam::*:role/aws-service-role/*",
            "arn:aws:iam::*:role/BreakGlassSecurityRole"
          ]
        }
      }
    },
    {
      "Sid": "DenyCloudWatchLogsDeletion",
      "Effect": "Deny",
      "Action": [
        "logs:DeleteLogGroup",
        "logs:DeleteLogStream",
        "logs:DeleteRetentionPolicy",
        "logs:DeleteSubscriptionFilter"
      ],
      "Resource": "*",
      "Condition": {
        "ArnNotLike": {
          "aws:PrincipalArn": [
            "arn:aws:iam::*:role/aws-service-role/*",
            "arn:aws:iam::*:role/BreakGlassSecurityRole"
          ]
        }
      }
    },
    {
      "Sid": "DenyS3LifecycleTampering",
      "Effect": "Deny",
      "Action": [
        "s3:PutLifecycleConfiguration",
        "s3:DeleteBucketLifecycle",
        "s3:PutObjectRetention",
        "s3:PutObjectLegalHold"
      ],
      "Resource": "*",
      "Condition": {
        "ArnNotLike": {
          "aws:PrincipalArn": [
            "arn:aws:iam::*:role/aws-service-role/*",
            "arn:aws:iam::*:role/BreakGlassSecurityRole"
          ]
        }
      }
    }
  ]
}
Terraform: Attach Isolation SCP to Log Archive OUhcl
resource "aws_organizations_policy" "log_archive_isolation_scp" {
  name        = "LogArchiveAccountIsolationGuardrails"
  description = "Prohibits log deletion, KMS key destruction, and retention tampering in Log Archive account"
  content     = data.aws_iam_policy_document.log_archive_scp.json
  type        = "SERVICE_CONTROL_POLICY"
}

resource "aws_organizations_policy_attachment" "attach_to_security_ou" {
  policy_id = aws_organizations_policy.log_archive_isolation_scp.id
  target_id = var.security_ou_id
}

Remediation Guide & Automation

Deploy the Log Archive isolation Service Control Policy (SCP) to the Security OU in AWS Organizations, and revoke standing administrative access to enforce zero-standing-privilege governance.

Step-by-Step Instructions

  1. Create the Log Archive Isolation SCP in the AWS Organizations Management account.
  2. Attach the policy to the Organizational Unit (OU) containing the Log Archive account.
  3. Audit and remove all standing IAM users, permanent access keys, and standard administrator roles in the Log Archive account.
  4. Configure an audited Break-Glass emergency IAM role with mandatory hardware MFA.
  5. Configure Amazon EventBridge alerts for any assume-role activity on the Break-Glass role.
AWS CLI: Attach Isolation SCP to Log Archive Account or OUbash
aws organizations attach-policy \
  --policy-id p-xxxxxxxxxx \
  --target-id ou-xxxx-xxxxxxxx

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.