EVOPEDIA

← all systems · see it in The System

Security operations center (SOC)

A unit responsible for protecting an organization against threats (src:wp:security-operations-center); in information technology a dedicated site where enterprise information systems are monitored, assessed and defended, where analysts monitor the network, investigate potential incidents and take steps to remediate them (src:wp:information-security-operations-center). Researchers define it as 'an organizational aspect of an enterprise's security strategy' that 'combines processes, technologies, and people to manage and enhance an organization's overall security posture' (src:vielberth-2020-soc). Walked as the team, the room, the tools and the routines: tiered analysts and managers, the SIEM and its alerts, triage, investigation and escalation, playbooks and metrics, shifts, and the burnout and alarm fatigue the research describes.

Properties published scienceour proposal

Sourced fields, and our own readings.

aliasesSecurity operations centres (analysts)
born atabout 2005 ('around 15 years ago' in a 2020 review); forerunners 1962 (AT&T Network Control Center), 1968 (NSA SIGINT watch centre), 1988 (first CERT)
born precisionyears to a decade
boundaryInside: the SOC's people (tier 1 triage analysts, tier 2 incident responders, tier 3 threat hunters, SOC managers, with security engineers, threat intelligence and malware analysts around them), its room and shifts, its tools (the SIEM as the 'single pane of glass', ticketing, automation and SOAR, dashboards), and its processes (data collection, detection and analysis, triage, escalation, containment, playbooks, metrics, governance and compliance). Outside: the organisation's systems it watches (networks, hosts, applications, endpoints) and the employees who use them; the detection tools that feed it (IDS, antivirus, firewalls, which other walks own); the attackers; the organisation's management, regulators and auditors; outsourced providers (MSSPs) and the network operations centre it works beside. The edge with incident response is contested (a CSIRT is 'classified either as an independent team or part of a SOC': C-1588).
nested levelAn organisational unit (rung 12) inside an organisation, the operating heart of its information security; built on the organisation's computer networks and on detection technology; staffed by people whose vigilance, judgement and morale are its upper floors.
scalesocial

Measures (21) published science

characteristic clock: staffing cycle8x5 to 24x7 hours a day x days a week
shift pattern (corporate SOC)L1: 4 days x 10 h; L2: 5 days x 8 h shifts
characteristic clock: discovery peak in the working day8-10 AM time of day
vigilance decrement onsetwithin 15 (as little as 8) minutes of sustained attention
analyst tenure in the job1-3 years (HP white paper, cited)
alerts per day (NCSA SOC, 2018-2022)24,000-134,000 alerts per day
share of alerts associated with true attacks0.01 %
share of alerts that are benign triggers49 (attack attempts 27) %
share of alerts auto-blocked (BHR)44.9 % (6,474,204 alerts, 2020-2022)
alerts per day reaching analysts after auto-blockabout 13,764 alerts per day
true attacks detected the same day; post-attack investigation66% same day; 53 days average % ; days
mean time to detect a breach (industry report, 2018)196 (plus 69 to contain) days
share of alarms analysts call false positives (perceived)99 % (one analyst's figure)
share reporting low network visibility71.43 of analysts, 60 of managers %
mitigation deadline by priority (one SOC)P0 30 min, P1 60 min, P2 120 min, P3 24 h, P4 48 h; 87% met time to mitigate
threat intelligence volume held (one SOC)17 to 20 terabytes in two months
devices watched (corporate SOC)about 300,000 devices online a day
devices watched (university SOC)55,000 devices in business hours (4 analysts)
time to correlate logs and file one ticket (manual)10 (about 15 such alerts a day) minutes
cybersecurity workforce gap (worldwide)roughly 4 million people
practitioners saying false positives are not a major issue15 of 18 interviewees

Open contentions (5) open contention

Where sources or readings disagree. Both stay on the map.

Partners and parts published science

Built from / builds (11)

Sits inside / holds (5)

Trades with (valence) (19)

expressed by (25)

floor filled by (20)

Kinds (8)

wired (6)

Notes published science

Layers

The ways it takes in its world, where they meet, and how it acts back, each from L1 (where it meets the world) up.

the boardroom (shared floors)

  1. L5: Tier 1 triage: analysts at the SIEM console validate each alarm (true, false, benign trigger), enrich it, prioritize it and escalate what they cannot solve; their vigilance, tacit knowledge, hunches and morale bound what is seen
  2. L6: Investigation and response: tier 2 incident responders assess escalated incidents in depth with threat intelligence, scope the attack, contain it; tier 3 threat hunters look for the unknown; situational awareness of the estate
  3. L7: Management and governance: the SOC manager and CISO set what the SOC watches and how (strategy, playbooks, staffing, budget, metrics, compliance), aiming at the organisation's security posture

the security operations center as SOC researchers and analysts describe it: the organisation's systems it watches up to the security posture it serves (reader's view)

  1. L1: The watched estate: enterprise information systems (websites, applications, databases, servers, networks, endpoints), the people who use them, and the threat landscape outside
  2. L2: Sensors and sources: security software (IDS/IPS, firewalls, antivirus, vulnerability scanners), network assets, operating systems, physical security, threat intelligence, employees
  3. L3: Collection: logs and alerts gathered, normalized, time-synchronized, filtered, reduced, aggregated and prioritized
  4. L4: Correlation and alarming: the SIEM's correlation rules turn events into alarms on dashboards, the single pane of glass
  5. L5: Tier 1 triage: validate, enrich, prioritize, escalate
  6. L6: Tier 2 and 3: in-depth investigation with threat intelligence, containment, recovery, threat hunting
  7. L7: Management and governance: the security posture, regulation, budget, staffing, metrics

way in: Hunches and tacit knowledge (inner)

  1. L1: Tacit knowledge, experience and understanding of the monitored network
  2. L2: Hunch feelings, commonly accurate
  3. L3: Skilled intuition: quick, heuristic (Type 1) decisions, hard to explain

way in: Knowledge of the organisation's own network and devices (inventories, architecture, onboarded devices)

  1. L1: The organisation's network setup and devices, often only partly known to the SOC
  2. L2: Network architecture documentation, device lists, asset inventory, configuration management database
  3. L4: Onboarding: the devices the SOC agreed to receive events from bound its view

way in: Management, regulators and the organisation's demands (metrics, budget, compliance)

  1. L1: Reasons and rules: sensitive data, industry rules (PCI DSS), government rules
  2. L2: Metric pressure relayed down
  3. L3: Funding follows management's perception of value

way in: Reports from employees (human-as-a-security-sensor)

  1. L1: Employees' daily work and mail, where phishing is the attack most often met
  2. L2: An employee notices a phishing mail and reports it

way in: Security alerts from detection tools (IDS, antivirus, firewalls, endpoint tools)

  1. L1: Activity on the enterprise information systems: websites, applications, databases, servers, networks, desktops and other endpoints
  2. L2: Security tools and network devices raise alerts when they detect a threat (signature- or anomaly-based IDSs and others)
  3. L3: Alerts and events collected into the SIEM: normalized, filtered, reduced, aggregated
  4. L4: Correlation rules (directive alarms) and prioritization turn alerts into alarms on the analysts' dashboard

way in: Sound: the room's soundscape and sonified network data

  1. L1: Non-speech audio carrying data (sonification), and the room's own soundscape (a radio, talk, headphones)
  2. L2: Analysts' hearing: attacks can be heard in sonified traffic in some contexts; one SIEM has a sonification module

way in: Strain and morale: monotony, frustration, exhaustion (interoceptive)

  1. L1: Repetitive, monotonous triage under pressure
  2. L2: Felt as frustration and lost confidence
  3. L3: Shows in work: exhausted analysts stop giving detailed updates and cherry-pick events

way in: System, application, network and security logs

  1. L1: Logs record the state of each system and the changes in it
  2. L2: Log generators: operating systems, applications, switches, routers, servers, proxies, mail servers
  3. L3: Collected, pushed or pulled, normalized to one format and time zone, filtered, reduced and aggregated
  4. L4: The SIEM correlates log events, enriches them with context and alerts

way in: The SOC's own metrics (event volume, missed events, processing time, coverage)

  1. L1: The SOC's own work stream: events received, processed, left unprocessed
  2. L2: Metrics generated automatically by the SIEM
  3. L4: Compared across shifts and periods
  4. L5: L2 analysts turn them into metrics and reports for management

way in: Threat intelligence (feeds, open sources, sharing platforms, other organisations)

  1. L1: The threat landscape as others record it: open-source intelligence, sharing platforms, other organisations
  2. L2: Open-source and commercial feeds
  3. L3: Volume held and filtered (17 to 20 terabytes in two months at one SOC; half to be filtered out)
  4. L4: Context for analysis: indicators and reports enrich alerts
  5. L5: Dedicated threat intelligence teams and analysts

way out: Automatic blocking without analysts (Black Hole Router; a reflex set by policy)

  1. L1: The offending address is blocked on the network
  2. L4: A high-confidence alert triggers the block in real time, skipping the analysts

way out: Contain and remediate (block, deactivate, reimage)

  1. L1: The attack activity is cut off on the network or host
  2. L3: Orchestration and automation tools carry it out
  3. L6: Decision on the evidence: block an activity, deactivate an account, watch, or escalate

way out: Escalate to incident management / incident response

  1. L6: Incidents needing in-depth analysis handed to the incident management team

way out: Notify users and device owners (tickets, emails)

  1. L1: Read by the user (on Human's sight channel), who reimages the device
  2. L5: Remediation instructions written to the user

way out: Report to management (metrics and stories)

  1. L1: Read by upper management, who fund or close the SOC
  2. L7: The SOC communicates its value upward

way out: Tune the detection rules

  1. L2: The detection tools' rules are changed (the IDS's rule set)
  2. L5: False positives corrected one by one after validation

Who fills each layer

Sources (27) published science

Ndichu et al., AI-Driven Security Alert Screening and Alert Fatigue Mitigation in Security Operations Centers: A Survey (arXiv:2605.08316)
Vielberth, M., Böhm, F., Fichtinger, I. & Pernul, G. (2020). Security Operations Center: A Systematic Study and Open Challenges. IEEE Access 8:227756-227779. doi:10.1109/ACCESS.2020.3045514 (CC BY 4.0; University of Regensburg repository copy)
Kokulu, F. B., Soneji, A., Bao, T., Shoshitaishvili, Y., Zhao, Z., Doupé, A. & Ahn, G.-J. (2019). Matched and Mismatched SOCs: A Qualitative Study on Security Operations Center Issues. ACM CCS 2019. doi:10.1145/3319535.3354239 (author copy) (behind its links)
Alahmadi, B. A., Axon, L. & Martinovic, I. (2022). 99% False Positives: A Qualitative Study of SOC Analysts' Perspectives on Security Alarms. 31st USENIX Security Symposium (behind its links)
Information security operations center (Wikipedia, via Wikimedia Enterprise snapshot 2026-11-01) (behind its links)
Sundaramurthy, S. C., Bardas, A. G., Case, J., Ou, X., Wesch, M., McHugh, J. & Rajagopalan, S. R. (2015). A Human Capital Model for Mitigating Security Analyst Burnout. SOUPS 2015, USENIX (open access) (behind its links)
Yang, L., Chen, Z., Wang, C., Zhang, Z., Booma, S., Cao, P., Adam, C., Withers, A., Kalbarczyk, Z., Iyer, R. K. & Wang, G. (2024). True Attacks, Attack Attempts, or Benign Triggers? An Empirical Measurement of Network Alerts in a Security Operations Center. 33rd USENIX Security Symposium (open access) (behind its links)
Guidetti, O. A., Speelman, C. & Bouhlas, P. (2023). A review of cyber vigilance tasks for network defense. Frontiers in Neuroergonomics 4:1104873. doi:10.3389/fnrgo.2023.1104873 (PMC10790933, CC BY) (behind its links)
Sundaramurthy, S. C., McHugh, J., Ou, X., Wesch, M., Bardas, A. G. & Rajagopalan, S. R. (2016). Turning Contradictions into Innovations or: How We Learned to Stop Whining and Improve Security Operations. SOUPS 2016, USENIX (open access) (behind its links)
Security operations center (Wikipedia, via Wikimedia Enterprise snapshot 2026-11-01) (behind its links)
Reeves, A. & Ashenden, D. (2023). Understanding decision making in security operations centres: building the case for cyber deception technology. Frontiers in Psychology 14:1165705. doi:10.3389/fpsyg.2023.1165705 (PMC10245128, CC BY) (behind its links)
Cichonski P, Millar T, Grance T, Scarfone K (2012) Computer Security Incident Handling Guide. NIST Special Publication 800-61 Rev. 2. doi:10.6028/NIST.SP.800-61r2 (US government work, not subject to copyright) (behind its links)
Hutchins, Cloppert and Amin, Intelligence-Driven Computer Network Defense Informed by Analysis of Adversary Campaigns and Intrusion Kill Chains, ICIW 2011 (behind its links)
Lain D, Kostiainen K, Čapkun S (2022) Phishing in Organizations: Findings from a Large-Scale and Long-Term Study. IEEE S&P 2022; arXiv:2112.07498 (behind its links)
Joint Task Force Transformation Initiative (2011). NIST SP 800-39, Managing Information Security Risk: Organization, Mission, and Information System View. doi:10.6028/NIST.SP.800-39 (behind its links)
Gelman, Hastings, Herath & Covert 2026, Workplace Surveillance and Insider Threat Risk Management: Legal Limits and Privacy Harms (arXiv:2608.21205v1) (behind its links)
Cyber threat intelligence (Wikipedia, via Wikimedia Enterprise snapshot) (behind its links)
Vulnerability management (Wikipedia, via Wikimedia Enterprise snapshot 2026-11-01) (behind its links)
Happe A, Cito J (2023). Understanding Hackers' Work: An Empirical Study of Offensive Security Practitioners. ESEC/FSE '23. doi:10.1145/3611643.3613900 (arXiv 2308.07057, author's version) (behind its links)
Lain D, Kostiainen K, Capkun S. Phishing in Organizations: Findings from a Large-Scale and Long-Term Study. IEEE Symposium on Security and Privacy 2022; arXiv:2112.07498 (behind its links)
Axon, L., Alahmadi, B., Nurse, J. R. C., Goldsmith, M. & Creese, S. (2018). Sonification in Security Operations Centres: What do Security Practitioners Think? USEC 2018. doi:10.14722/usec.2018.23024 (arXiv:1807.06706) (behind its links)
Network operations center (Wikipedia, via Wikimedia Enterprise snapshot 2026-11-01) (behind its links)
National Security Operations Center (Wikipedia, via Wikimedia Enterprise snapshot 2026-11-01) (behind its links)
Computer emergency response team (Wikipedia, via Wikimedia Enterprise snapshot 2026-11-01) (behind its links)
Chromik, J., Klopfenstein, S. A. I., Pfitzner, B., Sinno, Z.-C., Arnrich, B., Balzer, F. & Poncette, A.-S. (2022). Computational approaches to alleviate alarm fatigue in intensive care medicine: A systematic literature review. Frontiers in Digital Health (PMC9424650, CC BY) (behind its links)
Alarm fatigue (Wikipedia, via Wikimedia Enterprise snapshot 2026-11-01) (behind its links)
Vigilance (psychology) (Wikipedia, via Wikimedia Enterprise snapshot 2026-11-01) (behind its links)