[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6GXDVABFAQEN7ZN7D6VF3EW":3,"skill-same:01M6GXDVABFAQEN7ZN7D6VF3EW":108},{"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":22,"publishedAt":43,"linkOnly":44,"markdownContent":45,"markdownBody":46,"frontMatter":47,"refName":52,"commitSha":53,"skillDirectory":54,"forksCount":55,"repositoryHtmlUrl":56,"repositoryHomepageUrl":6,"ownerHtmlUrl":57,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":58,"install":59,"resources":72},"01M6GXDVABFAQEN7ZN7D6VF3EW","detecting-aws-guardduty-findings-automation",null,"Automate AWS GuardDuty threat detection findings processing using EventBridge and Lambda to enable real-time incident response, automatic quarantine of compromised resources, and security notification workflows.","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\u002Fdetecting-aws-guardduty-findings-automation\u002FSKILL.md",[17],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42],"detecting","automation","aws","guardduty","detecting aws guardduty findings automation","eventbridge","notification","processing","resources","time","incident","real-time","lambda","cybersecurity","detection","threat-detection","cloud-security","workflows","siem","incident response","2026-11-10 10:12:30",false,"---\nname: detecting-aws-guardduty-findings-automation\ndescription: Automate AWS GuardDuty threat detection findings processing using EventBridge and Lambda to enable real-time incident response, automatic quarantine of compromised resources, and security notification workflows.\ndomain: cybersecurity\nsubdomain: cloud-security\ntags: [aws, guardduty, eventbridge, lambda, threat-detection, automation, incident-response, siem]\nversion: \"1.0\"\nauthor: mahipal\nlicense: Apache-2.0\n---\n\n# Detecting AWS GuardDuty Findings Automation\n\n## Overview\n\nAmazon GuardDuty is a threat detection service that continuously monitors AWS accounts for malicious activity and unauthorized behavior. By integrating GuardDuty with Amazon EventBridge and AWS Lambda, security teams achieve automated, real-time responses to threats, reducing mean time to response (MTTR) from hours to seconds. GuardDuty analyzes VPC Flow Logs, CloudTrail management and data events, DNS logs, EKS audit logs, and S3 data events.\n\n\n## When to Use\n\n- When investigating security incidents that require detecting aws guardduty findings automation\n- When building detection rules or threat hunting queries for this domain\n- When SOC analysts need structured procedures for this analysis type\n- When validating security monitoring coverage for related attack techniques\n\n## Prerequisites\n\n- AWS account with GuardDuty enabled\n- IAM roles for Lambda execution\n- EventBridge configured for GuardDuty events\n- SNS topic for security notifications\n- Security Hub integration (recommended)\n\n## Enable GuardDuty\n\n```bash\n# Enable GuardDuty\naws guardduty create-detector --enable --finding-publishing-frequency FIFTEEN_MINUTES\n\n# Enable additional data sources\naws guardduty update-detector \\\n  --detector-id DETECTOR_ID \\\n  --data-sources '{\n    \"S3Logs\": {\"Enable\": true},\n    \"Kubernetes\": {\"AuditLogs\": {\"Enable\": true}},\n    \"MalwareProtection\": {\"ScanEc2InstanceWithFindings\": {\"EbsVolumes\": true}},\n    \"RuntimeMonitoring\": {\"Enable\": true}\n  }'\n```\n\n## EventBridge Rule Configuration\n\n### Rule for high-severity findings\n\n```json\n{\n  \"source\": [\"aws.guardduty\"],\n  \"detail-type\": [\"GuardDuty Finding\"],\n  \"detail\": {\n    \"severity\": [{\"numeric\": [\">=\", 7.0]}]\n  }\n}\n```\n\n### Create EventBridge rule via CLI\n\n```bash\naws events put-rule \\\n  --name \"guardduty-high-severity\" \\\n  --event-pattern '{\n    \"source\": [\"aws.guardduty\"],\n    \"detail-type\": [\"GuardDuty Finding\"],\n    \"detail\": {\n      \"severity\": [{\"numeric\": [\">=\", 7.0]}]\n    }\n  }'\n\naws events put-targets \\\n  --rule \"guardduty-high-severity\" \\\n  --targets \"Id\"=\"lambda-handler\",\"Arn\"=\"arn:aws:lambda:us-east-1:123456789012:function:guardduty-response\"\n```\n\n## Lambda Automated Response Functions\n\n### EC2 Instance Isolation\n\n```python\nimport boto3\nimport json\nimport os\n\nec2 = boto3.client('ec2')\nsns = boto3.client('sns')\n\nQUARANTINE_SG = os.environ.get('QUARANTINE_SECURITY_GROUP')\nSNS_TOPIC = os.environ.get('SNS_TOPIC_ARN')\n\ndef lambda_handler(event, context):\n    finding = event['detail']\n    finding_type = finding['type']\n    severity = finding['severity']\n    account_id = finding['accountId']\n    region = finding['region']\n\n    # Extract resource information\n    resource = finding.get('resource', {})\n    resource_type = resource.get('resourceType', '')\n\n    if resource_type == 'Instance':\n        instance_id = resource['instanceDetails']['instanceId']\n        instance_tags = {t['key']: t['value']\n                        for t in resource['instanceDetails'].get('tags', [])}\n\n        # Skip if already quarantined\n        if instance_tags.get('SecurityStatus') == 'Quarantined':\n            return {'statusCode': 200, 'body': 'Already quarantined'}\n\n        # Get current security groups for forensics\n        instance = ec2.describe_instances(InstanceIds=[instance_id])\n        current_sgs = [sg['GroupId'] for sg in\n                       instance['Reservations'][0]['Instances'][0]['SecurityGroups']]\n\n        # Tag instance with finding info and original SGs\n        ec2.create_tags(\n            Resources=[instance_id],\n            Tags=[\n                {'Key': 'SecurityStatus', 'Value': 'Quarantined'},\n                {'Key': 'GuardDutyFinding', 'Value': finding_type},\n                {'Key': 'OriginalSecurityGroups', 'Value': ','.join(current_sgs)},\n                {'Key': 'QuarantineTime', 'Value': finding['updatedAt']}\n            ]\n        )\n\n        # Move to quarantine security group (blocks all traffic)\n        if QUARANTINE_SG:\n            ec2.modify_instance_attribute(\n                InstanceId=instance_id,\n                Groups=[QUARANTINE_SG]\n            )\n\n        # Create EBS snapshots for forensics\n        volumes = ec2.describe_volumes(\n            Filters=[{'Name': 'attachment.instance-id', 'Values': [instance_id]}]\n        )\n        for vol in volumes['Volumes']:\n            ec2.create_snapshot(\n                VolumeId=vol['VolumeId'],\n                Description=f'GuardDuty forensic snapshot - {finding_type}',\n                TagSpecifications=[{\n                    'ResourceType': 'snapshot',\n                    'Tags': [\n                        {'Key': 'Purpose', 'Value': 'ForensicCapture'},\n                        {'Key': 'SourceInstance', 'Value': instance_id},\n                        {'Key': 'FindingType', 'Value': finding_type}\n                    ]\n                }]\n            )\n\n        # Notify security team\n        sns.publish(\n            TopicArn=SNS_TOPIC,\n            Subject=f'[GuardDuty] {finding_type} - Instance {instance_id} Quarantined',\n            Message=json.dumps({\n                'action': 'instance_quarantined',\n                'instance_id': instance_id,\n                'finding_type': finding_type,\n                'severity': severity,\n                'account': account_id,\n                'region': region,\n                'original_security_groups': current_sgs,\n                'description': finding.get('description', '')\n            }, indent=2)\n        )\n\n        return {\n            'statusCode': 200,\n            'body': f'Instance {instance_id} quarantined and snapshots created'\n        }\n\n    return {'statusCode': 200, 'body': 'Non-EC2 finding processed'}\n```\n\n### IAM Credential Compromise Response\n\n```python\nimport boto3\nimport json\nimport os\n\niam = boto3.client('iam')\nsns = boto3.client('sns')\n\nSNS_TOPIC = os.environ.get('SNS_TOPIC_ARN')\n\ndef lambda_handler(event, context):\n    finding = event['detail']\n    finding_type = finding['type']\n\n    if 'IAMUser' not in finding_type and 'UnauthorizedAccess' not in finding_type:\n        return {'statusCode': 200, 'body': 'Not an IAM finding'}\n\n    resource = finding.get('resource', {})\n    access_key_details = resource.get('accessKeyDetails', {})\n    user_name = access_key_details.get('userName', '')\n    access_key_id = access_key_details.get('accessKeyId', '')\n\n    if not user_name:\n        return {'statusCode': 200, 'body': 'No user identified'}\n\n    actions_taken = []\n\n    # Deactivate the compromised access key\n    if access_key_id and access_key_id != 'GeneratedFindingAccessKeyId':\n        try:\n            iam.update_access_key(\n                UserName=user_name,\n                AccessKeyId=access_key_id,\n                Status='Inactive'\n            )\n            actions_taken.append(f'Deactivated access key {access_key_id}')\n        except Exception as e:\n            actions_taken.append(f'Failed to deactivate key: {str(e)}')\n\n    # Attach deny-all policy to user\n    deny_policy = {\n        \"Version\": \"2012-10-17\",\n        \"Statement\": [{\n            \"Effect\": \"Deny\",\n            \"Action\": \"*\",\n            \"Resource\": \"*\"\n        }]\n    }\n\n    try:\n        iam.put_user_policy(\n            UserName=user_name,\n            PolicyName='GuardDuty-DenyAll-Quarantine',\n            PolicyDocument=json.dumps(deny_policy)\n        )\n        actions_taken.append(f'Applied deny-all policy to {user_name}')\n    except Exception as e:\n        actions_taken.append(f'Failed to apply deny policy: {str(e)}')\n\n    # Notify\n    sns.publish(\n        TopicArn=SNS_TOPIC,\n        Subject=f'[GuardDuty] IAM Compromise - {user_name}',\n        Message=json.dumps({\n            'finding_type': finding_type,\n            'user': user_name,\n            'access_key': access_key_id,\n            'actions_taken': actions_taken,\n            'severity': finding['severity']\n        }, indent=2)\n    )\n\n    return {'statusCode': 200, 'body': json.dumps(actions_taken)}\n```\n\n## Terraform Deployment\n\n```hcl\nresource \"aws_guardduty_detector\" \"main\" {\n  enable = true\n  finding_publishing_frequency = \"FIFTEEN_MINUTES\"\n\n  datasources {\n    s3_logs { enable = true }\n    kubernetes { audit_logs { enable = true } }\n    malware_protection {\n      scan_ec2_instance_with_findings {\n        ebs_volumes { enable = true }\n      }\n    }\n  }\n}\n\nresource \"aws_cloudwatch_event_rule\" \"guardduty_high\" {\n  name        = \"guardduty-high-severity\"\n  description = \"GuardDuty high severity findings\"\n\n  event_pattern = jsonencode({\n    source      = [\"aws.guardduty\"]\n    detail-type = [\"GuardDuty Finding\"]\n    detail = {\n      severity = [{ numeric = [\">=\", 7.0] }]\n    }\n  })\n}\n\nresource \"aws_cloudwatch_event_target\" \"lambda\" {\n  rule = aws_cloudwatch_event_rule.guardduty_high.name\n  arn  = aws_lambda_function.guardduty_response.arn\n}\n```\n\n## Finding Categories\n\n| Category | Severity Range | Examples |\n|----------|---------------|---------|\n| Backdoor | 5.0 - 8.0 | Backdoor:EC2\u002FC&CActivity |\n| CryptoCurrency | 5.0 - 8.0 | CryptoCurrency:EC2\u002FBitcoinTool |\n| Trojan | 5.0 - 8.0 | Trojan:EC2\u002FBlackholeTraffic |\n| UnauthorizedAccess | 5.0 - 8.0 | UnauthorizedAccess:IAMUser\u002FConsoleLogin |\n| Recon | 2.0 - 5.0 | Recon:EC2\u002FPortProbeUnprotected |\n| Persistence | 5.0 - 8.0 | Persistence:IAMUser\u002FAnomalousBehavior |\n\n## Multi-Account Setup\n\n```bash\n# Designate GuardDuty administrator\naws guardduty enable-organization-admin-account \\\n  --admin-account-id 111111111111\n\n# Auto-enable for new accounts\naws guardduty update-organization-configuration \\\n  --detector-id DETECTOR_ID \\\n  --auto-enable\n```\n\n## References\n\n- AWS GuardDuty Best Practices: https:\u002F\u002Faws.github.io\u002Faws-security-services-best-practices\u002Fguides\u002Fguardduty\u002F\n- EventBridge Integration: https:\u002F\u002Fdocs.aws.amazon.com\u002Fguardduty\u002Flatest\u002Fug\u002Fguardduty_findings_eventbridge.html\n- GuardDuty Finding Types Reference\n","# Detecting AWS GuardDuty Findings Automation\n\n## Overview\n\nAmazon GuardDuty is a threat detection service that continuously monitors AWS accounts for malicious activity and unauthorized behavior. By integrating GuardDuty with Amazon EventBridge and AWS Lambda, security teams achieve automated, real-time responses to threats, reducing mean time to response (MTTR) from hours to seconds. GuardDuty analyzes VPC Flow Logs, CloudTrail management and data events, DNS logs, EKS audit logs, and S3 data events.\n\n\n## When to Use\n\n- When investigating security incidents that require detecting aws guardduty findings automation\n- When building detection rules or threat hunting queries for this domain\n- When SOC analysts need structured procedures for this analysis type\n- When validating security monitoring coverage for related attack techniques\n\n## Prerequisites\n\n- AWS account with GuardDuty enabled\n- IAM roles for Lambda execution\n- EventBridge configured for GuardDuty events\n- SNS topic for security notifications\n- Security Hub integration (recommended)\n\n## Enable GuardDuty\n\n```bash\n# Enable GuardDuty\naws guardduty create-detector --enable --finding-publishing-frequency FIFTEEN_MINUTES\n\n# Enable additional data sources\naws guardduty update-detector \\\n  --detector-id DETECTOR_ID \\\n  --data-sources '{\n    \"S3Logs\": {\"Enable\": true},\n    \"Kubernetes\": {\"AuditLogs\": {\"Enable\": true}},\n    \"MalwareProtection\": {\"ScanEc2InstanceWithFindings\": {\"EbsVolumes\": true}},\n    \"RuntimeMonitoring\": {\"Enable\": true}\n  }'\n```\n\n## EventBridge Rule Configuration\n\n### Rule for high-severity findings\n\n```json\n{\n  \"source\": [\"aws.guardduty\"],\n  \"detail-type\": [\"GuardDuty Finding\"],\n  \"detail\": {\n    \"severity\": [{\"numeric\": [\">=\", 7.0]}]\n  }\n}\n```\n\n### Create EventBridge rule via CLI\n\n```bash\naws events put-rule \\\n  --name \"guardduty-high-severity\" \\\n  --event-pattern '{\n    \"source\": [\"aws.guardduty\"],\n    \"detail-type\": [\"GuardDuty Finding\"],\n    \"detail\": {\n      \"severity\": [{\"numeric\": [\">=\", 7.0]}]\n    }\n  }'\n\naws events put-targets \\\n  --rule \"guardduty-high-severity\" \\\n  --targets \"Id\"=\"lambda-handler\",\"Arn\"=\"arn:aws:lambda:us-east-1:123456789012:function:guardduty-response\"\n```\n\n## Lambda Automated Response Functions\n\n### EC2 Instance Isolation\n\n```python\nimport boto3\nimport json\nimport os\n\nec2 = boto3.client('ec2')\nsns = boto3.client('sns')\n\nQUARANTINE_SG = os.environ.get('QUARANTINE_SECURITY_GROUP')\nSNS_TOPIC = os.environ.get('SNS_TOPIC_ARN')\n\ndef lambda_handler(event, context):\n    finding = event['detail']\n    finding_type = finding['type']\n    severity = finding['severity']\n    account_id = finding['accountId']\n    region = finding['region']\n\n    # Extract resource information\n    resource = finding.get('resource', {})\n    resource_type = resource.get('resourceType', '')\n\n    if resource_type == 'Instance':\n        instance_id = resource['instanceDetails']['instanceId']\n        instance_tags = {t['key']: t['value']\n                        for t in resource['instanceDetails'].get('tags', [])}\n\n        # Skip if already quarantined\n        if instance_tags.get('SecurityStatus') == 'Quarantined':\n            return {'statusCode': 200, 'body': 'Already quarantined'}\n\n        # Get current security groups for forensics\n        instance = ec2.describe_instances(InstanceIds=[instance_id])\n        current_sgs = [sg['GroupId'] for sg in\n                       instance['Reservations'][0]['Instances'][0]['SecurityGroups']]\n\n        # Tag instance with finding info and original SGs\n        ec2.create_tags(\n            Resources=[instance_id],\n            Tags=[\n                {'Key': 'SecurityStatus', 'Value': 'Quarantined'},\n                {'Key': 'GuardDutyFinding', 'Value': finding_type},\n                {'Key': 'OriginalSecurityGroups', 'Value': ','.join(current_sgs)},\n                {'Key': 'QuarantineTime', 'Value': finding['updatedAt']}\n            ]\n        )\n\n        # Move to quarantine security group (blocks all traffic)\n        if QUARANTINE_SG:\n            ec2.modify_instance_attribute(\n                InstanceId=instance_id,\n                Groups=[QUARANTINE_SG]\n            )\n\n        # Create EBS snapshots for forensics\n        volumes = ec2.describe_volumes(\n            Filters=[{'Name': 'attachment.instance-id', 'Values': [instance_id]}]\n        )\n        for vol in volumes['Volumes']:\n            ec2.create_snapshot(\n                VolumeId=vol['VolumeId'],\n                Description=f'GuardDuty forensic snapshot - {finding_type}',\n                TagSpecifications=[{\n                    'ResourceType': 'snapshot',\n                    'Tags': [\n                        {'Key': 'Purpose', 'Value': 'ForensicCapture'},\n                        {'Key': 'SourceInstance', 'Value': instance_id},\n                        {'Key': 'FindingType', 'Value': finding_type}\n                    ]\n                }]\n            )\n\n        # Notify security team\n        sns.publish(\n            TopicArn=SNS_TOPIC,\n            Subject=f'[GuardDuty] {finding_type} - Instance {instance_id} Quarantined',\n            Message=json.dumps({\n                'action': 'instance_quarantined',\n                'instance_id': instance_id,\n                'finding_type': finding_type,\n                'severity': severity,\n                'account': account_id,\n                'region': region,\n                'original_security_groups': current_sgs,\n                'description': finding.get('description', '')\n            }, indent=2)\n        )\n\n        return {\n            'statusCode': 200,\n            'body': f'Instance {instance_id} quarantined and snapshots created'\n        }\n\n    return {'statusCode': 200, 'body': 'Non-EC2 finding processed'}\n```\n\n### IAM Credential Compromise Response\n\n```python\nimport boto3\nimport json\nimport os\n\niam = boto3.client('iam')\nsns = boto3.client('sns')\n\nSNS_TOPIC = os.environ.get('SNS_TOPIC_ARN')\n\ndef lambda_handler(event, context):\n    finding = event['detail']\n    finding_type = finding['type']\n\n    if 'IAMUser' not in finding_type and 'UnauthorizedAccess' not in finding_type:\n        return {'statusCode': 200, 'body': 'Not an IAM finding'}\n\n    resource = finding.get('resource', {})\n    access_key_details = resource.get('accessKeyDetails', {})\n    user_name = access_key_details.get('userName', '')\n    access_key_id = access_key_details.get('accessKeyId', '')\n\n    if not user_name:\n        return {'statusCode': 200, 'body': 'No user identified'}\n\n    actions_taken = []\n\n    # Deactivate the compromised access key\n    if access_key_id and access_key_id != 'GeneratedFindingAccessKeyId':\n        try:\n            iam.update_access_key(\n                UserName=user_name,\n                AccessKeyId=access_key_id,\n                Status='Inactive'\n            )\n            actions_taken.append(f'Deactivated access key {access_key_id}')\n        except Exception as e:\n            actions_taken.append(f'Failed to deactivate key: {str(e)}')\n\n    # Attach deny-all policy to user\n    deny_policy = {\n        \"Version\": \"2012-10-17\",\n        \"Statement\": [{\n            \"Effect\": \"Deny\",\n            \"Action\": \"*\",\n            \"Resource\": \"*\"\n        }]\n    }\n\n    try:\n        iam.put_user_policy(\n            UserName=user_name,\n            PolicyName='GuardDuty-DenyAll-Quarantine',\n            PolicyDocument=json.dumps(deny_policy)\n        )\n        actions_taken.append(f'Applied deny-all policy to {user_name}')\n    except Exception as e:\n        actions_taken.append(f'Failed to apply deny policy: {str(e)}')\n\n    # Notify\n    sns.publish(\n        TopicArn=SNS_TOPIC,\n        Subject=f'[GuardDuty] IAM Compromise - {user_name}',\n        Message=json.dumps({\n            'finding_type': finding_type,\n            'user': user_name,\n            'access_key': access_key_id,\n            'actions_taken': actions_taken,\n            'severity': finding['severity']\n        }, indent=2)\n    )\n\n    return {'statusCode': 200, 'body': json.dumps(actions_taken)}\n```\n\n## Terraform Deployment\n\n```hcl\nresource \"aws_guardduty_detector\" \"main\" {\n  enable = true\n  finding_publishing_frequency = \"FIFTEEN_MINUTES\"\n\n  datasources {\n    s3_logs { enable = true }\n    kubernetes { audit_logs { enable = true } }\n    malware_protection {\n      scan_ec2_instance_with_findings {\n        ebs_volumes { enable = true }\n      }\n    }\n  }\n}\n\nresource \"aws_cloudwatch_event_rule\" \"guardduty_high\" {\n  name        = \"guardduty-high-severity\"\n  description = \"GuardDuty high severity findings\"\n\n  event_pattern = jsonencode({\n    source      = [\"aws.guardduty\"]\n    detail-type = [\"GuardDuty Finding\"]\n    detail = {\n      severity = [{ numeric = [\">=\", 7.0] }]\n    }\n  })\n}\n\nresource \"aws_cloudwatch_event_target\" \"lambda\" {\n  rule = aws_cloudwatch_event_rule.guardduty_high.name\n  arn  = aws_lambda_function.guardduty_response.arn\n}\n```\n\n## Finding Categories\n\n| Category | Severity Range | Examples |\n|----------|---------------|---------|\n| Backdoor | 5.0 - 8.0 | Backdoor:EC2\u002FC&CActivity |\n| CryptoCurrency | 5.0 - 8.0 | CryptoCurrency:EC2\u002FBitcoinTool |\n| Trojan | 5.0 - 8.0 | Trojan:EC2\u002FBlackholeTraffic |\n| UnauthorizedAccess | 5.0 - 8.0 | UnauthorizedAccess:IAMUser\u002FConsoleLogin |\n| Recon | 2.0 - 5.0 | Recon:EC2\u002FPortProbeUnprotected |\n| Persistence | 5.0 - 8.0 | Persistence:IAMUser\u002FAnomalousBehavior |\n\n## Multi-Account Setup\n\n```bash\n# Designate GuardDuty administrator\naws guardduty enable-organization-admin-account \\\n  --admin-account-id 111111111111\n\n# Auto-enable for new accounts\naws guardduty update-organization-configuration \\\n  --detector-id DETECTOR_ID \\\n  --auto-enable\n```\n\n## References\n\n- AWS GuardDuty Best Practices: https:\u002F\u002Faws.github.io\u002Faws-security-services-best-practices\u002Fguides\u002Fguardduty\u002F\n- EventBridge Integration: https:\u002F\u002Fdocs.aws.amazon.com\u002Fguardduty\u002Flatest\u002Fug\u002Fguardduty_findings_eventbridge.html\n- GuardDuty Finding Types Reference\n",{"name":5,"tags":48,"author":50,"domain":36,"license":14,"version":51,"subdomain":39,"description":7},[25,26,28,35,38,24,49,41],"incident-response","mahipal","1.0","master","3f5d983eb4ef375b749adcd6b07ec03bd82ae8a8","_universal\u002Fcybersecurity-skills\u002Fskills\u002Fdetecting-aws-guardduty-findings-automation",0,"https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills","https:\u002F\u002Fgithub.com\u002Fmicsapp","2026-03-20 11:24:18",{"source":8,"skillName":5,"commands":60,"prompt":70,"zipAvailable":71},[61,64,67],{"tool":62,"command":63},"npx","npx skills add micsapp\u002Fmicstec-skills --skill detecting-aws-guardduty-findings-automation",{"tool":65,"command":66},"bunx","bunx skills add micsapp\u002Fmicstec-skills --skill detecting-aws-guardduty-findings-automation",{"tool":68,"command":69},"pnpm","pnpm dlx skills add micsapp\u002Fmicstec-skills --skill detecting-aws-guardduty-findings-automation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002F_universal\u002Fcybersecurity-skills\u002Fskills\u002Fdetecting-aws-guardduty-findings-automation\u002FSKILL.md",true,[73,79,84,90,94,98,104],{"path":74,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":77,"sourceHtmlUrl":78},"assets\u002Ftemplate.md","ASSET","资产文件",784,"https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002F_universal\u002Fcybersecurity-skills\u002Fskills\u002Fdetecting-aws-guardduty-findings-automation\u002Fassets\u002Ftemplate.md",{"path":80,"resourceType":80,"resourceTypeDesc":81,"sizeBytes":82,"sourceHtmlUrl":83},"LICENSE","许可证",11255,"https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002F_universal\u002Fcybersecurity-skills\u002Fskills\u002Fdetecting-aws-guardduty-findings-automation\u002FLICENSE",{"path":85,"resourceType":86,"resourceTypeDesc":87,"sizeBytes":88,"sourceHtmlUrl":89},"references\u002Fapi-reference.md","REFERENCE","参考文档",2450,"https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002F_universal\u002Fcybersecurity-skills\u002Fskills\u002Fdetecting-aws-guardduty-findings-automation\u002Freferences\u002Fapi-reference.md",{"path":91,"resourceType":86,"resourceTypeDesc":87,"sizeBytes":92,"sourceHtmlUrl":93},"references\u002Fstandards.md",668,"https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002F_universal\u002Fcybersecurity-skills\u002Fskills\u002Fdetecting-aws-guardduty-findings-automation\u002Freferences\u002Fstandards.md",{"path":95,"resourceType":86,"resourceTypeDesc":87,"sizeBytes":96,"sourceHtmlUrl":97},"references\u002Fworkflows.md",693,"https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002F_universal\u002Fcybersecurity-skills\u002Fskills\u002Fdetecting-aws-guardduty-findings-automation\u002Freferences\u002Fworkflows.md",{"path":99,"resourceType":100,"resourceTypeDesc":101,"sizeBytes":102,"sourceHtmlUrl":103},"scripts\u002Fagent.py","SCRIPT","脚本",7106,"https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002F_universal\u002Fcybersecurity-skills\u002Fskills\u002Fdetecting-aws-guardduty-findings-automation\u002Fscripts\u002Fagent.py",{"path":105,"resourceType":100,"resourceTypeDesc":101,"sizeBytes":106,"sourceHtmlUrl":107},"scripts\u002Fprocess.py",4087,"https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002F_universal\u002Fcybersecurity-skills\u002Fskills\u002Fdetecting-aws-guardduty-findings-automation\u002Fscripts\u002Fprocess.py",[109,145,172,192,212,237],{"skillNo":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":113,"licenseFileUrl":6,"sourceHtmlUrl":114,"categories":115,"keywords":124,"publishedAt":43},"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",[116,119],{"categoryNo":117,"categoryName":118,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":120,"categoryName":121,"taxonomyType":122,"taxonomyTypeDesc":123},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[125,126,127,128,129,130,131,132,133,134,135,136,137,138,139,140,141,142,143,144],"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":146,"name":147,"nameZh":6,"description":148,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":113,"licenseFileUrl":6,"sourceHtmlUrl":149,"categories":150,"keywords":157,"publishedAt":43},"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",[151,152,155,156],{"categoryNo":117,"categoryName":118,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":153,"categoryName":154,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000011","运维与部署",{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":120,"categoryName":121,"taxonomyType":122,"taxonomyTypeDesc":123},[158,159,40,160,126,161,162,163,164,165,166,167,134,135,141,168,169,142,170,171],"deployment","apiops deployment","azure devops","infrastructure","code","infrastructure as code","actions","ci","github actions","github-actions","as","guides","CI\u002FCD","implementing",{"skillNo":173,"name":174,"nameZh":6,"description":175,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":113,"licenseFileUrl":6,"sourceHtmlUrl":176,"categories":177,"keywords":179,"publishedAt":43},"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",[178],{"categoryNo":117,"categoryName":118,"taxonomyType":20,"taxonomyTypeDesc":21},[180,181,182,183,126,129,134,135,184,185,186,187,188,189,30,142,190,191,171,144],"policy","authoring","apim policy authoring","security","access","use","ready","api security","Access Control","error","cors configuration","production-ready",{"skillNo":193,"name":194,"nameZh":6,"description":195,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":113,"licenseFileUrl":6,"sourceHtmlUrl":196,"categories":197,"keywords":200,"publishedAt":43},"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",[198,199],{"categoryNo":117,"categoryName":118,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":120,"categoryName":121,"taxonomyType":122,"taxonomyTypeDesc":123},[201,183,202,134,187,203,126,158,204,205,206,207,135,208,142,209,210,211,143,144],"review","security review","api security review","benchmark","verification","owasp","owasp-api","alignment","azure security","reviews","top",{"skillNo":213,"name":214,"nameZh":6,"description":215,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":113,"licenseFileUrl":6,"sourceHtmlUrl":216,"categories":217,"keywords":218,"publishedAt":43},"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",[],[219,220,221,40,222,223,224,225,134,226,227,228,229,230,231,232,233,234,235,236],"cli","jira","jira cli","init","tasks","create","issues","common","work","command","edit","list","view","project","project work","token","line","sprints",{"skillNo":238,"name":239,"nameZh":6,"description":240,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":113,"licenseFileUrl":6,"sourceHtmlUrl":241,"categories":242,"keywords":243,"publishedAt":43},"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",[],[239,244,245,246,247,248,249,185,250,251],"npm","js","calculate","node","math","user","compute","errors"]