Last updated on September 29, 2024
Data security and compliance are top priorities for Overalls because they are fundamental to your experience with the product and the trusted relationship we aim to build with our Clients and Users. Overalls uses a variety of industry-standard technologies and services to secure User and Client Data from unauthorized access, disclosure, use, and loss.
All Overalls employees undergo background checks before employment and are trained on security practices during company onboarding and on an annual basis. Security is directed by Overalls’s Lead Architect and maintained by Overalls’s Security and Operations Team.
Overalls uses Heroku, a Platform as a Service (PAAS), to host its web application. Heroku deploys all applications on Amazon Web Services (AWS). AWS data centers feature a layered security model, including extensive safeguards such as:
As described in this Amazon Web Services whitepaper: “The AWS infrastructure has been architected to be one of the most flexible and secure cloud computing environments available today… AWS uses redundant and layered controls, continuous validation and testing, and a substantial amount of automation to ensure that the underlying infrastructure is monitored and protected 24x7.”
Overalls employees do not have physical access to AWS data centers, servers, network equipment, or storage.
Please use these embedded links to learn more about the security and compliance practices at Heroku or AWS.
Overalls is the assigned administrator of its infrastructure on Heroku, and only designated authorized Overalls engineering team members have access to configure the infrastructure on an as-needed basis behind a two-factor authenticated secure network.
Overalls undergoes annual penetration testing conducted by an independent, third-party agency. For testing, Overalls provides the agency with a high-level diagram of application architecture, and no customer data is exposed to the agency through penetration testing.
Information about any security vulnerabilities successfully exploited through penetration testing is used to set mitigation and remediation priorities, or a rationale is documented for taking alternate action. A summary of penetration test findings is available to customers or upon request.
Heroku and Amazon Web Services undergo various third-party independent audits regularly and can provide verification of compliance controls for its data centers, infrastructure, and operations. This includes, but is not limited to, the SSAE 18-compliant SOC 2 certification and ISO 27001 certification.
Overalls and Heroku’s intrusion detection and prevention systems (IDS/IPS) rely on both signature-based security and algorithm-based security to identify traffic patterns that are similar to known attack methods.
IDS/IPS involves tightly controlling the size and make-up of the attack surface, employing controls at data entry points, and leveraging services that automatically remedy dangerous situations, as well as preventing access to known threats.
In the event of a catastrophic event that renders Heroku inaccessible for an unacceptable amount of time, Overalls will re-provision the Overalls application onto Google Cloud. The decision to execute this redeploy and its oversight are the responsibility of the most senior Overalls technical member who has been able to verify their personal safety.
Because of the similarities between Heroku and Google Cloud, the expectation is that there is a maximum of 24 hours of down time while the new Google Cloud is provisioned from the company's code backup, which is stored in the GitHub repository hosting service and Overalls’ data backup which is stored the Overalls data lake on FiveTran. Github is integrated with the Overalls platform, Heroku as well as the disaster recovery strategy platform Google Cloud. Transitioning from one platform to the other is seamless.
Heroku does maintain accessible backups of their data stores that are in a separate location from the primary data source for the application.
In the event of a region-wide outage, Overalls will bring up a duplicate environment in a different AWS region. The Overalls engineering team has extensive experience performing full region migrations.
All data in Overalls servers is encrypted at rest. Heroku stores and manages data cryptography keys in its redundant and globally distributed Key Management Service. So, if an intruder were ever able to access any of the physical storage devices, the Overalls data contained therein would still be impossible to decrypt without the keys, rendering the information a useless jumble of random characters.
Encryption at rest also enables continuity measures like backup and infrastructure management without compromising data security and privacy.
Overalls exclusively sends data over HTTPS transport layer security (TLS) encrypted connections for additional security as data transits to and from the application.
In addition to the core Overalls platform, Overalls also uses the Kustomer ticketing platform to manage interactions with Users. Kustomer has a robust Privacy Policy and Security Policy and performs several third-party audits on an ongoing basis, including ISO 27001 and SOC 2 Type II.
Overalls retains non-sensitive User Data in production until a user account is deleted. Account deletion may be initiated by a User at any time. Overalls Clients may also request to suspend a User account (for example, if a User leaves the sponsoring company). In this instance, the account is suspended; however non-sensitive User Data will remain in production allowing the User to re-activate their account under a personal subscription.
Overalls Users may share Sensitive Data, including personally identifiable information (PII), personal health information, or financial information, with Overalls in order to allow Overalls to deliver individualized services. Most User Data is collected via the Overalls platform and is protected by the privacy and security measures in accordance with our Privacy and Security Policies. In the case of Sensitive Data that is needed for a one-time-use, for a specific request or other service, we may use a third-party service that encrypts information and automatically destroys information after it is received by Overalls or within a set time limit, so that it is not stored in the Overalls platform.
When a Client terminates their subscription, Client data is deleted from Production in accordance with the “Data Retention” section above, unless otherwise specified in the Master Service Agreement. Upon termination, Users are notified and given the option to create a personal Overalls account. For Users who do not elect to create a personal account, their Data is removed in accordance with the “Data Retention” section above.
The Overalls service includes email engagement and system-generated notifications. Outbound emails for this purpose are delivered through Hubspot and Sendgrid. Follow the embedded links for more information about their security practices.
For transactional emails related to the delivery of Overalls LifeConcierge and other platform services, Overalls uses Gmail for email communications and Twilio for SMS communications.
Overalls practices continuous delivery, which means all code changes are committed, tested, shipped, and iterated on in a rapid sequence. A continuous delivery methodology, complemented by pull request, continuous integration (CI), and automated error tracking, significantly decreases the likelihood of a security issue and improves the response time to and the effective eradication of bugs and vulnerabilities. At time of production release, new code passes through Brakeman, a security vulnerability scanner prior to release. When appropriate, new code is released into Overalls staging for additional QA prior to release. Software is designed to allow for segmented releases to specific client populations. As such, new features are released first to our beta users for additional testing QA prior to release to our GA clients.
At Overalls, we believe that good security practices start with our own team, so we go out of our way to protect against internal threats and local vulnerabilities. Overalls employs a distributed workforce located in the United States, and each employee has a company-provided workstation enrolled in Mobile Device Management (MDM) and Endpoint Detection and Response (EDR) solutions to enforce security settings including full-disk encryption, screen lock, and OS updates. Employees also go through security and privacy trainings.
All new employees receive onboarding and systems training, including environment and permissions setup, formal software development training (if pertinent), security policies review, company policies review, and corporate values and ethics training.
All employees additionally complete security training at least once a year. Policies presented to employees as part of the onboarding process are reviewed once a year to ensure we are keeping up with best practices.
For a complete list of personnel and equipment policies, our full HR Security Policy is available on request.
Overalls conducts background checks for all new hires, including verification on the following:
Overalls follows the risk management procedures outlined in NIST SP 800-30, which include nine steps for risk assessment and seven steps for risk mitigation.
All Overalls product changes must go through code review, CI, and build pipeline to reach production servers. Only designated employees on Overalls’s Engineering team have secure shell (SSH) access to production servers.
We perform testing and risk management on all systems and applications on a regular and ongoing basis. New methods are developed, reviewed, and deployed to production via pull request and internal review. New risk management practices are documented and shared via internal in team meetings and policies documenting best practices.
Overalls performs risk assessments throughout the product lifecycle per the standards outlined in HIPAA Security Rule, 45 CFR 164.308:
The Overalls operations team includes service continuity and threat remediation among its top priorities. We keep a contingency plan in case of unforeseen events, including risk management and disaster recovery plans that are tested and updated on an ongoing basis and thoroughly reviewed for gaps and changes at least annually.
Overalls follows the incident handling and response process recommended by SANS, which includes identifying, containing, eradicating, recovering from, communicating, and documenting security events. In the event of a data breach, Overalls will notify customers as soon as possible via email and phone call, followed by multiple periodic updates throughout each day addressing progress and impact.
Overalls maintains an internal folder of security policies, which is updated on an ongoing basis and reviewed annually for gaps. An overview of specific security policies is available to customers upon request:
Anyone can report a vulnerability or security concern with an Overalls product by contacting help@getoveralls.com and including a description of the concern, screenshot, and information about the system used to access Overalls. We take all disclosures very seriously, and once we receive a disclosure we rapidly verify each vulnerability before taking the necessary steps to fix it. Once verified, we periodically send status updates as problems are fixed.
As part of our commitment to maintaining a robust data security and compliance practice, Overalls has engaged a third party (Drata) to prepare for a SOC 2 Type 1 and Type 2 audits. In addition, over the coming months, Overalls will also conduct an additional penetration and pursue additional third-party attestations including ISO 27001 and HIPAA.