Blog

The MSP playbook for managed security services

A guide for MSPs expanding into security

Headshot of Mike DePalma

Mike DePalma

Last update: November 18, 2026•11 min read

Share

Key takeaways

  • Managed security services are defined by who owns each task, not by the tools: monitoring, investigation, response and reporting under a documented scope.
  • A written responsibility matrix across the MSP, the technology provider, the client and the monitoring team stops assumptions from turning into incidents.
  • Pre-authorized actions and severity-based response times decide how fast a threat is contained at 2:00 AM.
  • Taking on detection and response changes your liability: review your contracts, limitation of liability and errors and omissions cover before launch.

MSP leaders often reach a moment where the old boundary line between IT support and active defense simply dissolves. As you expand into managed security services, you take on greater responsibility for protecting clients from threats that can emerge at any hour. You can have every endpoint patched on schedule and every ticket closed within your SLA, yet a single compromised user credential on a Tuesday night can throw your client roster into chaos.

When a client faces an active threat, they don't distinguish between infrastructure maintenance and security oversight. To them, you are simply the team keeping the operational doors open. If systems go dark or data is encrypted, the liability and the panic land directly on your desk.

That shift in client expectations is reshaping the channel and is driving greater MSP expansion into security services. In fact, 95% of MSPs plan to expand their managed service offerings within the next year.1

Adding managed cybersecurity services carries far more weight than introducing another line item to your agreement, though. Once you assume responsibility for threat detection and incident response, your clients will evaluate you on factors like speed, technical savvy, and responsiveness.

The best protection for your team and your margins is to settle, in writing, who owns each task before the first alert fires. This guide shows how, with a responsibility matrix you can copy.

What managed security services are, in short

Managed security services are continuous security functions that an outside provider operates on a client's behalf under a defined scope and service agreement. The client is buying an outcome, not a license: someone monitors the environment, investigates anomalies, contains confirmed threats within agreed limits and reports back.

When you sell an endpoint protection license, the client owns software. When you deliver managed security services, an analyst isolates an infected workstation at 2:00 AM and explains the business impact the next morning.

When does an MSP become an MSSP?

When you accept ongoing, contractual responsibility for detecting, investigating and responding to threats in your clients' environments. We cover that threshold in our MSP vs MSSP post.

Who owns what in a managed security service

Managed security services usually cover endpoint protection and MDR, email security, security awareness training, backup and recovery, vulnerability and patch management, network and DNS protection, and compliance reporting.

Whichever services you launch, the risk is the same: taking a service to market before deciding who owns the work behind it. Without clear boundaries on who owns the workload, things can get messy. Your client assumes you are actively monitoring their environment around the clock, while your engineers assume the software is automatically handling triage. When those assumptions clash and create an incident, it erodes the client trust you worked so hard to build.

A service responsibility matrix is a useful resource to help you keep that from happening. It maps recurring operational tasks to the four parties involved in a managed security service: your MSP, your technology provider, your client, and your security operations team.

The security operations team is a group of analysts who monitor alerts around the clock, investigate suspicious activity, and contain threats. Some MSPs staff this team in-house and others contract it from a managed detection and response (MDR) provider, which can be the same vendor that supplies your security tools. The tasks stay the same whoever fills the role, so the matrix assigns them by function.

Service responsibility matrix

TaskMSPTechnology providerClient24/7 Monitoring team
Deploy and configure security toolsOwns deployment and policy setupSupplies software, updates, and threat intelligenceApproves changes and grants accessAdvises on detection policies
Round-the-clock monitoring and alert triageReceives escalationsMaintains detection enginesKeeps contact list currentOwns monitoring and triage
InvestigationSupplies environment contextSupplies telemetry and research supportAnswers questions about users and business activityLeads the investigation
Containment and responsePerforms approved remediation and restores systemsSupplies response capabilities in the productApproves actions outside the pre-authorized scopeContains threats within pre-authorized actions
Escalation and client communicationOwns the relationship and client notificationsSupports as neededNames decision makers and escalation contactsNotifies the MSP within agreed timelines
Reporting and reviewsDelivers business-level reports and reviewsSupplies reporting data and dashboardsReviews reports and acts on recommendationsSupplies incident summaries
User policy and trainingEnforces technical controlsSupplies training contentOwns acceptable use policies and staff participationFlags risky user behavior

Example: A ransomware alert at 11:40 on a Thursday night

Here’s how the matrix works during a real alert. The scenario below follows a high-severity endpoint detection and response (EDR) alert from the first detection to your client’s monthly report.

TimeStepWho actsWhat happens
11:40 p.m.DetectionTechnology providerThe EDR engine flags a process that has started to encrypt files on the server.
11:44 p.m.TriageSecurity operations teamAn analyst confirms ransomware behavior and raises the incident to critical.
11:50 p.m.InvestigationSecurity operations team and MSPThe analyst traces the process to a phishing attachment, and the MSP identifies the affected users and systems.
11:58 p.m.ContainmentSecurity operations teamThe analyst isolates the server and the employee’s laptop, both pre-authorized actions.
12:15 a.m.EscalationMSP and clientThe MSP calls the client’s emergency contact, and the client approves any restore actions that fall outside the pre-authorized scope.
Before business hoursRecoveryMSPThe MSP restores files from backup, resets credentials, and reimages the laptop.
Next morningCommunicationMSPThe account lead explains the incident’s impact and next steps to the client’s decision maker.
Next reviewReportingMSPThe monthly report includes the incident summary and recommendations.

What changes when an MSP adds security operations

Adding security operations changes your business in ways a standard software SKU never will. When you step into active defense, your operational cadence, your team's stress levels, and your client relationships undergo a fundamental shift.

You need to plan for changes across four core areas:

  • Hours of coverage: Cyber-attacks often occur after business hours and on the weekends. Offering managed security services requires a reliable strategy for alerts that hit at 3:00 AM on a Sunday, whether you choose to run an internal on-call rotation or lean on a partner's 24/7 security operations center (SOC).
  • Speed and urgency: Your traditional help desk operates on resolution windows measured in hours or days. A live ransomware infection spreads across a flat network in minutes. Your service level agreements, escalation paths, and pre-authorized containment steps must reflect that immediate operational pace.
  • Risk and liability: The moment you take on contractual responsibility for detection and containment, a missed alert shifts from an inconvenient ticket to a serious business and legal event. Before taking your service to market, review your client contracts, refine your limitation of liability language, and audit your own errors and omissions policy.
  • Client conversations: Delivering security pushes your quarterly business reviews away from basic health metrics and toward business continuity and risk exposure. Company executives rarely care about raw telemetry; they’ll want you to explain operational risk, emerging threat trends, and strategic investments in plain business terms.

Navigating these shifts comes down to operational readiness. When your team has clear protocols for response times, liability, and after-hours coverage, you can step into security without overloading your service desk or constantly reacting to surprises.

People, process, and technology requirements

Navigating those business shifts requires a solid infrastructure behind your service desk. While the external changes show up in your client conversations and contracts, managing the daily workload comes down to three practical building blocks: the staff making the decisions, the playbooks guiding their actions, and the tools feeding them data.

People

Investigating security events requires a different analytical skillset than troubleshooting desktop applications or configuring network switches. You need technicians who can interpret subtle system logs, recognize common attacker techniques, and stay calm during a live incident.

The primary hurdle for most MSSPs is continuous coverage. Running a round-the-clock internal security operation requires several dedicated analysts to handle shift rotations and time off. To keep overhead manageable, many service leaders assign one internal security owner who manages policy and coordinates directly with a specialized 24/7 delivery partner.

Process

Even experienced technicians will stumble during a crisis if they’re figuring out response steps on the fly. Before taking a security offering to market, write down your procedures for initial alert triage, escalation pathways, client communication, and post-incident reviews. Establish defined severity levels with target response times and spell out pre-authorized containment actions so your team or your partner knows exactly when they can isolate a server without waiting for client approval.

Technology

Your software stack needs to collect relevant telemetry across endpoints, email, and cloud workloads, connect related events, and present analysts with enough context to act quickly. Centralized multi-tenant management, automated onboarding, and direct connections to your PSA and RMM platforms are essential for keeping operational overhead low as you scale.

Platform integration deserves extra weight in your technology vendor evaluation. Working within a unified environment cuts down on the constant screen-switching that slows down investigations and exhausts your technicians. That’s why your peers put so much weight on it: 78% of MSPs view ease of integration as extremely important when picking their technology stack.2

How clients should see service value

When you do your job right in cybersecurity, nothing dramatic happens. That quiet reliability is great for your clients' peace of mind, but it can also create a unique business challenge. If your clients only see a monthly invoice without any visible fires, they can start to question why they’re paying for managed cybersecurity services in the first place.

To overcome that perception gap, you need to make the invisible work visible. Regular reporting bridges that divide by translating silent background service activity into tangible business value.

Structure your monthly and quarterly updates around four operational stories:

  • Activity: Highlight the workload your team handled behind the scenes. Include factors like the volume of threats blocked, alerts investigated, and suspicious events contained, accompanied by brief summaries of any significant incidents.
  • Posture: Track overall environment health trends over time. Show patch compliance rates, backup success percentages, active vulnerability counts, and any unmanaged devices that popped up on the network.
  • Response performance: Demonstrate your operational accountability. Measure how quickly your security desk or delivery partner acknowledged, investigated, and resolved alerts against the response times defined in your contracts.
  • Recommendations: Guide your client’s future strategy with prioritized next steps. Frame these items strictly by business risk, such as enforcing multi-factor authentication across lagging departments or replacing an outdated, unsupported server.

Quarterly business reviews give you a natural setting to walk through these metrics with decision makers. They also create an organic bridge into future service conversations.

Most business owners want simplicity when purchasing security services, and that 71% of small and mid-sized businesses prefer all-in-one prevention, detection, and response bundles.3 When your quarterly report clearly exposes a coverage gap in their email environment or backup strategy, presenting that broader package will feel like a logical next step rather than a cold sales pitch.

As you build these reviews and sales proposals, spell out exactly what your MSSP services cover and how you measure performance. Setting those realistic expectations early protects your client relationships and keeps everyone aligned to what you’re delivering.

How to evaluate a delivery partner or platform

Building a complete security operations stack entirely in-house requires immense capital, specialized talent, and constant oversight. For most growing MSPs, partnering with an established security vendor or co-managed SOC provider is the fastest path to market.

Because that partner directly impacts your margins, your team's daily workload, and your brand reputation, evaluating potential vendors requires looking past high-level sales pitches and also evaluating their platforms and quality of support.

When comparing providers, focus on these practical criteria:

  • Breadth of the portfolio: Look for a partner that covers core security tools like endpoint detection and response, email security, DNS protection, cloud backup, security awareness training, and 24/7 MDR under a single, unified umbrella. Stitching together disparate tools from different vendors leaves you managing separate contracts, renewal cycles, and different support queues. A consolidated ecosystem drastically simplifies administrative overhead and makes it easier to package cohesive managed cybersecurity services.
  • Integration and multi-tenant management: Insist on seeing their central management console in action before signing. You need true multi-tenant visibility so your technicians can manage policies, review alerts, and push updates across all your clients from one screen. Make sure the platform offers native, pre-built integrations with your existing PSA and RMM tools.
  • Packaging and pricing flexibility: A good partner supports how you go-to-market. Look for flexible licensing models that enable you to sell standardized, high-margin bundles while still giving you the freedom to line-item specific products for clients with unique compliance or budget needs. Avoid vendors that force rigid minimum commit thresholds or long-term lock-ins that eat into your margins before you even get your first customer.
  • Security operations depth: If you are leveraging a vendor's SOC or MDR team, make sure you have clear operational boundaries. You need to know their exact analyst tier structure, standard triage response times, and escalation paths. A reliable managed security service provider will clearly outline pre-authorized containment actions, specifying exactly what steps their SOC can execute on a client network at midnight versus what requires your team's explicit sign-off.
  • Partner program support: A vendor should invest in your growth beyond supplying software licenses. Look for partners that offer sales enablement, including co-brandable marketing assets, sales training for your account executives, and access to support engineers. Pay close attention to how their partner program rewards volume, whether through healthy margin protection, MDF allocation, or tiered deal registration.

How OpenText Cybersecurity supports MSSPs

We built the OpenText Secure Cloud platform to meet those operational standards. Secure Cloud brings together a comprehensive portfolio covering endpoint protection, email defense, DNS filtering, backup and recovery, MDR, and more within a single unified platform. Consolidating your stack with one partner means fewer vendor contracts, fewer management consoles to juggle, and far fewer handoffs when your team is resolving an active incident.

You also get the flexibility to sell your way. Prebuilt bundles package common protections so you can quickly launch new services or customize specific product combinations to fit a client's unique compliance requirements and budget. As your practice grows, our dedicated partner program supplies the technical enablement, sales tools, and co-marketing support your team needs to scale predictably.

The economic model supports long-term growth, too. Partners operating within the OpenText Cybersecurity ecosystem generate, on average, up to $6.73 in service revenue for every $1 their clients spend on core OpenText technologies. More than three-quarters of that long-term revenue opportunity develops after the initial deployment through ongoing managed services, monitoring, and strategic oversight.4

If you’re ready to build or expand your security practice:

Explore the MSP of the Future Guide for insights and resources to help you build and scale your security practice.

Share
Headshot of Mike DePalma

Mike DePalma

Mike DePalma is Vice President of Business Development at OpenText Cybersecurity, focused on channel strategy and partner growth. He brings extensive experience from Kaseya and Datto, where he spent over nine years in progressively senior business development and channel roles supporting MSP partners. A recipient of the CRN Channel Chief Award and multiple Global Business Development MVP honors, Mike holds a Bachelor's degree in Political Science from The Johns Hopkins University. He is dedicated to helping partners build scalable, profitable security practices