Our CMMC whitepaper has helped over 2000 defense contractors simplify their compliance journey.Download your copy!

Vulnerability Disclosure Policy

Last Updated: June 26, 2024

PreVeil takes our responsibility to protect the public’s information from unwarranted disclosure.

Security researchers should feel comfortable reporting vulnerabilities discovered, as defined in this policy, to afford PreVeil the opportunity to remediate any findings for the to ensure continued confidentiality. 

This policy describes what systems and types of research are covered under this policy, how to send PreVeil vulnerability reports, and how long we ask security researchers to wait before publicly disclosing vulnerabilities.

Scope

Any services not expressly listed above, such as any connected services, are excluded from scope and are not authorized for testing. Additionally, vulnerabilities resulting from our vendors (who are not a part of our FedRAMP boundary) fall outside of this policy’s scope and should be reported directly to the vendor according to their disclosure policy (if any). If you aren’t sure whether a system or endpoint is in scope or not, contact PreVeil via [email protected] before starting your research.

The following test types are not authorized:

  • User interface bugs or typos.
  • Network denial of service (DoS or DDoS) tests.
  • Physical testing (e.g. office access, open doors, tailgating), social engineering (e.g. phishing, vishing), or any other non-technical vulnerability testing.
  • Brute Force Attacks against login interfaces.

If you encounter any of the below on our systems while testing within the scope of this policy, stop your test and notify PreVeil immediately.  Disclosure of the following may not be made to any third party:

  • Personally identifiable information (PII).
  • Financial information (e.g. credit card or bank account numbers).
  • Proprietary information or trade secrets of companies of any party.

Guidelines

Security researchers shall:

  • Make every effort to avoid privacy violations, degradation of user experience, disruption to production systems, and destruction or manipulation of data.
  • Only use exploits to the extent necessary to confirm a vulnerability. Do not use an exploit to compromise or exfiltrate data, establish command line access and/or persistence, or use the exploit to “pivot” to other systems. Once you’ve established that a vulnerability exists, or encountered any of the sensitive data outlined above, you must stop your test and notify PreVeil immediately.
  • Keep confidential any information about discovered vulnerabilities for up to 90 calendar days after you have notified PreVeil. For details, please review Coordinated Disclosure. 

PreVeil is committed to acknowledging receipt of these reports within 3 business days via email sent to [email protected]

Legal

You must comply with all applicable Federal, State, and local laws in connection with your security research activities or other participation in this vulnerability disclosure program.

PreVeil does not authorize, permit, or otherwise allow (expressly or impliedly) any person, including any individual, group of individuals, consortium, partnership, or any other business or legal entity to engage in any security research or vulnerability or threat disclosure activity that is inconsistent with this policy or the law. If you engage in any activities that are inconsistent with this policy or the law, you may be subject to criminal and/or civil liabilities.

To the extent that any security research or vulnerability disclosure activity involves the networks, systems, information, applications, products, or services of a non-PreVeil entity (e.g., Federal departments or agencies; State, local, or tribal governments; private sector companies or persons; employees or personnel of any such entities; or any other such third party), that non-PreVeil third party may independently determine whether to pursue legal action or remedies related to such activities.

If you conduct your security research and vulnerability disclosure activities in accordance with the restrictions and guidelines set forth in this policy, (1) PreVeil will not initiate or recommend any law enforcement or civil lawsuits related to such activities, and (2) in the event of any law enforcement or civil action brought by anyone other than PreVeil, PreVeil will communicate as appropriate, in the absence of any legal restriction on PreVeil’s ability to so communicate, that your activities were conducted pursuant to and in compliance with this policy.

Reporting a vulnerability

You can email vulnerability reports to [email protected].

Note: Do not share sensitive information through commercial email.  If you believe it is necessary to share sensitive information with PreVeil, please do so via the PreVeil end-to-end email and file storage solution. To download a free account for access to secure PreVeil email, please set up your PreVeil account here. 

Reports should include:

  • Description of the location and potential impact of the vulnerability.
  • A detailed description of the steps required to reproduce the vulnerability. Proof of concept (POC) scripts, screenshots, and screen captures are all helpful. Please use extreme care to properly label and protect any exploit code.
  • Any technical information and related materials we would need to reproduce the issue.

Please keep your vulnerability reports current by sending PreVeil any new information as it becomes available, via a secure PreVeil account. We may share your vulnerability reports with US-CERT, as well as any affected vendors or open-source projects.

Coordinated disclosure

PreVeil is committed to patching vulnerabilities within 180 days or less (depending on the vulnerability type and impact) and disclosing the details of those vulnerabilities when patches are published. We believe that public disclosure of vulnerabilities is an essential part of the vulnerability disclosure process, and that one of the best ways to make software better is to enable everyone to learn from each other’s mistakes.

At the same time, we believe that disclosure in absence of a readily available patch tends to increase risk rather than reduce it, and so we request that you refrain from sharing your report with others while we work on our patch. If you believe there are others that should be informed of your report before the patch is available, please let PreVeil know so we can make arrangements.

If you have any questions about this policy, please reach out to [email protected].