
14 Nov 2026 Mr Santosh Agarwal
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.
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.
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.
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.
| The SOC provider typically handles | You still own |
|---|---|
| Monitoring and triage of alerts, 24x7 | Patching and vulnerability remediation |
| Correlating logs across firewalls, servers, cloud and identity systems | An accurate inventory of your assets and users |
| Escalating confirmed incidents with context and a recommended response | Access policy, multi-factor authentication and password hygiene |
| Containment actions agreed in advance, such as isolating an endpoint | Decisions that affect the business, such as taking a system offline |
| Incident reports and monthly summaries for audits | The legal duty to report to CERT-In and, where relevant, the Data Protection Board |
| Tuning detection rules to reduce false positives | Backups 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.
The labels vary from vendor to vendor, so compare scope rather than names.
| In-house SOC | SOC as a Service | MDR | |
|---|---|---|---|
| Who watches | Your own analysts | The provider's analysts | The provider's analysts |
| Typical focus | Whatever you choose to build | Logs from network, servers, cloud, identity and applications | Mostly endpoint tooling, with active response |
| Cost model | High fixed cost: payroll, tools, training | Subscription, often priced by log volume or number of assets | Subscription, often priced per endpoint |
| Control | Highest | Shared: you set scope and approvals | Shared |
| Time to start | Months | Depends on the number of log sources | Depends on endpoint rollout |
These questions work for any provider, including ours. Ask for the answers in writing.
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.
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.
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.
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.
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.
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.
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.