RingMD forces HTTPS for all connections including our public website. We also use HTTP Strict Transport Security(HSTS) to ensure browses interact with our servers only over HTTPS.
Uploaded files and call recording are both transmitted and stored using AES-256 encryption on Amazon’s Simple Storage Service (S3) in multiple data centers around the world.
Messages & notifications
All RingMD messages and notifications are encrypted with Secure WebSocket connection when transmitted between the server and users.
RingMD Payment follows Payment Card Industry Data Security Standard. No customer's credit card is stored on our system. The actual card's information is stored with our payment gateway - Stripe. Stripe has been audited by a PCI-certified auditor and is certified to PCI Service Provider Level 1.
Payment information from the RingMD server sends to the Stripe server using TLS 1.2.
Each RingMD white label tenant is using a separate AWS account for hosting and development. Each customer has their own set of cloud infrastructure, hosted on an AWS data center close to the tenant. We do not mix data tables between customers. This is a major step in preventing cross-pollination or contamination of data.
All the changes to RingMD's infrastructure in the cloud are logged permanently with AWS CloudTrail to AWS S3.
On the application level, all access or changes to user data triggers an immutable audit record.
RingMD offers industry standard two-factor authentication mechanisms such as the use of a physical token or an authenticator app as a second factor to authenticate users. In order to log in and access personal data, users must comply with a valid password and a 6 digit code from the authenticator app or physical token.
RingMD’s product security team has built a robust development lifecycle, which primarily leverages industry standard tools and strategies.
Training and security enforcement
RingMD takes security seriously with a mandatory security training program for new employees. We work to raise awareness internally and externally through seminars and training programs.
RingMD enforces two-factor authentication for all the tools we use internally, where applicable.
Code review is one of the effective techniques for identifying security flaws. When used together with automated tools and manual penetration testing, internal and external code review can significantly increase the security effectiveness of an organization.
RingMD uses Github for source code hosting. All code should be peer-reviewed before getting merged to our repositories via pull requests.
We enable Github Vulnerability alerts and use Snyk analyzing the current code base and the new source codes added automatically as an additional check for new pull requests. All code should be vulnerability-free before getting reviewed by peers.
Infrastructure as code
RingMD uses TerraForm to form all of our enterprise-level infrastructure. We conduct code review and anything added to the infrastructure is verified before getting merged and apply to the targeted AWS account.