A global e-commerce corporation manages its multi-account environment using AWS Organizations. The accounts are organized into several Organizational Units (OUs), including a Production workloads OU. Local administrators in these workload accounts possess full administrative rights via the AdministratorAccess IAM policy. To maintain strict regulatory compliance, the central security team must ensure that no user or role, including the root user, within the Production workloads OU can disable Amazon GuardDuty or AWS Security Hub. This security guardrail must apply immediately to all existing workload accounts and be automatically enforced on any new accounts added to the OU. Which solution should a Solutions Architect implement to meet these requirements with the least operational overhead?
- Attach a Service Control Policy (SCP) to the Production workloads OU that denies GuardDuty and Security Hub disabling and modification actions, while allowing local administrators to continue using their existing IAM policies.Cevap
- BConfigure an IAM permission boundary in each workload account that denies GuardDuty and Security Hub modification actions, and mandate that all local administrator roles must have this boundary attached.
- CDeploy an AWS Config rule across all workload accounts to detect unauthorized modifications to GuardDuty and Security Hub, and configure an AWS Systems Manager Automation document to automatically re-enable the services.
- DAttach a Service Control Policy (SCP) to the Production workloads OU that explicitly allows all administrative actions except for GuardDuty and Security Hub operations, and remove the local IAM AdministratorAccess policy from the workload accounts.