If you would like to report a vulnerability or have any security concerns with a Hook0 product, please contact [email protected].
Include a proof of concept, a list of tools used (including versions), and the output of the tools. We take all disclosures very seriously. Once disclosures are received, we rapidly verify each vulnerability before taking the necessary steps to fix it. Once verified, we periodically send status updates as problems are fixed.
If you would like to encrypt sensitive information that you send us, our PGP key can be found on Keybase.
We also have an open bug bounty for critical vulnerabilities report regarding Hook0 API (https://app.hook0.com/api/v1/).
Hook0 is hosted on Clever-Cloud Platform. CleverCloud data centers feature a layered security model, including extensive safeguards such as:
Hook0 employees do not have physical access to CleverCloud data centers, servers, network equipment, or storage.
Hook0 is the assigned administrator of its infrastructure on CleverCloud, and only designated authorized Hook0 operations team members to have access to configure the infrastructure on an as-needed basis behind a two-factor authenticated virtual private network. Specific private keys are required for individual servers, and keys are stored in a secure and encrypted location.
CleverCloud undergoes 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 SSAE 16-compliant SOC 2 certification and ISO 27001 certification.
Every part of the Hook0 service uses properly-provisioned, redundant servers (e.g., multiple load balancers, web servers, replica databases) in the case of failure. As part of regular maintenance, servers are taken out of operation without impacting availability.
Hook0 keeps hourly encrypted backups of data in multiple regions on CleverCloud. While never expected, in the case of production data loss (i.e., primary data stores lost), we will restore organizational data from these backups.
In the event of a region-wide outage, Hook0 will bring up a duplicate environment in a different CleverCloud region. The Hook0 operations team has extensive experience performing full region migrations.
At Hook0, 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.
Hook0 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 Hook0 product changes must go through code review, CI, and build pipeline to reach production servers. Only designated employees on Hook0’s operations 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 staff presentations on lessons learned and best practices.
Hook0 performs risk assessments throughout the product lifecycle per the standards outlined in HIPAA Security Rule, 45 CFR 164.308:
The Hook0 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, disaster recovery, and customer communication sub-plans that are tested and updated on an ongoing basis and thoroughly reviewed for gaps and changes at least annually.
Hook0 maintains an internal wiki of security policies, which is updated on an ongoing basis and reviewed annually for gaps.
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 engineers review security policies as part of onboarding and are encouraged to review and contribute to policies via internal documentation. Any change to policy affecting the product is communicated as a pull request, such that all engineers can review and contribute before internal publication. Major updates are communicated via email to all Hook0 employees.
Hook0 follows the incident handling and response process recommended by SANS, which includes identifying, containing, eradicating, recovering from, communicating, and documenting security events. Hook0 notifies customers of any data breaches as soon as possible via email and phone call, followed by multiple periodic updates throughout each day addressing progress and impact. Hook0 Enterprise plans include a dedicated customer success manager who holds responsibility for customer communication, as well as regular check-ins and escalations.
Hook0 maintains a live report of operational uptime and issues on our status page. Any known incidents are reported there, as well as on our Twitter feed.