SkillVaultskills Browse all 500 skills

Compliance · Version 1.0.0 · Reviewed 2026-08-02

SaaS Vendor Security Reviewer

Make a defensible decision about data access scoping and integration risk with evidence, explicit trade-offs, and a verification plan.

4 method steps 5 documented failure modes 4 diagnostic checks 7 quality gates

Assesses third-party vendor risk based on data access, integration depth, and realistic failure impact.

₹149 one-time

Get this skill archive

What this skill helps you do

  • Data access scoping
  • Integration risk
  • Exit planning

How SaaS Vendor Security Reviewer works

You provide

Requirements, data inventory, and evidence of current controls

It inspects

Requirement type and real implementation for data access scoping

It decides

A integration risk gap list with owners and severity

You verify

One obligation traced end to end to its enforcing system

What it checks first

SaaS Vendor Security Reviewer assesses third-party vendor risk based on data access, integration depth, and realistic failure impact. Use it when the work involves Data access scoping, Integration risk, Exit planning.

  1. Whether an obligation is a legal requirement, a contractual commitment, or internal policy.
  2. Whether a documented control is actually implemented in the system it claims to govern.
  3. Every downstream copy of regulated data, including backups, logs, and analytics.
  4. Who is accountable for each control, since an unowned control is not a control.

Failure modes it recognizes

  • Deletion implemented in the primary store while copies persist in backups, exports, and warehouses.
  • A control described in policy with no implementation, discovered during audit.
  • A subprocessor added without an agreement or the customer notification the contract requires.
  • Retention defined but never enforced by an automated job.
  • Consent collected for one purpose and reused for another without a valid basis.

Answers it will reject

  • Treating a certification report as evidence that a specific control functions.
  • Providing a definitive legal conclusion rather than a structured analysis for qualified review.
  • Relying on contract language to mitigate a risk that is technically preventable.

Decision rules it applies

  • Map every obligation to an implemented control and its evidence, or record it explicitly as a gap.
  • Prefer technical enforcement over documented intent, because intent is not a control.
  • Escalate anything constituting legal advice to qualified counsel and say so plainly.

Evidence it asks for

  • Build a data inventory covering category, purpose, basis, location, retention, and downstream copies.
  • Trace one real request or record end to end through the control being claimed.
  • Record the artifact an auditor would accept as evidence for each control.

The method inside

  1. Map the artifact, actors, boundaries, and invariants relevant to data access scoping.
  2. Trace concrete failure or abuse paths for integration risk; do not report checklist items without a mechanism.
  3. Prioritize exit planning findings by impact, likelihood, confidence, and cost of correction.
  4. Recommend the smallest defensible change, then define how an independent reviewer can verify it.

Deliverables

  • Data access scoping assessment
  • Integration risk decision and action plan
  • Exit planning verification checklist

Evidence requirements

  • Functional and quality requirements
  • Scale, latency, consistency, cost, and compliance constraints
  • Current topology and alternatives considered

Quality gates

  • Every material claim traces to supplied evidence or is labeled as a hypothesis.
  • The response follows the declared deliverable contract.
  • No execution, access, measurement, or verification is invented.
  • Secrets and personal data are redacted rather than repeated.
  • The user receives a concrete independent verification step.
  • The relevant failure modes in this domain were considered rather than only the reported symptom.
  • No listed anti-pattern was recommended as a solution.

Example task

Input

We are onboarding a vendor that needs read access to our customer database. What should the review actually cover?

Expected output

A certification report tells you the vendor has a process, not what happens to your data. Scope the access to the minimum fields, require that access be revocable by you unilaterally, and define the exit path including data deletion evidence before signing...

Boundaries and compatibility

Ideal for

  • Data access scoping: produce a decision or artifact grounded in supplied evidence.
  • Integration risk: produce a decision or artifact grounded in supplied evidence.
  • Exit planning: produce a decision or artifact grounded in supplied evidence.

Out of scope

  • Producing a generic reference architecture without requirements
  • Hiding material trade-offs behind best-practice language

Agent compatibility

  • GitHub Copilot custom agents
  • Claude Agent Skills / SKILL.md
  • Any instruction-following chat model

Tool policy: Advisory by default. No tools are assumed. If the host provides tools, use read-only evidence gathering unless the user explicitly approves a scoped write or execution action.