-
Notifications
You must be signed in to change notification settings - Fork 40
Added the file #115
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. Weβll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Added the file #115
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,61 @@ | ||
| ## Security Policy | ||
|
|
||
| ## Supported Versions | ||
|
|
||
| The following versions of Edulume are currently supported with security updates: | ||
|
|
||
| | Version | Supported | | ||
| |---------|-----------| | ||
| | 1.x.x | Yes | | ||
| | 0.x.x | No | | ||
|
|
||
| ## Reporting a Vulnerability | ||
|
|
||
| If you discover a security vulnerability in Edulume, we encourage you to report it as soon as possible. We will investigate all legitimate reports and do our best to quickly fix the issue. | ||
|
|
||
| ## How to Report | ||
|
|
||
| Please report vulnerabilities by emailing us at tarinagarwal@gmail.com. Include as much detail as possible to help us identify and fix the issue swiftly. | ||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. π‘ Suggestion β The email address 'tarinagarwal@gmail.com' is hardcoded in the security policy. Hardcoding contact information can make updates harder and may cause inconsistencies if used elsewhere. Consider defining the contact email as a named constant or referencing a centralized contact info file to improve maintainability. readability |
||
|
|
||
| Do not share the vulnerability publicly until it has been addressed and a patch is available. | ||
|
|
||
| ## Security Updates | ||
|
|
||
| We will notify users via GitHub releases for any critical security updates. | ||
| Minor security patches will be included in regular updates as needed. | ||
|
|
||
| ## Response Timeline | ||
|
|
||
| We aim to follow this response process: | ||
|
|
||
| - Initial acknowledgment: within 48 hours | ||
| - Investigation and assessment: within 5β7 business days | ||
| - Fix and patch release: as soon as reasonably possible, depending on severity | ||
|
|
||
| ## Scope of Security Concerns | ||
|
|
||
| The following areas are considered in scope for security reports: | ||
|
|
||
| - Authentication and authorization mechanisms | ||
| - API endpoints and backend services | ||
| - User data handling and storage | ||
| - File uploads and document storage | ||
| - Access control and permission issues | ||
| - Dependency-related vulnerabilities | ||
|
|
||
| The following are out of scope: | ||
|
|
||
| - Social engineering attacks | ||
| - Physical attacks | ||
| - Denial-of-service attacks without proof of concept | ||
|
|
||
| ## Security Best Practices | ||
|
|
||
| - Make sure to use the latest version of Edulume for the latest security features and patches. | ||
| - Follow password best practices, such as using strong, unique passwords for each account. | ||
| - Regularly update your dependencies to the latest versions. | ||
|
|
||
| ## Acknowledgements | ||
|
|
||
| We appreciate contributions from the community and researchers who help us improve the security of Edulume. Thank you for keeping the platform secure for everyone! | ||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
π Medium β The security policy includes an email address for reporting vulnerabilities. Publishing direct email addresses in public repos can lead to spam and phishing risks.
Consider using a dedicated security contact form or a security-specific email alias with spam filtering to handle vulnerability reports securely.
best-practices