[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7ACCDTCEEVKSPJVQRYH5AYP":3,"skill-same:01M7ACCDTCEEVKSPJVQRYH5AYP":143},{"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":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":43,"commitSha":44,"skillDirectory":45,"forksCount":46,"repositoryHtmlUrl":47,"repositoryHomepageUrl":6,"ownerHtmlUrl":48,"ownerBlogUrl":6,"ownerDescription":49,"updatedAt":50,"install":51,"resources":64},"01M7ACCDTCEEVKSPJVQRYH5AYP","securityhub-remediation-automator",null,"Designs automated remediation workflows for AWS Security Hub findings using EventBridge rules, SSM Automation runbooks, and Lambda remediation functions. Routes findings by severity (Critical\u002FHigh auto-remediate, Medium\u002FLow notify-only), maps finding types to runbooks or custom Lambda fixers, manages workflow status updates (NEW to NOTIFIED to RESOLVED via batch-update-findings), configures suppression rules with expiration, deploys Security Hub insights for tracking, enables control standards (FSBP, CIS, PCI DSS), integrates with Systems Manager Incident Manager for critical escalation, and orchestrates multi-account remediation via Organizations delegation. Emits AUTOMATION_DEPLOYED or REVIEW_REQUIRED with the specific gap.","jhkchan\u002Faws-agent-skills","jhkchan","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F1083902?v=4","01M7A2SVQYP9GQTPTDXP5JKYQ4","Jacky Chan","01M7A2SVS117YWCTZABB75HZR1",4,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fsecurityhub-remediation-automator\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: securityhub-remediation-automator\ndescription: Designs automated remediation workflows for AWS Security Hub findings using EventBridge rules, SSM Automation runbooks, and Lambda remediation functions. Routes findings by severity (Critical\u002FHigh auto-remediate, Medium\u002FLow notify-only), maps finding types to runbooks or custom Lambda fixers, manages workflow status updates (NEW to NOTIFIED to RESOLVED via batch-update-findings), configures suppression rules with expiration, deploys Security Hub insights for tracking, enables control standards (FSBP, CIS, PCI DSS), integrates with Systems Manager Incident Manager for critical escalation, and orchestrates multi-account remediation via Organizations delegation. Emits AUTOMATION_DEPLOYED or REVIEW_REQUIRED with the specific gap.\nlicense: Apache-2.0\ncompatibility: Agent runtime that reads SKILL.md (Claude Code, Cursor, Windsurf, Codex, Gemini). No AWS CLI required for offline workflow design. Live deployment uses aws securityhub enable-security-hub, update-standards, create-action-target, batch-update-findings, create-insight, aws events put-rule, put-targets, aws ssm start-automation-execution, aws lambda create-function, and aws cloudformation deploy — AWS CLI v2, SSO or key-based credentials.\nmetadata:\n  domain: aws-cloudops\n  complexity: high\n  requires_llm: 'true'\n  phase: '4'\n  supports_pipeline: 'true'\n  entry_point: 'false'\n  family: Security\n  task_type: automate\n  skill_class: capability\n  lifecycle_status: active\n  verdict_shape: AUTOMATION_DEPLOYED | REVIEW_REQUIRED\n  when_to_use: Designing auto-remediation for Security Hub findings, wiring EventBridge custom actions to findings, building severity-based remediation routing (Critical\u002FHigh auto-fix, Medium\u002FLow notify), enabling compliance standards (CIS, PCI DSS, FSBP) with automated enforcement, configuring suppression rules for accepted risks, deploying Security Hub insights for remediation tracking, or orchestrating multi-account remediation via Organizations delegated administrator.\n  activation_triggers: automate Security Hub remediation, Security Hub custom action, EventBridge finding to runbook, severity-based remediation SLA, batch-update-findings workflow status, Security Hub suppression rule, Security Hub insight for tracking, enable CIS PCI FSBP standard, Systems Manager Incident Manager integration, Security Hub multi-account delegation\n  invocation_schema: 'Input: either (a) a Security Hub finding type or standard control identifier plus target resource context, OR (b) a remediation requirement. Output: deterministic REMEDIATION block per finding type — FINDING_TYPE\u002FSEVERITY_ROUTE\u002FRUNBOOK\u002FTRIGGER\u002FSAFETY\u002FSUPPRESSION\u002FVERDICT — where VERDICT is AUTOMATION_DEPLOYED (deployment-ready template) or REVIEW_REQUIRED (specific gap cited).'\n  version: 0.1.0\n  author: Jacky Chan — AWS Community Builder\n  keywords: AWS Security Hub, Security Hub remediation, custom action, EventBridge finding, SSM Automation runbook, Lambda remediation, finding severity routing, batch-update-findings, workflow status, suppression rule, Security Hub insight, CIS benchmark, PCI DSS, AWS Foundational Security Best Practices, FSBP, Systems Manager Incident Manager, Organizations delegation, control enablement, compliance standard\n  tags: aws-security-hub, security-hub, eventbridge, ssm-automation, lambda-remediation, compliance, automate\n---\n\n# Security Hub Remediation Automator\n\n## Mindset\n\n**One-line takeaway:** every Security Hub remediation workflow is a five-stage\npipeline — **detect** (Security Hub control or partner finding) → **route**\n(EventBridge rule on severity + finding type) → **decide** (auto-remediate\nor notify-only) → **execute** (SSM Automation runbook or Lambda function) →\n**close** (update finding workflow status to RESOLVED, verify in insights).\nA gap in ANY stage produces either noise (findings pile up with no action)\nor silent failure (remediation fires but the finding never closes).\n\n- **Detection** without **routing** is a dashboard nobody watches: Critical\n  findings accumulate and operators lose visibility into what matters.\n- **Auto-remediation** on Critical\u002FHigh without a **safety gate** is risky:\n  the runbook fires on the first NEW finding, and if the fix is wrong, the\n  damage is done before any human reviews it.\n- **Finding closure** is the closing gate. A remediation that fixes the\n  underlying resource but does NOT update the finding workflow status leaves\n  the Security Hub dashboard perpetually dirty, destroying compliance\n  reporting accuracy.\n\n## Quick navigation\n\n| You want to... | Go to |\n|---|---|\n| Route findings by severity to auto-remediate vs notify | Step 3 (severity matrix) |\n| Wire a custom action to EventBridge for findings | Step 4 + worked CLI |\n| Map a finding type to an SSM runbook or Lambda fixer | Step 5 + Appendix A |\n| Build a Lambda remediation function for a custom finding | Step 6 |\n| Configure suppression rules for accepted risks | Step 7 |\n| Update finding workflow status (NEW to NOTIFIED to RESOLVED) | Step 8 |\n| Deploy Security Hub insights for remediation tracking | Step 9 |\n| Enable compliance standards (CIS, PCI DSS, FSBP) | Step 10 |\n| Integrate with Systems Manager Incident Manager | Step 11 |\n| Set up multi-account via Organizations delegation | Step 12 |\n| Avoid common remediation pitfalls | Anti-Patterns |\n| Recent features (custom actions, insights, control updates) | Recent AWS features |\n\n## Critical rules at a glance (do NOT bury these)\n\n1. **Security Hub custom actions are NOT automatic.** A custom action\n   creates a menu item in the console. It fires ONLY when an operator\n   manually selects findings and invokes the action. For automatic\n   remediation, you MUST use an EventBridge rule on the finding event\n   pattern — NOT the custom action ARN.\n\n2. **`batch-update-findings` is the ONLY API that updates workflow status.**\n   `update-findings` is deprecated and operates on a single finding.\n   `batch-update-findings` accepts up to 100 finding identifiers per call.\n   A remediation that does NOT call it leaves findings in NEW status\n   forever, corrupting compliance dashboards.\n\n3. **Security Hub finding events use `detail-type: \"Security Hub Findings -\n   Imported\"`.** NOT \"Custom Action\". The former fires on ingestion\n   (automation). The latter fires on human click (manual). Confusing the\n   two is the #1 reason EventBridge-driven remediation does not fire.\n\n4. **Control standards are region-specific.** Enabling CIS, PCI DSS, or\n   FSBP in us-east-1 does NOT enable them in eu-west-1. Multi-region\n   deployments require per-region `update-standards` calls.\n\n5. **Suppression rules archive findings but do NOT delete them.** A\n   suppressed finding has `WorkflowStatus: SUPPRESSED` and\n   `RecordState: ARCHIVED`. Always set a `Note` with the acceptance\n   rationale and an expiration date for re-evaluation.\n\n## STRICT output contract\n\nEvery remediation design MUST produce exactly one REMEDIATION block per\nfinding type, following this format:\n\n```text\nFINDING_ID: \u003CSecurity Hub finding Id — arn:aws:securityhub:...>\nFINDING_TYPE: \u003CSecurity Hub finding type>\nSTANDARD: \u003CCIS | PCI | FSBP | Custom | N\u002FA>\nVERDICT: AUTOMATION_DEPLOYED | REVIEW_REQUIRED\nCHECKLIST:\n  [✓|✗] Severity route: CRITICAL_AUTO | HIGH_AUTO | MEDIUM_NOTIFY | LOW_NOTIFY\n  [✓|✗] EventBridge rule: \u003Crule name + pattern summary>\n  [✓|✗] SSM runbook \u002F Lambda fixer: \u003Cdocument name | function ARN | NONE>\n  [✓|✗] batch-update-findings: NOTIFIED on dispatch → RESOLVED on success\n  [✓|✗] SQS DLQ: \u003CDLQ ARN on the EventBridge target>\n  [✓|✗] Suppression: \u003CNONE | rule + expiration YYYY-MM-DD>\n  [✓|✗] Insight: \u003Cinsight ARN | TBD>\n  [✓|✗] Safety gate: \u003Cdry-run 48h | pre-prod validated>\nGAP: \u003Cif REVIEW_REQUIRED, the specific missing piece>\nTEMPLATE: \u003CCLI snippet or IaC>\n```\n\n## NEVER section\n\n- **NEVER** wire an EventBridge rule on `aws.securityhub` without a\n  `Severity.Label` filter. Without it, the rule fires on EVERY finding\n  including LOW and INFORMATIONAL, overwhelming Lambda concurrency and\n  producing cost spikes.\n\n- **NEVER** use `update-findings` (deprecated). Use\n  `batch-update-findings` which accepts up to 100 findings per call and\n  is the forward-compatible API.\n\n- **NEVER** suppress a finding without an expiration date in the Note.\n  Permanent suppression violates every compliance framework (PCI DSS,\n  SOC 2, ISO 27001). Always include \"Suppressed until YYYY-MM-DD\" and\n  build the daily evaluator Lambda to re-open expired suppressions.\n\n- **NEVER** auto-remediate a finding without calling\n  `batch-update-findings` afterward. A remediation that fixes the\n  resource but leaves the finding in NEW status corrupts dashboards and\n  triggers duplicate remediation.\n\n- **NEVER** deploy a Lambda remediation function without an SQS DLQ on\n  the EventBridge target. Failed invocations are silently dropped\n  without a DLQ; the finding stays open and no one knows.\n\n- **NEVER** enable a compliance standard in production without staging\n  validation. Standards generate findings immediately upon enablement.\n  An unprepared account can see hundreds of findings in minutes.\n\n- **NEVER** assume Security Hub is enabled in all member accounts. A\n  member without Security Hub produces zero findings — not because it\n  is secure, but because no controls are running.\n\n- **NEVER** key remediation idempotency on `UpdatedAt`. Security Hub\n  re-evaluates controls periodically, changing `UpdatedAt` without\n  changing the finding state. Key on finding `Id` for idempotency.\n\n## Expert heuristic\n\n**EventBridge custom action pattern for finding-to-runbook + severity-based\nremediation SLA + suppression rule with expiration.**\n\nThe highest-leverage Security Hub automation pattern is a three-layer\nrouting design:\n\n1. **Layer 1 — Severity router (EventBridge rule):** An EventBridge rule\n   on `aws.securityhub` filtering on `detail.findings[0].Severity.Label`\n   in `[\"CRITICAL\", \"HIGH\"]` targets a Lambda dispatcher. Critical = 1hr\n   SLA; High = 24hr SLA.\n\n2. **Layer 2 — Finding-to-runbook mapper (Lambda dispatcher):** The\n   Lambda reads the finding, extracts `Resources[0].Id` and\n   `Resources[0].Type`, looks up the SSM runbook in a mapping table, and\n   invokes `ssm:start-automation-execution`. For findings without a\n   managed runbook, it calls `batch-update-findings` with NOTIFIED and\n   sends SNS.\n\n3. **Layer 3 — Suppression with expiration (scheduled Lambda):** A daily\n   Lambda checks suppressed findings for expiration. Any suppression\n   whose Note date has passed is un-suppressed, re-enabling the finding\n   for remediation routing.\n\n**Severity-based remediation SLA table (default):**\n\n| Severity | Auto-remediate | Notify | SLA |\n|---|---|---|---|\n| CRITICAL | Yes (if runbook + safety gate) | Page on-call | 1 hour |\n| HIGH | Yes (if runbook exists) | Email channel | 24 hours |\n| MEDIUM | No | Email channel | 7 days |\n| LOW | No | Weekly digest | 30 days |\n\n## Configuration dependency graph\n\n```\nSecurity Hub enabled (enable-security-hub)\n  +-- Standards enabled (CIS, PCI, FSBP)\n  |    +-- Controls generate findings\n  |         +-- EventBridge rule (severity-filtered)\n  |              +-- Lambda dispatcher (finding to runbook mapping)\n  |              |    +-- SSM Automation runbook (managed or custom)\n  |              |    +-- batch-update-findings (close finding)\n  |              +-- SNS topic (notify security channel)\n  |              +-- SQS DLQ (failed remediation buffer)\n  |         +-- Suppression evaluator (scheduled Lambda)\n  |              +-- batch-update-findings (expire suppressions)\n  +-- Organizations delegation (delegated administrator)\n  |    +-- Member accounts managed (standards enabled per member, per region)\n  +-- Insights (create-insight)\n  |    +-- Remediation tracking dashboard\n  +-- Incident Manager integration (critical escalation)\n       +-- Response plan to on-call escalation\n```\n\n## Pre-flight: data requirements\n\n| Input | Source | Why |\n|---|---|---|\n| Enabled standards | `get-enabled-standards` | Which control sets are active |\n| Active findings | `get-findings` with severity filter | Volume and types to automate |\n| Finding types | Finding `Title`, `Resources[0].Type` | Drives runbook selection |\n| Custom actions | `describe-action-targets` | Existing manual actions |\n| SSM documents | `ssm list-documents --document-type Automation` | Runbook inventory |\n| EventBridge rules | `events list-rules` on securityhub bus | Existing automation wiring |\n| Delegated admin | `list-organization-admin-accounts` | Multi-account setup state |\n| Insights | `get-insights` | Tracking dashboard state |\n\n**If the input is malformed**, emit:\n\n```text\nREMEDIATION: \u003Creference>\nFINDING_TYPE: UNKNOWN\nVERDICT: ERROR\nREASON: Cannot design remediation — finding type and resource context required.\nGAP: Re-supply get-findings output with Resources[] populated.\n```\n\n## Process — Workflow design (apply in order)\n\n### Step 0: Expert knowledge — non-obvious Security Hub behaviors\n\n> Moved to [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md#step-0-expert-knowledge--non-obvious-security-hub-behaviors).\n> Eight non-obvious behaviors: Imported-vs-Custom-Action detail-type, batch-update-findings Id+ProductArn, dedup by generator ID, standard enable delay, suppression re-eval, per-account custom actions, EventBridge input transformer, RESOLVED re-open.\n\n### Step 1: Verify Security Hub and standards are active\n\n```bash\naws securityhub get-enabled-standards \\\n  --query 'StandardsSubscriptions[?StandardsStatus==`ACTIVE`]' --output json\n```\n\nIf empty:\n\n```bash\naws securityhub batch-enable-standards \\\n  --standards-subscription-requests '[{\"StandardsArn\":\"arn:aws:securityhub:::ruleset\u002Fcis-aws-foundations-benchmark\u002Fv\u002F1.4.0\"},{\"StandardsArn\":\"arn:aws:securityhub:us-east-1::standards\u002Faws-foundational-security-best-practices\u002Fv\u002F1.0.0\"}]'\n```\n\n### Step 2: Classify findings and map strategy\n\n| Finding type | Standard | Resource | Strategy |\n|---|---|---|---|\n| FSBP S3.1 | FSBP | `AwsS3Bucket` | Auto-remediate (AWS-DisableS3BucketPublicAccess) |\n| FSBP IAM.3 | FSBP | `AwsIamUser` | Auto-remediate (AWS-IAMRevokeUnusedAccessKey) |\n| GuardDuty ConsoleLoginWithoutMFA | GuardDuty | `AwsIamUser` | Notify-only (human investigation) |\n| CIS 4.1 SG open | CIS | `AwsEc2SecurityGroup` | REVIEW_REQUIRED (custom runbook needed) |\n\n### Step 3: Route by severity (the severity matrix)\n\n| Severity | Finding characteristic | Route | Why |\n|---|---|---|---|\n| CRITICAL | Credential exposure, root compromise | Auto-remediate + Incident Manager | Breach risk; page on-call |\n| HIGH | Public S3, unused keys, disabled trail | Auto-remediate (if runbook exists) | Fixable, reversible; 24hr SLA |\n| MEDIUM | Missing tags, minor drift | Notify-only (SNS) | Low blast radius |\n| LOW | Informational | Weekly digest | No urgency |\n| ACCEPTED RISK | Known exception | Suppress with expiration | Compliant; re-evaluate |\n\n**Decision rule:** default to **notify-only** unless ALL of: (a) managed\nrunbook or tested Lambda exists, (b) fix is reversible, (c)\npost-execution verification configured, (d) `batch-update-findings`\nwired to close the finding.\n\n### Step 4: Wire EventBridge rule for automatic remediation\n\n```bash\naws events put-rule \\\n  --name securityhub-critical-high-auto-remediation \\\n  --event-pattern '{\n    \"source\": [\"aws.securityhub\"],\n    \"detail-type\": [\"Security Hub Findings - Imported\"],\n    \"detail\": {\n      \"findings\": {\n        \"Severity\": {\"Label\": [\"CRITICAL\", \"HIGH\"]},\n        \"Workflow\": {\"Status\": [\"NEW\"]}\n      }\n    }\n  }'\n\naws events put-targets \\\n  --rule securityhub-critical-high-auto-remediation \\\n  --targets '[{\n    \"Id\": \"remediation-dispatcher\",\n    \"Arn\": \"arn:aws:lambda:us-east-1:111111111111:function:securityhub-remediation-dispatcher\",\n    \"InputTransformer\": {\n      \"InputPathsMap\": {\"finding\": \"$.detail.findings[0]\"},\n      \"InputTemplate\": \"{\\\"finding\\\": \u003Cfinding>}\"\n    },\n    \"DeadLetterConfig\": {\"Arn\": \"arn:aws:sqs:us-east-1:111111111111:securityhub-remediation-dlq\"}\n  }]'\n```\n\n### Step 5: Map finding type to runbook (the dispatch table)\n\n| Finding pattern | SSM runbook | Reversible |\n|---|---|---|\n| S3 public access | `AWS-DisableS3BucketPublicAccess` | Yes |\n| S3 missing encryption | `AWS-EnableS3BucketEncryption` | Yes |\n| IAM unused access key | `AWS-IAMRevokeUnusedAccessKey` | Yes |\n| CloudTrail disabled | `AWS-EnableCloudTrailLogging` | Yes |\n| SG open to world | Custom Lambda | Verify false positives |\n| Root compromise | NONE — notify Incident Manager | N\u002FA |\n\n### Step 6: Build the Lambda remediation dispatcher\n\n> Moved to [references\u002Fworked-examples.md](references\u002Fworked-examples.md#step-6-build-the-lambda-remediation-dispatcher).\n> Full Lambda dispatcher reference implementation: RUNBOOK_MAP, start-automation-execution, batch-update-findings NOTIFIED\u002FFAILED notes, SNS fallback.\n\n### Step 7: Configure suppression rules for accepted risks\n\n```bash\naws securityhub batch-update-findings \\\n  --finding-identifiers '[{\"Id\":\"arn:aws:securityhub:us-east-1:111111111111:subscription\u002Fcis-finding\u002Fabc123\",\"ProductArn\":\"arn:aws:securityhub:us-east-1::product\u002Faws\u002Fsecurityhub\"}]' \\\n  --workflow '{\"Status\":\"SUPPRESSED\"}' \\\n  --note '{\"Text\":\"Suppressed until 2026-12-01; accepted risk: CI\u002FCD requires port 22. Re-evaluate after VPN migration.\",\"UpdatedBy\":\"security-team\"}' \\\n  --record-state ARCHIVED\n```\n\n### Step 8: Update finding workflow status after remediation\n\n```bash\naws securityhub batch-update-findings \\\n  --finding-identifiers '[{\"Id\":\"\u003Cfinding-id>\",\"ProductArn\":\"\u003Cproduct-arn>\"}]' \\\n  --workflow '{\"Status\":\"RESOLVED\"}' \\\n  --note '{\"Text\":\"Remediation verified: S3 public access disabled. Config confirms COMPLIANT.\",\"UpdatedBy\":\"verification-lambda\"}'\n```\n\n### Step 9: Deploy insights for remediation tracking\n\n```bash\naws securityhub create-insight \\\n  --name \"Remediation Backlog by Severity\" \\\n  --filters '{\"SeverityLabel\":[{\"Value\":\"CRITICAL\",\"Comparison\":\"EQUALS\"},{\"Value\":\"HIGH\",\"Comparison\":\"EQUALS\"}],\"WorkflowStatus\":[{\"Value\":\"NEW\",\"Comparison\":\"EQUALS\"}]}' \\\n  --group-by-attribute \"SeverityLabel\"\n```\n\n### Step 10: Enable compliance standards\n\n```bash\naws securityhub batch-enable-standards \\\n  --standards-subscription-requests '[{\"StandardsArn\":\"arn:aws:securityhub:us-east-1::standards\u002Faws-foundational-security-best-practices\u002Fv\u002F1.0.0\"},{\"StandardsArn\":\"arn:aws:securityhub:us-east-1::standards\u002Fpci-dss\u002Fv\u002F1.0.0\"}]'\n```\n\n### Step 11: Integrate with Incident Manager\n\nFor CRITICAL findings requiring human escalation:\n\n```bash\naws ssm-incidents create-response-plan \\\n  --name securityhub-critical-escalation \\\n  --incident-template '{\"title\":\"Security Hub Critical Finding\",\"impact\":1,\"severity\":1}'\n```\n\nWire an EventBridge rule on CRITICAL findings to trigger the response plan.\n\n### Step 12: Multi-account via Organizations delegation\n\n```bash\naws securityhub enable-organization-admin-account --admin-account-id 222222222222\naws securityhub create-members \\\n  --account-details '[{\"AccountId\":\"333333333333\",\"Email\":\"secops@example.com\"}]'\n```\n\n## Output format\n\n### Literal output labels\n\n> Moved to [references\u002Fworked-examples.md](references\u002Fworked-examples.md#literal-output-labels).\n> Literal output-label contract restated: FINDING_ID\u002FVERDICT\u002FCHECKLIST\u002FGAP\u002FTEMPLATE block, no prose preface.\n\n### FORBIDDEN — NEVER do these\n\n> Moved to [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md#forbidden--never-do-these).\n> Seven forbidden patterns: severity filter, deprecated update-findings, suppression expiration, close-after-remediate, SQS DLQ, detail-type confusion, UpdatedAt idempotency.\n\n### Worked example — Critical S3 public-access finding, auto-remediated\n\nScenario: FSBP control S3.1 detects a publicly accessible S3 bucket.\nEventBridge routes the CRITICAL finding to a Lambda dispatcher that\ninvokes the `AWS-DisableS3BucketPublicAccess` SSM runbook, then closes\nthe finding via `batch-update-findings`.\n\n```text\nFINDING_ID: arn:aws:securityhub:us-east-1:111111111111:subscription\u002Fcis-aws-foundations-benchmark\u002Fv\u002F1.2.0\u002F3.1\u002Ffinding\u002F01a23456-7890-abcd-ef01-234567890abc\nFINDING_TYPE: Software and Configuration Checks\u002FAWS Security Best Practices\u002FS3.1\nSTANDARD: FSBP\nVERDICT: AUTOMATION_DEPLOYED\nCHECKLIST:\n  [✓] Severity route: CRITICAL_AUTO (Critical → SSM auto-remediate, 1h SLA)\n  [✓] EventBridge rule: securityhub-critical-auto-remediation\n      pattern: {\"source\":[\"aws.securityhub\"],\"detail-type\":[\"Security Hub Findings - Imported\"],\"detail\":{\"findings\":{\"Severity\":{\"Label\":[\"CRITICAL\"]},\"Workflow\":{\"Status\":[\"NEW\"]}}}}\n  [✓] SSM runbook: AWS-DisableS3BucketPublicAccess (param: S3BucketName = corp-data-lake-prod)\n  [✓] batch-update-findings: NOTIFIED on dispatch → RESOLVED after runbook success\n  [✓] SQS DLQ: arn:aws:sqs:us-east-1:111111111111:securityhub-remediation-dlq\n  [✓] Suppression: NONE\n  [✓] Insight: arn:aws:securityhub:us-east-1:111111111111:insight\u002Fabc123\n  [✓] Safety gate: dry-run tested 48h in staging, zero false positives\nGAP: None\nTEMPLATE:\n  aws events put-rule --name securityhub-critical-auto-remediation \\\\\n    --event-pattern '{\"source\":[\"aws.securityhub\"],\"detail-type\":[\"Security Hub Findings - Imported\"],\"detail\":{\"findings\":{\"Severity\":{\"Label\":[\"CRITICAL\"]},\"Workflow\":{\"Status\":[\"NEW\"]}}}}'\n  aws ssm start-automation-execution \\\\\n    --document-name AWS-DisableS3BucketPublicAccess \\\\\n    --parameters '{\"S3BucketName\":[\"corp-data-lake-prod\"],\"AutomationAssumeRole\":[\"arn:aws:iam::111111111111:role\u002Faws-service-role\u002FAmazonSSMAutomationRole\u002FAWS-SSM-AutomationExecutionRole\"]}'\n  aws securityhub batch-update-findings \\\\\n    --finding-identifiers '[{\"Id\":\"arn:aws:securityhub:us-east-1:111111111111:subscription\u002Fcis-aws-foundations-benchmark\u002Fv\u002F1.2.0\u002F3.1\u002Ffinding\u002F01a23456-7890-abcd-ef01-234567890abc\",\"ProductArn\":\"arn:aws:securityhub:us-east-1::product\u002Faws\u002Fsecurityhub\"}]' \\\\\n    --workflow '{\"Status\":\"RESOLVED\"}' \\\\\n    --note '{\"Text\":\"S3 public access disabled via AWS-DisableS3BucketPublicAccess. Verified BlockPublicAccess=TRUE.\",\"UpdatedBy\":\"remediation-dispatcher\"}'\n```\n\nSeverity routing summary (how each tier is handled):\n\n| Severity | Route | Mechanism | SLA |\n|---|---|---|---|\n| CRITICAL | SSM auto-remediate | EventBridge → Lambda dispatcher → SSM runbook → batch-update-findings RESOLVED | 1 hour |\n| HIGH | Lambda fixer | EventBridge → Lambda custom remediation → batch-update-findings RESOLVED | 24 hours |\n| MEDIUM | Notify only | EventBridge → SNS → security channel email | 7 days |\n| LOW | Weekly digest | Scheduled Lambda → aggregated SNS digest | 30 days |\n\n### Worked example — REVIEW_REQUIRED, no runbook mapped\n\n> Moved to [references\u002Fworked-examples.md](references\u002Fworked-examples.md#worked-example--review_required-no-runbook-mapped).\n> REVIEW_REQUIRED block: custom Lambda credential-exposure finding with no managed runbook, gap and build plan cited.\n\n### Decision tree\n\n```text\nIs there a managed SSM runbook for this finding type?\n├─ Yes → Severity CRITICAL or HIGH?\n│        ├─ Yes → AUTOMATION_DEPLOYED\n│        │        (EventBridge → Lambda dispatcher → SSM runbook → batch-update-findings RESOLVED)\n│        └─ No (MEDIUM\u002FLOW) → MEDIUM_NOTIFY \u002F LOW_NOTIFY\n│                         (EventBridge → SNS → email\u002Fdigest, no auto-fix)\n└─ No → Is a custom Lambda remediation feasible?\n         ├─ Yes → Build + test in staging → AUTOMATION_DEPLOYED\n         └─ No → REVIEW_REQUIRED (cite the gap: \"no runbook, Lambda not feasible\")\n                  (route: NOTIFIED via SNS, create insight for backlog tracking)\n\nIs the finding an accepted risk?\n  → Suppress with expiration date in Note → daily evaluator re-opens when expired\n```\n\n## Anti-Patterns — NEVER do these things\n\n> Moved to [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md#anti-patterns--never-do-these-things).\n> Anti-pattern catalog: unfiltered EventBridge rules, update-findings, permanent suppression, unclosed findings, missing DLQ, unvalidated standards, detail-type confusion, UpdatedAt keying.\n\n## Pre-flight safety checks\n\n- **MANDATORY CONFIRMATION GATE.** Before any state-changing operation,\n  emit: `CONFIRM: About to \u003Caction> for finding \u003Ctype> in account\n  \u003Caccount>. Proceed? (yes\u002Fno)`\n\n- **Back up current configuration:** `aws securityhub get-enabled-standards\n  > \u002Ftmp\u002Fsecurityhub-baseline-$(date +%s).json`\n\n- **Before enabling auto-remediation on a new finding type**, test the\n  Lambda dispatcher with a sample finding payload and verify it produces\n  correct SSM execution parameters.\n\n## Appendix A — Common finding-to-runbook mappings\n\n> Moved to [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md#appendix-a--common-finding-to-runbook-mappings).\n> Finding-to-runbook mapping table: FSBP S3.1\u002FS3.4\u002FIAM.3\u002FCloudTrail.1 auto runbooks, CIS 4.1 custom Lambda.\n\n## Appendix B — Decision tree\n\n> Moved to [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md#appendix-b--decision-tree).\n> Compact decision tree: managed runbook → severity route → verdict; custom-Lambda feasibility branch.\n\n## Recent AWS features (2024-2026)\n\n> Moved to [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md#recent-aws-features-2024-2026).\n> Centralized configuration, cross-region finding aggregation, SSM native finding updates, new-service FSBP controls.\n\n## Expert heuristic: blast radius of auto-remediation\n\n> Moved to [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md#expert-heuristic-blast-radius-of-auto-remediation).\n> Pre-production validation protocol: staging deploy with planted findings, 48h dry-run, live enable, production promotion.\n\n## References (load on demand)\n\n- [advanced-patterns](references\u002Fadvanced-patterns.md) — Step 0 non-obvious behaviors, FORBIDDEN and Anti-Pattern catalogs, Appendix A runbook mappings, Appendix B compact decision tree, blast-radius validation protocol, recent AWS features\n- [worked-examples](references\u002Fworked-examples.md) — Step 6 Lambda dispatcher reference implementation, literal output-label contract, REVIEW_REQUIRED worked example\n- [eventbridge-finding-patterns](references\u002Feventbridge-finding-patterns.md) — EventBridge rule patterns, severity filters, input transformers, custom-action wiring\n- [ssm-runbook-templates](references\u002Fssm-runbook-templates.md) — SSM Automation runbook YAML templates and severity-based SLA table\n\n## Domain\n\nAWS CloudOps \u002F Security Automation — Security Hub-driven remediation.\n\n## AWS documentation\n\n- **AWS Security Hub** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fsecurityhub\u002Flatest\u002Fuserguide\u002Fwhat-is-securityhub.html\n- **Security Hub Automated Remediation** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fsecurityhub\u002Flatest\u002Fuserguide\u002Fsecurityhub-automated-remediation.html\n- **Security Hub Custom Actions** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fsecurityhub\u002Flatest\u002Fuserguide\u002Fsecurityhub-custom-actions.html\n- **BatchUpdateFindings API** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fsecurityhub\u002Flatest\u002FAPIReference\u002FAPI_BatchUpdateFindings.html\n- **Security Hub Insights** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fsecurityhub\u002Flatest\u002Fuserguide\u002Fsecurityhub-insights.html\n- **Systems Manager Incident Manager** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fincident-manager\u002Flatest\u002Fuserguide\u002Fwhat-is-incidents.html\n","# Security Hub Remediation Automator\n\n## Mindset\n\n**One-line takeaway:** every Security Hub remediation workflow is a five-stage\npipeline — **detect** (Security Hub control or partner finding) → **route**\n(EventBridge rule on severity + finding type) → **decide** (auto-remediate\nor notify-only) → **execute** (SSM Automation runbook or Lambda function) →\n**close** (update finding workflow status to RESOLVED, verify in insights).\nA gap in ANY stage produces either noise (findings pile up with no action)\nor silent failure (remediation fires but the finding never closes).\n\n- **Detection** without **routing** is a dashboard nobody watches: Critical\n  findings accumulate and operators lose visibility into what matters.\n- **Auto-remediation** on Critical\u002FHigh without a **safety gate** is risky:\n  the runbook fires on the first NEW finding, and if the fix is wrong, the\n  damage is done before any human reviews it.\n- **Finding closure** is the closing gate. A remediation that fixes the\n  underlying resource but does NOT update the finding workflow status leaves\n  the Security Hub dashboard perpetually dirty, destroying compliance\n  reporting accuracy.\n\n## Quick navigation\n\n| You want to... | Go to |\n|---|---|\n| Route findings by severity to auto-remediate vs notify | Step 3 (severity matrix) |\n| Wire a custom action to EventBridge for findings | Step 4 + worked CLI |\n| Map a finding type to an SSM runbook or Lambda fixer | Step 5 + Appendix A |\n| Build a Lambda remediation function for a custom finding | Step 6 |\n| Configure suppression rules for accepted risks | Step 7 |\n| Update finding workflow status (NEW to NOTIFIED to RESOLVED) | Step 8 |\n| Deploy Security Hub insights for remediation tracking | Step 9 |\n| Enable compliance standards (CIS, PCI DSS, FSBP) | Step 10 |\n| Integrate with Systems Manager Incident Manager | Step 11 |\n| Set up multi-account via Organizations delegation | Step 12 |\n| Avoid common remediation pitfalls | Anti-Patterns |\n| Recent features (custom actions, insights, control updates) | Recent AWS features |\n\n## Critical rules at a glance (do NOT bury these)\n\n1. **Security Hub custom actions are NOT automatic.** A custom action\n   creates a menu item in the console. It fires ONLY when an operator\n   manually selects findings and invokes the action. For automatic\n   remediation, you MUST use an EventBridge rule on the finding event\n   pattern — NOT the custom action ARN.\n\n2. **`batch-update-findings` is the ONLY API that updates workflow status.**\n   `update-findings` is deprecated and operates on a single finding.\n   `batch-update-findings` accepts up to 100 finding identifiers per call.\n   A remediation that does NOT call it leaves findings in NEW status\n   forever, corrupting compliance dashboards.\n\n3. **Security Hub finding events use `detail-type: \"Security Hub Findings -\n   Imported\"`.** NOT \"Custom Action\". The former fires on ingestion\n   (automation). The latter fires on human click (manual). Confusing the\n   two is the #1 reason EventBridge-driven remediation does not fire.\n\n4. **Control standards are region-specific.** Enabling CIS, PCI DSS, or\n   FSBP in us-east-1 does NOT enable them in eu-west-1. Multi-region\n   deployments require per-region `update-standards` calls.\n\n5. **Suppression rules archive findings but do NOT delete them.** A\n   suppressed finding has `WorkflowStatus: SUPPRESSED` and\n   `RecordState: ARCHIVED`. Always set a `Note` with the acceptance\n   rationale and an expiration date for re-evaluation.\n\n## STRICT output contract\n\nEvery remediation design MUST produce exactly one REMEDIATION block per\nfinding type, following this format:\n\n```text\nFINDING_ID: \u003CSecurity Hub finding Id — arn:aws:securityhub:...>\nFINDING_TYPE: \u003CSecurity Hub finding type>\nSTANDARD: \u003CCIS | PCI | FSBP | Custom | N\u002FA>\nVERDICT: AUTOMATION_DEPLOYED | REVIEW_REQUIRED\nCHECKLIST:\n  [✓|✗] Severity route: CRITICAL_AUTO | HIGH_AUTO | MEDIUM_NOTIFY | LOW_NOTIFY\n  [✓|✗] EventBridge rule: \u003Crule name + pattern summary>\n  [✓|✗] SSM runbook \u002F Lambda fixer: \u003Cdocument name | function ARN | NONE>\n  [✓|✗] batch-update-findings: NOTIFIED on dispatch → RESOLVED on success\n  [✓|✗] SQS DLQ: \u003CDLQ ARN on the EventBridge target>\n  [✓|✗] Suppression: \u003CNONE | rule + expiration YYYY-MM-DD>\n  [✓|✗] Insight: \u003Cinsight ARN | TBD>\n  [✓|✗] Safety gate: \u003Cdry-run 48h | pre-prod validated>\nGAP: \u003Cif REVIEW_REQUIRED, the specific missing piece>\nTEMPLATE: \u003CCLI snippet or IaC>\n```\n\n## NEVER section\n\n- **NEVER** wire an EventBridge rule on `aws.securityhub` without a\n  `Severity.Label` filter. Without it, the rule fires on EVERY finding\n  including LOW and INFORMATIONAL, overwhelming Lambda concurrency and\n  producing cost spikes.\n\n- **NEVER** use `update-findings` (deprecated). Use\n  `batch-update-findings` which accepts up to 100 findings per call and\n  is the forward-compatible API.\n\n- **NEVER** suppress a finding without an expiration date in the Note.\n  Permanent suppression violates every compliance framework (PCI DSS,\n  SOC 2, ISO 27001). Always include \"Suppressed until YYYY-MM-DD\" and\n  build the daily evaluator Lambda to re-open expired suppressions.\n\n- **NEVER** auto-remediate a finding without calling\n  `batch-update-findings` afterward. A remediation that fixes the\n  resource but leaves the finding in NEW status corrupts dashboards and\n  triggers duplicate remediation.\n\n- **NEVER** deploy a Lambda remediation function without an SQS DLQ on\n  the EventBridge target. Failed invocations are silently dropped\n  without a DLQ; the finding stays open and no one knows.\n\n- **NEVER** enable a compliance standard in production without staging\n  validation. Standards generate findings immediately upon enablement.\n  An unprepared account can see hundreds of findings in minutes.\n\n- **NEVER** assume Security Hub is enabled in all member accounts. A\n  member without Security Hub produces zero findings — not because it\n  is secure, but because no controls are running.\n\n- **NEVER** key remediation idempotency on `UpdatedAt`. Security Hub\n  re-evaluates controls periodically, changing `UpdatedAt` without\n  changing the finding state. Key on finding `Id` for idempotency.\n\n## Expert heuristic\n\n**EventBridge custom action pattern for finding-to-runbook + severity-based\nremediation SLA + suppression rule with expiration.**\n\nThe highest-leverage Security Hub automation pattern is a three-layer\nrouting design:\n\n1. **Layer 1 — Severity router (EventBridge rule):** An EventBridge rule\n   on `aws.securityhub` filtering on `detail.findings[0].Severity.Label`\n   in `[\"CRITICAL\", \"HIGH\"]` targets a Lambda dispatcher. Critical = 1hr\n   SLA; High = 24hr SLA.\n\n2. **Layer 2 — Finding-to-runbook mapper (Lambda dispatcher):** The\n   Lambda reads the finding, extracts `Resources[0].Id` and\n   `Resources[0].Type`, looks up the SSM runbook in a mapping table, and\n   invokes `ssm:start-automation-execution`. For findings without a\n   managed runbook, it calls `batch-update-findings` with NOTIFIED and\n   sends SNS.\n\n3. **Layer 3 — Suppression with expiration (scheduled Lambda):** A daily\n   Lambda checks suppressed findings for expiration. Any suppression\n   whose Note date has passed is un-suppressed, re-enabling the finding\n   for remediation routing.\n\n**Severity-based remediation SLA table (default):**\n\n| Severity | Auto-remediate | Notify | SLA |\n|---|---|---|---|\n| CRITICAL | Yes (if runbook + safety gate) | Page on-call | 1 hour |\n| HIGH | Yes (if runbook exists) | Email channel | 24 hours |\n| MEDIUM | No | Email channel | 7 days |\n| LOW | No | Weekly digest | 30 days |\n\n## Configuration dependency graph\n\n```\nSecurity Hub enabled (enable-security-hub)\n  +-- Standards enabled (CIS, PCI, FSBP)\n  |    +-- Controls generate findings\n  |         +-- EventBridge rule (severity-filtered)\n  |              +-- Lambda dispatcher (finding to runbook mapping)\n  |              |    +-- SSM Automation runbook (managed or custom)\n  |              |    +-- batch-update-findings (close finding)\n  |              +-- SNS topic (notify security channel)\n  |              +-- SQS DLQ (failed remediation buffer)\n  |         +-- Suppression evaluator (scheduled Lambda)\n  |              +-- batch-update-findings (expire suppressions)\n  +-- Organizations delegation (delegated administrator)\n  |    +-- Member accounts managed (standards enabled per member, per region)\n  +-- Insights (create-insight)\n  |    +-- Remediation tracking dashboard\n  +-- Incident Manager integration (critical escalation)\n       +-- Response plan to on-call escalation\n```\n\n## Pre-flight: data requirements\n\n| Input | Source | Why |\n|---|---|---|\n| Enabled standards | `get-enabled-standards` | Which control sets are active |\n| Active findings | `get-findings` with severity filter | Volume and types to automate |\n| Finding types | Finding `Title`, `Resources[0].Type` | Drives runbook selection |\n| Custom actions | `describe-action-targets` | Existing manual actions |\n| SSM documents | `ssm list-documents --document-type Automation` | Runbook inventory |\n| EventBridge rules | `events list-rules` on securityhub bus | Existing automation wiring |\n| Delegated admin | `list-organization-admin-accounts` | Multi-account setup state |\n| Insights | `get-insights` | Tracking dashboard state |\n\n**If the input is malformed**, emit:\n\n```text\nREMEDIATION: \u003Creference>\nFINDING_TYPE: UNKNOWN\nVERDICT: ERROR\nREASON: Cannot design remediation — finding type and resource context required.\nGAP: Re-supply get-findings output with Resources[] populated.\n```\n\n## Process — Workflow design (apply in order)\n\n### Step 0: Expert knowledge — non-obvious Security Hub behaviors\n\n> Moved to [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md#step-0-expert-knowledge--non-obvious-security-hub-behaviors).\n> Eight non-obvious behaviors: Imported-vs-Custom-Action detail-type, batch-update-findings Id+ProductArn, dedup by generator ID, standard enable delay, suppression re-eval, per-account custom actions, EventBridge input transformer, RESOLVED re-open.\n\n### Step 1: Verify Security Hub and standards are active\n\n```bash\naws securityhub get-enabled-standards \\\n  --query 'StandardsSubscriptions[?StandardsStatus==`ACTIVE`]' --output json\n```\n\nIf empty:\n\n```bash\naws securityhub batch-enable-standards \\\n  --standards-subscription-requests '[{\"StandardsArn\":\"arn:aws:securityhub:::ruleset\u002Fcis-aws-foundations-benchmark\u002Fv\u002F1.4.0\"},{\"StandardsArn\":\"arn:aws:securityhub:us-east-1::standards\u002Faws-foundational-security-best-practices\u002Fv\u002F1.0.0\"}]'\n```\n\n### Step 2: Classify findings and map strategy\n\n| Finding type | Standard | Resource | Strategy |\n|---|---|---|---|\n| FSBP S3.1 | FSBP | `AwsS3Bucket` | Auto-remediate (AWS-DisableS3BucketPublicAccess) |\n| FSBP IAM.3 | FSBP | `AwsIamUser` | Auto-remediate (AWS-IAMRevokeUnusedAccessKey) |\n| GuardDuty ConsoleLoginWithoutMFA | GuardDuty | `AwsIamUser` | Notify-only (human investigation) |\n| CIS 4.1 SG open | CIS | `AwsEc2SecurityGroup` | REVIEW_REQUIRED (custom runbook needed) |\n\n### Step 3: Route by severity (the severity matrix)\n\n| Severity | Finding characteristic | Route | Why |\n|---|---|---|---|\n| CRITICAL | Credential exposure, root compromise | Auto-remediate + Incident Manager | Breach risk; page on-call |\n| HIGH | Public S3, unused keys, disabled trail | Auto-remediate (if runbook exists) | Fixable, reversible; 24hr SLA |\n| MEDIUM | Missing tags, minor drift | Notify-only (SNS) | Low blast radius |\n| LOW | Informational | Weekly digest | No urgency |\n| ACCEPTED RISK | Known exception | Suppress with expiration | Compliant; re-evaluate |\n\n**Decision rule:** default to **notify-only** unless ALL of: (a) managed\nrunbook or tested Lambda exists, (b) fix is reversible, (c)\npost-execution verification configured, (d) `batch-update-findings`\nwired to close the finding.\n\n### Step 4: Wire EventBridge rule for automatic remediation\n\n```bash\naws events put-rule \\\n  --name securityhub-critical-high-auto-remediation \\\n  --event-pattern '{\n    \"source\": [\"aws.securityhub\"],\n    \"detail-type\": [\"Security Hub Findings - Imported\"],\n    \"detail\": {\n      \"findings\": {\n        \"Severity\": {\"Label\": [\"CRITICAL\", \"HIGH\"]},\n        \"Workflow\": {\"Status\": [\"NEW\"]}\n      }\n    }\n  }'\n\naws events put-targets \\\n  --rule securityhub-critical-high-auto-remediation \\\n  --targets '[{\n    \"Id\": \"remediation-dispatcher\",\n    \"Arn\": \"arn:aws:lambda:us-east-1:111111111111:function:securityhub-remediation-dispatcher\",\n    \"InputTransformer\": {\n      \"InputPathsMap\": {\"finding\": \"$.detail.findings[0]\"},\n      \"InputTemplate\": \"{\\\"finding\\\": \u003Cfinding>}\"\n    },\n    \"DeadLetterConfig\": {\"Arn\": \"arn:aws:sqs:us-east-1:111111111111:securityhub-remediation-dlq\"}\n  }]'\n```\n\n### Step 5: Map finding type to runbook (the dispatch table)\n\n| Finding pattern | SSM runbook | Reversible |\n|---|---|---|\n| S3 public access | `AWS-DisableS3BucketPublicAccess` | Yes |\n| S3 missing encryption | `AWS-EnableS3BucketEncryption` | Yes |\n| IAM unused access key | `AWS-IAMRevokeUnusedAccessKey` | Yes |\n| CloudTrail disabled | `AWS-EnableCloudTrailLogging` | Yes |\n| SG open to world | Custom Lambda | Verify false positives |\n| Root compromise | NONE — notify Incident Manager | N\u002FA |\n\n### Step 6: Build the Lambda remediation dispatcher\n\n> Moved to [references\u002Fworked-examples.md](references\u002Fworked-examples.md#step-6-build-the-lambda-remediation-dispatcher).\n> Full Lambda dispatcher reference implementation: RUNBOOK_MAP, start-automation-execution, batch-update-findings NOTIFIED\u002FFAILED notes, SNS fallback.\n\n### Step 7: Configure suppression rules for accepted risks\n\n```bash\naws securityhub batch-update-findings \\\n  --finding-identifiers '[{\"Id\":\"arn:aws:securityhub:us-east-1:111111111111:subscription\u002Fcis-finding\u002Fabc123\",\"ProductArn\":\"arn:aws:securityhub:us-east-1::product\u002Faws\u002Fsecurityhub\"}]' \\\n  --workflow '{\"Status\":\"SUPPRESSED\"}' \\\n  --note '{\"Text\":\"Suppressed until 2026-12-01; accepted risk: CI\u002FCD requires port 22. Re-evaluate after VPN migration.\",\"UpdatedBy\":\"security-team\"}' \\\n  --record-state ARCHIVED\n```\n\n### Step 8: Update finding workflow status after remediation\n\n```bash\naws securityhub batch-update-findings \\\n  --finding-identifiers '[{\"Id\":\"\u003Cfinding-id>\",\"ProductArn\":\"\u003Cproduct-arn>\"}]' \\\n  --workflow '{\"Status\":\"RESOLVED\"}' \\\n  --note '{\"Text\":\"Remediation verified: S3 public access disabled. Config confirms COMPLIANT.\",\"UpdatedBy\":\"verification-lambda\"}'\n```\n\n### Step 9: Deploy insights for remediation tracking\n\n```bash\naws securityhub create-insight \\\n  --name \"Remediation Backlog by Severity\" \\\n  --filters '{\"SeverityLabel\":[{\"Value\":\"CRITICAL\",\"Comparison\":\"EQUALS\"},{\"Value\":\"HIGH\",\"Comparison\":\"EQUALS\"}],\"WorkflowStatus\":[{\"Value\":\"NEW\",\"Comparison\":\"EQUALS\"}]}' \\\n  --group-by-attribute \"SeverityLabel\"\n```\n\n### Step 10: Enable compliance standards\n\n```bash\naws securityhub batch-enable-standards \\\n  --standards-subscription-requests '[{\"StandardsArn\":\"arn:aws:securityhub:us-east-1::standards\u002Faws-foundational-security-best-practices\u002Fv\u002F1.0.0\"},{\"StandardsArn\":\"arn:aws:securityhub:us-east-1::standards\u002Fpci-dss\u002Fv\u002F1.0.0\"}]'\n```\n\n### Step 11: Integrate with Incident Manager\n\nFor CRITICAL findings requiring human escalation:\n\n```bash\naws ssm-incidents create-response-plan \\\n  --name securityhub-critical-escalation \\\n  --incident-template '{\"title\":\"Security Hub Critical Finding\",\"impact\":1,\"severity\":1}'\n```\n\nWire an EventBridge rule on CRITICAL findings to trigger the response plan.\n\n### Step 12: Multi-account via Organizations delegation\n\n```bash\naws securityhub enable-organization-admin-account --admin-account-id 222222222222\naws securityhub create-members \\\n  --account-details '[{\"AccountId\":\"333333333333\",\"Email\":\"secops@example.com\"}]'\n```\n\n## Output format\n\n### Literal output labels\n\n> Moved to [references\u002Fworked-examples.md](references\u002Fworked-examples.md#literal-output-labels).\n> Literal output-label contract restated: FINDING_ID\u002FVERDICT\u002FCHECKLIST\u002FGAP\u002FTEMPLATE block, no prose preface.\n\n### FORBIDDEN — NEVER do these\n\n> Moved to [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md#forbidden--never-do-these).\n> Seven forbidden patterns: severity filter, deprecated update-findings, suppression expiration, close-after-remediate, SQS DLQ, detail-type confusion, UpdatedAt idempotency.\n\n### Worked example — Critical S3 public-access finding, auto-remediated\n\nScenario: FSBP control S3.1 detects a publicly accessible S3 bucket.\nEventBridge routes the CRITICAL finding to a Lambda dispatcher that\ninvokes the `AWS-DisableS3BucketPublicAccess` SSM runbook, then closes\nthe finding via `batch-update-findings`.\n\n```text\nFINDING_ID: arn:aws:securityhub:us-east-1:111111111111:subscription\u002Fcis-aws-foundations-benchmark\u002Fv\u002F1.2.0\u002F3.1\u002Ffinding\u002F01a23456-7890-abcd-ef01-234567890abc\nFINDING_TYPE: Software and Configuration Checks\u002FAWS Security Best Practices\u002FS3.1\nSTANDARD: FSBP\nVERDICT: AUTOMATION_DEPLOYED\nCHECKLIST:\n  [✓] Severity route: CRITICAL_AUTO (Critical → SSM auto-remediate, 1h SLA)\n  [✓] EventBridge rule: securityhub-critical-auto-remediation\n      pattern: {\"source\":[\"aws.securityhub\"],\"detail-type\":[\"Security Hub Findings - Imported\"],\"detail\":{\"findings\":{\"Severity\":{\"Label\":[\"CRITICAL\"]},\"Workflow\":{\"Status\":[\"NEW\"]}}}}\n  [✓] SSM runbook: AWS-DisableS3BucketPublicAccess (param: S3BucketName = corp-data-lake-prod)\n  [✓] batch-update-findings: NOTIFIED on dispatch → RESOLVED after runbook success\n  [✓] SQS DLQ: arn:aws:sqs:us-east-1:111111111111:securityhub-remediation-dlq\n  [✓] Suppression: NONE\n  [✓] Insight: arn:aws:securityhub:us-east-1:111111111111:insight\u002Fabc123\n  [✓] Safety gate: dry-run tested 48h in staging, zero false positives\nGAP: None\nTEMPLATE:\n  aws events put-rule --name securityhub-critical-auto-remediation \\\\\n    --event-pattern '{\"source\":[\"aws.securityhub\"],\"detail-type\":[\"Security Hub Findings - Imported\"],\"detail\":{\"findings\":{\"Severity\":{\"Label\":[\"CRITICAL\"]},\"Workflow\":{\"Status\":[\"NEW\"]}}}}'\n  aws ssm start-automation-execution \\\\\n    --document-name AWS-DisableS3BucketPublicAccess \\\\\n    --parameters '{\"S3BucketName\":[\"corp-data-lake-prod\"],\"AutomationAssumeRole\":[\"arn:aws:iam::111111111111:role\u002Faws-service-role\u002FAmazonSSMAutomationRole\u002FAWS-SSM-AutomationExecutionRole\"]}'\n  aws securityhub batch-update-findings \\\\\n    --finding-identifiers '[{\"Id\":\"arn:aws:securityhub:us-east-1:111111111111:subscription\u002Fcis-aws-foundations-benchmark\u002Fv\u002F1.2.0\u002F3.1\u002Ffinding\u002F01a23456-7890-abcd-ef01-234567890abc\",\"ProductArn\":\"arn:aws:securityhub:us-east-1::product\u002Faws\u002Fsecurityhub\"}]' \\\\\n    --workflow '{\"Status\":\"RESOLVED\"}' \\\\\n    --note '{\"Text\":\"S3 public access disabled via AWS-DisableS3BucketPublicAccess. Verified BlockPublicAccess=TRUE.\",\"UpdatedBy\":\"remediation-dispatcher\"}'\n```\n\nSeverity routing summary (how each tier is handled):\n\n| Severity | Route | Mechanism | SLA |\n|---|---|---|---|\n| CRITICAL | SSM auto-remediate | EventBridge → Lambda dispatcher → SSM runbook → batch-update-findings RESOLVED | 1 hour |\n| HIGH | Lambda fixer | EventBridge → Lambda custom remediation → batch-update-findings RESOLVED | 24 hours |\n| MEDIUM | Notify only | EventBridge → SNS → security channel email | 7 days |\n| LOW | Weekly digest | Scheduled Lambda → aggregated SNS digest | 30 days |\n\n### Worked example — REVIEW_REQUIRED, no runbook mapped\n\n> Moved to [references\u002Fworked-examples.md](references\u002Fworked-examples.md#worked-example--review_required-no-runbook-mapped).\n> REVIEW_REQUIRED block: custom Lambda credential-exposure finding with no managed runbook, gap and build plan cited.\n\n### Decision tree\n\n```text\nIs there a managed SSM runbook for this finding type?\n├─ Yes → Severity CRITICAL or HIGH?\n│        ├─ Yes → AUTOMATION_DEPLOYED\n│        │        (EventBridge → Lambda dispatcher → SSM runbook → batch-update-findings RESOLVED)\n│        └─ No (MEDIUM\u002FLOW) → MEDIUM_NOTIFY \u002F LOW_NOTIFY\n│                         (EventBridge → SNS → email\u002Fdigest, no auto-fix)\n└─ No → Is a custom Lambda remediation feasible?\n         ├─ Yes → Build + test in staging → AUTOMATION_DEPLOYED\n         └─ No → REVIEW_REQUIRED (cite the gap: \"no runbook, Lambda not feasible\")\n                  (route: NOTIFIED via SNS, create insight for backlog tracking)\n\nIs the finding an accepted risk?\n  → Suppress with expiration date in Note → daily evaluator re-opens when expired\n```\n\n## Anti-Patterns — NEVER do these things\n\n> Moved to [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md#anti-patterns--never-do-these-things).\n> Anti-pattern catalog: unfiltered EventBridge rules, update-findings, permanent suppression, unclosed findings, missing DLQ, unvalidated standards, detail-type confusion, UpdatedAt keying.\n\n## Pre-flight safety checks\n\n- **MANDATORY CONFIRMATION GATE.** Before any state-changing operation,\n  emit: `CONFIRM: About to \u003Caction> for finding \u003Ctype> in account\n  \u003Caccount>. Proceed? (yes\u002Fno)`\n\n- **Back up current configuration:** `aws securityhub get-enabled-standards\n  > \u002Ftmp\u002Fsecurityhub-baseline-$(date +%s).json`\n\n- **Before enabling auto-remediation on a new finding type**, test the\n  Lambda dispatcher with a sample finding payload and verify it produces\n  correct SSM execution parameters.\n\n## Appendix A — Common finding-to-runbook mappings\n\n> Moved to [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md#appendix-a--common-finding-to-runbook-mappings).\n> Finding-to-runbook mapping table: FSBP S3.1\u002FS3.4\u002FIAM.3\u002FCloudTrail.1 auto runbooks, CIS 4.1 custom Lambda.\n\n## Appendix B — Decision tree\n\n> Moved to [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md#appendix-b--decision-tree).\n> Compact decision tree: managed runbook → severity route → verdict; custom-Lambda feasibility branch.\n\n## Recent AWS features (2024-2026)\n\n> Moved to [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md#recent-aws-features-2024-2026).\n> Centralized configuration, cross-region finding aggregation, SSM native finding updates, new-service FSBP controls.\n\n## Expert heuristic: blast radius of auto-remediation\n\n> Moved to [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md#expert-heuristic-blast-radius-of-auto-remediation).\n> Pre-production validation protocol: staging deploy with planted findings, 48h dry-run, live enable, production promotion.\n\n## References (load on demand)\n\n- [advanced-patterns](references\u002Fadvanced-patterns.md) — Step 0 non-obvious behaviors, FORBIDDEN and Anti-Pattern catalogs, Appendix A runbook mappings, Appendix B compact decision tree, blast-radius validation protocol, recent AWS features\n- [worked-examples](references\u002Fworked-examples.md) — Step 6 Lambda dispatcher reference implementation, literal output-label contract, REVIEW_REQUIRED worked example\n- [eventbridge-finding-patterns](references\u002Feventbridge-finding-patterns.md) — EventBridge rule patterns, severity filters, input transformers, custom-action wiring\n- [ssm-runbook-templates](references\u002Fssm-runbook-templates.md) — SSM Automation runbook YAML templates and severity-based SLA table\n\n## Domain\n\nAWS CloudOps \u002F Security Automation — Security Hub-driven remediation.\n\n## AWS documentation\n\n- **AWS Security Hub** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fsecurityhub\u002Flatest\u002Fuserguide\u002Fwhat-is-securityhub.html\n- **Security Hub Automated Remediation** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fsecurityhub\u002Flatest\u002Fuserguide\u002Fsecurityhub-automated-remediation.html\n- **Security Hub Custom Actions** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fsecurityhub\u002Flatest\u002Fuserguide\u002Fsecurityhub-custom-actions.html\n- **BatchUpdateFindings API** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fsecurityhub\u002Flatest\u002FAPIReference\u002FAPI_BatchUpdateFindings.html\n- **Security Hub Insights** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fsecurityhub\u002Flatest\u002Fuserguide\u002Fsecurityhub-insights.html\n- **Systems Manager Incident Manager** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fincident-manager\u002Flatest\u002Fuserguide\u002Fwhat-is-incidents.html\n",{"name":5,"license":15,"metadata":24,"description":7,"compatibility":42},{"tags":25,"phase":26,"author":27,"domain":28,"family":29,"version":30,"keywords":31,"task_type":32,"complexity":33,"entry_point":34,"skill_class":35,"when_to_use":36,"requires_llm":37,"verdict_shape":38,"lifecycle_status":39,"invocation_schema":40,"supports_pipeline":37,"activation_triggers":41},"aws-security-hub, security-hub, eventbridge, ssm-automation, lambda-remediation, compliance, automate","4","Jacky Chan — AWS Community Builder","aws-cloudops","Security","0.1.0","AWS Security Hub, Security Hub remediation, custom action, EventBridge finding, SSM Automation runbook, Lambda remediation, finding severity routing, batch-update-findings, workflow status, suppression rule, Security Hub insight, CIS benchmark, PCI DSS, AWS Foundational Security Best Practices, FSBP, Systems Manager Incident Manager, Organizations delegation, control enablement, compliance standard","automate","high","false","capability","Designing auto-remediation for Security Hub findings, wiring EventBridge custom actions to findings, building severity-based remediation routing (Critical\u002FHigh auto-fix, Medium\u002FLow notify), enabling compliance standards (CIS, PCI DSS, FSBP) with automated enforcement, configuring suppression rules for accepted risks, deploying Security Hub insights for remediation tracking, or orchestrating multi-account remediation via Organizations delegated administrator.","true","AUTOMATION_DEPLOYED | REVIEW_REQUIRED","active","Input: either (a) a Security Hub finding type or standard control identifier plus target resource context, OR (b) a remediation requirement. Output: deterministic REMEDIATION block per finding type — FINDING_TYPE\u002FSEVERITY_ROUTE\u002FRUNBOOK\u002FTRIGGER\u002FSAFETY\u002FSUPPRESSION\u002FVERDICT — where VERDICT is AUTOMATION_DEPLOYED (deployment-ready template) or REVIEW_REQUIRED (specific gap cited).","automate Security Hub remediation, Security Hub custom action, EventBridge finding to runbook, severity-based remediation SLA, batch-update-findings workflow status, Security Hub suppression rule, Security Hub insight for tracking, enable CIS PCI FSBP standard, Systems Manager Incident Manager integration, Security Hub multi-account delegation","Agent runtime that reads SKILL.md (Claude Code, Cursor, Windsurf, Codex, Gemini). No AWS CLI required for offline workflow design. Live deployment uses aws securityhub enable-security-hub, update-standards, create-action-target, batch-update-findings, create-insight, aws events put-rule, put-targets, aws ssm start-automation-execution, aws lambda create-function, and aws cloudformation deploy — AWS CLI v2, SSO or key-based credentials.","main","eeace51bd5dd1db2030729d83eeab988861553aa","skills\u002Fsecurityhub-remediation-automator",0,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills","https:\u002F\u002Fgithub.com\u002Fjhkchan","CTO & Co-Founder @Beever-AI  & @votee. CAISP. AWS Community Builder. Organizer@GDGCloudHK. MongoDB Champion. Technopreneur + Infornographer.","2026-09-24 08:54:10",{"source":8,"skillName":5,"commands":52,"prompt":62,"zipAvailable":63},[53,56,59],{"tool":54,"command":55},"npx","npx skills add jhkchan\u002Faws-agent-skills --skill securityhub-remediation-automator",{"tool":57,"command":58},"bunx","bunx skills add jhkchan\u002Faws-agent-skills --skill securityhub-remediation-automator",{"tool":60,"command":61},"pnpm","pnpm dlx skills add jhkchan\u002Faws-agent-skills --skill securityhub-remediation-automator","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fsecurityhub-remediation-automator\u002FSKILL.md",true,[65,71,75,79,83,87,91,95,99,103,107,111,115,119,123,127,131,135,139],{"path":66,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":69,"sourceHtmlUrl":70},"eval\u002Ftest-cases.yaml","REFERENCE","参考文档",6043,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fsecurityhub-remediation-automator\u002Feval\u002Ftest-cases.yaml",{"path":72,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":73,"sourceHtmlUrl":74},"evals\u002Fbaselines\u002Fcritical-s3-auto-remediation.md",921,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fsecurityhub-remediation-automator\u002Fevals\u002Fbaselines\u002Fcritical-s3-auto-remediation.md",{"path":76,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":77,"sourceHtmlUrl":78},"evals\u002Fbaselines\u002Fcustom-finding-no-runbook.md",714,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fsecurityhub-remediation-automator\u002Fevals\u002Fbaselines\u002Fcustom-finding-no-runbook.md",{"path":80,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":81,"sourceHtmlUrl":82},"evals\u002Fbaselines\u002Fhigh-iam-key-revoke.md",682,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fsecurityhub-remediation-automator\u002Fevals\u002Fbaselines\u002Fhigh-iam-key-revoke.md",{"path":84,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":85,"sourceHtmlUrl":86},"evals\u002Fbaselines\u002Fmulti-account-delegation.md",710,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fsecurityhub-remediation-automator\u002Fevals\u002Fbaselines\u002Fmulti-account-delegation.md",{"path":88,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":89,"sourceHtmlUrl":90},"evals\u002Fbaselines\u002Fsuppression-with-expiration.md",588,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fsecurityhub-remediation-automator\u002Fevals\u002Fbaselines\u002Fsuppression-with-expiration.md",{"path":92,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":93,"sourceHtmlUrl":94},"evals\u002Feval_config.yaml",1489,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fsecurityhub-remediation-automator\u002Fevals\u002Feval_config.yaml",{"path":96,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":97,"sourceHtmlUrl":98},"evals\u002Fevals.json",4222,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fsecurityhub-remediation-automator\u002Fevals\u002Fevals.json",{"path":100,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":101,"sourceHtmlUrl":102},"evals\u002Fprompts\u002Fcritical-s3-auto-remediation.md",839,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fsecurityhub-remediation-automator\u002Fevals\u002Fprompts\u002Fcritical-s3-auto-remediation.md",{"path":104,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":105,"sourceHtmlUrl":106},"evals\u002Fprompts\u002Fcustom-finding-no-runbook.md",800,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fsecurityhub-remediation-automator\u002Fevals\u002Fprompts\u002Fcustom-finding-no-runbook.md",{"path":108,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":109,"sourceHtmlUrl":110},"evals\u002Fprompts\u002Fhigh-iam-key-revoke.md",769,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fsecurityhub-remediation-automator\u002Fevals\u002Fprompts\u002Fhigh-iam-key-revoke.md",{"path":112,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":113,"sourceHtmlUrl":114},"evals\u002Fprompts\u002Fmulti-account-delegation.md",747,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fsecurityhub-remediation-automator\u002Fevals\u002Fprompts\u002Fmulti-account-delegation.md",{"path":116,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":117,"sourceHtmlUrl":118},"evals\u002Fprompts\u002Fsuppression-with-expiration.md",729,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fsecurityhub-remediation-automator\u002Fevals\u002Fprompts\u002Fsuppression-with-expiration.md",{"path":120,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":121,"sourceHtmlUrl":122},"examples\u002FREADME.md",3656,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fsecurityhub-remediation-automator\u002Fexamples\u002FREADME.md",{"path":124,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":125,"sourceHtmlUrl":126},"references\u002Fadvanced-patterns.md",6672,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fsecurityhub-remediation-automator\u002Freferences\u002Fadvanced-patterns.md",{"path":128,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":129,"sourceHtmlUrl":130},"references\u002Feventbridge-finding-patterns.md",4701,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fsecurityhub-remediation-automator\u002Freferences\u002Feventbridge-finding-patterns.md",{"path":132,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":133,"sourceHtmlUrl":134},"references\u002Fssm-runbook-templates.md",1806,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fsecurityhub-remediation-automator\u002Freferences\u002Fssm-runbook-templates.md",{"path":136,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":137,"sourceHtmlUrl":138},"references\u002Fworked-examples.md",4310,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fsecurityhub-remediation-automator\u002Freferences\u002Fworked-examples.md",{"path":140,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":141,"sourceHtmlUrl":142},"skill.usf.yaml",4563,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fsecurityhub-remediation-automator\u002Fskill.usf.yaml",[144,151,158,165,172,179],{"skillNo":145,"name":146,"nameZh":6,"description":147,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":148,"categories":149,"keywords":150,"publishedAt":19},"01M7ADVD60X4PCAPKSE58P9NDC","xray-tracing-deployer","Deploys AWS X-Ray distributed tracing with production-grade configuration: X-Ray daemon deployment (EC2 systemd, ECS sidecar, EKS DaemonSet, Lambda built-in), SDK instrumentation (Java, Python, Node.js, Go, .NET) with annotations and metadata, sampling rules (default reservoir + rate vs custom rules with URL \u002F method \u002F service-name predicates), service map generation, trace query and retrieval, groups and insights, CloudWatch ServiceLens integration, IAM permissions (PutTraceSegments, GetSamplingRules), and latest features (Lambda Powertools tracing, OpenTelemetry \u002F ADOT Collector support, W3C trace context). Emits a READY_TO_DEPLOY checklist with every configuration item verified. Use when enabling X-Ray on a new application, adding tracing to ECS \u002F EKS \u002F Lambda, validating a sampling configuration, or generating daemon deployment CLI and IaC templates. Triggers: X-Ray, distributed tracing, X-Ray daemon, sampling rules, service map, X-Ray SDK, OpenTelemetry, ADOT, Lambda Powertools, CloudWatch ServiceLens.","https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fxray-tracing-deployer\u002FSKILL.md",[],[],{"skillNo":152,"name":153,"nameZh":6,"description":154,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":155,"categories":156,"keywords":157,"publishedAt":19},"01M7ADTVJ7DCBM9CB1FY51GH7J","wellarchitected-workload-auditor","Audits AWS Well-Architected Tool workloads for review staleness, per-pillar high-risk issue counts, milestone tracking gaps, and remediation plan completeness. Emits a deterministic verdict (STALE_REVIEW | HIGH_RISK | CONFIG_GAP | OK) per workload with per-pillar risk breakdown, milestone trend analysis, and specific remediation. Use when reviewing Well-Architected workloads, checking WA review freshness, auditing high-risk issues per pillar, validating milestone coverage, or tracking remediation plans.","https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fwellarchitected-workload-auditor\u002FSKILL.md",[],[],{"skillNo":159,"name":160,"nameZh":6,"description":161,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":162,"categories":163,"keywords":164,"publishedAt":19},"01M7ADT59G6FTTNZYHT2QRPNNP","wellarchitected-review-operator","Operates AWS Well-Architected Tool reviews end-to-end — creates workloads, runs pillar reviews (operational excellence, security, reliability, performance, cost optimization, sustainability, Prosperity), answers questions with risk-tier rationale, generates reports and improvement plans, creates milestones, and integrates with Trusted Advisor and Well-Architected Labs. Runs deterministic pre-checks (workload existence, lens availability, pillar coverage), emits the exact update-answer \u002F get-consolidated-report CLI behind a CONFIRM gate, and verifies risk-tier transitions. Emits READY | BLOCKED | COMPLETED. Use when creating a workload, answering pillar questions, generating an improvement plan, creating a milestone, or integrating with Trusted Advisor. Triggers: well-architected tool, well architected review, workload review, pillar, operational excellence, security, reliability, performance, cost optimization, sustainability, prosperity, improvement plan, milestone, trusted advisor.","https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fwellarchitected-review-operator\u002FSKILL.md",[],[],{"skillNo":166,"name":167,"nameZh":6,"description":168,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":169,"categories":170,"keywords":171,"publishedAt":19},"01M7ADSH5JA9QHNPPHQCD7EVA7","wafv2-web-acl-deployer","Provisions AWS WAFv2 Web ACLs with correct production defaults: scope selection (CLOUDFRONT vs REGIONAL), managed rule groups (AWSManagedRulesCommonRuleSet, SQLiRuleSet, LinuxRuleSet, WindowsRuleSet, IPReputationList, BotControlRuleSet, AmazonIpReputationList, ATP), custom rules (byte match, IP set, regex pattern, geo match, size constraint, rate-based), rule priority ordering, logging destinations (Kinesis Firehose, CloudWatch Logs, S3), resource association (ALB, API Gateway, CloudFront), rate-based rules with aggregate keys (IP, forwarded IP), Challenge and CAPTCHA actions, and account takeover prevention. Emits a READY_TO_DEPLOY checklist. Use when creating a Web ACL, attaching managed rules, configuring rate limiting, enabling WAF logging, associating a Web ACL with an ALB\u002FAPI Gateway\u002FCloudFront, or configuring CAPTCHA\u002FChallenge actions. Triggers: create WAF Web ACL, WAFv2, managed rule groups, WAF rate limiting, WAF logging, WAF CAPTCHA, WAF Challenge action, bot control, ATP managed rules.","https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fwafv2-web-acl-deployer\u002FSKILL.md",[],[],{"skillNo":173,"name":174,"nameZh":6,"description":175,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":176,"categories":177,"keywords":178,"publishedAt":19},"01M7ADRYFAT8R73FBNCHRC573X","wafv2-web-acl-auditor","Audits AWS WAFv2 Web ACL configurations to determine whether the ACL provides effective protection: default-action posture (Allow vs Block), managed-rule-group coverage gaps, rule effectiveness (BLOCK vs COUNT, shadow\u002Fbypass rules, stale exclusions), rate-based rule correctness, logging and visibility configuration, and text-transformation bypass vectors. Emits a deterministic verdict per Web ACL. Use when reviewing a WAFv2 Web ACL for security posture, checking managed-rule coverage, validating rate-limit configuration, auditing WAF logging, or hardening a WAF before production deployment. Triggers: WAF, WAFv2, Web ACL, managed rule group, AWSManagedRules, rate-based rule, CAPTCHA, Challenge, OverrideAction, Count mode, forwarded IP, Bot Control, ATP, text transformation, WAF logging, WAF visibility, OWASP, SQLi, XSS, RFI.","https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fwafv2-web-acl-auditor\u002FSKILL.md",[],[],{"skillNo":180,"name":181,"nameZh":6,"description":182,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":183,"categories":184,"keywords":185,"publishedAt":19},"01M7ADR8W7G72JX4KFGN03QK8Q","waf-rule-deployer","Provisions AWS WAFv2 rule sets with production defaults: Web ACL creation (CloudFront scope in us-east-1 vs Regional scope), rule groups (managed vs custom) with capacity planning in WCU (Web ACL Capacity Units, 1500 default per ACL), managed rule groups (AWSManagedRulesCommonRuleSet, AWSManagedRulesSQLiRuleSet, AWSManagedRulesAmazonIpReputationList, AWSManagedRulesLinuxRuleSet, AWSManagedRulesWindowsRuleSet, AWSManagedRulesUnixRuleSet), custom rules (byte-match, regex pattern set, geo-match, rate-based), IP set and regex pattern set resources, rule priority ordering (lowest number evaluated first), action types (allow, block, count, CAPTCHA, Challenge), bot control managed rule group, account takeover. Triggers: create WAF rule, WAF managed rule group, WAF custom rule, WAF byte match, WAF geo match, WAF rate based rule, WAF IP set, WAF regex pattern set, WAF WCU budget, WAF CloudFront ACL, WAF logging Kinesis Firehose, WAF bot control, WAF ATP, WAF label matching, WAF Challenge action, WAF CAPTCHA.","https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fwaf-rule-deployer\u002FSKILL.md",[],[]]