Skip to content

Commit 8a2c1dc

Browse files
committed
Update new format SECURITY.md
1 parent 702f1a3 commit 8a2c1dc

File tree

1 file changed

+3
-7
lines changed

1 file changed

+3
-7
lines changed

Diff for: SECURITY.md

+3-7
Original file line numberDiff line numberDiff line change
@@ -11,19 +11,15 @@ This policy applies to all open source projects developed, maintained, or hosted
1111
## Reporting Security Vulnerabilities
1212
If you believe you've discovered a potential security vulnerability in one of our open source projects, we strongly encourage you to report it to us responsibly.
1313

14-
Please submit your findings as [security advisories](https://github.com/wazuh/wazuh/security/advisories) under the "Security" tab in the relevant GitHub repository. Alternatively, you may send the details of your findings to [[email protected]](mailto:[email protected]).
14+
Please submit your findings as security advisories under the "Security" tab in the relevant GitHub repository. Alternatively, you may send the details of your findings to [[email protected]](mailto:[email protected]).
1515

1616
## Vulnerability Disclosure Policy
1717
Upon receiving a report of a potential vulnerability, our team will initiate an investigation. If the reported issue is confirmed as a vulnerability, we will take the following steps:
1818

1919
1. Acknowledgment: We will acknowledge the receipt of your vulnerability report and begin our investigation.
20-
2120
2. Validation: We will validate the issue and work on reproducing it in our environment.
22-
23-
3. Remediation: We will work on a fix and thoroughly test it.
24-
21+
3. Remediation: We will work on a fix and thoroughly test it
2522
4. Release & Disclosure: After 90 days from the discovery of the vulnerability, or as soon as a fix is ready and thoroughly tested (whichever comes first), we will release a security update for the affected project. We will also publicly disclose the vulnerability by publishing a CVE (Common Vulnerabilities and Exposures) and acknowledging the discovering party.
26-
2723
5. Exceptions: In order to preserve the security of the Wazuh community at large, we might extend the disclosure period to allow users to patch their deployments.
2824

2925
This 90-day period allows for end-users to update their systems and minimizes the risk of widespread exploitation of the vulnerability.
@@ -46,4 +42,4 @@ We ask that all users and contributors respect this policy and the security of o
4642
## Changes to this Security Policy
4743
This policy may be revised from time to time. Each version of the policy will be identified at the top of the page by its effective date.
4844

49-
If you have any questions about this Security Policy, please contact us at [[email protected]](mailto:[email protected]).
45+
If you have any questions about this Security Policy, please contact us at [[email protected]](mailto:[email protected])

0 commit comments

Comments
 (0)