Centralized Security Hub Management
Specification & Description
Enable AWS Security Hub across all AWS Organizations accounts and aggregate findings from all operational regions into the designated Security delegated administrator account.
Technical Specifications
AWS Security Hub consolidates security findings and posture checks across AWS accounts and regions into a single delegated administrator account in the Security OU.
1. Delegated Administrator and Organization Modes
- Trusted access for
securityhub.amazonaws.comand delegated administrator designation are configured from the Organizations Management account. - Security Hub supports two organization configuration modes in the
delegated administrator account:
- LOCAL: Sets
AutoEnable = trueandAutoEnableStandards = DEFAULT, automatically enrolling new member accounts with default standards while allowing member-level standard adjustments. - CENTRAL: Sets
AutoEnable = falseandAutoEnableStandards = NONEwithConfigurationType = CENTRAL, governing standards, security controls, and account exclusions from central configuration policies in the home aggregation region.
- LOCAL: Sets
2. Cross-Region Finding Aggregation
- Create a Finding Aggregator in the Security delegated administrator account to replicate findings from linked regions into the home region.
- Route aggregated findings via Amazon EventBridge to the central SIEM or ticketing system so baseline posture findings bypass ad-hoc chat alerts.
3. Member-Account Tamper Prevention
- Attach a Service Control Policy (SCP) to the Organization Root preventing member accounts from disabling Security Hub, detaching from the delegated administrator, deleting aggregators, or disabling standards.
Security Rationale
Decentralized security posture management creates visibility blind spots and inconsistent standards enforcement across accounts. Consolidating findings in a dedicated Security account gives security engineering consistent oversight, while routing findings to a central ticketing or SIEM pipeline prevents alert fatigue in application teams.
Business & Security Impact
Without centralized Security Hub aggregation, misconfigurations and high-severity findings remain fragmented across member accounts, delaying triage and weakening audit evidence across the landing zone.
Operational & Implementation Notes
SCPs never apply to the AWS Organizations Management account, so restricting securityhub:DisableOrganizationAdminAccount relies on Management account IAM policies and break-glass governance rather than SCPs. When using CENTRAL organization configuration mode instead of LOCAL, set auto_enable to false and auto_enable_standards to NONE, then attach an aws_securityhub_configuration_policy to the Organization Root or target OUs.
Related Controls & Guardrails (3)
Compliance Framework Mappings (6)
Regulatory baselines and industry standards mapped to this control specification.
| Framework / Standard | Mapped Requirements & Controls | Controls |
|---|---|---|
NIST 800-53 Rev 5NIST 800-53 | CA-7CM-6 | 2 |
CIS AWS Foundations Benchmark v3.0CIS AWS | 4.16 | 1 |
ISO 27001:2022ISO 27001 | A.8.16 | 1 |
PCI DSS v4.0PCI DSS | 11.6.1 | 1 |
SOC 2SOC 2 | CC7.2 | 1 |
AWS Foundational Security Best PracticesAWS FSBP | SecurityHub.1 | 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: aws-api • Automated: Yes
Verify that the Security account is registered as the Security Hub organization administrator, confirm the organization configuration mode and auto-enable settings in the delegated administrator account, and verify that a cross-region Finding Aggregator is present in the home region.
Preventative Enforcement Policies
Remediation Guide & Automation
Enable trusted access and designate the Security account as the Security Hub delegated administrator from the Management account. From the Security account, enable Security Hub, create a cross-region finding aggregator, configure organization auto-enablement (LOCAL or CENTRAL mode), and route findings via EventBridge to the central SIEM or ticketing workflow.
Step-by-Step Instructions
- From the AWS Organizations Management account, enable trusted access for securityhub.amazonaws.com and designate the Security account as delegated administrator.
- From the Security delegated administrator account, enable Security Hub and create a Finding Aggregator linking all operational regions into the home region.
- Configure organization-wide enrollment in LOCAL mode (auto-enable with default standards) or CENTRAL mode (managed configuration policies).
- Deploy EventBridge rules in the Security account to forward Security Hub findings into the central ticketing system or SIEM.
- Attach the protective SCP to the Organization Root so member accounts cannot disable Security Hub or detach from the administrator.