Skip to content

Commit ce8275a

Browse files
authored
Merge pull request #5 from inextensodigital/chore-add-security-template
Chore: Add security template.
2 parents 6c07e35 + 658ac03 commit ce8275a

File tree

1 file changed

+34
-0
lines changed

1 file changed

+34
-0
lines changed

security.md

Lines changed: 34 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,34 @@
1+
## Security
2+
3+
We take the security of our software products and components seriously, which includes all source code repositories managed through our [In Extenso Digital's GitHub organization](https://github.com/inextensodigital).
4+
5+
If you believe you have found a security vulnerability in any In Extenso Digital's repository that meets Wikipedia's definition of a security vulnerability ([English version](https://en.wikipedia.org/wiki/Vulnerability_(computing)), [French version](https://fr.wikipedia.org/wiki/Vuln%C3%A9rabilit%C3%A9_(informatique))), please report it to us as described below.
6+
7+
## Reporting security vulnerability Issues
8+
9+
:warning: **Please do not report security vulnerabilities through public GitHub issues.**
10+
11+
Instead, **please report them by email** to [[email protected]](mailto:[email protected]).
12+
13+
You should receive a response as soon as possible. If for some reason you do not, please follow up via email to our [Administrator Team](mailto:[email protected]) to ensure we received your original message.
14+
15+
For private repositories, you can also send an email or directly use the dedicated issue template for security vulnerability.
16+
17+
:bulb: In any ways, please include the requested information listed below (**as much as you can provide**) to help us better understand the nature and scope of the possible issue:
18+
19+
* Type of issue (e.g. Denial of service, Elevation of privilege, Information disclosure, Remote Code Execution, Security feature bypass, buffer overflow, SQL injection, cross-site scripting, etc.)
20+
* Full paths of source file(s) related to the manifestation of the issue
21+
* The location of the affected source code (tag/branch/commit or direct URL)
22+
* Step-by-step instructions to reproduce the issue, including any special configuration required to reproduce
23+
* (if possible) Proof-of-concept or exploit code
24+
* Description and Impact of the issue, including how an attacker might exploit the issue
25+
26+
This information will help us triage your report more quickly.
27+
28+
## Preferred Languages
29+
30+
We prefer all communications to be in English, but if you are not comfortable, French is acceptable too.
31+
32+
## Policy
33+
34+
In Extenso Digital follows the principle of [Microsoft's Coordinated Vulnerability Disclosure](https://www.microsoft.com/en-us/msrc/cvd).

0 commit comments

Comments
 (0)