Bug › Module 9 › Lesson 1
Triage Lifecycle
What happens after submit on $PROGRAM — states, timelines, and hunter expectations without entitlement.
Visual · t20_triage_lifecycle
Triage lifecycle = submit → validate → severity → bounty/N/A/dup. Original Cyberlium.
Opening
After you click submit, the report enters someone else's queue — learn the lifecycle so you do not rage-quit on day three.
Typical bounty triage lifecycle: submission received → automated checks → human triage → needs more info → accepted severity assignment → fix coordination → bounty payout or duplicate/N/A/invalid closure. Timelines vary by program size — days to weeks is normal; critical production issues may move faster. Hunters track status in platform dashboard; do not open parallel tickets on email/Slack unless program invites it. Cyberlium teaches lifecycle literacy so you plan patience and follow-ups professionally on YOUR $PROGRAM submissions — not harassment, not public shaming on day two, not assuming silence means accept. Defenders juggle patch cycles, legal, and dup databases — your clear report speeds the path.
1. Lifecycle states
New, triaged, needs info, resolved, duplicate, informative, N/A — know platform labels on HackerOne/Bugcrowd/Intigriti class platforms.
Severity may change after internal repro — not personal attack on your skills.
Command guide
Try these commands — Lifecycle states
═══ TOOLS & WEBSITES ═══ Browse / read these (authorized learning only — stay in YOUR lab / program scope)
Triage states — new | needs info | duplicate | resolved Polite replies — factual, no pressure
═══ INSTALL ═══
Linux (Debian/Ubuntu):
Command — copy this
sudo apt install curl sudo apt install python3
macOS:
Command — copy this
brew install python3
Windows: Built-in (PowerShell: Invoke-WebRequest) Download https://python.org/downloads/
═══ LINUX / macOS ═══
Command — copy this
python3 -c "print('Triage: new | needs_more_info | duplicate | resolved')"
curl -sS https://docs.hackerone.com/en/articles/triage | head -5 2>/dev/null || curl -sS https://www.hackerone.com/ | head -5Primary tools to practice this lesson: curl, python3. Reference sites: Triage states; Polite replies. Run every command in the box — install first, then the usage lines — only on YOUR lab / program scope.
2. Hunter habits
One polite follow-up after stated SLA window — not daily pings.
Keep validation notes; respond to needs-info with minimal additional proof quickly.
3. Defender view
Triage balances signal vs noise — your dup/noise hygiene from Module 7 affects queue trust.
Retest after fix may be hunter responsibility on some programs — read policy.
4. What you ship: triage lifecycle map
State diagram or bullet lifecycle + SLA patience rule + one follow-up template.
5. What you record before the next lesson
Triage lifecycle map 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
Public tweet '@company ignored my report' 24 hours after submit.
Right
Triage lifecycle map written. Next: Communication.
Mission: triage lifecycle map
1) List six lifecycle states. 2) Write SLA patience rule for $PROGRAM. 3) Draft polite needs-info response. 4) Note retest policy if any.
Stuck? Ask Cyberlium AI Mentor
Ask Mentor: “Needs-info — how fast to respond?”
Knowledge Check
APPLY: After submit, report enters:
Multiple choice
Knowledge Check
APPLY: True or False: Silence for 48h always means accept.
True or False
Knowledge Check
APPLY: Severity may change because:
Multiple choice