The real test
What a managed SOC quote commits to at three in the morning
We do not have an office in Saudi Arabia
We serve organisations there from our Riyadh office and our engineering hubs in Lahore and Karachi, travelling for the parts of an engagement that need to happen in person.
The moment a SOC contract is really priced for is not the demo but the overnight incident: an alert fires at three in the morning, and what happens next depends entirely on what was bought. Under one contract a qualified analyst investigates and isolates the affected host within the hour; under a cheaper one, an email waits in a queue for your own team to find at nine. Both were sold as "managed SOC", and the difference between them was never in the total — it was in the coverage window and the authority to act.
That is why comparing SOC offers on the monthly figure alone is meaningless. The figure is an output; the inputs are the six commitments below, and until they are pinned down identically across suppliers, a lower number tells you only that less was promised.
The inputs
The six commitments behind a managed SOC's monthly figure
Each commitment moves the figure in a known direction. None of them is a price, and any offer that quotes one before settling them has answered these questions for you, silently.
| Variable | Effect on price | Why |
|---|---|---|
| Log volume and sources | The metered input | Every server, endpoint, cloud account and application you connect adds telemetry to ingest, store and tune detections over, and most SOC pricing scales with that volume in some form. The discipline that controls this line is scoping which sources genuinely matter to detection rather than forwarding everything and paying to store noise. |
| Coverage hours | 8×5 and 24×7 are different services | Staffing qualified analysts through nights, weekends and holidays is where much of a SOC's cost structure lives, which is why around-the-clock coverage costs so much more than business hours. Incidents do not keep office hours; the honest way to choose is to ask what an attack discovered on Sunday morning instead of Thursday night would cost the business. |
| Response scope | Watching is cheaper than acting | A SOC that only alerts costs less than one authorised to isolate a host, disable an account or block traffic on your behalf, because containment carries playbooks, rehearsal and accountability. Decide in advance how far the provider may go without waking you — that authority, written down, is much of what the higher figure buys. |
| Data residency requirements | Constrains who can serve you, and how | A requirement to keep logs and their processing in-country narrows the platforms, locations and providers that qualify, and shapes the architecture of the whole service. It is a legitimate requirement for many organisations here — but it has to be named at scoping, because retrofitting residency onto a running service is a redesign, not a setting. |
| Tooling ownership | Whose SIEM sets the exit cost too | Monitoring on the provider's stack onboards faster and often quotes lower, but leaving means migrating detections and history you never owned. Monitoring on your own SIEM keeps the data and the tuning yours, and pays instead for the licences and the skills to run it. Neither is wrong; the choice moves both the monthly figure and the cost of ever changing provider. |
| Onboarding effort | The first months are their own project | Connecting sources, tuning detections to your environment and writing the playbooks the analysts will follow is real work that happens before the service protects anything. An offer that shows only a monthly figure has either buried onboarding inside it or left it out — and in the second case, detection coverage arrives months later than the invoice does. |
Ask any supplier quoting this
- Which log sources are inside this figure, and what happens to the price as volume grows?
- Who exactly is watching at 3am on a Friday, and from where?
- On a confirmed incident, are you authorised to contain it, or do you notify us and wait?
- Where is our telemetry stored and processed, and can you keep it in-country if we require that?
- If we leave after two years, who owns the detections, playbooks and log history?
- What does onboarding involve, and when does detection coverage become real rather than contractual?
Coverage shapes
Three shapes of managed SOC service and where the money concentrates
Not a ranking — each shape fits a different risk appetite. The point is what each one leaves with your own team when the alert fires.
| Option | Coverage window | Action on detection | Where the cost concentrates | What stays with your team | Best for |
|---|---|---|---|---|---|
| Business-hours monitoring | Working days, working hours. | Alerts investigated and escalated to you during the window. | A small analyst pool and the tooling — the lightest structure. | Everything outside the window, including the incidents that prefer it. | Organisations with their own on-call capability who need depth during the day, not a night shift. |
| Around-the-clock monitoring | Every hour of every day, in shifts. | Investigation and escalation at any hour; action waits for you. | The night, weekend and holiday shifts — staffing is the bill. | The decision and the act of containment, whenever it is needed. | Organisations that must know at 3am but keep the authority to act in their own hands. |
| 24×7 with containment authority | Every hour, with agreed authority to act. | Isolation, account disabling or blocking within pre-agreed limits. | Playbooks, rehearsal and the accountability of acting on your systems. | Setting the limits of that authority, and the exceptions to it. | Organisations where the cost of an hour's spread outweighs the discomfort of delegated action. |
Our role
What we put in writing before pricing security monitoring
- 01
The sources that matter
We scope which systems genuinely feed detection before anything is metered, so you pay to watch what an attacker would touch rather than to store everything that produces a log.
- 02
Authority, agreed in advance
The actions we may take on your systems during an incident — and the ones that always wait for you — are written into the service before it starts, because 3am is the wrong time to negotiate them.
- 03
An exit you are not punished for
Ownership of detections, playbooks and log history is settled at signature, so changing provider one day is a migration you planned rather than a hostage negotiation.
How much risk to carry unwatched, and how much authority to delegate, are decisions only you can make; we put the commitments in writing so the figure you compare is the service you will actually receive.
Common questions
What buyers ask
Can you give a rough monthly figure for a managed SOC before scoping?+
No, and the refusal is the useful part of the answer. A figure quoted before your log sources, coverage window, response authority and residency requirements are known would be a guess about a different organisation, and it would anchor your budget to whichever assumption we happened to make. The scoping that replaces the guess is short — an inventory of sources, a coverage decision, an authority decision — and at the end of it the figure is real. Any supplier who quotes before asking those questions has answered them for you without saying so.
Is 24×7 SOC coverage worth what it costs over business-hours monitoring?+
The honest comparison is not between the two figures but between the larger figure and the cost of an incident that runs unattended overnight or across a weekend. Attackers favour exactly those windows, and the expensive part of many incidents is not the breach but the hours it spread before anyone looked. If your team already carries a genuine on-call rota, business-hours monitoring can be a rational choice; if the night shift is nobody, the cheaper contract has quietly decided that overnight incidents wait until morning. Price that decision, not the line item.
Will using our own SIEM make a managed SOC cheaper?+
It changes where the money goes more than how much goes. On your own SIEM you carry the licences and the platform work, and the provider charges for analysis and response on top; on theirs, the platform is inside the figure but the detections, tuning and history accumulate in a system you do not own. The real difference appears at exit: leaving a provider-owned stack means rebuilding content elsewhere, while leaving with your own SIEM is closer to changing analysts. Decide based on how much you value that freedom, not on which quote is lower this year.
In this cluster
A scoping session that writes down your log sources, coverage window and response authority, so every SOC offer you receive can be priced against the same commitments.
Scope your monitoring with us
