[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71CDMT9G41NWZH5AMWDQ853":3,"skill-same:01M71CDMT9G41NWZH5AMWDQ853":95},{"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":28,"publishedAt":49,"linkOnly":50,"markdownContent":51,"markdownBody":52,"frontMatter":53,"refName":68,"commitSha":69,"skillDirectory":70,"forksCount":14,"repositoryHtmlUrl":71,"repositoryHomepageUrl":6,"ownerHtmlUrl":72,"ownerBlogUrl":6,"ownerDescription":73,"updatedAt":74,"install":75,"resources":88},"01M71CDMT9G41NWZH5AMWDQ853","aws-securityhub-audit",null,"This skill covers deploying AWS Security Hub as a centralized cloud security posture management platform that aggregates findings from GuardDuty, Inspector, Macie, and third-party tools. It details enabling security standards like CIS AWS Foundations Benchmark, configuring automated remediation, and building executive dashboards for compliance tracking across multi-account AWS organizations.","DCx7C5\u002Fai-marketplace","DCx7C5","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F42419559?v=4","01M71C01G2AZV3NTNGWAWSHJPP","DC","01M71C01GQW6G50S2BYMS7PP3E",0,"MIT","https:\u002F\u002Fgithub.com\u002FDCx7C5\u002Fai-marketplace\u002Fblob\u002Fmain\u002Fskills\u002Fcloud\u002Faws\u002Fsecurityhub\u002Faudit\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000037","律师与法务","PROFESSION","适用职业",[29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48],"audit","aws securityhub audit","aws","Bash","cybersecurity","foundations","security standards","de","across","aggregates","cm","aws security","finding-aggregation","security-standards","compliance-automation","aws-security-hub","cspm","security-hub","macie","guardduty","2026-11-10 10:12:30",false,"---\nname: aws-securityhub-audit\ndescription: This skill covers deploying AWS Security Hub as a centralized cloud security posture management platform that aggregates findings from GuardDuty, Inspector, Macie, and third-party tools. It details enabling security standards like CIS AWS Foundations Benchmark, configuring automated remediation, and building executive dashboards for compliance tracking across multi-account AWS organizations.\ndomain: cybersecurity\nsubdomain: cloud-security\ntags:\n- aws-security-hub\n- cspm\n- compliance-automation\n- security-standards\n- finding-aggregation\nnist_csf:\n- PR.IR-01\n- ID.AM-08\n- GV.SC-06\n- DE.CM-01\nmodel: sonnet\nmaxTurns: 20\ntools: [Read, Bash, Glob, Grep]\ncapec: []\n---\n\n# Implementing AWS Security Hub\n\n## When to Use\n\n- When establishing a centralized security findings dashboard across multiple AWS accounts\n- When enabling automated compliance checks against CIS, PCI-DSS, NIST, or AWS Foundational Security Best Practices\n- When integrating findings from GuardDuty, Inspector, Macie, and third-party security tools\n- When building automated remediation workflows for recurring security misconfigurations\n- When preparing compliance evidence for auditors requiring continuous posture monitoring\n\n**Do not use** for real-time threat detection (see detecting-cloud-threats-with-guardduty), for Azure compliance monitoring (see securing-azure-with-microsoft-defender), or for deep vulnerability scanning of container images (see securing-container-registry).\n\n## Prerequisites\n\n- AWS Organization with a designated security administrator account\n- AWS Config enabled in all target accounts and regions\n- GuardDuty, Inspector, and Macie activated for finding integration\n- IAM permissions for securityhub:* and config:* in the administrator account\n\n## Workflow\n\n### Step 1: Enable Security Hub with Standards\n\nActivate Security Hub in the delegated administrator account and enable security standards. AWS Security Hub CSPM supports CIS AWS Foundations Benchmark v5.0, AWS Foundational Security Best Practices, PCI DSS v3.2.1, and NIST SP 800-53.\n\n```bash\n# Enable Security Hub with standards\naws securityhub enable-security-hub \\\n  --enable-default-standards \\\n  --tags '{\"Environment\":\"production\",\"ManagedBy\":\"security-team\"}'\n\n# Enable CIS AWS Foundations Benchmark v5.0\naws securityhub batch-enable-standards \\\n  --standards-subscription-requests '[\n    {\"StandardsArn\": \"arn:aws:securityhub:::ruleset\u002Fcis-aws-foundations-benchmark\u002Fv\u002F5.0.0\"},\n    {\"StandardsArn\": \"arn:aws:securityhub:us-east-1::standards\u002Faws-foundational-security-best-practices\u002Fv\u002F1.0.0\"},\n    {\"StandardsArn\": \"arn:aws:securityhub:us-east-1::standards\u002Fpci-dss\u002Fv\u002F3.2.1\"}\n  ]'\n\n# Verify enabled standards\naws securityhub get-enabled-standards \\\n  --query 'StandardsSubscriptions[*].[StandardsArn,StandardsStatus]' --output table\n```\n\n### Step 2: Configure Multi-Account Aggregation\n\nDesignate a Security Hub administrator and automatically enroll all organization member accounts. Configure cross-region aggregation to consolidate findings into a single region.\n\n```bash\n# Designate delegated admin\naws securityhub enable-organization-admin-account \\\n  --admin-account-id 111122223333\n\n# Auto-enable for all org members\naws securityhub update-organization-configuration \\\n  --auto-enable \\\n  --organization-configuration '{\"ConfigurationType\": \"CENTRAL\"}'\n\n# Enable cross-region aggregation\naws securityhub create-finding-aggregator \\\n  --region-linking-mode ALL_REGIONS\n```\n\n### Step 3: Integrate Security Services and Third-Party Tools\n\nConfigure product integrations to receive findings from AWS services and partner security tools. Map third-party findings to AWS Security Finding Format (ASFF).\n\n```bash\n# List available product integrations\naws securityhub describe-products \\\n  --query 'Products[*].[ProductName,CompanyName,ProductSubscriptionResourcePolicy]' --output table\n\n# Enable specific integrations\naws securityhub enable-import-findings-for-product \\\n  --product-arn \"arn:aws:securityhub:us-east-1::product\u002Faws\u002Fguardduty\"\n\naws securityhub enable-import-findings-for-product \\\n  --product-arn \"arn:aws:securityhub:us-east-1::product\u002Faws\u002Finspector\"\n\n# Import custom findings using ASFF format\naws securityhub batch-import-findings --findings '[{\n  \"SchemaVersion\": \"2018-10-08\",\n  \"Id\": \"custom-finding-001\",\n  \"ProductArn\": \"arn:aws:securityhub:us-east-1:123456789012:product\u002F123456789012\u002Fdefault\",\n  \"GeneratorId\": \"custom-scanner\",\n  \"AwsAccountId\": \"123456789012\",\n  \"Types\": [\"Software and Configuration Checks\u002FVulnerabilities\u002FCVE\"],\n  \"Title\": \"Unpatched OpenSSL in production ALB backend\",\n  \"Description\": \"CVE-2024-12345 detected on backend instances\",\n  \"Severity\": {\"Label\": \"HIGH\"},\n  \"Resources\": [{\"Type\": \"AwsEc2Instance\", \"Id\": \"arn:aws:ec2:us-east-1:123456789012:instance\u002Fi-0abc123\"}]\n}]'\n```\n\n### Step 4: Build Automated Remediation\n\nCreate Security Hub custom actions linked to EventBridge rules and Lambda functions for one-click or fully automated remediation of common findings.\n\n```bash\n# Create a custom action for remediation\naws securityhub create-action-target \\\n  --name \"IsolateInstance\" \\\n  --description \"Isolate EC2 instance by replacing security groups\" \\\n  --id \"IsolateInstance\"\n\n# EventBridge rule for automated remediation of specific controls\naws events put-rule \\\n  --name SecurityHubAutoRemediate \\\n  --event-pattern '{\n    \"source\": [\"aws.securityhub\"],\n    \"detail-type\": [\"Security Hub Findings - Imported\"],\n    \"detail\": {\n      \"findings\": {\n        \"Compliance\": {\"Status\": [\"FAILED\"]},\n        \"Severity\": {\"Label\": [\"CRITICAL\", \"HIGH\"]},\n        \"GeneratorId\": [\"aws-foundational-security-best-practices\u002Fv\u002F1.0.0\u002FS3.1\"]\n      }\n    }\n  }'\n```\n\n### Step 5: Monitor Compliance Scores and Generate Reports\n\nTrack security scores across standards, monitor compliance drift over time, and generate reports for audit evidence.\n\n```bash\n# Get security score for a standard\naws securityhub get-security-control-definition \\\n  --security-control-id \"S3.1\"\n\n# List all failed controls with counts\naws securityhub get-findings \\\n  --filters '{\n    \"ComplianceStatus\": [{\"Value\": \"FAILED\", \"Comparison\": \"EQUALS\"}],\n    \"RecordState\": [{\"Value\": \"ACTIVE\", \"Comparison\": \"EQUALS\"}]\n  }' \\\n  --sort-criteria '{\"Field\": \"SeverityLabel\", \"SortOrder\": \"desc\"}' \\\n  --max-items 50\n```\n\n## Key Concepts\n\n| Term | Definition |\n|------|------------|\n| Security Standard | Pre-packaged set of controls mapped to compliance frameworks such as CIS, PCI-DSS, NIST 800-53, and AWS best practices |\n| Security Control | Individual automated check that evaluates a specific AWS resource configuration against a security requirement |\n| ASFF | AWS Security Finding Format, a standardized JSON schema for normalizing findings from all integrated security products |\n| Compliance Score | Percentage of controls in a passing state within a given security standard, calculated per account and aggregated at the organization level |\n| Finding Aggregator | Cross-region mechanism that consolidates findings from all enabled regions into a single administrator region |\n| Custom Action | User-defined action that can be triggered from the Security Hub console to invoke EventBridge rules for manual or automated response |\n\n## Tools & Systems\n\n- **AWS Security Hub CSPM**: Core platform for automated security posture checks and finding aggregation\n- **AWS Config**: Underlying configuration recorder that Security Hub relies on for resource evaluation\n- **Amazon EventBridge**: Event routing service for connecting Security Hub findings to automated remediation workflows\n- **AWS Systems Manager**: Automation documents that Security Hub can invoke for remediation of common misconfigurations\n- **AWS Audit Manager**: Generates audit-ready reports using Security Hub findings as evidence\n\n## Common Scenarios\n\n### Scenario: Failed CIS Controls Across 50 Accounts\n\n**Context**: An enterprise enables CIS AWS Foundations Benchmark v5.0 and discovers 340 failed controls across 50 accounts, primarily in IAM password policy, CloudTrail configuration, and VPC flow log enablement.\n\n**Approach**:\n1. Export all FAILED findings grouped by control ID to identify the most prevalent issues\n2. Prioritize Critical and High severity controls that affect the most accounts\n3. Create Systems Manager Automation documents for the top 10 recurring failures\n4. Deploy automated remediation via EventBridge for controls like S3.1 (block public access) and CloudTrail.1 (enable multi-region trail)\n5. Schedule weekly compliance score reviews and track improvement over a 90-day remediation window\n\n**Pitfalls**: Enabling automated remediation for all controls at once can break production workloads that legitimately require public S3 access or specific network configurations. Always test remediation in a staging account first.\n\n## Output Format\n\n```\nAWS Security Hub Compliance Report\n====================================\nOrganization: acme-corp\nAdministrator Account: 111122223333\nReport Date: 2025-02-23\nStandards Enabled: CIS v5.0, AWS FSBP v1.0, PCI DSS v3.2.1\n\nCOMPLIANCE SCORES:\n  CIS AWS Foundations Benchmark v5.0: 78%\n  AWS Foundational Security Best Practices: 85%\n  PCI DSS v3.2.1: 72%\n\nTOP FAILED CONTROLS (by account count):\n  [S3.1]   Block public access settings enabled      - 23\u002F50 accounts FAILED\n  [CT.1]   CloudTrail multi-region enabled            - 12\u002F50 accounts FAILED\n  [IAM.4]  Root account has no access keys            -  3\u002F50 accounts FAILED\n  [EC2.19] Security groups restrict unrestricted ports- 31\u002F50 accounts FAILED\n  [RDS.3]  RDS encryption at rest enabled             - 18\u002F50 accounts FAILED\n\nFINDING SUMMARY:\n  Total Active Findings: 1,247\n  Critical: 34 | High: 189 | Medium: 567 | Low: 457\n  Auto-Remediated This Month: 89\n  Suppressed: 23\n```\n","# Implementing AWS Security Hub\n\n## When to Use\n\n- When establishing a centralized security findings dashboard across multiple AWS accounts\n- When enabling automated compliance checks against CIS, PCI-DSS, NIST, or AWS Foundational Security Best Practices\n- When integrating findings from GuardDuty, Inspector, Macie, and third-party security tools\n- When building automated remediation workflows for recurring security misconfigurations\n- When preparing compliance evidence for auditors requiring continuous posture monitoring\n\n**Do not use** for real-time threat detection (see detecting-cloud-threats-with-guardduty), for Azure compliance monitoring (see securing-azure-with-microsoft-defender), or for deep vulnerability scanning of container images (see securing-container-registry).\n\n## Prerequisites\n\n- AWS Organization with a designated security administrator account\n- AWS Config enabled in all target accounts and regions\n- GuardDuty, Inspector, and Macie activated for finding integration\n- IAM permissions for securityhub:* and config:* in the administrator account\n\n## Workflow\n\n### Step 1: Enable Security Hub with Standards\n\nActivate Security Hub in the delegated administrator account and enable security standards. AWS Security Hub CSPM supports CIS AWS Foundations Benchmark v5.0, AWS Foundational Security Best Practices, PCI DSS v3.2.1, and NIST SP 800-53.\n\n```bash\n# Enable Security Hub with standards\naws securityhub enable-security-hub \\\n  --enable-default-standards \\\n  --tags '{\"Environment\":\"production\",\"ManagedBy\":\"security-team\"}'\n\n# Enable CIS AWS Foundations Benchmark v5.0\naws securityhub batch-enable-standards \\\n  --standards-subscription-requests '[\n    {\"StandardsArn\": \"arn:aws:securityhub:::ruleset\u002Fcis-aws-foundations-benchmark\u002Fv\u002F5.0.0\"},\n    {\"StandardsArn\": \"arn:aws:securityhub:us-east-1::standards\u002Faws-foundational-security-best-practices\u002Fv\u002F1.0.0\"},\n    {\"StandardsArn\": \"arn:aws:securityhub:us-east-1::standards\u002Fpci-dss\u002Fv\u002F3.2.1\"}\n  ]'\n\n# Verify enabled standards\naws securityhub get-enabled-standards \\\n  --query 'StandardsSubscriptions[*].[StandardsArn,StandardsStatus]' --output table\n```\n\n### Step 2: Configure Multi-Account Aggregation\n\nDesignate a Security Hub administrator and automatically enroll all organization member accounts. Configure cross-region aggregation to consolidate findings into a single region.\n\n```bash\n# Designate delegated admin\naws securityhub enable-organization-admin-account \\\n  --admin-account-id 111122223333\n\n# Auto-enable for all org members\naws securityhub update-organization-configuration \\\n  --auto-enable \\\n  --organization-configuration '{\"ConfigurationType\": \"CENTRAL\"}'\n\n# Enable cross-region aggregation\naws securityhub create-finding-aggregator \\\n  --region-linking-mode ALL_REGIONS\n```\n\n### Step 3: Integrate Security Services and Third-Party Tools\n\nConfigure product integrations to receive findings from AWS services and partner security tools. Map third-party findings to AWS Security Finding Format (ASFF).\n\n```bash\n# List available product integrations\naws securityhub describe-products \\\n  --query 'Products[*].[ProductName,CompanyName,ProductSubscriptionResourcePolicy]' --output table\n\n# Enable specific integrations\naws securityhub enable-import-findings-for-product \\\n  --product-arn \"arn:aws:securityhub:us-east-1::product\u002Faws\u002Fguardduty\"\n\naws securityhub enable-import-findings-for-product \\\n  --product-arn \"arn:aws:securityhub:us-east-1::product\u002Faws\u002Finspector\"\n\n# Import custom findings using ASFF format\naws securityhub batch-import-findings --findings '[{\n  \"SchemaVersion\": \"2018-10-08\",\n  \"Id\": \"custom-finding-001\",\n  \"ProductArn\": \"arn:aws:securityhub:us-east-1:123456789012:product\u002F123456789012\u002Fdefault\",\n  \"GeneratorId\": \"custom-scanner\",\n  \"AwsAccountId\": \"123456789012\",\n  \"Types\": [\"Software and Configuration Checks\u002FVulnerabilities\u002FCVE\"],\n  \"Title\": \"Unpatched OpenSSL in production ALB backend\",\n  \"Description\": \"CVE-2024-12345 detected on backend instances\",\n  \"Severity\": {\"Label\": \"HIGH\"},\n  \"Resources\": [{\"Type\": \"AwsEc2Instance\", \"Id\": \"arn:aws:ec2:us-east-1:123456789012:instance\u002Fi-0abc123\"}]\n}]'\n```\n\n### Step 4: Build Automated Remediation\n\nCreate Security Hub custom actions linked to EventBridge rules and Lambda functions for one-click or fully automated remediation of common findings.\n\n```bash\n# Create a custom action for remediation\naws securityhub create-action-target \\\n  --name \"IsolateInstance\" \\\n  --description \"Isolate EC2 instance by replacing security groups\" \\\n  --id \"IsolateInstance\"\n\n# EventBridge rule for automated remediation of specific controls\naws events put-rule \\\n  --name SecurityHubAutoRemediate \\\n  --event-pattern '{\n    \"source\": [\"aws.securityhub\"],\n    \"detail-type\": [\"Security Hub Findings - Imported\"],\n    \"detail\": {\n      \"findings\": {\n        \"Compliance\": {\"Status\": [\"FAILED\"]},\n        \"Severity\": {\"Label\": [\"CRITICAL\", \"HIGH\"]},\n        \"GeneratorId\": [\"aws-foundational-security-best-practices\u002Fv\u002F1.0.0\u002FS3.1\"]\n      }\n    }\n  }'\n```\n\n### Step 5: Monitor Compliance Scores and Generate Reports\n\nTrack security scores across standards, monitor compliance drift over time, and generate reports for audit evidence.\n\n```bash\n# Get security score for a standard\naws securityhub get-security-control-definition \\\n  --security-control-id \"S3.1\"\n\n# List all failed controls with counts\naws securityhub get-findings \\\n  --filters '{\n    \"ComplianceStatus\": [{\"Value\": \"FAILED\", \"Comparison\": \"EQUALS\"}],\n    \"RecordState\": [{\"Value\": \"ACTIVE\", \"Comparison\": \"EQUALS\"}]\n  }' \\\n  --sort-criteria '{\"Field\": \"SeverityLabel\", \"SortOrder\": \"desc\"}' \\\n  --max-items 50\n```\n\n## Key Concepts\n\n| Term | Definition |\n|------|------------|\n| Security Standard | Pre-packaged set of controls mapped to compliance frameworks such as CIS, PCI-DSS, NIST 800-53, and AWS best practices |\n| Security Control | Individual automated check that evaluates a specific AWS resource configuration against a security requirement |\n| ASFF | AWS Security Finding Format, a standardized JSON schema for normalizing findings from all integrated security products |\n| Compliance Score | Percentage of controls in a passing state within a given security standard, calculated per account and aggregated at the organization level |\n| Finding Aggregator | Cross-region mechanism that consolidates findings from all enabled regions into a single administrator region |\n| Custom Action | User-defined action that can be triggered from the Security Hub console to invoke EventBridge rules for manual or automated response |\n\n## Tools & Systems\n\n- **AWS Security Hub CSPM**: Core platform for automated security posture checks and finding aggregation\n- **AWS Config**: Underlying configuration recorder that Security Hub relies on for resource evaluation\n- **Amazon EventBridge**: Event routing service for connecting Security Hub findings to automated remediation workflows\n- **AWS Systems Manager**: Automation documents that Security Hub can invoke for remediation of common misconfigurations\n- **AWS Audit Manager**: Generates audit-ready reports using Security Hub findings as evidence\n\n## Common Scenarios\n\n### Scenario: Failed CIS Controls Across 50 Accounts\n\n**Context**: An enterprise enables CIS AWS Foundations Benchmark v5.0 and discovers 340 failed controls across 50 accounts, primarily in IAM password policy, CloudTrail configuration, and VPC flow log enablement.\n\n**Approach**:\n1. Export all FAILED findings grouped by control ID to identify the most prevalent issues\n2. Prioritize Critical and High severity controls that affect the most accounts\n3. Create Systems Manager Automation documents for the top 10 recurring failures\n4. Deploy automated remediation via EventBridge for controls like S3.1 (block public access) and CloudTrail.1 (enable multi-region trail)\n5. Schedule weekly compliance score reviews and track improvement over a 90-day remediation window\n\n**Pitfalls**: Enabling automated remediation for all controls at once can break production workloads that legitimately require public S3 access or specific network configurations. Always test remediation in a staging account first.\n\n## Output Format\n\n```\nAWS Security Hub Compliance Report\n====================================\nOrganization: acme-corp\nAdministrator Account: 111122223333\nReport Date: 2025-02-23\nStandards Enabled: CIS v5.0, AWS FSBP v1.0, PCI DSS v3.2.1\n\nCOMPLIANCE SCORES:\n  CIS AWS Foundations Benchmark v5.0: 78%\n  AWS Foundational Security Best Practices: 85%\n  PCI DSS v3.2.1: 72%\n\nTOP FAILED CONTROLS (by account count):\n  [S3.1]   Block public access settings enabled      - 23\u002F50 accounts FAILED\n  [CT.1]   CloudTrail multi-region enabled            - 12\u002F50 accounts FAILED\n  [IAM.4]  Root account has no access keys            -  3\u002F50 accounts FAILED\n  [EC2.19] Security groups restrict unrestricted ports- 31\u002F50 accounts FAILED\n  [RDS.3]  RDS encryption at rest enabled             - 18\u002F50 accounts FAILED\n\nFINDING SUMMARY:\n  Total Active Findings: 1,247\n  Critical: 34 | High: 189 | Medium: 567 | Low: 457\n  Auto-Remediated This Month: 89\n  Suppressed: 23\n```\n",{"name":5,"tags":54,"capec":55,"model":56,"tools":57,"domain":33,"maxTurns":61,"nist_csf":62,"subdomain":67,"description":7},[44,45,43,42,41],[],"sonnet",[58,32,59,60],"Read","Glob","Grep",20,[63,64,65,66],"PR.IR-01","ID.AM-08","GV.SC-06","DE.CM-01","cloud-security","main","a91f1293287ffa9f4f1b8f486cd6e835a1568c84","skills\u002Fcloud\u002Faws\u002Fsecurityhub\u002Faudit","https:\u002F\u002Fgithub.com\u002FDCx7C5\u002Fai-marketplace","https:\u002F\u002Fgithub.com\u002FDCx7C5","#Python","2026-09-01 11:21:00",{"source":8,"skillName":5,"commands":76,"prompt":86,"zipAvailable":87},[77,80,83],{"tool":78,"command":79},"npx","npx skills add DCx7C5\u002Fai-marketplace --skill aws-securityhub-audit",{"tool":81,"command":82},"bunx","bunx skills add DCx7C5\u002Fai-marketplace --skill aws-securityhub-audit",{"tool":84,"command":85},"pnpm","pnpm dlx skills add DCx7C5\u002Fai-marketplace --skill aws-securityhub-audit","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FDCx7C5\u002Fai-marketplace\u002Fblob\u002Fmain\u002Fskills\u002Fcloud\u002Faws\u002Fsecurityhub\u002Faudit\u002FSKILL.md",true,[89],{"path":90,"resourceType":91,"resourceTypeDesc":92,"sizeBytes":93,"sourceHtmlUrl":94},"index.json","REFERENCE","参考文档",674,"https:\u002F\u002Fgithub.com\u002FDCx7C5\u002Fai-marketplace\u002Fblob\u002Fmain\u002Fskills\u002Fcloud\u002Faws\u002Fsecurityhub\u002Faudit\u002Findex.json",[96,119,140,161,183,199],{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":49},"01M71HAPZ01KQ30RKTB0FFSQ05","services-wmi-persistence-detect","Detect WMI event subscription persistence by enumerating ActiveScriptEventConsumer, CommandLineEventConsumer, and permanent subscriptions in the WMI repository.","https:\u002F\u002Fgithub.com\u002FDCx7C5\u002Fai-marketplace\u002Fblob\u002Fmain\u002Fskills\u002Fwindows\u002Fservices\u002Fwmi\u002Fpersistence\u002Fdetect\u002FSKILL.md",[],[103,104,105,106,107,36,39,108,109,110,111,112,113,114,115,116,117,33,118],"services","detect","services wmi persistence detect","wmi","persistence","process","activescript","event","subscriptions","commandline-consumer","repository","subscription","event-subscription","t1546.003","forensics","process-forensics",{"skillNo":120,"name":121,"nameZh":6,"description":122,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":123,"categories":124,"keywords":125,"publishedAt":49},"01M71HAK6JTTTS229T17WJMMCG","services-wmi-exec-exploit","Perform lateral movement across Windows networks using WMI-based remote execution techniques including Impacket wmiexec.py, CrackMapExec, and native WMI commands for stealthy post-exploitation during red team engagements.","https:\u002F\u002Fgithub.com\u002FDCx7C5\u002Fai-marketplace\u002Fblob\u002Fmain\u002Fskills\u002Fwindows\u002Fservices\u002Fwmi\u002Fexec\u002Fexploit\u002FSKILL.md",[],[126,103,127,106,128,129,130,33,32,131,132,37,133,134,36,135,136,137,138,139],"exploit","services wmi exec exploit","exec","remote","traffic","analysis","team","crackmapexec","native","command","lateral movement","read","lateral-movement","Impacket",{"skillNo":141,"name":142,"nameZh":6,"description":143,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":144,"categories":145,"keywords":146,"publishedAt":49},"01M71HAG6MHKNQV8KDZKMT4886","registry-artifact-extract","Extract and analyze Windows Registry hives to uncover user activity, installed software, autostart entries, and evidence of system compromise.","https:\u002F\u002Fgithub.com\u002FDCx7C5\u002Fai-marketplace\u002Fblob\u002Fmain\u002Fskills\u002Fwindows\u002Fregistry\u002Fartifact\u002Fextract\u002FSKILL.md",[],[147,148,149,150,151,152,33,32,153,131,154,155,36,137,156,157,158,159,160,56],"artifact","registry","registry artifact extract","extract","evidence-collection","artifact-analysis","collection","analyze","uncover","software","activity","digital-forensics","windows-registry","regripper",{"skillNo":162,"name":163,"nameZh":6,"description":164,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":165,"categories":166,"keywords":167,"publishedAt":49},"01M71HACR4A8XTWTTSXK4124AA","processes-token-impersonate-detect","Detect Windows token impersonation and privilege abuse including SeImpersonatePrivilege exploitation via Potato attacks and token stealing techniques.","https:\u002F\u002Fgithub.com\u002FDCx7C5\u002Fai-marketplace\u002Fblob\u002Fmain\u002Fskills\u002Fwindows\u002Fprocesses\u002Ftoken\u002Fimpersonate\u002Fdetect\u002FSKILL.md",[],[104,168,169,170,171,172,173,39,174,33,118,175,176,177,178,179,180,181,182,36],"processes token impersonate detect","token","processes","attacks","windows","escalation","techniques","privilege-escalation","seimpersonate","token-impersonation","printspoofer","exploitation","potato","impersonation","via",{"skillNo":184,"name":185,"nameZh":6,"description":186,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":187,"categories":188,"keywords":189,"publishedAt":49},"01M71HAABSB4Z6QFSXEG00R4RK","processes-thread-injection-detect","Detect Windows thread injection techniques including CreateRemoteThread, QueueUserAPC, NtCreateThreadEx, and thread hijacking via process memory analysis.","https:\u002F\u002Fgithub.com\u002FDCx7C5\u002Fai-marketplace\u002Fblob\u002Fmain\u002Fskills\u002Fwindows\u002Fprocesses\u002Fthread\u002Finjection\u002Fdetect\u002FSKILL.md",[],[190,191,104,192,170,172,193,39,194,174,33,118,131,195,196,197,198,182,36,108],"thread","processes thread injection detect","injection","memory","process-injection","api","apc-injection","thread-injection","nt-api",{"skillNo":200,"name":201,"nameZh":6,"description":202,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":203,"categories":204,"keywords":205,"publishedAt":49},"01M71HA7H311V5G14WMX58HQSS","processes-hollow-technique-detect","Detect process hollowing (RunPE) by identifying processes with mismatched image paths between PEB and VAD tree, or unmapped PE headers in memory.","https:\u002F\u002Fgithub.com\u002FDCx7C5\u002Fai-marketplace\u002Fblob\u002Fmain\u002Fskills\u002Fwindows\u002Fprocesses\u002Fhollow\u002Ftechnique\u002Fdetect\u002FSKILL.md",[],[206,104,170,207,193,39,208,209,33,118,210,211,212,213,214,215,36,108,216,217],"processes hollow technique detect","tree","memory-forensics","process-hollow","peb","runpe","image","pe-header","in memory","with","mismatched","headers"]