Skip to content

Update SECURITY.md #151

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.

Sign up for GitHub

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

Open
wants to merge 1 commit into
base: main-2.0
Choose a base branch
from
Open

Update SECURITY.md #151

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
24 changes: 11 additions & 13 deletions SECURITY.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,23 +1,21 @@
<!--
SPDX-FileCopyrightText: 2019-2022 Alliander N.V.
SPDX-FileCopyrightText: 'Copyright Contributors to the weather-provider-api project'

SPDX-License-Identifier: MPL-2.0
-->
# Security Policy

## Supported Versions
# Security

At Alliander, we consider the security of our systems and software a top priority. But no matter how much effort we put into system security, there can still be vulnerabilities present.

The following versions of the API and its libraries are currently being supported:
If you discover a vulnerability, we would like to know about it so we can take steps to address it as quickly as possible. We would like to ask you to help us better protect our clients and our systems.

| VERSION | SUPPORTED |
| ------- | ---------------------- |
| 3.0.x | :x: *(in development)* |
| 2.x | :white_check_mark: |
| < 2.0 | :x: |
## Report a security issue

## Reporting a Vulnerability
Use the contact details on the [Alliander.com Vulnerability Reporting page](https://www.alliander.com/en/coordinated-vulnerability-disclosure/).

To report a vulnerability, please directly contact us at: weather.provider@alliander.com
Please describe clearly how the issue can be reproduced, so we can fix it quickly. Typically, the IP address or URL of the affected system and a description of the vulnerability are sufficient. We may contact you if we need more information about a complex vulnerability.

Upon receiving information on this vulnerability, we will aim to either immediately repair it, or issue a warning via the discussion board, depending on the ease with which it can be fixed. In both cases we will aim to solve the vulnerability as fast as possible.
## Thanks

Should a vulnerability pose an extremely high risk, we may decide to flag releases as "High Risk", and we may issue temporary releases with limited functionality, to prevent our users from being unnecessarily at risk. These events will also be advertised on the Discussions board, and these "High Risk" and "Limited Functionality" releases will be tagged as such.
We don't have a bug bounty program, but we're grateful for all the reports we get. We offer an Alliander Security hoodie as a reward for significant security problems.
Loading