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

Free RFP template | Detection and Response

SIEM and XDR RFP

An RFP template for a security monitoring platform or managed detection service. Covers sources and volume, response authority, staffing, retention, data location and a licensing model you can forecast.
Threat intelligence
Pages
9
Sections
11
Fill-in fields
25
Scored criteria
6

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 and Project Background

    State the outcome you want, not only the product category.

  2. 02

    Scope of Work

    Volume and sources drive price. Give vendors real numbers.

  3. 03

    Platform and Service Requirements

    Separate what the technology must do from who will operate it.

  4. 04

    Deliverables and Reporting Standards

    Decide what evidence you need to see every month.

  5. 05

    Timeline and Milestones

    Fixed dates for questions, submission, decision and delivery, with bidders asked to confirm capacity against them.

  6. 06

    Vendor Qualifications

    The named people who will do the work, their recent experience with environments like yours, and anything subcontracted.

  7. 07

    Evaluation Criteria and Scoring Matrix

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

  8. 08

    Pricing Structure

    Ask for a model you can forecast, with a rate card for anything outside the stated scope.

  9. 09

    Compliance and Legal Requirements

    Confidentiality, data handling and destruction, insurance, liability and the legal terms to confirm before award.

  10. 10

    Sample Vendor Questions

    Open questions that separate capability from marketing.

  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 SIEM and XDR RFP

Issue this RFP when you need threats detected, investigated and contained and must decide between operating a platform yourself and buying a managed service.

Be clear about the outcome first. Many buyers ask for a product when what they need is someone watching and acting at night. This template lets vendors of either kind respond and makes the difference visible.

What to put in scope

Bidders can only price what you describe. Cover each of these in the scope section of the template.
  • Endpoints, servers and operating systems, with counts
  • Identity provider and number of users
  • Cloud and SaaS sources
  • Network and security devices
  • Daily log volume, if known
  • Monitoring hours required and who may take response actions
  • Retention period and data location

Evaluation criteria

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

Detection and response

Coverage mapped to MITRE ATT&CK, and what actions can be taken without calling you.

Service and staffing

Who investigates overnight, and whether any of it is subcontracted.

Fit

Support for the sources you actually run.

Commercial model

Licensing you can forecast as volume grows.

Weight detection and response capability highest, and ask to see it live. A demonstration from first activity to incident report tells you more than any feature list.

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
%
Service delivery and staffing
%
Fit with our environment and integrations
%
Reporting and evidence
%
Price and licensing model
%
Onboarding plan and timeline
%
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.
  • Which response actions can your analysts take without calling us?
  • Who investigates an alert on our environment at 3 a.m., and where are they?
  • How is licensing calculated, and what happens when log volume grows?
  • How long does onboarding take, and what do you need from us?
  • What happens to our data if we leave?
  • Show us one incident from first signal to closure: what fired, who looked, what was done and how long each step took.
  • Which detections are maintained by your team, how often are they updated, and can we add our own?
  • How do you measure and report false positives, and who tunes them?
  • Where is our data stored and processed, and can that be fixed contractually?
  • What does a typical month of reporting look like, and can we see a redacted example?

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.

Notification only

A service that alerts you and leaves containment to your team.

Volume pricing with no cap

Costs that rise unpredictably with log growth.

No live demonstration

Reluctance to show detection on real activity.

Coverage claims without mapping

Broad promises of full coverage with no ATT&CK mapping or detection list behind them.

Onboarding with no plan

No named onboarding lead, no source-by-source plan and no date for when monitoring actually starts.

How to run this RFP

  1. Agree the outcome

    Write down why you are buying and how you will judge success before drafting.
  2. Complete the template

    Fill in real counts and delete what does not apply.
  3. Issue and answer questions

    Give bidders two to three weeks and publish every answer to all of them.
  4. Score and shortlist

    Score against the published weights, then interview the top two or three.
  5. Check references and award

    Speak to a customer of similar size before you sign.

SIEM and XDR RFP: Frequently Asked Questions

Should we buy a platform or a managed service?

If you cannot staff monitoring around the clock, a managed or co-managed service is usually the realistic choice.

What is the difference between SIEM and XDR?

A SIEM collects and correlates logs from many sources. XDR combines detection and response across endpoint, identity, cloud and network. Many offerings now do both.

How long should logs be retained?

Twelve months is a common baseline. Check what your regulators, contracts and insurer require.

How much log volume will we generate?

It depends on sources and verbosity. Ask bidders to estimate from your counts and to state how pricing changes if the estimate is wrong in either direction.

Can we start small and add sources later?

Yes, and it is often the better path. Start with endpoints, identity and email, prove response works, then add network and cloud sources on a schedule written into the contract.

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.