Logo
What Is SOC as a Service and How Does It Work for Mid-Size Indian Companies

14 Nov 2026  Mr Santosh Agarwal

What Is SOC as a Service and How Does It Work for Mid-Size Indian Companies

SOC as a Service (SOCaaS) is a subscription security operations centre run by an external team. It collects logs from your systems, watches them around the clock, investigates alerts and helps you contain real threats. You get the monitoring of a security operations centre without hiring, training and rostering the analysts yourself.

SOC as a Service (SOCaaS) is a subscription security operations centre run by an external team. It collects logs from your systems, watches them around the clock, investigates alerts and helps you contain real threats. You get the monitoring of a security operations centre without hiring, training and rostering the analysts yourself.

For most mid-size Indian companies the real question is not whether someone should be watching the logs at 2 a.m. It is whether you can afford to staff that person, and the tools around them, yourself. This article explains what SOC as a Service does, how it works day to day, what it leaves with you, and eight questions to put to any provider before you sign.

Why a mid-size company struggles to run its own SOC

A security operations centre that watches 24x7 needs people on shift every hour of every day. One industry estimate puts the minimum at 8 to 12 full-time analysts once leave, sickness and night shifts are counted, and that is before you add a manager. Then come the tools: a SIEM platform to collect and correlate logs, threat intelligence feeds, and engineers who write and tune the detection rules. For a company with an IT team of a few dozen people, that is rarely a realistic build.

Attackers do not keep office hours, and the time they spend inside a network before anyone notices is not short. Mandiant's M-Trends 2026 report puts the global median dwell time at 14 days in 2025, up from 11 days the year before. Exploited vulnerabilities were the most common way in, at 32 percent of intrusions. A company that reads its logs during the working day will find out late.

Finding out late is expensive. IBM's 2025 Cost of a Data Breach research puts the average breach in India at ₹22 crore, a record, with an average of 263 days to identify and contain a breach.

What Indian regulation expects of your detection and reporting

No Indian rule says "buy SOC as a Service". Several of them, however, assume that you can detect an incident, keep the evidence and report it quickly.

  • CERT-In Directions (2022). Cyber incidents must be reported to CERT-In within 6 hours of being noticed. Logs must be kept for a rolling 180 days, stored within India.
  • DPDP Rules, 2025. A personal data breach must be intimated to the Data Protection Board without delay, followed by a detailed report within 72 hours. Reasonable security safeguards include access controls, activity logs and backups, and logs must be retained for at least one year. The main obligations are due from 13 May 2027.
  • SEBI CSCRF (August 2024). SEBI-regulated entities must have a SOC that continuously monitors security events. It can sit inside the entity, in a group company or with a third-party provider.

A SOC service does not discharge any of these duties for you. It does make them achievable: the logs are already collected, someone is watching while the reporting clock runs, and the evidence is organised by the time a regulator asks for it.

How SOC as a Service works, step by step

  1. Onboarding and asset mapping. The provider maps what you run: servers, endpoints, cloud workloads, network devices, identity systems and SaaS applications. Together you decide which log sources matter most.
  2. Log and telemetry collection. Collectors or agents forward logs to the provider's SIEM. Ask where those logs are stored, because the CERT-In 180-day rule expects them to be kept in India.
  3. Detection. Correlation rules, behavioural analytics and threat intelligence pick suspicious patterns out of the noise.
  4. Triage and investigation. Analysts review each alert, discard false positives and confirm real incidents. This is where most of the value sits. A SIEM without people watching it is an alarm nobody answers.
  5. Response. Depending on the contract, the provider either recommends actions or takes them with your authorisation, such as isolating an endpoint, disabling an account or blocking an address.
  6. Reporting and tuning. You receive incident reports and periodic summaries, and the detection rules are adjusted to your environment over time.

What the provider handles and what stays with you

The SOC provider typically handlesYou still own
Monitoring and triage of alerts, 24x7Patching and vulnerability remediation
Correlating logs across firewalls, servers, cloud and identity systemsAn accurate inventory of your assets and users
Escalating confirmed incidents with context and a recommended responseAccess policy, multi-factor authentication and password hygiene
Containment actions agreed in advance, such as isolating an endpointDecisions that affect the business, such as taking a system offline
Incident reports and monthly summaries for auditsThe legal duty to report to CERT-In and, where relevant, the Data Protection Board
Tuning detection rules to reduce false positivesBackups and recovery testing

The fifth row catches people out. A provider can supply the evidence and help draft the report, but the obligation to file it stays with your organisation.

In-house SOC, SOC as a Service and MDR: the differences

The labels vary from vendor to vendor, so compare scope rather than names.

 In-house SOCSOC as a ServiceMDR
Who watchesYour own analystsThe provider's analystsThe provider's analysts
Typical focusWhatever you choose to buildLogs from network, servers, cloud, identity and applicationsMostly endpoint tooling, with active response
Cost modelHigh fixed cost: payroll, tools, trainingSubscription, often priced by log volume or number of assetsSubscription, often priced per endpoint
ControlHighestShared: you set scope and approvalsShared
Time to startMonthsDepends on the number of log sourcesDepends on endpoint rollout

How to evaluate a SOC provider: eight questions

These questions work for any provider, including ours. Ask for the answers in writing.

  1. Is monitoring really 24x7 with analysts on shift? Or is the night handled by on-call staff and automated alerts? Ask to see the shift model.
  2. Where are your logs stored, and who can access them? Indian residency matters for the CERT-In 180-day rule and for sector regulators.
  3. What accreditations and certifications does the provider hold? Look for relevant government accreditation, such as NCIIPC, and standards such as ISO 27001, and ask which legal entity holds them: the provider itself or only a parent or partner.
  4. What are the response-time commitments? Time to acknowledge, to triage and to escalate should be written into the SLA, with a remedy if they are missed.
  5. What can the provider do during an incident? Advise only, or act? Which actions need your approval first?
  6. Which log sources can it take in? Firewalls, cloud platforms, endpoints, Microsoft 365, identity systems and your own applications. Check whether onboarding each source is included in the price.
  7. How is detection tuned to your environment? Ask how false positives are handled and request a sample report.
  8. How do you leave? You should be able to export your logs, rules and reports if you change providers.

Where ZeaCloud fits

ZeaCloud provides SOC services together with Fluidech, an NCIIPC-accredited security partner. Because the same group also runs ZeaCloud's sovereign cloud, backup and disaster recovery services, monitoring can be planned alongside the infrastructure it protects, with data held in India. If you are weighing SOC as a Service for the first time, the most useful starting point is usually a conversation about which log sources matter most in your environment.

Talk to a ZeaCloud security architect about the monitoring your environment needs.

Frequently asked questions

How much does SOC as a Service cost in India?

Price depends on the number of log sources or assets monitored, the volume of logs, how long they are retained and how much response work the provider does. Ask for a quote based on your own environment, and compare it with the payroll of 8 to 12 analysts plus tooling that an in-house 24x7 SOC would need.

What is the difference between SOC as a Service and MDR?

SOC as a Service usually monitors logs from across your network, servers, cloud and applications. MDR usually centres on endpoint tooling with active response. Vendors use both terms loosely, so compare what each contract actually covers.

Does SOC as a Service cover cloud workloads and Microsoft 365?

It can, provided the provider integrates those log sources. Ask for the list of supported sources and whether onboarding each one is included in the price.

Does it help with CERT-In and DPDP compliance?

It helps you detect incidents, keep evidence and report within the 6-hour CERT-In window and the 72-hour DPDP breach report. The legal duty to report stays with your organisation.

How long does onboarding take?

It depends on how many log sources you connect and how accurate your asset inventory is. Ask any provider for an onboarding plan with dates before you sign.

Sources

ZeaCloud Services Private Limited is an Indian sovereign cloud provider and a wholly owned subsidiary of NSE-listed Esconet Technologies Limited. This article is part of ZeaCloud's ongoing coverage of security operations and compliance in India.