Build

A TPRM platform RFP checklist: what to ask, and what to demand evidence for

A comparison framework tells you what to care about. An RFP is the document that makes a bidder prove it, with an artifact you can score, and that treats the company selling the platform as a supplier you still have to assess. Here is how to write and score one.

By Guy Halfon,

The criteria for choosing a third-party risk platform, and a fair map of who sells what, already live in how to compare TPRM platforms and the market overview. This page does not repeat them. An RFP is a procurement document. Its job is to turn those criteria into questions a bidder cannot answer with a brochure, to say in advance how the answers will be scored, and to treat the winning company as a supplier whose own security, subcontractors, and exit terms you are about to accept.

NIST SP 800-161 Revision 1 describes that job in section 3.1.2, on the role of cyber supply chain risk management in acquisition. The enterprise defines requirements first, may use a request for information to screen the market, and then releases a request for proposal. Bidders are evaluated against critical supply-chain criteria. The review includes procurement, the business-process owner, the relevant system owners, and technical experts. The same section says applicable security requirements should be a qualifying condition for award, and it tells enterprises to avoid a "lowest price, technically acceptable" source selection when buying ICT or OT products and services. SP 800-161 is guidance, not a statute. It is still the clearest public description of how an RFP should carry supply-chain requirements. NIST SP 800-53 control SA-4 is the contract-side version of the same idea: the acquisition agreement should state the security and privacy functional requirements, the assurance requirements, and the acceptance criteria, explicitly or by reference. See NIST SP 800-161 for C-SCRM.

Decide criticality, gates, and weights before anyone writes back

NIST CSF 2.0 splits this into two supply-chain outcomes. GV.SC-06 is planning and due diligence before you enter a supplier relationship. GV.SC-05 is the follow-through: cybersecurity supply-chain requirements are prioritized and written into contracts and other agreements. NIST's CSF 1.1 to 2.0 core transition spreadsheet records the implementation examples for GV.SC-06: due diligence consistent with procurement planning and commensurate with the risk, criticality, and complexity of the relationship, and an assessment of the prospective supplier's technology and risk-management practices. See CSF 2.0 and third parties for the full category. Take the weights from the evaluation framework and freeze them before the first response arrives. A bidder's demo is a poor moment to discover what you care about.

If you are a banking organization, the 2023 interagency guidance, issued by the OCC as Bulletin 2023-17 jointly with the Federal Reserve and the FDIC, says due diligence comes before you select and enter the relationship, and that its degree should be commensurate with the level of risk and complexity of that relationship. Relying solely on familiarity with a company is not a substitute for that diligence. It is supervisory guidance rather than a regulation, and examiners apply it to the banking organizations those agencies supervise. The sequence is a sound one for any buyer: plan, select on evidence, contract, then monitor.

What the RFP itself contains

Keep the document short enough that a serious bidder answers it carefully. Five parts are enough.

  1. Scope. What decision this RFP supports, which regimes your program actually has to evidence, the systems the platform must talk to, and the vendor tiers you will put through it. Point bidders at your tiering rule rather than pasting it. See how to build the program if that rule is not written down yet. A platform cannot repair a missing inventory policy.
  2. Gates, written as pass or fail, with the artifact that proves a pass.
  3. Scored questions, each mapped to a frozen weight, and each asking for an artifact rather than an adjective.
  4. A pilot script. The scenarios, the data you will allow, the clock, and what a finished pilot has to show. Put it in the RFP so every bidder runs the same test.
  5. Contract terms you will not trade away, attached as a schedule, rather than discovered in legal review after you have a preferred bidder.

Ask for an artifact, not a claim

A question that can be answered with "yes" will be. The useful form is: do this, and show the record. Drop a row that does not match a criterion you actually weighted. Do not add a row because it appeared on one vendor's datasheet.

What you need to knowWhat counts as an answer
Can it see vendors you did not type in?A list produced from your tenant, or from a synthetic tenant you control, with the source of each record (spend, single sign-on, a contract repository) written beside it. A slide that says "discovery" is not that list.
Can it tell a verified control from a claimed one?One SOC 2 report or ISO/IEC 27001 certificate run through the product, showing what was marked verified, what was left as the vendor's own statement, and where the report's scope did not cover the service you would buy. See evidence-based scoring and SOC 2 in vendor assessment.
What would it have raised between reviews?A 90-day history for one named vendor: which signals would have been shown to a person, which were suppressed, and why. See continuous vendor monitoring.
Does a finding become tracked work?One finding opened, assigned to a named role, visible to the vendor, and closed with a timestamp and the evidence that closed it. A dashboard count is not that record.
Where does a person approve an action?A scripted vendor-breach walkthrough that marks each step a human must approve under your rules. See the vendor breach playbook. Treat a platform that cannot show that boundary as a failed gate.
Can you leave?An export of the assessment record in a documented format, plus a written list of what that export leaves out. Run the export during the pilot, from your data, rather than from a sample file the bidder prepared.

NIST SP 800-161 is explicit that the RFP review covers the supplier, not only the product. The criteria include the bidder's security processes and its security track record. A polished feature response with no account of how the company handles its own incidents is an incomplete bid.

Who scores, and in what order

Score gates before points. One reviewer reads every bid against the gates and records pass or fail, with the artifact or its absence, before anyone discusses a favorite. Then the panel scores. NIST SP 800-161 names who should be in that room: procurement, the business-process owner, the relevant system owners, and technical experts. For this purchase that is usually procurement or vendor management, the person who will run the program, a security engineer who will live in the product, and counsel for the contract schedule. The interagency guidance treats documentation of the third-party risk process, and of the specific relationship, as part of risk management across the life cycle. Write down the scores, the dissent, and any gate you waived. A waiver with no name on it is how a failed gate gets averaged back in.

Do not let a live demo reset a weight. If a bidder shows something you wish you had asked for, note it for the next RFP. Changing the rubric after you have seen the answers is how the evaluation stops being one you can defend.

The pilot is a section of the RFP

NIST SP 800-161 says the early due diligence, including a request for information, should not be treated as the whole assessment. The pilot is where the critical criteria get tested, and it belongs in the RFP so the conditions are identical for every bidder. Use a slice of your own inventory that includes one vendor you already treat as critical, or a synthetic set built to resemble that slice if counsel will not allow production data. Time-box it. Publish the success criteria in the script: the export completed, a scope mismatch on the audit report was flagged, a human approval was required before a vendor was notified, and the history for the named vendor was produced without an engineer from the bidder driving the screen for the whole session.

A bidder who can only demonstrate on a portfolio they prepared has answered a different question. Score that scenario as failed.

The platform vendor is a third party

The company that will hold your vendor inventory, your assessment notes, and the contact details of the people and vendors in that record is a supplier. The interagency guidance's due diligence factors apply to that company in proportion to how much you will depend on it. On information security, the guidance points reviewers at the third party's own program, at gaps that would put your data at risk, at how access to your data is limited, at whether the third party keeps up with known and emerging threats, and at vulnerability and penetration-test results together with the corrective actions that followed. For a SOC report, the guidance's test is whether the scope and the results are relevant to the activity you are buying.

On subcontractors, the guidance says to look at the volume and type of subcontracted work and at how the third party selects and oversees those subcontractors, including whether they implement effective controls. Ask for the subprocessors that would touch your tenant, and for the flow-down that binds them. NIST SP 800-161 treats flow-down of applicable requirements to subcontractors, where it applies, as part of keeping supply-chain risk managed after signature. See fourth-party risk.

On the contract, NIST SP 800-161 says the agreement should provide for periodic revalidation of the supplier's adherence, a protocol for reporting vulnerabilities, incidents, and other disruptions, each party's role when a supply-chain risk is identified, and grounds for termination when that risk cannot be brought within the level you will accept. The publication writes those roles in federal terms (government, supplier, and other third parties). A commercial RFP uses the same structure: your organization, the supplier, and anyone else who has to act. The interagency guidance's incident-reporting factor is separate and practical: whether the third party has documented processes, timelines, and accountability for identifying, reporting, investigating, and escalating incidents, and whether those match your expectations. Put the notice window and the cooperation duty in the schedule attached to the RFP.

If the platform will process personal data, the contract question is the one in GDPR and third-party risk, including whether a processor may add a sub-processor. If you are in scope for DORA, this platform is an ICT third-party service: the Article 30(2) contract terms apply whatever its criticality, the arrangement goes on your Register of Information, and Article 30(3) adds further terms if it supports a critical or important function. See DORA third-party risk. A product demo satisfies neither.

Lines that do not belong in the RFP

Where the bidders usually sit

Outside-in rating providers such as BitSight, SecurityScorecard, and UpGuard, workflow and GRC platforms such as OneTrust and ProcessUnity, and assessment platforms such as Panorays will each answer this RFP in the shape of their product. Rescana is one more option in that set, and it should have to produce the same artifacts as the others. Your approvals. Our agents. What gets acted on stays under your rules, with human control. If another bidder's pilot matches your frozen weights more closely, that is the result the RFP was for.

Talk to an expert about running this checklist on a live evaluation.

Frequently asked questions

What should a third-party risk management RFP include?

Five parts: the scope of the decision and the systems and vendor tiers the platform must cover; pass-or-fail gates with the artifact that proves each one; scored questions mapped to weights you froze in advance; a pilot script with scenarios, data rules, a clock, and success criteria; and a contract schedule of terms you will not trade away. NIST SP 800-161 describes this sequence as defining supply-chain requirements before the request for proposal, then evaluating bidders against those critical criteria. The product criteria themselves belong in your evaluation framework. The RFP is how you force proof.

How do you evaluate responses to a TPRM platform RFP?

Score gates before points. One reviewer records pass or fail against each gate, with the artifact or its absence, before a panel scores the weighted items. NIST SP 800-161 puts procurement, the business-process owner, system owners, and technical experts in that review. Do not change a weight after a demo. A failed gate is not averaged away by a high score elsewhere, and a waived gate needs a named person and a reason. The 2023 interagency guidance, for banking organizations, expects the selection and the relationship to be documented, not just decided.

What evidence should you ask a TPRM vendor for during procurement?

Ask for records, not adjectives. Useful ones are a vendor list the product produced from your tenant or a synthetic tenant, with the source of each record; one SOC 2 or ISO/IEC 27001 report run through the product showing what was verified, what was only attested, and where the scope did not match; a 90-day history for a named vendor showing what would have been raised to a person; one finding opened, assigned, and closed with the evidence that closed it; a breach walkthrough marking each step a human must approve; and an export of the assessment record from your own data, plus a list of what the export leaves out.

Who should score a third-party risk management RFP?

A mixed panel, not the sponsor alone. NIST SP 800-161 names procurement, the business-process owner, the relevant system owners, and technical experts. On a TPRM platform purchase that is typically procurement or vendor management, the person who will run the program, a security engineer who will use the product, and counsel for the contract schedule. One of them should score the gates before the group discusses favorites, so a good demo cannot talk a failed security requirement back into the average.

What contract terms should you require when buying a TPRM platform?

Treat the platform vendor as a supplier. NIST SP 800-161 calls for periodic revalidation of the supplier's adherence, a protocol for reporting vulnerabilities and incidents, a statement of each party's role when a supply-chain risk appears, flow-down of applicable requirements to subcontractors, and grounds for termination when the risk cannot be brought within what you will accept. The 2023 interagency guidance adds a practical test of incident reporting: documented processes, timelines, and accountability. Attach those terms to the RFP. If the platform will process personal data, the contract has to carry the GDPR Article 28(3) processor terms. If you are in scope for DORA, every ICT services contract needs the Article 30(2) terms, and a critical or important function adds Article 30(3).