Blue teaming is the defender's side of security: preventing, detecting and responding to attacks on the systems an organisation runs. It is less about one clever trick than about knowing your own environment well enough to see what does not belong, and about making the usual failures hard.
Key concepts
- Asset inventory: you cannot defend what you do not know you have; list systems, software, accounts and data.
- Hardening: remove what is not needed, patch quickly, apply secure configurations and least privilege.
- Visibility: logs from endpoints, servers, identity and network, collected centrally and kept long enough to investigate.
- Detection: rules and baselines that turn logs into alerts, tuned to cut noise.
- Resilience: backups that are tested, segmented networks and practised recovery.
Vocabulary
- Baseline: what normal looks like, so the abnormal stands out.
- EDR: endpoint detection and response, agents that record and react on hosts.
- SIEM: a system that gathers and searches security logs.
- IOC: indicator of compromise, a trace such as a hash or an address that suggests an intrusion.
What to study, in order
- Administer a Linux and a Windows machine of your own, and learn their normal logs.
- Harden both against a published benchmark and note what each change prevents.
- Collect logs into a small open-source stack and build a dashboard of normal activity.
- Write detections for a few documented behaviours and test them in your lab.
- Restore a system from backup, timed, and write the runbook for it.
Related tags
#soc #incident-response #threat-intelligence #sysadmin #observability