Discord

Security

The security and integrity of user data is paramount at HASH. Many businesses, including our own, rely on HASH simulations to process sensitive personally identifiable information, and to predict and manage critical business risks.

We have implemented a mix of physical, human, systems and software security measures to minimize risk. A number of the steps we take are outlined in our Privacy Guarantee. Further details are provided below.

Organizational Security

SOC 2 Compliance

We have an Information Security Program in place that is communicated throughout the organization. Our Information Security Program follows the criteria set forth by the SOC 2 Framework. SOC 2 is a widely known information security auditing procedure created by the American Institute of Certified Public Accountants.

Third-Party Audits

Our organization undergoes independent third-party assessments to test our security and compliance controls at least once a year.

Third-Party Penetration Testing

Our organization undergoes independent third-party assessments to test our security and compliance controls at least once a year.

Confidentiality & Access Control

All HASH employees and contractors sign non-disclosure and confidentiality agreements prior to beginning work.

Access to platform infrastructure is strictly limited to engineers who require such access as part of their role, and we employ role-based access authentication by default throughout our systems (as well as enhanced attribute-based access controls, where available). You can find out more under the ‘Access Security’ section below.

Access permissions are granted based on the principle of least privilege, and we enforce multi-factor authentication across our stack. System access attempts are logged, and controls are in place to prevent brute-force and other attacks. You can find out more under the ‘Logging and Monitoring’ section below.

Roles and responsibilities related to our Information Security Program and the protection of our customer’s data are well defined and documented. Our team members are required to review and accept all of our security policies before their first day at HASH.

Security Awareness Training

All HASH employees and contractors are required to go through security awareness training covering industry standard practices and information security topics such as phishing and password management.

Background Checks

We perform background checks on all new employees in accordance with local laws.

Cloud Security

Cloud Infrastructure Security

All of our services are hosted with Amazon Web Services (AWS), Google Cloud Platform (GCP), Microsoft Azure (Azure) and Cloudflare. They employ a robust security program with multiple certifications. For more information on our provider’s security processes, please visit AWS SecurityGCP Security, Azure Compliance and Cloudflare Compliance.

Encryption at Rest

All HASH databases are encrypted at rest.

Encryption in Transit

All HASH data in encrypted in transit using SSL/TLS.

Vulnerability Scanning

We perform vulnerability scanning and actively monitor for threats.

Logging and Monitoring

We stringently log access and activity (both actual and attempted) across our services, and actively monitor these logs.

Business Continuity and Disaster Recovery

We use our data hosting provider’s backup services to reduce any risk of data loss in the event of a hardware failure. We utilize monitoring services to alert the HASH team in the event of any failures affecting users.

Incident Response

We have a process for handling information security events which includes escalation procedures, rapid mitigation and communication. The HASH live status page can be found at status.hash.ai

Payment Processing

Our payment processor, 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 in the payments industry.

Vendor Security & Risk Management

In addition to our Cloud Security policies (outlined above), we have processes in place to qualify all other vendors of HASH in relation to security, information inter.

Annual Risk Assessment

We undergo at least annual risk assessments to identify any potential threats, including considerations for fraud, social and insider risk.

Vendor Risk Management

Vendor risk is determined and the appropriate vendor reviews are performed prior to authorizing a new vendor.

Access Security

Permissions and Authentication

Access to cloud infrastructure and other sensitive tools are limited to authorized employees who require it for their role.

Where available we have Single Sign-On (SSO), Multi-Factor Authentication (MFA) and strong password policies to ensure access to cloud services are protected.

Least Privilege Access Control

We follow the principle of least privilege with respect to identity and access management.

Quarterly & Continuous Access Reviews

We perform across-the-board standing quarterly access reviews. In practice, access is checked more regularly than this and processes are in place to automatically and centrally monitor access on an ongoing basis.

Password Requirements

All team members are required to adhere to a minimum set of password requirements and complexity for access, in addition to ensuring uniqueness across services.

Password Management

All HASH employees, contractors, and company issued devices utilize a password manager for team members to manage passwords and maintain password complexity.

Bug Bounty

Invitation To Test

We value the work of security researchers who help keep our users safe. To show our appreciation we operate a bug bounty that rewards the responsible, confidential disclosure of vulnerabilities.

Bounty Terms and Conditions

At its discretion, HASH may reward the responsible disclosure of design or implementation issues that could be used to undermine the confidentiality or integrity of our users’ data. Qualifying vulnerabilities must:

  1. be disclosed to us privately with reasonable time to respond;
  2. avoid compromising other users and accounts; and
  3. avoid the loss of funds that are not your own.

We do not reward reports relating to (i) denial of service, (ii) spam, or (iii) phishing/social engineering vulnerabilities, and do not permit research in relation to these to take place on our live systems without express prior written permission. To request such permission, please let us know your specific research interest by reaching out directly through the form at hash.ai/contact and await a response.

Additional Information

If you have any additional concerns or queries, please get in touch with us directly via the form at hash.ai/contact.

Policy last updated on 2021-01-03