Managed IT Services19 November 202610 min read

SOC as a Service: Does Your Australian Business Need One?

Pitched SOC as a service or MDR? Learn what a security operations centre does, how the options compare, what drives cost and the questions to ask before you sign.

MVMarcus VanceCSPRO insights
SOC as a Service: Does Your Australian Business Need One?

If you have been pitched SOC as a service or managed detection and response (MDR), here is the short answer. It is worth paying for once your security basics are in place and nobody in your business can act on a serious alert at 2 am. If you are still missing multi-factor authentication (MFA), reliable patching, endpoint detection and response (EDR) or useful logs, fix those first. A security operations centre can only watch what you give it, and it can only act if the contract lets it.

The rest of this guide walks through what a SOC does, how SOC-as-a-service compares with the alternatives, what drives cost, and the questions to ask before you sign. For the wider choice between outsourcing security and hiring for it, see the Computer Support Professionals (CSPRO) guide to managed vs in-house security.

SOC as a service is a subscription in which an outside team watches your security data, usually around the clock. Its analysts sort real threats from noise, investigate what happened and then either contain the threat or tell you what to do. You get the people and processes of a security operations centre without having to build and staff one.

What a security operations centre actually does

A security operations centre (SOC) is a team, its processes and its tools. Whether it sits in your building or a provider's, the work falls into four jobs.

  1. Monitoring: collecting activity records (logs) from laptops, Microsoft 365 sign-ins, firewalls, servers and cloud apps, and watching for anything suspicious.
  2. Triage: deciding which alerts matter. Many alerts turn out to be harmless, so this step decides whether real threats get attention in time.
  3. Investigation: working out what happened, which accounts and devices are involved, and whether the activity is still going on.
  4. Response: containing the threat, for example by isolating a laptop or disabling an account, then handing over for clean-up and recovery.

Where a SIEM fits

The Australian Signals Directorate (ASD) describes a security information and event management (SIEM) platform as software that collects, centralises and analyses log data, then raises alerts for a security team to investigate. A related tool, security orchestration, automation and response (SOAR), automates some responses using predefined playbooks.

The SIEM is a tool; the SOC is the people using it. ASD's executive guidance on SIEM and SOAR platforms, published on 27 May 2025, says neither is "set and forget". Without skilled people choosing the right logs and tuning the rules, teams either drown in false alerts or miss real ones. That ongoing tuning is a large part of what you pay a SOC provider for.

SOC as a service vs MDR vs your IT provider vs in-house

These labels are not standardised, and providers use them differently. Treat the comparison below as a guide to what to ask, not a fixed definition. In short, SOC as a service watches logs from many systems, while MDR adds analysts to a specific security platform such as EDR.

Option

What you mainly get

Who acts on a confirmed threat

Usually suits

Watch for

SOC as a service

Analysts watching logs from many systems, often through a SIEM

Varies: some contain threats, many alert and advise

Businesses with many systems, or clients asking for evidence of monitoring

Log-volume costs and alert-only contracts

MDR

Detection and response built on a specific platform such as EDR

Often the provider, if you grant the access

Businesses with no one to act on alerts after hours

Blind spots outside the vendor's tools

IT provider (MSP) monitoring

Alerts from managed firewalls, endpoints and backups, fixed by the team that runs them

Your IT provider, within agreed hours

Most small businesses, as the foundation

Whether "24/7" means people or automated alerts

In-house SOC

Your own analysts and tools, with full business context

Your own team

Large organisations, or those running critical services

Cost, hiring and round-the-clock rostering

ASD's guidance is candid about building in-house: expect several people working on a SIEM full time, in skills that are in high demand. It also warns that outsourcing can create visibility gaps, duplicated work and communication problems. For most small and medium businesses, that points to buying the capability and managing the relationship carefully.

What SOC as a service includes and often leaves out

Two quotes with the same headline can cover very different things. Check these areas closely.

  • Alert-only or hands-on response: some services contain threats themselves, while others send you a ticket and a recommendation. The difference often comes down to the access you grant. Microsoft's documentation for its own MDR service shows this clearly: with a higher permission level its analysts act on your behalf, while with read-only access the actions wait for your team.
  • Hours: ask whether analysts work overnight and on weekends, or whether after-hours coverage is automated alerting that someone reviews the next morning.
  • Data sources: a SOC only sees the systems connected to it. Confirm whether Microsoft 365, sign-in logs, laptops, servers, firewalls and key cloud apps are all in scope.
  • Incident response and recovery: containment is not the same as a full investigation and rebuild. Microsoft states that its MDR service is not an incident response engagement for an active compromise. Assume a similar boundary applies elsewhere until a contract says otherwise.
  • Log retention: ASD's event logging best practices warn that default retention periods are often insufficient, noting that in some cases an incident can take up to 18 months to discover. As at November 2026, Microsoft's documentation says Microsoft 365 standard audit logs are kept for 180 days by default.
  • Where your data goes: ASD recommends checking whether a provider is bound by foreign data storage requirements or operates from overseas. Security logs often hold names, email addresses and sign-in locations. If your business is covered by the Privacy Act 1988, giving personal information to an overseas contractor is usually a disclosure under Australian Privacy Principle 8, and you remain accountable for how it is handled.

This is general information, not legal advice. Check your privacy and contractual obligations with a qualified adviser or the Office of the Australian Information Commissioner (OAIC).

What drives the cost of SOC as a service

Pricing models vary, so compare quotes on scope rather than the monthly figure alone. The main cost drivers are:

  • Size: the number of users, devices and servers covered.
  • Log volume: ASD notes that most SIEM pricing is based on how much data is ingested. Without a cap, costs can climb sharply as more logs are added.
  • Data sources: each extra system connected adds set-up and tuning work.
  • Hours and response depth: round-the-clock analysts with authority to contain threats cost more than business-hours alerting.
  • Retention: keeping logs searchable for longer adds storage cost.
  • Add-ons: threat hunting, incident response retainers and compliance reporting are often priced separately.
  • Prerequisite licences: some services only work with particular security products or licence tiers, which may sit outside the quote.

ASD also notes that a SIEM is not the only way to centralise logs, and mentions lower-cost options for smaller organisations without a SOC. Ask whether a simpler setup would match your risk.

Fix the basics before you buy a managed SOC

SOC as a service detects and responds. It does not patch your systems, switch on MFA or test your backups. If those gaps remain, the SOC will spend its time reporting the same problems back to you.

Basics to have in place first

  • MFA on email, remote access and every admin account.
  • Prompt patching of internet-facing systems, operating systems and applications.
  • EDR on every laptop, desktop and server, not just antivirus. CSPRO's guide to antivirus versus EDR explains the difference.
  • Admin privileges limited to the people and tasks that need them.
  • Tested backups, as part of a ransomware protection plan.
  • Logging switched on and kept long enough to investigate, including Microsoft 365 audit logs and firewall logs.

Most of these map to the Essential Eight controls. As at November 2026, ASD is moving from the Essential Eight to its new ASD Essentials series, published on 15 October 2026. ASD's transition guidance brings logging, detection and incident response together in a "Visibility and response" domain. That domain sits in the first priority phase, alongside governance and culture, boundary services and identity services. ASD says the series is written mainly for government, critical infrastructure and large organisations, but smaller businesses can use it where relevant. It also advises continuing current uplift programs.

Signs you are ready

  • The basics above are in place and someone maintains them.
  • Nobody can act on a serious alert overnight, on weekends or during holidays.
  • An outage or data exposure would seriously hurt clients, revenue or reputation.
  • You hold sensitive records, such as health, financial or legal information.
  • Clients, contracts or your cyber insurer ask how you detect and respond to incidents.
  • Your security tools already produce alerts that nobody reviews promptly.

If several of these apply, SOC as a service or MDR is worth pricing. If only the last one applies, start by asking your IT provider who should be reviewing those alerts.

Questions to ask a SOC as a service provider before you sign

Ask for answers in writing, and make sure they appear in the contract or service schedule.

  1. When you confirm a real threat at 2 am, what will you do yourselves, and what will you hand back to us?
  2. Which actions are pre-approved, such as isolating a laptop or disabling an account, and who approves anything else?
  3. Who watches overnight and on weekends: analysts, or automated alerts?
  4. Which of our systems are in scope, and what is excluded?
  5. How long are our logs kept and searchable, and can we export them if we leave?
  6. Where are logs stored and analysed, and do any staff or subcontractors access them from overseas?
  7. What are your notification and response targets, and how do you report against them?
  8. Is incident response after containment included, or charged separately?
  9. How do you secure your own access to our systems?
  10. How do you test that detections work and reduce false alarms over time?

The US National Institute of Standards and Technology (NIST) backs this level of detail. Its incident response guidance, SP 800-61 Revision 3, published in April 2025, says responsibilities shared with a provider should be clearly defined in the contract. That includes information flows, coordination and the provider's authority to act on your behalf. NIST also notes that providers often hold privileged access to your systems, so their own security becomes part of your risk.

How a managed SOC fits alongside your IT provider

Buying SOC as a service does not replace your IT provider. The SOC watches and contains; someone still has to maintain, repair and restore your systems.

NIST notes that a provider watching many customers may spot malicious activity sooner because it can correlate events across them. The weak point is the hand-off. The SOC sees the alert, but your IT provider usually knows the systems and does the fix.

Agree a simple split like the one below, and write it into your incident response plan.

Task

SOC or MDR provider

IT provider

Your business

Watch and triage alerts

Leads

Told about confirmed incidents

Receives summaries

Contain a confirmed threat

Acts within pre-approved limits

Supports and checks impact

Approves anything outside those limits

Fix and restore systems

Advises

Leads

Sets business priorities

Insurer, legal and privacy notifications

Provides evidence

Provides technical detail

Decides and notifies

Planned changes and maintenance

Told in advance

Tells the SOC

Approves

Flagging planned work matters more than it looks: without notice, a routine server update can resemble an attack. Finally, check that both providers hold your current after-hours contacts.

How CSPRO Can Help

Before you compare SOC as a service quotes, it helps to know where your foundations stand. CSPRO provides cybersecurity services that cover that groundwork: managed endpoint protection, managed firewall configuration and monitoring, email filtering and phishing protection, MFA and identity access controls, patching, 24/7 threat monitoring and ongoing alignment with the ACSC Essential Eight.

A good first step is the free initial cybersecurity risk assessment offered with CSPRO's cybersecurity services. It reviews your current systems and controls and highlights the gaps worth prioritising, so you can judge any SOC or MDR proposal against your real risk. Call 1300 660 368 to arrange it.

TaggedCybersecurity ServicesManaged Security Services

SOC as a Service: FAQs

Not exactly, although the two overlap. SOC as a service usually means an outside team watching logs from many systems, often through a SIEM. MDR usually builds on a specific security platform, such as an endpoint detection and response tool, and adds analysts who investigate and respond. Because providers use both labels loosely, compare the written scope, hours and response authority rather than the name.

Not always. A small business with solid basics, a responsive IT provider and limited sensitive data may be well served by managed security monitoring. Round-the-clock analyst coverage becomes more valuable when nobody can act on alerts after hours, when downtime would be costly, or when clients and insurers ask how incidents are detected and handled.

A SIEM collects, centralises and analyses log data from across your systems, then raises alerts when activity looks suspicious. It is a tool, not a team. The Australian Signals Directorate stresses that a SIEM is not set and forget: skilled people need to choose the right logs, tune the detection rules and keep testing them as systems and threats change.

Yes, and in most cases it should. The SOC watches for threats and contains them within agreed limits, while your IT provider maintains and repairs your systems. Problems arise when roles are unclear, so agree in writing who receives alerts, who can isolate devices or disable accounts, who restores systems and who contacts insurers or regulators.

Long enough to investigate an incident that is discovered late. The Australian Signals Directorate notes that default retention periods are often insufficient and that some incidents take up to 18 months to discover. Set retention based on your risks and any regulatory or contractual requirements, and check how long logs stay searchable, not just stored.

Keep reading

More practical guidance

All articles