OAuth 2.0 PKCE & Token Encryption
We strictly adhere to OAuth 2.0 Web Server Flow with Proof Key for Code Exchange (PKCE). Access and refresh tokens are encrypted at rest using industry-standard AES-256-GCM.
- Cryptographically salted per-tenant encryption keys
- Zero plaintext OAuth credentials stored on disk or in logs
- Instant token revocation on connection disconnect
Database Multi-Tenant Isolation
A2Z Connector implements strict row-level and connection-pool isolation. Every flow, mapping rule, execution record, and credential is bound to an authenticated tenant ID.
- Hard user-partitioning across PostgreSQL & Supabase
- Scoped connection pools preventing cross-tenant leakage
- Role-Based Access Control (Admin vs Standard Member)
Ephemeral In-Flight Execution
Your operational data belongs to you. Intermediate Salesforce records, Xero invoices, and Slack messages are processed in-flight in volatile memory and never permanently written to database tables.
- Zero long-term payload caching or CRM data hoarding
- Sub-millisecond stream transformations in memory
- Transient memory garbage collection immediately upon dispatch
Audit Logging & Data Retention
Execution logs capture operational telemetry (timestamps, node outcomes, error codes) for troubleshooting. You maintain total sovereignty over your log lifecycle.
- Automated 30-day log purge cycle to prevent data buildup
- 1-click global purge to instantly wipe all historical logs
- Full JSON & CSV export for external SIEM / compliance ingest
Transport & Network Defense
All inbound webhooks, user browser traffic, and outbound API calls enforce TLS 1.3 cryptographic transport with HSTS. Built-in rate limiting mitigates brute-force attacks.
- TLS 1.3 with Perfect Forward Secrecy on all endpoints
- Distributed IP rate-limiting on authentication & reset routes
- Account lockout after 5 consecutive failed login attempts
Developer Pedigree & App Reviews
Architected by Certified Salesforce Platform Developers and Cloud Integration Engineers at MSD Automations. Built for enterprise AppExchange, Google OAuth, and Xero partner review standards.
- Strict scope minimization (only requested SObjects/APIs)
- Comprehensive audit trails for compliance validation
- Dedicated vulnerability response team and disclosure protocol
Technical Security & Cryptographic Specifications
Below is the technical specification of the controls and cryptographic standards implemented across the A2Z Connector platform:
| Security Control | Technical Standard | Implementation Detail |
|---|---|---|
| OAuth Refresh Tokens | AES-256-GCM + PBKDF2 | Encrypted with per-tenant initialization vectors (IV) and cryptographic salt prior to database storage. |
| In-Transit Encryption | TLS 1.3 / HTTPS | All ingress (webhooks, browser) and egress (Salesforce, Stripe, Xero, Slack APIs) traffic encrypted in transit. |
| Database Isolation | PostgreSQL Row Partitioning | Every query enforces tenant constraint (WHERE user_id = :authenticatedUserId). No cross-tenant reads. |
| Authentication Engine | JWT + bcrypt (12 rounds) | Signed JSON Web Tokens with automated expiration, secure HTTP-only session tokens, and cryptographic password hashing. |
| Log Lifecycle Policy | Configurable / 30-Day Auto-Purge | Execution logs automatically purged after 30 days. On-demand full wipe and CSV/JSON export supported anytime. |
| DDoS & Brute Force | Sliding-Window Rate Limiting | IP-based rate limiters protect auth endpoints (max 10 attempts / 15 min window) with automated IP lockouts. |
Responsible Vulnerability Disclosure
We take security reports with highest priority. If you believe you have discovered a vulnerability, security bug, or compliance issue in A2Z Connector, please contact our security team directly.