{"id":"fdb60014-3864-46a0-bd4c-dcf1fed7d8ad","engagementId":"87f44df8-3ec7-4ef3-be3d-ff91f87520a3","data":{"brief":{"id":"4358c322-e853-4f05-9195-0d08da89e8ea","name":"National Park Service","tagline":"Submit your findings here!","description":"\u003cp\u003eThe Department of the Interior (DOI), of which the National Park Service is a bureau, 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.\u003c/p\u003e\n\n\u003cp\u003eThis 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.\u003c/p\u003e\n\n\u003cp\u003eWe encourage you to contact us to report potential vulnerabilities in our systems. Use this form to report vulnerabilities to National Park Service systems.\u003c/p\u003e\n\n\u003ch2\u003eGuidelines\u003c/h2\u003e\n\n\u003cp\u003eYou MUST read and agree to abide by the guidelines in this policy for conducting security research and disclosure of vulnerabilities or indicators of vulnerabilities related to NPS information systems. We will presume you are acting in good faith when you discover, test, and submit reports of vulnerabilities or indicators of vulnerabilities in accordance with these guidelines:\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003eYou MAY test internet-accessible NPS information systems to detect a vulnerability or identify an indicator related to a vulnerability for the sole purpose of providing NPS information about such vulnerability.\u003c/li\u003e\n\u003cli\u003eYou MUST avoid harm to NPS information systems and operations.\u003c/li\u003e\n\u003cli\u003eYou MUST NOT exploit any vulnerability beyond the minimal amount of testing required to prove that the vulnerability exists or to identify an indicator related to that vulnerability.\u003c/li\u003e\n\u003cli\u003eYou MUST NOT intentionally access the content of any communications, data, or information transiting or stored on NPS information system(s) – except to the extent that the information is directly related to a vulnerability and the access is necessary to prove that the vulnerability exists.\u003c/li\u003e\n\u003cli\u003eYou MUST NOT exfiltrate any data under any circumstances.\u003c/li\u003e\n\u003cli\u003eYou MUST NOT intentionally compromise the privacy or safety of NPS personnel (e.g., civilian employees) or any legitimate third parties.\u003c/li\u003e\n\u003cli\u003eYou MUST NOT intentionally compromise the intellectual property or other commercial or financial interests of any NPS personnel or entities or any legitimate third parties.\u003c/li\u003e\n\u003cli\u003eYou MUST NOT disclose any details of any extant NPS information system vulnerability or indicator of vulnerability to any party not already aware at the time the report is submitted to NPS.\u003c/li\u003e\n\u003cli\u003eYou MUST NOT create user (or any) accounts on NPS systems for testing.\u003c/li\u003e\n\u003cli\u003eIn the event that you find a vulnerability in a NPS information system consequent to a vulnerability in a generally available product, you MAY report the product vulnerability to the affected vendor or a third party vulnerability coordination service in order to enable the product to be fixed.\u003c/li\u003e\n\u003cli\u003eYou MUST NOT disclose any incidental proprietary data revealed during testing or the content of information rendered available by the vulnerability to any party not already aware at the time the report is submitted to NPS.\u003c/li\u003e\n\u003cli\u003eYou MUST NOT cause a denial of any legitimate services in the course of your testing.\u003c/li\u003e\n\u003cli\u003eYou MUST NOT conduct social engineering in any form of NPS personnel or contractors.\u003c/li\u003e\n\u003cli\u003eYou SHOULD strive to submit high-quality reports.\u003c/li\u003e\n\u003cli\u003eYou MUST NOT submit a high-volume of low-quality reports.\u003c/li\u003e\n\u003cli\u003eYou MUST comply with all applicable Federal, State, and local laws in connection with security research activities or other participation in this vulnerability disclosure program.\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003cp\u003eSecurity researchers must:\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003eCease testing and notify us immediately upon discovery of a vulnerability.\u003c/li\u003e\n\u003cli\u003eCease testing and notify us immediately upon discovery of an exposure of nonpublic data.\u003c/li\u003e\n\u003cli\u003ePurge any stored NPS nonpublic data upon reporting a vulnerability.\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003ch2\u003eRatings/Rewards:\u003c/h2\u003e\n\n\u003cp\u003e\u003cem\u003eFor the initial prioritization/rating of findings, this program will use the \u003ca href=\"https://bugcrowd.com/vulnerability-rating-taxonomy\" rel=\"nofollow noreferrer\" target=\"_blank\"\u003eBugcrowd Vulnerability Rating Taxonomy\u003c/a\u003e. However, it is important to note that in some cases a vulnerability priority will be modified due to its likelihood or impact. In any instance where an issue is downgraded, a full, detailed explanation will be provided to the researcher - along with the opportunity to appeal, and make a case for a higher priority.\u003c/em\u003e\u003c/p\u003e","industryTagId":"2a38890b-c88e-4bc0-8db0-02059f3fafe6","targetsOverview":"\u003cp\u003eThis policy applies to any internet-accessible information system, application, or website owned, operated, or controlled by the National Park Service, including any web applications hosted on those sites. Contractor information systems operated on behalf of the NPS are not included within the scope of this policy. Any domain/property of the National Park Service not listed in the targets section is out of scope. \u003c/p\u003e\n\n\u003chr\u003e\n\n\u003ch2\u003eLegal / Authorization\u003c/h2\u003e\n\n\u003cp\u003eIf 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.\u003c/p\u003e\n\n\u003cp\u003eThe NPS does not authorize, permit, or otherwise allow (expressly or implicitly) 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. Any activities that are inconsistent with this policy or the law may lead to criminal and/or civil liabilities. Third parties (e.g., any non-NPS entity) may independently determine whether to pursue legal recourse or related. NPS may modify the terms of this policy, or suspend this policy at any time.\u003c/p\u003e\n\n\u003ch2\u003eScope\u003c/h2\u003e\n\n\u003cul\u003e\n\u003cli\u003eThis policy applies to the following systems and services managed by the National Park Service:\n*.nps.gov\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003cp\u003e*.everykidoutdoors.gov\u003cbr\u003e\u003cbr\u003e\n*.sierrawild.gov\u003cbr\u003e\u003cbr\u003e\n*.volunteer.gov\u003c/p\u003e\n\n\u003cp\u003eThis policy applies to any internet-accessible information system, application, or website owned, operated, or controlled by the National Park Service, including any web applications hosted on those sites. Contractor information systems operated on behalf of the NPS are not included within the scope of this policy. Any domain/property of the National Park Service not listed in the targets section is out of scope.\u003c/p\u003e\n\n\u003cp\u003eAny service not expressly listed above, such as any connected services, are excluded from scope and are not authorized for testing. Additionally, vulnerabilities found in 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 at \u003ca href=\"mailto:support@bugcrowd.com\" rel=\"nofollow noreferrer\" target=\"_blank\"\u003esupport@bugcrowd.com\u003c/a\u003e before starting your research (or at the security contact for the system’s domain name listed in the .gov WHOIS).\u003c/p\u003e\n\n\u003cp\u003eThough we develop and maintain other internet-accessible systems or services, we ask that active research and testing only be conducted on the systems and services covered by the scope of this document. If there is a particular system not in scope that you think merits testing, please contact us to discuss it first. We will increase the scope of this policy over time.\u003c/p\u003e\n\n\u003ch2\u003eReporting A Vulnerability\u003c/h2\u003e\n\n\u003cp\u003eInformation submitted under this policy will be used for defensive purposes only—to mitigate or remediate vulnerabilities. If your findings include newly discovered vulnerabilities that affect all users of a product or service and not solely DOI, we may share your report with the Cybersecurity and Infrastructure Security Agency, where it will be handled under their coordinated vulnerability disclosure process. We will not share your name or contact information without express permission.\u003c/p\u003e\n\n\u003cp\u003eWe accept vulnerability reports through this form. Reports may be submitted anonymously. If you share contact information, we will acknowledge receipt of your report within 3 business days.\u003c/p\u003e\n\n\u003cp\u003eWe do not support PGP-encrypted emails. For particularly sensitive information, submit through our HTTPS web form.\u003c/p\u003e\n\n\u003ch2\u003eWhat We Would Like To See From You\u003c/h2\u003e\n\n\u003cp\u003eIn order to help us triage and prioritize submissions, we recommend that your reports:\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003eDescribe the location the vulnerability was discovered and the potential impact of exploitation.\u003c/li\u003e\n\u003cli\u003eOffer a detailed description of the steps needed to reproduce the vulnerability (proof of concept scripts or screenshots are helpful).\u003c/li\u003e\n\u003cli\u003eBe in English, if possible.\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003ch2\u003eWhat You Can Expect From Us\u003c/h2\u003e\n\n\u003cp\u003eWhen you choose to share your contact information with us, we commit to coordinating with you as openly and as quickly as possible.\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003eWithin 3 business days, we will acknowledge that your report has been received.\u003c/li\u003e\n\u003cli\u003eTo the best of our ability, we will confirm the existence of the vulnerability to you and be as transparent as possible about what steps we are taking during the remediation process, including on issues or challenges that may delay resolution.\u003c/li\u003e\n\u003cli\u003eDOI does not provide payment to reporters for submitting vulnerabilities.\u003c/li\u003e\n\u003cli\u003eReporters submitting vulnerabilities to DOI, in so doing, waive any claims to compensation.\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003ch2\u003eDisclosure\u003c/h2\u003e\n\n\u003cp\u003eThe NPS is committed to timely correction of vulnerabilities. However, we recognize that public disclosure of a vulnerability, in absence of a readily available corrective action, likely increases versus decreases risk. Accordingly, we require that you refrain from sharing information about discovered vulnerabilities for 90 calendar days after you have received our acknowledgement of receipt of your report. If you believe others should be informed of the vulnerability prior to our implementation of corrective actions, we require that you coordinate in advance with us.\u003c/p\u003e\n\n\u003cp\u003eWe may share vulnerability reports with the Cybersecurity and Infrastructure Security Agency (CISA), as well as any affected vendors. We will not share names or contact data of security researchers unless given explicit permission.\u003c/p\u003e\n\n\u003ch2\u003eQuestions\u003c/h2\u003e\n\n\u003cp\u003eQuestions regarding this policy may be sent using this form. We also invite you to contact us with suggestions for improving this policy.\u003c/p\u003e\n\n\u003chr\u003e\n\n\u003ch2\u003eSafe Harbor:\u003c/h2\u003e\n\n\u003cp\u003e\u003cstrong\u003eWhen conducting vulnerability research according to this policy, we consider this research to be:\u003c/strong\u003e\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003eAuthorized in accordance with the Computer Fraud and Abuse Act (CFAA) (and/or similar state laws), and we will not initiate or support legal action against you for accidental, good faith violations of this policy;\u003c/li\u003e\n\u003cli\u003eExempt from the Digital Millennium Copyright Act (DMCA), and we will not bring a claim against you for circumvention of technology controls;\u003c/li\u003e\n\u003cli\u003eExempt from restrictions in our Terms \u0026amp; Conditions that would interfere with conducting security research, and we waive those restrictions on a limited basis for work done under this policy; and\u003c/li\u003e\n\u003cli\u003eLawful, helpful to the overall security of the Internet, and conducted in good faith.\u003c/li\u003e\n\u003cli\u003eYou are expected, as always, to comply with all applicable laws.\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003cp\u003e\u003cem\u003eIf at any time you have concerns or are uncertain whether your security research is consistent with this policy, please inquire via support@bugcrowd.com before going any further.\u003c/em\u003e\u003c/p\u003e","safeHarborStatus":{"status":"full","label":"Safe harbor","description":"This engagement is fully committed to providing safe harbor for good-faith security research."},"collaborationEnabled":true,"additionalInformation":""},"scope":[{"id":"2ae21f71-8c29-470d-8de8-1d9113f9fe18","name":"In Scope Targets","targets":[{"id":"46fda6fc-8383-4b4c-bfc6-d89ece6d573b","uri":"https://*.nps.gov","name":"*.nps.gov","category":"website","ipAddress":null,"description":null,"engagementBriefTargetGroupTarget":{"id":"5ce80e98-d690-413a-a0ec-f041b03f8cd2","sortOrder":0},"sortOrder":0,"tags":null,"recentChangeFlags":null},{"id":"b9912cc4-2c8f-4a99-921d-dafea3f811c2","uri":"","name":"*.everykidoutdoors.gov","category":"website","ipAddress":"","description":null,"engagementBriefTargetGroupTarget":{"id":"125bcdf8-15e7-4811-b167-785639534826","sortOrder":0},"sortOrder":0,"tags":null,"recentChangeFlags":null},{"id":"4d03bfc2-89a1-4641-befc-18b41d075528","uri":"","name":" *.sierrawild.gov","category":"website","ipAddress":"","description":null,"engagementBriefTargetGroupTarget":{"id":"5f83c889-69f7-4b5d-8167-4047e04b1d02","sortOrder":0},"sortOrder":0,"tags":null,"recentChangeFlags":null},{"id":"38c660d3-0371-482b-bae6-659b8a5082f9","uri":"","name":" *.volunteer.gov","category":"website","ipAddress":"","description":null,"engagementBriefTargetGroupTarget":{"id":"b11ecf74-21c2-4d9a-9206-09fe3507e673","sortOrder":0},"sortOrder":0,"tags":null,"recentChangeFlags":null}],"inScope":true,"sortOrder":0,"description":null,"rewardRange":null,"descriptionHtml":"\u003ch2\u003eTest Methods\u003c/h2\u003e\n\n\u003cp\u003eThe following test methods are not authorized and are considered Out of Scope:\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003eTest any system other than the systems set forth in the ‘Scope’ section.\u003c/li\u003e\n\u003cli\u003eDisclose vulnerability information except as set forth in the ‘Reporting a Vulnerability’ section below.\u003c/li\u003e\n\u003cli\u003eEngage in physical testing (e.g. office access, open doors, tailgating), social engineering (e.g. phishing, vishing), or any other non-technical vulnerability testing.\u003c/li\u003e\n\u003cli\u003eSend unsolicited electronic mail to NPS users, including “phishing” messages.\u003c/li\u003e\n\u003cli\u003eExecute or attempt to execute “Denial of Service” or “Resource Exhaustion” attacks or introduce malicious software.\u003c/li\u003e\n\u003cli\u003eTest in a manner known to degrade the operation of NPS systems; or intentionally impair, disrupt, or disable NPS systems.\u003c/li\u003e\n\u003cli\u003eTest third-party applications, websites, or services that integrate with or link to or from NPS systems.\u003c/li\u003e\n\u003cli\u003eAttempt to create accounts on NPS system for testing.\u003c/li\u003e\n\u003cli\u003eFull red-team penetration testing that involves unauthorized access to our servers.\u003c/li\u003e\n\u003cli\u003eDelete, alter, share, retain, or destroy NPS data, or render NPS data inaccessible,\u003c/li\u003e\n\u003cli\u003eUse an exploit to exfiltrate data, establish command line access, establish a persistent presence on NPS systems, or “pivot” to other NPS systems.\u003c/li\u003e\n\u003c/ul\u003e","rewardRangeData":{},"recentChangeFlags":null}],"resources":[],"engagement":{"id":"87f44df8-3ec7-4ef3-be3d-ff91f87520a3","code":"nps-vdp","state":"in_progress","endsAt":null,"bountyId":"3cdb2402-6c08-4249-a4f1-3e0fc4549c05","startsAt":"2023-06-20T12:00:00Z"},"engagementConfiguration":{"participation":"open","crowdSelectionStrategy":"none"}},"industryName":"Government","methodologyName":null,"logoUrl":"https://logos.bugcrowdusercontent.com/logos/d5ec/083c/1dba0bd4/b8295fb7faafc9476d78966dd832065a_nps.jpeg","logoBackgroundColor":"#ffffff","displayDisclosureTerms":true,"coordinatedDisclosure":true,"collaborationEnabled":true,"participation":"open","rewardAllocation":"no_reward","engagementTypeDetail":{"iconVariant":"vdp","productLabel":"Vulnerability Disclosure","timeboxed":false},"pausedReason":null,"lastTransitionAt":"2023-06-20T12:00:00.000Z","cancellationReason":null,"statusLabel":"In progress","routesPaths":{"brief":"/engagements/nps-vdp","changelogs":"/engagements/nps-vdp/changelog","submissions":null,"announcements":"/engagements/nps-vdp/announcements","hallOfFame":"/engagements/nps-vdp/hall_of_fames","crowdstream":"/engagements/nps-vdp/crowdstream"},"announcementsCount":2,"knownIssuesEnabled":true,"isDemo":false,"serviceLevel":"Priority Triage","submitReportUrl":"/engagements/nps-vdp/submissions/new","methodologyUrl":null,"progressPercentage":0,"badgeVariant":null,"userBannedFromEngagement":null,"isLoggedIn":false,"loginUrl":"/user/sign_in","scopedSubmissionsUrl":"/submissions?engagement%5B%5D=nps-vdp\u0026sort%5B%5D=submitted-desc","isFollowing":null,"credentialsUrl":null,"toggleSubscriptionUrl":"/nps-vdp/engagement_subscribers","engagementChangelogsUrl":"/engagements/nps-vdp/changelog","publishedAt":"2024-04-30T12:43:34.757Z","engagementChangelogUrl":"/engagements/nps-vdp/changelog/fdb60014-3864-46a0-bd4c-dcf1fed7d8ad","createUserFeedbacksUrl":"/engagements/nps-vdp/feedbacks","engagementCrowdstreamUrl":"/engagements/nps-vdp/crowdstream","acceptedSubmissionsEnabled":false,"disclosedReportsEnabled":true,"engagementsUrl":"/engagements","engagementPaymentDetailUrl":null,"shouldShowHideButton":false,"engagementHiddenData":{},"totalRewardPool":null,"vrtScopeRules":{"data":[]},"vrtVersion":"1.19.1","isSubmissionPublishThrottled":false,"showIdVerificationAlert":false,"identityVerificationSettingsUrl":"https://bugcrowd.com/h/settings/identity_verification","identityUrl":null}