Communication
Professional triage communication on $PROGRAM — clarity, politeness, boundaries, no harassment or disclosure threats.
Visual · t20_communication
Communication = professional, concise, evidence-backed. Original Cyberlium.
The hunter who writes like a colleague gets faster answers — entitlement gets closed tickets.
Effective triage communication: respond in platform thread, quote report sections, attach only new minimal proof when asked, accept language fixes, never insult analysts, never threaten immediate public disclosure as leverage on first response. Ask clarifying questions about scope politely; if disagree on severity, provide rubric row and additional proof — not CAPS LOCK. Programs may request retest on staging — coordinate within rules. Cyberlium refuses coaching harassment, doxing triagers, or coordinated disclosure threats against strangers. Boundaries work both ways: triagers may close spam — keep signal high. chmod 600 drafts before paste; redact in all replies.
1. Professional replies
Thank triager, answer each question numbered, link step numbers from original report.
If wrong about scope, accept and update notes — learning beats arguing OOS.
Command guide
Try these commands — Professional replies
═══ TOOLS & WEBSITES ═══ Browse / read these (authorized learning only — stay in YOUR lab / program scope)
Duplicate search — platform search before filing Reply plan — polite, factual
═══ INSTALL ═══
Linux (Debian/Ubuntu):
Command — copy this
sudo apt install jq
macOS:
Command — copy this
brew install jq
Windows:
Command — copy this
choco install jq
═══ LINUX / macOS ═══
Command — copy this
grep status "$HOME/cyberlium-lab/t20-triage-notes.txt" 2>/dev/null || echo 'status: new' curl -sS 'https://httpbin.org/get?duplicate_check=yes' | jq '.args'
Primary tools to practice this lesson: grep, jq. Reference sites: Duplicate search; Reply plan. Run every command in the box — install first, then the usage lines — only on YOUR lab / program scope.
2. Escalation ethics
Follow program disclosure policy timeline — coordinated disclosure, not surprise Twitter CVE.
If legal or safety concern, use program security contact — not public drama.
3. Refused communication
Harassment, slurs, threats, bribery offers, repeated dup spam after N/A — burn reputation and may ban.
No sharing private triage threads publicly without redaction and permission.
4. What you ship: communication templates
Needs-info reply + severity clarification + polite close templates — no threats.
5. What you record before the next lesson
Communication templates path.
6. Wrong vs right: random sites vs in-scope program
Worked failure — same MSF word, opposite target. Right never needs a café Wi-Fi or classmate laptop.
- Wrong: Threaten full disclosure unless paid in 24 hours on first triage reply.
- Right: Communication templates written. Next: Payment Reality.
Mission: communication templates
1) Draft needs-info reply. 2) Draft severity clarification (polite). 3) Write disclosure policy reminder line. 4) List three refused behaviors.
Stuck? Ask Cyberlium AI Mentor
Ask Mentor: “Disagree on dup — what proof helps?”
APPLY: Professional triage reply:
APPLY: True or False: Disclosure threats day one are OK.
APPLY: Severity disagreement:
Payment Reality
Part of Bug Bounty Hunting with AI — Triage and Reality.
Lab — Triage Notes
Part of Bug Bounty Hunting with AI — Triage and Reality.
Quiz — Triage
Part of Bug Bounty Hunting with AI — Triage and Reality.