-
Notifications
You must be signed in to change notification settings - Fork 2
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
cafb767
commit 3af368a
Showing
1 changed file
with
28 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,28 @@ | ||
# Security Policy | ||
|
||
## Reporting a Vulnerability | ||
|
||
At SnapSpeak, we take security seriously. If you discover any security issues or vulnerabilities within our project, please let us know immediately. We appreciate your help in making SnapSpeak a safer place for everyone. | ||
|
||
To report a security vulnerability, please email us at [[email protected]](mailto:[email protected]) with the following details: | ||
|
||
- Description of the vulnerability. | ||
- Steps to reproduce the vulnerability. | ||
- Potential impact of the vulnerability. | ||
- Any additional information that could help us understand and address the issue. | ||
|
||
Please refrain from publicly disclosing any security vulnerabilities until we have had an opportunity to investigate and provide a fix. We will work diligently to address the issue and keep you informed of our progress. | ||
|
||
## Security Updates | ||
|
||
We are committed to promptly addressing and disclosing any security vulnerabilities that may arise within SnapSpeak. When a security issue is reported and confirmed, we will take the following steps: | ||
|
||
1. Investigate the reported vulnerability to verify its validity and scope. | ||
2. Develop and test a fix for the vulnerability. | ||
3. Release a security update containing the fix, along with any necessary instructions or mitigations for users. | ||
4. Notify users of the security update via our official communication channels, including our website, blog, and social media. | ||
|
||
We prioritize the security of our users and strive to maintain a transparent and responsive approach to handling security vulnerabilities. | ||
|
||
Thank you for your cooperation and support in helping us keep SnapSpeak safe and secure. | ||
|