Fix Markdown lint issues in Secure Product Design Cheat Sheet #1835
+15
−10
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
szh
requested changes
Sep 29, 2025
| 8. Have a practiced Security Incident response plan: Having a plan in place for how to respond to a security incident is essential for minimizing the damage caused by any successful attack and a crucial part of the Product Support Model. | ||
|
|
||
| Details of how to precisely ensure secure configuration can be found in [Infrastructure as Code Security Cheat Sheet](Infrastructure_as_Code_Security_Cheat_Sheet.md) | ||
| - [OWASP Secure Product Design Cheat Sheet](https://cheatsheetseries.owasp.org/cheatsheets/Secure_Product_Design_Cheat_Sheet.html) |
There was a problem hiding this comment.
This would be a circular link...
|
|
||
| Details of how to precisely ensure secure configuration can be found in [Infrastructure as Code Security Cheat Sheet](Infrastructure_as_Code_Security_Cheat_Sheet.md) | ||
| - [OWASP Secure Product Design Cheat Sheet](https://cheatsheetseries.owasp.org/cheatsheets/Secure_Product_Design_Cheat_Sheet.html) | ||
| - [CISA Secure by Design Guidelines](https://www.cisa.gov/secure-design) |
There was a problem hiding this comment.
This page doesn't appear to exist...
There was a problem hiding this comment.
Oh also, the changes in the PR are much more extensive than the PR description.
|
Hi @szh, all requested link fixes and formatting issues have been updated. |
…in Secure Product Design Cheat Sheet
szh
requested changes
Sep 29, 2025
|
I do not see a reason to update this markdown, our linter likes this version and it looks good in markdown and on the website. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR addresses the markdown lint issues in the Secure Product Design Cheat Sheet only.
It is a follow-up to PR #1790, which was closed because it unintentionally included changes to multiple cheat sheets. This new PR ensures:
Secure_Product_Design_Cheat_Sheet.mdis modifiedNo other cheat sheets are affected.
Closes #1790 (supersedes previous PR).