Log Archive Account Isolation and Immutability Guardrails
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.
Related Controls & Guardrails (4)
Compliance Framework Mappings (5)
Regulatory baselines and industry standards mapped to this control specification.
| Framework / Standard | Mapped Requirements & Controls | Controls |
|---|---|---|
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.
Preventative Enforcement Policies
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
- Create the Log Archive Isolation SCP in the AWS Organizations Management account.
- Attach the policy to the Organizational Unit (OU) containing the Log Archive account.
- Audit and remove all standing IAM users, permanent access keys, and standard administrator roles in the Log Archive account.
- Configure an audited Break-Glass emergency IAM role with mandatory hardware MFA.
- Configure Amazon EventBridge alerts for any assume-role activity on the Break-Glass role.