{"id":"b0c22ce5-d000-4652-9fa3-27f6165d44cd","engagementId":"3cd96484-d4d4-4d7a-83f7-6dd5f605d468","data":{"brief":{"id":"5f96440d-6082-4fb6-9a56-fec93ddc690e","name":"Railroad Retirement Board - Vulnerability Disclosure Program","tagline":"Vulnerability Disclosure Program - Powered by Bugcrowd","description":"\u003ch2\u003eIntroduction\u003c/h2\u003e\n\n\u003cp\u003eAs part of a U.S. government agency, the Railroad Retirement Board (RRB) takes seriously our responsibility to protect the railroad public's information, including financial and personal information, from unwarranted disclosure.  A part of this responsibility is allowing security researchers to seek vulnerabilities in the RRB’s systems that support the mission of the agency.\u003c/p\u003e\n\n\u003cp\u003eWe want security researchers to feel comfortable reporting vulnerabilities they've discovered, as set out in this policy, so that we can fix them and keep our information safe.\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\u003chr\u003e\n\n\u003ch2\u003eGuidelines\u003c/h2\u003e\n\n\u003cp\u003eWe require that you:\u003c/p\u003e\n\n\u003cp\u003eMake every effort to avoid privacy violations, degradation of user experience, disruption to production systems, and destruction or manipulation of data.\u003c/p\u003e\n\n\u003cp\u003eOnly 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 below, you must stop your test and notify us immediately.\u003c/p\u003e\n\n\u003cp\u003eKeep confidential any information about discovered vulnerabilities for up to 90 calendar days after you have notified RRB.\u003c/p\u003e\n\n\u003chr\u003e\n\n\u003ch2\u003eLegal\u003c/h2\u003e\n\n\u003cp\u003eYou 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.\u003c/p\u003e\n\n\u003cp\u003eRRB 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.\u003c/p\u003e\n\n\u003cp\u003eTo the extent that any security research or vulnerability disclosure activity involves the networks, systems, information, applications, products, or services of a non-RRB entity (e.g., other 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-RRB third party may independently determine whether to pursue legal action or remedies related to such activities.\u003c/p\u003e\n\n\u003cp\u003eIf you conduct your security research and vulnerability disclosure activities in accordance with the restrictions and guidelines set forth in this policy, (1) RRB 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 RRB, RRB will communicate as appropriate, in the absence of any legal restriction on RRB's ability to so communicate, that your activities were conducted pursuant to and in compliance with this policy.\u003c/p\u003e\n\n\u003chr\u003e","industryTagId":"2a38890b-c88e-4bc0-8db0-02059f3fafe6","targetsOverview":"\u003cp\u003eAny services not expressly listed above, such as any connected services, are excluded from scope and are not authorized for testing. Additionally, 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 or endpoint is in scope or not, contact us at security@rrb.gov before starting your research.\u003c/p\u003e\n\n\u003cp\u003eFor any non-RRB systems, if a contact for that site can't be easily found, we encourage you to report them to the Department of Homeland Security (DHS).\u003c/p\u003e\n\n\u003cp\u003eThe following test types are not authorized:\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003eUser interface bugs or typos.\u003c/li\u003e\n\u003cli\u003eNetwork denial of service (DoS or DDoS) tests. \u003c/li\u003e\n\u003cli\u003ePhysical 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\u003eBrute Force Attacks against login interfaces\u003cbr\u003e\n\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003cp\u003eIf you encounter any of the below on our systems while testing within the scope of this policy, stop your test and notify us immediately:\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003ePersonally identifiable information\u003c/li\u003e\n\u003cli\u003eFinancial information (e.g. credit card or bank account numbers)\u003c/li\u003e\n\u003cli\u003eProprietary information or trade secrets of companies of any party \u003c/li\u003e\n\u003cli\u003eAuthorization\u003c/li\u003e\n\u003c/ul\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, will work with you to understand and resolve the issue quickly, and RRB will not initiate or recommend legal action related to your research.\u003c/p\u003e\n\n\u003chr\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 the Railroad Retirement Board, we may share your report with the Cybersecurity and Infrastructure Security Agency, where it will be handled under their coordinated vulnerability disclosure process.\u003c/p\u003e\n\n\u003cp\u003eReports should include:\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003eDescription of the location and potential impact of the vulnerability.\u003c/li\u003e\n\u003cli\u003eA 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.\u003c/li\u003e\n\u003cli\u003eAny technical information and related materials we would need to reproduce the issue. \u003c/li\u003e\n\u003c/ul\u003e\n\n\u003cp\u003ePlease keep your vulnerability reports current by sending us any new information as it becomes available.\u003c/p\u003e\n\n\u003cp\u003eWe may share your vulnerability reports with US-CERT, as well as any affected vendors or open source projects.\u003c/p\u003e\n\n\u003chr\u003e\n\n\u003ch2\u003eCoordinated Disclosure\u003c/h2\u003e\n\n\u003cp\u003eRRB is committed to patching vulnerabilities within 90 days or less, 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.\u003c/p\u003e\n\n\u003cp\u003eAt 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 us know so we can make arrangements.\u003c/p\u003e\n\n\u003cp\u003eWe may want to coordinate an advisory with you to be published simultaneously with the patch, but you are also welcome to self-disclose if you prefer. By default, we prefer to disclose everything, but we will never publish information about you or our communications with you without your permission. In some cases, we may also have some sensitive information that should be redacted, and so please check with us before self-disclosing.\u003c/p\u003e\n\n\u003chr\u003e\n\n\u003ch2\u003eQuestions\u003c/h2\u003e\n\n\u003cp\u003eQuestions regarding this policy can be sent to security@rrb.gov\u003c/p\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\n\n\u003chr\u003e\n\n\u003cp\u003eThe Cybersecurity and Infrastructure Security Agency (CISA) Vulnerability Disclosure Policy Platform (VDP Platform) gives agencies the option to use a centrally managed system to intake vulnerability information from and collaborate with the public to improve the security of their internet-accessible systems. CISA has a contract with EnDyna and Bugcrowd, private companies, to manage the platform used by the public to report vulnerability information; CISA exercises general oversight of the program.  CISA does not collect, maintain, use, or disseminate any Personally Identifiable Information (PII) provided to Bugcrowd for the purposes of creating a profile on the website or reporting a vulnerability to agencies other than CISA.  Participating agencies provide their own program vulnerability disclosure policy, setting out the agency’s parameters for vulnerability disclosures, including provisions for collection and use of submitted information. Any submissions of vulnerabilities pertaining to CISA’s own information systems would be governed by the DHS VDP brief.\u003c/p\u003e","safeHarborStatus":null,"collaborationEnabled":false,"additionalInformation":""},"scope":[{"id":"8810a956-c2ff-4756-b034-dea52e1a4458","name":"In Scope","targets":[{"id":"fa1c27f7-0e7a-4d97-8fe5-339df1170e8e","uri":"","name":"*.rrb.gov","category":"website","ipAddress":null,"description":null,"engagementBriefTargetGroupTarget":{"id":"ebf15cce-81f7-4684-bf85-674865083ec6","sortOrder":0},"sortOrder":0,"tags":null,"recentChangeFlags":null}],"inScope":true,"sortOrder":1,"description":null,"rewardRange":null,"descriptionHtml":"\u003cp\u003eThis policy applies to the following systems:\u003c/p\u003e","rewardRangeData":{},"recentChangeFlags":null}],"resources":[],"engagement":{"id":"3cd96484-d4d4-4d7a-83f7-6dd5f605d468","code":"rrb-vdp","state":"in_progress","endsAt":null,"bountyId":"5c626653-5bf7-4971-873f-f2607da67f60","startsAt":"2022-03-08T19:00:00Z"},"engagementConfiguration":{"participation":"open","crowdSelectionStrategy":"none"}},"industryName":"Government","methodologyName":null,"logoUrl":"https://logos.bugcrowdusercontent.com/logos/f6fd/44dc/2d7991bd/6664c71e2e14333d4d8ac1f89d52f518_1200px-RRB_seal.svg.png","logoBackgroundColor":"#ffffff","displayDisclosureTerms":true,"coordinatedDisclosure":true,"collaborationEnabled":false,"participation":"open","rewardAllocation":"no_reward","engagementTypeDetail":{"iconVariant":"vdp","productLabel":"Vulnerability Disclosure","timeboxed":false},"pausedReason":null,"lastTransitionAt":"2022-03-08T19:00:00.000Z","cancellationReason":null,"statusLabel":"In progress","routesPaths":{"brief":"/engagements/rrb-vdp","changelogs":"/engagements/rrb-vdp/changelog","submissions":null,"announcements":"/engagements/rrb-vdp/announcements","hallOfFame":"/engagements/rrb-vdp/hall_of_fames","crowdstream":"/engagements/rrb-vdp/crowdstream"},"announcementsCount":0,"knownIssuesEnabled":true,"isDemo":false,"serviceLevel":"Priority Triage","submitReportUrl":"/engagements/rrb-vdp/submissions/new","methodologyUrl":null,"progressPercentage":0,"badgeVariant":null,"userBannedFromEngagement":null,"isLoggedIn":false,"loginUrl":"/user/sign_in","scopedSubmissionsUrl":"/submissions?engagement%5B%5D=rrb-vdp\u0026sort%5B%5D=submitted-desc","isFollowing":null,"credentialsUrl":null,"toggleSubscriptionUrl":"/rrb-vdp/engagement_subscribers","engagementChangelogsUrl":"/engagements/rrb-vdp/changelog","publishedAt":"2022-09-06T17:49:00.588Z","engagementChangelogUrl":"/engagements/rrb-vdp/changelog/b0c22ce5-d000-4652-9fa3-27f6165d44cd","createUserFeedbacksUrl":"/engagements/rrb-vdp/feedbacks","engagementCrowdstreamUrl":"/engagements/rrb-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}