Skip to content

Security Overview

Fp Switchboard is designed with security at its core. This page outlines our security architecture and practices.

Encryption at Rest

All tokens encrypted with AES-256-GCM

Encryption in Transit

TLS 1.3 for all connections

Zero Trust

Every request authenticated and authorized

Audit Logging

Complete audit trail for all operations

OAuth tokens and API keys are encrypted before storage:

  • Algorithm: AES-256-GCM
  • Key Management: Keys stored in Cloudflare Workers secrets
  • Per-Tenant Keys: Each organization has unique encryption keys

Fp Switchboard tokens (e.g., fps_unified_xxx) are stored as hashes:

  • Algorithm: SHA-256 with salt
  • Lookup: First 8 characters used for fast lookup
  • Verification: Full hash comparison for authentication
StageSecurity Measure
GenerationCryptographically secure random bytes
StorageEncrypted at rest, hashed for verification
TransmissionTLS 1.3 only
RevocationImmediate, tokens cannot be “unrevoked”
ExpirationConfigurable, default 90 days

All traffic passes through Cloudflare:

  • WAF — Web Application Firewall blocks common attacks
  • DDoS Protection — Automatic mitigation
  • Bot Management — Blocks automated attacks
  • Rate Limiting — Prevents abuse

The dashboard at switchboard.fpdigital.ai is protected by:

  • Cloudflare Access — Identity-aware proxy
  • SSO Integration — Enterprise SSO supported
  • MFA Required — Multi-factor authentication enforced

Each organization’s data is isolated:

  • Separate encryption keys
  • Database-level isolation (org_id on all tables)
  • No cross-organization queries possible
  • Primary: Cloudflare global network
  • Audit Logs: Cloudflare R2 (configurable region)
  • EU Option: Available for enterprise customers
Data TypeStorageEncryption
OAuth tokensCloudflare D1AES-256-GCM
Fp tokensCloudflare D1SHA-256 hash
Audit logsCloudflare R2AES-256
User profilesCloudflare D1At rest
  • User passwords (SSO only)
  • Raw API responses
  • Personal data from connected services
  • Tool call results (beyond audit summary)
  • Dashboard: Cloudflare Access (SSO/email)
  • API: Bearer token authentication
  • OAuth: Per-service OAuth flows
  • Role-Based: User, Org Admin, Platform Admin
  • Service-Level: Users can only access connected services
  • Token-Level: Tokens scoped to specific services/bundles
  • Penetration Testing: Annual third-party assessment
  • Dependency Scanning: Automated daily scans
  • Code Review: All changes reviewed before deployment

Found a vulnerability? Email security@fpdigital.ai

  • We respond within 24 hours
  • We don’t pursue legal action for good-faith reports
  • We credit researchers (if desired)
  • Real-time anomaly detection
  • Automated alerting for suspicious patterns
  • 24/7 monitoring
  • Enterprise SLA: 1-hour response
  • Standard SLA: 4-hour response
  • Post-incident reports within 5 business days

SOC 2 Type II

Certified for security, availability, and confidentiality

GDPR

Compliant with EU data protection requirements

HIPAA

BAA available for healthcare organizations

PCI-DSS

Compliant handling of payment data

See Compliance for detailed compliance information.

Yes. Your OAuth tokens are encrypted with AES-256-GCM before storage. Even if our database were compromised, the tokens would be useless without the encryption keys, which are stored separately in Cloudflare Workers secrets.

No. We have technical controls preventing employee access to customer data. Audit logs track all administrative access. Access to production systems requires approval and is logged.

  1. Revoke the token immediately from the dashboard
  2. All associated access is terminated instantly
  3. Generate a new token
  4. Review audit logs for unauthorized access
  • Critical vulnerabilities: Patched within 24 hours
  • High severity: Patched within 7 days
  • Routine updates: Monthly maintenance window