Skill: edge-computing-security

SkillCloud & infra

Edge computing security testing covering CDN bypass, Cloudflare Workers abuse, AWS Lambda@Edge attacks, cache poisoning, origin IP discovery, WAF bypass, and edge function injection.

Available today. Use it from your connected AI after setup.

Connect ahel once, and every AI you use reads what you have installed.

Then ask your AI: use the Skill: edge-computing-security skill

What this skill tells your AI

The instructions your AI receives, as published by brucesongs/kali-claw in skills/edge-computing-security/SKILL.md and read by ahel’s review.

Summary

Edge computing security testing covering CDN bypass, Cloudflare Workers abuse, AWS Lambda@Edge attacks, cache poisoning, origin IP discovery, WAF bypass, and edge function injection.

Tools: garak, PyRIT, promptfoo, custom harnesses

Domain: edge

MITRE: TA0001-Initial Access, T1190-Exploit Public-Facing App

Description

Edge computing security testing covering CDN bypass, Cloudflare Workers abuse, AWS Lambda@Edge attacks, cache poisoning, origin IP discovery, WAF bypass, and edge function injection.

This skill covers the offensive side of cdn-edge security, including reconnaissance, vulnerability discovery, exploitation, persistence, and reporting. Aligned with OWASP Top 10, MITRE ATT&CK, and industry-specific compliance frameworks.


Use Cases

  1. CDN/WAF bypass: Bypass CDN to attack origin directly.
  2. Edge function exploitation: Abuse Cloudflare Workers, Lambda@Edge for code execution at edge.
  3. Cache poisoning: Poison cached responses to affect all users.
  4. Origin IP discovery: Find direct IP to bypass CDN/WAF.
  5. Edge persistence: Maintain persistence via edge functions (survives origin compromise).

Core Tools

| Cloudflare wrangler | Workers development/deploy | wrangler deploy | | serverless-cli | Multi-cloud serverless | serverless deploy | | waf-bypass | WAF bypass payloads | Various scripts | | Curl with resolver | Origin IP discovery | curl --resolve target.com:443:ORIGIN_IP | | Burp Suite Collaborator | Cache poisoning | Out-of-band detection | | DNS recon | Origin IP discovery | dig, dnsrecon | | Nmap | Direct origin scan | nmap -sS ORIGIN_IP |


Methodology

Attack Chain

[1] CDN Detection           [2] Origin Discovery      [3] Bypass WAF
  - Cloudflare/Akamai/etc     - DNS history (SecurityTrails)   - Origin direct
  - Worker script analysis    - SSL cert SAN            - HTTP/2 multiplexing
  - Edge function audit       - HTTP headers leak         |
  - Cache key analysis        - IP blocks (Shodan)        v
        |                       v            [4] Exploitation
        v             [2.5] WAF fingerprint  - Edge function RCE
[1.5] Cache analysis  - Rule identification  - Cache poisoning
  - Cache key structure      - Bypass technique           - Origin compromise
  - TTL behavior               |                            |
                               v                            v
                          [5] Persistence   [6] Reporting
                          - Edge function   - CDN config audit
                          - Worker script   - Origin compromise
                          - Cache poisoning - WAF effectiveness

Defense Perspective

Defense LayerMeasuresKey Points
CDN/WAF ConfigurationStrict origin policy; WAF rule set; rate limitingCDN is first line of defense; configure properly
Origin ProtectionOrigin only accessible via CDN (IP allowlist); no direct internetIf origin IP leaks, attacker bypasses CDN entirely
Cache SecurityProper cache key (include auth header); cache key sanitizationCache poisoning affects all users; cache key is critical
Edge Function SecuritySandbox edge functions; least privilege; secret scanningEdge functions have CDN-wide impact; sandbox is essential
TLS ConfigurationModern TLS (1.3); HSTS; certificate pinningTLS downgrade allows interception; HSTS prevents
Origin NetworkOrigin in private subnet; security group allows only CDNNetwork-level protection; deny direct access

Practical Steps

See payloads.md for detailed payloads and test-cases.md for the complete test checklist.

1. Reconnaissance

Identify target infrastructure; fingerprint products; enumerate attack surface.

2. Vulnerability Discovery

Run automated scanners (garak, PyRIT); manual testing per OWASP Top 10.

3. Exploitation

Chain vulnerabilities for maximum impact; document PoC.

4. Persistence

Establish persistence via configuration changes, scheduled tasks, or backdoors.

5. Reporting

Map findings to MITRE ATT&CK, OWASP, regulatory frameworks; include concrete remediation.


Detection Methods

CDN / Edge Function Logs

  • Cloudflare Workers abuse: Anomalous Worker invocations; outbound fetch to attacker domains.
  • AWS Lambda@Edge anomalies: Function duration spikes; cross-region data egress from edge.
  • Origin IP discovery: Direct origin access bypassing CDN (signature: requests to origin IP from internet).

SIEM Detection Rules

  • Splunk SPL: index=cdn sourcetype=cloudflare:workers | stats count by script | sort -count | head 10
  • Cloudflare Analytics: Native bot/security analytics.
  • AWS CloudTrail: Lambda@Edge invocation logs.

Defense Evasion Techniques

CDN Bypass

  • Direct origin access: Find origin IP via DNS history, leak in HTTP headers, SSL cert; bypass CDN/WAF.
  • Cache poisoning: Poison cached response; affect all users.
  • Cache deception: Trick CDN into caching dynamic content with sensitive data.

Edge Function Exploitation

  • Worker script injection: Inject code into Worker via compromised account or supply chain.
  • Lambda@Edge privilege abuse: Use Lambda@Edge for global execution.
  • Origin IP rotation: Use direct IP for exfil; CDN sees only legitimate traffic.

Common Pitfalls

  • Testing in unauthorized environments
  • Ignoring rate limiting (will get blocked)
  • Single-shot testing (real attacks are sustained)
  • Neglecting supply chain
  • Forgetting monitoring/alerting

Reporting and Documentation

Reports should include CVSS scores, MITRE ATT&CK mapping, concrete PoC, business impact, and specific remediation.

Legal and Ethical Considerations

Ensure proper authorization before testing. Document scope in engagement letter. Some attack techniques may violate local laws (e.g., radio transmission without license).

Hacker Laws

LawApplication
Trust but VerifyVerify all outputs; verify all sources
First PrinciplesUnderstand underlying protocols before attacking
Defense in DepthMultiple layers required for robust defense
Assume BreachDesign assuming attacker already inside
Minimize Attack SurfaceReduce unnecessary features/exposure

Learning Resources

Skill supplementary files: payloads.md, test-cases.md

External Resources:

Signals

GitHub stars
71
Forks
18
Last commit
Sep 2026
Advanced
Catalog kind
skill
Gateway key
edge-computing-security
Source
github.com/brucesongs/kali-claw