Skip to content
Guides

Managed detection and response, an in-house SOC or a co-managed model: which fits a mid-size firm?

Quick answer, Nov 15, 2026As of 15 November 2026, no public standard names one right model. NIST SP 800-61r3 and the UK NCSC both say many firms mix staff and contracted help. Outsource what you use seldom or cannot staff, such as overnight cover. Write business context, log access and the authority to act into the contract.

Three models, and what the guidance calls them

NIST SP 800-61r3 (April 2025), section 2.2 "Incident Response Roles and Responsibilities", says an organization's incident handlers might be "on staff", "on contract (e.g., outsourcing a security operations center [SOC] to a managed security services provider [MSSP]…)" or "available when needed". It adds: "Many organizations may use more than one of these approaches."

Providers sell the contract version as managed detection and response (MDR) or managed security services. In a co-managed model, your staff keep some functions and a provider runs the rest.

The UK National Cyber Security Centre (NCSC) says the same in Designing an Operating Model, part of its Building a Security Operations Centre (SOC) guidance (published 23 May 2022). Under "Locality": "Most SOCs will outsource some of their operations, even if it is just the signatures that your tools will use for detection." The buying question is which functions to keep.

How the three compare

DecisionIn-house SOCMDR or MSSPCo-managedWhere it is written
Business context"Better business context""Potentially lacking business context"Your staff supply it to the providerNCSC, "Locality" table
Hours of cover24/7 needs "significantly more staff than a 9-5 operation with out-of-hours on-call"The provider's hours, as contractedYour team in hours; the provider or an on-call analyst afterNCSC, "Hours of operation"
Authority to actYoursOnly what the contract grantsSplit; write down who actsSP 800-61r3 section 2.2; CSF 2.0 RS.MA-01
LogsYou hold themAsk for "direct access to security logging information"Both read the same storeCISA MSP Insights, "What should an MSP provide…"; CPG 2.U
Provider riskInsider risk stays internalProviders "often have privileged access"SameSP 800-61r3 section 2.2; CSF 2.0 DE.CM-06
ExitNot applicablePlan the handover before signingSameCSF 2.0 GV.SC-10

When each one fits

In-house fits when context matters more than coverage hours. NCSC, "Locality": in-house functions bring "better contextual awareness of the business, which will aid any investigations." Its "Resources" section names the cost: "Finding the right people for the job may be one of the largest constraints."

Outsourced fits a function you rarely use or cannot staff. NCSC, "Locality": "it can also be effective to outsource a function if it is seldom used, or if the SOC simply doesn't have the resources to implement the function internally." SP 800-61r3 section 2.2 gives the provider's advantage: it "may detect malicious activity sooner than individual organizations would because it can correlate events across its customers."

Co-managed fits a firm with IT or security staff in office hours and no night shift. NCSC, "Hours of operation", suggests routing "high priority out-of-hours security alerts" to an existing 24/7 team "for initial triage, before escalating to SOC analysts."

The same section carries a warning for any model: "The effectiveness of a 24/7 SOC would be greatly reduced if other IT functions are only covered 9-5 with no on-call arrangements." Our reading: a provider that watches all night still needs someone on your side who can act on its call.

What to get in writing before you sign

SP 800-61r3 section 2.2 says the provider's responsibilities "should be clearly defined in a contract", including "information flows, coordination, and authority to act on behalf of the organization." That covers limits such as "immediately deactivating certain services to contain an incident."

CISA wrote its Risk Considerations for Managed Service Provider Customers (2 September 2021) for IT service customers. Our reading is that its questions carry over to a provider that watches your logs. Under "What should an MSP provide to an organization in advance of contract award?" it lists:

  • service levels with "a clear delineation of operational IT services and security services";
  • "Detailed guidelines for incident management, including the MSP's incident response responsibilities";
  • "Direct access to security logging information, network intrusion detection, and anomaly analysis data telemetry";
  • notice of "any sub-contracts and independent consultants" that could expose your data.

CSF 2.0 adds three outcomes under Cybersecurity Supply Chain Risk Management. GV.SC-05 puts requirements into "contracts and other types of agreements". GV.SC-08 includes suppliers "in incident planning, response, and recovery activities". GV.SC-10 covers "activities that occur after the conclusion of a partnership or service agreement".

What stays yours in every model

CISA's Overview says outsourcing "does not absolve an organization from risk management responsibilities." Its "Tactical Decision-Making" section adds that "policies and controls on network access, controls, and logs, remain the organization's responsibility" and recommends "maintaining controls and logs separate from the vendor's records."

CISA's Cross-Sector Cybersecurity Performance Goals (v1.0.1, March 2023), goal 2.U "Secure Log Storage", asks that logs "can only be accessed or modified by authorized and authenticated users."

SP 800-61r3 section 2.2 says "the risk of malicious insiders or the service provider being compromised should be considered and addressed". CSF 2.0 DE.CM-06 says to monitor "external service provider activities and services".

Where this sits next to the other pages

A provider whose own tool goes offline is in Your MSP's RMM tool just went dark. The contract side after a provider-led breach is in Third-party risk after a provider-led breach. If an incident is already under way, start with Choosing a cyber crisis response firm.

From an AI assistant, the Distributed Risk MCP server runs search_kev and list_cyber_advisories to check a product against CISA's record. If you want managed security and 24/7 monitoring arranged, brief an advisor and we arrange a partner firm.

Questions

Is a 9-to-5 SOC worth having? NCSC, "Hours of operation": "a 9-5 operation still provides 100% more monitoring than having no SOC at all." It says 24/7 "may be appropriate in high threat scenarios."

Does outsourcing move the risk to the provider? No. CISA says outsourcing "does not absolve an organization from risk management responsibilities," and CSF 2.0 GV.RR-01 keeps leadership "responsible and accountable for cybersecurity risk."

Is this legal advice? No. This page is a procedural checklist drawn from the public record. Counsel decides what your contracts and your regulator require.

Brief an advisor