Vendor & Subprocessor Management Policy
| Owner | [Security Owner β to be named: founder/CTO] |
| Approved by | [signatory] |
| Effective date | [set on approval] |
| Review cadence | Annual |
| Version | 0.1 β DRAFT |
| TSC mapping | CC9.2 |
1. Purpose
Section titled β1. PurposeβEnsure third parties that process Company or customer data meet the Companyβs security commitments, and that the Company can demonstrate oversight of them.
2. Subprocessor inventory
Section titled β2. Subprocessor inventoryβThe Company maintains a register of all subprocessors that store or process customer data. Current subprocessors (from the CASA self-assessment Β§1):
| Subprocessor | Purpose | Data |
|---|---|---|
| Clerk | Authentication / identity | User identity |
| Google Cloud | Application hosting (Cloud Run), infra | All platform data |
| Neon | Application database (Postgres) | Orders, PII |
| Cloudflare | R2 object storage, Access, edge/CDN | Documents, PO files |
| Stripe | Billing | Company billing data |
| WhereFour | ERP integration | Order/PO data |
| Prophet21 (Epicor) | Customer ERP integration | Order/PO data |
| Infisical | Secrets management | Credentials |
| 1Password | Secrets / credential vault | Credentials |
| Google Workspace | Email, identity, docs | Company data |
3. Onboarding a new vendor
Section titled β3. Onboarding a new vendorβBefore a vendor processes Company or customer data, the Security Owner:
- Confirms the business need and the data the vendor will touch.
- Collects the vendorβs SOC 2 / ISO 27001 report (or equivalent) as inherited evidence; records the report date and any exceptions.
- Signs a Data Processing Agreement (DPA) where the vendor processes personal data.
- Records the vendor in the register with owner, data class, and review date.
4. Ongoing review
Section titled β4. Ongoing reviewβ- The vendor register is reviewed annually: re-collect current SOC 2/ISO reports, re-confirm DPAs, and re-assess risk.
- Subprocessor SOC 2 reports also serve as the Companyβs inherited evidence for physical security and data-center controls (CC6.4), since all infrastructure is cloud-hosted.
5. Public subprocessor list
Section titled β5. Public subprocessor listβThe Company publishes a current subprocessor list to customers (trust center / website) and updates it when subprocessors change.
6. Review
Section titled β6. ReviewβReviewed at least annually by the Security Owner.