Skip to content

docs: add SECURITY.md to outline vulnerability reporting process #238

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

Open
wants to merge 1 commit into
base: develop
Choose a base branch
from
Open
Changes from all commits
Commits
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
22 changes: 22 additions & 0 deletions SECURITY.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,22 @@
# Security Policy

## Supported Versions

Use this section to tell people about which versions of your project are
currently being supported with security updates.

| Version | Supported |
| ------- | ------------------ |
| 1.5.7 | :white_check_mark: |
| < 1.5.7 | :x: |

## Reporting a Vulnerability

We currently only receive security vulnerability reports through GitHub.

To begin a report, please go to the top-level repository, for example, c-jimenez/open-ocpp, and click on the Security tab. If you are on mobile, click the ... dropdown menu, and then click Security.

Click Report a Vulnerability to open the advisory form. Fill in the advisory details form. Make sure your title is descriptive, and the development team can find all of the relevant details needed to verify on the description box.
We recommend you add as much data as possible. We welcome logs, screenshots, photos, and videos, anything that can help us verify and identify the issues being reported.

At the bottom of the form, click Submit report. The maintainer team will be notified and will get back to you ASAP.