Third-party risk for SY0-701

Exam objectiveExplain the processes associated with third-party risk assessment and management

The short answer

What objective 5.3 asks you to know

Objective 5.3 covers third-party risk assessment and management across the vendor lifecycle: assess and select a vendor, put the relationship in writing, and keep checking after the contract is signed.

Assessment and selection. Before trusting a vendor with data or systems, gather evidence about how it protects them. Assessment methods include penetration testing, a right-to-audit clause, evidence of internal audits, independent assessments, and supply chain analysis. Internal audit evidence is self-produced, while an independent assessment comes from an impartial third party. Testing a vendor yourself needs its written permission. Vendor selection relies on due diligence before signing and on handling any conflict of interest so the choice is unbiased.

Agreement types. A service-level agreement (SLA) sets measurable service levels and remedies. A master service agreement (MSA) sets general terms that later work orders reference, and a statement of work (SOW) or work order (WO) sets one project's scope, deliverables, schedule, and cost. A memorandum of agreement (MOA) is a formal commitment, while a memorandum of understanding (MOU) states looser intent and is usually not legally binding. A non-disclosure agreement (NDA) covers secrecy, and a business partners agreement (BPA) covers a partnership's structure.

After signing. Vendor monitoring is continuous follow-up. Questionnaires gather comparable, self-reported answers, which important claims should back with evidence such as an independent audit report. Rules of engagement set written limits on any testing, covering targets, methods, timing, and contacts.

Exam questions give a vendor scenario and ask which document or assessment fits, such as SLA versus MSA versus SOW versus NDA, or what evidence shows a vendor is secure.

Written by Knotch · reviewed Nov 15, 2026 · 3 study articles behind this page

Practice the rest

This page is the map. Knotch is where you drill it until it sticks.

  • 3step-by-step lessons with predict-and-reveal and look-alike duels
  • 38exam-style questions with a rationale for every wrong answer
  • 1review queue that brings back what you missed
Start practicing freeFree to start. No card needed.
Tell them apart

Pairs people mix up

  • MSA vs. SOW

    An MSA sets the general terms of the relationship. A SOW sets one project's specifics: scope, deliverables, schedule, and cost.

  • MOA vs. MOU

    An MOA is more formal and spells out each party's specific responsibilities, and it can be binding depending on its terms. An MOU is a looser statement of intent that is usually not legally binding.

  • Questionnaire vs. Audit report

    A questionnaire records what the vendor says about itself. An audit report records findings from an examination of evidence, and may come from the vendor's internal auditors or an outside audit firm.

  • SLA vs. NDA

    An SLA covers performance. An NDA covers secrecy.

The full set of look-alike pairs for this objective is inside Knotch.

Know these cold

Key terms

Right-to-audit clause
A contract term that lets a customer, or an auditor it appoints, inspect a vendor's controls instead of seeing only what the vendor shares.
Service-level agreement (SLA)
An agreement that sets measurable service levels, such as uptime and response times, plus reporting and remedies such as service credits.
Master service agreement (MSA)
An umbrella contract with general terms, such as liability, payment, and security duties, that later work orders reference.
Memorandum of understanding (MOU)
A less formal statement of shared intent and general terms that is usually not legally binding.
Rules of engagement
Written limits for testing a vendor that cover the target list, methods, timing, and contacts.
Due diligence
Gathering evidence about a vendor before signing, as opposed to ongoing monitoring, which continues afterward.
Try one

Sample question

Question 5.3-001 · medium

A vendor returned a security questionnaire in which every answer was yes. The questionnaire contains no attachments.

What is the BEST next step?

  1. A. Accept the answers because the questionnaire was signed by an executive
  2. B. Ask for evidence such as a recent independent audit report
  3. C. Reject the vendor because every answer was positive
  4. D. Send the same questionnaire again and compare the two sets of answers
Show the answer and why
Answer: B, Ask for evidence such as a recent independent audit report

Questionnaires are self-reported, so important claims need supporting evidence.

A standardized questionnaire makes vendors comparable, but its answers are self-reported and can be optimistic. Audit reports and certificates back up important claims.

Why not A: A signature does not verify the answers, which can still be optimistic.

Why not C: Positive answers are not proof of dishonesty, and the better response is to request evidence.

Why not D: Repeating a self-reported questionnaire adds no independent proof.

Quick answers

Common questions on this objective

What is the difference between an SLA and an MSA?

An SLA sets measurable service levels and remedies such as service credits. An MSA is the umbrella contract with general terms that later work orders reference.

Is a vendor security questionnaire enough to prove a vendor is secure?

No. Questionnaire answers are self-reported and can be optimistic, so important claims need supporting evidence such as a recent independent audit report.

Can you penetration test a vendor's systems?

Only with the vendor's written permission and agreed rules of engagement. A vendor's own recent test results are evidence you can review without testing it yourself.

Know it. Now spot it in a scenario.

Start practicing free