Buyer guide · Managed security

How do you choose an MSSP in Israel?

YouCC Technologies ·

Choose an MSSP by how it handles a real incident, not by its slide deck. Check four things: an analyst (not just automation) triages alerts around the clock, the response time is contractual, your logs, rules and playbooks stay in your own tenant, and the provider knows your actual platform, whether Microsoft, AWS or a mix. Then ask who pays for log ingestion as volume grows, because that is where most MSSP budgets break.

What an MSSP actually does

A managed security service provider runs your security monitoring and response as a service: it collects logs from your cloud, endpoints, identities and network, triages alerts, hunts for threats that no rule caught, responds to incidents and reports on all of it. For most organizations of 100 to 1,000 employees this costs less than building an internal SOC, which needs at least five or six analysts to cover every hour of the week.

Several terms describe overlapping services. MDR (managed detection and response) focuses on detecting and stopping attacks on endpoints and cloud workloads. SOC as a service usually means monitoring and triage on a platform the provider runs. An MSSP may include both, plus management of security tools such as firewalls, SASE and identity. What matters is not the label but what is written in the contract.

Three types of providers in the Israeli market

  • Large integrators with a central SOC: Broad coverage and a large team, a good fit for enterprises and government. Smaller customers can end up with a standard package and little attention.
  • Dedicated SOC companies: Deep monitoring and response expertise, often on their own platform. Worth checking how well they know your cloud environment, and who fixes what they find.
  • Providers that run both your cloud and your security: The same team operates the infrastructure and monitors it, so a finding can become a fix without passing between two vendors. A good fit for cloud-first organizations on Microsoft 365, Azure or AWS.

What to check before you sign

  • Who triages at night: An analyst who looks at the alert, or an automated forward to your inbox. Ask to see a real night shift report.
  • Response time in the contract: Not "best effort". When does the clock start, at the alert or at the analyst's acknowledgement, and what happens when it is missed?
  • Log ingestion costs: SIEM platforms charge by data volume. Who pays when volume doubles, and is there a cap? This is the most common surprise in the second year.
  • Data and rule ownership: Does the SIEM run in your tenant, such as Microsoft Sentinel in your Azure subscription, or on the provider's platform? If you leave, do your logs, detection rules and playbooks stay with you?
  • Fix, not only alert: Can the provider isolate a device, disable a user or change a policy, with your approval, or does it only notify you?
  • Platform depth: Generic monitoring misses cloud-specific attacks. Ask for examples on your stack: Entra ID, Defender, AWS GuardDuty, or the firewall and SASE you already run.
  • Credentials that are earned: Vendor designations awarded on measured performance, such as Microsoft Solutions Partner for Security, say more than a partner logo.

Israeli regulation shapes the choice

Amendment 13 to the Privacy Protection Law raised the bar on securing personal data and on reporting incidents. The Israel National Cyber Directorate's cyber defense methodology is the common reference for which controls an organization should have. Banks, insurers and other financial bodies also answer to sector rules, such as Bank of Israel Directive 361 and the Capital Market Authority's cyber circulars.

In practice this means an MSSP should help you produce evidence, not only alerts: who saw what, when, and what was done. If your enterprise customers ask for ISO 27001 or SOC 2 reports, the provider's reporting should map to those controls.

Questions to ask every MSSP

  • Who looks at an alert at 3am, and how fast do you commit to respond?
  • Will the SIEM, the rules and the playbooks live in our tenant, and stay with us if we leave?
  • Who pays for log ingestion when our data volume grows, and is there a cap?
  • Can you contain a threat yourselves, with our approval, or only alert us?
  • Show us an incident you handled on a stack like ours.
  • Which vendor designations do you hold today, and what were they awarded for?
  • Who speaks Hebrew with our management, and with a regulator, during an incident?
  • What does the monthly report look like, and who reviews it with us?

Where YouCC fits

YouCC is a provider of the third type: the same certified engineers run Microsoft 365, Azure and AWS environments and the security operations on top of them, from a 24/7 SOC with Hebrew-speaking support in Petah Tikva. YouCC is a Microsoft Solutions Partner for Security, deploys and operates Microsoft Sentinel and Defender, and also manages network security such as Fortinet FortiSASE.

Common questions

How much does an MSSP cost in Israel?

Pricing is usually per user, per endpoint or per monitored asset, plus the SIEM's data ingestion costs, which are often billed separately. Compare proposals on the same scope and include ingestion at your expected volume in a year, not only today's.

What is the difference between an MSSP and MDR?

MDR focuses on detecting and responding to attacks, mainly on endpoints and cloud workloads. An MSSP is broader and can also manage security tools, such as firewalls, SASE and identity policies. Many providers offer both under one contract.

Do we need our own SIEM?

Not necessarily, but owning it, for example Microsoft Sentinel in your Azure subscription, means your logs and detection rules stay with you if you change provider. If the provider runs its own platform, make sure the contract defines how your data is exported when you leave.

How long does it take to switch MSSP?

Usually four to eight weeks: connecting log sources, rebuilding or migrating detection rules, and a tuning period to cut false positives. Running the old and new provider in parallel for a few weeks avoids a gap in coverage.

Does an MSSP replace a CISO?

No. An MSSP runs operations; a CISO owns risk, policy and the conversation with management. Organizations without a full-time CISO often combine an MSSP with a part-time or virtual CISO.

Related reading