Outcome

• Deliver a 30-second and a 2-minute pitch (Sec, IT, Legal).
• Map to three pains: downstream reuse, liability, supply-chain duties.

Pitch

Short: “PastWipe makes copied or exfiltrated data non-reusable. Like cancelling a stolen credit card — validations fail post-breach or policy change.”

Long: “RepSec™ adds an attestable control to data interactions. Apps validate tokens before use; breach toggles neutralize reuse. SLO ≤ 75 ms; integrate via SDK/CLI/API.”

Flow (10–12 min)

1. Current post-exfiltration playbook & lessons.
2. Top 3 systems & access patterns for sensitive data.
3. Owner/budget for downstream risk; timeline & trigger.

Qual fields

• Metric: datasets & reuse surface.
• Economic buyer & decision path.
• Criteria: speed (≤75ms), attestation, auditability.

Capture

• Validations vs Declines (invalid/expired/no token).
• Median validation latency (rolling 120).
• Spike/baseline to explain jitter.

Narrative

Show pre-breach validates, then simulate breach: subsequent validations decline → copied data becomes unusable.

Method

1. Identify datasets & reuse scenarios.
2. Quantify exposure window & attempts.
3. Apply neutralization coverage & validation rate.
4. Translate to avoided legal/ops costs & fines risk.

Essentials

• Tiers & discounts: Bronze / Silver / Gold.
• Registration rules & lock periods.
• Commissions accrue after customer payment.

Control plane

• Attestation authority • token service • validation path.
• Policy: breach-trigger, time-bound, context-bound.

Threats & mitigations

• Token theft/replay ➜ short TTL, signed claims, nonce.
• Offline access ➜ deny on validation failure; audit trail.

Install

• SDK: add package, set API base & key.
• CLI: download, make executable, configure profile.

Quick use

• Issue token → validate (allow/deny) → rotate key.
• Toggle breach policy and observe declines.

Endpoints (concept)

• Auth — obtain/rotate keys.
• Issue — signed token with policy claims.
• Validate — fast decision; audit trail.
• Neutralize — breach/policy update.

Errors & retries

• Fail-closed on timeout; idempotent neutralization.
• Return: allowed / declined / error (retry/backoff).

Targets

• Edge validation (Cloudflare Workers).
• AWS Lambda (API gateway front).
• Okta + SIEM enrichment/telemetry.
• EDR/IR playbooks for containment.

Guardrails

• Median validation ≤ 75 ms (window 120).
• Jitter budget & spike handling.
• Throughput targets (dev / pilot / prod).

Roles

• Pilot Customer • Technical Partner • Partner Bronze/Silver/Gold.
• Access: downloads • docs • support • deal reg.

How-to

• Assign seats; manage renewals/refunds.
• Find invoices & update payment method.

Partners will see

• Registered deals, status, payout timing (after payment).
• PMoR override visibility (if enabled).

Security

• Keys/signing • token revocation • audit trails.
• Neutralization as mitigation; regulator evidence.

Maintain

• Public roadmap (quarterly themes).
• Release notes (date • change • impact • action).