Implementing AWS Security Hub to aggregate security findings across AWS accounts, enable compliance standards like CIS AWS Foundations and PCI DSS, configure automated remediation with EventBridge and Lambda, and create custom security insights for organizational risk management.
Standardmäßig ist der Prompt ausgewählt, der zuerst die Quelle prüft. Sie können zu einem direkten Befehl wechseln oder eine lokale Kopie herunterladen.
Quelldateien prüfen
Lesen Sie SKILL.md und alle von SkillsMP angezeigten Begleitdateien, bevor Sie sich für eine Installation entscheiden.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Ein direkter Befehl überspringt den Prüf-Prompt. Prüfen Sie die Quelle, bevor Sie ihn ausführen.
Implementing AWS Security Hub to aggregate security findings across AWS accounts, enable compliance standards like CIS AWS Foundations and PCI DSS, configure automated remediation with EventBridge and Lambda, and create custom security insights for organizational risk management.
When establishing centralized security posture management across multiple AWS accounts
When compliance requirements demand continuous monitoring against CIS, PCI DSS, or NIST 800-53 standards
When aggregating findings from GuardDuty, Inspector, Macie, Firewall Manager, and third-party tools
When building automated remediation workflows triggered by security findings
When executive stakeholders require a security compliance dashboard across the organization
Do not use for real-time threat detection (use GuardDuty), for vulnerability scanning (use Inspector), or for data classification (use Macie). Security Hub aggregates findings from these services but does not replace them.
Common Misconfigurations & Verification
AWS Config not recording in every account/region: Security Hub controls evaluate Config items. If Config is off, controls show No data (not PASS/FAIL) and the compliance score is silently incomplete. Confirm a running recorder per region: aws configservice describe-configuration-recorder-status --query 'ConfigurationRecordersStatus[?recording!=true]'.
auto-enable disabled on the org config: existing accounts may be enrolled but new accounts are not. Verify aws securityhub describe-organization-configuration returns AutoEnable: true (and AutoEnableStandards: DEFAULT).
No cross-region finding aggregator: without one, findings stay siloed per region and the admin view is partial. Check aws securityhub list-finding-aggregators returns an ARN.
Control finding generator mismatch: mixing STANDARD_CONTROL and SECURITY_CONTROL (consolidated) generators across accounts double-counts or hides controls. Keep it consistent org-wide.
Auto-remediation that never closes findings: the Lambda must call batch_update_findings with Workflow.Status or findings reappear as NEW forever.
AWS service that aggregates security findings from AWS services and third-party tools, evaluates compliance against standards, and provides a unified security dashboard
Security Standard
A predefined set of security controls (CIS, PCI DSS, NIST 800-53) that Security Hub evaluates against your AWS configuration
Security Control
An individual check within a standard that evaluates a specific AWS resource configuration, such as whether S3 buckets block public access
Finding
A security issue detected by Security Hub or an integrated service, formatted in AWS Security Finding Format (ASFF)
Insight
A custom or managed grouping of findings by a specific attribute, providing aggregated views for security analysis
ASFF
AWS Security Finding Format, the standardized JSON schema used by all Security Hub integrations for consistent finding representation
Tools & Systems
AWS Security Hub: Central aggregation and compliance evaluation platform for security findings across AWS accounts
AWS Config: Configuration recording service required by Security Hub for evaluating resource compliance
Amazon EventBridge: Event bus for routing Security Hub findings to Lambda, SNS, or external remediation systems
AWS Lambda: Serverless compute for automated remediation functions triggered by Security Hub findings
Prowler: Open-source tool that can send findings to Security Hub via ASFF integration
Common Scenarios
Scenario: Rolling Out Security Hub Across a 50-Account Organization
Context: A security team needs to enable Security Hub with CIS and FSBP standards across all accounts in an AWS Organization, with centralized finding aggregation and automated alerting.
Approach:
Enable Security Hub in the management account and designate a security account as delegated admin
Configure auto-enable for all existing and new member accounts via update-organization-configuration
Create a cross-region finding aggregator to consolidate findings from all regions into the admin account
Enable CIS AWS Foundations 1.4 and AWS FSBP standards across all accounts
Create EventBridge rules to route CRITICAL findings to PagerDuty and all findings to Splunk
Build custom insights for the top organizational risks: public resources, missing encryption, unused credentials
Schedule weekly compliance reports to stakeholders using Lambda and SES
Pitfalls: Security Hub requires AWS Config to be enabled in every account and region. Failing to enable Config will result in controls showing as "No data" rather than PASSED or FAILED. Member accounts with Config disabled will silently produce incomplete compliance scores.
Output Format
AWS Security Hub Compliance Report
=====================================
Organization: acme-corp (50 accounts)
Region: us-east-1 (aggregated from all regions)
Report Date: 2026-02-23
Standards Enabled: CIS 1.4, FSBP v1.0, PCI DSS 3.2.1
COMPLIANCE SCORES:
CIS AWS Foundations 1.4: 78% (142/182 controls passing)
AWS FSBP v1.0.0: 85% (198/233 controls passing)
PCI DSS 3.2.1: 72% (89/124 controls passing)
CRITICAL FINDINGS: 23
HIGH FINDINGS: 87
MEDIUM FINDINGS: 245
LOW FINDINGS: 412
TOP FAILING CONTROLS:
[IAM.6] MFA not enabled for root account 12 accounts
[S3.2] S3 Block Public Access not enabled 8 accounts
[EC2.19] Security groups allow unrestricted access 15 accounts
[RDS.3] RDS encryption at rest not enabled 6 accounts
AUTO-REMEDIATION ACTIONS (Last 30 Days):
S3 Block Public Access enabled: 14
Security Group rules restricted: 8
CloudTrail logging re-enabled: 3
Total auto-remediated findings: 25
