--- name: finta-security-basics description: 'Secure Finta fundraising data and investor information. Trigger with phrases like "finta security", "finta data privacy". ' allowed-tools: Read, Grep version: 1.0.0 license: MIT author: Jeremy Longshore tags: - saas - fundraising-crm - investor-management - finta compatibility: Designed for Claude Code --- # Finta Security Basics ## Overview Finta manages fundraising pipelines containing investor contact information, term sheet details, valuation data, cap table snapshots, and deal room documents. A breach exposes confidential fundraising strategy, investor relationships, and financial terms that could damage competitive positioning. Protect API credentials, deal room access controls, and any integration that syncs investor data to external CRMs or spreadsheets. ## API Key Management ```typescript function createFintaClient(): { apiKey: string; baseUrl: string } { const apiKey = process.env.FINTA_API_KEY; if (!apiKey) { throw new Error("Missing FINTA_API_KEY — store in secrets manager, never in code"); } // Finta keys access investor contacts and financial terms — treat as highly sensitive console.log("Finta client initialized (key suffix:", apiKey.slice(-4), ")"); return { apiKey, baseUrl: "https://api.trustfinta.com/v1" }; } ``` ## Webhook Signature Verification ```typescript import crypto from "crypto"; import { Request, Response, NextFunction } from "express"; function verifyFintaWebhook(req: Request, res: Response, next: NextFunction): void { const signature = req.headers["x-finta-signature"] as string; const secret = process.env.FINTA_WEBHOOK_SECRET!; const expected = crypto.createHmac("sha256", secret).update(req.body).digest("hex"); if (!signature || !crypto.timingSafeEqual(Buffer.from(signature), Buffer.from(expected))) { res.status(401).send("Invalid signature"); return; } next(); } ``` ## Input Validation ```typescript import { z } from "zod"; const InvestorContactSchema = z.object({ investor_id: z.string().uuid(), firm_name: z.string().min(1).max(200), contact_email: z.string().email(), deal_stage: z.enum(["prospect", "contacted", "meeting", "term_sheet", "closed", "passed"]), check_size: z.number().positive().optional(), valuation_cap: z.number().positive().optional(), }); function validateInvestorData(data: unknown) { return InvestorContactSchema.parse(data); } ``` ## Data Protection ```typescript const FINTA_SENSITIVE_FIELDS = ["valuation_cap", "check_size", "term_sheet_url", "cap_table", "investor_email", "phone"]; function redactFintaLog(record: Record): Record { const redacted = { ...record }; for (const field of FINTA_SENSITIVE_FIELDS) { if (field in redacted) redacted[field] = "[REDACTED]"; } return redacted; } ``` ## Security Checklist - [ ] API keys stored in secrets manager, not in code - [ ] Strong password + 2FA enabled on Finta account - [ ] Deal room access permissions reviewed after each round - [ ] Access revoked for investors who pass on the round - [ ] Data room set to view-only (no download) for early-stage investors - [ ] Connected CRM integration permissions audited quarterly - [ ] Valuation and term sheet data never logged in plaintext - [ ] Pipeline exports encrypted and never committed to git ## Error Handling | Vulnerability | Risk | Mitigation | |---|---|---| | Leaked API key | Full access to investor pipeline and deal terms | Secrets manager + rotation | | Overly broad deal room access | Confidential terms exposed to wrong investors | Per-investor permission scoping | | Unencrypted pipeline exports | Financial strategy leaked via CSV files | GPG encryption + `.gitignore` | | Stale investor access | Former prospects retain document access | Post-round access review | | CRM sync without redaction | Valuation data leaks to third-party CRM | Field-level redaction before sync | ## Resources - [Finta Website](https://www.trustfinta.com) - [OWASP API Security Top 10](https://owasp.org/www-project-api-security/) ## Next Steps See `finta-prod-checklist`.