Security

Secure Development Policy

Secure software development practices for Vertex CRM, including authz, secrets handling, and Meta integration safety.

Reviewed August 2026

1. Purpose

Describe secure software development practices for Vertex CRM.

2. Practices

  • Version-controlled source code with review before production deploy
  • Secrets kept in environment configuration, not hardcoded in repositories
  • Authentication and authorization checks on administrative and tenant routes
  • Input validation on public forms and webhooks; Meta webhook signature verification where enabled
  • Parameterized SQL via the data access layer to reduce injection risk
  • Dependency hygiene and timely upgrades for security fixes
  • Staging/production separation for hosted releases

3. Meta integration safety

OAuth state is HMAC-protected; tokens encrypted at rest when configured; deletion callbacks verify signed requests; unmapped webhook assets are not delivered to arbitrary tenants.

4. Related

Vulnerability management · Encryption · Access control

Last updated: August 2026.