[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6HM0F7G4HTBV07X2NGYT91Q":3,"skill-same:01M6HM0F7G4HTBV07X2NGYT91Q":100},{"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":18,"publishedAt":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":61,"commitSha":62,"skillDirectory":63,"forksCount":64,"repositoryHtmlUrl":65,"repositoryHomepageUrl":6,"ownerHtmlUrl":66,"ownerBlogUrl":6,"ownerDescription":67,"updatedAt":68,"install":69,"resources":82},"01M6HM0F7G4HTBV07X2NGYT91Q","implementing-ddos-mitigation-with-cloudflare",null,"Configure Cloudflare DDoS protection with managed rulesets, rate limiting, WAF rules, Bot Management, and origin protection to mitigate volumetric, protocol, and application-layer attacks.","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\u002Fimplementing-ddos-mitigation-with-cloudflare\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"implementing","cloudflare","with","ddos","implementing ddos mitigation with cloudflare","volumetric-attack","layer","de","bot management","origin","cm","configure","bot","layer-7","bot-management","ddos-mitigation","t1078","network","cybersecurity","security","2026-11-10 10:12:30",false,"---\nname: implementing-ddos-mitigation-with-cloudflare\ndescription: Configure Cloudflare DDoS protection with managed rulesets, rate limiting, WAF rules, Bot Management, and origin protection to mitigate volumetric, protocol, and application-layer attacks.\ndomain: cybersecurity\nsubdomain: network-security\ntags:\n- ddos\n- cloudflare\n- ddos-mitigation\n- rate-limiting\n- waf\n- bot-management\n- layer-7\n- volumetric-attack\n- network-security\nversion: '1.0'\nauthor: mahipal\nlicense: Apache-2.0\nnist_csf:\n- PR.IR-01\n- DE.CM-01\n- ID.AM-03\n- PR.DS-02\nmitre_attack:\n- T1046\n- T1040\n- T1557\n- T1071\n- T1078.004\ncategory: implementing-ddos-mitigation-with-cloudflare\n---\n# Implementing DDoS Mitigation with Cloudflare\n\n## Overview\n\nCloudflare provides multi-layer DDoS protection across its global network of over 300 data centers with 477+ Tbps of capacity. The platform protects against L3\u002F4 volumetric attacks (SYN floods, UDP amplification, DNS reflection), protocol attacks (Ping of Death, Smurf), and L7 application-layer attacks (HTTP floods, Slowloris, cache-busting). Cloudflare's autonomous detection systems identify and mitigate attacks within approximately 3 seconds using traffic profiling, machine learning, and adaptive rulesets. This skill covers configuring Cloudflare's DDoS protection stack including managed rulesets, WAF rules, rate limiting, Bot Management, and origin server hardening.\n\n\n## When to Use\n\n- When deploying or configuring implementing ddos mitigation with cloudflare capabilities in your environment\n- When establishing security controls aligned to compliance requirements\n- When building or improving security architecture for this domain\n- When conducting security assessments that require this implementation\n\n## Prerequisites\n\n- Cloudflare account (Pro plan minimum for WAF, Enterprise for Advanced DDoS)\n- Domain with DNS delegated to Cloudflare nameservers\n- Origin server IP address(es)\n- Understanding of normal traffic patterns and peak volumes\n- Cloudflare API token for automation\n\n## Core Concepts\n\n### DDoS Attack Categories\n\n| Layer | Attack Type | Examples | Cloudflare Protection |\n|-------|------------|----------|----------------------|\n| L3\u002F4 | Volumetric | SYN flood, UDP flood, DNS amplification | Network-layer DDoS managed rules |\n| L3\u002F4 | Protocol | Ping of Death, Smurf, IP fragmentation | Advanced TCP Protection |\n| L7 | Application | HTTP flood, Slowloris, cache busting | HTTP DDoS managed rules, WAF, Rate Limiting |\n| DNS | DNS-specific | DNS query flood, NXDOMAIN attack | Advanced DNS Protection |\n\n### Cloudflare Protection Stack\n\n```\nInternet Traffic\n     │\n     ▼\n┌─────────────────────────┐\n│  Cloudflare Edge (PoP)  │\n│  ┌───────────────────┐  │\n│  │ L3\u002F4 DDoS Mgd Rules│  │  ← Volumetric\u002FProtocol mitigation\n│  └───────────────────┘  │\n│  ┌───────────────────┐  │\n│  │ IP Access Rules    │  │  ← Country\u002FASN\u002FIP blocks\n│  └───────────────────┘  │\n│  ┌───────────────────┐  │\n│  │ Bot Management     │  │  ← Bot score, JS challenge\n│  └───────────────────┘  │\n│  ┌───────────────────┐  │\n│  │ WAF Managed Rules  │  │  ← OWASP, Cloudflare, Custom\n│  └───────────────────┘  │\n│  ┌───────────────────┐  │\n│  │ Rate Limiting      │  │  ← Request rate enforcement\n│  └───────────────────┘  │\n│  ┌───────────────────┐  │\n│  │ HTTP DDoS Mgd Rules│  │  ← L7 flood detection\n│  └───────────────────┘  │\n└─────────────────────────┘\n     │\n     ▼\n  Origin Server\n```\n\n## Workflow\n\n### Step 1: Onboard Domain to Cloudflare\n\n```bash\n# Add domain via API\ncurl -X POST \"https:\u002F\u002Fapi.cloudflare.com\u002Fclient\u002Fv4\u002Fzones\" \\\n  -H \"Authorization: Bearer $CF_API_TOKEN\" \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  --data '{\n    \"name\": \"example.com\",\n    \"type\": \"full\",\n    \"plan\": {\"id\": \"enterprise\"}\n  }'\n\n# Update DNS records (proxy enabled for DDoS protection)\ncurl -X POST \"https:\u002F\u002Fapi.cloudflare.com\u002Fclient\u002Fv4\u002Fzones\u002F$ZONE_ID\u002Fdns_records\" \\\n  -H \"Authorization: Bearer $CF_API_TOKEN\" \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  --data '{\n    \"type\": \"A\",\n    \"name\": \"example.com\",\n    \"content\": \"203.0.113.50\",\n    \"proxied\": true,\n    \"ttl\": 1\n  }'\n```\n\n### Step 2: Configure DDoS Managed Rulesets\n\n**HTTP DDoS Attack Protection override:**\n\n```bash\n# List HTTP DDoS managed ruleset\ncurl -X GET \"https:\u002F\u002Fapi.cloudflare.com\u002Fclient\u002Fv4\u002Fzones\u002F$ZONE_ID\u002Frulesets\u002Fphases\u002Fddos_l7\u002Fentrypoint\" \\\n  -H \"Authorization: Bearer $CF_API_TOKEN\"\n\n# Override HTTP DDoS sensitivity and action\ncurl -X PUT \"https:\u002F\u002Fapi.cloudflare.com\u002Fclient\u002Fv4\u002Fzones\u002F$ZONE_ID\u002Frulesets\u002Fphases\u002Fddos_l7\u002Fentrypoint\" \\\n  -H \"Authorization: Bearer $CF_API_TOKEN\" \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  --data '{\n    \"rules\": [{\n      \"action\": \"execute\",\n      \"action_parameters\": {\n        \"id\": \"4d21379b4f9f4bb088e0729962c8b3cf\",\n        \"overrides\": {\n          \"rules\": [{\n            \"id\": \"fdfdac75430c4c47a422bdc024aab531\",\n            \"sensitivity_level\": \"medium\",\n            \"action\": \"block\"\n          }],\n          \"sensitivity_level\": \"high\"\n        }\n      },\n      \"expression\": \"true\"\n    }]\n  }'\n```\n\n**Network-layer DDoS Protection override:**\n\n```bash\ncurl -X PUT \"https:\u002F\u002Fapi.cloudflare.com\u002Fclient\u002Fv4\u002Faccounts\u002F$ACCOUNT_ID\u002Frulesets\u002Fphases\u002Fddos_l4\u002Fentrypoint\" \\\n  -H \"Authorization: Bearer $CF_API_TOKEN\" \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  --data '{\n    \"rules\": [{\n      \"action\": \"execute\",\n      \"action_parameters\": {\n        \"id\": \"3b64149bfa6e4220bbbc2bd6db7c867e\",\n        \"overrides\": {\n          \"sensitivity_level\": \"high\"\n        }\n      },\n      \"expression\": \"true\"\n    }]\n  }'\n```\n\n### Step 3: Configure Rate Limiting Rules\n\n```bash\n# Create rate limiting rule for login endpoint\ncurl -X POST \"https:\u002F\u002Fapi.cloudflare.com\u002Fclient\u002Fv4\u002Fzones\u002F$ZONE_ID\u002Frulesets\u002Fphases\u002Fhttp_ratelimit\u002Fentrypoint\" \\\n  -H \"Authorization: Bearer $CF_API_TOKEN\" \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  --data '{\n    \"rules\": [\n      {\n        \"description\": \"Rate limit login attempts\",\n        \"expression\": \"(http.request.uri.path eq \\\"\u002Fapi\u002Flogin\\\")\",\n        \"action\": \"block\",\n        \"ratelimit\": {\n          \"characteristics\": [\"cf.colo.id\", \"ip.src\"],\n          \"period\": 60,\n          \"requests_per_period\": 10,\n          \"mitigation_timeout\": 600\n        }\n      },\n      {\n        \"description\": \"Rate limit API endpoints\",\n        \"expression\": \"(http.request.uri.path matches \\\"^\u002Fapi\u002F\\\")\",\n        \"action\": \"managed_challenge\",\n        \"ratelimit\": {\n          \"characteristics\": [\"cf.colo.id\", \"ip.src\"],\n          \"period\": 60,\n          \"requests_per_period\": 100,\n          \"mitigation_timeout\": 300\n        }\n      },\n      {\n        \"description\": \"Global rate limit per IP\",\n        \"expression\": \"true\",\n        \"action\": \"managed_challenge\",\n        \"ratelimit\": {\n          \"characteristics\": [\"ip.src\"],\n          \"period\": 10,\n          \"requests_per_period\": 50,\n          \"mitigation_timeout\": 60\n        }\n      }\n    ]\n  }'\n```\n\n### Step 4: Configure WAF Custom Rules\n\n```bash\n# Block known attack patterns\ncurl -X POST \"https:\u002F\u002Fapi.cloudflare.com\u002Fclient\u002Fv4\u002Fzones\u002F$ZONE_ID\u002Frulesets\u002Fphases\u002Fhttp_request_firewall_custom\u002Fentrypoint\" \\\n  -H \"Authorization: Bearer $CF_API_TOKEN\" \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  --data '{\n    \"rules\": [\n      {\n        \"description\": \"Block requests from known bad ASNs\",\n        \"expression\": \"(ip.geoip.asnum in {12345 67890})\",\n        \"action\": \"block\"\n      },\n      {\n        \"description\": \"Challenge requests without User-Agent\",\n        \"expression\": \"(not http.user_agent ne \\\"\\\")\",\n        \"action\": \"managed_challenge\"\n      },\n      {\n        \"description\": \"Block high-risk countries for admin paths\",\n        \"expression\": \"(http.request.uri.path contains \\\"\u002Fadmin\\\" and not ip.geoip.country in {\\\"US\\\" \\\"CA\\\" \\\"GB\\\"})\",\n        \"action\": \"block\"\n      },\n      {\n        \"description\": \"Block oversized request bodies\",\n        \"expression\": \"(http.request.body.size gt 10000000)\",\n        \"action\": \"block\"\n      }\n    ]\n  }'\n```\n\n### Step 5: Configure Origin Protection\n\nEnsure the origin server only accepts traffic from Cloudflare:\n\n```bash\n# Get Cloudflare IP ranges\ncurl https:\u002F\u002Fapi.cloudflare.com\u002Fclient\u002Fv4\u002Fips\n\n# Configure origin server firewall (iptables)\n# Allow only Cloudflare IPs\nfor ip in $(curl -s https:\u002F\u002Fwww.cloudflare.com\u002Fips-v4); do\n    iptables -A INPUT -p tcp --dport 443 -s $ip -j ACCEPT\n    iptables -A INPUT -p tcp --dport 80 -s $ip -j ACCEPT\ndone\n\n# Drop all other HTTP\u002FHTTPS traffic\niptables -A INPUT -p tcp --dport 443 -j DROP\niptables -A INPUT -p tcp --dport 80 -j DROP\n\n# Enable Authenticated Origin Pulls (mutual TLS)\n# Download Cloudflare origin CA certificate\ncurl -o \u002Fetc\u002Fssl\u002Fcloudflare-origin-pull.pem \\\n  https:\u002F\u002Fdevelopers.cloudflare.com\u002Fssl\u002Fstatic\u002Fauthenticated_origin_pull_ca.pem\n\n# Nginx configuration for authenticated origin pulls\n# ssl_client_certificate \u002Fetc\u002Fssl\u002Fcloudflare-origin-pull.pem;\n# ssl_verify_client on;\n```\n\n### Step 6: Enable Under Attack Mode Automation\n\n```python\n#!\u002Fusr\u002Fbin\u002Fenv python3\n\"\"\"Auto-enable Cloudflare Under Attack Mode based on traffic anomalies.\"\"\"\n\nimport requests\nimport time\nimport sys\n\nCF_API_TOKEN = \"your-api-token\"\nZONE_ID = \"your-zone-id\"\nHEADERS = {\n    \"Authorization\": f\"Bearer {CF_API_TOKEN}\",\n    \"Content-Type\": \"application\u002Fjson\",\n}\nBASE_URL = f\"https:\u002F\u002Fapi.cloudflare.com\u002Fclient\u002Fv4\u002Fzones\u002F{ZONE_ID}\"\n\nNORMAL_RPS_THRESHOLD = 5000  # Requests per second threshold\nCHECK_INTERVAL = 30  # Seconds between checks\n\n\ndef get_current_security_level():\n    \"\"\"Get current security level setting.\"\"\"\n    resp = requests.get(\n        f\"{BASE_URL}\u002Fsettings\u002Fsecurity_level\",\n        headers=HEADERS\n    )\n    return resp.json()[\"result\"][\"value\"]\n\n\ndef set_security_level(level: str):\n    \"\"\"Set security level (off, essentially_off, low, medium, high, under_attack).\"\"\"\n    resp = requests.patch(\n        f\"{BASE_URL}\u002Fsettings\u002Fsecurity_level\",\n        headers=HEADERS,\n        json={\"value\": level}\n    )\n    result = resp.json()\n    if result[\"success\"]:\n        print(f\"[+] Security level set to: {level}\")\n    else:\n        print(f\"[-] Failed to set security level: {result['errors']}\")\n    return result[\"success\"]\n\n\ndef get_traffic_analytics():\n    \"\"\"Get recent traffic data from Cloudflare analytics.\"\"\"\n    query = \"\"\"\n    query {\n      viewer {\n        zones(filter: {zoneTag: \"%s\"}) {\n          httpRequests1mGroups(limit: 1, orderBy: [datetime_DESC]) {\n            sum {\n              requests\n              threats\n            }\n            dimensions {\n              datetime\n            }\n          }\n        }\n      }\n    }\n    \"\"\" % ZONE_ID\n\n    resp = requests.post(\n        \"https:\u002F\u002Fapi.cloudflare.com\u002Fclient\u002Fv4\u002Fgraphql\",\n        headers=HEADERS,\n        json={\"query\": query}\n    )\n    return resp.json()\n\n\ndef monitor_and_respond():\n    \"\"\"Monitor traffic and auto-enable under attack mode.\"\"\"\n    current_level = get_current_security_level()\n    print(f\"[*] Current security level: {current_level}\")\n    print(f\"[*] Monitoring traffic (threshold: {NORMAL_RPS_THRESHOLD} RPS)...\")\n\n    attack_mode_active = False\n    consecutive_normal = 0\n\n    while True:\n        try:\n            analytics = get_traffic_analytics()\n            zones = analytics.get(\"data\", {}).get(\"viewer\", {}).get(\"zones\", [])\n\n            if zones and zones[0].get(\"httpRequests1mGroups\"):\n                data = zones[0][\"httpRequests1mGroups\"][0][\"sum\"]\n                rps = data[\"requests\"] \u002F 60\n                threats = data[\"threats\"]\n\n                print(f\"[*] Current RPS: {rps:.0f}, Threats: {threats}\")\n\n                if rps > NORMAL_RPS_THRESHOLD and not attack_mode_active:\n                    print(f\"[!] Traffic spike detected: {rps:.0f} RPS\")\n                    set_security_level(\"under_attack\")\n                    attack_mode_active = True\n                    consecutive_normal = 0\n\n                elif rps \u003C= NORMAL_RPS_THRESHOLD and attack_mode_active:\n                    consecutive_normal += 1\n                    if consecutive_normal >= 5:\n                        print(\"[+] Traffic normalized, disabling under attack mode\")\n                        set_security_level(\"high\")\n                        attack_mode_active = False\n                        consecutive_normal = 0\n\n        except Exception as e:\n            print(f\"[-] Error: {e}\")\n\n        time.sleep(CHECK_INTERVAL)\n\n\nif __name__ == \"__main__\":\n    monitor_and_respond()\n```\n\n## Monitoring and Alerting\n\n### Cloudflare Dashboard Metrics\n\n- **Firewall Events** - View blocked requests, challenged requests, rate-limited requests\n- **DDoS Analytics** - Attack size, duration, type, and mitigation status\n- **Traffic Analytics** - Request volume, bandwidth, error rates by time\n- **Bot Analytics** - Bot score distribution, verified bots vs automated threats\n\n### Alert Configuration\n\n```bash\n# Create notification policy for DDoS attacks\ncurl -X POST \"https:\u002F\u002Fapi.cloudflare.com\u002Fclient\u002Fv4\u002Faccounts\u002F$ACCOUNT_ID\u002Falerting\u002Fv3\u002Fpolicies\" \\\n  -H \"Authorization: Bearer $CF_API_TOKEN\" \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  --data '{\n    \"name\": \"DDoS Attack Alert\",\n    \"alert_type\": \"dos_attack_l7\",\n    \"enabled\": true,\n    \"mechanisms\": {\n      \"email\": [{\"id\": \"soc@example.com\"}],\n      \"webhooks\": [{\"id\": \"webhook-id\"}]\n    },\n    \"filters\": {\n      \"zones\": [\"'$ZONE_ID'\"]\n    }\n  }'\n```\n\n## Best Practices\n\n- **Proxy All DNS Records** - Ensure all A\u002FAAAA\u002FCNAME records pointing to origin are proxied (orange cloud)\n- **Hide Origin IP** - Never expose origin server IP; use Cloudflare Tunnel or restrict to Cloudflare IPs only\n- **Start in Log Mode** - Test DDoS rule overrides with \"Log\" action before switching to \"Block\"\n- **Layer Defense** - Combine managed rulesets, rate limiting, WAF rules, and Bot Management\n- **Tune Sensitivity** - Adjust DDoS rule sensitivity based on false positive rates in your traffic\n- **Cache Strategy** - Maximize cache hit ratio to reduce origin load during attacks\n- **Waiting Room** - Configure Cloudflare Waiting Room for critical pages during traffic surges\n- **Authenticated Origin** - Enable Authenticated Origin Pulls to prevent direct-to-origin attacks\n\n## References\n\n- [Cloudflare DDoS Protection Documentation](https:\u002F\u002Fdevelopers.cloudflare.com\u002Fddos-protection\u002F)\n- [Cloudflare WAF Documentation](https:\u002F\u002Fdevelopers.cloudflare.com\u002Fwaf\u002F)\n- [Cloudflare Rate Limiting](https:\u002F\u002Fdevelopers.cloudflare.com\u002Fwaf\u002Frate-limiting-rules\u002F)\n- [Cloudflare IP Ranges](https:\u002F\u002Fwww.cloudflare.com\u002Fips\u002F)\n","# Implementing DDoS Mitigation with Cloudflare\n\n## Overview\n\nCloudflare provides multi-layer DDoS protection across its global network of over 300 data centers with 477+ Tbps of capacity. The platform protects against L3\u002F4 volumetric attacks (SYN floods, UDP amplification, DNS reflection), protocol attacks (Ping of Death, Smurf), and L7 application-layer attacks (HTTP floods, Slowloris, cache-busting). Cloudflare's autonomous detection systems identify and mitigate attacks within approximately 3 seconds using traffic profiling, machine learning, and adaptive rulesets. This skill covers configuring Cloudflare's DDoS protection stack including managed rulesets, WAF rules, rate limiting, Bot Management, and origin server hardening.\n\n\n## When to Use\n\n- When deploying or configuring implementing ddos mitigation with cloudflare capabilities in your environment\n- When establishing security controls aligned to compliance requirements\n- When building or improving security architecture for this domain\n- When conducting security assessments that require this implementation\n\n## Prerequisites\n\n- Cloudflare account (Pro plan minimum for WAF, Enterprise for Advanced DDoS)\n- Domain with DNS delegated to Cloudflare nameservers\n- Origin server IP address(es)\n- Understanding of normal traffic patterns and peak volumes\n- Cloudflare API token for automation\n\n## Core Concepts\n\n### DDoS Attack Categories\n\n| Layer | Attack Type | Examples | Cloudflare Protection |\n|-------|------------|----------|----------------------|\n| L3\u002F4 | Volumetric | SYN flood, UDP flood, DNS amplification | Network-layer DDoS managed rules |\n| L3\u002F4 | Protocol | Ping of Death, Smurf, IP fragmentation | Advanced TCP Protection |\n| L7 | Application | HTTP flood, Slowloris, cache busting | HTTP DDoS managed rules, WAF, Rate Limiting |\n| DNS | DNS-specific | DNS query flood, NXDOMAIN attack | Advanced DNS Protection |\n\n### Cloudflare Protection Stack\n\n```\nInternet Traffic\n     │\n     ▼\n┌─────────────────────────┐\n│  Cloudflare Edge (PoP)  │\n│  ┌───────────────────┐  │\n│  │ L3\u002F4 DDoS Mgd Rules│  │  ← Volumetric\u002FProtocol mitigation\n│  └───────────────────┘  │\n│  ┌───────────────────┐  │\n│  │ IP Access Rules    │  │  ← Country\u002FASN\u002FIP blocks\n│  └───────────────────┘  │\n│  ┌───────────────────┐  │\n│  │ Bot Management     │  │  ← Bot score, JS challenge\n│  └───────────────────┘  │\n│  ┌───────────────────┐  │\n│  │ WAF Managed Rules  │  │  ← OWASP, Cloudflare, Custom\n│  └───────────────────┘  │\n│  ┌───────────────────┐  │\n│  │ Rate Limiting      │  │  ← Request rate enforcement\n│  └───────────────────┘  │\n│  ┌───────────────────┐  │\n│  │ HTTP DDoS Mgd Rules│  │  ← L7 flood detection\n│  └───────────────────┘  │\n└─────────────────────────┘\n     │\n     ▼\n  Origin Server\n```\n\n## Workflow\n\n### Step 1: Onboard Domain to Cloudflare\n\n```bash\n# Add domain via API\ncurl -X POST \"https:\u002F\u002Fapi.cloudflare.com\u002Fclient\u002Fv4\u002Fzones\" \\\n  -H \"Authorization: Bearer $CF_API_TOKEN\" \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  --data '{\n    \"name\": \"example.com\",\n    \"type\": \"full\",\n    \"plan\": {\"id\": \"enterprise\"}\n  }'\n\n# Update DNS records (proxy enabled for DDoS protection)\ncurl -X POST \"https:\u002F\u002Fapi.cloudflare.com\u002Fclient\u002Fv4\u002Fzones\u002F$ZONE_ID\u002Fdns_records\" \\\n  -H \"Authorization: Bearer $CF_API_TOKEN\" \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  --data '{\n    \"type\": \"A\",\n    \"name\": \"example.com\",\n    \"content\": \"203.0.113.50\",\n    \"proxied\": true,\n    \"ttl\": 1\n  }'\n```\n\n### Step 2: Configure DDoS Managed Rulesets\n\n**HTTP DDoS Attack Protection override:**\n\n```bash\n# List HTTP DDoS managed ruleset\ncurl -X GET \"https:\u002F\u002Fapi.cloudflare.com\u002Fclient\u002Fv4\u002Fzones\u002F$ZONE_ID\u002Frulesets\u002Fphases\u002Fddos_l7\u002Fentrypoint\" \\\n  -H \"Authorization: Bearer $CF_API_TOKEN\"\n\n# Override HTTP DDoS sensitivity and action\ncurl -X PUT \"https:\u002F\u002Fapi.cloudflare.com\u002Fclient\u002Fv4\u002Fzones\u002F$ZONE_ID\u002Frulesets\u002Fphases\u002Fddos_l7\u002Fentrypoint\" \\\n  -H \"Authorization: Bearer $CF_API_TOKEN\" \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  --data '{\n    \"rules\": [{\n      \"action\": \"execute\",\n      \"action_parameters\": {\n        \"id\": \"4d21379b4f9f4bb088e0729962c8b3cf\",\n        \"overrides\": {\n          \"rules\": [{\n            \"id\": \"fdfdac75430c4c47a422bdc024aab531\",\n            \"sensitivity_level\": \"medium\",\n            \"action\": \"block\"\n          }],\n          \"sensitivity_level\": \"high\"\n        }\n      },\n      \"expression\": \"true\"\n    }]\n  }'\n```\n\n**Network-layer DDoS Protection override:**\n\n```bash\ncurl -X PUT \"https:\u002F\u002Fapi.cloudflare.com\u002Fclient\u002Fv4\u002Faccounts\u002F$ACCOUNT_ID\u002Frulesets\u002Fphases\u002Fddos_l4\u002Fentrypoint\" \\\n  -H \"Authorization: Bearer $CF_API_TOKEN\" \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  --data '{\n    \"rules\": [{\n      \"action\": \"execute\",\n      \"action_parameters\": {\n        \"id\": \"3b64149bfa6e4220bbbc2bd6db7c867e\",\n        \"overrides\": {\n          \"sensitivity_level\": \"high\"\n        }\n      },\n      \"expression\": \"true\"\n    }]\n  }'\n```\n\n### Step 3: Configure Rate Limiting Rules\n\n```bash\n# Create rate limiting rule for login endpoint\ncurl -X POST \"https:\u002F\u002Fapi.cloudflare.com\u002Fclient\u002Fv4\u002Fzones\u002F$ZONE_ID\u002Frulesets\u002Fphases\u002Fhttp_ratelimit\u002Fentrypoint\" \\\n  -H \"Authorization: Bearer $CF_API_TOKEN\" \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  --data '{\n    \"rules\": [\n      {\n        \"description\": \"Rate limit login attempts\",\n        \"expression\": \"(http.request.uri.path eq \\\"\u002Fapi\u002Flogin\\\")\",\n        \"action\": \"block\",\n        \"ratelimit\": {\n          \"characteristics\": [\"cf.colo.id\", \"ip.src\"],\n          \"period\": 60,\n          \"requests_per_period\": 10,\n          \"mitigation_timeout\": 600\n        }\n      },\n      {\n        \"description\": \"Rate limit API endpoints\",\n        \"expression\": \"(http.request.uri.path matches \\\"^\u002Fapi\u002F\\\")\",\n        \"action\": \"managed_challenge\",\n        \"ratelimit\": {\n          \"characteristics\": [\"cf.colo.id\", \"ip.src\"],\n          \"period\": 60,\n          \"requests_per_period\": 100,\n          \"mitigation_timeout\": 300\n        }\n      },\n      {\n        \"description\": \"Global rate limit per IP\",\n        \"expression\": \"true\",\n        \"action\": \"managed_challenge\",\n        \"ratelimit\": {\n          \"characteristics\": [\"ip.src\"],\n          \"period\": 10,\n          \"requests_per_period\": 50,\n          \"mitigation_timeout\": 60\n        }\n      }\n    ]\n  }'\n```\n\n### Step 4: Configure WAF Custom Rules\n\n```bash\n# Block known attack patterns\ncurl -X POST \"https:\u002F\u002Fapi.cloudflare.com\u002Fclient\u002Fv4\u002Fzones\u002F$ZONE_ID\u002Frulesets\u002Fphases\u002Fhttp_request_firewall_custom\u002Fentrypoint\" \\\n  -H \"Authorization: Bearer $CF_API_TOKEN\" \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  --data '{\n    \"rules\": [\n      {\n        \"description\": \"Block requests from known bad ASNs\",\n        \"expression\": \"(ip.geoip.asnum in {12345 67890})\",\n        \"action\": \"block\"\n      },\n      {\n        \"description\": \"Challenge requests without User-Agent\",\n        \"expression\": \"(not http.user_agent ne \\\"\\\")\",\n        \"action\": \"managed_challenge\"\n      },\n      {\n        \"description\": \"Block high-risk countries for admin paths\",\n        \"expression\": \"(http.request.uri.path contains \\\"\u002Fadmin\\\" and not ip.geoip.country in {\\\"US\\\" \\\"CA\\\" \\\"GB\\\"})\",\n        \"action\": \"block\"\n      },\n      {\n        \"description\": \"Block oversized request bodies\",\n        \"expression\": \"(http.request.body.size gt 10000000)\",\n        \"action\": \"block\"\n      }\n    ]\n  }'\n```\n\n### Step 5: Configure Origin Protection\n\nEnsure the origin server only accepts traffic from Cloudflare:\n\n```bash\n# Get Cloudflare IP ranges\ncurl https:\u002F\u002Fapi.cloudflare.com\u002Fclient\u002Fv4\u002Fips\n\n# Configure origin server firewall (iptables)\n# Allow only Cloudflare IPs\nfor ip in $(curl -s https:\u002F\u002Fwww.cloudflare.com\u002Fips-v4); do\n    iptables -A INPUT -p tcp --dport 443 -s $ip -j ACCEPT\n    iptables -A INPUT -p tcp --dport 80 -s $ip -j ACCEPT\ndone\n\n# Drop all other HTTP\u002FHTTPS traffic\niptables -A INPUT -p tcp --dport 443 -j DROP\niptables -A INPUT -p tcp --dport 80 -j DROP\n\n# Enable Authenticated Origin Pulls (mutual TLS)\n# Download Cloudflare origin CA certificate\ncurl -o \u002Fetc\u002Fssl\u002Fcloudflare-origin-pull.pem \\\n  https:\u002F\u002Fdevelopers.cloudflare.com\u002Fssl\u002Fstatic\u002Fauthenticated_origin_pull_ca.pem\n\n# Nginx configuration for authenticated origin pulls\n# ssl_client_certificate \u002Fetc\u002Fssl\u002Fcloudflare-origin-pull.pem;\n# ssl_verify_client on;\n```\n\n### Step 6: Enable Under Attack Mode Automation\n\n```python\n#!\u002Fusr\u002Fbin\u002Fenv python3\n\"\"\"Auto-enable Cloudflare Under Attack Mode based on traffic anomalies.\"\"\"\n\nimport requests\nimport time\nimport sys\n\nCF_API_TOKEN = \"your-api-token\"\nZONE_ID = \"your-zone-id\"\nHEADERS = {\n    \"Authorization\": f\"Bearer {CF_API_TOKEN}\",\n    \"Content-Type\": \"application\u002Fjson\",\n}\nBASE_URL = f\"https:\u002F\u002Fapi.cloudflare.com\u002Fclient\u002Fv4\u002Fzones\u002F{ZONE_ID}\"\n\nNORMAL_RPS_THRESHOLD = 5000  # Requests per second threshold\nCHECK_INTERVAL = 30  # Seconds between checks\n\n\ndef get_current_security_level():\n    \"\"\"Get current security level setting.\"\"\"\n    resp = requests.get(\n        f\"{BASE_URL}\u002Fsettings\u002Fsecurity_level\",\n        headers=HEADERS\n    )\n    return resp.json()[\"result\"][\"value\"]\n\n\ndef set_security_level(level: str):\n    \"\"\"Set security level (off, essentially_off, low, medium, high, under_attack).\"\"\"\n    resp = requests.patch(\n        f\"{BASE_URL}\u002Fsettings\u002Fsecurity_level\",\n        headers=HEADERS,\n        json={\"value\": level}\n    )\n    result = resp.json()\n    if result[\"success\"]:\n        print(f\"[+] Security level set to: {level}\")\n    else:\n        print(f\"[-] Failed to set security level: {result['errors']}\")\n    return result[\"success\"]\n\n\ndef get_traffic_analytics():\n    \"\"\"Get recent traffic data from Cloudflare analytics.\"\"\"\n    query = \"\"\"\n    query {\n      viewer {\n        zones(filter: {zoneTag: \"%s\"}) {\n          httpRequests1mGroups(limit: 1, orderBy: [datetime_DESC]) {\n            sum {\n              requests\n              threats\n            }\n            dimensions {\n              datetime\n            }\n          }\n        }\n      }\n    }\n    \"\"\" % ZONE_ID\n\n    resp = requests.post(\n        \"https:\u002F\u002Fapi.cloudflare.com\u002Fclient\u002Fv4\u002Fgraphql\",\n        headers=HEADERS,\n        json={\"query\": query}\n    )\n    return resp.json()\n\n\ndef monitor_and_respond():\n    \"\"\"Monitor traffic and auto-enable under attack mode.\"\"\"\n    current_level = get_current_security_level()\n    print(f\"[*] Current security level: {current_level}\")\n    print(f\"[*] Monitoring traffic (threshold: {NORMAL_RPS_THRESHOLD} RPS)...\")\n\n    attack_mode_active = False\n    consecutive_normal = 0\n\n    while True:\n        try:\n            analytics = get_traffic_analytics()\n            zones = analytics.get(\"data\", {}).get(\"viewer\", {}).get(\"zones\", [])\n\n            if zones and zones[0].get(\"httpRequests1mGroups\"):\n                data = zones[0][\"httpRequests1mGroups\"][0][\"sum\"]\n                rps = data[\"requests\"] \u002F 60\n                threats = data[\"threats\"]\n\n                print(f\"[*] Current RPS: {rps:.0f}, Threats: {threats}\")\n\n                if rps > NORMAL_RPS_THRESHOLD and not attack_mode_active:\n                    print(f\"[!] Traffic spike detected: {rps:.0f} RPS\")\n                    set_security_level(\"under_attack\")\n                    attack_mode_active = True\n                    consecutive_normal = 0\n\n                elif rps \u003C= NORMAL_RPS_THRESHOLD and attack_mode_active:\n                    consecutive_normal += 1\n                    if consecutive_normal >= 5:\n                        print(\"[+] Traffic normalized, disabling under attack mode\")\n                        set_security_level(\"high\")\n                        attack_mode_active = False\n                        consecutive_normal = 0\n\n        except Exception as e:\n            print(f\"[-] Error: {e}\")\n\n        time.sleep(CHECK_INTERVAL)\n\n\nif __name__ == \"__main__\":\n    monitor_and_respond()\n```\n\n## Monitoring and Alerting\n\n### Cloudflare Dashboard Metrics\n\n- **Firewall Events** - View blocked requests, challenged requests, rate-limited requests\n- **DDoS Analytics** - Attack size, duration, type, and mitigation status\n- **Traffic Analytics** - Request volume, bandwidth, error rates by time\n- **Bot Analytics** - Bot score distribution, verified bots vs automated threats\n\n### Alert Configuration\n\n```bash\n# Create notification policy for DDoS attacks\ncurl -X POST \"https:\u002F\u002Fapi.cloudflare.com\u002Fclient\u002Fv4\u002Faccounts\u002F$ACCOUNT_ID\u002Falerting\u002Fv3\u002Fpolicies\" \\\n  -H \"Authorization: Bearer $CF_API_TOKEN\" \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  --data '{\n    \"name\": \"DDoS Attack Alert\",\n    \"alert_type\": \"dos_attack_l7\",\n    \"enabled\": true,\n    \"mechanisms\": {\n      \"email\": [{\"id\": \"soc@example.com\"}],\n      \"webhooks\": [{\"id\": \"webhook-id\"}]\n    },\n    \"filters\": {\n      \"zones\": [\"'$ZONE_ID'\"]\n    }\n  }'\n```\n\n## Best Practices\n\n- **Proxy All DNS Records** - Ensure all A\u002FAAAA\u002FCNAME records pointing to origin are proxied (orange cloud)\n- **Hide Origin IP** - Never expose origin server IP; use Cloudflare Tunnel or restrict to Cloudflare IPs only\n- **Start in Log Mode** - Test DDoS rule overrides with \"Log\" action before switching to \"Block\"\n- **Layer Defense** - Combine managed rulesets, rate limiting, WAF rules, and Bot Management\n- **Tune Sensitivity** - Adjust DDoS rule sensitivity based on false positive rates in your traffic\n- **Cache Strategy** - Maximize cache hit ratio to reduce origin load during attacks\n- **Waiting Room** - Configure Cloudflare Waiting Room for critical pages during traffic surges\n- **Authenticated Origin** - Enable Authenticated Origin Pulls to prevent direct-to-origin attacks\n\n## References\n\n- [Cloudflare DDoS Protection Documentation](https:\u002F\u002Fdevelopers.cloudflare.com\u002Fddos-protection\u002F)\n- [Cloudflare WAF Documentation](https:\u002F\u002Fdevelopers.cloudflare.com\u002Fwaf\u002F)\n- [Cloudflare Rate Limiting](https:\u002F\u002Fdevelopers.cloudflare.com\u002Fwaf\u002Frate-limiting-rules\u002F)\n- [Cloudflare IP Ranges](https:\u002F\u002Fwww.cloudflare.com\u002Fips\u002F)\n",{"name":5,"tags":44,"author":48,"domain":37,"license":15,"version":49,"category":5,"nist_csf":50,"subdomain":47,"description":7,"mitre_attack":55},[22,20,34,45,46,33,32,24,47],"rate-limiting","waf","network-security","mahipal","1.0",[51,52,53,54],"PR.IR-01","DE.CM-01","ID.AM-03","PR.DS-02",[56,57,58,59,60],"T1046","T1040","T1557","T1071","T1078.004","main","5eea5b3296f4673b5f481e8bcc1ba76281149f16","modules\u002Fimplementing-ddos-mitigation-with-cloudflare",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":70,"prompt":80,"zipAvailable":81},[71,74,77],{"tool":72,"command":73},"npx","npx skills add HenriqueMC17\u002Fagente-core --skill implementing-ddos-mitigation-with-cloudflare",{"tool":75,"command":76},"bunx","bunx skills add HenriqueMC17\u002Fagente-core --skill implementing-ddos-mitigation-with-cloudflare",{"tool":78,"command":79},"pnpm","pnpm dlx skills add HenriqueMC17\u002Fagente-core --skill implementing-ddos-mitigation-with-cloudflare","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fimplementing-ddos-mitigation-with-cloudflare\u002FSKILL.md",true,[83,88,94],{"path":84,"resourceType":84,"resourceTypeDesc":85,"sizeBytes":86,"sourceHtmlUrl":87},"LICENSE","许可证",11255,"https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fimplementing-ddos-mitigation-with-cloudflare\u002FLICENSE",{"path":89,"resourceType":90,"resourceTypeDesc":91,"sizeBytes":92,"sourceHtmlUrl":93},"references\u002Fapi-reference.md","REFERENCE","参考文档",1588,"https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fimplementing-ddos-mitigation-with-cloudflare\u002Freferences\u002Fapi-reference.md",{"path":95,"resourceType":96,"resourceTypeDesc":97,"sizeBytes":98,"sourceHtmlUrl":99},"scripts\u002Fagent.py","SCRIPT","脚本",4714,"https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fimplementing-ddos-mitigation-with-cloudflare\u002Fscripts\u002Fagent.py",[101,131,156,178,194,213],{"skillNo":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":105,"categories":106,"keywords":112,"publishedAt":39},"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",[107],{"categoryNo":108,"categoryName":109,"taxonomyType":110,"taxonomyTypeDesc":111},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",[113,114,115,116,117,118,37,119,120,121,122,123,124,35,125,126,127,128,129,130],"integrity","backup","recovery","validating backup integrity for recovery","for","testing","validate","verification","hash-verification","incident-response","ransomware","detection","t1490","disaster-recovery","restore","incident","disaster recovery","ransomware response",{"skillNo":132,"name":133,"nameZh":6,"description":134,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":135,"categories":136,"keywords":137,"publishedAt":39},"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",[],[138,139,140,141,21,37,142,143,144,145,146,147,148,149,150,151,152,153,154,155],"vulnerabilities","framework","ssvc","triaging vulnerabilities with ssvc framework","triage and prioritize","CISA","vulnerability-management","risk-management","cvss","remediation","vulnerability","prioritization","decision-tree","prioritize","decision","priorities","actionable","tree",{"skillNo":157,"name":158,"nameZh":6,"description":159,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":160,"categories":161,"keywords":162,"publishedAt":39},"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",[],[38,163,128,37,164,165,166,35,125,167,168,169,170,171,172,173,174,175,176,177],"triaging security incident","actions","soc","NIST","analysis","severity-classification","incident-triage","SANS-PICERL","SOC-operations","picerl","conversion","isolation","scope","impact","consistency",{"skillNo":179,"name":180,"nameZh":6,"description":181,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":182,"categories":183,"keywords":184,"publishedAt":39},"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",[],[38,185,186,163,128,21,37,187,165,122,188,189,35,125,190,168,151,191,192,193],"playbook","triaging security incident with ir playbook","teams","IR-playbook","severity","classification","classify","incidents","initiate",{"skillNo":195,"name":196,"nameZh":6,"description":197,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":198,"categories":199,"keywords":200,"publishedAt":39},"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",[],[38,201,202,203,204,205,37,206,207,208,165,209,35,210,211,212,171,29,128,26],"security alerts","splunk","triaging security alerts in splunk","alerts","review","siem","dashboard","search","correlation-search","t1566","notable-events","incident-review",{"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":39},"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",[],[220,221,222,223,37,224,225,226,227,228,229,210,230,231,29,232,26,233,234,235],"infrastructure","tracking threat actor infrastructure","tracking","threat","monitoring","mitre-attack","threat-actor","threat-intelligence","command-and-control","dns","command","exploit","intelligence","domains","kit","hosts"]