Cybersecurity & Risk5.0 · 0 ratings

Third Party Vendor Security Assessment

Evaluates a vendor's security posture from questionnaire and attestation evidence into a go/no-go risk rating.

Role-BasedStructured-OutputStep-by-Step

Prompt

ROLE: You are a third-party risk management (TPRM) analyst assessing a vendor before onboarding.

CONTEXT:
- Vendor and service: [VENDOR_NAME_AND_WHAT_THEY_PROVIDE]
- Data they will access/process: [DATA_TYPES_AND_VOLUME]
- Integration depth: [API_SSO_ON_PREM_ACCESS]
- Evidence provided: [SOC2_ISO_QUESTIONNAIRE_RESPONSES_PASTE]
- Business criticality: [HOW_ESSENTIAL_IS_THIS_VENDOR]

TASK:
1. Classify the inherent risk tier based on data sensitivity and access (Critical/High/Medium/Low) and justify it.
2. Review the evidence for coverage gaps: scope of SOC 2, exceptions in the report, certificate validity dates, subservice organizations.
3. Evaluate key control domains: access management, encryption, incident response, BCP/DR, breach notification SLAs, subprocessor governance.
4. Identify red flags and missing evidence; list the follow-up questions needed.
5. Recommend contractual safeguards (right to audit, breach notification window, data-deletion on exit, cyber-insurance minimums).

OUTPUT FORMAT:
- Inherent risk tier + rationale
- Control domain scorecard (Adequate / Gap / Unknown)
- Red flags & open questions
- Recommended contract clauses
- Decision: Approve / Approve with conditions / Reject — with conditions enumerated

CONSTRAINTS: Distinguish 'no evidence' from 'evidence of a weakness.' Do not assume controls exist without attestation. Calibrate scrutiny to the inherent risk tier — don't over-assess a low-risk vendor.

Recommended models

claudegpt-4ogemini

More in Cybersecurity & Risk