[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6GY7TA9GRD2M19YMKCPZ2P2":3,"skill-same:01M6GY7TA9GRD2M19YMKCPZ2P2":95},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":27,"publishedAt":48,"linkOnly":49,"markdownContent":50,"markdownBody":51,"frontMatter":52,"refName":57,"commitSha":58,"skillDirectory":59,"forksCount":60,"repositoryHtmlUrl":61,"repositoryHomepageUrl":6,"ownerHtmlUrl":62,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":63,"install":64,"resources":77},"01M6GY7TA9GRD2M19YMKCPZ2P2","implementing-aws-security-hub",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.","micsapp\u002Fmicstec-skills","micsapp","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F82411001?v=4","01M6GWCFQ6D3PV8EHNY62NN5VW","01M6GWCFVE1PA5HG0DKC7AMFJ3",4,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002F_universal\u002Fcybersecurity-skills\u002Fskills\u002Fimplementing-aws-security-hub\u002FSKILL.md",[17,22],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",{"categoryNo":23,"categoryName":24,"taxonomyType":25,"taxonomyTypeDesc":26},"01JBSEEDCAT000000000000037","律师与法务","PROFESSION","适用职业",[28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47],"aws","hub","aws security","implementing aws security hub","security","compliance-automation","foundations","security standards","across","aggregates","finding-aggregation","security-standards","aws-security-hub","cspm","security-hub","macie","guardduty","remediation","cloud-security","cybersecurity","2026-11-10 10:12:30",false,"---\nname: implementing-aws-security-hub\ndescription: >\n  This skill covers deploying AWS Security Hub as a centralized cloud security posture\n  management platform that aggregates findings from GuardDuty, Inspector, Macie, and\n  third-party tools. It details enabling security standards like CIS AWS Foundations\n  Benchmark, configuring automated remediation, and building executive dashboards for\n  compliance tracking across multi-account AWS organizations.\ndomain: cybersecurity\nsubdomain: cloud-security\ntags: [aws-security-hub, cspm, compliance-automation, security-standards, finding-aggregation]\nversion: 1.0.0\nauthor: mahipal\nlicense: Apache-2.0\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":53,"author":54,"domain":47,"license":14,"version":55,"subdomain":46,"description":56},[40,41,33,39,38],"mahipal","1.0.0","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.\n","master","3f5d983eb4ef375b749adcd6b07ec03bd82ae8a8","_universal\u002Fcybersecurity-skills\u002Fskills\u002Fimplementing-aws-security-hub",0,"https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills","https:\u002F\u002Fgithub.com\u002Fmicsapp","2026-03-20 11:24:18",{"source":8,"skillName":5,"commands":65,"prompt":75,"zipAvailable":76},[66,69,72],{"tool":67,"command":68},"npx","npx skills add micsapp\u002Fmicstec-skills --skill implementing-aws-security-hub",{"tool":70,"command":71},"bunx","bunx skills add micsapp\u002Fmicstec-skills --skill implementing-aws-security-hub",{"tool":73,"command":74},"pnpm","pnpm dlx skills add micsapp\u002Fmicstec-skills --skill implementing-aws-security-hub","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002F_universal\u002Fcybersecurity-skills\u002Fskills\u002Fimplementing-aws-security-hub\u002FSKILL.md",true,[78,83,89],{"path":79,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":81,"sourceHtmlUrl":82},"LICENSE","许可证",11255,"https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002F_universal\u002Fcybersecurity-skills\u002Fskills\u002Fimplementing-aws-security-hub\u002FLICENSE",{"path":84,"resourceType":85,"resourceTypeDesc":86,"sizeBytes":87,"sourceHtmlUrl":88},"references\u002Fapi-reference.md","REFERENCE","参考文档",2354,"https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002F_universal\u002Fcybersecurity-skills\u002Fskills\u002Fimplementing-aws-security-hub\u002Freferences\u002Fapi-reference.md",{"path":90,"resourceType":91,"resourceTypeDesc":92,"sizeBytes":93,"sourceHtmlUrl":94},"scripts\u002Fagent.py","SCRIPT","脚本",6933,"https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002F_universal\u002Fcybersecurity-skills\u002Fskills\u002Fimplementing-aws-security-hub\u002Fscripts\u002Fagent.py",[96,130,158,178,198,223],{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":100,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":109,"publishedAt":48},"01M6HBTJ02FXBFG9NYEHHYAP52","azure-apim-architecture","Analyzes and explains Azure API Management architecture decisions for enterprise API marketplace implementations using VNet Internal mode, Front Door, hybrid authentication, and multi-environment strategies. Use when discussing APIM component selection, network topology, cost optimization, or comparing alternatives like workspaces vs instances, VNet Internal vs External mode, or Front Door vs Application Gateway.","MIT","https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fcopilot-cli\u002Fcopilot-agent-skills\u002F.github\u002Fskills\u002Fazure-apim-architecture\u002FSKILL.md",[103,106],{"categoryNo":104,"categoryName":105,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":107,"categoryName":108,"taxonomyType":25,"taxonomyTypeDesc":26},"01JBSEEDCAT000000000000030","开发工程师",[110,111,112,113,114,115,116,117,118,119,120,121,122,123,124,125,126,127,128,129],"architecture","azure","azure apim architecture","component","authentication","gateway","topology","Optimization","network","api","team","environment","multi-environment","workspaces","instances","selection","strategies","azure api management","mode","for",{"skillNo":131,"name":132,"nameZh":6,"description":133,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":100,"licenseFileUrl":6,"sourceHtmlUrl":134,"categories":135,"keywords":142,"publishedAt":48},"01M6HBT7J4H082JEEA670B3EQ9","apiops-deployment","Guides deployment of Azure API Management infrastructure using Infrastructure as Code (Bicep\u002FTerraform), CI\u002FCD pipelines (GitHub Actions\u002FAzure DevOps), and APIOps workflows. Use when deploying APIM, creating pipelines, or implementing dev→test→prod promotion strategies.","https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fcopilot-cli\u002Fcopilot-agent-skills\u002F.github\u002Fskills\u002Fapiops-deployment\u002FSKILL.md",[136,137,140,141],{"categoryNo":104,"categoryName":105,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":138,"categoryName":139,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000011","运维与部署",{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":107,"categoryName":108,"taxonomyType":25,"taxonomyTypeDesc":26},[143,144,145,146,111,147,148,149,150,151,152,153,119,120,126,154,155,127,156,157],"deployment","apiops deployment","workflows","azure devops","infrastructure","code","infrastructure as code","actions","ci","github actions","github-actions","as","guides","CI\u002FCD","implementing",{"skillNo":159,"name":160,"nameZh":6,"description":161,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":100,"licenseFileUrl":6,"sourceHtmlUrl":162,"categories":163,"keywords":165,"publishedAt":48},"01M6HBT2HEA23THNE9E00GYQBE","apim-policy-authoring","Creates production-ready Azure API Management policy XML for authentication (OAuth 2.0, JWT validation, subscription keys), rate limiting, CORS configuration, error handling, and API transformations. Use when implementing API security, access control, or request\u002Fresponse processing logic.","https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fcopilot-cli\u002Fcopilot-agent-skills\u002F.github\u002Fskills\u002Fapim-policy-authoring\u002FSKILL.md",[164],{"categoryNo":104,"categoryName":105,"taxonomyType":20,"taxonomyTypeDesc":21},[166,167,168,32,111,114,119,120,169,170,171,172,173,174,175,127,176,177,157,129],"policy","authoring","apim policy authoring","access","use","ready","api security","Access Control","error","processing","cors configuration","production-ready",{"skillNo":179,"name":180,"nameZh":6,"description":181,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":100,"licenseFileUrl":6,"sourceHtmlUrl":182,"categories":183,"keywords":186,"publishedAt":48},"01M6HBSY65SB29J9WE9KYD0K6T","api-security-review","Reviews Azure API Management configurations for security vulnerabilities, OWASP API Security Top 10 compliance, VNet Internal mode validation, Private Link verification, and Azure Security Benchmark alignment. Use when performing security audits, pre-deployment validation, or compliance reviews.","https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fcopilot-cli\u002Fcopilot-agent-skills\u002F.github\u002Fskills\u002Fapi-security-review\u002FSKILL.md",[184,185],{"categoryNo":104,"categoryName":105,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":107,"categoryName":108,"taxonomyType":25,"taxonomyTypeDesc":26},[187,32,188,119,172,189,111,143,190,191,192,193,120,194,127,195,196,197,128,129],"review","security review","api security review","benchmark","verification","owasp","owasp-api","alignment","azure security","reviews","top",{"skillNo":199,"name":200,"nameZh":6,"description":201,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":100,"licenseFileUrl":6,"sourceHtmlUrl":202,"categories":203,"keywords":204,"publishedAt":48},"01M6HBSRW4PDFE6K4F8JYPZQ05","jira-cli","Interact with Jira from the command line to create, list, view, edit, and transition issues, manage sprints and epics, and perform common Jira workflows. Use when the user asks about Jira tasks, tickets, issues, sprints, or needs to manage project work items.","https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fcopilot-cli\u002Fawesome-copilot-agents\u002Fskills\u002Fjira-cli\u002FSKILL.md",[],[205,206,207,145,208,209,210,211,119,212,213,214,215,216,217,218,219,220,221,222],"cli","jira","jira cli","init","tasks","create","issues","common","work","command","edit","list","view","project","project work","token","line","sprints",{"skillNo":224,"name":225,"nameZh":6,"description":226,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":100,"licenseFileUrl":6,"sourceHtmlUrl":227,"categories":228,"keywords":229,"publishedAt":48},"01M6HBSNS3JHMW603G47TWE31H","calculator","Performs arbitrary-precision arithmetic calculations including addition, subtraction, multiplication, division, and exponents. Use when the user asks to calculate, compute, or evaluate math expressions, or when precise decimal arithmetic is needed to avoid floating-point errors.","https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fcopilot-cli\u002Fawesome-copilot-agents\u002Fskills\u002Fcalculator\u002FSKILL.md",[],[225,230,231,232,233,234,235,170,236,237],"npm","js","calculate","node","math","user","compute","errors"]