[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6AE9M84ZP9P52V4V95A48AV":3,"skill-same:01M6AE9M84ZP9P52V4V95A48AV":123},{"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":69,"ownerHtmlUrl":70,"ownerBlogUrl":71,"ownerDescription":72,"updatedAt":73,"install":74,"resources":87},"01M6AE9M84ZP9P52V4V95A48AV","detecting-aws-guardduty-findings-automation",null,"Build automated AWS GuardDuty finding response pipelines using EventBridge and Lambda to trigger real-time incident response, automatically quarantine compromised resources, and route security notifications. Use when designing automated remediation playbooks for GuardDuty findings across VPC Flow Logs, CloudTrail, DNS, EKS, or S3 data events, or when reducing mean time to respond to cloud threats.","mukul975\u002FAnthropic-Cybersecurity-Skills","mukul975","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F42860185?v=4","01M6ADEQR8T5M4EEG6C67BQCWF","Mahipal","01M6ADJPMYWG1E5GM1FWBE3128",35925,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\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 aws guardduty findings automation","automation","aws","threat-detection","lambda","eventbridge","guardduty","remediation","eks","data","flow","security","dns","cloud-security","notifications","logs","pr","siem","incident response","cybersecurity","2026-11-10 10:12:30",false,"---\nname: detecting-aws-guardduty-findings-automation\ndescription: Build automated AWS GuardDuty finding response pipelines using EventBridge\n  and Lambda to trigger real-time incident response, automatically quarantine compromised\n  resources, and route security notifications. Use when designing automated remediation\n  playbooks for GuardDuty findings across VPC Flow Logs, CloudTrail, DNS, EKS, or S3\n  data events, or when reducing mean time to respond to cloud threats.\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\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":49,"author":51,"domain":43,"license":15,"version":52,"nist_csf":53,"subdomain":37,"description":7,"mitre_attack":58},[26,30,29,28,27,25,50,41],"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","54a798831d2266a3ca61ce68a7acb80b81160d57","skills\u002Fdetecting-aws-guardduty-findings-automation",4384,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills","https:\u002F\u002Fmahipal.engineer\u002FAnthropic-Cybersecurity-Skills\u002F","https:\u002F\u002Fgithub.com\u002Fmukul975","Mahipal.engineer","🔐 Cybersecurity | 💻 Dev | 📷 Street Photographer\r\n🎓 MSc | 📚 Research & AI Security","2026-08-31 12:32:44",{"source":8,"skillName":5,"commands":75,"prompt":85,"zipAvailable":86},[76,79,82],{"tool":77,"command":78},"npx","npx skills add mukul975\u002FAnthropic-Cybersecurity-Skills --skill detecting-aws-guardduty-findings-automation",{"tool":80,"command":81},"bunx","bunx skills add mukul975\u002FAnthropic-Cybersecurity-Skills --skill detecting-aws-guardduty-findings-automation",{"tool":83,"command":84},"pnpm","pnpm dlx skills add mukul975\u002FAnthropic-Cybersecurity-Skills --skill detecting-aws-guardduty-findings-automation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fdetecting-aws-guardduty-findings-automation\u002FSKILL.md",true,[88,94,99,105,109,113,119],{"path":89,"resourceType":90,"resourceTypeDesc":91,"sizeBytes":92,"sourceHtmlUrl":93},"assets\u002Ftemplate.md","ASSET","资产文件",784,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fdetecting-aws-guardduty-findings-automation\u002Fassets\u002Ftemplate.md",{"path":95,"resourceType":95,"resourceTypeDesc":96,"sizeBytes":97,"sourceHtmlUrl":98},"LICENSE","许可证",11255,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fdetecting-aws-guardduty-findings-automation\u002FLICENSE",{"path":100,"resourceType":101,"resourceTypeDesc":102,"sizeBytes":103,"sourceHtmlUrl":104},"references\u002Fapi-reference.md","REFERENCE","参考文档",2450,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fdetecting-aws-guardduty-findings-automation\u002Freferences\u002Fapi-reference.md",{"path":106,"resourceType":101,"resourceTypeDesc":102,"sizeBytes":107,"sourceHtmlUrl":108},"references\u002Fstandards.md",668,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fdetecting-aws-guardduty-findings-automation\u002Freferences\u002Fstandards.md",{"path":110,"resourceType":101,"resourceTypeDesc":102,"sizeBytes":111,"sourceHtmlUrl":112},"references\u002Fworkflows.md",693,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fdetecting-aws-guardduty-findings-automation\u002Freferences\u002Fworkflows.md",{"path":114,"resourceType":115,"resourceTypeDesc":116,"sizeBytes":117,"sourceHtmlUrl":118},"scripts\u002Fagent.py","SCRIPT","脚本",7106,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fdetecting-aws-guardduty-findings-automation\u002Fscripts\u002Fagent.py",{"path":120,"resourceType":115,"resourceTypeDesc":116,"sizeBytes":121,"sourceHtmlUrl":122},"scripts\u002Fprocess.py",4087,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fdetecting-aws-guardduty-findings-automation\u002Fscripts\u002Fprocess.py",[124,148,172,199,223,249],{"skillNo":125,"name":126,"nameZh":6,"description":127,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":128,"categories":129,"keywords":131,"publishedAt":44},"01M6AGDM3HJXTKXX15ZZ0ZVCJ3","verifying-build-provenance-with-slsa-sigstore","Verifies artifact signatures and SLSA provenance using Sigstore's cosign (verify, verify-attestation, verify-blob-attestation) and slsa-verifier (verify-artifact), enforcing keyless OIDC builder identity and source repo against SLSA Build levels. Use in CI\u002FCD before deploying artifacts, when consuming third-party attestations, establishing a SLSA Build L3 pipeline, or confirming provenance during incident response or admission control.","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fverifying-build-provenance-with-slsa-sigstore\u002FSKILL.md",[130],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[132,133,134,135,35,43,42,136,40,137,138,139,140,141,142,143,144,145,146,147],"sigstore","provenance","slsa","verifying build provenance with slsa sigstore","identity","code","artifacts","ci","supply-chain","pipeline","supply-chain-security","t1195","attestation","code-signing","cosign","keyless",{"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":155,"publishedAt":44},"01M6AGDGBPWYVZ2F11GFKJ4HZ9","validating-tpm-measured-boot-attestation","Verifies TPM 2.0 measured-boot integrity and remote attestation with tpm2-tools -- reading PCRs (tpm2_pcrread), replaying the boot event log, generating and checking signed quotes (tpm2_quote\u002Ftpm2_checkquote), and sealing secrets to a PCR policy. Use to confirm a system booted trusted firmware\u002Fkernel for Zero Trust device posture, detect boot-chain tampering via PCR drift, or build a golden-value baseline for fleet attestation.","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fvalidating-tpm-measured-boot-attestation\u002FSKILL.md",[154],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[156,144,157,158,35,159,43,40,160,161,162,163,164,165,166,167,168,169,170,171],"boot","TPM","validating tpm measured boot attestation","policy","verification","ZeRO","firmware","Tools","measured-boot","PCR","integrity","secrets","remote-attestation","tpm2-tools","integrity-verification","trusted-computing",{"skillNo":173,"name":174,"nameZh":6,"description":175,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":176,"categories":177,"keywords":182,"publishedAt":44},"01M6AGDCW0Y4FXZ3362GT1941M","validating-backup-integrity-for-recovery","Validates backup integrity through cryptographic hash verification, automated restore testing, corruption detection, and recoverability checks to confirm backups are reliable for disaster recovery and ransomware response. Use before relying on backups for recovery, when building post-backup validation pipelines, auditing backup infrastructure for compliance, or checking immutable\u002Fair-gapped backups for silent corruption or tampering.","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fvalidating-backup-integrity-for-recovery\u002FSKILL.md",[178,181],{"categoryNo":179,"categoryName":180,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[166,183,184,185,186,43,187,188,160,189,190,50,191,192,193,194,195,196,197,198],"backup","recovery","validating backup integrity for recovery","testing","infrastructure","validation","compliance","hash-verification","ransomware","cryptocurrency","detection","t1078","t1490","immutable","disaster-recovery","restore-testing",{"skillNo":200,"name":201,"nameZh":6,"description":202,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":203,"categories":204,"keywords":206,"publishedAt":44},"01M6AGD9GBG2KZ336AE763J3WH","triaging-windows-with-kape","Runs KAPE (Kroll Artifact Parser and Extractor) to collect targeted forensic artifacts (registry hives, $MFT, event logs, prefetch, browser data) via Targets and parse them with Modules wrapping Eric Zimmerman's EZ Tools (PECmd, MFTECmd, RECmd). Use during early incident containment\u002Ftriage when full disk imaging is impractical but a defensible, parseable Windows artifact set is needed quickly, including at-scale remote collection.","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Ftriaging-windows-with-kape\u002FSKILL.md",[205],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[207,208,209,43,210,211,39,212,213,214,215,33,216,217,218,219,163,220,221,222],"windows","kape","triaging windows with kape","registry","browser","windows-forensics","dfir","mft","mftecmd","prefetch","eric-zimmerman","digital-forensics","SET","collection","pecmd","artifact-collection",{"skillNo":224,"name":225,"nameZh":6,"description":226,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":227,"categories":228,"keywords":230,"publishedAt":44},"01M6AGD5PW5J4EVZM958WD74ZQ","triaging-vulnerabilities-with-ssvc-framework","Triages and prioritizes vulnerabilities with CISA's Stakeholder-Specific Vulnerability Categorization (SSVC) decision tree, weighing exploitation status (via the CISA KEV catalog and FIRST EPSS API), technical impact, automatability, and mission prevalence to output Track\u002FTrack*\u002FAttend\u002FAct decisions. Use when prioritizing vulnerability scan results (OpenVAS, Nessus, Qualys) for remediation planning beyond raw CVSS scores.","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Ftriaging-vulnerabilities-with-ssvc-framework\u002FSKILL.md",[229],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[231,232,233,43,234,235,236,237,238,239,240,241,242,31,243,244,245,246,247,248],"vulnerabilities","framework","triaging vulnerabilities with ssvc framework","status","planning","CISA","vulnerability-management","risk-management","nessus","qualys","openvas","cvss","risk","vulnerability","api","prioritization","ssvc","decision-tree",{"skillNo":250,"name":251,"nameZh":6,"description":252,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":253,"categories":254,"keywords":256,"publishedAt":44},"01M6AGD24TTQQM4CXG69E3B9TJ","triaging-security-incident","Performs initial triage of security incidents using the NIST SP 800-61r3 and SANS PICERL frameworks, classifying incident type, assigning priority by business impact, and routing to the appropriate response team. Use when a SIEM\u002FEDR alert needs human classification, concurrent alerts must be prioritized, or a user report or threat-intel IOC match requires initial incident categorization.","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Ftriaging-security-incident\u002FSKILL.md",[255],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[35,257,43,41,258,259,260,261,262,263,264,194,265,195,266,267,268,269,270,271],"triaging security incident","file","ioc","soc","NIST-800-61","NIST","severity","edr","execution","analysis","classification","severity-classification","incident-triage","SANS-PICERL","SOC-operations"]