Skip to content
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

chore: add security-related #391

Merged
merged 2 commits into from
Apr 22, 2024
Merged
Show file tree
Hide file tree
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
5 changes: 4 additions & 1 deletion .github/ISSUE_TEMPLATE/config.yml
Original file line number Diff line number Diff line change
@@ -1,2 +1,5 @@
blank_issues_enabled: false

contact_links:
- name: "Crash bug"
url: https://github.com/LinuxSuRen/api-testing/SECURITY.md
about: "Please file any crash bug with [email protected]."
18 changes: 18 additions & 0 deletions SECURITY.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,18 @@
## Reporting Security Issues

Check notice on line 1 in SECURITY.md

View check run for this annotation

Codacy Production / Codacy Static Code Analysis

SECURITY.md#L1

Expected: [None]; Actual: ## Reporting Security Issues

Check notice on line 1 in SECURITY.md

View check run for this annotation

Codacy Production / Codacy Static Code Analysis

SECURITY.md#L1

First line in a file should be a top-level heading

The API Testing commnity takes a rigorous standpoint in annihilating the security issues in its software projects. API Testing is highly sensitive and forthcoming to issues pertaining to its features and functionality.

Check notice on line 3 in SECURITY.md

View check run for this annotation

Codacy Production / Codacy Static Code Analysis

SECURITY.md#L3

Expected: 80; Actual: 218

## REPORTING VULNERABILITY

If you have apprehensions regarding API Testing's security or you discover vulnerability or potential threat, don’t hesitate to get in touch with the api-testing Security Team by dropping a mail at [[email protected]](mailto:[email protected]). In the mail, specify the description of the issue or potential threat. You are also urged to recommend the way to reproduce and replicate the issue. The API Testing community will get back to you after assessing and analysing the findings.

Check notice on line 7 in SECURITY.md

View check run for this annotation

Codacy Production / Codacy Static Code Analysis

SECURITY.md#L7

Expected: 80; Actual: 524

PLEASE PAY ATTENTION to report the security issue on the security email before disclosing it on public domain.

Check notice on line 9 in SECURITY.md

View check run for this annotation

Codacy Production / Codacy Static Code Analysis

SECURITY.md#L9

Expected: 80; Actual: 110

## VULNERABILITY HANDLING

An overview of the vulnerability handling process is:

The reporter reports the vulnerability privately to API Testing community.
The appropriate project's security team works privately with the reporter to resolve the vulnerability.

Check notice on line 16 in SECURITY.md

View check run for this annotation

Codacy Production / Codacy Static Code Analysis

SECURITY.md#L16

Expected: 80; Actual: 103
A new release of the API Testing product concerned is made that includes the fix.
The vulnerability is publically announced.
Loading