GreyNoise Intelligence, Inc.

Security Policy

Security reporting

Please reach out to for submitting security incidents, confidential issues, or general security concerns.

Amazon Web Services

GreyNoise infrastructure is hosted and managed within Amazon’s secure data centers. GreyNoise leverages all of the platform’s built-in security, privacy and redundancy features. AWS continually monitors its data centers for risk and undergoes assessments to ensure compliance with industry standards. Amazon’s data center operations have been accredited under: ISO 27001, SOC 1 and SOC 2/SSAE 16/ISAE 3402 (Previously SAS 70 Type II), PCI Level 1, FISMA Moderate and Sarbanes-Oxley (SOX).


Data that passes through GreyNoise is encrypted. All connections from the browser to the GreyNoise platform are encrypted in transit using TLS SHA-256 with RSA Encryption. GreyNoise requires HTTPS for all services. While in transit, data is encrypted through HTTPS with at least TLS 1.2.

Background checks

All GreyNoise employees go through a thorough background check.


All employees are trained on security and data handling to ensure that they uphold our strict commitment to the privacy and security of our data.

Mobile device management

We secure our employees' machines and laptops using mobile device management to ensure that each device follows our information security standards, including encryption.

Vulnerability scanning

We keep our systems up to date with the latest security patches and continuously monitor for new vulnerabilities through compliance and security mailing lists. This includes automatic scanning of our infrastructure and code repositories for vulnerable dependencies.

Login credential protection

GreyNoise never collects passwords. GreyNoise supports 2FA and SSO with Google and Auth0. Our password policy adheres to NIST 800-63B, requires a minimum of ten characters, is salted/hashed using bcrypt, and checked against known-breached password lists.

Routine audits

GreyNoise continuously scans the product for service interruptions, performance degradation and security vulnerabilities to immediately alert our engineers and take action when an incident has been detected.

Code deployments

Changes to the platform and infrastructure are thoroughly reviewed by multiple engineers and tested to ensure high availability and a great customer experience. Changes to our codebase are required to include unit tests, integration tests and end-to-end tests. Changes are run against our continuous integration pipeline, which enables us to automatically detect any issues in development. Once a change has completed testing in development, it is manually peer reviewed by two or more members of the engineering team before approval..

Invoice payment

Your payment information is never retained by GreyNoise or stored on our infrastructure but forwarded to a third party: Stripe. Visit Stripe’s Security webpage for more details.

Vulnerability reporting

We deeply appreciate any effort to discover and coordinate the disclosure of security vulnerabilities. GreyNoise does not currently operate a public bug bounty program or offer monetary rewards for vulnerability reports, but individuals may be acknowledged in product security bulletins as appropriate.

If you would like to report a vulnerability in one of our products or services, or have security concerns regarding GreyNoise software or systems, please email

To support a timely and effective response to your report, please include any of the following:

  • Steps to reproduce or proof-of-concept
  • Any relevant tools, including versions used
  • Tool output

GreyNoise takes all vulnerability reports very seriously and aims to rapidly respond and verify the vulnerability before taking the necessary steps to address it. After an initial reply to your disclosure, which should be directly after receiving it, we will update you periodically with our response and remediation status.

Security issues related to GreyNoise-owned domains/properties that we have already assessed for risk and will address in future include:

  • HTTPS configuration, including supported TLS versions & ciphersuites
  • HTTP headers, for purposes including Strict Transport Security, Content Security Policy, and clickjacking/XSS protection
  • DNS records including those related to email (SPF, DKIM, DMARC) and certificate issuance (CAA).


GreyNoise respects your privacy and is committed to protecting your Personal Information (any information that relates to an identified or identifiable individual). Our belief is that any Personal Information provided to us by you is just that: personal and private.

We do not rent, sell or trade your Personal Information.

Our full privacy policy is available at including your data rights. For any privacy related questions, including Data Subject Requests, please email