https://appsec.equinor.com/toolbox/guidelines/secret-scanning/#steps-to-mitigate-a-leak
The bullet points here are rendered in github-flavor markdown as indented, but its not kept in the website:
Actual markdown:
### Steps to mitigate a leak
- Revoke/rotate the exposed secret - `THIS IS PRIORITY #1`
- Depending on risk consequence - considering contacting IT-Security for assistance
- Contact Help Desk at (+47) 51 999 222
- Clean the git history
- If the repo is public/internal, consider making it `private` until the secrets are removed
- Potentially inspect logs
- Do a retrospective with your team
Markdown preview in github:
Website:
All bullets on the same "level"/indentation in the website.
Some markdown renders expect 4 spaces of indentation for nested bullet points. I suggest that this is checked as the nesting of bullet points can give the text and lists different meanings than intended.
https://appsec.equinor.com/toolbox/guidelines/secret-scanning/#steps-to-mitigate-a-leak
The bullet points here are rendered in github-flavor markdown as indented, but its not kept in the website:
Actual markdown:
Markdown preview in github:
Website:
All bullets on the same "level"/indentation in the website.
Some markdown renders expect 4 spaces of indentation for nested bullet points. I suggest that this is checked as the nesting of bullet points can give the text and lists different meanings than intended.