Skip to the content ForoHackers
Log inJoin

Security operations: start here

Security operations
#777 · Ophuscado · · Report

A security operations centre watches an organisation's systems around the clock, decides which signals are real threats and starts the response. The work is part detection engineering, part investigation and part process: turning a flood of logs into a few well-understood cases, handled the same way every time.

Key concepts

  • Telemetry: endpoint, network, identity and cloud logs, normalised so one search covers them all.
  • Triage: for each alert, decide quickly whether it is benign, suspicious or an incident, and what to do next.
  • Detection tuning: reduce false positives without hiding true ones; every rule has an owner and a test.
  • Playbooks: written steps for common cases, so analysts act consistently and can automate the routine.
  • Metrics: time to detect and time to respond, measured to improve rather than to blame.

Vocabulary

  • SIEM: the platform that collects, correlates and searches logs.
  • SOAR: tooling that automates response steps from playbooks.
  • False positive: an alert for something harmless.
  • Tier 1, 2, 3: levels of analyst, from first triage to deep investigation.

What to study, in order

  1. Log sources and formats: system, web server, firewall and identity logs from your own lab.
  2. Query a log store with a search language and answer questions such as who logged in from where.
  3. Write a detection for one behaviour, test it against generated activity, and tune it.
  4. Practise triage on public datasets of sample incidents, writing a short verdict for each.
  5. Draft a playbook and a handover note, then run it as a tabletop with a friend.

Related tags

#blue-team #incident-response #observability #threat-intelligence #forensics

Log in or join to reply.