Skip to content

Commit 218a46a

Browse files
docs (SECURITY.md): fix linting errors
1 parent 72132ee commit 218a46a

1 file changed

Lines changed: 10 additions & 5 deletions

File tree

SECURITY.md

Lines changed: 10 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,5 @@
1+
<!-- markdownlint-disable MD033 -->
2+
13
# Security Policy
24

35
* [Security Policy](#security-policy)
@@ -9,12 +11,14 @@
911
* [3. Remediation](#3-remediation)
1012

1113
<a name="reporting"></a>
14+
1215
## Reporting Security Problems
1316

1417
**DO NOT CREATE AN ISSUE** to report a security problem. Instead, please
15-
send an email to burrows_remix6p@icloud.com.
18+
send an email to [burrows_remix6p@icloud.com](mailto:burrows_remix6p@icloud.com).
1619

1720
<a name="contact"></a>
21+
1822
## Security Point of Contact
1923

2024
The security point of contact is Lance Stephens. Lance responds to security incident reports as fast as possible, within one business day
@@ -23,6 +27,7 @@ at the latest.
2327
If they don't respond within two days, please try emailing again.
2428

2529
<a name="process"></a>
30+
2631
## Incident Response Process
2732

2833
In case an incident is discovered or reported, I will follow the following
@@ -32,10 +37,10 @@ process to contain, respond and remediate:
3237

3338
The first step is to find out the root cause, nature and scope of the incident.
3439

35-
- Is still ongoing? If yes, first priority is to stop it.
36-
- Is the incident outside of my influence? If yes, first priority is to contain it.
37-
- Find out knows about the incident and who is affected.
38-
- Find out what data was potentially exposed.
40+
* Is still ongoing? If yes, first priority is to stop it.
41+
* Is the incident outside of my influence? If yes, first priority is to contain it.
42+
* Find out knows about the incident and who is affected.
43+
* Find out what data was potentially exposed.
3944

4045
### 2. Response
4146

0 commit comments

Comments
 (0)