{"engagementBriefUrl":"https://bugcrowd.com/engagements/doi-vdp","earlyFetchProps":{"code":"doi-vdp","engagementCrowdstreamUrl":"/engagements/doi-vdp/crowdstream","headerProps":{"name":"Department of Interior: Vulnerability Disclosure Program","tagline":"Submit vulnerabilities to DOI !","state":"in_progress","statusLabel":"In progress","code":"doi-vdp","rewardAllocation":"no_reward","startsAt":"2021-11-02T19:00:00Z","endsAt":null,"logoUrl":"https://logos.bugcrowdusercontent.com/logos/96f0/cd22/c7ebf1be/e298074ca985f3a89f0f87fc67c21fc9_logo.png","logoBackgroundColor":"#ffffff","engagementTypeDetail":{"iconVariant":"vdp","productLabel":"Vulnerability Disclosure","timeboxed":false},"engagementsUrl":"/engagements","badgeVariant":null,"scopeRank":1,"progressPercentage":0},"description":"

Introduction

The Department of the Interior (DOI) 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 discovery activities and to convey our preferences in how to submit discovered vulnerabilities to us.

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

We encourage you to contact us to report potential vulnerabilities in our systems.

Authorization

If you make a good faith effort to 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, and DOI will not recommend or pursue legal action related to your research. Should legal action be initiated by a third party against you for activities that were conducted in accordance with this policy, we will make this authorization known.

Guidelines

Under this policy, “research” means activities in which you:

Notify us as soon as possible after you discover a real or potential security issue.
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 command-line access and/or persistence, or use the exploit to pivot to other systems.
Provide us a reasonable amount of time to resolve the issue before you disclose it publicly.
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. ##Test methods The following test 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
Full red-team penetration testing that involves unauthorized access to our servers

"}}