Skip to content

Commit

Permalink
Create SECURITY.md
Browse files Browse the repository at this point in the history
  • Loading branch information
ruberino authored and andreasnp committed Dec 13, 2024
1 parent d1cdbbc commit 6ce94d7
Showing 1 changed file with 31 additions and 0 deletions.
31 changes: 31 additions & 0 deletions SECURITY.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,31 @@
# Security Policy

## Supported Versions

The following table outlines the versions of our project that are currently supported with security updates:

| Version | Supported |
| ------- | ------------------ |
| 16.0.x | :white_check_mark: |
| < 16.0 | :x: |

## Reporting a Vulnerability

We encourage users to report security vulnerabilities to help us maintain the safety and integrity of our project. Please follow these steps to report a vulnerability:

1. **Open an Issue:** Navigate to the [Issues](https://github.com/helsenorge/refero/issues) section of our repository and create a new issue.

2. **Use the "Security" Label:** When creating the issue, apply the "Security" label to categorize it appropriately.

3. **Provide Detailed Information:** Include comprehensive details about the vulnerability, such as:
- Steps to reproduce the issue
- Potential impact
- Any suggested solutions or mitigations

4. **Response Time:** Our team will acknowledge and begin investigating reported vulnerabilities within one week during business days. We will keep you informed about the progress and any actions taken.

5. **Confidentiality:** To protect our users, please refrain from publicly disclosing the vulnerability until we have addressed it and released a fix.

By adhering to this process, you assist us in ensuring the security and reliability of our project.

*Note: This policy is based on best practices for vulnerability management and coordinated disclosure.* [Learn more](https://docs.github.com/en/code-security/getting-started/adding-a-security-policy-to-your-repository)

0 comments on commit 6ce94d7

Please sign in to comment.