Frequently Asked Questions


We go to great lengths to make sure your data is secure. In this article, you'll learn about BigTime’s security protocols.

  • What encryption protocols does BigTime support?
    The BigTime application supports TLS 1.2.
  • How does BigTime protect its publicly accessible systems?
    BigTime resides in a Virtual Private Cloud on Amazon Web Services (AWS). We only permit HTTPS traffic to our web servers through our load balancers. Our databases and support systems that do not require web access are not public-facing. We also rely on AWS Shield, WAF, GuardDuty and Cloudflare to help block suspicious traffic and denial-of-service attacks.
  • Is all client data encrypted?
    All traffic to BigTime is served over HTTPS and all datastores are encrypted. Our snapshots, image-based backups, and sensitive data within the BigTime database are encrypted as well.
  • How is administrative access to BigTime systems secured?
    Administrative access to BigTime systems is tightly controlled and monitored. Selected essential members of the BigTime team have secure remote access capabilities. This access relies on multiple layers of authentication.
  • Does BigTime have a written security policy?
    Yes, BigTime has a written network security policy and our compliance team meets to review and approve all changes to internal security policies.
  • Does BigTime enforce a strong password requirement?
    Yes, client administrators can enable a strong password requirement.
  • How is user security organized within BigTime?
    BigTime offers role-based permissions for login and access to projects and reports.
  • I think I found a vulnerability. How do I report it?
    Any suspected breaches of security or discovered vulnerabilities can be reported to security@bigtime.net for review by our team.

Where to go from here:

Hosting and Architecture

Releases, Upgrades and Changes with BigTime

Was This Helpful?