Security is given high importance at VXT. This document provides an overview of our system architecture, with a focus on security, and our security practices.

Architecture diagram.png

At a glance

<aside> ℹ️

Some calls may include a public switched telephone network (PSTN) leg external to VXT, which may not benefit from SRTP encryption, as with any PSTN call.

</aside>

Authentication

VXT utilizes Firebase Authentication, which benefits from Google’s internal expertise managing secure authentication.

Through Firebase Authentication, we offer federated login with Google, Apple, and Microsoft (at current), allowing users to take advantage of account security features offered by these large scale federated identity providers.

Data storage

VXT utilizes Google Cloud Firestore for storing user data, and Google Cloud Storage for storing files such as call recordings. Access control is integrated with Firebase Authentication, and all logic relating to access control goes through a thorough testing and peer review process prior to deployment. Google encrypts data in these services in transit and at rest.

OWASP Top Ten

The following is a summary of our mitigations for OWASP Top Ten vulnerabilities.

A01:2021 - Broken Access Control Access control restrictions are enforced on the server side, with processes in place to ensure nothing slips through the cracks. The principle of least privilege is followed, and cross-origin resource sharing (CORS) is configured correctly.

A02:2021 - Cryptographic Failures Data is never transmitted in clear text, with encryption used as standard. As a rule, we do not roll our own cryptography, and outsource this to industry-leading providers or libraries, as applicable. Payment data is processed by Stripe, and authentication is managed by Firebase Authentication.