Log in
Talk to an expert

Security

Security is one of the biggest considerations in everything we do. If you have any questions after reading this, or encounter any issues, please contact us at [email protected]. We implement secure engineering practices in the design and code of CallHub. Our security architecture details are below:

Data Center

CallHub uses Amazon Web Services (AWS) as our cloud infrastructure provider. AWS’s world-class data centers are highly secure, nondescript and have numerous safeguards against perimeter intrusion. They utilize multi-level biometrics and other physical security safeguards to restrict access to the data centers themselves, as well as regions on the data center floor. The full redundancy of these data centers in various locations around the world ensures that CallHub will remain resilient in the event of a disaster or system failure. More details about AWS security is  here.

Network Firewalls

Each system uses firewalls to restrict access to systems from external networks and between systems internally. To mitigate internal and external risk, access is restricted to only the ports and protocols required for specific business needs.

TLS Encryption

CallHub forces HTTPS for all services, including our public website. All web session traffic between your application and CallHub is encrypted using TLS (transport layer security) to protect all of your data. The TLS protocol provides data encryption and authentication between your application and our servers and prevents third parties from stealing information. Sensitive data between applications are protected by access tokens and are encrypted during transmission.

Authentication

To prevent unauthorized account access, each session requires the account username and a strong passphrase for access to each CallHub account. All passwords are stored encrypted with a one-way hashing algorithm resistant to brute-force and dictionary attacks by using a salt. Passwords are not logged. CallHub does not retain any customer credit card information as all data is directly provided to our payment processor, Stripe.

Credit Card

Our payments are processed by Stripe.com. Stripe stores your credit card information on its servers. Your credit card information never reaches our servers, and is never stored there. Stripe has been audited by a PCI-certified auditor, and is certified to PCI Service Provider Level 1. This is the most stringent level of certification available. More details about Stripe security is  here.

Limited Access

CallHub’s policies and procedures limits and logs all external and internal access to customer data and requests management approval prior to access. Internally, only select CallHub employees that deal directly with valid customer tickets are permitted to access customer data. These select groups include, customer support, development, and security teams.

Data Privacy

We take your privacy seriously. Your data is only used in accordance with our privacy policy. Complete details of our privacy policy can be found here.

Disclosure

We rapidly investigate all reported security issues. If you believe you’ve discovered a bug in CallHub’s security, please get in touch at  [email protected] . We will respond as quickly as possible to your report. We request that you not publicly disclose the issue until it has been addressed by CallHub.

CallHub Vulnerability Reporting Policy

At CallHub trust is one of our core values and we take the protection of our customer’s data seriously. CallHub appreciates the role security researchers play in internet security. We encourage responsible reporting of any vulnerabilities that are found in our marketing website or the product.

We have developed a program to make it easier for you (security researchers or customers) to report vulnerabilities to CallHub and to recognize you for your efforts to make the internet a better place. For research into our products, you may refer to our Developer Documentation and any material on the CallHub support forums.

Please review the below scope and guidelines before you test and/or report a vulnerability. CallHub pledges not to initiate legal action against researchers for penetrating or attempting to penetrate CallHub systems as long as they adhere to the below guidelines.

Vulnerability Reporting Program

To appreciate your efforts, CallHub runs a bug bounty program. If you submit a valid report on the eligible products mentioned in the Scope and Description of Vulnerability section in this policy, CallHub will consider your report to our bug bounty program. If the reported vulnerability is accepted by the security team, CallHub will provide the following incentives.

  1. Your full name and gravatar will be mentioned on our Security Hall Of Fame
  2. Organization’s name, email address (as per request)
  3. Links to social profile such as Twitter or LinkedIn or any previous work (as per request)

Note: Currently CallHub doesn’t provide monetary incentives for Vulnerability reporting

Scope and Description of Vulnerability

All CallHub products are in scope for reporting the vulnerabilities. Any design or implementation issue that substantially affects the confidentiality or integrity of user data is covered in the scope of this policy. Common examples include:

  1. XSS – Cross-site scripting
  2. CSRF – Cross-site request forgery
  3. SQL Injection
  4. Mixed-content scripts
  5. MITM – man-in-the-middle Attacks
  6. Authentication or authorization flaws
  7. SSI – Server-side code execution bugs

Following scenarios are not considered a vulnerability

  1. Presence or absence of HTTP headers (X-Frame-Options, nosniff, etc.)
  2. Exposed stack traces or 500 errors
  3. Content spoofing by administrative users

CallHub will reward reports with a significant impact across our entire product portfolio and we encourage you to report bugs via this program based on the below guidelines.

Reporting a potential security vulnerability:

You are requested to adhere to following guidelines while reporting a vulnerability

  • Privately share details of the suspected vulnerability with CallHub by sending an email to [email protected] If you are a customer you can also report the issue to [email protected]
  • Provide full details of the suspected vulnerability so the CallHub team may validate and reproduce the issue
    • Type of issue (cross-site scripting, SQL injection)
      Product and version with the bug or a URL
    • The potential impact of the vulnerability (i.e. what data can be accessed or modified)
    • Step-by-step instructions to reproduce the issue
    • Any proof-of-concept or exploit code required to reproduce the vulnerability

We expect reporters to use their own judgment and provide sufficient details and evidence while reporting the vulnerability.

Responsible Conduct:

While we encourage you to discover and report to us any vulnerabilities you find in a responsible manner, CallHub does not permit the following conduct:

  • Performing actions that may negatively affect CallHub or its users (e.g. Spam, Brute Force, DDoS Attacks)
  • Accessing, or attempting to access, data or information that does not belong to you
  • Destroying or corrupting, or attempting to destroy or corrupt, data or information that does not belong to you
  • Conducting any kind of physical or electronic attack on CallHub personnel, property or data centers
  • Social engineering any CallHub employee or contractor
  • Conduct vulnerability testing of participating services using anything other than test accounts
  • Violating any laws or breaching any agreements in order to discover vulnerabilities

Researchers also commit to not share or publicize the reported (yet unresolved) vulnerability with/to third parties.

CallHub Commitment

Once you report a vulnerability to us, the CallHub team will make efforts to:

  • Respond in a timely manner, acknowledging receipt of your vulnerability report
  • We will investigate all legitimate reports and respond to you with appropriate qualification (Critical, High or Medium) based on the impact
  • Provide an estimated time frame for addressing the vulnerability report
  • Request you for more information on the vulnerability if needed to fix the issue
  • Notify you on when the vulnerability is planned to be addressed 
  • Inform you when the reported vulnerability is fixed

We thank every individual researcher who submits a vulnerability report helping us improve our overall security posture at CallHub.

Security Hall of Fame

CallHub would like to thank the following people who have responsibly disclosed vulnerabilities to us:

Shiraz Ali Khan

Sahil Mehra & Shivam Kamboj Dattana