← All projectsON THE JOB / ANALYST WORKFLOWS
Knowledge that scales.
Custom YARA detections, operational runbooks, and technical documentation to support security investigations and consistent analyst workflows.
- Original portfolio example
- Contains no employer procedures or rules
ORIGINAL PORTFOLIO EXAMPLE
A runbook another analyst can follow.
I created this reusable example for the portfolio. It contains no employer procedures, detection rules, or internal evidence. The goal is to make the reasoning and handoff clear.
- TRIAGE
Define the question
What triggered the alert? Identify the affected asset, observation time, and evidence needed to assess the behavior.
- INVESTIGATE
Record competing explanations
Compare suspicious indicators with expected administrative or business activity. Record corroborating evidence and unresolved questions.
- HAND OFF
Make the next action clear
State the disposition, confidence, proposed response, approval requirements, owner, and follow-up checks.
Minimum investigation record| Field | What to capture |
|---|
| Evidence | Source, timestamp with timezone, relevant observations, and evidence reference. |
| Analysis | Why the activity is suspicious or expected; distinguish observed facts from hypotheses. |
| Decision | Disposition, confidence, remaining uncertainty, and reason for escalation or closure. |
| Follow-up | Assigned owner, approved actions, verification steps, and next review. |
For detection changes, document the purpose, required telemetry, positive and negative test cases, false-positive conditions, and rollback criteria before proposing deployment.
Download the sample runbook ↓