Security logging architecture
Which logs matter, how to collect them without losing any, how long to keep them and how to make them searchable when it counts.
● Must know for interviews🔒 PROLesson·26 min read·Intermediate → Advanced
loggingSIEMtelemetryretention
01The logs that solve incidents
✓What you will learn
- Prioritise log sources by investigative value
- Design a lossless pipeline with backpressure and buffering
- Pick hot / warm / cold tiers and retention
- Normalise to a common schema (OCSF / ECS) early
| Source | Answers | Priority |
|---|---|---|
| Identity provider / SSO | Who logged in, from where, with which factor | 1 |
| Cloud audit (CloudTrail, GCP Audit) | Who changed infra, who read secrets | 1 |
| EDR / endpoint | What ran on the host, process trees | 1 |
| Application auth + authz | Who accessed which object | 2 |
| DNS + egress proxy | Where data went | 2 |
| Network flow | Lateral movement | 3 |
FigA security log pipeline
- ACTOR
- EDGE
- SERVICE
- DATA
- STREAM
- Live flow
- Lookup / async
This is an advanced module
Detection & Response Engineering is part of the Pro pass. 1 more section — the deep dives, the final design, follow-ups and the test — unlock with it.
Already a cyart.io or studio.cyart.io member? Your pass code is in your Studio account.