Study and Review Calendar
Proposed start: 31 Aug 2026Self-pacedFocused blocksRegular one-on-one review
Suggested weekly rhythm
The assessment indicates very high willingness to allocate learning time, but it also identifies time division between work and learning as a challenge. The IDR therefore uses focused core sessions rather than filling every available hour.
| Day | Time | Activity | Output |
|---|---|---|---|
| Monday | 18:30–19:30 | Theory / primary documentation | Notes + one question |
| Wednesday | 18:30–20:00 | Lab / investigation | Technical evidence |
| Thursday | 18:30–19:30 | Documentation / GitHub | README, timeline or rule notes |
| Saturday | 09:00–11:00 | Deep work / portfolio | Completed weekly artefact |
| Alternate Wednesday | 20:00–20:30 | Mentor / one-on-one review | Feedback + next actions |
The core timetable is about 5.5 hours per week, deliberately lower than the maximum time Nkateko said he is willing to invest. Extra learning time should be optional and targeted, not used to create an unsustainable backlog.
12-week schedule
| Week commencing | Focus | Primary output |
|---|---|---|
| 31 Aug 2026 | Baseline and SOC foundations | Capability matrix + lab architecture |
| 7 Sep 2026 | Networking and Windows telemetry | Event-source map |
| 14 Sep 2026 | Wazuh operations | Three alert-triage records |
| 21 Sep 2026 | Event 4625 investigation | Investigation pack |
| 28 Sep 2026 | Detection engineering | Two tested detection ideas |
| 5 Oct 2026 | Incident response | Tabletop runbook |
| 12 Oct 2026 | GitHub workflow | Reviewed evidence repository |
| 19 Oct 2026 | Cloud security | Control baseline |
| 26 Oct 2026 | ATT&CK and threat intelligence | Technique-to-telemetry matrix |
| 2 Nov 2026 | Automation | Python/PowerShell SOC utility |
| 9 Nov 2026 | Communication and interviews | Incident brief + interview stories |
| 16 Nov 2026 | Capstone | Multi-stage case study + next-90-day plan |
Review checkpoints
- Weekly: record evidence, blockers and learning hours.
- Fortnightly: one-on-one review of one completed artefact.
- Day 30: check investigation method, Wazuh confidence and workload sustainability.
- Day 60: review detection quality, incident-response thinking and communication progress.
- Day 90: assess portfolio readiness and choose the next specialisation emphasis.
Rescheduling rule
Missed time is not recovered by doubling the following week. Move the highest-value activity, preserve the evidence outcome and record the reason. Repeated slippage should trigger a scope reduction rather than hidden backlog.