Add security-report.yaml issue template
This commit is contained in:
49
.gitea/issue_template/security-report.yaml
Normal file
49
.gitea/issue_template/security-report.yaml
Normal file
@@ -0,0 +1,49 @@
|
|||||||
|
name: Security Report
|
||||||
|
about: Report a security vulnerability or concern
|
||||||
|
title: "[Security] "
|
||||||
|
labels:
|
||||||
|
- security
|
||||||
|
- priority:high
|
||||||
|
body:
|
||||||
|
- type: textarea
|
||||||
|
id: vulnerability
|
||||||
|
attributes:
|
||||||
|
label: Vulnerability Description
|
||||||
|
description: Describe the security issue
|
||||||
|
validations:
|
||||||
|
required: true
|
||||||
|
- type: dropdown
|
||||||
|
id: component
|
||||||
|
attributes:
|
||||||
|
label: Affected Component
|
||||||
|
options:
|
||||||
|
- SSH Keys / Authentication
|
||||||
|
- Firewall / Network
|
||||||
|
- API Tokens / Secrets
|
||||||
|
- DNS / Tunnels
|
||||||
|
- Docker / Containers
|
||||||
|
- Web Application
|
||||||
|
- Database
|
||||||
|
- CI/CD Pipeline
|
||||||
|
- Physical Access
|
||||||
|
- type: dropdown
|
||||||
|
id: severity
|
||||||
|
attributes:
|
||||||
|
label: Severity
|
||||||
|
options:
|
||||||
|
- Critical (active exploitation possible)
|
||||||
|
- High (significant risk)
|
||||||
|
- Medium (limited exposure)
|
||||||
|
- Low (theoretical risk)
|
||||||
|
validations:
|
||||||
|
required: true
|
||||||
|
- type: textarea
|
||||||
|
id: reproduce
|
||||||
|
attributes:
|
||||||
|
label: Steps to Reproduce
|
||||||
|
description: How can the vulnerability be demonstrated?
|
||||||
|
- type: textarea
|
||||||
|
id: fix
|
||||||
|
attributes:
|
||||||
|
label: Suggested Fix
|
||||||
|
description: How should this be remediated?
|
||||||
Reference in New Issue
Block a user