Threat Hunting
Supply-Chain Package Poisoning Desk
Trace a poisoned dependency update through build logs, package hashes, and CI alerts without accusing vendors recklessly.
KRW 920,000 informational only
Description
A developer workstation scenario blends CI logs with artifact repositories. Analysts learn to narrate supply-chain risk using evidence-backed language, highlight where quality standards broke down, and propose monitoring improvements that engineering teams can adopt.
Features
- Hash comparison walkthrough with benign drift examples
- CI alert correlation with commit metadata
- Vendor communication template without legal stamp language
- Risk scoring card for leadership
- Purple-team note on pipeline sensor gaps
- Activity log timeline for build chain events
- Post-incident learning prompts for retrospectives
Outcomes
- Identify the earliest reliable detection moment
- Draft engineering-facing recommendations
- Capture residual uncertainty after containment