[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6HE4TKATP3H6ZVPTHGCHKS3":3,"skill-same:01M6HE4TKATP3H6ZVPTHGCHKS3":121},{"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":23,"publishedAt":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":64,"commitSha":65,"skillDirectory":66,"forksCount":67,"repositoryHtmlUrl":68,"repositoryHomepageUrl":6,"ownerHtmlUrl":69,"ownerBlogUrl":6,"ownerDescription":70,"updatedAt":71,"install":72,"resources":85},"01M6HE4TKATP3H6ZVPTHGCHKS3","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.","HenriqueMC17\u002Fagente-core","HenriqueMC17","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F206460478?v=4","01M6HB63HBBF18AC4H09XTB549","Henrique Monteiro Cardoso","01M6HB63NGSQXWKWCFWW2B20W0",1,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fdetecting-aws-guardduty-findings-automation\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"detecting","automation","aws","guardduty","detecting aws guardduty findings automation","lambda","processing","resources","de","time","incident","cm","t1078","cybersecurity","eventbridge","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:\n- aws\n- guardduty\n- eventbridge\n- lambda\n- threat-detection\n- automation\n- incident-response\n- siem\nversion: '1.0'\nauthor: mahipal\nlicense: Apache-2.0\nnist_csf:\n- PR.IR-01\n- ID.AM-08\n- GV.SC-06\n- DE.CM-01\nmitre_attack:\n- T1078.004\n- T1496\n- T1580\n- T1530\n- T1110\ncategory: detecting-aws-guardduty-findings-automation\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":49,"author":51,"domain":37,"license":15,"version":52,"category":5,"nist_csf":53,"subdomain":40,"description":7,"mitre_attack":58},[26,27,38,29,39,25,50,42],"incident-response","mahipal","1.0",[54,55,56,57],"PR.IR-01","ID.AM-08","GV.SC-06","DE.CM-01",[59,60,61,62,63],"T1078.004","T1496","T1580","T1530","T1110","main","5eea5b3296f4673b5f481e8bcc1ba76281149f16","modules\u002Fdetecting-aws-guardduty-findings-automation",0,"https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core","https:\u002F\u002Fgithub.com\u002FHenriqueMC17","Qualquer tecnologia suficientemente avançada é indistinguível da mágica.","2026-09-28 22:40:38",{"source":8,"skillName":5,"commands":73,"prompt":83,"zipAvailable":84},[74,77,80],{"tool":75,"command":76},"npx","npx skills add HenriqueMC17\u002Fagente-core --skill detecting-aws-guardduty-findings-automation",{"tool":78,"command":79},"bunx","bunx skills add HenriqueMC17\u002Fagente-core --skill detecting-aws-guardduty-findings-automation",{"tool":81,"command":82},"pnpm","pnpm dlx skills add HenriqueMC17\u002Fagente-core --skill detecting-aws-guardduty-findings-automation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fdetecting-aws-guardduty-findings-automation\u002FSKILL.md",true,[86,92,97,103,107,111,117],{"path":87,"resourceType":88,"resourceTypeDesc":89,"sizeBytes":90,"sourceHtmlUrl":91},"assets\u002Ftemplate.md","ASSET","资产文件",784,"https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fdetecting-aws-guardduty-findings-automation\u002Fassets\u002Ftemplate.md",{"path":93,"resourceType":93,"resourceTypeDesc":94,"sizeBytes":95,"sourceHtmlUrl":96},"LICENSE","许可证",11255,"https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fdetecting-aws-guardduty-findings-automation\u002FLICENSE",{"path":98,"resourceType":99,"resourceTypeDesc":100,"sizeBytes":101,"sourceHtmlUrl":102},"references\u002Fapi-reference.md","REFERENCE","参考文档",2450,"https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fdetecting-aws-guardduty-findings-automation\u002Freferences\u002Fapi-reference.md",{"path":104,"resourceType":99,"resourceTypeDesc":100,"sizeBytes":105,"sourceHtmlUrl":106},"references\u002Fstandards.md",668,"https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fdetecting-aws-guardduty-findings-automation\u002Freferences\u002Fstandards.md",{"path":108,"resourceType":99,"resourceTypeDesc":100,"sizeBytes":109,"sourceHtmlUrl":110},"references\u002Fworkflows.md",693,"https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fdetecting-aws-guardduty-findings-automation\u002Freferences\u002Fworkflows.md",{"path":112,"resourceType":113,"resourceTypeDesc":114,"sizeBytes":115,"sourceHtmlUrl":116},"scripts\u002Fagent.py","SCRIPT","脚本",7106,"https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fdetecting-aws-guardduty-findings-automation\u002Fscripts\u002Fagent.py",{"path":118,"resourceType":113,"resourceTypeDesc":114,"sizeBytes":119,"sourceHtmlUrl":120},"scripts\u002Fprocess.py",4087,"https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fdetecting-aws-guardduty-findings-automation\u002Fscripts\u002Fprocess.py",[122,148,174,197,213,231],{"skillNo":123,"name":124,"nameZh":6,"description":125,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":126,"categories":127,"keywords":131,"publishedAt":44},"01M6HPFF0RCN0X6WT5EBSV71GY","validating-backup-integrity-for-recovery","Validate backup integrity through cryptographic hash verification, automated restore testing, corruption detection, and recoverability checks to ensure backups are reliable for disaster recovery and ransomware response scenarios.","https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fvalidating-backup-integrity-for-recovery\u002FSKILL.md",[128],{"categoryNo":129,"categoryName":130,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",[132,133,134,135,136,137,37,138,139,140,50,141,142,36,143,144,145,34,146,147],"integrity","backup","recovery","validating backup integrity for recovery","for","testing","validate","verification","hash-verification","ransomware","detection","t1490","disaster-recovery","restore","disaster recovery","ransomware response",{"skillNo":149,"name":150,"nameZh":6,"description":151,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":152,"categories":153,"keywords":154,"publishedAt":44},"01M6HPFAWJVFK25Q33K3T7WQ8G","triaging-vulnerabilities-with-ssvc-framework","Triage and prioritize vulnerabilities using CISA's Stakeholder-Specific Vulnerability Categorization (SSVC) decision tree framework to produce actionable remediation priorities.","https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Ftriaging-vulnerabilities-with-ssvc-framework\u002FSKILL.md",[],[155,156,157,158,159,37,160,161,162,163,164,165,166,167,168,169,170,171,172,173],"vulnerabilities","framework","ssvc","triaging vulnerabilities with ssvc framework","with","triage and prioritize","CISA","vulnerability-management","risk-management","cvss","remediation","vulnerability","prioritization","decision-tree","prioritize","decision","priorities","actionable","tree",{"skillNo":175,"name":176,"nameZh":6,"description":177,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":178,"categories":179,"keywords":180,"publishedAt":44},"01M6HPF6JS9X72WP59094H3ASQ","triaging-security-incident","Performs initial triage of security incidents to determine severity, scope, and required response actions using the NIST SP 800-61r3 and SANS PICERL frameworks. Classifies incidents by type, assigns priority based on business impact, and routes...","https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Ftriaging-security-incident\u002FSKILL.md",[],[181,182,34,37,183,184,185,36,143,186,187,188,189,190,191,192,193,194,195,196],"security","triaging security incident","actions","soc","NIST","analysis","severity-classification","incident-triage","SANS-PICERL","SOC-operations","picerl","conversion","isolation","scope","impact","consistency",{"skillNo":198,"name":199,"nameZh":6,"description":200,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":201,"categories":202,"keywords":203,"publishedAt":44},"01M6HPF2EX6ZYNYYHKBRJN7GEF","triaging-security-incident-with-ir-playbook","Classify and prioritize security incidents using structured IR playbooks to determine severity, assign response teams, and initiate appropriate response procedures.","https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Ftriaging-security-incident-with-ir-playbook\u002FSKILL.md",[],[181,204,205,182,34,159,37,206,184,50,207,208,36,143,209,187,169,210,211,212],"playbook","triaging security incident with ir playbook","teams","IR-playbook","severity","classification","classify","incidents","initiate",{"skillNo":214,"name":215,"nameZh":6,"description":216,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":217,"categories":218,"keywords":219,"publishedAt":44},"01M6HPEY9XPGE7X95AG4XJFQAW","triaging-security-alerts-in-splunk","Triages security alerts in Splunk Enterprise Security by classifying severity, investigating notable events, correlating related telemetry, and making escalation or closure decisions using SPL queries and the Incident Review dashboard. Use when...","https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Ftriaging-security-alerts-in-splunk\u002FSKILL.md",[],[181,220,221,222,223,224,37,42,225,226,184,227,36,228,229,230,190,35,34,32],"security alerts","splunk","triaging security alerts in splunk","alerts","review","dashboard","search","correlation-search","t1566","notable-events","incident-review",{"skillNo":232,"name":233,"nameZh":6,"description":234,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":235,"categories":236,"keywords":237,"publishedAt":44},"01M6HPET6XGEPEJPN7V032JGZ0","tracking-threat-actor-infrastructure","Threat actor infrastructure tracking involves monitoring and mapping adversary-controlled assets including command-and-control (C2) servers, phishing domains, exploit kit hosts, bulletproof hosting, a","https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Ftracking-threat-actor-infrastructure\u002FSKILL.md",[],[238,239,240,241,37,242,243,244,245,246,247,228,248,249,35,250,32,251,252,253],"infrastructure","tracking threat actor infrastructure","tracking","threat","monitoring","mitre-attack","threat-actor","threat-intelligence","command-and-control","dns","command","exploit","intelligence","domains","kit","hosts"]