Vendor / Third-Party Risk Management Assessment
Assess the vendor and third-party risk management (TPRM) program for "$ARGUMENTS". Evaluate vendor lifecycle management from identification through offboarding, including due diligence, contractual requirements, ongoing monitoring, and subprocessor management.
Arguments. $ARGUMENTS may contain the project name and optional flags. Take the first token as <project> and treat --skip-checks as a flag; never include flags in file paths. All paths below use <project>. If --skip-checks is present, skip the prerequisite check and, before writing any artifact, append one line to .singularskills/log.jsonl: {"ts":"<ISO timestamp>","skill":"compliance-vendor-tprm","workflow":"compliance","phase":1,"project":"<project>","event":"skipped","artifact":"01-assess/","note":"<reason or \"none given\">"}.
Prerequisites
Part of a workflow. This skill is phase 1 (Assess) of the GRC Lifecycle workflow (compliance); cross-domain workflows run it too. First check .singularskills/log.jsonl for an open run for this project: a run-started line with "project":"<project>" and no later run-finished line for the same workflow and project. If one exists, the conductor is running you: continue here. Otherwise, if the user asked to start, run, continue or resume a process or workflow rather than this one step, do not continue here: invoke the workflow skill with the workflow the user asked for, or compliance when they named none, followed by <project>; it runs this phase in order, asks before it writes and records the run. Otherwise continue here: a later phase runs on its own, behind its gate.
Run this skill's gate before writing: sh <this skill's folder>/scripts/gate.sh <project> <project root>, where <project root> is the folder that contains .singularskills/ (use . when you are already there). If it exits non-zero, stop and tell the user what it printed, unless --skip-checks was given (see Arguments). On a refusal, before you stop, append this line to .singularskills/log.jsonl (create the folder and file if missing): {"ts":"<ISO timestamp>","skill":"compliance-vendor-tprm","workflow":"compliance","phase":1,"project":"<project>","event":"refused","artifact":"01-assess/","note":"<what the gate printed>"}. Once the gate has passed, or under --skip-checks once you have appended the skipped line, append this line before you start work: {"ts":"<ISO timestamp>","skill":"compliance-vendor-tprm","workflow":"compliance","phase":1,"project":"<project>","event":"started","artifact":"01-assess/","note":""}.
Read .singularskills/compliance/<project>/00-scope.md. If this file does not exist, tell the user:
Phase 0 (Scope) has not been completed for "". Run /compliance-regulatory-landscape <project> first, or use --skip-checks to bypass.
Process
Read context files:
- Read
references/grc-lifecycle-guide.md for GRC methodology reference
- Read
references/assessment-template.md for output structure
- Read
.singularskills/compliance/<project>/00-scope.md for scope and control framework context
Vendor identification and classification:
- Assess vendor inventory completeness (all third parties identified and cataloged)
- Evaluate risk-based classification methodology (critical, high, medium, low risk)
- Review classification criteria: data access, system connectivity, business impact, regulatory scope, replaceability
- Assess vendor categorization by type (cloud services, SaaS, professional services, outsourced operations, subcontractors)
- Evaluate concentration risk assessment (dependency on single vendors, geographic concentration)
Due diligence process:
- Assess pre-engagement due diligence procedures per risk tier
- Evaluate security questionnaire process (SIG, CAIQ, custom questionnaires)
- Review SOC report analysis (SOC 2 Type II, SOC 1, bridging letters, complementary user entity controls)
- Assess penetration testing and vulnerability assessment requirements for vendors
- Evaluate financial stability assessment (credit reports, financial statements, insurance coverage)
- Review legal and regulatory compliance verification (certifications, licenses, regulatory actions)
- Assess business continuity and disaster recovery capability evaluation
- Evaluate privacy impact assessment for vendors processing personal data
Contractual requirements:
- Assess Data Processing Agreement (DPA) coverage and adequacy
- Evaluate Service Level Agreements (SLAs) with measurable metrics and remedies
- Review security addenda and minimum security requirements
- Assess right-to-audit clauses and audit facilitation provisions
- Evaluate breach notification requirements (timelines, content, cooperation)
- Review data return/destruction clauses upon termination
- Assess liability, indemnification, and insurance requirements
- Evaluate subprocessor approval and notification rights
Ongoing monitoring:
- Assess periodic reassessment cadence per risk tier (annual for critical, biennial for high, etc.)
- Evaluate continuous monitoring signals (security ratings, breach notifications, news monitoring)
- Review performance monitoring against SLAs and KPIs
- Assess incident and near-miss tracking for vendor-related events
- Evaluate vendor relationship governance (steering committees, business reviews)
- Review compliance certificate and certification renewal tracking
- Assess trigger-based reassessment procedures (material changes, incidents, M&A)
Offboarding procedures:
- Assess data return and destruction procedures (certificates of destruction, verification)
- Evaluate access revocation process (system access, physical access, credentials)
- Review knowledge transfer requirements for critical vendors
- Assess transition planning and migration support obligations
- Evaluate post-termination confidentiality and data handling obligations
Subprocessor management:
- Assess subprocessor identification and approval workflow
- Evaluate notification obligations for subprocessor changes (advance notice period)
- Review flow-down requirements (security, privacy, compliance obligations)
- Assess objection rights and procedures for subprocessor changes
- Evaluate fourth-party risk visibility and oversight
Program governance:
- Assess TPRM policy and procedures documentation
- Evaluate roles and responsibilities (TPRM team, business owners, legal, security, privacy)
- Review TPRM tooling and automation (GRC platform, vendor risk management system)
- Assess reporting and metrics (vendor risk dashboards, board reporting)
- Evaluate exception and risk acceptance processes
Write the artifact to .singularskills/compliance/<project>/01-assess/vendor-tprm.md following the assessment template structure with:
- Vendor Inventory — completeness and risk classification coverage
- Due Diligence — process maturity per risk tier and assessment coverage
- Contractual Framework — DPA, SLA, security, and audit clause coverage
- Ongoing Monitoring — reassessment cadence, continuous monitoring, and performance tracking
- Offboarding — data destruction, access revocation, and transition procedures
- Subprocessor Management — identification, approval, and flow-down requirements
- Program Governance — policy, roles, tooling, and reporting
- Evidence Inventory — existing evidence and evidence gaps
- Remediation Priorities — ranked list of gaps to address
Output
The vendor TPRM assessment written to .singularskills/compliance/<project>/01-assess/vendor-tprm.md. Present a summary to the user highlighting:
- Vendor inventory completeness and risk classification coverage
- Due diligence and contractual coverage rates by risk tier
- Ongoing monitoring maturity and reassessment compliance
- Top 3 gaps requiring remediation
Record the run. After you have written the artifact, append this line to .singularskills/log.jsonl (the started line of Prerequisites, with "event":"finished"): {"ts":"<ISO timestamp>","skill":"compliance-vendor-tprm","workflow":"compliance","phase":1,"project":"<project>","event":"finished","artifact":"01-assess/","note":""}.
Open the artifact with this frontmatter (agent is the agent you run in, or unknown; gate is passed when the gate ran clean and skipped under --skip-checks):
---
skill: compliance-vendor-tprm
workflow: compliance
phase: 1
project: <project>
started: <ISO timestamp>
finished: <ISO timestamp>
agent: <the agent you run in, or "unknown">
gate: <passed|skipped>
---
End the artifact with ## Decisions and ## Open questions, in this shape:
## Decisions
- <what was chosen> — <why> — <what was rejected>
## Open questions
- <what the next phase or a reviewer must settle>
End the artifact with this paragraph, verbatim:
Not legal or audit advice. This artifact supports preparation for compliance work; certification, attestation and regulatory conclusions require a qualified auditor or counsel.
1---2name: compliance-vendor-tprm3description: Assess the vendor and third-party risk management program — vendor tiering, due diligence, contract clauses, ongoing monitoring, offboarding and subprocessor management. Use when the user wants to assess their own vendor risk program, needs TPRM for an audit, or a customer asks how they vet their own suppliers. Not for scoring security risks; see /security-risk-assessment.4metadata:5 source: https://skillmd.com/skills/bromso/compliance-vendor-tprm6 argument-hint: "[project] [--skip-checks]"7 workflow: compliance8 phase: 19 artifact: 01-assess/10---1112# Vendor / Third-Party Risk Management Assessment1314Assess the vendor and third-party risk management (TPRM) program for "$ARGUMENTS". Evaluate vendor lifecycle management from identification through offboarding, including due diligence, contractual requirements, ongoing monitoring, and subprocessor management.1516**Arguments.** `$ARGUMENTS` may contain the project name and optional flags. Take the first token as `<project>` and treat `--skip-checks` as a flag; never include flags in file paths. All paths below use `<project>`. If `--skip-checks` is present, skip the prerequisite check and, **before writing any artifact**, append one line to `.singularskills/log.jsonl`: `{"ts":"<ISO timestamp>","skill":"compliance-vendor-tprm","workflow":"compliance","phase":1,"project":"<project>","event":"skipped","artifact":"01-assess/","note":"<reason or \"none given\">"}`.1718## Prerequisites1920**Part of a workflow.** This skill is phase 1 (Assess) of the GRC Lifecycle workflow (`compliance`); cross-domain workflows run it too. First check `.singularskills/log.jsonl` for an open run for this project: a `run-started` line with `"project":"<project>"` and no later `run-finished` line for the same `workflow` and `project`. If one exists, the conductor is running you: continue here. Otherwise, if the user asked to start, run, continue or resume a process or workflow rather than this one step, do not continue here: invoke the `workflow` skill with the workflow the user asked for, or `compliance` when they named none, followed by `<project>`; it runs this phase in order, asks before it writes and records the run. Otherwise continue here: a later phase runs on its own, behind its gate.2122Run this skill's gate before writing: `sh <this skill's folder>/scripts/gate.sh <project> <project root>`, where `<project root>` is the folder that contains `.singularskills/` (use `.` when you are already there). If it exits non-zero, stop and tell the user what it printed, unless `--skip-checks` was given (see Arguments). On a refusal, before you stop, append this line to `.singularskills/log.jsonl` (create the folder and file if missing): `{"ts":"<ISO timestamp>","skill":"compliance-vendor-tprm","workflow":"compliance","phase":1,"project":"<project>","event":"refused","artifact":"01-assess/","note":"<what the gate printed>"}`. Once the gate has passed, or under `--skip-checks` once you have appended the `skipped` line, append this line before you start work: `{"ts":"<ISO timestamp>","skill":"compliance-vendor-tprm","workflow":"compliance","phase":1,"project":"<project>","event":"started","artifact":"01-assess/","note":""}`.2324Read `.singularskills/compliance/<project>/00-scope.md`. If this file does not exist, tell the user:2526> Phase 0 (Scope) has not been completed for "<project>". Run `/compliance-regulatory-landscape <project>` first, or use `--skip-checks` to bypass.2728## Process29301. **Read context files:**31 - Read `references/grc-lifecycle-guide.md` for GRC methodology reference32 - Read `references/assessment-template.md` for output structure33 - Read `.singularskills/compliance/<project>/00-scope.md` for scope and control framework context34352. **Vendor identification and classification:**36 - Assess vendor inventory completeness (all third parties identified and cataloged)37 - Evaluate risk-based classification methodology (critical, high, medium, low risk)38 - Review classification criteria: data access, system connectivity, business impact, regulatory scope, replaceability39 - Assess vendor categorization by type (cloud services, SaaS, professional services, outsourced operations, subcontractors)40 - Evaluate concentration risk assessment (dependency on single vendors, geographic concentration)41423. **Due diligence process:**43 - Assess pre-engagement due diligence procedures per risk tier44 - Evaluate security questionnaire process (SIG, CAIQ, custom questionnaires)45 - Review SOC report analysis (SOC 2 Type II, SOC 1, bridging letters, complementary user entity controls)46 - Assess penetration testing and vulnerability assessment requirements for vendors47 - Evaluate financial stability assessment (credit reports, financial statements, insurance coverage)48 - Review legal and regulatory compliance verification (certifications, licenses, regulatory actions)49 - Assess business continuity and disaster recovery capability evaluation50 - Evaluate privacy impact assessment for vendors processing personal data51524. **Contractual requirements:**53 - Assess Data Processing Agreement (DPA) coverage and adequacy54 - Evaluate Service Level Agreements (SLAs) with measurable metrics and remedies55 - Review security addenda and minimum security requirements56 - Assess right-to-audit clauses and audit facilitation provisions57 - Evaluate breach notification requirements (timelines, content, cooperation)58 - Review data return/destruction clauses upon termination59 - Assess liability, indemnification, and insurance requirements60 - Evaluate subprocessor approval and notification rights61625. **Ongoing monitoring:**63 - Assess periodic reassessment cadence per risk tier (annual for critical, biennial for high, etc.)64 - Evaluate continuous monitoring signals (security ratings, breach notifications, news monitoring)65 - Review performance monitoring against SLAs and KPIs66 - Assess incident and near-miss tracking for vendor-related events67 - Evaluate vendor relationship governance (steering committees, business reviews)68 - Review compliance certificate and certification renewal tracking69 - Assess trigger-based reassessment procedures (material changes, incidents, M&A)70716. **Offboarding procedures:**72 - Assess data return and destruction procedures (certificates of destruction, verification)73 - Evaluate access revocation process (system access, physical access, credentials)74 - Review knowledge transfer requirements for critical vendors75 - Assess transition planning and migration support obligations76 - Evaluate post-termination confidentiality and data handling obligations77787. **Subprocessor management:**79 - Assess subprocessor identification and approval workflow80 - Evaluate notification obligations for subprocessor changes (advance notice period)81 - Review flow-down requirements (security, privacy, compliance obligations)82 - Assess objection rights and procedures for subprocessor changes83 - Evaluate fourth-party risk visibility and oversight84858. **Program governance:**86 - Assess TPRM policy and procedures documentation87 - Evaluate roles and responsibilities (TPRM team, business owners, legal, security, privacy)88 - Review TPRM tooling and automation (GRC platform, vendor risk management system)89 - Assess reporting and metrics (vendor risk dashboards, board reporting)90 - Evaluate exception and risk acceptance processes91929. **Write the artifact** to `.singularskills/compliance/<project>/01-assess/vendor-tprm.md` following the assessment template structure with:93 - **Vendor Inventory** — completeness and risk classification coverage94 - **Due Diligence** — process maturity per risk tier and assessment coverage95 - **Contractual Framework** — DPA, SLA, security, and audit clause coverage96 - **Ongoing Monitoring** — reassessment cadence, continuous monitoring, and performance tracking97 - **Offboarding** — data destruction, access revocation, and transition procedures98 - **Subprocessor Management** — identification, approval, and flow-down requirements99 - **Program Governance** — policy, roles, tooling, and reporting100 - **Evidence Inventory** — existing evidence and evidence gaps101 - **Remediation Priorities** — ranked list of gaps to address102103## Output104105The vendor TPRM assessment written to `.singularskills/compliance/<project>/01-assess/vendor-tprm.md`. Present a summary to the user highlighting:106- Vendor inventory completeness and risk classification coverage107- Due diligence and contractual coverage rates by risk tier108- Ongoing monitoring maturity and reassessment compliance109- Top 3 gaps requiring remediation110111**Record the run.** After you have written the artifact, append this line to `.singularskills/log.jsonl` (the `started` line of Prerequisites, with `"event":"finished"`): `{"ts":"<ISO timestamp>","skill":"compliance-vendor-tprm","workflow":"compliance","phase":1,"project":"<project>","event":"finished","artifact":"01-assess/","note":""}`.112113Open the artifact with this frontmatter (`agent` is the agent you run in, or `unknown`; `gate` is `passed` when the gate ran clean and `skipped` under `--skip-checks`):114115```yaml116---117skill: compliance-vendor-tprm118workflow: compliance119phase: 1120project: <project>121started: <ISO timestamp>122finished: <ISO timestamp>123agent: <the agent you run in, or "unknown">124gate: <passed|skipped>125---126```127128End the artifact with `## Decisions` and `## Open questions`, in this shape:129130```markdown131## Decisions132- <what was chosen> — <why> — <what was rejected>133134## Open questions135- <what the next phase or a reviewer must settle>136```137138End the artifact with this paragraph, verbatim:139140> **Not legal or audit advice.** This artifact supports preparation for compliance work; certification, attestation and regulatory conclusions require a qualified auditor or counsel.