From 15d604d4f6a16c1c01d2196c00773e4858c2cd88 Mon Sep 17 00:00:00 2001 From: Christian Fasching Date: Mon, 6 May 2024 14:16:44 +0200 Subject: [PATCH] Update security reporting --- doc/26_Best_Practice/75_Security_Concept.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/26_Best_Practice/75_Security_Concept.md b/doc/26_Best_Practice/75_Security_Concept.md index 8bd94ae99e6..511536d76d2 100644 --- a/doc/26_Best_Practice/75_Security_Concept.md +++ b/doc/26_Best_Practice/75_Security_Concept.md @@ -65,8 +65,8 @@ This issue can be resolved either by using Pimcore [Headscript extension](../02_ ### Handling Security Issues In the case of a security issue/vulnerability in the Pimcore core framework, we handle them with the following procedure: - **Reporting Issue**: -Report issue via [Pimcore Security form](https://pimcorehq.wufoo.com/forms/pimcore-security-report/), not via public -issue tracker (according guidelines also available at public issue tracker). +Report issue via [Github security advisory mechanism]([https://pimcorehq.wufoo.com/forms/pimcore-security-report/](https://docs.github.com/en/code-security/security-advisories/guidance-on-reporting-and-writing-information-about-vulnerabilities/privately-reporting-a-security-vulnerability#privately-reporting-a-security-vulnerability) of the corresponding repository, e.g. for [here for core framework](https://github.com/pimcore/pimcore/security). Not via public +issue tracker (according guidelines also available at public issue tracker)! - **Resolving Issue**: - Reported issue is forwarded directly forwarded to Pimcore core team, verified and if confirmed resolved in following steps