Vulnerability Disclosure Policy
The Presidio Trust is committed to ensuring the security of the American public by protecting their information. This policy is intended to give security researchers clear guidelines for conducting vulnerability disclosure activities and to convey our preferences for how to submit discovered vulnerabilities to us.
This policy describes
what systems and types of research are covered under this policy,
how to send vulnerability reports to the Presidio Trust, and how long the Presidio Trust asks security researchers to wait before publicly disclosing vulnerabilities.
The Presidio Trust encourages security researchers to report vulnerabilities they’ve discovered – as set out in this policy – so we can fix them. We have developed this policy to reflect our values and uphold our sense of responsibility to security researchers who share their expertise with us in good faith.
This policy applies to systems and services directly within the following domains:
Any service not expressly listed above, such as any connected services, are excluded from scope and are not authorized for testing. We ask that active research and testing be only conducted on the systems and services covered by the scope of this document.
Vulnerabilities found in non-federal systems from our vendors 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 is in scope or not, contact us via email at the Security Contact for the system’s domain listed in the .gov WHOIS database before starting your research.
If there is a particular system not in scope that you think merits testing, please contact us to discuss it first.
If you comply with this policy during your security research, we will consider your research to be authorized. We will work with you to understand and resolve the issue quickly.
Unauthorized Test Methods
The following methods are not authorized:
- Network denial of service (DoS or DDoS) tests or other tests that impair access to or damage a system or data
- Physical testing (e.g. office access, open doors, tailgating), social engineering (e.g. phishing, vishing), or any other non-technical vulnerability testing
Under this policy, “research” means activities in which you:
- Notify us as soon as possible after you discover a real or potential security or privacy issue.
- Provide us a reasonable amount of time to resolve the issue before you disclose it publicly.
- 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’s presence. Do not use an exploit to compromise or exfiltrate data, establish persistent command line access, or use the exploit to “pivot” to other systems.
- Do not submit a high volume of low-quality reports.
Once you’ve established that a vulnerability exists or encounter any sensitive data (including personally identifiable information, financial information, or proprietary information or trade secrets of any party),
you must stop your test, notify us immediately, and not disclose this data to anyone else.
Reporting a Vulnerability
We accept vulnerability reports via the submission form below. Reports may be submitted anonymously.
To assist with the triaging and prioritization of submissions, we ask that your reports:
- Describe the vulnerability, where it was discovered, and the potential impact of exploitation.
- Offer a detailed description of the steps needed to reproduce the vulnerability (proof of concept script or screenshots are helpful).
- Be in English, if possible.
By submitting a vulnerability, you acknowledge that you have no expectation of payment and that you expressly waive any future pay claims against the U.S. Government related to your submission.