As protection tools multiply, someone has to work through their alerts — every day, and often at night. According to CERT-UA, the team handled 5,927 cyber incidents in 2025 against 4,315 a year earlier. So the question is no longer whether security monitoring is needed, but who will do it: your own team, an external SOC or both together.
We covered what SIEM and SOC are and how they differ in “SIEM vs SOC: the difference for business”. Here — how to choose the model.
In short
| In-house SOC | SOC as a Service | Hybrid | |
|---|---|---|---|
| Who does the work | Your analysts and engineers | The provider’s team | Partly you, partly the provider |
| What it takes to start | Hiring, processes, technology, premises | Connecting event sources and agreeing playbooks | A clear split of roles |
| Control | Full | Within the contract and SLA | Shared |
| Knowledge of your business | The deepest | Context has to be handed over at the start | Stays with your team |
| Round-the-clock cover | Needs shifts — and people for them | If written into the contract | The provider often takes nights and weekends |
| Main costs | Salaries, training, licences, premises | The service fee | Both, on a smaller scale |
How many people a round-the-clock SOC needs
A week is 168 hours, not 40. The EU Agency for Cybersecurity, ENISA, gives a benchmark in its guide to setting up a CSIRT and SOC: operating 24/7 all year needs at least 12 additional employees — six teams of two, in eight-hour shifts. It also notes that 24/7 shift work can become very expensive.
That is only the first line. You also need experienced analysts for investigations, an engineer who connects sources and tunes detection rules, a manager and training for everyone.
This is why ENISA lists typical compromises: operate only during business hours; have someone on duty for emergency escalations; outsource night and weekend monitoring to an external party for initial triage; rely on an existing 24/7 network operations centre.
When an in-house SOC makes sense
- Scale. Many systems, sites and events that justify a team of your own.
- Deep integration with the business. Response is closely tied to internal processes, and decisions are made on the spot.
- Resources to build it. There is budget, time and the ability to hire and keep analysts.
- Maturity. A security lead, protection tools, logging and response processes are already in place.
When SOC as a Service makes sense
- There is no in-house security monitoring team.
- Protection tools are in place, but nobody has time to analyse their events.
- There are regulatory requirements for logging and incident response.
- Nights, weekends and holidays need to be covered.
- Monitoring has to start sooner than an in-house centre could be built.
Hybrid
ENISA notes that a SOC can consist of internal and outsourced staff, and that over time organisations move between the two. A typical split: the provider runs round-the-clock monitoring and initial triage, while the internal team makes decisions, handles escalations and fixes root causes. A hybrid works only when the boundaries of responsibility are written down in advance.
What to put in the contract
- Event sources and the critical assets to connect first.
- Monitoring hours — a coverage schedule that matches how critical the systems are.
- Response time — separately for each incident severity level.
- Log retention that takes your industry’s requirements into account.
- Who decides on isolating systems, especially business-critical ones, and who fixes the root cause.
- Reporting — format and frequency for IT and management.
- Confidentiality and access — an NDA, what access the provider gets, where your logs are stored.
- End of contract — return of data and revocation of access.
NBU requirements for NBFIs
Insurers, credit unions, finance companies and pawnshops can hand part of the work to an external contractor. NBU Resolution No. 143 (paragraph 9) allows them to engage persons entitled to provide such services for information security measures and incident response, on two mandatory conditions:
- the contract contains non-disclosure provisions (an NDA);
- the contractor is not a resident of the aggressor state, has no ultimate beneficial owners resident there, does not process or store data in clouds or data centres located in that state or in the temporarily occupied territories, and is not under sanctions.
At the same time, the NBFI’s responsible person monitors and investigates incidents (paragraph 13). So an external SOC works together with that person, not instead of them. More in “NBU Resolution 143: cybersecurity rules for NBFIs” and “Cyber incident response plan under NBU rules”.
Questions to ask a provider
- Which event sources do you connect and what do you need from us?
- Who works through alerts at night and at weekends?
- What do we receive: “raw” alerts or notifications with a severity assessment and recommended actions?
- Who may isolate a system, and on what terms?
- Where are our logs stored and who can access them?
- What does a regular report look like? Ask for a sample.
- What happens to the data and access when the contract ends?
How Bereg-IT can help
Bereg-IT’s SOC as a Service is a full cycle from event to closed incident without building your own centre. We connect 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, investigate incidents and respond according to an agreed playbook. You receive notifications with a severity assessment and recommended actions, and regular reports.
Who does what is fixed before launch, and the coverage schedule, response time and log retention period are written into the contract. You can start with a consultation or audit: it shows which event sources are critical and what to connect first.
The first consultation is free. Send a request and an information security specialist will get in touch.
Sources
- ENISA, How to set up CSIRT and SOC (10.12.2020) — SOC models, round-the-clock shifts and typical compromises: https://www.enisa.europa.eu/publications/how-to-set-up-csirt-and-soc
- 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 9, 13 of the Regulation (in Ukrainian): https://bank.gov.ua/admin_uploads/law/09122025_143.pdf