• SOC 2 Readiness
  • 24/7 incident line
  • 24/7 security operations team

Free RFP template | Managed Security

Managed Security Services RFP

Complete RFP template for evaluating Managed Security Service Providers (MSSPs) and Managed Detection and Response (MDR) vendors. Covers SLA requirements, technology stack, and transition planning.
Soc analysts
Pages
8
Sections
11
Fill-in fields
24
Scored criteria
5

What is inside

11 sections, ready to fill in

Each section opens with a short note on why it matters, followed by the wording and fill-in fields you complete before issuing.

  1. 01

    Executive Summary & Security Objectives

    State the outcome you are buying. "24/7 monitoring" is not an outcome; "mean time to contain under one hour for critical alerts" is.

  2. 02

    Current State Assessment Requirements

    Give bidders the environment facts they need to price accurately.

  3. 03

    Scope of Managed Services

    Be explicit about what the provider does versus what stays with your team.

  4. 04

    Technology Platform Requirements

    Establish who owns the platform and the data. This determines what happens at the end of the contract.

  5. 05

    SLA Definitions & Penalty Structure

    Define the clock precisely, when it starts, when it stops, and what happens when it is missed. An SLA with no remedy is a statement of intent.

  6. 06

    Staffing & Analyst Qualifications

    Establish who is watching, where they sit, and whether you get continuity.

  7. 07

    Reporting & Metrics Dashboard Requirements

    Specify what you need to report upward, so the provider produces it rather than you rebuilding it.

  8. 08

    Onboarding & Transition Plan

    Onboarding is where managed security engagements most often disappoint. Make it contractual.

  9. 09

    Pricing Model

    Require pricing in a directly comparable unit, and make the growth path explicit so year two is not a surprise.

  10. 10

    Vendor Evaluation Scorecard

    Published weightings for every criterion, scored on a 1 to 5 scale, so bidders know exactly how they will be judged.

  11. 11

    Submission Instructions

    How, when and to whom to submit, the response format, and the single point of contact for clarification questions.

When to use the Managed Security Services RFP

This RFP is for organizations that want someone else to watch their environment around the clock: a managed security service provider (MSSP), a managed detection and response (MDR) provider, or a SOC as a service. It suits teams that have security tools generating alerts but not enough people to triage them at night, at weekends or during holidays.

A managed security contract usually runs for years and sits inside your most sensitive systems, so the RFP has to cover more than price per endpoint. It should pin down what is monitored, what the provider will do when something is found, who owns the data and the configuration, and how you leave if the relationship does not work.

What to put in scope

Bidders can only price what you describe. Cover each of these in the scope section of the template.
  • The environment to be monitored: number of endpoints, servers, cloud accounts, identity platforms, email, firewalls and key applications, with expected growth over the contract term
  • Log sources the provider must ingest, and whether you expect them to bring their own platform or operate yours
  • Service tiers: monitoring and alerting only, or detection plus active response such as isolating hosts and disabling accounts
  • Hours of coverage, escalation paths and who on your side receives which alerts
  • Threat hunting, vulnerability management, detection tuning and reporting expectations
  • Compliance needs the service must support, such as log retention periods required by PCI DSS or your own policies
  • Onboarding scope and the exit plan: what data, rules and documentation come back to you at the end

Evaluation criteria

Score every response against the same criteria, agreed before the first proposal arrives.

Detection and response capability

What the provider actually detects, how alerts are investigated, and how far they will go in containing a threat. This is the core of the service and should carry the most weight.

People and process

Analyst coverage across all hours, escalation to senior staff, and whether you get a named contact who knows your environment.

Fit with your environment

Support for your operating systems, cloud platforms, identity provider and existing tools, without forcing a rip and replace you did not plan for.

Transparency and reporting

Whether you can see the alerts, investigations and rule changes, not only a monthly summary.

Contract terms and exit

Data ownership, retention, termination rights, and the cost of leaving, weighed alongside the recurring fee.

A sensible starting split puts detection and response capability and people and process well ahead of the rest, with environment fit and transparency next, and price judged across the whole term rather than year one. Adapt it to your situation and publish the weights with the RFP.

The template's scoring matrix, ready to use

These are the starting weights published in the download. Adjust them, score up to three bidders and compare weighted totals as responses come in.

Scoring matrix

Score each bidder from 1 to 5. Totals are weighted and shown out of 100.

CriterionWeight
Detection and response capability
%
SLA commitments and credibility of remedies
%
Platform, data ownership and portability
%
Team quality and continuity
%
Total three-year cost
%
Weighted total100%
60
60
60

Questions to ask every bidder

Ask the same questions of every vendor and require written answers, so responses can be compared line by line.
  • Walk us through an alert from detection to closure. Who looks at it, how quickly, and what do they tell us?
  • Which response actions will you take on our behalf without asking first, and which need our approval?
  • How do you map your detection coverage, for example against MITRE ATT&CK, and how do you show us gaps?
  • Whose platform holds our data, where is it hosted, and can we keep a copy in our own environment?
  • How do you tune detections to reduce false positives in the first months, and how is that reported?
  • Who will be our named contact, and how do we reach a senior analyst during an active incident?
  • How are your service levels defined, measured and reported, and what happens when they are missed?
  • What does onboarding involve from our side, and how long before monitoring is fully in place?
  • At the end of the contract, what do we get back: logs, detection rules, documentation, asset inventories?

Red flags in a response

Any one of these is worth a follow-up question. Several together usually mean the bidder is not the right fit.

Alerts forwarded, not investigated

If the provider's answer to a detection is an email to you, you are buying an alert relay. Ask what investigation happens before you are contacted.

No clear response authority

Vague answers about who can isolate a host or disable an account at 3 a.m. mean the response part of the service is unclear.

Lock-in by design

Proprietary agents you cannot remove, data you cannot export, or long terms with no exit for poor performance all make a bad fit expensive.

Service levels that measure the wrong thing

A promise to acknowledge an alert quickly says little about how fast it is investigated or contained. Check what each metric actually starts and stops on.

How to run this RFP

  1. Document the current state

    Inventory assets, log sources, existing tools and contracts, and note what currently happens to alerts outside business hours.
  2. Decide the service model

    Choose between monitoring only, MDR with response, or a co-managed model where your team and the provider share the work.
  3. Run scenario-based demos

    Give shortlisted bidders the same realistic scenario, such as a compromised account sending mail, and watch how they investigate it.
  4. Check references in your sector

    Ask for customers of a similar size and environment, and ask them about onboarding and false positive volumes.
  5. Negotiate the exit before you sign

    Agree data return, transition assistance and termination rights while you still have leverage.

Managed Security Services RFP: Frequently Asked Questions

Should we issue one RFP for MSSP and MDR providers?

You can, as long as the scope says which outcomes you need. If you need active response, say so, and score bidders who only monitor and notify accordingly. Our MDR vs MSSP guide explains the difference in more detail.

Can a provider use our existing security tools?

Many can. Ask each bidder which of your current tools they support, what they would replace, and the cost and timing of any change.

How long should the initial contract be?

Longer terms often bring better pricing but more risk. Whatever the length, include performance-based exit rights and a defined transition period.

What should we provide bidders so they can price accurately?

Asset and user counts, log sources, cloud platforms, current tools, compliance requirements and any expected growth. The more precise the numbers, the closer the bids.

How do we compare pricing models?

Normalise every bid to total cost over the full term for the same scope, including onboarding, platform licensing, incident response hours and any data ingestion charges.

Need help with vendor selection?

Our team can help you tighten the scope, review vendor responses against your criteria and prepare questions for shortlist interviews.