What is a SOC, and how does 24/7 monitoring work?
A security operations center (SOC) is the team, process and tools that watch an organisation’s systems for attacks and respond when something goes wrong. Here is what a SOC does day to day, who works in one, and how to decide between building your own and using a managed SOC.

- A SOC is a function, not a room: people, process and tools that watch for attacks and respond to them.
- Its daily work is collecting logs, triaging alerts, investigating the real ones, containing threats and improving detections.
- Round-the-clock cover needs several people per shift, which is why many companies use a managed SOC instead of building one.
- A SOC is only as good as what it can see: if a system sends no logs, the SOC is blind to it.
- Judge a SOC by how fast it confirms and contains real incidents, not by how many alerts it processes.
What a SOC is
A security operations center (SOC, sometimes spelled centre) is the part of an organisation that watches for cyber attacks and deals with them. It can be a team in a dedicated room, a few people working remotely, or an outside provider. What makes it a SOC is the job: see what is happening across your systems, decide what is dangerous, and act.
Without a SOC, warning signs such as a login from an unusual country, malware on a laptop or a sudden spike in data leaving the network often sit unread in a log until the damage is done.
What a SOC does every day
- Collects. Logs and alerts flow in from laptops and servers, email, identity systems, firewalls, cloud accounts and business apps, usually into a SIEM (security information and event management) platform.
- Triages. Analysts sort alerts: false alarm, harmless but odd, or worth investigating.
- Investigates. For serious alerts, they piece together what happened, which accounts and machines are involved, and whether an attacker is active.
- Responds. They contain the threat, for example by isolating a device or disabling an account, and hand larger incidents to an incident response team.
- Hunts. They look for attackers that did not trigger any alert, often guided by known techniques in MITRE ATT&CK.
- Improves. Every incident leads to better detection rules, fewer false alarms and fixes for the gaps it exposed.
Who works in a SOC
| Role | What they do |
|---|---|
| Tier 1 analyst | Watches the alert queue, closes false alarms and escalates real issues |
| Tier 2 analyst | Investigates escalated alerts in depth and starts containment |
| Tier 3 / threat hunter | Hunts for hidden attackers and handles the most complex incidents |
| Detection engineer | Writes and tunes the rules that turn raw logs into useful alerts |
| SOC manager | Runs shifts, reporting and the link to leadership and IT |
Smaller SOCs combine these roles. What matters is that someone qualified is awake and watching at every hour, including nights, weekends and holidays.
Build your own SOC or use a managed one?
Covering every hour of the year takes several people per role once you allow for shifts, leave and training, plus the tools and the time to tune them. That is why many organisations choose a managed SOC, where a specialist provider supplies the team, process and often the tools. A closely related option is MDR (managed detection and response).
- In-house SOC suits large organisations with strict data rules, deep budgets and the ability to hire and keep security analysts.
- Managed SOC suits most small and mid-sized companies: 24/7 cover from day one, with your team keeping ownership of decisions.
- Hybrid is common too: your own team works office hours, and a provider covers nights, weekends and overflow.
What good SOC monitoring looks like
- Wide visibility. Endpoints, email, identity, cloud, network and the apps that hold your data, including AI tools and agents.
- Clear authority. Written agreement on what the SOC may do on its own and when it must call you.
- Measured speed. Target times to triage alerts and contain confirmed incidents, reported every month.
- Tuned detections. Rules mapped to real attacker techniques and reviewed regularly, not left at vendor defaults.
- Useful reports. Real threats, open risks and next steps, rather than a count of alerts processed.
What a SOC cannot do alone
A SOC finds and stops attacks in progress. It cannot see systems that send it no logs, and it does not fix the weaknesses attackers use. Pair it with regular vulnerability management and penetration testing, tested backups and an incident response plan, as described in NIST SP 800-61.