SkillVaultskills Browse all 500 skills

Security · Version 1.2.0 · Reviewed 2026-08-02

PII Data Flow Mapper

Find and prioritize exploitable risk in data inventory and deletion path verification with evidence, explicit trade-offs, and a verification plan.

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

Maps personal data through collection, processing, storage, sharing, and deletion, exposing the copies that break deletion guarantees.

₹149 one-time

Get this skill archive

What this skill helps you do

  • Data inventory
  • Deletion path verification
  • Third-party sharing review

How PII Data Flow Mapper works

You provide

Systems inventory, processors, and retention policy

It inspects

Every downstream copy including logs, backups, warehouses

It decides

A deletion path with feasibility per store

You verify

Trace one real record end to end through deletion

What it checks first

PII Data Flow Mapper maps personal data through collection, processing, storage, sharing, and deletion, exposing the copies that break deletion guarantees. Use it when the work involves Data inventory, Deletion path verification, Third-party sharing review.

  1. Trust boundaries and every point where untrusted input crosses one.
  2. Where authorization is enforced relative to where data is accessed.
  3. Secret handling: creation, storage, transmission, rotation, and revocation.
  4. What an attacker gains at each step, which determines whether a finding is material.

Failure modes it recognizes

  • Authorization enforced at the perimeter while internal callers reach the same data unchecked.
  • A single unparameterized query path among many parameterized ones.
  • Sensitive values written to logs or error responses.
  • A dependency vulnerability that is reachable in one code path and unreachable in the rest.

Answers it will reject

  • Reporting theoretical findings as exploitable without a demonstrated path.
  • Blocking a payload signature instead of removing the vulnerability class.
  • Treating obscurity as a control, which delays discovery without preventing exploitation.

Decision rules it applies

  • Prioritize by reachability and blast radius, not by scanner severity.
  • Fail closed on any ambiguity in an access decision.
  • Prefer eliminating the capability over sanitizing input into it.

Evidence it asks for

  • Trace input to sink and name every file and function on the path.
  • Verify the fix by attempting the original exploit path.
  • Check logs for prior exploitation before closing a finding.

The method inside

  1. Establish what is actually true about data inventory from the supplied evidence, and mark what is missing.
  2. Identify the mechanism behind deletion path verification rather than restating the symptom.
  3. Choose the smallest defensible change for third-party sharing review, weighing impact, confidence, effort, and reversibility.
  4. Recommend defense-in-depth and verification

Deliverables

  • Data inventory assessment
  • Deletion path verification decision and action plan
  • Third-party sharing review verification checklist

Evidence requirements

  • Code, configuration, data flows, and trust boundaries
  • Identity, authorization, and deployment context
  • Threat model, controls, and known assumptions

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 need to prove we can honor deletion requests within 30 days. Where do we start?

Expected output

Start by tracing one real record rather than surveying teams, because surveys miss the copies nobody owns. The paths that usually break the guarantee are analytics warehouses, log retention, backups, and third-party processors, each with a different feasible answer...

Boundaries and compatibility

Ideal for

  • Data inventory: produce a decision or artifact grounded in supplied evidence.
  • Deletion path verification: produce a decision or artifact grounded in supplied evidence.
  • Third-party sharing review: produce a decision or artifact grounded in supplied evidence.

Out of scope

  • Authorizing offensive actions against systems without permission
  • Reporting theoretical issues as exploitable without a path

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.