Defense Lab — 429 and Policy Sheet
Catch 429 on :8818; write injection + SSRF policy sheet.
Visual · api_defense_lab
Lab: rate evidence + policy pack. Original Cyberlium.
Availability and input trust — on one page.
Demonstrate rate limit. Attach injection/SSRF policy. No flooding strangers.
1. 429 pass
Loop lab login until 429.
Save codes.
Command guide
Try these commands — 429 pass
═══ TOOLS & WEBSITES ═══ Browse / read these (authorized learning only — stay in YOUR lab / program scope)
OWASP ZAP — https://www.zaproxy.org/getting-started/ (proxy literacy on YOUR lab) Burp Suite learning — https://portswigger.net/burp/documentation/desktop/getting-started
═══ INSTALL ═══
Linux (Debian/Ubuntu):
Command — copy this
sudo apt install curl sudo apt install jq
macOS:
Command — copy this
brew install jq
Windows: Built-in (PowerShell: Invoke-WebRequest)
Command — copy this
choco install jq
═══ LINUX / macOS ═══
Save a replayable request from YOUR lab (ZAP/Burp export equivalent)
Command — copy this
curl -sS -X POST http://127.0.0.1:8818/items -H "Content-Type: application/json" -H "Authorization: Bearer lab-token" -d '{"name":"replay-test"}' -D /tmp/cyberlium-replay.headers -o /tmp/cyberlium-replay.body
curl -sS -X POST http://127.0.0.1:8818/items -H "Content-Type: application/json" -H "Authorization: Bearer lab-token" -d '{"name":"replay-test"}' | jq .
head -5 /tmp/cyberlium-replay.headers 2>/dev/null || truePrimary tools to practice this lesson: curl, jq. Reference sites: OWASP ZAP (https://www.zaproxy.org/getting-started/); Burp Suite learning (https://portswigger.net/burp/documentation/desktop/getting-started). Run every command in the box — install first, then the usage lines — only on YOUR lab / program scope.
2. Injection policy
Parameterize. NEVER sqlmap strangers.
Name sinks.
3. SSRF policy
Allowlist. NEVER metadata probes.
Name sinks.
4. What you ship: defense lab pack
429 transcript + dual policy sheet.
5. What you record before the next lesson
Port 8818 + policies.
6. Wrong vs right: stranger APIs vs literacy on systems you own
Worked failure — same API word, opposite target. Right never needs a live shop or classmate token.
- Wrong: DoS a public API for the 429 screenshot.
- Right: Lab only. Next: quiz.
Mission: defense lab
1) 429 on lab. 2) Injection policy. 3) SSRF policy.
Stuck? Ask Cyberlium AI Mentor
Ask Mentor: “How many requests before documenting 429?”
APPLY: 429 from:
APPLY: True or False: Metadata SSRF labs on cloud are required.
APPLY: Pack includes: