Skip to content
Let’s talk
Analista de seguridad revisando datos en pantalla en una oficina a oscuras

SOC in cybersecurity: what it is, how it works and when it makes sense for a Spanish SME

A tender may require security monitoring capabilities and an incident may lead you to review how you detect threats. Before choosing an in-house, outsourced or hybrid SOC, it’s worth pinning down the risk, the applicable obligations and the coverage you need. NIS2 doesn’t require every SME to hire a SOC.

We explain what a SOC is, how it relates to MDR, MSSP and SIEM and what to review to decide whether it fits your company.

What a SOC is in cybersecurity

A SOC (Security Operations Center) is a unit — physical, virtual or mixed — that combines people, processes and technology to monitor, detect and respond to cybersecurity threats continuously. Usually 24/7.

A useful analogy is an airport control tower: it doesn’t fly the planes, but it makes sure none of them collide, coordinates whoever needs to act in an emergency and keeps order. A SOC doesn’t manage your infrastructure either. It watches what happens in it and triggers protocols when something smells wrong.

In Spain the term COS, Centro de Operaciones de Seguridad, is also used. The CCN-STIC 896 guide covers the compliance profile for managed security services and the maturity levels of SOCs; it doesn’t turn any service using those initials into a certified service.

What a SOC really does, step by step

When a provider sells you a SOC, it’s selling you a continuous process with five phases. Not software.

Continuous prevention

The SOC uses the asset inventory and vulnerability information to guide monitoring. Patching, configuration changes and policy updates must be assigned to the responsible team according to the agreed scope; they aren’t automatically included in every SOC service.

Detection and monitoring

SIEM and EDR/XDR provide logs and signals to detect suspicious activity. Alerts depend on the sources connected, the rules and how they’re tuned. An unusual login time or a large transfer needs context; not every anomaly is detected or means an attack.

Investigation and triage

Not every alert is an attack. The L1 analyst filters out noise. If it looks bad, they escalate to an L2 who investigates the context. If the incident is complex, an L3 takes it on and carries out proactive threat hunting and forensics.

Response and containment

When an incident is confirmed, the team follows the agreed procedure: it can isolate devices, block connections, revoke credentials and preserve evidence. Acting quickly can limit the impact; it doesn’t allow a universal ratio between response minutes and incident cost to be set.

Recovery and learning

After containment, it’s time to restore systems, verify that the attacker has no persistence left and document. The least visible but most valuable part: each incident updates the playbooks, detection rules and controls. So it doesn’t happen the same way again.

The three pillars: people, processes, technology

A SOC that doesn’t have all three in balance isn’t a SOC. It’s an expensive dashboard.

People

L1 analysts (triage, 24/7), L2 (in-depth investigation), L3 (incident response and threat hunting), plus a SOC manager and often detection engineers who fine-tune the rules. In SMEs with an outsourced SOC, this team is at the provider, not on your payroll.

Processes

Playbooks, response commitments, escalation and communication channels with the relevant recipients depending on the incident. For significant incidents, Article 23 of NIS2 provides, as a general rule, for an early warning within 24 hours and notification within 72 hours of becoming aware, with exceptions and a later final report. The applicable national framework must be checked. Source: NIS2 Directive.

Technology

SIEM at the core (Splunk, Microsoft Sentinel, Elastic, Wazuh), SOAR to automate repetitive responses, EDR/XDR on endpoints (SentinelOne, Microsoft Defender for Business, Sophos), threat intelligence feeds and ticketing for traceability. Without technology there’s no SOC. With technology alone, there isn’t one either.

SOC vs MDR vs MSSP vs SIEM: they aren’t the same

These terms describe functions, services and tools that can overlap. Comparing the scope of the contract avoids confusing a platform with the team and procedures that use it.

ItemWhat it isWhat’s includedWho buys it
SOCFunction / organisational unitPeople + processes + technology (all of it)Companies that want full operational cybersecurity capability
MDR (Managed Detection & Response)Outsourced commercial serviceDetection + active response, focused on endpoint and networkSMEs and mid-sized companies that need 24/7 without building their own SOC
MSSP (Managed Security Service Provider)Managed security service providerMay offer SOC, MDR, managed firewall, pentesting, audits…Companies that outsource layers of security by contract
SIEM (Security Information & Event Management)Technology platform (software)Log collection and correlation + alertsIn-house SOCs or providers that build detection on top of it

A SIEM is a tool; a SOC is an operational security capability; MDR is a managed detection and response service; and MSSP refers to a managed security provider. Commercial names don’t on their own define the scope. Ask which sources are monitored, who responds, during what hours and what actions they can take.

SOC models: in-house, outsourced or hybrid

In-house SOC (dedicated)

Your own team, infrastructure and tools. Feasibility depends on the risk, workload, shifts, absences, specialisation and budget. There’s no universal employee threshold or number of analysts that on its own guarantees a 24/7 SOC.

Outsourced SOC (SOCaaS)

You contract a provider for the defined services and coverage. The fee may depend on the devices, the data processed or the scope. It’s a way to access a shared team without building all the capability internally; it’s worth comparing costs, responsibilities and dependencies.

Hybrid SOC (co-managed)

Your in-house IT handles the day-to-day. The provider contributes 24/7 monitoring, threat hunting and out-of-hours response. It’s usually the most efficient model for companies with capable in-house IT but no capacity for shifts. At islaNet it’s the model we most often recommend for SMEs with 50–250 employees in the Balearic Islands.

Does your SME need a SOC? Four clear scenarios

These four scenarios justify evaluating your detection and response capability. The right solution may be in-house, managed or combined and should respond to the specific risk and requirements.

Your sector is covered by NIS2

If your activity fits NIS2’s types of entity, review size, exceptions and applicable national regulations. Article 21 requires measures proportionate to risk, not the universal purchase of a SOC. A SOC can support detection and response, but it doesn’t on its own prove compliance or replace the entity’s responsibility. More in NIS2 compliance.

Your clients or suppliers ask for it

A contract or tender may require monitoring, response and specific evidence. Check the scope and award criteria: hiring a SOC can help meet a requirement, but it doesn’t guarantee winning the contract.

You’ve suffered an incident and don’t want another

After an incident it’s worth reviewing which signals were missing and how alerts were handled. A SOC can improve detection and response, but it doesn’t guarantee discovering every attack before it causes damage.

You’re in a high-risk sector

Hotels, healthcare organisations, logistics, finance and law firms handle systems or information whose unavailability or exposure can have significant consequences. Assess the impact and probability in your case; not every attack is inevitable.

How to choose a SOC provider: a practical checklist

If you’ve already decided to outsource, these are the seven criteria that separate a real SOC from one that only sells the badge.

Response SLAs written into the contract

Maximum time to acknowledge, analyse and contain, by criticality level. If the SLA isn’t in writing, it doesn’t exist.

Real, demonstrable 24/7 coverage

Ask how many analysts there are per shift, where they work from and how they demonstrate night-time coverage. A “24/7” SOC with two analysts in total isn’t 24/7.

Provider and team certifications

Check the scope and validity of relevant certifications, such as ISO 27001 or ENS, and SOC 2 assurance reports where applicable. SOC 2 is an audit report, not an ISO certification. Also assess the team’s experience and credentials in light of the service contracted.

Transparency about the technology stack

Ask for information about the SIEM, EDR, intelligence sources and third-party dependencies. The provider should explain the architecture and responsibilities in enough detail to assess the service, within the necessary confidentiality limits.

Integration with your current stack

Microsoft 365, Google Workspace, ERP, CRM, firewalls and cloud services can provide useful logs. Identify which sources are integrated and what’s left out: lack of visibility makes investigation harder, although it doesn’t show where an attack will occur.

Executive reporting, not just technical

Monthly reports management can read: incidents detected, mean time to contain, maturity. If the reporting is a wall of alerts, management loses context and the SOC loses internal sponsorship.

Real response exercises

Regular tabletop exercises with management and a purple team exercise at least once a year. With a SOC that never tests you, you won’t know whether it works until the worst happens.

Primary sources: CISA StopRansomware · NIST SP 800-61r3 · NIS2, Arts. 2, 21, 23.

SOC FAQs

“We’re small, nobody’s going to attack us”

Size doesn’t eliminate the risk. An SME can suffer credential theft, fraud or service interruptions. It’s worth assessing assets, exposure and controls, without using a general percentage of attacks as a diagnosis of your company.

“I already have an IT person, why would I want a SOC?”

They’re different things. Your IT person manages systems: making sure they work, are up to date and people can do their jobs. A SOC monitors security 24/7 with specific tools and processes. They don’t replace each other, they complement each other. A SOC normally works on the infrastructure your IT already maintains.

What’s the difference between a SOC and a NOC?

A NOC focuses on the availability and operation of networks and services; a SOC focuses on detecting, investigating and responding to security threats. They can share data sources and coordinate. Check which security tasks your IT provider actually includes.

Can I set up an in-house SOC with 2–3 people?

Two or three people on their own can hardly sustain all the shifts, rest periods, holidays and specialities of a 24/7 staffed operation. Size coverage and cover arrangements with a real plan. An outsourced or hybrid model can provide additional capacity, depending on its contract.

What are L1, L2 and L3 SOC analysts?

L1 does initial alert triage and filters out false positives. L2 investigates what looks bad, correlates events and escalates if it’s a real incident. L3 handles complex incident response, digital forensics and proactive threat hunting. The career path starts at L1 and progresses with experience and certifications.

Does a SOC replace antivirus or a firewall?

No. A SOC uses signals from different sources, such as endpoints, the firewall, identity, email and the cloud. These tools and the review processes complement each other. Alert review can also exist outside a formal SOC; what matters is assigning owners, coverage and actions.

Do you subcontract the SOC to another country?

At islaNet, no. We run the SOC from Palma with our own technicians. When a critical alert fires at 3 in the morning, one of our technicians in Mallorca picks up, not an operator in another time zone or a generic call centre.

Does NIS2 require every SME to have a SOC?

There’s no universal obligation for every SME to hire a SOC. NIS2’s scope depends on activity, size, business relationships and exceptions; being a supplier doesn’t automatically make you an obliged entity. The applicable national regulations need checking. A SOC can support detection and response measures, but it doesn’t on its own prove compliance. A cybersecurity audit can help review your case.

Etiquetas

Keep reading

See the blog

Would you rather we explained it for your case?

If a guide has left you with a specific question about your company, tell us about it in a free 30-minute call. We’ll tell you where to start, no strings attached.

Book a free 30-minute call

+34 871 030 201 · Carrer de Can Martí Feliu, 4, Palma

Cookies

We use Google Analytics and Google Ads cookies to see how people find us and which enquiries the website brings in. They are only switched on if you accept. Cookie policy