In commercial offers, “we’ll implement a SIEM” and “we’ll connect a SOC” often sound like synonyms. In fact they are different things. A SIEM is a system, a software platform. A SOC is the team and processes that work with that system and other tools. In short: a SIEM shows what is happening, and a SOC decides what to do about it.
Below: how they differ, where EDR, XDR, SOAR and MDR fit into the picture, and how to choose a security monitoring model for a company.
In short
| SIEM | SOC | |
|---|---|---|
| What it is | A software platform | A unit or a service: people, processes and technology |
| What it does | Collects event logs, correlates them and raises alerts | Analyses alerts, investigates incidents, responds and reports |
| Outcome | Alerts and dashboards | An investigated and closed incident, recommendations |
| Doesn’t work without | Connected sources and tuned rules | Data — including from the SIEM — and agreed authority |
| How to get it | A licence or subscription, your own deployment | An in-house team, an external provider (SOC as a Service) or a hybrid |
What a SIEM is
A SIEM (Security Information and Event Management) is a system for collecting and analysing security events. NIST defines a SIEM tool as an application that gathers security data from information system components and presents it as actionable information through a single interface.
In practice a SIEM:
- collects event logs from network equipment and firewalls, servers, endpoints, email and cloud services;
- normalises them — brings records from different systems into one format;
- correlates — matches events from different sources against rules. One failed login is noise. Dozens of failed logins, then a successful login from an unusual place and mass file copying already look like an attack;
- raises alerts and shows them on dashboards;
- stores logs for investigations and reports, including for regulatory requirements.
Examples of platforms: FortiSIEM, Elastic Security, Splunk, Microsoft Sentinel, Wazuh (open source).
On its own, a SIEM does not investigate or make decisions. It raises alerts, and someone has to work through them.
What a SOC is
A SOC (Security Operations Center) is a function that monitors security events, detects and investigates incidents and responds to them. The company itself decides the hours: from business hours to round-the-clock coverage.
A SOC has three parts:
- People. First-line analysts filter out false positives and escalate suspicious events. More experienced analysts investigate incidents, hunt for hidden threats and tune detection rules.
- Processes. Response scenarios (playbooks), escalation rules, the split of roles with IT and the business, reporting.
- Technology. The SIEM is usually at the centre, but not alone: there is also EDR on endpoints, response automation tools (SOAR) and threat intelligence.
The outcome of a SOC’s work is not an alert but a closed incident: what happened is established, the threat is contained, the cause is removed, the lessons are applied. NIST’s incident response recommendations (SP 800-61 Rev. 3, 2025) describe this cycle too: preparation, detection, response and recovery.
Why a SIEM alone is not enough
- There are many alerts, and some are false. Without people to work through them, the real signal is lost in the noise and the SIEM becomes an expensive log archive.
- Rules go stale. Attacks change and the company gets new systems. Correlation rules need constant tuning, and new sources need connecting.
- An alert is not yet a response. Isolating a server, blocking an account, stopping a service — these are decisions that need authority agreed with the business.
- Threats are growing. According to CERT-UA, the team handled 5,927 cyber incidents in 2025 against 4,315 in 2024. Phishing cases numbered 1,727 against 843 a year earlier.
The reverse is also true: a SOC without data is blind. If logs are not collected or are kept for only a few days, there is nothing to investigate.
EDR, XDR, SOAR and MDR: where they fit
- EDR (Endpoint Detection and Response) — protection and telemetry on endpoints: laptops, workstations, servers. Gives the SOC detailed data on processes on the device and lets it isolate the device.
- XDR (Extended Detection and Response) — an extension of EDR: detection based on data from several layers (endpoints, network, email, cloud) with built-in correlation, usually within one vendor’s ecosystem.
- SOAR (Security Orchestration, Automation and Response) — response automation: typical playbook steps (enrich an alert with data, block an address, open a ticket) run automatically.
- MDR (Managed Detection and Response) — a managed service: the provider takes on detection and response, often with its own tools. In substance it is close to SOC as a Service.
EDR, XDR, SOAR and SIEM are tools. A SOC and MDR are the people and processes that use them.
How to choose a model
| Model | When it fits | What to consider |
|---|---|---|
| A SIEM without a team | A small infrastructure with an IT specialist who reviews alerts regularly | Who responds at night, at weekends, during holidays; who tunes the rules |
| An in-house SOC | Large organisations that need full control | Analysts at several levels, a coverage schedule, processes, training — and time to build |
| SOC as a Service | Companies without their own monitoring team, or those that cannot keep up with events from existing tools | The split of responsibilities and service parameters must be written into the contract |
| Hybrid | There is an in-house SIEM or a security specialist, but no capacity for continuous monitoring | Clear boundaries: who monitors, who decides, who fixes the consequences |
What about regulatory requirements
For insurers, credit unions, finance companies and pawnshops, NBU Resolution No. 143 contains requirements that directly concern SIEM and SOC:
- systems must record and store in logs events related to access to settings, identification and authentication and access rights management, and protect these records from modification (paragraph 26 of the Regulation);
- logs are archived at least once a year and kept for at least one year from archiving; only the responsible person has access to them (paragraph 28);
- the responsible information security person monitors and investigates incidents (paragraph 13).
Operations must be brought into line by mid-December 2026. More in “NBU Resolution 143: cybersecurity rules for NBFIs” and “Cyber incident response plan under NBU rules”.
Questions to ask before choosing
- Which systems are critical and should become event sources first?
- Who works through alerts, and in which hours? What happens at night and at weekends?
- How long should logs be kept, given the requirements of your industry?
- Who may isolate a system or block an account, and who approves it?
- What response time is needed for each incident severity level, and where is it written down?
- Which reports do IT and management need, and how often?
How Bereg-IT can help
SOC as a Service is a full monitoring cycle without building your own centre. We connect event sources: network equipment and NGFW, servers, endpoints, web applications and WAF, cloud and email services. We set up correlation and detection rules, filter out false positives and investigate incidents. You receive notifications with a severity assessment and recommended actions, not “raw” alerts. We respond according to an agreed playbook and prepare regular reports.
Who does what is fixed before launch. The coverage schedule, response time and log retention period are written into the contract. If your protection tools still need to be built, we will help with information security.
If an incident is happening right now, see the first steps on the “Security incident” page.
The first consultation is free. Send a request and an information security specialist will get in touch.
Sources
- NIST CSRC Glossary, security information and event management (SIEM) tool (definition from NIST SP 800-128): https://csrc.nist.gov/glossary/term/security_information_and_event_management_tool
- NIST SP 800-61 Rev. 3, Incident Response Recommendations and Considerations for Cybersecurity Risk Management: A CSF 2.0 Community Profile (April 2025): https://csrc.nist.gov/pubs/sp/800/61/r3/final
- SSSCIP, “CERT-UA handled almost 6,000 cyber incidents in 2025: the number of enemy attacks rose by 37%” (07.01.2026, in Ukrainian): https://cip.gov.ua/ua/news/cert-ua-u-2025-roci-opracyuvala-maizhe-6000-kiberincidentiv-kilkist-vorozhikh-atak-zrosla-na-37
- Resolution of the Board of the National Bank of Ukraine of 09.12.2025 No. 143, paragraphs 13, 26, 28 of the Regulation (in Ukrainian): https://bank.gov.ua/admin_uploads/law/09122025_143.pdf