From ea1cb273c3b5d06f2699a9773e8b2a63532ac8a3 Mon Sep 17 00:00:00 2001 From: Mike Rossman <38231021+RikeMossman@users.noreply.github.com> Date: Tue, 20 Aug 2024 15:22:32 -0700 Subject: [PATCH 1/4] INFOSEC-10276 Update report-security-vulnerabilities.mdx Updating disclosure URL to our public bounty through Bugcrowd. --- .../report-security-vulnerabilities.mdx | 13 +++++-------- 1 file changed, 5 insertions(+), 8 deletions(-) diff --git a/src/content/docs/security/security-privacy/information-security/report-security-vulnerabilities.mdx b/src/content/docs/security/security-privacy/information-security/report-security-vulnerabilities.mdx index 78887796f56..26c581a07b3 100644 --- a/src/content/docs/security/security-privacy/information-security/report-security-vulnerabilities.mdx +++ b/src/content/docs/security/security-privacy/information-security/report-security-vulnerabilities.mdx @@ -8,9 +8,9 @@ metaDescription: New Relic partners with bug bounty platforms to make it as easy redirects: - /docs/security/new-relic-security/data-privacy/reporting-security-vulnerabilities - /docs/security/new-relic-security/data-privacy/report-security-vulnerabilities - - /docs/security/new-relic-security/data-privacy/report-security-vulnerabilities-hackerone - - /docs/security/new-relic-security/information-security/report-security-vulnerabilities-hackerone - - /docs/security/security-privacy/information-security/report-security-vulnerabilities-hackerone + - /docs/security/new-relic-security/data-privacy/report-security-vulnerabilities-bugcrowd + - /docs/security/new-relic-security/information-security/report-security-vulnerabilities-bugcrowd + - /docs/security/security-privacy/information-security/report-security-vulnerabilities-bugcrowd freshnessValidatedDate: never --- @@ -22,14 +22,11 @@ If you believe you have found a security vulnerability in one of our products or New Relic partners with established bug bounty platforms to make it as easy as possible for researchers to report security vulnerabilities to us. In recognition of the effort involved in finding these issues, we may provide bounties for eligible reports. -After many years, New Relic is transitioning our coordinated disclosure program to Bugcrowd in March 2024. - -* Reports to the HackerOne program will pause on March 11, 2024 and close fully on March 29, 2024. -* The new Bugcrowd program will open initially as a private program. +New Relic has officially transitioned our coordinated disclosure program to BugCrowd. To participate in the coordinated disclosure program: -1. Ensure that you're familiar with [our policies with HackerOne](https://hackerone.com/newrelic) before initiating any security testing. +1. Please ensure that you're familiar with and follow [our Bugcrowd policies](https://bugcrowd.com/newrelic-mbb-og-public) before initiating any security testing. 2. Only test against accounts you control. ## Customer security issues [#customer-issues] From d61f232e8d7d4b13a846621743537733367e3149 Mon Sep 17 00:00:00 2001 From: Mike Rossman <38231021+RikeMossman@users.noreply.github.com> Date: Tue, 20 Aug 2024 16:21:07 -0700 Subject: [PATCH 2/4] Legal Team Revisions Revisions required from the legal review. --- .../information-security/report-security-vulnerabilities.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/content/docs/security/security-privacy/information-security/report-security-vulnerabilities.mdx b/src/content/docs/security/security-privacy/information-security/report-security-vulnerabilities.mdx index 26c581a07b3..bfbd8338ec9 100644 --- a/src/content/docs/security/security-privacy/information-security/report-security-vulnerabilities.mdx +++ b/src/content/docs/security/security-privacy/information-security/report-security-vulnerabilities.mdx @@ -26,8 +26,8 @@ New Relic has officially transitioned our coordinated disclosure program to BugC To participate in the coordinated disclosure program: -1. Please ensure that you're familiar with and follow [our Bugcrowd policies](https://bugcrowd.com/newrelic-mbb-og-public) before initiating any security testing. -2. Only test against accounts you control. +1. You must agree to the Bugcrowd Researcher Terms & Conditions and ensure that you're familiar with and follow [our Bugcrowd policies](https://bugcrowd.com/newrelic-mbb-og-public) before initiating any security testing. +2. You will be prompted to create a New Relic account that can be used only for permitted testing activity and with the applicable [Terms of Service](https://newrelic.com/termsandconditions/terms). ## Customer security issues [#customer-issues] From 9489e32b008c9f4fb876e90ebb1f8f41c13f7b67 Mon Sep 17 00:00:00 2001 From: Mike Rossman <38231021+RikeMossman@users.noreply.github.com> Date: Wed, 21 Aug 2024 07:10:50 -0700 Subject: [PATCH 3/4] Final Commit - Update URL Updated URL --- .../information-security/report-security-vulnerabilities.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/content/docs/security/security-privacy/information-security/report-security-vulnerabilities.mdx b/src/content/docs/security/security-privacy/information-security/report-security-vulnerabilities.mdx index bfbd8338ec9..fb58052cf0f 100644 --- a/src/content/docs/security/security-privacy/information-security/report-security-vulnerabilities.mdx +++ b/src/content/docs/security/security-privacy/information-security/report-security-vulnerabilities.mdx @@ -26,7 +26,7 @@ New Relic has officially transitioned our coordinated disclosure program to BugC To participate in the coordinated disclosure program: -1. You must agree to the Bugcrowd Researcher Terms & Conditions and ensure that you're familiar with and follow [our Bugcrowd policies](https://bugcrowd.com/newrelic-mbb-og-public) before initiating any security testing. +1. You must agree to the Bugcrowd Researcher Terms & Conditions and ensure that you're familiar with and follow [our Bugcrowd policies](https://bugcrowd.com/engagements/newrelic-mbb-og-public) before initiating any security testing. 2. You will be prompted to create a New Relic account that can be used only for permitted testing activity and with the applicable [Terms of Service](https://newrelic.com/termsandconditions/terms). ## Customer security issues [#customer-issues] From a00195dee6da60db10d2eb64f7acab151179e0a0 Mon Sep 17 00:00:00 2001 From: cbehera-newrelic Date: Thu, 22 Aug 2024 11:28:57 +0530 Subject: [PATCH 4/4] Update report-security-vulnerabilities.mdx The redirect paths are reverted back. --- .../report-security-vulnerabilities.mdx | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/src/content/docs/security/security-privacy/information-security/report-security-vulnerabilities.mdx b/src/content/docs/security/security-privacy/information-security/report-security-vulnerabilities.mdx index fb58052cf0f..2318ef4a5bc 100644 --- a/src/content/docs/security/security-privacy/information-security/report-security-vulnerabilities.mdx +++ b/src/content/docs/security/security-privacy/information-security/report-security-vulnerabilities.mdx @@ -8,9 +8,9 @@ metaDescription: New Relic partners with bug bounty platforms to make it as easy redirects: - /docs/security/new-relic-security/data-privacy/reporting-security-vulnerabilities - /docs/security/new-relic-security/data-privacy/report-security-vulnerabilities - - /docs/security/new-relic-security/data-privacy/report-security-vulnerabilities-bugcrowd - - /docs/security/new-relic-security/information-security/report-security-vulnerabilities-bugcrowd - - /docs/security/security-privacy/information-security/report-security-vulnerabilities-bugcrowd + - /docs/security/new-relic-security/data-privacy/report-security-vulnerabilities-hackerone + - /docs/security/new-relic-security/information-security/report-security-vulnerabilities-hackerone + - /docs/security/security-privacy/information-security/report-security-vulnerabilities-hackerone freshnessValidatedDate: never ---