[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7ACAQ003TSXHKZ2XFNPBVSH":3,"skill-same:01M7ACAQ003TSXHKZ2XFNPBVSH":145},{"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":38,"commitSha":39,"skillDirectory":40,"forksCount":41,"repositoryHtmlUrl":42,"repositoryHomepageUrl":6,"ownerHtmlUrl":43,"ownerBlogUrl":6,"ownerDescription":44,"updatedAt":45,"install":46,"resources":59},"01M7ACAQ003TSXHKZ2XFNPBVSH","securityhub-control-compliance-auditor",null,"Audits AWS Security Hub control compliance findings and maps each to a deterministic compliance verdict (FAILED | WARNING | PASSED | NOT_APPLICABLE), then maps every FAILED \u002F WARNING control to a specific fix action. Handles the full Security Hub finding lifecycle — active findings, suppressed findings, resolved-but-still-failing, archived findings, NOT_AVAILABLE with StatusReasons, multi-account aggregation, and cross-standard control families (FSBP, CIS, PCI-DSS, NIST 800-53). Use when reviewing Security Hub control status, triaging a compliance gap report, mapping findings to remediation runbooks, or preparing for an audit \u002F executive compliance summary.","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-control-compliance-auditor\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: securityhub-control-compliance-auditor\ndescription: Audits AWS Security Hub control compliance findings and maps each to a deterministic compliance verdict (FAILED | WARNING | PASSED | NOT_APPLICABLE), then maps every FAILED \u002F WARNING control to a specific fix action. Handles the full Security Hub finding lifecycle — active findings, suppressed findings, resolved-but-still-failing, archived findings, NOT_AVAILABLE with StatusReasons, multi-account aggregation, and cross-standard control families (FSBP, CIS, PCI-DSS, NIST 800-53). Use when reviewing Security Hub control status, triaging a compliance gap report, mapping findings to remediation runbooks, or preparing for an audit \u002F executive compliance summary.\nlicense: Apache-2.0\ncompatibility: Agent runtime that reads SKILL.md (Claude Code, Cursor, Windsurf, Codex, Gemini). No AWS CLI required for offline classification — the skill reasons over provided Security Hub finding JSON (ASFF). For live-account audits, AWS CLI v2 with securityhub access (ListEnabledStandards, GetEnabledStandards, GetFindings, batch-update-findings) and SSO or key-based credentials.\nmetadata:\n  domain: aws-cloudops\n  complexity: high\n  requires_llm: 'true'\n  phase: '2'\n  supports_pipeline: 'true'\n  entry_point: 'false'\n  family: Security\n  verdict_shape: FAILED | WARNING | PASSED | NOT_APPLICABLE\n  when_to_use: Reviewing Security Hub control compliance status, triaging a compliance gap report, mapping findings to remediation actions, auditing finding lifecycle states (suppressed \u002F resolved \u002F archived), preparing for a compliance audit, or generating an executive compliance summary across FSBP \u002F CIS \u002F PCI-DSS \u002F NIST standards.\n  version: 0.2.0\n  author: Jacky Chan — AWS Community Builder\n  keywords: Security Hub, compliance, control status, FSBP, Foundational Security Best Practices, CIS Benchmark, PCI-DSS, NIST 800-53, ASFF, finding lifecycle, suppression, remediation runbook, compliance verdict, NOT_AVAILABLE, StatusReasons, Workflow Status, Record State, delegated administrator\n  tags: aws, securityhub, security, compliance, fsbp, cis, pci-dss, nist, audit, remediation, asff\n---\n\n# Security Hub Control-Compliance Auditor\n\n> **Structural pattern:** ASFF Audit Pipeline — Activation → Output Contract →\n> Mindset → Decision Tree → Process Steps → Reference Tables → Anti-Patterns →\n> Safety Checks. Read top-to-bottom for a cold start; jump to the Decision Tree\n> for a single finding.\n\n## Quick Start (the 3 rules that prevent 80% of misclassifications)\n\n1. **NOT_AVAILABLE is NOT the same as NOT_APPLICABLE.** Check\n   `StatusReasons[].Code`: `NO_RESOURCES`\u002F`DISABLED_CONTROL` →\n   NOT_APPLICABLE; everything else (especially\n   `SUPPORTED_SERVICE_NOT_ENABLED`) → WARNING.\n2. **SUPPRESSED + FAILED is WARNING, never PASSED.** Suppression hides the\n   finding but the control is still failing.\n3. **ARCHIVED is always NOT_APPLICABLE.** The resource was deleted or the\n   control superseded — historical state, not current posture.\n\nFull classification: see Decision Tree below. Detailed reasoning: see\nProcess steps. Fix actions: see Control-to-fix-action mapping.\n\n## Activation\n\n> Moved to [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md#activation).\n> Four ASFF detection signals and the do-NOT-invoke exclusions (CloudTrail events, bare IAM policy JSON, Audit Manager, Config compliance JSON).\n\n## Output Contract (CRITICAL — read before any classification)\n\nEvery finding MUST produce this EXACT output block. An agent that omits\nany field fails the audit. Copy this template verbatim and fill the\nplaceholders:\n\n```text\nCONTROL: \u003CControlId from GeneratorId, e.g. S3.2>\nVERDICT: \u003CFAILED | WARNING | PASSED | NOT_APPLICABLE>\nREASON: \u003CRule number + the specific field values that drove the verdict.\nMUST cite Compliance.Status, Workflow.Status, RecordState, and StatusReasons\ncode if applicable. For SUPPRESSED findings, MUST include whether a Workflow\nNote is present and its content or absence. 1-2 sentences.>\nSEVERITY: \u003CCRITICAL | HIGH | MEDIUM | LOW | INFORMATIONAL>\nREMEDIATION: \u003CSpecific fix action from the control-to-fix-action table, or\n\"None required — control is compliant\" for PASSED, or\n\"None required — control does not apply\" for NOT_APPLICABLE.>\n```\n\nRules for filling the template:\n- ALWAYS include ALL FIVE headers (`CONTROL`, `VERDICT`, `REASON`, `SEVERITY`,\n  `REMEDIATION`) even when the finding is PASSED or NOT_APPLICABLE — a blank\n  `REMEDIATION: None required` is correct, but omitting the header is a\n  contract violation.\n- The `VERDICT` value must be ONE of exactly four tokens: `FAILED`,\n  `WARNING`, `PASSED`, `NOT_APPLICABLE`. Never output compound statuses like\n  `WARNING (PENDING)` or `NOT_APPLICABLE\u002FARCHIVED`.\n- For SUPPRESSED findings, the REASON field MUST mention the suppression\n  context: whether `Workflow.Note` is present, its author\u002Fdate, or explicitly\n  state \"Suppression has no documented justification.\" Omitting the\n  suppression context from a SUPPRESSED finding is a contract violation.\n- Never prefix the block with conversational text (\"Sure, here is the\n  audit...\") or disclaimers (\"I cannot access...\"). Start directly with\n  `CONTROL:`.\n\n## Mindset\n\n> Moved to [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md#mindset).\n> Four overlapping finding states, read in dashboard-triage order, reflect current real-world posture rather than the raw status string.\n\n## Decision Tree (classification flow)\n\nApply top-to-bottom. First matching rule wins.\n\n```\nSTART\n  │\n  ├─ Compliance block missing? ───────────────► NOT_APPLICABLE (integration finding)\n  │\n  ├─ RecordState = ARCHIVED? ─────────────────► NOT_APPLICABLE (stale)\n  │\n  ├─ Workflow.Status = SUPPRESSED + FAILED? ──► WARNING (governance flag)\n  │\n  ├─ Workflow.Status = RESOLVED + FAILED? ────► WARNING (>48h → FAILED)\n  │\n  ├─ Compliance.Status = NOT_AVAILABLE?\n  │    ├─ NO_RESOURCES \u002F DISABLED_CONTROL ────► NOT_APPLICABLE\n  │    ├─ UNSUPPORTED_INSTANCE_TYPE ─────────► NOT_APPLICABLE\n  │    ├─ SUPPORTED_SERVICE_NOT_ENABLED ──────► WARNING (Config gap)\n  │    ├─ ASSUME_ROLE_ERROR \u002F PERMISSION_DENIED► WARNING\n  │    ├─ CONFIG_RETURNS_UNKNOWN ─────────────► WARNING\n  │    ├─ ASSESSMENT_FAILED ──────────────────► WARNING\n  │    ├─ SECURITY_HUB_NOT_ENABLED_IN_REGION ─► WARNING\n  │    └─ empty \u002F absent ─────────────────────► WARNING (ambiguous)\n  │\n  ├─ Compliance.Status = FAILED? ─────────────► FAILED\n  ├─ Compliance.Status = WARNING? ────────────► WARNING\n  ├─ Compliance.Status = PASSED? ─────────────► PASSED\n  │\n  └─ (unrecognized status) ───────────────────► WARNING + \"unrecognized Compliance.Status\"\n```\n\n**Two rules that cause the most misclassifications — always double-check:**\n- `NOT_AVAILABLE` + `SUPPORTED_SERVICE_NOT_ENABLED` = **WARNING** (not\n  NOT_APPLICABLE — Config being disabled is a monitoring gap).\n- `SUPPRESSED` + `FAILED` = **WARNING** (not PASSED — suppression hides but\n  does not fix).\n\n## Process — Classification logic (reference for each step)\n\n### Step 0 — Validate input, detect edge cases\n\nVerify the input is an ASFF record. Edge cases to handle before\nclassification:\n\n**Malformed JSON:** If the finding JSON cannot be parsed, output:\n\n> Moved to [references\u002Ferror-handling.md](references\u002Ferror-handling.md#step-0--malformed-json-error-emit-block).\n> WARNING emit template for unparseable finding JSON (GetFindings re-fetch, support case for the source integration).\n\n**Missing Compliance block:** If the `Compliance` key is absent entirely,\nthe finding is an **integration finding** (GuardDuty, Inspector, Macie,\nDetective, Firewall Manager) or a custom product finding. It is a security\nevent, not a control compliance evaluation:\n\n> Moved to [references\u002Ferror-handling.md](references\u002Ferror-handling.md#step-0--missing-compliance-block-emit).\n> NOT_APPLICABLE emit template for integration findings (GuardDuty, Inspector, Macie, Detective, Firewall Manager) and custom products.\n\n\n**Malformed ARN fields:** If the finding `Id` or `Resources[].Id` does not\nmatch the AWS ARN pattern\n`arn:aws:[a-z0-9-]+:[a-z]{2}-[a-z]+-\\d:\\d{12}:.*`, append:\n\n> Moved to [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md#step-0--malformed-arn-data_quality-flag).\n> DATA_QUALITY flag for finding Id \u002F Resources[].Id not matching the AWS ARN pattern (does not change the verdict).\n\n\n**Field-defaulting rules (apply when a field is absent but non-fatal):**\n\n> Moved to [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md#step-0--field-defaulting-rules).\n> Defaults: StatusReasons-missing-on-NOT_AVAILABLE → WARNING (never NOT_APPLICABLE), RecordState → ACTIVE, Workflow → NEW, UpdatedAt-absent → STALE_FLAG, Severity → MEDIUM.\n\n### Step 1 — RecordState = ARCHIVED → NOT_APPLICABLE (stale)\n\nSecurity Hub archives findings when the resource was deleted, the control was\ndisabled, or the finding was superseded by a newer one. An archived finding\nrepresents a **historical** state. If `RecordState = ARCHIVED`, emit\n**NOT_APPLICABLE** regardless of `Compliance.Status`.\n\nCite \"Rule 1: archived — resource deleted or control superseded\".\n\n\n> Moved to [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md#step-1--freshness-guard).\n> STALE_FLAG when UpdatedAt is >30 days old even on ACTIVE findings (delegated-admin removal, control re-enable).\n\n\n### Step 2 — Suppressed failure → WARNING (governance flag)\n\nIf `Workflow.Status = SUPPRESSED` AND `Compliance.Status = FAILED`, emit\n**WARNING**. This is the single most misunderstood Security Hub state.\nSuppression hides the finding from the default dashboard view, but **the\ncontrol is still failing**. Suppression is an operational triage decision\n(accepted risk, compensating control, false positive), not a remediation.\n\nCite \"Rule 2: suppressed FAILED — governance concern\". Always include in the\nREASON whether the suppression has a `Note`:\n\n- If `Workflow.Note` is present, cite it (e.g., \"Suppressed by\n  securityops@example.com on 2026-06-15: 'Accepted risk — compensating\n  control via WAF rule arn:aws:wafv2:...'\").\n- If no `Note`, flag: \"Suppression has no documented justification — review\n  whether the suppression is still valid.\"\n- Security Hub does not natively expire suppressions. A suppression created\n  months ago for a temporary exception may still be hiding a failing control.\n\n\n> Moved to [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md#step-2--suppression-lifecycle-heuristic).\n> No suppression TTL — validity heuristic by age and Note presence (\u003C30d valid, 30-90d review, >90d stale, no-Note suspect).\n\n### Step 3 — Resolved but still FAILED → WARNING (pending re-evaluation)\n\nIf `Workflow.Status = RESOLVED` AND `Compliance.Status = FAILED`, emit\n**WARNING**. The operator marked the finding resolved (remediation applied),\nbut Security Hub has not yet re-evaluated the control.\n\nSecurity Hub re-runs control checks every **12 to 24 hours** (the Config rule\nevaluation trigger determines the exact interval — see Config-rule evaluation\ntriggers reference). If the finding was marked `RESOLVED` more than 48 hours\nago and is still `FAILED`, the remediation likely **failed** — escalate to\n**FAILED** and note: \"Resolution marked >48h ago but control still FAILED —\nremediation likely incomplete. Re-investigate the resource directly.\"\n\n\n### Step 4 — NOT_AVAILABLE → split by StatusReasons\n\n`Compliance.Status = NOT_AVAILABLE` means Security Hub **could not produce a\ndefinitive PASSED\u002FFAILED**. The reason matters — it splits into two verdicts:\n\n**NOT_APPLICABLE** (control genuinely does not apply):\n- `NO_RESOURCES` — zero resources in scope. Example: Redshift.1 with no\n  Redshift clusters.\n- `DISABLED_CONTROL` — control disabled by the delegated administrator (or\n  via Security Hub Central Configuration).\n- `UNSUPPORTED_INSTANCE_TYPE` — resource exists but the control does not\n  evaluate this variant.\n\n**WARNING** (Security Hub tried and failed — needs investigation):\n- `SUPPORTED_SERVICE_NOT_ENABLED` — AWS Config not enabled in the region. The\n  control cannot run — a monitoring posture misconfiguration, not a pass.\n- `CONFIG_RETURNS_UNKNOWN` — Config rule returned UNKNOWN (transient error or\n  permissions issue with the Config service-linked role).\n- `ASSESSMENT_FAILED` — assessment threw an error. Often transient but may\n  indicate systemic problems (permissions, throttling).\n- `ASSUME_ROLE_ERROR` or `PERMISSION_DENIED` — service-linked role lacks\n  permissions to evaluate the resource.\n- `SECURITY_HUB_NOT_ENABLED_IN_REGION` — Hub disabled in the region.\n- `CANNOT_ENABLE_RECORDS` — cannot enable Config recording.\n- `UNKNOWN_CONTROL_STATUS` — undetermined, investigate.\n- StatusReasons empty or absent → WARNING: \"NOT_AVAILABLE with no\n  StatusReasons — investigate manually.\"\n\n\n> Moved to [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md#step-4--full-statusreason-code-reference).\n> Complete StatusReason code → verdict → meaning table (NO_RESOURCES through UNKNOWN_CONTROL_STATUS).\n\nCite \"Rule 4: NOT_AVAILABLE — \u003Ccode>\".\n\n### Step 5 — Compliance.Status = FAILED → FAILED\n\n`RecordState = ACTIVE`, `Workflow.Status ∈ {NEW, NOTIFIED}`,\n`Compliance.Status = FAILED`. The control is currently failing and has not\nbeen triaged. Emit **FAILED**.\n\nCite \"Rule 5: active FAILED — control is non-compliant\". Map to the\nfix-action table for the specific remediation.\n\n### Step 6 — Compliance.Status = WARNING → WARNING\n\nSecurity Hub uses `WARNING` for partially compliant controls or informational\nconcerns. Example: a CloudTrail trail exists but log validation is disabled.\nEmit **WARNING**.\n\nCite \"Rule 6: WARNING — partial compliance or informational concern\".\n\n### Step 7 — Compliance.Status = PASSED → PASSED\n\n`Compliance.Status = PASSED` AND `RecordState = ACTIVE`. The resource is\nfully compliant. Emit **PASSED** with `REMEDIATION: None required — control\nis compliant`.\n\n### Step 8 — Aggregation (multi-finding rollup)\n\nWhen auditing multiple findings for the same control across resources, or\nmultiple controls across an account, the aggregate verdict is the **worst\nverdict**:\n\n```\nFAILED > WARNING > PASSED > NOT_APPLICABLE\n```\n\nReport the count of each verdict in the aggregate:\n```text\nCONTROL: \u003CControlId>\nAGGREGATE VERDICT: FAILED\nBREAKDOWN: 3 FAILED, 1 WARNING, 12 PASSED, 2 NOT_APPLICABLE (across 18 resources)\n```\n\n## Severity escalation matrix\n\n> Moved to [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md#severity-escalation-matrix).\n> Verdict × severity priority\u002FSLA table, cross-standard severity rule, and blast-radius escalation (aggregate N>10, time-decay >90d, trust-boundary → P0).\n\n## Config-rule evaluation triggers (expert reference)\n\n> Moved to [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md#config-rule-evaluation-triggers-expert-reference).\n> Config-change vs periodic trigger families per control, 5-30 min vs 6-24h re-evaluation windows, describe-config-rules verification.\n\n## Security Hub internals (non-obvious operational knowledge)\n\n> Moved to [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md#security-hub-internals-non-obvious-operational-knowledge).\n> Dedup composite key, BatchUpdateFindings race, Config backlog delays, ingestion latency stages, automation-rule silent suppression, control enablement cost model.\n\n## Finding correlation and root-cause grouping\n\n> Moved to [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md#finding-correlation-and-root-cause-grouping).\n> Root-cause grouping rules (S3 BPA fan-in, account-policy gaps, Config-disabled clusters, cross-standard duplicates).\n\n## Coverage assessment heuristic\n\n> Moved to [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md#coverage-assessment-heuristic).\n> coverage_score formula and 90% \u002F 70% operational benchmarks.\n\n## Control-to-fix-action mapping\n\n> Moved to [references\u002Fremediation-guidance.md](references\u002Fremediation-guidance.md#control-to-fix-action-mapping).\n> FSBP (S3, IAM, CloudTrail, Config, EC2, KMS, RDS, Lambda), CIS v1.2-v2.0, and PCI\u002FNIST control → fix action → CLI tables.\n\n## Multi-account aggregation (Organizations)\n\n> Moved to [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md#multi-account-aggregation-organizations).\n> Delegated-admin aggregation, enrolled-but-not-enabled WARNING, FindingAggregator cross-region propagation, ASSUME_ROLE_ERROR root cause and fix.\n\n## Custom controls and non-standard findings\n\n> Moved to [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md#custom-controls-and-non-standard-findings).\n> Custom control remediation lookup chain (Description\u002FRemediationUrl → ASFF Remediation fields → resource-type derivation) and automation-rule detection.\n\n## Output format — worked examples\n\n### Multi-finding report\n\n```text\nCONTROL: S3.2 (S3 Bucket-Level Public Access Prohibition)\nVERDICT: FAILED\nREASON: Rule 5 (active FAILED) — Compliance.Status is FAILED,\nWorkflow.Status is NEW, RecordState is ACTIVE. Bucket app-uploads-prod\ndoes not have bucket-level BPA enabled.\nSEVERITY: HIGH\nREMEDIATION: Enable all 4 bucket-level BPA settings on app-uploads-prod:\naws s3api put-public-access-block --bucket app-uploads-prod\n  --public-access-block-configuration\n    BlockPublicAcls=true,IgnorePublicAcls=true,\n    BlockPublicPolicy=true,RestrictPublicBuckets=true\n\nCONTROL: IAM.7 (IAM Password Policy)\nVERDICT: PASSED\nREASON: Rule 7 (PASSED) — Compliance.Status is PASSED, RecordState is ACTIVE.\nPassword policy meets all FSBP requirements.\nSEVERITY: MEDIUM\nREMEDIATION: None required — control is compliant.\n\nCONTROL: Redshift.1 (Redshift Clusters Public Access)\nVERDICT: NOT_APPLICABLE\nREASON: Rule 4 (NOT_AVAILABLE — NO_RESOURCES) — Compliance.Status is\nNOT_AVAILABLE with StatusReasons code NO_RESOURCES. No Redshift clusters\nexist in this account\u002Fregion.\nSEVERITY: MEDIUM\nREMEDIATION: None required — control does not apply.\n\nCONTROL: Config.1 (AWS Config Enabled)\nVERDICT: WARNING\nREASON: Rule 4 (NOT_AVAILABLE — SUPPORTED_SERVICE_NOT_ENABLED) —\nCompliance.Status is NOT_AVAILABLE with StatusReasons code\nSUPPORTED_SERVICE_NOT_ENABLED. AWS Config is not enabled in eu-west-2,\nso this control cannot evaluate. This is a monitoring gap, not a pass.\nSEVERITY: MEDIUM\nREMEDIATION: Enable AWS Config in eu-west-2:\naws configservice put-configuration-recorder\n  --configuration-recorder name=default,roleARN=\u003Crole>\n  --recording-group allSupported=true,includeGlobalResourceTypes=true\n```\n\n## NEVER (anti-patterns)\n\n- NEVER pass through `Compliance.Status = NOT_AVAILABLE` as NOT_APPLICABLE\n  without checking `StatusReasons`. `NO_RESOURCES` means the control does not\n  apply (NOT_APPLICABLE), but `SUPPORTED_SERVICE_NOT_ENABLED` means Config is\n  off — a monitoring posture gap that is a WARNING. Treating the latter as\n  NOT_APPLICABLE hides a misconfiguration that makes the entire compliance\n  posture unreliable.\n\n- NEVER treat a SUPPRESSED finding as PASSED. `Workflow.Status = SUPPRESSED`\n  means someone hid the finding from the default view. If\n  `Compliance.Status = FAILED`, the control is still failing — the verdict is\n  WARNING. Suppression is a triage decision, not a remediation.\n\n- NEVER treat `Workflow.Status = RESOLVED` as evidence that the resource is\n  now compliant. RESOLVED is an operator assertion. Security Hub re-evaluates\n  on its own schedule. If still `FAILED` after 48h (or 1h for config-change\n  controls), the fix failed.\n\n- NEVER classify an ARCHIVED finding as FAILED. `RecordState = ARCHIVED` means\n  the resource was deleted or the control superseded. The verdict is\n  NOT_APPLICABLE.\n\n- NEVER ignore `FirstObservedAt` \u002F `UpdatedAt` timestamps. A `FAILED` finding\n  open for 180 days is a different operational concern than one opened\n  yesterday. Age compounds risk — escalate for findings > 90 days old.\n\n- NEVER classify an integration finding (GuardDuty, Inspector, Macie,\n  Detective, Firewall Manager) as a control compliance verdict. These lack a\n  `Compliance` block — they are security events. Route them to the\n  appropriate detector skill.\n\n- NEVER assume a single region's findings represent global compliance.\n  Security Hub is regional. A finding for `us-east-1` says nothing about\n  `eu-west-1`. Always check the `Region` field. In multi-region accounts, the\n  delegated administrator must aggregate via `FindingAggregator`.\n\n- NEVER recommend disabling a Security Hub control as the fix for a FAILED\n  finding. Disabling removes visibility — it trades FAILED for\n  NOT_APPLICABLE without fixing the resource. The only legitimate reason to\n  disable is a confirmed false-positive.\n\n- NEVER aggregate findings by severity alone without considering blast radius.\n  A `MEDIUM` FAILED on an IAM role with cross-account trust is more dangerous\n  than ten `HIGH` findings on isolated dev resources.\n\n- NEVER assume `Severity.Label` is the final priority. The aggregate (N > 10)\n  and time-decay (> 90 days) escalation rules override the label — a `MEDIUM`\n  FAILED on 50 resources for 6 months is effectively P1.\n\n- NEVER batch-update finding workflow status to RESOLVED without confirming\n  the resource is actually fixed. If the resource is still non-compliant,\n  Security Hub re-opens the finding on the next cycle.\n\n- NEVER trust ARN fields blindly. A finding `Resources[].Id` that does not\n  match the AWS ARN pattern\n  (`arn:aws:[service]:[region]:[account]:[resource]`) indicates either a\n  malformed ASFF payload or a non-AWS resource incorrectly ingested. Flag\n  the data-quality issue and verify the finding source before acting on the\n  remediation. Malformed ARNs cause downstream failures in any CLI command\n  that takes `--resource-arn` or `--bucket` parameters.\n\n- NEVER assume cross-account Security Hub findings are actionable from the\n  administrator account. The delegated administrator can SEE findings from\n  member accounts but may not have permission to MODIFY the underlying\n  resources. A control backed by a Config rule that assumes\n  `AWSServiceRoleForSecurityHub` in the member account will show\n  `ASSUME_ROLE_ERROR` if that role's trust policy is broken or the member\n  account was enrolled without enabling Security Hub. This is a WARNING — the\n  role trust must be fixed before the control can evaluate.\n\n- NEVER call `BatchUpdateFindings` with more than 100 finding identifiers.\n  The API rejects batches over 100 with `InvalidInputException`. Chunk into\n  groups of 100 or fewer.\n\n- NEVER apply remediation commands in a tight loop without exponential\n  backoff. Config rule evaluations and Security Hub API calls share a rate\n  limit. A burst across 50 resources can trigger `ThrottlingException` and\n  leave some unremediated silently.\n\n- NEVER attempt to update `Compliance.Status` via `BatchUpdateFindings` — it\n  is a system-managed field. Only `Workflow.Status`, `RecordState`, `Note`,\n  and `Severity` are user-updatable. Trying to set `Compliance.Status`\n  returns `InvalidInputException`.\n\n## API and CLI constraints\n\n> Moved to [references\u002Ferror-handling.md](references\u002Ferror-handling.md#api-and-cli-constraints).\n> Pagination and batch limits (100 findings, 4 KB Note), throttling\u002Fbackoff, eventual consistency, CLI failure recovery (InvalidInputException, AccessDenied, NoSuchBucket).\n\n## Pre-flight safety checks (run before any remediation)\n\n> Moved to [references\u002Fdiagnostic-commands.md](references\u002Fdiagnostic-commands.md#pre-flight-safety-checks-run-before-any-remediation).\n> Dry-run mode for batch remediation, resource-existence probes per service, rollback state capture, region\u002Fdelegated-admin verification, trust-boundary incident handling, permission-fallback escalation.\n\n## Remediation guidance\n\n> Moved to [references\u002Fremediation-guidance.md](references\u002Fremediation-guidance.md#remediation-guidance).\n> FAILED playbook (map → pre-flight → fix → RESOLVED → await re-evaluation), WARNING playbook (suppression review\u002Funsuppress, resolved-pending, Config gap), NOT_APPLICABLE disposition.\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> Central configuration, Automated Security Response on AWS, control lifecycle updates, Audit Manager integration.\n\n## References (load on demand)\n\n- [advanced-patterns](references\u002Fadvanced-patterns.md) — Activation triggers, Mindset, Step 0-4 detail prose, severity escalation matrix, Config-rule triggers, Security Hub internals, correlation, coverage heuristic, multi-account aggregation, custom controls, recent AWS features\n- [diagnostic-commands](references\u002Fdiagnostic-commands.md) — pre-flight safety checks (dry-run, existence probes, rollback capture)\n- [error-handling](references\u002Ferror-handling.md) — malformed-input emit blocks and API\u002FCLI constraints with failure recovery\n- [remediation-guidance](references\u002Fremediation-guidance.md) — control-to-fix-action mapping tables and per-verdict remediation playbooks\n\n## Domain\n\nAWS CloudOps \u002F Security Hub Compliance & Posture Management.\n\n## AWS documentation\n\n- **AWS Security Hub User Guide** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fsecurityhub\u002Flatest\u002Fuserguide\u002Fwhat-is-securityhub.html\n- **Security Hub Security** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fsecurityhub\u002Flatest\u002Fuserguide\u002Fsecurity.html\n- **Security Hub API Reference** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fsecurityhub\u002F1.0\u002FAPIReference\u002F\n- **Security Hub CLI Reference** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fcli\u002Flatest\u002Freference\u002Fsecurityhub\u002F\n- **Central configuration** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fsecurityhub\u002Flatest\u002Fuserguide\u002Fcentral-configuration.html\n","# Security Hub Control-Compliance Auditor\n\n> **Structural pattern:** ASFF Audit Pipeline — Activation → Output Contract →\n> Mindset → Decision Tree → Process Steps → Reference Tables → Anti-Patterns →\n> Safety Checks. Read top-to-bottom for a cold start; jump to the Decision Tree\n> for a single finding.\n\n## Quick Start (the 3 rules that prevent 80% of misclassifications)\n\n1. **NOT_AVAILABLE is NOT the same as NOT_APPLICABLE.** Check\n   `StatusReasons[].Code`: `NO_RESOURCES`\u002F`DISABLED_CONTROL` →\n   NOT_APPLICABLE; everything else (especially\n   `SUPPORTED_SERVICE_NOT_ENABLED`) → WARNING.\n2. **SUPPRESSED + FAILED is WARNING, never PASSED.** Suppression hides the\n   finding but the control is still failing.\n3. **ARCHIVED is always NOT_APPLICABLE.** The resource was deleted or the\n   control superseded — historical state, not current posture.\n\nFull classification: see Decision Tree below. Detailed reasoning: see\nProcess steps. Fix actions: see Control-to-fix-action mapping.\n\n## Activation\n\n> Moved to [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md#activation).\n> Four ASFF detection signals and the do-NOT-invoke exclusions (CloudTrail events, bare IAM policy JSON, Audit Manager, Config compliance JSON).\n\n## Output Contract (CRITICAL — read before any classification)\n\nEvery finding MUST produce this EXACT output block. An agent that omits\nany field fails the audit. Copy this template verbatim and fill the\nplaceholders:\n\n```text\nCONTROL: \u003CControlId from GeneratorId, e.g. S3.2>\nVERDICT: \u003CFAILED | WARNING | PASSED | NOT_APPLICABLE>\nREASON: \u003CRule number + the specific field values that drove the verdict.\nMUST cite Compliance.Status, Workflow.Status, RecordState, and StatusReasons\ncode if applicable. For SUPPRESSED findings, MUST include whether a Workflow\nNote is present and its content or absence. 1-2 sentences.>\nSEVERITY: \u003CCRITICAL | HIGH | MEDIUM | LOW | INFORMATIONAL>\nREMEDIATION: \u003CSpecific fix action from the control-to-fix-action table, or\n\"None required — control is compliant\" for PASSED, or\n\"None required — control does not apply\" for NOT_APPLICABLE.>\n```\n\nRules for filling the template:\n- ALWAYS include ALL FIVE headers (`CONTROL`, `VERDICT`, `REASON`, `SEVERITY`,\n  `REMEDIATION`) even when the finding is PASSED or NOT_APPLICABLE — a blank\n  `REMEDIATION: None required` is correct, but omitting the header is a\n  contract violation.\n- The `VERDICT` value must be ONE of exactly four tokens: `FAILED`,\n  `WARNING`, `PASSED`, `NOT_APPLICABLE`. Never output compound statuses like\n  `WARNING (PENDING)` or `NOT_APPLICABLE\u002FARCHIVED`.\n- For SUPPRESSED findings, the REASON field MUST mention the suppression\n  context: whether `Workflow.Note` is present, its author\u002Fdate, or explicitly\n  state \"Suppression has no documented justification.\" Omitting the\n  suppression context from a SUPPRESSED finding is a contract violation.\n- Never prefix the block with conversational text (\"Sure, here is the\n  audit...\") or disclaimers (\"I cannot access...\"). Start directly with\n  `CONTROL:`.\n\n## Mindset\n\n> Moved to [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md#mindset).\n> Four overlapping finding states, read in dashboard-triage order, reflect current real-world posture rather than the raw status string.\n\n## Decision Tree (classification flow)\n\nApply top-to-bottom. First matching rule wins.\n\n```\nSTART\n  │\n  ├─ Compliance block missing? ───────────────► NOT_APPLICABLE (integration finding)\n  │\n  ├─ RecordState = ARCHIVED? ─────────────────► NOT_APPLICABLE (stale)\n  │\n  ├─ Workflow.Status = SUPPRESSED + FAILED? ──► WARNING (governance flag)\n  │\n  ├─ Workflow.Status = RESOLVED + FAILED? ────► WARNING (>48h → FAILED)\n  │\n  ├─ Compliance.Status = NOT_AVAILABLE?\n  │    ├─ NO_RESOURCES \u002F DISABLED_CONTROL ────► NOT_APPLICABLE\n  │    ├─ UNSUPPORTED_INSTANCE_TYPE ─────────► NOT_APPLICABLE\n  │    ├─ SUPPORTED_SERVICE_NOT_ENABLED ──────► WARNING (Config gap)\n  │    ├─ ASSUME_ROLE_ERROR \u002F PERMISSION_DENIED► WARNING\n  │    ├─ CONFIG_RETURNS_UNKNOWN ─────────────► WARNING\n  │    ├─ ASSESSMENT_FAILED ──────────────────► WARNING\n  │    ├─ SECURITY_HUB_NOT_ENABLED_IN_REGION ─► WARNING\n  │    └─ empty \u002F absent ─────────────────────► WARNING (ambiguous)\n  │\n  ├─ Compliance.Status = FAILED? ─────────────► FAILED\n  ├─ Compliance.Status = WARNING? ────────────► WARNING\n  ├─ Compliance.Status = PASSED? ─────────────► PASSED\n  │\n  └─ (unrecognized status) ───────────────────► WARNING + \"unrecognized Compliance.Status\"\n```\n\n**Two rules that cause the most misclassifications — always double-check:**\n- `NOT_AVAILABLE` + `SUPPORTED_SERVICE_NOT_ENABLED` = **WARNING** (not\n  NOT_APPLICABLE — Config being disabled is a monitoring gap).\n- `SUPPRESSED` + `FAILED` = **WARNING** (not PASSED — suppression hides but\n  does not fix).\n\n## Process — Classification logic (reference for each step)\n\n### Step 0 — Validate input, detect edge cases\n\nVerify the input is an ASFF record. Edge cases to handle before\nclassification:\n\n**Malformed JSON:** If the finding JSON cannot be parsed, output:\n\n> Moved to [references\u002Ferror-handling.md](references\u002Ferror-handling.md#step-0--malformed-json-error-emit-block).\n> WARNING emit template for unparseable finding JSON (GetFindings re-fetch, support case for the source integration).\n\n**Missing Compliance block:** If the `Compliance` key is absent entirely,\nthe finding is an **integration finding** (GuardDuty, Inspector, Macie,\nDetective, Firewall Manager) or a custom product finding. It is a security\nevent, not a control compliance evaluation:\n\n> Moved to [references\u002Ferror-handling.md](references\u002Ferror-handling.md#step-0--missing-compliance-block-emit).\n> NOT_APPLICABLE emit template for integration findings (GuardDuty, Inspector, Macie, Detective, Firewall Manager) and custom products.\n\n\n**Malformed ARN fields:** If the finding `Id` or `Resources[].Id` does not\nmatch the AWS ARN pattern\n`arn:aws:[a-z0-9-]+:[a-z]{2}-[a-z]+-\\d:\\d{12}:.*`, append:\n\n> Moved to [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md#step-0--malformed-arn-data_quality-flag).\n> DATA_QUALITY flag for finding Id \u002F Resources[].Id not matching the AWS ARN pattern (does not change the verdict).\n\n\n**Field-defaulting rules (apply when a field is absent but non-fatal):**\n\n> Moved to [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md#step-0--field-defaulting-rules).\n> Defaults: StatusReasons-missing-on-NOT_AVAILABLE → WARNING (never NOT_APPLICABLE), RecordState → ACTIVE, Workflow → NEW, UpdatedAt-absent → STALE_FLAG, Severity → MEDIUM.\n\n### Step 1 — RecordState = ARCHIVED → NOT_APPLICABLE (stale)\n\nSecurity Hub archives findings when the resource was deleted, the control was\ndisabled, or the finding was superseded by a newer one. An archived finding\nrepresents a **historical** state. If `RecordState = ARCHIVED`, emit\n**NOT_APPLICABLE** regardless of `Compliance.Status`.\n\nCite \"Rule 1: archived — resource deleted or control superseded\".\n\n\n> Moved to [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md#step-1--freshness-guard).\n> STALE_FLAG when UpdatedAt is >30 days old even on ACTIVE findings (delegated-admin removal, control re-enable).\n\n\n### Step 2 — Suppressed failure → WARNING (governance flag)\n\nIf `Workflow.Status = SUPPRESSED` AND `Compliance.Status = FAILED`, emit\n**WARNING**. This is the single most misunderstood Security Hub state.\nSuppression hides the finding from the default dashboard view, but **the\ncontrol is still failing**. Suppression is an operational triage decision\n(accepted risk, compensating control, false positive), not a remediation.\n\nCite \"Rule 2: suppressed FAILED — governance concern\". Always include in the\nREASON whether the suppression has a `Note`:\n\n- If `Workflow.Note` is present, cite it (e.g., \"Suppressed by\n  securityops@example.com on 2026-06-15: 'Accepted risk — compensating\n  control via WAF rule arn:aws:wafv2:...'\").\n- If no `Note`, flag: \"Suppression has no documented justification — review\n  whether the suppression is still valid.\"\n- Security Hub does not natively expire suppressions. A suppression created\n  months ago for a temporary exception may still be hiding a failing control.\n\n\n> Moved to [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md#step-2--suppression-lifecycle-heuristic).\n> No suppression TTL — validity heuristic by age and Note presence (\u003C30d valid, 30-90d review, >90d stale, no-Note suspect).\n\n### Step 3 — Resolved but still FAILED → WARNING (pending re-evaluation)\n\nIf `Workflow.Status = RESOLVED` AND `Compliance.Status = FAILED`, emit\n**WARNING**. The operator marked the finding resolved (remediation applied),\nbut Security Hub has not yet re-evaluated the control.\n\nSecurity Hub re-runs control checks every **12 to 24 hours** (the Config rule\nevaluation trigger determines the exact interval — see Config-rule evaluation\ntriggers reference). If the finding was marked `RESOLVED` more than 48 hours\nago and is still `FAILED`, the remediation likely **failed** — escalate to\n**FAILED** and note: \"Resolution marked >48h ago but control still FAILED —\nremediation likely incomplete. Re-investigate the resource directly.\"\n\n\n### Step 4 — NOT_AVAILABLE → split by StatusReasons\n\n`Compliance.Status = NOT_AVAILABLE` means Security Hub **could not produce a\ndefinitive PASSED\u002FFAILED**. The reason matters — it splits into two verdicts:\n\n**NOT_APPLICABLE** (control genuinely does not apply):\n- `NO_RESOURCES` — zero resources in scope. Example: Redshift.1 with no\n  Redshift clusters.\n- `DISABLED_CONTROL` — control disabled by the delegated administrator (or\n  via Security Hub Central Configuration).\n- `UNSUPPORTED_INSTANCE_TYPE` — resource exists but the control does not\n  evaluate this variant.\n\n**WARNING** (Security Hub tried and failed — needs investigation):\n- `SUPPORTED_SERVICE_NOT_ENABLED` — AWS Config not enabled in the region. The\n  control cannot run — a monitoring posture misconfiguration, not a pass.\n- `CONFIG_RETURNS_UNKNOWN` — Config rule returned UNKNOWN (transient error or\n  permissions issue with the Config service-linked role).\n- `ASSESSMENT_FAILED` — assessment threw an error. Often transient but may\n  indicate systemic problems (permissions, throttling).\n- `ASSUME_ROLE_ERROR` or `PERMISSION_DENIED` — service-linked role lacks\n  permissions to evaluate the resource.\n- `SECURITY_HUB_NOT_ENABLED_IN_REGION` — Hub disabled in the region.\n- `CANNOT_ENABLE_RECORDS` — cannot enable Config recording.\n- `UNKNOWN_CONTROL_STATUS` — undetermined, investigate.\n- StatusReasons empty or absent → WARNING: \"NOT_AVAILABLE with no\n  StatusReasons — investigate manually.\"\n\n\n> Moved to [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md#step-4--full-statusreason-code-reference).\n> Complete StatusReason code → verdict → meaning table (NO_RESOURCES through UNKNOWN_CONTROL_STATUS).\n\nCite \"Rule 4: NOT_AVAILABLE — \u003Ccode>\".\n\n### Step 5 — Compliance.Status = FAILED → FAILED\n\n`RecordState = ACTIVE`, `Workflow.Status ∈ {NEW, NOTIFIED}`,\n`Compliance.Status = FAILED`. The control is currently failing and has not\nbeen triaged. Emit **FAILED**.\n\nCite \"Rule 5: active FAILED — control is non-compliant\". Map to the\nfix-action table for the specific remediation.\n\n### Step 6 — Compliance.Status = WARNING → WARNING\n\nSecurity Hub uses `WARNING` for partially compliant controls or informational\nconcerns. Example: a CloudTrail trail exists but log validation is disabled.\nEmit **WARNING**.\n\nCite \"Rule 6: WARNING — partial compliance or informational concern\".\n\n### Step 7 — Compliance.Status = PASSED → PASSED\n\n`Compliance.Status = PASSED` AND `RecordState = ACTIVE`. The resource is\nfully compliant. Emit **PASSED** with `REMEDIATION: None required — control\nis compliant`.\n\n### Step 8 — Aggregation (multi-finding rollup)\n\nWhen auditing multiple findings for the same control across resources, or\nmultiple controls across an account, the aggregate verdict is the **worst\nverdict**:\n\n```\nFAILED > WARNING > PASSED > NOT_APPLICABLE\n```\n\nReport the count of each verdict in the aggregate:\n```text\nCONTROL: \u003CControlId>\nAGGREGATE VERDICT: FAILED\nBREAKDOWN: 3 FAILED, 1 WARNING, 12 PASSED, 2 NOT_APPLICABLE (across 18 resources)\n```\n\n## Severity escalation matrix\n\n> Moved to [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md#severity-escalation-matrix).\n> Verdict × severity priority\u002FSLA table, cross-standard severity rule, and blast-radius escalation (aggregate N>10, time-decay >90d, trust-boundary → P0).\n\n## Config-rule evaluation triggers (expert reference)\n\n> Moved to [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md#config-rule-evaluation-triggers-expert-reference).\n> Config-change vs periodic trigger families per control, 5-30 min vs 6-24h re-evaluation windows, describe-config-rules verification.\n\n## Security Hub internals (non-obvious operational knowledge)\n\n> Moved to [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md#security-hub-internals-non-obvious-operational-knowledge).\n> Dedup composite key, BatchUpdateFindings race, Config backlog delays, ingestion latency stages, automation-rule silent suppression, control enablement cost model.\n\n## Finding correlation and root-cause grouping\n\n> Moved to [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md#finding-correlation-and-root-cause-grouping).\n> Root-cause grouping rules (S3 BPA fan-in, account-policy gaps, Config-disabled clusters, cross-standard duplicates).\n\n## Coverage assessment heuristic\n\n> Moved to [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md#coverage-assessment-heuristic).\n> coverage_score formula and 90% \u002F 70% operational benchmarks.\n\n## Control-to-fix-action mapping\n\n> Moved to [references\u002Fremediation-guidance.md](references\u002Fremediation-guidance.md#control-to-fix-action-mapping).\n> FSBP (S3, IAM, CloudTrail, Config, EC2, KMS, RDS, Lambda), CIS v1.2-v2.0, and PCI\u002FNIST control → fix action → CLI tables.\n\n## Multi-account aggregation (Organizations)\n\n> Moved to [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md#multi-account-aggregation-organizations).\n> Delegated-admin aggregation, enrolled-but-not-enabled WARNING, FindingAggregator cross-region propagation, ASSUME_ROLE_ERROR root cause and fix.\n\n## Custom controls and non-standard findings\n\n> Moved to [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md#custom-controls-and-non-standard-findings).\n> Custom control remediation lookup chain (Description\u002FRemediationUrl → ASFF Remediation fields → resource-type derivation) and automation-rule detection.\n\n## Output format — worked examples\n\n### Multi-finding report\n\n```text\nCONTROL: S3.2 (S3 Bucket-Level Public Access Prohibition)\nVERDICT: FAILED\nREASON: Rule 5 (active FAILED) — Compliance.Status is FAILED,\nWorkflow.Status is NEW, RecordState is ACTIVE. Bucket app-uploads-prod\ndoes not have bucket-level BPA enabled.\nSEVERITY: HIGH\nREMEDIATION: Enable all 4 bucket-level BPA settings on app-uploads-prod:\naws s3api put-public-access-block --bucket app-uploads-prod\n  --public-access-block-configuration\n    BlockPublicAcls=true,IgnorePublicAcls=true,\n    BlockPublicPolicy=true,RestrictPublicBuckets=true\n\nCONTROL: IAM.7 (IAM Password Policy)\nVERDICT: PASSED\nREASON: Rule 7 (PASSED) — Compliance.Status is PASSED, RecordState is ACTIVE.\nPassword policy meets all FSBP requirements.\nSEVERITY: MEDIUM\nREMEDIATION: None required — control is compliant.\n\nCONTROL: Redshift.1 (Redshift Clusters Public Access)\nVERDICT: NOT_APPLICABLE\nREASON: Rule 4 (NOT_AVAILABLE — NO_RESOURCES) — Compliance.Status is\nNOT_AVAILABLE with StatusReasons code NO_RESOURCES. No Redshift clusters\nexist in this account\u002Fregion.\nSEVERITY: MEDIUM\nREMEDIATION: None required — control does not apply.\n\nCONTROL: Config.1 (AWS Config Enabled)\nVERDICT: WARNING\nREASON: Rule 4 (NOT_AVAILABLE — SUPPORTED_SERVICE_NOT_ENABLED) —\nCompliance.Status is NOT_AVAILABLE with StatusReasons code\nSUPPORTED_SERVICE_NOT_ENABLED. AWS Config is not enabled in eu-west-2,\nso this control cannot evaluate. This is a monitoring gap, not a pass.\nSEVERITY: MEDIUM\nREMEDIATION: Enable AWS Config in eu-west-2:\naws configservice put-configuration-recorder\n  --configuration-recorder name=default,roleARN=\u003Crole>\n  --recording-group allSupported=true,includeGlobalResourceTypes=true\n```\n\n## NEVER (anti-patterns)\n\n- NEVER pass through `Compliance.Status = NOT_AVAILABLE` as NOT_APPLICABLE\n  without checking `StatusReasons`. `NO_RESOURCES` means the control does not\n  apply (NOT_APPLICABLE), but `SUPPORTED_SERVICE_NOT_ENABLED` means Config is\n  off — a monitoring posture gap that is a WARNING. Treating the latter as\n  NOT_APPLICABLE hides a misconfiguration that makes the entire compliance\n  posture unreliable.\n\n- NEVER treat a SUPPRESSED finding as PASSED. `Workflow.Status = SUPPRESSED`\n  means someone hid the finding from the default view. If\n  `Compliance.Status = FAILED`, the control is still failing — the verdict is\n  WARNING. Suppression is a triage decision, not a remediation.\n\n- NEVER treat `Workflow.Status = RESOLVED` as evidence that the resource is\n  now compliant. RESOLVED is an operator assertion. Security Hub re-evaluates\n  on its own schedule. If still `FAILED` after 48h (or 1h for config-change\n  controls), the fix failed.\n\n- NEVER classify an ARCHIVED finding as FAILED. `RecordState = ARCHIVED` means\n  the resource was deleted or the control superseded. The verdict is\n  NOT_APPLICABLE.\n\n- NEVER ignore `FirstObservedAt` \u002F `UpdatedAt` timestamps. A `FAILED` finding\n  open for 180 days is a different operational concern than one opened\n  yesterday. Age compounds risk — escalate for findings > 90 days old.\n\n- NEVER classify an integration finding (GuardDuty, Inspector, Macie,\n  Detective, Firewall Manager) as a control compliance verdict. These lack a\n  `Compliance` block — they are security events. Route them to the\n  appropriate detector skill.\n\n- NEVER assume a single region's findings represent global compliance.\n  Security Hub is regional. A finding for `us-east-1` says nothing about\n  `eu-west-1`. Always check the `Region` field. In multi-region accounts, the\n  delegated administrator must aggregate via `FindingAggregator`.\n\n- NEVER recommend disabling a Security Hub control as the fix for a FAILED\n  finding. Disabling removes visibility — it trades FAILED for\n  NOT_APPLICABLE without fixing the resource. The only legitimate reason to\n  disable is a confirmed false-positive.\n\n- NEVER aggregate findings by severity alone without considering blast radius.\n  A `MEDIUM` FAILED on an IAM role with cross-account trust is more dangerous\n  than ten `HIGH` findings on isolated dev resources.\n\n- NEVER assume `Severity.Label` is the final priority. The aggregate (N > 10)\n  and time-decay (> 90 days) escalation rules override the label — a `MEDIUM`\n  FAILED on 50 resources for 6 months is effectively P1.\n\n- NEVER batch-update finding workflow status to RESOLVED without confirming\n  the resource is actually fixed. If the resource is still non-compliant,\n  Security Hub re-opens the finding on the next cycle.\n\n- NEVER trust ARN fields blindly. A finding `Resources[].Id` that does not\n  match the AWS ARN pattern\n  (`arn:aws:[service]:[region]:[account]:[resource]`) indicates either a\n  malformed ASFF payload or a non-AWS resource incorrectly ingested. Flag\n  the data-quality issue and verify the finding source before acting on the\n  remediation. Malformed ARNs cause downstream failures in any CLI command\n  that takes `--resource-arn` or `--bucket` parameters.\n\n- NEVER assume cross-account Security Hub findings are actionable from the\n  administrator account. The delegated administrator can SEE findings from\n  member accounts but may not have permission to MODIFY the underlying\n  resources. A control backed by a Config rule that assumes\n  `AWSServiceRoleForSecurityHub` in the member account will show\n  `ASSUME_ROLE_ERROR` if that role's trust policy is broken or the member\n  account was enrolled without enabling Security Hub. This is a WARNING — the\n  role trust must be fixed before the control can evaluate.\n\n- NEVER call `BatchUpdateFindings` with more than 100 finding identifiers.\n  The API rejects batches over 100 with `InvalidInputException`. Chunk into\n  groups of 100 or fewer.\n\n- NEVER apply remediation commands in a tight loop without exponential\n  backoff. Config rule evaluations and Security Hub API calls share a rate\n  limit. A burst across 50 resources can trigger `ThrottlingException` and\n  leave some unremediated silently.\n\n- NEVER attempt to update `Compliance.Status` via `BatchUpdateFindings` — it\n  is a system-managed field. Only `Workflow.Status`, `RecordState`, `Note`,\n  and `Severity` are user-updatable. Trying to set `Compliance.Status`\n  returns `InvalidInputException`.\n\n## API and CLI constraints\n\n> Moved to [references\u002Ferror-handling.md](references\u002Ferror-handling.md#api-and-cli-constraints).\n> Pagination and batch limits (100 findings, 4 KB Note), throttling\u002Fbackoff, eventual consistency, CLI failure recovery (InvalidInputException, AccessDenied, NoSuchBucket).\n\n## Pre-flight safety checks (run before any remediation)\n\n> Moved to [references\u002Fdiagnostic-commands.md](references\u002Fdiagnostic-commands.md#pre-flight-safety-checks-run-before-any-remediation).\n> Dry-run mode for batch remediation, resource-existence probes per service, rollback state capture, region\u002Fdelegated-admin verification, trust-boundary incident handling, permission-fallback escalation.\n\n## Remediation guidance\n\n> Moved to [references\u002Fremediation-guidance.md](references\u002Fremediation-guidance.md#remediation-guidance).\n> FAILED playbook (map → pre-flight → fix → RESOLVED → await re-evaluation), WARNING playbook (suppression review\u002Funsuppress, resolved-pending, Config gap), NOT_APPLICABLE disposition.\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> Central configuration, Automated Security Response on AWS, control lifecycle updates, Audit Manager integration.\n\n## References (load on demand)\n\n- [advanced-patterns](references\u002Fadvanced-patterns.md) — Activation triggers, Mindset, Step 0-4 detail prose, severity escalation matrix, Config-rule triggers, Security Hub internals, correlation, coverage heuristic, multi-account aggregation, custom controls, recent AWS features\n- [diagnostic-commands](references\u002Fdiagnostic-commands.md) — pre-flight safety checks (dry-run, existence probes, rollback capture)\n- [error-handling](references\u002Ferror-handling.md) — malformed-input emit blocks and API\u002FCLI constraints with failure recovery\n- [remediation-guidance](references\u002Fremediation-guidance.md) — control-to-fix-action mapping tables and per-verdict remediation playbooks\n\n## Domain\n\nAWS CloudOps \u002F Security Hub Compliance & Posture Management.\n\n## AWS documentation\n\n- **AWS Security Hub User Guide** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fsecurityhub\u002Flatest\u002Fuserguide\u002Fwhat-is-securityhub.html\n- **Security Hub Security** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fsecurityhub\u002Flatest\u002Fuserguide\u002Fsecurity.html\n- **Security Hub API Reference** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fsecurityhub\u002F1.0\u002FAPIReference\u002F\n- **Security Hub CLI Reference** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fcli\u002Flatest\u002Freference\u002Fsecurityhub\u002F\n- **Central configuration** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fsecurityhub\u002Flatest\u002Fuserguide\u002Fcentral-configuration.html\n",{"name":5,"license":15,"metadata":24,"description":7,"compatibility":37},{"tags":25,"phase":26,"author":27,"domain":28,"family":29,"version":30,"keywords":31,"complexity":32,"entry_point":33,"when_to_use":34,"requires_llm":35,"verdict_shape":36,"supports_pipeline":35},"aws, securityhub, security, compliance, fsbp, cis, pci-dss, nist, audit, remediation, asff","2","Jacky Chan — AWS Community Builder","aws-cloudops","Security","0.2.0","Security Hub, compliance, control status, FSBP, Foundational Security Best Practices, CIS Benchmark, PCI-DSS, NIST 800-53, ASFF, finding lifecycle, suppression, remediation runbook, compliance verdict, NOT_AVAILABLE, StatusReasons, Workflow Status, Record State, delegated administrator","high","false","Reviewing Security Hub control compliance status, triaging a compliance gap report, mapping findings to remediation actions, auditing finding lifecycle states (suppressed \u002F resolved \u002F archived), preparing for a compliance audit, or generating an executive compliance summary across FSBP \u002F CIS \u002F PCI-DSS \u002F NIST standards.","true","FAILED | WARNING | PASSED | NOT_APPLICABLE","Agent runtime that reads SKILL.md (Claude Code, Cursor, Windsurf, Codex, Gemini). No AWS CLI required for offline classification — the skill reasons over provided Security Hub finding JSON (ASFF). For live-account audits, AWS CLI v2 with securityhub access (ListEnabledStandards, GetEnabledStandards, GetFindings, batch-update-findings) and SSO or key-based credentials.","main","eeace51bd5dd1db2030729d83eeab988861553aa","skills\u002Fsecurityhub-control-compliance-auditor",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":47,"prompt":57,"zipAvailable":58},[48,51,54],{"tool":49,"command":50},"npx","npx skills add jhkchan\u002Faws-agent-skills --skill securityhub-control-compliance-auditor",{"tool":52,"command":53},"bunx","bunx skills add jhkchan\u002Faws-agent-skills --skill securityhub-control-compliance-auditor",{"tool":55,"command":56},"pnpm","pnpm dlx skills add jhkchan\u002Faws-agent-skills --skill securityhub-control-compliance-auditor","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fsecurityhub-control-compliance-auditor\u002FSKILL.md",true,[60,66,70,74,78,82,86,90,94,98,102,106,110,113,117,121,125,129,133,137,141],{"path":61,"resourceType":62,"resourceTypeDesc":63,"sizeBytes":64,"sourceHtmlUrl":65},"eval\u002Ftest-cases.yaml","REFERENCE","参考文档",7360,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fsecurityhub-control-compliance-auditor\u002Feval\u002Ftest-cases.yaml",{"path":67,"resourceType":62,"resourceTypeDesc":63,"sizeBytes":68,"sourceHtmlUrl":69},"evals\u002Fbaselines\u002Farchived-finding.md",715,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fsecurityhub-control-compliance-auditor\u002Fevals\u002Fbaselines\u002Farchived-finding.md",{"path":71,"resourceType":62,"resourceTypeDesc":63,"sizeBytes":72,"sourceHtmlUrl":73},"evals\u002Fbaselines\u002Fiam-password-policy-passed.md",612,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fsecurityhub-control-compliance-auditor\u002Fevals\u002Fbaselines\u002Fiam-password-policy-passed.md",{"path":75,"resourceType":62,"resourceTypeDesc":63,"sizeBytes":76,"sourceHtmlUrl":77},"evals\u002Fbaselines\u002Fnot-available-no-resources.md",651,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fsecurityhub-control-compliance-auditor\u002Fevals\u002Fbaselines\u002Fnot-available-no-resources.md",{"path":79,"resourceType":62,"resourceTypeDesc":63,"sizeBytes":80,"sourceHtmlUrl":81},"evals\u002Fbaselines\u002Fnot-available-service-disabled.md",655,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fsecurityhub-control-compliance-auditor\u002Fevals\u002Fbaselines\u002Fnot-available-service-disabled.md",{"path":83,"resourceType":62,"resourceTypeDesc":63,"sizeBytes":84,"sourceHtmlUrl":85},"evals\u002Fbaselines\u002Fs3-bpa-failed.md",759,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fsecurityhub-control-compliance-auditor\u002Fevals\u002Fbaselines\u002Fs3-bpa-failed.md",{"path":87,"resourceType":62,"resourceTypeDesc":63,"sizeBytes":88,"sourceHtmlUrl":89},"evals\u002Fbaselines\u002Fsuppressed-failed.md",706,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fsecurityhub-control-compliance-auditor\u002Fevals\u002Fbaselines\u002Fsuppressed-failed.md",{"path":91,"resourceType":62,"resourceTypeDesc":63,"sizeBytes":92,"sourceHtmlUrl":93},"evals\u002Feval_config.yaml",2028,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fsecurityhub-control-compliance-auditor\u002Fevals\u002Feval_config.yaml",{"path":95,"resourceType":62,"resourceTypeDesc":63,"sizeBytes":96,"sourceHtmlUrl":97},"evals\u002Fevals.json",4908,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fsecurityhub-control-compliance-auditor\u002Fevals\u002Fevals.json",{"path":99,"resourceType":62,"resourceTypeDesc":63,"sizeBytes":100,"sourceHtmlUrl":101},"evals\u002Fprompts\u002Farchived-finding.md",889,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fsecurityhub-control-compliance-auditor\u002Fevals\u002Fprompts\u002Farchived-finding.md",{"path":103,"resourceType":62,"resourceTypeDesc":63,"sizeBytes":104,"sourceHtmlUrl":105},"evals\u002Fprompts\u002Fiam-password-policy-passed.md",799,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fsecurityhub-control-compliance-auditor\u002Fevals\u002Fprompts\u002Fiam-password-policy-passed.md",{"path":107,"resourceType":62,"resourceTypeDesc":63,"sizeBytes":108,"sourceHtmlUrl":109},"evals\u002Fprompts\u002Fnot-available-no-resources.md",850,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fsecurityhub-control-compliance-auditor\u002Fevals\u002Fprompts\u002Fnot-available-no-resources.md",{"path":111,"resourceType":62,"resourceTypeDesc":63,"sizeBytes":108,"sourceHtmlUrl":112},"evals\u002Fprompts\u002Fnot-available-service-disabled.md","https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fsecurityhub-control-compliance-auditor\u002Fevals\u002Fprompts\u002Fnot-available-service-disabled.md",{"path":114,"resourceType":62,"resourceTypeDesc":63,"sizeBytes":115,"sourceHtmlUrl":116},"evals\u002Fprompts\u002Fs3-bpa-failed.md",841,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fsecurityhub-control-compliance-auditor\u002Fevals\u002Fprompts\u002Fs3-bpa-failed.md",{"path":118,"resourceType":62,"resourceTypeDesc":63,"sizeBytes":119,"sourceHtmlUrl":120},"evals\u002Fprompts\u002Fsuppressed-failed.md",896,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fsecurityhub-control-compliance-auditor\u002Fevals\u002Fprompts\u002Fsuppressed-failed.md",{"path":122,"resourceType":62,"resourceTypeDesc":63,"sizeBytes":123,"sourceHtmlUrl":124},"example\u002Fend-to-end-audit.md",7988,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fsecurityhub-control-compliance-auditor\u002Fexample\u002Fend-to-end-audit.md",{"path":126,"resourceType":62,"resourceTypeDesc":63,"sizeBytes":127,"sourceHtmlUrl":128},"references\u002Fadvanced-patterns.md",18986,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fsecurityhub-control-compliance-auditor\u002Freferences\u002Fadvanced-patterns.md",{"path":130,"resourceType":62,"resourceTypeDesc":63,"sizeBytes":131,"sourceHtmlUrl":132},"references\u002Fdiagnostic-commands.md",3105,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fsecurityhub-control-compliance-auditor\u002Freferences\u002Fdiagnostic-commands.md",{"path":134,"resourceType":62,"resourceTypeDesc":63,"sizeBytes":135,"sourceHtmlUrl":136},"references\u002Ferror-handling.md",2441,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fsecurityhub-control-compliance-auditor\u002Freferences\u002Ferror-handling.md",{"path":138,"resourceType":62,"resourceTypeDesc":63,"sizeBytes":139,"sourceHtmlUrl":140},"references\u002Fremediation-guidance.md",8227,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fsecurityhub-control-compliance-auditor\u002Freferences\u002Fremediation-guidance.md",{"path":142,"resourceType":62,"resourceTypeDesc":63,"sizeBytes":143,"sourceHtmlUrl":144},"skill.usf.yaml",4233,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fsecurityhub-control-compliance-auditor\u002Fskill.usf.yaml",[146,153,160,167,174,181],{"skillNo":147,"name":148,"nameZh":6,"description":149,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":150,"categories":151,"keywords":152,"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":154,"name":155,"nameZh":6,"description":156,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":157,"categories":158,"keywords":159,"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":161,"name":162,"nameZh":6,"description":163,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":164,"categories":165,"keywords":166,"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":168,"name":169,"nameZh":6,"description":170,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":171,"categories":172,"keywords":173,"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":175,"name":176,"nameZh":6,"description":177,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":178,"categories":179,"keywords":180,"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":182,"name":183,"nameZh":6,"description":184,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":185,"categories":186,"keywords":187,"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",[],[]]