Skip to content

Commit

Permalink
Update security reporting (#17014)
Browse files Browse the repository at this point in the history
  • Loading branch information
fashxp committed May 6, 2024
1 parent fb78bee commit f922419
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions doc/26_Best_Practice/75_Security_Concept.md
Expand Up @@ -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
Expand Down

0 comments on commit f922419

Please sign in to comment.