[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M733YAT31SWBMA6JZM16A3M4":3,"skill-same:01M733YAT31SWBMA6JZM16A3M4":89},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":16,"sourceHtmlUrl":17,"categories":18,"keywords":19,"publishedAt":20,"linkOnly":21,"markdownContent":22,"markdownBody":23,"frontMatter":24,"refName":49,"commitSha":50,"skillDirectory":51,"forksCount":52,"repositoryHtmlUrl":53,"repositoryHomepageUrl":54,"ownerHtmlUrl":55,"ownerBlogUrl":56,"ownerDescription":57,"updatedAt":58,"install":59,"resources":72},"01M733YAT31SWBMA6JZM16A3M4","implementing-aws-security-hub-compliance",null,"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.","Horonomos-laps\u002FYana-AI","Horonomos-laps","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F355299122?v=4","01M76B3QPXE88ET2SQPDPVATZT"," Horonomos-laps","01M72ZQRJPCYPSSWT4D00VJR2A",13,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-aws-security-hub-compliance\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-aws-security-hub-compliance\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: implementing-aws-security-hub-compliance\ndescription: 'Implementing AWS Security Hub to aggregate security findings across\n  AWS accounts, enable compliance standards like CIS AWS Foundations and PCI DSS,\n  configure automated remediation with EventBridge and Lambda, and create custom security\n  insights for organizational risk management.\n\n  '\ndomain: cybersecurity\nsubdomain: cloud-security\ntags:\n- cloud-security\n- aws\n- security-hub\n- compliance\n- cspm\n- cis-benchmark\nversion: '1.0'\nauthor: mahipal\nlicense: Apache-2.0\nnist_csf:\n- PR.IR-01\n- ID.AM-08\n- GV.SC-06\n- DE.CM-01\nmitre_attack:\n- T1078.004\n- T1530\n- T1537\n- T1580\nsource: https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\nsource_commit: 04450304b12645cb2b974ab96d28c0664758a88d\nnote: \"Vendored verbatim from an external Apache-2.0 security-skill library, pinned by commit. Exceeds the internal 300-line skill guideline (agent-code-constraints.md) -- kept as-is because this is vendored reference material (forensics\u002Fthreat-intel procedure), not Yana AI-authored content, and trimming would damage technical accuracy.\"\n---\n\n# Implementing AWS Security Hub Compliance\n\n## When to Use\n\n- When establishing centralized security posture management across multiple AWS accounts\n- When compliance requirements demand continuous monitoring against CIS, PCI DSS, or NIST 800-53 standards\n- When aggregating findings from GuardDuty, Inspector, Macie, Firewall Manager, and third-party tools\n- When building automated remediation workflows triggered by security findings\n- When executive stakeholders require a security compliance dashboard across the organization\n\n**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.\n\n## Prerequisites\n\n- AWS Organizations with delegated administrator for Security Hub\n- IAM permissions for `securityhub:*`, `config:*`, `events:*`, and `lambda:*`\n- AWS Config enabled in all target accounts and regions (required by Security Hub)\n- CloudFormation StackSets or Terraform for multi-account deployment\n- SNS topics configured for alert routing to security team\n\n## Workflow\n\n### Step 1: Enable Security Hub with Compliance Standards\n\nEnable Security Hub in the management account and select compliance standards to evaluate.\n\n```bash\n# Enable Security Hub in the current account\u002Fregion\naws securityhub enable-security-hub \\\n  --enable-default-standards \\\n  --control-finding-generator SECURITY_CONTROL\n\n# Enable specific compliance standards\naws securityhub batch-enable-standards --standards-subscription-requests \\\n  '[\n    {\"StandardsArn\": \"arn:aws:securityhub:us-east-1::standards\u002Faws-foundational-security-best-practices\u002Fv\u002F1.0.0\"},\n    {\"StandardsArn\": \"arn:aws:securityhub:us-east-1::standards\u002Fcis-aws-foundations-benchmark\u002Fv\u002F1.4.0\"},\n    {\"StandardsArn\": \"arn:aws:securityhub:us-east-1::standards\u002Fpci-dss\u002Fv\u002F3.2.1\"},\n    {\"StandardsArn\": \"arn:aws:securityhub:us-east-1::standards\u002Fnist-800-53\u002Fv\u002F5.0.0\"}\n  ]'\n\n# Verify enabled standards\naws securityhub get-enabled-standards \\\n  --query 'StandardsSubscriptions[*].[StandardsArn,StandardsStatus]' --output table\n```\n\n### Step 2: Configure Multi-Account Aggregation\n\nSet up a delegated administrator and aggregate findings from all organization accounts.\n\n```bash\n# Designate a delegated admin (run from management account)\naws securityhub enable-organization-admin-account \\\n  --admin-account-id 111122223333\n\n# From the delegated admin account, enable auto-enrollment\naws securityhub update-organization-configuration \\\n  --auto-enable \\\n  --auto-enable-standards DEFAULT\n\n# Create a finding aggregator for cross-region aggregation\naws securityhub create-finding-aggregator \\\n  --region-linking-mode ALL_REGIONS\n\n# List member accounts\naws securityhub list-members \\\n  --query 'Members[*].[AccountId,MemberStatus]' --output table\n```\n\n### Step 3: Review Compliance Scores and Failed Controls\n\nQuery Security Hub for compliance posture across enabled standards and identify failing controls.\n\n```bash\n# Get overall compliance score for CIS benchmark\naws securityhub get-standards-control-associations \\\n  --security-control-id \"IAM.1\" \\\n  --query 'StandardsControlAssociationSummaries[*].[StandardsArn,AssociationStatus]' \\\n  --output table\n\n# List all failed controls\naws securityhub get-findings \\\n  --filters '{\n    \"ComplianceStatus\": [{\"Value\": \"FAILED\", \"Comparison\": \"EQUALS\"}],\n    \"RecordState\": [{\"Value\": \"ACTIVE\", \"Comparison\": \"EQUALS\"}],\n    \"WorkflowStatus\": [{\"Value\": \"NEW\", \"Comparison\": \"EQUALS\"}]\n  }' \\\n  --sort-criteria '{\"Field\": \"SeverityNormalized\", \"SortOrder\": \"desc\"}' \\\n  --max-items 50 \\\n  --query 'Findings[*].[Title,Severity.Label,Compliance.Status,Resources[0].Id]' \\\n  --output table\n\n# Get finding counts by severity\naws securityhub get-insight-results \\\n  --insight-arn \"arn:aws:securityhub:us-east-1:111122223333:insight\u002F111122223333\u002Fdefault\u002F2\"\n```\n\n### Step 4: Create Custom Security Insights\n\nBuild custom insights to track organization-specific security priorities.\n\n```bash\n# Create insight for publicly accessible resources\naws securityhub create-insight \\\n  --name \"Publicly Accessible Resources\" \\\n  --filters '{\n    \"ResourceType\": [\n      {\"Value\": \"AwsS3Bucket\", \"Comparison\": \"EQUALS\"},\n      {\"Value\": \"AwsEc2SecurityGroup\", \"Comparison\": \"EQUALS\"},\n      {\"Value\": \"AwsRdsDbInstance\", \"Comparison\": \"EQUALS\"}\n    ],\n    \"ComplianceStatus\": [{\"Value\": \"FAILED\", \"Comparison\": \"EQUALS\"}],\n    \"SeverityLabel\": [{\"Value\": \"CRITICAL\", \"Comparison\": \"EQUALS\"}, {\"Value\": \"HIGH\", \"Comparison\": \"EQUALS\"}]\n  }' \\\n  --group-by-attribute \"ResourceType\"\n\n# Create insight for unencrypted resources\naws securityhub create-insight \\\n  --name \"Unencrypted Resources Across Accounts\" \\\n  --filters '{\n    \"Title\": [{\"Value\": \"encryption\", \"Comparison\": \"CONTAINS\"}],\n    \"ComplianceStatus\": [{\"Value\": \"FAILED\", \"Comparison\": \"EQUALS\"}]\n  }' \\\n  --group-by-attribute \"AwsAccountId\"\n```\n\n### Step 5: Configure Automated Remediation with EventBridge\n\nSet up EventBridge rules to trigger Lambda-based auto-remediation for specific finding types.\n\n```bash\n# Create EventBridge rule for Security Hub findings\naws events put-rule \\\n  --name \"security-hub-critical-findings\" \\\n  --event-pattern '{\n    \"source\": [\"aws.securityhub\"],\n    \"detail-type\": [\"Security Hub Findings - Imported\"],\n    \"detail\": {\n      \"findings\": {\n        \"Severity\": {\"Label\": [\"CRITICAL\"]},\n        \"Compliance\": {\"Status\": [\"FAILED\"]},\n        \"Workflow\": {\"Status\": [\"NEW\"]}\n      }\n    }\n  }'\n\n# Example Lambda auto-remediation for S3 public access (Python)\ncat > \u002Ftmp\u002Fremediate_s3.py \u003C\u003C 'PYEOF'\nimport boto3\nimport json\n\ndef lambda_handler(event, context):\n    s3 = boto3.client('s3')\n    securityhub = boto3.client('securityhub')\n\n    for finding in event['detail']['findings']:\n        if 'S3' in finding.get('Title', '') and 'public' in finding.get('Title', '').lower():\n            bucket_arn = finding['Resources'][0]['Id']\n            bucket_name = bucket_arn.split(':::')[-1]\n\n            s3.put_public_access_block(\n                Bucket=bucket_name,\n                PublicAccessBlockConfiguration={\n                    'BlockPublicAcls': True,\n                    'IgnorePublicAcls': True,\n                    'BlockPublicPolicy': True,\n                    'RestrictPublicBuckets': True\n                }\n            )\n\n            securityhub.batch_update_findings(\n                FindingIdentifiers=[{\n                    'Id': finding['Id'],\n                    'ProductArn': finding['ProductArn']\n                }],\n                Workflow={'Status': 'RESOLVED'},\n                Note={\n                    'Text': 'Auto-remediated: Block Public Access enabled',\n                    'UpdatedBy': 'security-hub-auto-remediation'\n                }\n            )\n    return {'statusCode': 200}\nPYEOF\n```\n\n### Step 6: Export Findings and Generate Compliance Reports\n\nExport Security Hub findings for reporting and integration with external SIEM or GRC platforms.\n\n```bash\n# Export all findings to S3 via a custom script\naws securityhub get-findings \\\n  --filters '{\n    \"RecordState\": [{\"Value\": \"ACTIVE\", \"Comparison\": \"EQUALS\"}]\n  }' \\\n  --max-items 1000 \\\n  --output json > security-hub-findings-export.json\n\n# Send critical findings to SNS\naws sns publish \\\n  --topic-arn arn:aws:sns:us-east-1:111122223333:security-alerts \\\n  --subject \"Security Hub Daily Summary\" \\\n  --message file:\u002F\u002Fdaily-summary.json\n\n# Integrate with third-party SIEM via EventBridge\naws events put-targets \\\n  --rule security-hub-critical-findings \\\n  --targets '[{\n    \"Id\": \"splunk-hec\",\n    \"Arn\": \"arn:aws:events:us-east-1:111122223333:api-destination\u002Fsplunk-hec\",\n    \"HttpParameters\": {\n      \"HeaderParameters\": {\"Authorization\": \"Splunk HEC_TOKEN\"}\n    }\n  }]'\n```\n\n## Key Concepts\n\n| Term | Definition |\n|------|------------|\n| Security Hub | AWS service that aggregates security findings from AWS services and third-party tools, evaluates compliance against standards, and provides a unified security dashboard |\n| Security Standard | A predefined set of security controls (CIS, PCI DSS, NIST 800-53) that Security Hub evaluates against your AWS configuration |\n| Security Control | An individual check within a standard that evaluates a specific AWS resource configuration, such as whether S3 buckets block public access |\n| Finding | A security issue detected by Security Hub or an integrated service, formatted in AWS Security Finding Format (ASFF) |\n| Insight | A custom or managed grouping of findings by a specific attribute, providing aggregated views for security analysis |\n| ASFF | AWS Security Finding Format, the standardized JSON schema used by all Security Hub integrations for consistent finding representation |\n\n## Tools & Systems\n\n- **AWS Security Hub**: Central aggregation and compliance evaluation platform for security findings across AWS accounts\n- **AWS Config**: Configuration recording service required by Security Hub for evaluating resource compliance\n- **Amazon EventBridge**: Event bus for routing Security Hub findings to Lambda, SNS, or external remediation systems\n- **AWS Lambda**: Serverless compute for automated remediation functions triggered by Security Hub findings\n- **Prowler**: Open-source tool that can send findings to Security Hub via ASFF integration\n\n## Common Scenarios\n\n### Scenario: Rolling Out Security Hub Across a 50-Account Organization\n\n**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.\n\n**Approach**:\n1. Enable Security Hub in the management account and designate a security account as delegated admin\n2. Configure auto-enable for all existing and new member accounts via `update-organization-configuration`\n3. Create a cross-region finding aggregator to consolidate findings from all regions into the admin account\n4. Enable CIS AWS Foundations 1.4 and AWS FSBP standards across all accounts\n5. Create EventBridge rules to route CRITICAL findings to PagerDuty and all findings to Splunk\n6. Build custom insights for the top organizational risks: public resources, missing encryption, unused credentials\n7. Schedule weekly compliance reports to stakeholders using Lambda and SES\n\n**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.\n\n## Output Format\n\n```\nAWS Security Hub Compliance Report\n=====================================\nOrganization: acme-corp (50 accounts)\nRegion: us-east-1 (aggregated from all regions)\nReport Date: 2026-02-23\nStandards Enabled: CIS 1.4, FSBP v1.0, PCI DSS 3.2.1\n\nCOMPLIANCE SCORES:\n  CIS AWS Foundations 1.4:     78% (142\u002F182 controls passing)\n  AWS FSBP v1.0.0:             85% (198\u002F233 controls passing)\n  PCI DSS 3.2.1:               72% (89\u002F124 controls passing)\n\nCRITICAL FINDINGS: 23\nHIGH FINDINGS: 87\nMEDIUM FINDINGS: 245\nLOW FINDINGS: 412\n\nTOP FAILING CONTROLS:\n  [IAM.6]  MFA not enabled for root account           12 accounts\n  [S3.2]   S3 Block Public Access not enabled          8 accounts\n  [EC2.19] Security groups allow unrestricted access   15 accounts\n  [RDS.3]  RDS encryption at rest not enabled          6 accounts\n\nAUTO-REMEDIATION ACTIONS (Last 30 Days):\n  S3 Block Public Access enabled:    14\n  Security Group rules restricted:    8\n  CloudTrail logging re-enabled:      3\n  Total auto-remediated findings:    25\n```\n","# Implementing AWS Security Hub Compliance\n\n## When to Use\n\n- When establishing centralized security posture management across multiple AWS accounts\n- When compliance requirements demand continuous monitoring against CIS, PCI DSS, or NIST 800-53 standards\n- When aggregating findings from GuardDuty, Inspector, Macie, Firewall Manager, and third-party tools\n- When building automated remediation workflows triggered by security findings\n- When executive stakeholders require a security compliance dashboard across the organization\n\n**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.\n\n## Prerequisites\n\n- AWS Organizations with delegated administrator for Security Hub\n- IAM permissions for `securityhub:*`, `config:*`, `events:*`, and `lambda:*`\n- AWS Config enabled in all target accounts and regions (required by Security Hub)\n- CloudFormation StackSets or Terraform for multi-account deployment\n- SNS topics configured for alert routing to security team\n\n## Workflow\n\n### Step 1: Enable Security Hub with Compliance Standards\n\nEnable Security Hub in the management account and select compliance standards to evaluate.\n\n```bash\n# Enable Security Hub in the current account\u002Fregion\naws securityhub enable-security-hub \\\n  --enable-default-standards \\\n  --control-finding-generator SECURITY_CONTROL\n\n# Enable specific compliance standards\naws securityhub batch-enable-standards --standards-subscription-requests \\\n  '[\n    {\"StandardsArn\": \"arn:aws:securityhub:us-east-1::standards\u002Faws-foundational-security-best-practices\u002Fv\u002F1.0.0\"},\n    {\"StandardsArn\": \"arn:aws:securityhub:us-east-1::standards\u002Fcis-aws-foundations-benchmark\u002Fv\u002F1.4.0\"},\n    {\"StandardsArn\": \"arn:aws:securityhub:us-east-1::standards\u002Fpci-dss\u002Fv\u002F3.2.1\"},\n    {\"StandardsArn\": \"arn:aws:securityhub:us-east-1::standards\u002Fnist-800-53\u002Fv\u002F5.0.0\"}\n  ]'\n\n# Verify enabled standards\naws securityhub get-enabled-standards \\\n  --query 'StandardsSubscriptions[*].[StandardsArn,StandardsStatus]' --output table\n```\n\n### Step 2: Configure Multi-Account Aggregation\n\nSet up a delegated administrator and aggregate findings from all organization accounts.\n\n```bash\n# Designate a delegated admin (run from management account)\naws securityhub enable-organization-admin-account \\\n  --admin-account-id 111122223333\n\n# From the delegated admin account, enable auto-enrollment\naws securityhub update-organization-configuration \\\n  --auto-enable \\\n  --auto-enable-standards DEFAULT\n\n# Create a finding aggregator for cross-region aggregation\naws securityhub create-finding-aggregator \\\n  --region-linking-mode ALL_REGIONS\n\n# List member accounts\naws securityhub list-members \\\n  --query 'Members[*].[AccountId,MemberStatus]' --output table\n```\n\n### Step 3: Review Compliance Scores and Failed Controls\n\nQuery Security Hub for compliance posture across enabled standards and identify failing controls.\n\n```bash\n# Get overall compliance score for CIS benchmark\naws securityhub get-standards-control-associations \\\n  --security-control-id \"IAM.1\" \\\n  --query 'StandardsControlAssociationSummaries[*].[StandardsArn,AssociationStatus]' \\\n  --output table\n\n# List all failed controls\naws securityhub get-findings \\\n  --filters '{\n    \"ComplianceStatus\": [{\"Value\": \"FAILED\", \"Comparison\": \"EQUALS\"}],\n    \"RecordState\": [{\"Value\": \"ACTIVE\", \"Comparison\": \"EQUALS\"}],\n    \"WorkflowStatus\": [{\"Value\": \"NEW\", \"Comparison\": \"EQUALS\"}]\n  }' \\\n  --sort-criteria '{\"Field\": \"SeverityNormalized\", \"SortOrder\": \"desc\"}' \\\n  --max-items 50 \\\n  --query 'Findings[*].[Title,Severity.Label,Compliance.Status,Resources[0].Id]' \\\n  --output table\n\n# Get finding counts by severity\naws securityhub get-insight-results \\\n  --insight-arn \"arn:aws:securityhub:us-east-1:111122223333:insight\u002F111122223333\u002Fdefault\u002F2\"\n```\n\n### Step 4: Create Custom Security Insights\n\nBuild custom insights to track organization-specific security priorities.\n\n```bash\n# Create insight for publicly accessible resources\naws securityhub create-insight \\\n  --name \"Publicly Accessible Resources\" \\\n  --filters '{\n    \"ResourceType\": [\n      {\"Value\": \"AwsS3Bucket\", \"Comparison\": \"EQUALS\"},\n      {\"Value\": \"AwsEc2SecurityGroup\", \"Comparison\": \"EQUALS\"},\n      {\"Value\": \"AwsRdsDbInstance\", \"Comparison\": \"EQUALS\"}\n    ],\n    \"ComplianceStatus\": [{\"Value\": \"FAILED\", \"Comparison\": \"EQUALS\"}],\n    \"SeverityLabel\": [{\"Value\": \"CRITICAL\", \"Comparison\": \"EQUALS\"}, {\"Value\": \"HIGH\", \"Comparison\": \"EQUALS\"}]\n  }' \\\n  --group-by-attribute \"ResourceType\"\n\n# Create insight for unencrypted resources\naws securityhub create-insight \\\n  --name \"Unencrypted Resources Across Accounts\" \\\n  --filters '{\n    \"Title\": [{\"Value\": \"encryption\", \"Comparison\": \"CONTAINS\"}],\n    \"ComplianceStatus\": [{\"Value\": \"FAILED\", \"Comparison\": \"EQUALS\"}]\n  }' \\\n  --group-by-attribute \"AwsAccountId\"\n```\n\n### Step 5: Configure Automated Remediation with EventBridge\n\nSet up EventBridge rules to trigger Lambda-based auto-remediation for specific finding types.\n\n```bash\n# Create EventBridge rule for Security Hub findings\naws events put-rule \\\n  --name \"security-hub-critical-findings\" \\\n  --event-pattern '{\n    \"source\": [\"aws.securityhub\"],\n    \"detail-type\": [\"Security Hub Findings - Imported\"],\n    \"detail\": {\n      \"findings\": {\n        \"Severity\": {\"Label\": [\"CRITICAL\"]},\n        \"Compliance\": {\"Status\": [\"FAILED\"]},\n        \"Workflow\": {\"Status\": [\"NEW\"]}\n      }\n    }\n  }'\n\n# Example Lambda auto-remediation for S3 public access (Python)\ncat > \u002Ftmp\u002Fremediate_s3.py \u003C\u003C 'PYEOF'\nimport boto3\nimport json\n\ndef lambda_handler(event, context):\n    s3 = boto3.client('s3')\n    securityhub = boto3.client('securityhub')\n\n    for finding in event['detail']['findings']:\n        if 'S3' in finding.get('Title', '') and 'public' in finding.get('Title', '').lower():\n            bucket_arn = finding['Resources'][0]['Id']\n            bucket_name = bucket_arn.split(':::')[-1]\n\n            s3.put_public_access_block(\n                Bucket=bucket_name,\n                PublicAccessBlockConfiguration={\n                    'BlockPublicAcls': True,\n                    'IgnorePublicAcls': True,\n                    'BlockPublicPolicy': True,\n                    'RestrictPublicBuckets': True\n                }\n            )\n\n            securityhub.batch_update_findings(\n                FindingIdentifiers=[{\n                    'Id': finding['Id'],\n                    'ProductArn': finding['ProductArn']\n                }],\n                Workflow={'Status': 'RESOLVED'},\n                Note={\n                    'Text': 'Auto-remediated: Block Public Access enabled',\n                    'UpdatedBy': 'security-hub-auto-remediation'\n                }\n            )\n    return {'statusCode': 200}\nPYEOF\n```\n\n### Step 6: Export Findings and Generate Compliance Reports\n\nExport Security Hub findings for reporting and integration with external SIEM or GRC platforms.\n\n```bash\n# Export all findings to S3 via a custom script\naws securityhub get-findings \\\n  --filters '{\n    \"RecordState\": [{\"Value\": \"ACTIVE\", \"Comparison\": \"EQUALS\"}]\n  }' \\\n  --max-items 1000 \\\n  --output json > security-hub-findings-export.json\n\n# Send critical findings to SNS\naws sns publish \\\n  --topic-arn arn:aws:sns:us-east-1:111122223333:security-alerts \\\n  --subject \"Security Hub Daily Summary\" \\\n  --message file:\u002F\u002Fdaily-summary.json\n\n# Integrate with third-party SIEM via EventBridge\naws events put-targets \\\n  --rule security-hub-critical-findings \\\n  --targets '[{\n    \"Id\": \"splunk-hec\",\n    \"Arn\": \"arn:aws:events:us-east-1:111122223333:api-destination\u002Fsplunk-hec\",\n    \"HttpParameters\": {\n      \"HeaderParameters\": {\"Authorization\": \"Splunk HEC_TOKEN\"}\n    }\n  }]'\n```\n\n## Key Concepts\n\n| Term | Definition |\n|------|------------|\n| Security Hub | AWS service that aggregates security findings from AWS services and third-party tools, evaluates compliance against standards, and provides a unified security dashboard |\n| Security Standard | A predefined set of security controls (CIS, PCI DSS, NIST 800-53) that Security Hub evaluates against your AWS configuration |\n| Security Control | An individual check within a standard that evaluates a specific AWS resource configuration, such as whether S3 buckets block public access |\n| Finding | A security issue detected by Security Hub or an integrated service, formatted in AWS Security Finding Format (ASFF) |\n| Insight | A custom or managed grouping of findings by a specific attribute, providing aggregated views for security analysis |\n| ASFF | AWS Security Finding Format, the standardized JSON schema used by all Security Hub integrations for consistent finding representation |\n\n## Tools & Systems\n\n- **AWS Security Hub**: Central aggregation and compliance evaluation platform for security findings across AWS accounts\n- **AWS Config**: Configuration recording service required by Security Hub for evaluating resource compliance\n- **Amazon EventBridge**: Event bus for routing Security Hub findings to Lambda, SNS, or external remediation systems\n- **AWS Lambda**: Serverless compute for automated remediation functions triggered by Security Hub findings\n- **Prowler**: Open-source tool that can send findings to Security Hub via ASFF integration\n\n## Common Scenarios\n\n### Scenario: Rolling Out Security Hub Across a 50-Account Organization\n\n**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.\n\n**Approach**:\n1. Enable Security Hub in the management account and designate a security account as delegated admin\n2. Configure auto-enable for all existing and new member accounts via `update-organization-configuration`\n3. Create a cross-region finding aggregator to consolidate findings from all regions into the admin account\n4. Enable CIS AWS Foundations 1.4 and AWS FSBP standards across all accounts\n5. Create EventBridge rules to route CRITICAL findings to PagerDuty and all findings to Splunk\n6. Build custom insights for the top organizational risks: public resources, missing encryption, unused credentials\n7. Schedule weekly compliance reports to stakeholders using Lambda and SES\n\n**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.\n\n## Output Format\n\n```\nAWS Security Hub Compliance Report\n=====================================\nOrganization: acme-corp (50 accounts)\nRegion: us-east-1 (aggregated from all regions)\nReport Date: 2026-02-23\nStandards Enabled: CIS 1.4, FSBP v1.0, PCI DSS 3.2.1\n\nCOMPLIANCE SCORES:\n  CIS AWS Foundations 1.4:     78% (142\u002F182 controls passing)\n  AWS FSBP v1.0.0:             85% (198\u002F233 controls passing)\n  PCI DSS 3.2.1:               72% (89\u002F124 controls passing)\n\nCRITICAL FINDINGS: 23\nHIGH FINDINGS: 87\nMEDIUM FINDINGS: 245\nLOW FINDINGS: 412\n\nTOP FAILING CONTROLS:\n  [IAM.6]  MFA not enabled for root account           12 accounts\n  [S3.2]   S3 Block Public Access not enabled          8 accounts\n  [EC2.19] Security groups allow unrestricted access   15 accounts\n  [RDS.3]  RDS encryption at rest not enabled          6 accounts\n\nAUTO-REMEDIATION ACTIONS (Last 30 Days):\n  S3 Block Public Access enabled:    14\n  Security Group rules restricted:    8\n  CloudTrail logging re-enabled:      3\n  Total auto-remediated findings:    25\n```\n",{"name":5,"note":25,"tags":26,"author":33,"domain":34,"source":35,"license":15,"version":36,"nist_csf":37,"subdomain":27,"description":42,"mitre_attack":43,"source_commit":48},"Vendored verbatim from an external Apache-2.0 security-skill library, pinned by commit. Exceeds the internal 300-line skill guideline (agent-code-constraints.md) -- kept as-is because this is vendored reference material (forensics\u002Fthreat-intel procedure), not Yana AI-authored content, and trimming would damage technical accuracy.",[27,28,29,30,31,32],"cloud-security","aws","security-hub","compliance","cspm","cis-benchmark","mahipal","cybersecurity","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills","1.0",[38,39,40,41],"PR.IR-01","ID.AM-08","GV.SC-06","DE.CM-01","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.\n",[44,45,46,47],"T1078.004","T1530","T1537","T1580","04450304b12645cb2b974ab96d28c0664758a88d","main","481dcd7dd2e288b9d627a2bd017db70e64e6c6fa",".claude\u002Fskills\u002Fimplementing-aws-security-hub-compliance",2,"https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI","https:\u002F\u002Fyana.vutam.link\u002F","https:\u002F\u002Fgithub.com\u002FHoronomos-laps","https:\u002F\u002Fyana.vutam.link","An open-source governed runtime & execution environment for multi-agent AI systems.","2026-11-14 13:24:09",{"source":8,"skillName":5,"commands":60,"prompt":70,"zipAvailable":71},[61,64,67],{"tool":62,"command":63},"npx","npx skills add Horonomos-laps\u002FYana-AI --skill implementing-aws-security-hub-compliance",{"tool":65,"command":66},"bunx","bunx skills add Horonomos-laps\u002FYana-AI --skill implementing-aws-security-hub-compliance",{"tool":68,"command":69},"pnpm","pnpm dlx skills add Horonomos-laps\u002FYana-AI --skill implementing-aws-security-hub-compliance","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-aws-security-hub-compliance\u002FSKILL.md",true,[73,77,83],{"path":74,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":76,"sourceHtmlUrl":16},"LICENSE","许可证",11255,{"path":78,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":81,"sourceHtmlUrl":82},"references\u002Fapi-reference.md","REFERENCE","参考文档",2366,"https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-aws-security-hub-compliance\u002Freferences\u002Fapi-reference.md",{"path":84,"resourceType":85,"resourceTypeDesc":86,"sizeBytes":87,"sourceHtmlUrl":88},"scripts\u002Fagent.py","SCRIPT","脚本",7181,"https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-aws-security-hub-compliance\u002Fscripts\u002Fagent.py",[90,98,105,113,121,129],{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":94,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":20},"01M735GKET5YVYKAY62W2P5YXB","openai--sentry--sentry","Use when the user asks to inspect Sentry issues or events, summarize recent production errors, or pull basic Sentry health data via the Sentry API; perform read-only queries with the bundled script and require `SENTRY_AUTH_TOKEN`.","MIT","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fopenai--sentry--sentry\u002FSKILL.md",[],[],{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":20},"01M73DCAP83T17HY7SMGK7MGFE","ito-basket-compare","Compare Itô prediction-market baskets against a user's knowledge base, portfolio notes, financial context, watchlist, or research thesis. Use for read-only basket comparison and gap analysis without investment advice or live trading.","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fito-basket-compare\u002FSKILL.md",[],[],{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":109,"sourceHtmlUrl":110,"categories":111,"keywords":112,"publishedAt":20},"01M734CYEMZFDR3KH6SW0JP8TD","implementing-network-traffic-baselining","Build network traffic baselines from NetFlow\u002FIPFIX data using Python pandas for statistical analysis, z-score anomaly detection, and hourly\u002Fdaily traffic pattern profiling","https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-network-traffic-baselining\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-network-traffic-baselining\u002FSKILL.md",[],[],{"skillNo":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":117,"sourceHtmlUrl":118,"categories":119,"keywords":120,"publishedAt":20},"01M73ASZ6NJRJM44Z2P84NGQ3Q","detecting-evasion-techniques-in-endpoint-logs","Detects defense evasion techniques used by adversaries in endpoint logs including log tampering, timestomping, process injection, and security tool disabling. Use when investigating suspicious endpoint behavior, building detection rules for evasion tactics, or conducting threat hunting for stealthy adversary activity. Activates for requests involving evasion detection, defense evasion analysis, log tampering detection, or MITRE ATT&CK TA0005.","https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fdetecting-evasion-techniques-in-endpoint-logs\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fdetecting-evasion-techniques-in-endpoint-logs\u002FSKILL.md",[],[],{"skillNo":122,"name":123,"nameZh":6,"description":124,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":125,"sourceHtmlUrl":126,"categories":127,"keywords":128,"publishedAt":20},"01M734AFNXD06Z78QRK0VKGT7Q","implementing-microsegmentation-with-guardicore","Implementing microsegmentation using Akamai Guardicore Segmentation to map application dependencies, create granular network policies, visualize east-west traffic flows, and enforce least-privilege communication between workloads across data centers and cloud.","https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-microsegmentation-with-guardicore\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-microsegmentation-with-guardicore\u002FSKILL.md",[],[],{"skillNo":130,"name":131,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":132,"categories":133,"keywords":134,"publishedAt":20},"01M736TK27QMCXK0DVCH25SJN5","ramdisk-tmpfs-patterns","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Framdisk-tmpfs-patterns\u002FSKILL.md",[],[]]