Our business is security. It’s built on trust.
Here’s how we earn it.
General Data Protection Regulation
We ensure our data collection and handling practices comply with the General Data Protection Regulation (GDPR) and its rules on data protection, privacy, and transfer. Our continued efforts include appointing a privacy officer, implementing policies and procedures, entering into a Data Processing Addendum with our customers and vendors, providing a list of data subprocessors, training all internal employees on privacy, and reviewing these practices annually with a third-party to ensure they remain effective and current.
HackerOne is GDPR compliant.
Privacy Shield Framework
We adhere to the EU-U.S. and Swiss-U.S. Privacy Shield Frameworks, which were designed by these respective governments to help global companies comply with the various data protection requirements. The Privacy Shield covers how participating organizations use and treat personal data received from the EU, the UK, and Switzerland.
Data Processing Addendum (DPA)
We use a Data Processing Addendum (DPA) to ensure adequate safeguards are put in place to protect customer personal data processed by HackerOne. The DPA obliges us to implement appropriate security measures, limit access to personal data, alert customers to incidents and data requests involving their data, and more.
California Consumer Privacy Act (CCPA)
We comply with the California Consumer Privacy Act (CCPA), which outlines privacy requirements related to data collection, storage, access, and more. We do not sell the personal information we collect to other parties.
Our customers trust us with critical data contained within vulnerability reports and related to their technologies and security efforts. We work hard to ensure every bit of data is safe and protected.
How We Improve Our Own Security
- Building an engineering team experienced in security and penetration testing.
- Using mandatory peer reviews and analysis tools to help identify potentially vulnerable code.
- Encrypting all network communications with SSL/TLS, Perfect Forward Secrecy, and HTTP Strict Transport Security (HSTS).
- Enforcing strong password creation, using two-factor authentication, and storing bcrypt hashes instead of storing user passwords.
We also run our own vulnerability disclosure and bug bounty programs, available at https://hackerone.com/security. We believe in transparency, so reported vulnerabilities are publicly disclosed once confirmed and resolved. Additionally, our latest hacker-powered penetration test results are available for review.
Our Application Security Efforts Include:
- All commits go through mandatory code and security review, along with examination by static analysis.
- Our architecture implements safe-by-default principles to consolidate user input, authorization, and business logic.
- All data access and mutation goes through a framework utilizing strong typing and parameterization to eliminate SQL Injection attacks, as well as enforcing the presence of an anti-CSRF token prior to any data mutation.
- We utilize a strict Content Security Policy and a safe-by-default templating language to effectively neutralize Cross-Site Scripting (XSS).
- We encrypt all network communications with SSL/TLS accompanied with Perfect Forward Secrecy and HTTP Strict Transport Security (HSTS), including being HSTS preloaded in most major browsers.
- All requests pass through multiple rate-limiting methods to protect against brute-force attacks.
- We don't store passwords; we store
bcrypt(15, salt, strcat(password, sha512(app-token, env-token)))
Guardrails to Help Users Stay Aware of Security Responsibilities Include:
- Passwords must be a minimum of 12 characters and pass a zxcvbn strong entropy check.
- User-submitted content (such as attachments and images) is stored in Amazon S3, encrypted at rest using AES-256, and served from a sandboxed domain, protecting from Same-origin Policy attacks.
- Two-factor authentication, IP whitelisting, and SAML are available to further restrict access to accounts.
- Role-based access control allows for granular permissions for team members.
For Infrastructure and Operational Security, Our Efforts Include:
- Network segregation is aggressively deployed between services and environments.
- Databases, files, and backups are encrypted at rest using AES-256.
- All infrastructure access requires two-factor, multi-stage authentication.
- We use Cloudflare to supplement our infrastructure’s resilience.
- Enforced usage of strong passwords, password managers, client encryption, mobile device management, and screen locking.
- All employees undergo a criminal background check prior to hiring.
Security is a never-ending job and we are constantly seeking to improve. If you have any questions about our security efforts or suggestions on how HackerOne could be improved, please let us know at firstname.lastname@example.org.
As part of our commitments to our customers, we further commit to specific Data & Information Security Terms. These cover policy, security, management, incident response, and more to detail how we protect customer data.
We provide our users with a service, and they look to us to ensure we have adequate internal controls over our systems and their data.
We’ve engaged respected third-party firms to audit our infrastructure and security practices, resulting in a System and Organization Controls (SOC) 2 Type II audit report, FedRAMP authorization, ISO 27001 certification, and UK Cyber Essentials certification.
The HackerOne Platform runs on Amazon Web Services (AWS). We recommend you also review their compliance information at aws.amazon.com/compliance.
SOC 2 is a means for ensuring a service provider adequately secures customer data, and the SSAE 18 audit standard assures customers that a provider’s security apparatus is working smoothly. Our SOC 2 Type II report covering the security, availability, and confidentiality trust service criteria is available under NDA to current and prospective customers, but our SOC 3 report is available here for anyone to review.
FedRAMP is a U.S. federal government program that provides a standardized approach to security assessment, authorization, and continuous monitoring of cloud products and services to ensure that the proper level of security is in place when government agencies seek to access them. The program offers a "do once, use many times" authorization model, speeding up the government's adoption of cloud services so that the agencies do not have to individually evaluate the same offerings. We are FedRAMP Authorized at the Tailored Low-Impact SaaS level. Our authorization package can be obtained by agencies from the FedRAMP PMO.
ISO 29147 provides requirements on the disclosure of vulnerabilities in products and services. We are in compliance with these requirements and can help our customers comply as well.
ISO 30111 provides guidelines for how to process and resolve potential vulnerability information in a product or online service. We are in compliance with these requirements and can help our customers comply as well.
The PCI Security Standards Council helps develop and implement security standards for account data protection. We do not store, process, and/or transmit cardholder data, and instead use Stripe, a third-party processor certified as a PCI Level 1 service provider. See how Stripe protects credit card data. For our part in accepting credit cards, we have completed the PCI DSS Self-Assessment Questionnaire and the related Attestation of Compliance, both of which are available upon request.
Section 508 is a U.S. federal law mandating that all information and communications technology used by the government be accessible to people with disabilities. Our platform supports or partially supports this requirement, details of which can be found in our Voluntary Product Accessibility Template (VPAT).
CSA Cloud Security Alliance
The Security Trust Assurance and Risk (STAR) Program encompasses key principles of transparency, rigorous auditing, and harmonization of standards. Companies who use STAR indicate best practices and validate the security posture of their cloud offerings.
The STAR registry documents the security and privacy controls provided by popular cloud computing offerings. This publicly accessible registry allows cloud customers to assess their security providers in order to make the best procurement decisions. View HackerOne's listing here.
We believe all technology contains vulnerabilities and the public plays a crucial role in identifying these gaps.
How We Improve Our Own Security
Since we are a technology company, we encourage the public to seek and report potential security vulnerabilities in our technology, and we even use our own technology to facilitate this process. That includes working with them to resolve the issue and ensuring they are fairly compensated for their discovery.
We also believe in transparency when it comes to our security, and that public disclosure not only reassures our customers, it makes the internet safer for everyone. When valid vulnerabilities are discovered in our technology, they are publicly disclosed once confirmed and resolved. You can see those disclosures on our hacktivity page, which shows information from our vulnerability disclosure and bug bounty programs. Additionally, our latest hacker-powered penetration test results can be freely reviewed.
Transparency also extends to our platform uptime, incidents, and service level agreements, details of which are available on our status page.