WCWealth CRM Direct
Guides › Security

Managed SOC or In-House? How Banks Should Decide Who Watches Their Network

Round-the-clock monitoring takes roughly 8 to 12 analysts once leave and turnover count. Here's the staffing math, what DORA, MAS and RBI expect from outsourcing, and when a hybrid SOC wins.

Wealth CRM Direct editorial team · November 2026 · 7 min read

The decision is about accountability at 3 a.m., not tooling

Every bank already owns security tools. What it has to decide is who watches the alerts those tools produce, at every hour of the year, and who answers to the regulator when something gets missed. There are three routes: build an in-house security operations center, buy a managed SOC for banks (most often delivered as managed detection and response, or MDR), or split the work between your staff and a provider.

Most institutions start by comparing prices. Price matters, but three other factors usually settle it: whether you can staff 24x7 coverage and keep it staffed, what your supervisor expects from an outsourced arrangement, and where your log data is allowed to sit. Get those right and the commercial choice gets simpler.

Advertisement

Our position: most banks and lenders with fewer than roughly 3,000 employees should outsource round-the-clock triage. Large or heavily targeted institutions should keep threat hunting and incident command in-house, whatever else they buy. The rest of this piece explains why.

Why 24x7 coverage takes 8 to 12 analysts

A year has 8,760 hours. After annual leave, public holidays, sick days and training, one full-time analyst puts in roughly 1,600 to 1,800 working hours, depending on the country. Leave entitlements in much of Europe and the Middle East run well above those in the US, which pushes headcount up.

Keeping one seat filled around the clock takes about five people. A bank shouldn't run a single-analyst night shift, though. One person can't investigate an incident while new alerts keep arriving, and can't second-check their own decision to escalate. With two analysts on every shift, you need about ten people.

Coverage modelSeats filled at all timesAnalysts needed (approx.)Plus
Business hours only, on-call overnight1 to 2 in daytime3 to 4On-call rota, slower night response
24x7, single analyst15 to 6Shift lead, detection engineer
24x7, two-analyst minimum29 to 11SOC manager, 1 to 2 engineers

Then there's turnover. SOC analysts change jobs often, and a new hire typically needs several months before working a night shift alone. If two people leave in a year, you're short for much of it unless you hire ahead of attrition. That's why realistic plans land at 8 to 12 analysts, plus a manager and engineers who sit outside the shift rota.

MDR pricing versus SOC staffing costs

Take a hypothetical mid-sized bank with 2,000 employees, about 2,500 endpoints and a few hundred servers and cloud workloads. The figures below are indicative typical 2026 market ranges. They vary widely by contract, scope and country, so confirm with vendors.

Cost lineIn-house 24x7 SOCMDR / managed SOC
People10 to 14 FTEs; roughly $0.9M to $2M per year in US, UK or Western European salary markets, often much lower in India or Southeast AsiaIncluded in the service fee
SIEM / data platformRoughly $150K to $600K per year, driven by daily ingest volumeSometimes bundled, often still licensed by the bank
Service feeNot applicableOften $8 to $25 per endpoint per month, or ingest-based pricing; roughly $250K to $750K per year at this size
Time to stand upCommonly 9 to 18 monthsCommonly 6 to 12 weeks onboarding

On paper MDR usually looks cheaper. Three cost drivers narrow the gap:

  • Response scope. Some providers stop at a ticket describing what they found. Others isolate hosts, disable accounts and contain the threat. Active response costs more and needs pre-agreed authority.
  • Data ingest. Ingest-based contracts climb quickly once you add core banking, payment switch and cloud logs.
  • Retained internal staff. You still need people to own the relationship, tune detections against your fraud and payments context, and run incidents. Budget for two to four FTEs even when you outsource fully.

Widely available options include CrowdStrike Falcon Complete, Microsoft Defender Experts, Palo Alto Networks Unit 42 MDR, Sophos MDR, Arctic Wolf, Rapid7 and Expel, plus large integrators and regional MSSPs. Global coverage, local-language analysts and in-country data handling differ considerably between them.

What DORA, MAS TRM and RBI expect from security operations center outsourcing

Regulators don't ban security operations center outsourcing. They insist that accountability stays with the bank's board and management. Details differ by jurisdiction, but the expectations overlap.

  • European Union (DORA). An MDR provider is an ICT third-party service provider and belongs in your register of information. The contract needs the mandated provisions on service levels, audit and access rights, incident assistance and exit strategies. If the service supports critical or important functions, as monitoring usually does, expect closer supervisory attention. The provider must also support your major-incident classification and reporting deadlines, which are tight.
  • Singapore (MAS TRM Guidelines and Outsourcing Guidelines). MAS expects due diligence on the provider, ongoing oversight, and audit and access rights for both the institution and MAS. Incident notification deadlines are short, so the provider's escalation path has to reach your people within minutes.
  • India (RBI and CERT-In). RBI's Master Direction on outsourcing of IT services keeps responsibility with the regulated entity and requires risk assessment, audit rights and business-continuity arrangements. CERT-In's rules add a short incident-reporting window and log-retention expectations, including keeping logs within Indian jurisdiction.
  • Elsewhere. The UK's PRA and FCA outsourcing and operational resilience rules, Saudi Arabia's SAMA Cyber Security Framework and UAE central bank guidance follow similar lines: materiality assessment, contractual audit rights, tested exit plans and fast incident escalation.

A provider whose standard contract lacks audit rights, subcontractor disclosure and a documented exit plan isn't ready to serve a regulated bank, however good its detection is. Interpretation varies, so have compliance and outside counsel review the contract against your regulator's current text.

Log data residency and who can see your telemetry

Residency often settles the decision. Logs from core banking, payments and identity systems contain customer identifiers, account numbers and transaction metadata. Where those logs are stored, processed and viewed from is regulated in many markets.

India's payment data localization rules and CERT-In log requirements, data-sovereignty rules in Saudi Arabia and Indonesia, and GDPR transfer restrictions in Europe all shape the design. A follow-the-sun MDR service, where analysts on three continents view your raw logs, can count as a cross-border transfer even when storage stays in-country.

Ask every provider these questions in writing:

  1. In which regions are logs ingested, stored and backed up, and can you pin them to one region?
  2. From which countries do analysts access the data, and can you restrict access to cleared staff in named locations?
  3. Which subcontractors and cloud sub-processors touch the data?
  4. Can sensitive fields be masked or tokenized before they leave your environment?
  5. How is data returned and deleted on exit, and on what timeline?

Treat "our cloud is global" as a red flag. Prefer architectures where the SIEM or data lake sits in your own tenancy and the provider works inside it, rather than copying your logs to their platform.

When a hybrid model is the better fit

Hybrid usually means the provider handles 24x7 alert triage and first-line containment, while your team owns threat hunting, detection engineering, incident command and the link to fraud operations. For many institutions it's the best of the three structures. Triage is high-volume, repetitive shift work, which is the hardest to staff. Threat hunting depends on knowing your payment flows, privileged users and fraud patterns, and an external analyst covering dozens of clients rarely builds that depth.

Managed detection and response for financial services works best this way when three things are defined up front: which alerts the provider can contain without calling you, who is on call to accept escalations, and how quickly detection rules your hunters write get deployed into the provider's pipeline.

A practical decision rule:

  • Fully outsource if you can't fund at least ten security operations staff, or can't retain them in your labor market.
  • Go hybrid if you have three to six capable security staff, face targeted fraud or payments attacks, or your regulator expects demonstrable in-house incident capability.
  • Build in-house only if you can staff 12 or more analysts, need in-country handling no provider can meet, or treat security operations as a competitive asset.

Your next step: run the staffing math against your own leave policy and local salary bands, then send three providers the five residency questions and a request for their standard contract. Their answers on audit rights and data location will narrow the shortlist faster than any detection demo.

Common questions

Can a small bank or credit union rely entirely on a managed SOC?

Yes, and for most small institutions it's the realistic way to get true 24x7 coverage. You still need one or two internal people to own the provider relationship, approve containment actions and lead incident response, because regulators hold the institution accountable, not the provider.

What's the difference between an MSSP and MDR?

A traditional MSSP typically manages security devices and forwards alerts, leaving investigation and response to you. MDR providers investigate alerts, hunt for threats and often take containment actions such as isolating endpoints or disabling accounts. Contracts blur these labels, so judge providers by the written scope of response, not the product name.

How is MDR typically priced?

Most providers charge per endpoint or user per month, by daily log ingest volume, or a mix of both. Typical 2026 market ranges run roughly $8 to $25 per endpoint per month, with active response, extra log sources and dedicated analysts adding cost. Pricing varies by region and contract, so get quotes against your actual endpoint count and ingest volume.

Does outsourcing the SOC satisfy DORA or similar rules?

Outsourcing is permitted, but it doesn't transfer accountability. You still need due diligence, contractual audit and access rights, incident reporting support, register entries and a tested exit plan. Ask compliance and qualified legal counsel to check the arrangement against your regulator's current requirements.

Written by the Wealth CRM Direct editorial team. Prices, features and rules change often - confirm details with the vendor or a licensed professional before you decide.